What's New in UML 2.0

Transcription

1 What's New in UML 2.0 M.W.Richardson Lead Applications Engineer I-Logix UK

2 What is UML? Unified Modeling Language Comprehensive full life-cycle 3 rd Generation modeling language Standardized in 1997 by the OMG Created by a consortium of 12 companies from various domains I-Logix a key contributor to behavioral modeling Incorporates state of the art Software and Systems A&D concepts Matches the growing complexity of real-time systems Large scale systems, Networking, Web enabling, Data management Extensible and configurable Unprecedented inter-disciplinary market penetration UML 2.0 is latest version in the process of being released

3 Advent of the UML UML Dr David Harel adds Statecharts Ivar Jacobson (Objectory) join them and add OOSE UML 0.9 & 0.91 Released OMG Issues RFP RFP Response for UML 1.0 UML 1.1 UML 1.3 Grady Booch and Jim Rumbaugh begin unifying Booch & OMT UML 1.4 Methods begin to merge No Of Identifiable OO Modelling Languages Increases from <10 to >50 UML 2.0 Identifiable OO modelling languages began to appear Method Wars Begin! Mid 70s Late 80s OOSE = Object Oriented Software Engineering Method OMT = Object Modelling Technique

4 Infrastructure UML 2.0 Submissions Simplify and rework the hairy underbelly of the UML Align with MOF Superstructure Contains most user-visible features Improve scalability and architectural support Improve ability to model business workflows Add semantics of state machine inheritance OCL Object Constraint Language is used in the definition of the UML itself General improvements of the OCL Diagram Interchange Add ability to interchange diagram to the existing XMI

5 Structure Object Deployment Component UML 2.0 Package Structural Class Interaction Behavioral Activity State Machine Use Case Timing Communication Interaction Sequence

6 Ports & Structured Classes

7 How can we model the following in UML?

8 PC System with UML 1.5

9 Improved Design with UML 1.5

10 Internal View of PC Problem: Not obvious that the instance of Motherboard created by the PC is connected to the instances of USBCard and GraphicsCard created by the PC.

11 PC System Problem: No way to cleanly specify which instance of pc is connected to which instance of Keyboard

12 UML 2.0 Ports Ports are named connection points Ports allow a part to provide an interface across the boundary of its enclosing structured class without revealing to the client of the service the internal structure of the structured class Client talks to the port without internal knowledge Ports are typed by their interfaces Provided interfaces Required interfaces These interfaces can consist of synchronous and / or asynchronous operations

13 UML 2.0 Ports Port Provided Contract Required Contract

14 Devices

15 PC System : Plug & Play Part Structured Class Connector

16 PC Internals Relay Port Note here that the PC actually does nothing, all the external ports are connected to internal parts. Behavioral Port

17 Things to Remember about Ports Ports are optional! There is NOTHING you can do with ports that you can t do without them Ports enforce encapsulation of internal parts Parts can publish services across the boundary of their owning composite classes without revealing the to the client of the service which part offers it Parts are typed by interfaces Compatible ports are conjugates one offers, the other requires the same or compatible interface Sub-classed provided interfaces are compatible with super-class required interfaces Ports are a design pattern All design patterns have pros and cons Con: Ports are instantiable and so take up some amount of memory and require some amount of execution time Ports are implemented by classes that provide behavioral delegation services to their clients Ports can have multiplicity and can be connected dynamically

18 Ports Example

19 Easy testing

20 White Box View

21 Sequence

22 Horizontal Decomposition Messaging between structured classes Interaction Occurrence

23 Vertical Decomposition Messaging between structured classes Part Decomposition

24 Interaction Fragment Operators sd named sequence diagram ref reference to interaction fragment loop repeat interaction fragment opt optional exemplar alt selection par concurrent (parallel) regions seq partial ordering (default) (aka weak ) strict strict ordering criticalregion identifies atomic fragments assert required (i.e. causal) neg can t happen or a negative specification Ignore/consider messages outside/inside causal stream Naming Flow of Control Ordering Causality

25 Interaction Operator : Loop

26 Interaction Operator : Opt

27 Interaction Operators : Critical Region

28 Inherited State Behaviour

29 Inherited State Behavior Assumes Liskov substitution principle for generalization: A subclass must be freely substitutable for the super-class in any operation You can Add new states Elaborate sub-states in inherited states Add new transitions and actions You cannot Delete inherited transitions or states

30 Example: Generalization Modified action list New sub-states and transitions New and-states

31 Activity

32 Activity graspat interruptable section interrupting edge Emergency Stop Proximity Alert Interrupting edge Position Compute joint angles (a,b) event reception Event reception or exception Input pin Joint 1 to a Joint 2 to b Open manipulator Rotate manipulator Joint_1 Joint_2 Joint_3 Interruptible region swim lane representing the objects executing the activities nested within Grasp Object

33 Timing

34 Timing Diagram Transceiver Coil Driver Idle Receiving Sending Receiving::High Receving::Low Sending::High Sending::Low Tristate Monitor Initializing Acquiring Reporting Idle send(value) send(value) transmit(value) {1 ms +/- 0.2ms} {3 ms +/- 0.2ms} tm(bittime) Time evdone A Timing Diagram shows the timing between objects.

35 UML 2.0 Summary Makes it easier to construct scaleable architectures Makes exchange of models between tools possible Facilitates use of UML by Systems Engineers