Issue 11152: UML 2.2 scope statement (uml2-rtf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Revision Severity: Critical Summary: Current Scope section in UML 2.1.1 Infrastructure ================================================= This UML 2.1.1: Infrastructure is the first of two complementary specifications that represent a major revision to the Object Management Group's Unified Modeling Language (UML), for which the previous current version was UML v1.5. The second specification, which uses the architectural foundation provided by this specification, is the UML 2.1.1: Superstructure. The UML 2.1.1: Infrastructure defines the foundational language constructs required for UML 2.1.1. It is complemented by UML 2.1.1: Superstructure, which defines the user level constructs required for UML 2.1.1. Current Scope section in UML 2.1.1 Superstructure ================================================= This Unified Modeling Language: Superstructure is the second of two complementary specifications that represent a major revision to the Object Management Group's Unified Modeling Language (UML), for which the most current version is UML v2.0. The first specification, which serves as the architectural foundation for this specification, is the Unified Modeling Language: Infrastructure. This Unified Modeling Language: Superstructure defines the user level constructs required for UML 2. It is complemented by Unified Modeling Language: Infrastructure which defines the foundational language constructs required for UML 2. The two complementary specifications constitute a complete specification for the UML 2 modeling language. Proposed Scope section ====================== This specification defines the Unified Modeling Language (UML), revision 2. The objective of UML is to provide system architects, software engineers, and software developers with tools for analysis, design, and implementation of software-based systems as well as for modelling business and similar processes. The initial versions of UML (UML 1) originated with three leading object-oriented methods (Booch, OMT, and OOSE), and incorporated a number of best practices from modelling language design, object-oriented programming and architectural description languages. Relative to UML 1, this revision of UML has been enhanced with significantly more precise definitions of its abstract syntax rules and semantics, a more modular language structure, and a greatly improved capability for modelling large-scale systems. One of the primary goals of UML is to advance the state of the industry by enabling object visual modeling tool interoperability. However, to enable meaningful exchange of model information between tools, agreement on semantics and notation is required. UML meets the following requirements: * A formal definition of a common MOF-based metamodel that specifies the abstract syntax of the UML. The abstract syntax defines the set of UML modelling concepts, their attributes and their relationships, as well as the rules for combining these concepts to construct partial or complete UML models. * A detailed explanation of the semantics of each UML modelling concept. The semantics define, in a technology-independent manner, how the UML concepts are to be realised by computers. * A specification of the human-readable notation elements for representing the individual UML modelling concepts as well as rules for combining them into a variety of different diagram types corresponding to different aspects of modelled systems. * A detailed definition of ways in which UML tools can be made compliant with this specification. This is supported (in a separate specification) with an XML-based specification of corresponding model interchange formats (XMI) that must be realised by compliant tools. Resolution: Revised Text: Actions taken: July 12, 2007: received issue Discussion: End of Annotations:===== c: Kenneth Hussey , liaison@omg.org Subject: Fw: UML 2.2 scope statement X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 From: Branislav Selic Date: Thu, 12 Jul 2007 17:18:05 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 7.0.2HF446 | March 16, 2007) at 07/12/2007 17:18:06, Serialize complete at 07/12/2007 17:18:06 Juergen, We need an issue number for this to be handled by the upcoming URGENT ballot. Thanks, Bran Selic IBM Distinguished Engineer IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph.: (613) 591-7915 fax: (613) 599-3912 e-mail: bselic@ca.ibm.com ----- Forwarded by Branislav Selic/Ottawa/IBM on 07/12/2007 05:16 PM ----- Andrew Watson 06/26/2007 08:13 AM To Branislav Selic/Ottawa/IBM@IBMCA cc liaison@omg.org Subject UML 2.2 scope statement Bran, As you and I discussed at lunch, we'd like to help smooth the path of UML 2.2 for acceptance as an ISO PAS specification by extending the Scope statements in both the Infrastructure and Superstructure specifications. Attached below are the current scope sections from UML 2.1.1 Infra and Super (extracted from formal/07-02-05 & 06), and an initial proposal for a new ISO-friendly Scope statement, penned by Bryan Wood. If we (ISO-experienced liaison people and the UML 2.2 RTF) can agree a new proposed scope statement that meets both groups' expectations in the next couple of weeks, then we'd like to submit it as an issue for resolution before the close of the UML 2.2 RTF (which I gather will be around the end of September 2007). Thanks, Andrew Current Scope section in UML 2.1.1 Infrastructure ================================================= This UML 2.1.1: Infrastructure is the first of two complementary specifications that represent a major revision to the Object Management Group's Unified Modeling Language (UML), for which the previous current version was UML v1.5. The second specification, which uses the architectural foundation provided by this specification, is the UML 2.1.1: Superstructure. The UML 2.1.1: Infrastructure defines the foundational language constructs required for UML 2.1.1. It is complemented by UML 2.1.1: Superstructure, which defines the user level constructs required for UML 2.1.1. Current Scope section in UML 2.1.1 Superstructure ================================================= This Unified Modeling Language: Superstructure is the second of two complementary specifications that represent a major revision to the Object Management Group's Unified Modeling Language (UML), for which the most current version is UML v2.0. The first specification, which serves as the architectural foundation for this specification, is the Unified Modeling Language: Infrastructure. This Unified Modeling Language: Superstructure defines the user level constructs required for UML 2. It is complemented by Unified Modeling Language: Infrastructure which defines the foundational language constructs required for UML 2. The two complementary specifications constitute a complete specification for the UML 2 modeling language. Proposed Scope section ====================== This specification defines the Unified Modeling Language (UML), revision 2. The objective of UML is to provide system architects, software engineers, and software developers with tools for analysis, design, and implementation of software-based systems as well as for modelling business and similar processes. The initial versions of UML (UML 1) originated with three leading object-oriented methods (Booch, OMT, and OOSE), and incorporated a number of best practices from modelling language design, object-oriented programming and architectural description languages. Relative to UML 1, this revision of UML has been enhanced with significantly more precise definitions of its abstract syntax rules and semantics, a more modular language structure, and a greatly improved capability for modelling large-scale systems. One of the primary goals of UML is to advance the state of the industry by enabling object visual modeling tool interoperability. However, to enable meaningful exchange of model information between tools, agreement on semantics and notation is required. UML meets the following requirements: * A formal definition of a common MOF-based metamodel that specifies the abstract syntax of the UML. The abstract syntax defines the set of UML modelling concepts, their attributes and their relationships, as well as the rules for combining these concepts to construct partial or complete UML models. * A detailed explanation of the semantics of each UML modelling concept. The semantics define, in a technology-independent manner, how the UML concepts are to be realised by computers. * A specification of the human-readable notation elements for representing the individual UML modelling concepts as well as rules for combining them into a variety of different diagram types corresponding to different aspects of modelled systems. * A detailed definition of ways in which UML tools can be made compliant with this specification. This is supported (in a separate specification) with an XML-based specification of corresponding model interchange formats (XMI) that must be realised by compliant tools. Subject: RE: URGENT issues resolution ballot Date: Tue, 28 Aug 2007 21:05:42 +0200 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: URGENT issues resolution ballot Thread-Index: Acflq3GLXa1W2AbTTg249soiVPJ0PwDh2zPw From: "Tim Weilkiens" To: "Branislav Selic" , Cc: "Andrew Watson" X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id l7SJ8iGI016711 One minor remark: Issue 11152: New scope 2nd paragraph Isn't Jacobson's method called Objectory instead of OOSE? Tim > -----Original Message----- > From: Branislav Selic [mailto:bselic@ca.ibm.com] > Sent: Thursday, August 23, 2007 7:22 PM > To: uml2-rtf@omg.org > Cc: Andrew Watson > Subject: URGENT issues resolution ballot > > > There has not been any feedback on the draft of the URGENT > issues ballot sent out almost 4 weeks ago. I worry that this > may be because of summer vacations and that some folks simply > did not have a chance to respond. As a result, I decided > holding off the formal ballot. With summer ending, I think it > is time for us to pass this ballot as soon as possible -- I > plan to start it on Monday, Sept. 4 (yes, on Labour Day). > > For your convenience, I am resending the draft ballot. Note > that none of the fixes will result in metamodel changes, > which means that the resolutions are pretty harmless to both > vendors and users. The result will be UML 2.1.2. > > Cheers, > > Bran Selic > IBM Distinguished Engineer > > IBM Rational Software > 770 Palladium Drive > Kanata, Ontario, Canada > K2V 1C8 > ph.: (613) 591-7915 > fax: (613) 599-3912 > e-mail: bselic@ca.ibm.com > > > Subject: RE: URGENT issues resolution ballot Date: Tue, 28 Aug 2007 16:10:41 -0400 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: URGENT issues resolution ballot Thread-Index: Acflq3GLXa1W2AbTTg249soiVPJ0PwDh2zPwAB8Z1hA= From: "Frank, Karl (Mission Systems)" To: "Tim Weilkiens" , "Branislav Selic" , Cc: "Andrew Watson" X-OriginalArrivalTime: 28 Aug 2007 20:10:40.0661 (UTC) FILETIME=[819F7C50:01C7E9AF] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id l7SK905R024256 It may be a legal issue of IP. OOSE is short for the book in which he published the method, hence is probably not IP. Objectory is the name of his methodology products and his company, Objective Systems, was renamed as Objectory, prior to its acquisition by Rational. So the name Objectory may be IP now owned by IBM. Cordially yours, Karl Frank General Scientist, Mission Systems Northrop-Grumman Corporation GMT-5 (EDT, EST) cell: +1 978 853 3592 -----Original Message----- From: Tim Weilkiens [mailto:Tim.Weilkiens@oose.de] Sent: Tuesday, August 28, 2007 3:06 PM To: Branislav Selic; uml2-rtf@omg.org Cc: Andrew Watson Subject: RE: URGENT issues resolution ballot One minor remark: Issue 11152: New scope 2nd paragraph Isn't Jacobson's method called Objectory instead of OOSE? Tim > -----Original Message----- > From: Branislav Selic [mailto:bselic@ca.ibm.com] > Sent: Thursday, August 23, 2007 7:22 PM > To: uml2-rtf@omg.org > Cc: Andrew Watson > Subject: URGENT issues resolution ballot > > > There has not been any feedback on the draft of the URGENT issues > ballot sent out almost 4 weeks ago. I worry that this may be because > of summer vacations and that some folks simply did not have a chance > to respond. As a result, I decided holding off the formal ballot. With > summer ending, I think it is time for us to pass this ballot as soon > as possible -- I plan to start it on Monday, Sept. 4 (yes, on Labour > Day). > > For your convenience, I am resending the draft ballot. Note that none > of the fixes will result in metamodel changes, which means that the > resolutions are pretty harmless to both vendors and users. The result > will be UML 2.1.2. > > Cheers, > > Bran Selic > IBM Distinguished Engineer > > IBM Rational Software > 770 Palladium Drive > Kanata, Ontario, Canada > K2V 1C8 > ph.: (613) 591-7915 > fax: (613) 599-3912 > e-mail: bselic@ca.ibm.com > >