Presentation on theme: "1 Getting Service Engineering Right UML 2 in a nushell Based on a paper by Birger Møller-Pedersen, Øystein Haugen, Thomas Weigert."— Presentation transcript:
1 Getting Service Engineering Right UML 2 in a nushell Based on a paper by Birger Møller-Pedersen, Øystein Haugen, Thomas Weigert.
2 Getting Service Engineering Right The Acess System Domain: a class diagram Note there are no parts i.e. instances here
3 Getting Service Engineering Right The context as a Collaboration Role Connector multiplicity Note there are no classes here, only a structure of part properties called roles!
4 Getting Service Engineering Right 4 Collaboration diagrams Service roleA:TypeA roleC:TypeC roleB:TypeB session1: Session session2: Session session3: Session roleX roleY roleX roleY roleX roleY A collaboration with three roles and three collaboration uses: may define a service structure Session roleX:TypeX roleY:TypeY A collaboration with two roles: may define a semantic connector TypeA must be compatible with (the semantic interface) TypeX Compatibility means that the role behaviours must be contained in the total behaviour of the actor – how is a semantic variation point in UML2
5 Getting Service Engineering Right 5 Behaviour can be in three places: –The collaboration itself –The roles –The context (scope) of the collaboration: Service roleA:typeA roleC:typeC roleB:typeB session1: Session session2: Session session3: Session roleXroleY roleX roleY roleX roleY sd 1 3 2 1 3 2
6 Getting Service Engineering Right The Taxi System with interfaces bound as collaboration uses This is a composite class with parts. Each part shall satisfy the roles bound to it
7 Getting Service Engineering Right Collaborations for interface definitions Reusable definitions not bound to a system
8 Getting Service Engineering Right A composite class: the AC system Part Port Connector
Your consent to our cookies if you continue to use this website.