UML 2.0 vs. SDL/MSC - Ericsson Position Statement SDL and MSC - PDF document

UML 2.0 vs. SDL/MSC - Ericsson Position Statement SDL and MSC Workshop Grenoble June 2000 Øystein Haugen, Ericsson NorARC UML 2.0 Position Statement / Slide 1 Ericsson’s approach to UML 2.0 in OMG � We want UML to become better � We want UML to become more precise � We believe SDL and MSC have a lot of advantages compared with current versions of UML � We want major ideas from SDL and MSC to find its way into UML such that a wider audience may reap their benefits � We believe in cooperation rather than going for capitulation – we do not think OMG/UML will admit the superiority of SDL/MSC – we do not think OMG/UML will take SDL/MSC all in one chunk – we do not think they even want to give much credit to SDL/MSC when they adopt ideas from them Øystein Haugen, Ericsson NorARC UML 2.0 Position Statement / Slide 2

Modelling Large and Complex Systems � For the modeling of large-scale systems and support of component based development it is important for UML to have A structuring mechanisms capable of capturing the architecture of a system in terms of – what objects it is composed of – how these are contained in c: C higher-level objects b: B – how these objects are connected, – and how potential communication is specified Øystein Haugen, Ericsson NorARC UML 2.0 Position Statement / Slide 3 Sequence Diagrams � Proposals shall provide A :Player B :Player mechanisms to refer within abracadabra : AEp : AAgt : Bagt : decomposed as PA decomposed as PB User Endpoint UA UA one interaction to other A interactions within the same getstarted (or other) collaboration. b: B Invoke c: C Request � Proposals shall define Play � Proposals shall provide for an encapsulation Request mechanism for states and state machines, mechanisms to describe the e.g., by defining an interface in terms of the SeqDiagReference Play entry or exit points of transitions, so that the internal details of a composite state can be PlayingConfirmed decomposition of a role in an defined independently of the use of it in the Playing Playing enclosing state interaction into an interaction � Proposals shall support that the same composite state can appear in more than one Proceeding state chart in order to allow reuse of of its component parts. behavior (the state may respond in the same Proceeding manner to a set of events) across a number continue of classes. Sequence Diagram Roadmaps with references and guards Øystein Haugen, Ericsson NorARC UML 2.0 Position Statement / Slide 4

Structuring States in State Diagrams state ATM state ReadAmount VerifyCard acceptCard(account) ReadAmount aborted OutOfService ReleaseCard SelectAmount abort reenter aborted otherAmout rejectTransaction abort Amount(amount) VerifyTransaction EnterAmount � Proposals shall provide for an encapsulation ok mechanism for states and state machines, e.g., by defining an interface in terms of the entry or exit points of transitions reenter Øystein Haugen, Ericsson NorARC UML 2.0 Position Statement / Slide 5