UML Diagrams & And Some Of Their Elements

Transcription

1 UML Diagrams 2013, J.P.N., page 1 UML Diagrams & And Some Of Their Elements

2 UML Diagrams 2013, J.P.N., page 2 Building blocks of the UML As part of a model you have: modelling elements relationships between the modeling elements diagrams that group and visualize the modeling elements and the relations between them. E.g. class diagram: Company 1 1..* LocatedAt 1..* Department Office * *

3 UML Diagrams 2013, J.P.N., page 3 Comment You can add comments on all type of diagrams, attaching them to all kinds of elements. Semantically insignificant.

4 UML Diagrams 2013, J.P.N., page 4 UML 2.0 The taxonomy of diagrams Structure diagrams show the static structure of the objects in a system. That is, they depict those elements in a specification that are irrespective of time... example, a structure diagram for an airline reservation system may include classifiers that represent tickets. Diagram Structure Diagram Behaviour Diagram Behavior diagrams show the dynamic behavior of the objects in a system, including their methods, collaborations, activities and state histories. The dynamic behavior of a system can be described as a series of changes to the system over time... the boundaries between the various kinds of diagram types are not strictly enforced.

5 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

6 UML Diagrams 2013, J.P.N., page 6 Grouping Elements You can group elements with the help of packages and by this organize your classes, diagrams, etc. java applet +Applet

7 UML Diagrams 2013, J.P.N., page 7 Dependency: A relationship between two modeling elements indicates that a change in the destination may effect the source. Example dependency between classes: Company is dependent on Employee Company add(e : Employee) Employee The operation add has an employee object as argument: A change in Employee may inflict a change of the add operation.

8 UML Diagrams 2013, J.P.N., page 8 Dependency on Package Diagram From MagicDraw

9 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

10 UML Diagrams 2013, J.P.N., page 10 Stereotype From Wikipedia Allow designers to extend the vocabulary of UML in order to create new model elements, derived from existing ones, but that have specific properties that are suitable for a particular problem domain or otherwise specialized usage.

11 UML Diagrams 2013, J.P.N., page 11 Some Extensibility Mechanisms stereotype «container» EventQueue {version 2.1} add(e:event) remove(n:int) «query» length():int «helper function» reorder() tagged value {add runs in O(1) time} constraint (not expressed in OCL)

12 UML Diagrams 2013, J.P.N., page 12 Class: Describes a Set of Objects class name visibility operation signature Point - x : int - y : int + getx() : int + setx(ax : int) : void + gety() : int + sety(ay : int) : void attributes compartment operations compartment Modelling tool: Rational Rose 2000 Additional compartments may be supplied, e.g., a constraints compartment.

13 UML Diagrams 2013, J.P.N., page 13 Attribute (Implemented as Field in Java, data member in C++) [5] An attribute is the description of a named slot of a specified type in a class; each object of the class separately holds a value of the type. <<stereotype>> opt / opt visibility opt name multiplicity opt : type opt E.g. <<unique>> Used if the value of the attribute can be derived from other information. - (private) only the class can see this attribute # (protected) only the class and all of its subclasses + (public) all classes that can see the class can also see the attribute ~ (package) only classes in the package can see the attribute

14 UML Diagrams 2013, J.P.N., page 14 Attribute continues Example: Tagged value e.g. Author = Kari name multiplicity opt : type opt = initial-value opt {property-string} opt Example: [1..*] : String Indicating one or more addresses. (If no is present you will still have the empty string ( ).) If [0..*] : String is specified, then can be null.

15 UML Diagrams 2013, J.P.N., page 15 Operation (Implemented as method in Java, as member function in C++) [5]: An operation is a specification of a transformation or query that an object may be called to execute. A method is a procedure that implements an operation. It has an algorithm or procedure description. <<stereotype>> opt visibility opt name(parameter-list) : return-type opt Examples: + <<query>> getx() : double + setx(newx : double)

16 UML Diagrams 2013, J.P.N., page 16 Encapsulation (Information Hiding) Hiding design decisions in a computer program that are most likely to change. Point - x : int - y : int + getx() : int + setx(ax : int) : void + gety() : int + sety(ay : int) : void E.g.: Store data in slots or Calculate them or Retrieve them from a database? Wanted effect: Protection of other parts of the program from extensive modification if the design decision is changed. Realized by having the attributes private/protected and supplying public operations to access the hidden data.

17 Static Features (i.e., attributes and operations) UML Diagrams 2013, J.P.N., page 17 Features are usually defined for instances of the class (e.g., an attribute gives a slot for each instance of the class). Static or class scoped features are also possible: o The class is then like an object with these features. o No object of the class is needed to use. Static features are underline in UML. [8]

18 UML Diagrams 2013, J.P.N., page 18 Association A relationship that describes a set of links between classes of objects, indicating some sort of connection between objects of the involved classes. Example: student follows a course. In UML class diagrams you can distinguish between ordinary association, simple aggregation and composition (strong aggregation).

19 UML Diagrams 2013, J.P.N., page 19 Ordinary Association: This relationship indicate that there is a connection from one type of objects to another type. From the UML 2.1 specification - semantic description of association : An association declares that there can be links between instances of the associated types. A link is a tuple with one value for each end of the association, where each value is an instance of the type of the end. composition or strong aggregation Company 1 association name multiplicity 1..* LocatedAt 1..* Department Office * * ordinary association

20 Ordinary Assocaition With Navigability: If you have a Quiz-object, the associated Questionobjects can be directly reach from the Quiz-object. I.e., there will be a reference to each Question-object inside the Quiz-object but not the other way around. base class Quiz direction of navigation * 1..* association with navigation Question class Quiz{ // A list of questions Question [] questions;... } One possible mapping to Java class Question { // no reference to Quiz... } UML Diagrams 2013, J.P.N., page 20

21 UML Diagrams 2013, J.P.N., page 21 Navigability And Use Of Rolename E.g. implementation in Java: editansweralternative() may contain the following code: rightanswer.settxt( Some smart answer ) Question editansweralternative() Role name rightanswer 1 1 AnswerAlternative txt : String settxt(txt : String)

22 UML Diagrams 2013, J.P.N., page 22 A Class Diagram - Mapping to Java Person #name : String #imail : String #homepage : String 1 responsible for * 1 tech. responsible for * Course -name : String -description : String 1 Student 1 * * StudentCourseProfile -finished : boolean public class Person { protected String name; protected String imail; protected String homepage; // // Navigation protected Course[] responsiblefor; protected Course[] techresponsiblefor; } public class Student extends Person { // // Navigation public StudentCourseProfile[] studentcourseprofile; }

23 UML Diagrams 2013, J.P.N., page 23 Generalization: A relationship between a more general element and a more specific one. For example: A bird is also an animal. (Generalization is not an association, but it do relate objects in regard to classification.) A bird is a specialization of an animal. It inherits the structure and behaviour of Animal. Animal Bird Eagle Generalization is a transitive relation!

24 Realization: UML: A semantic relationships between classifiers, in which one classifier specifies a contract that another classifier guarantees to carry out. The class Snake realises (implements) the interface Movable. <<interface>> Movable move(x,y) Snake Snake inherits the behaviour specified by the operations of Movable (as an interface Movable has no internal structure). move(x,y) UML Diagrams 2013, J.P.N., page 24

25 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

26 Object Diagram - Capture Instances and Links Class Company noofemploees : int Possible object Object HiA: Company noofemploees=600 name slot with value object class UML Diagrams 2013, J.P.N., page 26

27 Object Diagram with Links Class Diagram Object Diagram Company Language: Department :LocatedAt Gimlemoen: Office 1 1..* Department * LocatedAt 1..* Office Possible object diagram HiA: Company Engineering : Department :LocatedAt Grooseveien: Office Link - A link is an instance of an association, analogous to an object being an instance of a class. UML Diagrams 2013, J.P.N., page 27

28 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

29 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. State Machine D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

30 Activity diagram - Capture Dynamic Behaviour (Activity-oriented) [2] UML Diagrams 2013, J.P.N., page 30

31 Activity Diagram With Swim Lanes UML Diagrams 2013, J.P.N., page 31

32 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D. page 32

33 UML Diagrams 2013, J.P.N., page 33 Interaction User: :Oven-control -unit :Oven-light SetTemperature(250C) heaton() lighton() Interaction: A behaviour that comprises a set of messages sent between a set of objects to archive a special purpose, like in a sequence diagram.

34 Synchronous & Asynchronous Message Communication Asynchronous flow of control: the sender continue its execution as soon as the message has been sent Synchronous flow of control: the sender is blocked until it receives a reply (e.g., procedural call in C, ). UML Diagrams 2013, J.P.N., page 34

35 page 35 object message Sequence Diagram Example: activation bar life line

36 [2] Sequence Diagram with Asynchronous Flow of Control sequence diagram (sd) asynchronous communication is when the sender does not wait for the reply of the message sent UML Diagrams 2013, J.P.N., page 36

37 [2] One More Sequence Diagram with Conditional Fragment UML Diagrams 2013, J.P.N., page 37

38 Diagram Structure D. Behaviour D. Package D. Class D. Object D. Composite Structure D. Component D. Deployment D. Activity D. Use Case D. StateChart D. Interaction D. Sequence D. Communication D. Interaction Overview D. Timing D.

39 UML Diagrams 2013, J.P.N., page 39 Communication diagram Focus is on objects, links and flow of messages! 1: Button( ) 3: addactionlistener(onelistener) : MyApplication okbutton : Button 2: MyListener( ) 4: "Push OK button" 5: actionperformed(actionevent) onelistener : MyListener Ola : A User

40 [5] Communication Diagram Example UML Diagrams 2013, J.P.N., page 40

41 UML Diagrams 2012, J.P.N., page 41 References [1] Grady Booch, James Rumbaugh and Ivar Jacobson: The Unified Modeling Language User Guide. Addison-Wesley, 1999 [2] James Rumbaugh, Ivar Jacobson and Grady Booch: The Unified Modeling Language Reference Manual Second Edition. Addison-Wesley, 2005 [3] [4] [5] Ref: [6] [7] Accessed 7th September 2011: [8] Accessed 7th September 2011: [9] Accessed 12 th September 2013: