UML Testing Profile 2 Avatar
  1. OMG Specification

UML Testing Profile 2 — All Issues

  • Acronym: UTP2
  • Issues Count: 6
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

UTP should incorporate concepts to speciy decision tables for allowing decision table testing

  • Key: UMLTP22-14
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
  • Summary:

    Decision table testing is a major and frequently used black-box test design technique. In system and acceptance testing as well as testing of business processes, decision table testing is used to identify the test conditions within business rules by representing these rules in a tabluar format.

    The Decision Modeling Notation (DMN) provides a MOF-based metamodel for modeling decision tables. Within the DMN, decition tables are an isolated part, well suited for being extracted as profile as part of UTP.

    Incorporating a decision table profile into UTP, inspired by the DMN MOF-based metamodel, would improve UTP in the area of business rule testing and make UTP more complete regarding specification-oriented test design techniques.

  • Reported: UTP2 2.1 — Mon, 14 Dec 2020 21:24 GMT
  • Disposition: Deferred — $issue.fixedSpecification.name
  • Disposition Summary:

    Deferred due to lack of time

    The RTF agreed that there should be a tighter integration between decision tables and utp2 to perform decision table testing. Due to lack of time, the RTF agreed to defer the resolution of this issue to a subsequence RTF

  • Updated: Fri, 5 Jan 2024 20:27 GMT

UTP should incorporate concepts to speciy decision tables for allowing decision table testing

  • Key: UMLTP23-26
  • Status: open  
  • Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
  • Summary:

    Decision table testing is a major and frequently used black-box test design technique. In system and acceptance testing as well as testing of business processes, decision table testing is used to identify the test conditions within business rules by representing these rules in a tabluar format.

    The Decision Modeling Notation (DMN) provides a MOF-based metamodel for modeling decision tables. Within the DMN, decition tables are an isolated part, well suited for being extracted as profile as part of UTP.

    Incorporating a decision table profile into UTP, inspired by the DMN MOF-based metamodel, would improve UTP in the area of business rule testing and make UTP more complete regarding specification-oriented test design techniques.

  • Reported: UTP2 2.1 — Mon, 14 Dec 2020 21:24 GMT
  • Updated: Fri, 5 Jan 2024 20:27 GMT

Correction of typografical and editorial formatting on specification documents

  • Key: UMLTP22-40
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
  • Summary:

    The specification documents (both ptc/23-04-02 and ptc/23-04-03) that were submitted with the UTP 2.2 RTF report (doc#: ptc/23-04-01) contained some issue with editiorial content. Some words that were set in (bold) blue do not represent links, but the typographical convention for these words are not given in the specification. Furthermore, the newly added clauses made not use of those links at all.

  • Reported: UTP2 2.1 — Fri, 21 Jul 2023 08:47 GMT
  • Disposition: Resolved — $issue.fixedSpecification.name
  • Disposition Summary:

    Complementary editorial/typographical changes from AB comments

    The following resolution and the editing instructions represent complementary editorial corrections of the already submitted specification documents (both ptc/23-04-02 and ptc/23-04-03) because of the Ab review comments recieved after submission of the UTP 2.2 in May 2023 (doc# ptc/23-04-01).
    The editing instructions describe only the delta of changes, thus, all the changes reported by the editing instructions of the formert report (doc# ptc/23-04-01) are present in the new specifications documents. In addition, the new submitted specification documents (ptc/24-07-02 and ptc/23-07-03) contain editing instructions as a result of the AB review of the former submission (ptc/23-04-01).

  • Updated: Fri, 5 Jan 2024 20:12 GMT

Syntactical correction of machine-readable files for UTP 2.2 submision

  • Key: UMLTP22-39
  • Status: closed  
  • Source: Fraunhofer FOKUS ( Mr. Marc-Florian Wendland)
  • Summary:

    The machine-readable files submitted with UTP 2.2 RTF report (doc#: ptc/23-04-01) contained some syntactical issues that prevented the import of the machine readable files into compliant tools.

  • Reported: UTP2 2.1 — Fri, 21 Jul 2023 08:43 GMT
  • Disposition: Resolved — $issue.fixedSpecification.name
  • Disposition Summary:

    Minor editorial changes to the XMI

    The machine-readable file for the UTP2 metamodel (utp2.xm, ptc/23-04-06) contained the following issues that prevent import/validity:

    Issue in Line 1091
    <ownedEnd xmi:type="uml:Property" xmi:id="_1CSfwPAuEeW2VZXfgcC2cA" name="referencedBy" type="_omHdQKJVEeS8gLY2208_PA" isDerived="true"association="_1CR4sPAuEeW2VZXfgcC2cA">

    Corrected to:
    <ownedEnd xmi:type="uml:Property" xmi:id="_1CSfwPAuEeW2VZXfgcC2cA" name="referencedBy" type="_omHdQKJVEeS8gLY2208_PA" isDerived="true" association="_1CR4sPAuEeW2VZXfgcC2cA">

    Issue in line 1231:
    <ownedLiteral xmi:type="uml:EnumerationLiteral" xmi:id="_MPcSIFeHEeihnpddrZbjug" name="implicitExpect"i/>

    Corrected to:
    <ownedLiteral xmi:type="uml:EnumerationLiteral" xmi:id="_MPcSIFeHEeihnpddrZbjug" name="implicitExpect"/>

    Issue in Line 1566:
    <ownedEnd xmi:type="uml:ExtensionEnd" xmi:id="KAmGUHJKEemyx_XW_ukewg" name="extension_TestTechniqueStructure" type="_90Z0HJJEemyx_XW_ukewg" aggregation="composite"association="_KAc8YHJKEemyx_XW_ukewg"/>

    Corrected to:
    <ownedEnd xmi:type="uml:ExtensionEnd" xmi:id="KAmGUHJKEemyx_XW_ukewg" name="extension_TestTechniqueStructure" type="_90Z0HJJEemyx_XW_ukewg" aggregation="composite" association="_KAc8YHJKEemyx_XW_ukewg"/>

  • Updated: Fri, 5 Jan 2024 20:12 GMT
  • Attachments:

Cannot access XMI library and TypesLibrary for UTP 2.1

  • Key: UMLTP23-2
  • Status: open   Implementation work Blocked
  • Source: Lockheed Martin ( Justin Nguyen)
  • Summary:

    Error when attempting to open UTP 2.1 Library and Types Library. The same error message is presented when opening either file

    "error on line 3 at column 80: xmlns:StandardProfile: ' http://www.omg.org/spec/UML/20161101/StandardProfile' is not a valid URI"

  • Reported: UTP2 2.1 — Tue, 15 Feb 2022 11:40 GMT
  • Updated: Fri, 8 Dec 2023 13:56 GMT

XMI files reference non-working URLs. Cannot import into tool.

  • Key: UMLTP23-1
  • Status: open   Implementation work Blocked
  • Source: JHU APL ( Trisha Radocaj)
  • Summary:

    The .xmi files for the UTP2 have links that do not work. Even when separately going to the OMG UML site and downloading the StandardProfile.xmi and the PrimitiveTypes.xmi, unable to load the utp2.xmi profile. Tool vendor (Cameo Systems Modeler)--they suggest that the problem is in the references in the profile. In the utp2.xmi import may be getting stuck on the UML.xmi "used project". It will not let me manually select the UML.xmi file as it says "NOT A USED PROJECT!" Many permutations of installation have been attempted. This is preventing effective use of the standard in its application of test to our system model.

  • Reported: UTP2 2.1 — Fri, 1 Apr 2022 14:36 GMT
  • Updated: Fri, 8 Dec 2023 13:56 GMT