UML Modeling I. Instructor: Yongjie Zheng September 3, CS 490MT/5555 Software Methods and Tools

Transcription

1 UML Modeling I Instructor: Yongjie Zheng September 3, 2015 CS 490MT/5555 Software Methods and Tools

2 Object-Oriented Design: Topics & Skills Rational Unified Process Unified Modeling Languages (UML) Provide a range of notations that can be used to document an object-oriented design. Structure Behavior Requirements Use Case Diagrams Design Design Patterns Class Diagrams Package Diagrams Sequence Diagrams State Diagrams Activity Diagrams Reuse solutions, rather than solve every problem from first principles. 2

3 The History of UML Developed by the following three people at the Rational Software Corporation in 1996 (UML 0.x). Grady Booch (the Booch method) Ivar Jacobson (the OOSE method) James Rumbaugh (the OMT method) The Object Management Group (OMG) started the process of UML standardization in 1997 (UML 1.x). The current version is UML 2.4.x. 3

4 UML Diagrams 4

5 UML Metamodel Metamodel A model that is written in a language (called metalanguage) to define some specific modeling language. For example: UML is defined by its metamodel, which is written in MOF. Meta level Reflects the linguistic instance-of relationship between a model and its metamodel. In other words, a model is written in a language that is defined by the model s metamodel at a higher meta level. 5

6 UML Metamodel Layer Description Instance M3: metametamodel M2: metamodel M1: model Define the language for specifying metamodels. An instance of a metametamodel, defining the language for specifying models. An instance of a metamodel, modeling a specific information domain. M0: systems An instance of a model 6 Meta-Object Framework (MOF). UML, CWM, XMI. UML model, data model. Modeled systems

7 7 Overview of Layers M0 to M3. - [MDA Explained, Addison-Wesley, 2003]

8 UML Class Diagram Definition: a class diagram describes the types of objects in the system and the various kinds of static relationships that exist among them. Essential elements Classes Attributes Operations Associations Generalization Aggregation Composition 8

9 An Example of UML Class Diagram 9

10 Classes Identity Attributes Class attributes operations() visibility name: type multiplicity = default {propertystring} Operations visibility name (parameter-list) : return-type {property-string} parameter-list: direction name: type = default 10

11 Attribute Syntax visibility name: type multiplicity = default {property-string} optional visibility: + public, - private, # protected name: the name of this attribute optional type: data type of this attribute optional multiplicity: optional [0..1], mandatory [1]. optional default: initial value of attribute optional property string: OCL, e.g. ordered, readonly Examples firstname, -lastname: String -age: int {>=0} - name: String [1] = "Untitled" {readonly} 11

12 Property String Any information that cannot be expressed in the diagram notation can be included as text. Most of them are constraints. Can be Informal English Object Constraint Language The only rule Put them inside braces ({}) 12

13 Operation Syntax visibility name (parameter-list) : return-type {property-string} optional visibility: + public, - private, # protected name: the name of this operation optional parameters-list, parameters to this operation (separated by a comma): direction name: type = default optional direction: in, out, inout name optional type optional default optional type: return type of operation optional property string 13

14 Operation Syntax Examples getfirstname() {query} +getmiddlename(): String -setlastname(name: String) {sequential} +paintportrait(inout c: Canvas, subject: Person) 14

15 Associations Relationships between instances of classes E.g. a person works for a company; a company has a number of offices. Roles Name labeled on an association end. If no label, an association end can be named after the target class. Multiplicities Indicates how many objects may participate in the given relationship. 0, 1, *, 0..1, 1..*, 5..6, and so on. Would be realized through Arrays, Sets, Lists, and so on. Navigability Bidirectional: each class references the other. Unidirectional: A knows B, but B doesn t know A. No arrow heads: means either bidirectional or not specified. 15

16 Associations Associations are another way of representing attributes. 16

17 Question When to use attributes versus association lines? Data type refers to objects for which unique identity is not important. Common data types are primitive-oriented types, such as Boolean, Date, Number, Character, String, Time, Address, Color, Phone Number, Social Security Number, Zip code. Use the attribute for data type objects and the association line notation for others. Both are semantically equal, but showing an association line to another class box in the diagram gives visual emphasis. 17

18 Variations of Associations Generalization Inheritance relationship between instances of two classes. Correspond to the Java keyword "extends" (is-a). Aggregation Special associations that represent part-whole relationships (part-of) - parts can join the whole and later leave; one part could be part of more than one whole. Composition A strong kind of aggregation (has-a) - parts are created with the whole and stay with exactly one whole until both are destroyed together. 18

19 Generalization Generalization corresponds to "extends Generalizations are drawn with a solid line and a white triangular arrow touching the superclass. It is common practice to arrange the diagram so that: Generalization arrows point upward. If one class has many subclasses, the Generalization arrows overlap. 19

20 Aggregation Aggregations are special associations that represent part-whole relationships. The whole side is often called the assembly or the aggregate. This symbol is a shorthand notation association named ispartof. 20

21 Composition A composition is a strong kind of aggregation. If the aggregate is destroyed, then the parts are destroyed as well. 21

22 Some Mnemonics Generalization = is-a Aggregation = part-of Composition = has-a Examples Toaster is-a Appliance Member part-of club Toaster has-a slot 22

23 Advanced Concepts of Class Diagrams Stereotypes and profiles The core extension mechanism of the UML Stereotypes are usually shown in text between guillemots (<<>>) A profile is defined by a set of steotypes, a set of related constraints (in OCL), and a set of tagged valued. Object Diagram (Instance Diagram) A snapshot of the objects in a system at a point in time The names are underlined. Each name takes the form: instance name : class name. Interfaces and Abstract Classes 23

24 Example: Class to Object Diagrams 24

25 Interfaces and Abstract Classes Question: what is different between abstract classes and interfaces in an object-oriented programming language (e.g. Java)? 25

26 Interfaces and Abstract Classes UML Interface A class that has only public operations with no method bodies or attributes. Representation Italicize the name of interfaces or abstract classes. Use the {abstract} constraint for abstract classes (optional) and the <<interface>> stereotype for interfaces. Realization Relationship between an implementation class and an interface. Drawn with a dashed line and a white triangular arrow touching the interface. 26

27 Example 27

28 To summarize 28

29 Package Diagrams Package is a grouping construct. Most commonly used for class diagrams, but can be used with any UML diagram or elements. Used to create a hierarchy or higher level of abstraction. Corresponds to package in Java. Each package represents a namespace. Like Java, can have classes with same name in different packages. 29

30 Representing Packages 30

31 References Software Engineering van Vliet, Hans. Software Engineering: Principles and Practice. 2nd edition. Addison-Wesley, UML Modeling Craig Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3rd Edition. Prentice Hall, ISBN-10: Fowler, M UML Distilled: a Brief Guide to the Standard Object Modeling Language. 3. Addison-Wesley Longman Publishing Co., Inc. 31

32 Reminder Lab #2 is on next Tuesday. Assignment #2 will be out after the lab. Assignment #1 is due next Monday midnight. 32