UML Design

1. UML Design Dr. Zhen Jiang West Chester University E-mail: zjiang@wcupa.edu

2. Outline • Motivation • Introduction to UML • Introduction to object and class • UML class diagram • UML design • Use of UML in DB implementation

3. Motivation • Game, to know the need for a more efficient method of the programmer, in order for him/her to know the exact design idea • You play the role as the program designer • Your partner plays the role as the programmer to obtain what you want to tell him/her via the documental work • See if you can build a very efficient communication to exchange ideas! • No talk, read and write only!

4. Motivation • Look at this picture carefully • You need to identify it from VERY similar pictures in the next slide

5. Motivation • Which one is shown before? • In the next slide, your partner will see the • selected picture and other two pictures together. Write down something to help your partner to pick up the same picture correctly in a similar test.

6. Motivation • Partner’s job

7. Motivation • Which one?

8. Introduction to UML • What’s UML

9. UML: Unified Modeling Language • The Unified Modeling Language (UML) is an industry-standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems • The UML definition was led by Grady Booch, Ivar Jacobson, and Jim Rumbaugh (all now at Rational Software)

10. UML simplifies the process of software design, making a "blueprint" for construction In Essence: a tool used through the analysis and design phases of system development for expressing the constructs and relationships of complex systems Target Usage: for building object-oriented and component-based systems

11. Goals of UML 1. Provide users with a ready-to-use, expressive visual modeling language so they can develop and exchange meaningful models 2. Provide extensibility and specialization mechanisms to extend the core concepts. 3. Be independent of particular programming languages and development processes. 4. Provide a formal basis for understanding the modeling language. 5. Encourage the growth of the Object-Oriented tools market. 6. Support higher-level development concepts such as collaborations, frameworks, patterns and components. 7. Integrate best practices.

12. Many free learning materials on the web • e.g. www.rational.com/uml • Standard of UML www.cs.wcupa.edu/~zjiang/01-09-67.pdf • Some recommended texts on UML: • The Unified Modeling Language User Guide, [G. Booch, J. Rumbaugh, I. Jacobson, 2000] • UML Explained, [Kendall Scott, 2001] • Applying UML and Patterns 2nd Ed., [Craig Larman, 2002] • UML Distilled 2nd Ed., [Martin Fowler with K. Scott, 2000] • UML and C++, [R. Lee & W. Tepfenhart, 2001]

13. UML Overview • The artifacts might include requirements, architecture, design, source code, project plans, tests, prototypes, releases • UML is a language for visualizing, specifying, constructing and documenting the artifacts of a software system • Simply, UML is a standard, forcing everyone to use a common language to exchange ideas.

14. Introduction to object and class • UML interprets system component with object and classes • What’s object • Identity • State • Behavior • Messages and methods • What’s class • Objects and Classes • Class Attributes • Operation (Method) • Interfaces • Interfaces and Implementation

15. What’s object • Conceptually, there are many ways to think of an object • something that can be seen or touched • a thing to which some action is directed • something that performs an action • The structure and behaviour of similar objects are defined in their common class • Objects have three properties: identity , state, and behaviour

16. Object Property 1: Identity • Identity is that property of an object which distinguishes it from all other objects • Most programming languages use variable names to refer to objects • Keep in mind, however, that an object may not have a name; Similarly, an object might have multiple names (aliases) • For this reason, there is a subtle distinction made between the concepts of "name" and "identity"

17. Object Property 2: State • The state of an object encompasses all of the descriptions of the object plus the current values of each of these descriptions

18. Object Property 3: Behaviour • Behaviour is how an object acts and reacts, in terms of its state changes and message passing • The state of an object represents the cumulative results of its behavior • In object-oriented programming, the behavior is invoked by an active motion, not just a passive impact.

19. Example Objects • There are many physical objects we can examine right in this room • each person is an object • any chair is not an object • each light bulb is an object • Any book is not an object • this room itself is an object (full or not)

20. See if the followings are objects or not: • Desk • Lamp • Person • Log • The Earth • Clock • Machine • Computer • Saving account • Answer: N, Y, Y, N, Y, Y, Y, Y, Y

21. What’s class • A class describes the common structure (attributes/state) and behaviour of its instances • For example, • 3.14, 2.71, and 5.5 can be classified as Floats • the following shapes can be classified as Circles

22. Classes and Objects • An object is called an "instance" of a class • The terms instance and object are interchangeable • Creating an object from a class is often called instantiation • For example, there are many person objects in this room -- each person is an instance of the person class

23. Classes and objects • How would we describe the state, behaviour, and identity for each of these objects • We have looked at objects and we have seen that objects can be "classified" into classes • As programmers, we work with both classes and objects from those classes • For example, we might write a stack class and create multiple stack objects for use in our program

24. In a 2D drawing package, circles have a radius, a line thickness, a line colour, and a fill colour • Each individual circle (instance) drawn by the user has its own value for each attribute • The programmer writes a Circle class and the program instantiates a Circle object every time the user draws a Circle a snowman made from 9 Circle instances

25. Class Attributes • An attribute is a named property of a class that describes the range of values that instances of the property may hold.(Booch,1999) • An attribute has a type that defines the type of its instances. • Only the object itself should be able to change the value of its attributes. • The values of the attributes define the state of the object

26. Review something Object action action state1 state2 operations/methods attributes: {attribute1, attribute2} structure operation/method attribute1 attribute2 value

27. Light Turn on/off On Off operations/methods: Turn_on/off ( ) attributes: {True, False} structure Turn_on True False Turn_off value

28. Class Diagram • Introduction • Class Icon • Relationships • Constraints

29. Introduction • The class diagram is fundamental to object-oriented programming • UML’s class diagrams capture the attributes and operations of each class as well the relationship that exist between classes • ! This (class) relation defines the OWNERSHIP between the data field/attribute of the object of one class and the one of the relevant object (in type of the class on the other side of this relation)

30. Class Icon • Class Icon • Hiding Details • Visibility Notation • Attribute Specification • Operation Specification

31. Class Icon • The UML class icon is a rectangle with three compartments: • class name • class attributes • class operations • Attributes are specified in the following form: • object:class name

32. Hiding Detail • You can optionally leave out the attributes, operations, or both in a class icon:

33. UML Member Visibility Notation • UML has three visibility prefixes for members:+ for public, # for protected, and – for private • e.g.

34. Full UML Attribute Specification • The full form of a UML attribute is as follows:[visibility] name [multiplicity] [: type] [= initial value] [{property}] • The property choices are changeable, addOnly, and frozen

35. Full UML Operation Specification • The full form of a UML operation is as follows:[visibility] name [(parameter-list)] [:return-type] [{property}] • The property choices are sequential, concurrent, guarded, and isQuery • The full form of a UML parameter is:[direction] name : type [= default-value] • The direction choices are in, out, and inout

36. UML Class Relationships • A class relationship is a connection between two (or more) classes • The three most important class relationships are generalizations, associations, and aggregations • UML provides a graphical representation for each of the relationships using a different line type for each relationship

37. Class Relationships • Generalization • Association • Association Class • Qualified Association • Ternary Association • Aggregation

38. Generalization • A generalization is a relationship between a general thing (superclass) and a more specific kind of that thing (subclass) • In the UML, generalization requires that objects of the subclass may be used anywhere an object of the superclass appears

39. Association • An association is a structural relationship that specifies that objects of one thing are connected to objects of another

40. Association • Associations can be adorned with a name. Teaching

41. Association • Associations can be adorned with the roles. teacher learner

42. Association • Associations can be adorned with the multiplicity. 1 4..*

43. Association Class (relation attributes) • Each object of association class is one instance of relationship (link) in an association. 1..* 4..*

44. Qualified Association • Qualified association relates two classes and a qualifier. • The qualifier is a special attribute that reduces the effective multiplicity of an association.

45. Ternary Association • A ternary association is a structural relationship that specifies that objects of one thing are connected to objects of other two’s.

46. Aggregation • An aggregation is an association that represents whole/part relationship • The “whole” end of the association relationship is adorned with an open diamond shape (e.g. X is part of Y) • e.g. door:Door is part of car:Car X Y

47. Generalization, Aggregation, and Association • See if the following pairs of classes have generalization, aggregation or association • Faculty & student (as) • Hospital & doctor (as) • Door & Car (ag --<>) • Member & Organization (ag --<>) • People & student (ge <|-- ) • Circle & point (ge --|>) • Department & Faculty (as) • Employee & Faculty (ge <|--) • Item & Printer (ge <|--) • Account & Checking account (ge <|-- )

48. Constraints • Constraints on Object • Constraints on Relations (Ordering) • General Constraints (Dependency)

49. Constraints on Object • The constraints restricts the values that objects can be. • Example: No employee’s salary can exceed the salary of the employee’s boss. {salary <=boss.salary}

50. Constraints on Relations (Ordering) • {Order} indicates that the elements of the “many” end of an association have an explicit order that must be preserved. {ordered} 1 1..*