Object Oriented Analysis and Design Using The UML: Nabgha Hashmi Faculty of Computer Science University of Gujrat

Object Oriented Analysis and Design
Using the UML
Nabgha Hashmi
Faculty of Computer Science
University of Gujrat
OOAD Using the UML - Introduction to Object Orientation, v 4.2

Copyright  1998-1999 Rational Software, all rights reserved 1
Basic Concepts of Object Orientation
 Object
 Class
 Attribute
 Operation
 Interface (Polymorphism)
 Relationships

Relationships
1. Association
i. Aggregation
ii. Composition
2. Dependency
3. Generalization
4. Realization

1. Association

Relationships: Association
 Models a semantic connection among classes
Association Name
Professor Works for University
Association
Role Names
Class University
Professor
Employee Employer

Association: Multiplicity
 Unspecified
 Exactly one 1
 Zero or more (many, unlimited) 0..*
*
 One or more 1..*
 Zero or one 0..1
 Specified range 2..4
 Multiple, disjoint ranges 2, 4..6

1.1. Aggregation

Relationships: Aggregation
 A special form of association that models a whole-part

relationship between an aggregate (the whole) and its
parts
Whole Part
Student Schedule
Aggregation

1.2. Composition

Relationships: Composition
 A form of aggregation with strong
ownership and coincident lifetimes
 The parts cannot survive the whole/aggregate
Whole Part
Student Schedule
Aggregation

UML Notations

Difference......

What If You are Not Sure What Type of Relationship to Use?
 Do not get too confuse if you are unable to decide whether a particular
whole-part relationship is best described as an aggregation or
composition because the distinction is helpful, it is not critical.
 If you are not even sure whether the relationship is best

described as Composition or Aggregation, then model it as an
Association.
 In fact, there is nothing wrong with modelling all whole-part

relationships as simple Associations.
 it will make no difference to the resulting solution.

2.Dependency

Relationships: Dependency
 A relationship between two model elements
where a change in one may cause a
change in the other
 Non-structural, “using” relationship
Client Supplier Component
Class
Package Client Supplier

Dependency
relationship
ClientPackage SupplierPackage
Dependency
relationship
3. Generalization

Relationships: Generalization
 A relationship among classes where one
class shares the structure and/or behavior
of one or more classes
 Defines a hierarchy of abstractions in which
a subclass inherits from one or more
superclasses
 Single inheritance
 Multiple inheritance
 Generalization is an “is-a-kind of”
relationship

Example: Single Inheritance
 One class inherits from another
Ancestor
Account
balance
name
Superclass number
(parent) Withdraw()
CreateStatement()
Generalization
Relationship
Checking Savings
Subclasses Withdraw() GetInterest()

Withdraw()
Descendents
Example: Multiple Inheritance
 A class can inherit from several other
classes
FlyingThing Animal
multiple
inheritance
Airplane Helicopter Bird Wolf Horse
Use multiple inheritance only when needed, and

always with caution !
4. Realization

Realization
 In UML modelling, a realization relationship is a

relationship between two model elements, in which one
model element (the client) realizes (implements or
executes) the behavior that the other model element
(the supplier) specifies.
 Realizations can only be shown on class or component

diagrams.

Relationships: Realization
 One classifier serves as the contract that
the other classifier agrees to carry out
 Found between:
 Interfaces and the classifiers that realize them
Class Component
Subsystem
Interface Interface
Interface
Elided form
 Use cases and the collaborations that realize
them
Canonical form
Use Case Use-Case Realization

UML Tools

UML Tools
 Rational Rose is the “real world” standard; full round-trip code
generation
 Together (from Borland) is a lot like Rational Rose
 ArgoUML looks interesting (and is open source)
 BlueJ, displays simple UML diagrams
 Drawing programs with UML support
 Visio is a Microsoft tool
 Dia is a freeware clone of Visio

Tool Links
 Rational Rose
 http://www-3.ibm.com/software/awdtools/developer/rosexde/
 Together
 http://www.borland.com/together/

Tool Links
 ArgoUML
 http://argouml.tigris.org
 Visio
 http://msdn.microsoft.com/office/understanding/visio/
 Dia
 http://www.lysator.liu.se/~alla/dia


Object Oriented Analysis and Design Using The UML: Nabgha Hashmi Faculty of Computer Science University of Gujrat

Uploaded by

Copyright:

Available Formats

Object Oriented Analysis and Design Using The UML: Nabgha Hashmi Faculty of Computer Science University of Gujrat

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Object Oriented Analysis and Design Using The UML: Nabgha Hashmi Faculty of Computer Science University of Gujrat

Uploaded by

Copyright:

Available Formats

Object Oriented Analysis and Design

Using the UML

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

Professor Works for University

OOAD Using the UML - Introduction to Object Orientation, v 4.2

 Zero or one 0..1

 Specified range 2..4

 Multiple, disjoint ranges 2, 4..6

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

 A special form of association that models a whole-part

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

 If you are not even sure whether the relationship is best

 In fact, there is nothing wrong with modelling all whole-part

 it will make no difference to the resulting solution.

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

Package Client Supplier

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

Subclasses Withdraw() GetInterest()

Airplane Helicopter Bird Wolf Horse

Use multiple inheritance only when needed, and

OOAD Using the UML - Introduction to Object Orientation, v 4.2

 In UML modelling, a realization relationship is a

 Realizations can only be shown on class or component

OOAD Using the UML - Introduction to Object Orientation, v 4.2

Use Case Use-Case Realization

OOAD Using the UML - Introduction to Object Orientation, v 4.2

 Together (from Borland) is a lot like Rational Rose

 ArgoUML looks interesting (and is open source)

 BlueJ, displays simple UML diagrams

 Drawing programs with UML support

 Visio is a Microsoft tool

 Dia is a freeware clone of Visio

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

OOAD Using the UML - Introduction to Object Orientation, v 4.2

You might also like