Issue 7195: UML 2.0 Alignment (uml-testing-profile-rtf) Source: Fraunhofer FOKUS (Dr. Ina Schieferdecker, ina.schieferdecker(at)fokus.fraunhofer.de) Nature: Uncategorized Issue Severity: Summary: Summary: U2TP has to be aligned with the finalized UML 2.0 Resolution: Since this is an old issue, alignment with the most recent version of UML (2.3) at the beginning of the UTP 1.1 RTF is targeted. Due to the changes of previously applied resolutions, UTP is now compatible with UML 2.3. Additionally, the resolution of this issue includes the alignment of the introductory sections with UML 2.3. Revised Text: Change first sentence of third paragraph in section 1 from The UML Testing Profile is based on the UML 2.0 specification. To The UML Testing Profile is based on the UML 2.3 specification. Update Text Replace word phrases of first bullet point in section 1 from … as defined in the UML Infrastructure volume of UML 2.0. To … as defined in the UML Infrastructure 2.3. Update Text Update normative references in section 3 from • UML 2.0 Infrastructure Specification • UML 2.0 Superstructure Specification • UML 2.0 OCL Specification • MOF 2.0 Specification To • [UML] Unified Modeling Language (UML) Specification: Superstructure, version 2.3, formal/2010-05-05, 2010 • [OCL] Object Constraint Language (OCL), version 2.2, formal/2010-02-01 • [MOF] Meta Object Facility (MOF) Core Specification, version 2.0, formal/2006-01-01, 2010 Update Text Update lower part of informative references in section 3.1 from (notice section numbering was already removed by resolution of issue 15770) • JUnit: http://www.junit.org. • ETSI ES 201 873-1: The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language. V2.2.1 (2002- 10), 2002; also an ITU-T standard Z.140. • ETSI ES 201 873-3: The Testing and Test Control Notation version 3; Part 3: TTCN-3 Graphical Presentation Format (GFT). V2.2.1 (2002-10), 2002; also an ITU-T standard Z.142. • ITU-T Z.120: Message Sequence Charts (MSC), Nov. 1999 To • [JUNIT] JUnit: http://www.junit.org. • [[TTCN3p1] ES 201 873-1: The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language. V4.2.1 (2010-07), 2010. • [TTCN3p3]ETSI ES 201 873-3: The Testing and Test Control Notation version 3; Part 3: TTCN-3 Graphical Presentation Format (GFT). V3.2.1 (2007-02), 2010. • [MSC] ITU-T Z.120: Message Sequence Charts (MSC), Nov. 1999 • [SysML] OMG Systems Modeling Language (OMG SysML), Version 1.2, formal/2010-06-01, 2010. • [ISTQBg] ISTQB Standard glossary of terms used in Software Testing, Version 2.1 (dd. April 1st, 2010) • [IEEE1012] 1012-1998 - IEEE Standard for Software Verification and Validation, 1998 Replace Text Replace entire section 6.1 Acknowledgements with The following companies submitted and/or supported parts of the original specification: • Fraunhofer FOKUS • Ericsson • Motorola • University of Lόbeck • Telelogic • IBM • Softeam • iLogix • IRISA • Scapa Technologies The following persons were members of the team that designed and wrote this specification: Ina Schieferdecker, Ψystein Haugen, Paul Baker, Zhen Ru Dai, Jens Grabowski, Serge Lucio, Eric Samuelson, Clay Williams. The following companies submitted and/or supported parts of the 1.1 RTF of this specification: • Fraunhofer FOKUS • KnowGravity, Inc. • Lockheed Martin • SINTEF • sepp.med GmbH • UFR Sciences et Techniques • Softeam • THALES • IBM • NoMagic, Inc. • University of Applied Sciences Hamburg • University of Pitest The following persons were members who submitted and/or supported parts of the 1.1 RTF of this specification: Marc-Florian Wendland, Markus Schacher, Jon D. Hagar, Ina Schieferdecker, Armin Metzger, Zhen Ru Dai, Fabien Perureux, Eldad Palachi, Laurent Rioux, J.D. Baker, Alin Stefanescu, Andreas Hoffmann, Max Bureck Update Text Update the first bullet point of the second paragraph in section 6.2 from • is based upon the UML 2.0 specification, To • is based upon the UML 2.3 specification, Update Text Update the last paragraph in section 6.2 from Chapter 6 contains the terminology, the metamodel, examples, and mappings for these concepts. To Chapter 7 contains the abstract syntax and the terminology for these concepts. Annex A - Mappings defines a mapping between UTP concepts and TTCN-3 as well as JUnit. Annex B - Examples provides examples of how the UTP can be applied. (notice, chapter 6 has already been renumbered to section 7 by the resolution of issue 15770) Update Text Change the second bullet point of second paragraph of section 6.2 (notice that section 6.2 has been merged with section overview by resolution of issue 15772 and numbering was removed by resolution of issue 15770) from Defining the UML 2.0 based metamodel of UML Testing Profile. To Defining the UML 2.3 based metamodel of UML Testing Profile. Update Text Change the last paragraph of section 6.2 (notice that section 6.2 has been merged with section overview by resolution of issue 15772 and numbering was removed by resolution of issue 15770) from All sections form the definition of the UML Testing Profile. In case of ambiguities, the UML 2.0 based metamodel takes precedence. To All sections form the definition of the UML Testing Profile. In case of ambiguities, the UML 2.3 based metamodel takes precedence. Actions taken: March 30, 2004: received issue October 21, 2011: closed issue Discussion: End of Annotations:===== te: Wed, 31 Mar 2004 04:51:47 +0200 From: Ina Schieferdecker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en To: Juergen Boldt Subject: WICHTIG: U2TP issues Hallo Juergen, denkst Du bitte noch an die beiden outstanding issues bei U2TP - ohne eine Nummer wird der Vote schwierig. Kannst Du zudem noch ein Issue zwecks Alignment mit UML 2.0 aufnehmen: ------------- Titel: UML 2.0 Alignment Submitter: Fraunhofer FOKUS, Ina Schieferdecker, schieferdecker@fokus.fraunhofer.de Summary: U2TP has to be aligned with the finalized UML 2.0 ------------- Bzgl. dem Alignment: unsere Strategie waere nun, dass AB entscheiden zu lassen - aber technisch gesehen, muesste man U2TP FTF rechartern, dann on hold legen bis UML 2.0 fertig ist - also am besten noch 1 Cycle mehr als die Plannung von UML 2.0 Zudem nochmals die Frage: muss der finale FTF report und die finale Spec am Montag zu Dir geschickt werden, oder aber haben wir noch etwas mehr Zeit? Besten Dank, Ina. -- ----------------------------------------------------------------------- Ina Schieferdecker Fraunhofer FOKUS email: Schieferdecker@fokus.fraunhofer.de Kaiserin-Augusta-Allee 31 tel: ++49-30-3463-7241 D-10589 Berlin fax: ++49-30-3463-8241 -----------------------------------------------------------------------