Class & Object Diagrams

Software Design Methodology

UML Class Diagrams

The heart of the UML Describes the classes in the system and the relations among them Supports most OO concepts

associations aggregation inheritance

(including multiple)

Classes

Classes are denoted by rectangles. Attributes Operations Responsibilities Class

attribute: type operation operation(parameters) responsibility
3

Classes
Attribute: A named property of a class that describes a range of values that instances of the property may hold. Operation: Implementation of a service that can be requested. Responsibility: A contract or an obligation of a class. As the model is refined the responsibilities are transformed into attributes and operations.

4

Object
Object - a concept, an abstraction, a thing meaningful to the domain
Joe Smith Lassie flight #713 the top window Person Dog Flight Window

Object Class - a collection of all objects having the same set of features. Each object has a unique identity and is an instance of its object class.
5

Class Diagrams vs. Object Diagrams

p:Person Person name employeeID title name=Yahoo employeeID=1212 title=VP of production

Joe Smith:Person

Relationships
A relationship is a connection among things. Common relationships: Dependencies, Associations, Generalization and Aggregations.

Dependency

A dependency states that a change in specification of one thing may effect another thing that uses it
A class takes an object of another class as a parameter
Course

CourseSchedule add(c:Course) remove(c:course) Window open() close() Student grade

A class accesses an object of another class

Event

A class calls a class operation in another class

Dean
8

CalculateAverage(grade)

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

Country
Name: string Population: integer Area: Km2 Has-capital

City
Name: string Population: integer

Association Name
Printed

at the center of the line Describes the nature of the relationship (usually a verb) A direction triangle can be added

10

Association Multiplicity
Used when it is important to state how many objects may be connected across an instance of an association. When a number is stated at an end of an association it is specified that for each object at the class at the opposite end there must be that many objects at the near end. An * denotes many - which can be any number between zero and infinity.

11

Multiplicity Example
1..* Employee 1..10 0..1 Office At least one employee in a department An employee belongs to exactly one department An employee has zero or one office An office is assigned to a number of one up to 10 employees 1 Department

12

Multiplicity symbols (participation constraints)

Line
Name: string

0,2..*

Intersects

Point

Is Endpoint Of 2 Name: string X-Coordinate: integer Y-Coordinate: integer

13

Association Classes
Denoted as a class attached to the association Specify properties of the association Does not belong to any of the connected class
Car * Reg. Num. Model Year Owner of Year Purchased 1.. * Person Name
14

Association Attributes
Person
Name: string ID: string Address: string

1..* Works-for
salary: float job: string

Company
*
Name: string Address: string

Student
Name ID Faculty

140 submit

Assignment
4
Number Subject Submission date
15

Grade

Association Role Names

Names may be added at each end of the association Provide better understanding of the association meaning Especially helpful in self-associated classes

Worker

*..1 Person 1..0

Manager employee

*
employer

Company

Manages

16

Role Names, Constraints and Qualifiers Role 1 owner

* 0..1 authorized user User * * Directory container * contents 1

Ordering
Window
* {ordered}
visible-on

Screen

Qualifier:
an attribute that reduces the associations multiplicity. Directory file name *
0..1

File
17

Classes versus Objects

Class Diagram Classes name attributes operations responsibility Association name multiplicity role Association Classes Object Diagram Objects values for attributes

Link

Link Object
18

Class Diagram Example

Reader
Name ID Address

0..1 holds
Return date

* Code

Copy

* {ordered}
reserved

Shelf location Status Loan duration

* *

Book
Code Name Edition Author

of

19

Object Diagram Example

357:Reader
Name=Joe ID=357 Address=Jerusalem

holds
Return date=16.11.00

57168-1:Copy
Code=57168-1 Shelf location=681.3.06 Status=at loan Loan duration=2 weeks

482:Reader
Name:Michel ID=482 Address=Haifa

holds
Return date=24.11.00

57168-2:Copy
Code=57168-2 Shelf location=681.3.06 Status=at loan Loan duration=1 month

936:Reader
Name=David ID=936 Address=Haifa

UML:Book
Code=57168 Name=The Unified Modeling Language User Guide Edition=1 Author=Booch, Rumbaugh, Jacobson

of of
20

reserved

Aggregation
whole-part relationship between classes Assemble a class from other classes

Combined with many - assemble a class from a couple of instances of that class

May be replaced by associations...

Document text font pages * Paragraph * Picture
21

* Sentence

Aggregation (whole-part; part-of; and)

Microcomputer aggregate; whole
constituents; parts 0..* 1 System box 0..1 1

Monitor

Mouse

Keyboard

1 CPU

0..1

RAM

Fan

Chassis
22

Constraint
A functional relationship between entities (objects, classes, attributes, links, associations) of an object model.
Employee
salary

0..1 boss

Window
length width

* {salary < boss.salary} Company * Office *

{0.8 length/width1.5} {ordered} * * * Committee

23

Person

Member-of

Person

{subset}
Chair-of

Constraint (Cont.)
Portfolio {secured} BankAccount {xor} 0..1 wife Person gender:{female, male} {self.wife.gender=female and self.husband.gender=male} 0..1 husband
24

Corporation

{secured}=Across the association communicated is encrypted.

Inheritance (Generalization)
Denoted by a triangle - connects one superclass to many subclasses Multiple inheritance is allowed

a

subclass may be connected to more than one superclass not recommended - hard to understand, hard to implement

Four applicable standard constraints:

Complete Incomplete disjoint overlapping
25

Generalization (gen-spec; kind-of; or)

Figure color center position pen type Move Rotate Display 0 Dimensional subclasses Line Endpoints Display

superclass

1 Dimensional Orientation Scale

2 Dimensional Orientation fill type fill Scale Spline Control pts Display Polygon Endpoints Display Circle Diameter Display
26

Arc Radius Angle Display

Multiple Inheritance
InterestBearingItem InsurableItem Asset

BankAccount

RealEstate

Security

CheckingAccount

SavingAccount

Stock

Bond
27

Abstract Class - a class that has no direct instances

subclass

1..*

Class

1..*
has subclasses

has subclasses

Instance

has direct instances

Concrete Class

Abstract Class

1..*
superclass

superclass

1..*

Non-leaf Class

Leaf Class

28

Recursive Aggregation

Program
1..* 2..*

Block

Compound statement

Simple statement
29

Recursive Terms (Multiple Binary term use)

Second Operand First Operand

1 1

Term

Expression Binary Operator * *

Variable Name

Constant Value

30

(x+y/2)/(x/3+y)
di1:Expression Binary op=/
1st 2nd

pl1:Expression Binary op=+

1st 2nd

pl2:Expression Binary op=+ di3:Expression Binary op=/

1st 2nd

di2:Expression Binary op=/

1st 1st

x:Variable Name=x
2nd 2nd

y:Variable Name=y three:Constant Value=3 two:Constant Value=2

31

Recursive Terms (Unary &Binary & Single Term Use)

Second Operand First Operand

1 1

Term

Expression

Variable Name

Constant Value

Binary

Unary

32

Abstract Operations
The origin class defines Employee the protocol: semantics; year-to-date earnings attribute types; compute pay {abstract} number and type of arguments for methods

Hourly Employee hourly rate overtime rate compute pay

Salaried Employee weekly rate compute pay

Exempt Employee monthly rate compute pay

33

Generalization as Extension and Restriction

Extension: addition of new features. (e.g. Person vs. Student) Restriction: constraining ancestor attributes. (e.g. nullifying some attributes)

34

Overriding Operations

Tension between use of inheritance for abstraction vs. implementation reuse. Reasons for overriding:
Extension

(e.g. Person has Report_Marriage; Employee has Report_Marriage that extends the code of Report_Marriage) Restriction (e.g. Subclass operation use some of superclass sub-operations)

35

Reasons for overriding (cont.)

Optimization

e.g. IntegerSet has findMax; SortedIntegerSet has another implementation for findMax. Convenience Look for a similar class and use it as superclass. This is ad hoc use which is semantically wrong. Better: define a third common class, from which both will inherit.

Rule for method overriding: All methods that implement an operation must have the same protocol.
36