ch11 Intro To OO & Modeling Concept

Object Oriented Analysis and Design
Using the UML

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

Copyright  1998-1999 Rational Software, all rights reserved 1
Objectives: Introduction to Object Orientation
Understand the basic principles of object
orientation
Understand the basic concepts and terms
of object orientation and the associated
UML notation
Appreciate the strengths of object
orientation
Understand some basic UML modeling
mechanisms

Introduction to Object Orientation Topics
Basic Principles of Object Orientation
Basic Concepts of Object Orientation
Strengths of Object Orientation
General UML Modeling Mechanisms

Object Orientation
Encapsulation
Abstraction
Modularity
Hierarchy
What is Abstraction?
Salesperson
Not saying
Which
salesperson
– just a
salesperson
in general!!!
Product
Customer
Manages Complexity
What is Encapsulation?
Hide implementation from clients
Clients depend on interface
How does an object encapsulate?

What does it encapsulate?
Improves Resiliency
What is Modularity?
The breaking up of something complex into
manageable pieces
Order
Entry
Order Processing
System Order
Fulfillment
Billing
Manages Complexity
What is Hierarchy?
Levels of abstraction Asset
Increasing
abstraction
BankAccount Security RealEstate
Savings Checking Stock Bond
Decreasing Elements at the same level of the hierarchy

abstraction should be at the same level of abstraction

Object
Class
Attribute
Operation
Interface (Polymorphism)
Component
Package
Subsystem
Relationships

Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is an Object?
Informally, an object represents an entity,
either physical, conceptual, or software
Physical entity
Truck
Conceptual entity
Chemical Process
Software entity Linked List

A More Formal Definition
An object is a concept, abstraction, or thing
with sharp boundaries and meaning for an
application
An object is something that has:
State
Behavior
Identity

Representing Objects
An object is represented as rectangles with
underlined names
: Professor
a + b = 10
ProfessorClark
Class Name Only
Professor Clark
ProfessorClark :
Professor Object Name Only
Class and Object Name

(stay tuned for classes)
Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is a Class?
A class is a description of a group of objects
with common properties (attributes),
behavior (operations), relationships, and
semantics
An object is an instance of a class
A class is an abstraction in that it:
Emphasizes relevant characteristics
Suppresses other characteristics
OO Principle: Abstraction
Sample Class
Class
Course
Properties Behavior
Name Add a student
Location Delete a student
a + b = 10
Days offered Get course roster
Credit hours Determine if it is full
Start time
End time

Representing Classes
A class is represented using a
compartmented rectangle
a + b = 10
Professor
Professor Clark

Class Compartments
A class is comprised of three sections
The first section contains the class name
The second section shows the structure
(attributes)
The third section shows the behavior
(operations)
Class Name Professor
name
Attributes empID
Operations create( )
save( )
delete( )
change( )

Classes of Objects
How many classes do you see?

The Relationship Between Classes and Objects
A class is an abstract definition of an object
It defines the structure and behavior of each
object in the class
It serves as a template for creating objects
Objects are grouped into classes
Objects Class
Professor
Professor Smith Professor Mellon
Professor Jones
Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is an Attribute?
Object
Class
Attribute Attribute Value

:CourseOffering
number = 101
startTime = 900
CourseOffering endTime = 1100
number
startTime
endTime :CourseOffering
number = 104
startTime = 1300
endTime = 1500

Visibility of the Attributes
+ public
# protected
- private
~ package (default)
/ derived
Underline Static attributes
Derived Attribute(/): Not stored, but can be
computed from other attribute values.
E.g. Age can be counted from Date of Birth

Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is an Operation/Methods?
CourseOffering
Class
addStudent
deleteStudent
getStartTime
Operation getEndTime

Class Operations/Methods
Visibility name (parameters): return_type
Visibility:
+ public
# protected
- private
~ package (default)
Underline Static Methods
Omit return_type on constructors and when
return type is void.

Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

Polymorphism
One of the most useful programming
techniques of the object-oriented
paradigm.
Means “Many forms” - is the ability to
treat an object of any subclass of a
base class as if it were an object of the
base class.
A base class has, therefore, many
forms: the base class itself, and any of
its subclasses.
What is Polymorphism?
The ability to hide many different
implementations behind a single interface
Manufacturer B
Manufacturer A Manufacturer C
OO Principle:
Encapsulation

Polymorphism in Java
To use an object of type Liquid, you must
create aLiquid object with new and store
the returned reference in a variable:
Liquid myFavoriteBeverage = new
Liquid();
myFavoriteBeverage variable holds a
reference to a Liquid object. This is a
sensible arrangement;
However, with the help of polymorphism,
you can assign a reference to any object
that is-a Liquid to a variable of
type Liquid.

Hence any of the following assignments
will also work:
Coffee();
// or...
Milk();

What is an Interface?
Interfaces formalize polymorphism
Interfaces support “plug-and-play”
architectures
Tube
<<interface>>
Shape
Pyramid
Draw
Move
Scale
Rotate Cube
Realization relationship (stay tuned for realization relationships)

Interface Representations
Tube
Elided/Iconic
Representation
(“lollipop”) Pyramid
Shape Cube
Canonical Tube
(Class/Stereotype) <<interface>>
Representation Shape
Pyramid
Draw
Move
Scale
Rotate Cube
(stay tuned for realization relationships)
Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is a Component?
A non-trivial, nearly independent, and
replaceable part of a system that fulfills a
clear function in the context of a well-
defined architecture
A component may be
A source code component OO Principle:
A run time components or Encapsulation
An executable component
Source File <<EXE>> <<DLL>>

Name Executable Component
Name Component Name
Interface
Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is a Package?
A package is a general purpose mechanism
for organizing elements into groups
A model element which can contain other
model elements
OO Principle:
Package Name Modularity
Uses
Organize the model under development
A unit of configuration management
Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

What is a Subsystem?
A combination of a package (can contain
other model elements) and a class (has
behavior)
Realizes one or more interfaces which
define its behavior
Realization
Subsystem
<<subsystem>>
Interface Subsystem Name
Interface
OO Principles: Encapsulation and Modularity

(stay tuned for realization relationship)
Subsystems and Components
Components are the physical realization of
an abstraction in the design
Subsystems can be used to represent the
component in the design
Design Model Implementation Model
<<subsystem>> Component
Component Name Name
Component Component
Interface Interface
OO Principles: Encapsulation and Modularity

Object
Class
Attribute
Operation
Component
Package
Subsystem
Relationships

Relationships
Association
Aggregation
Composition
Dependency
Generalization
Realization

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

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

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

Association: Multiplicity and Navigation
Multiplicity defines how many objects
participate in a relationships
The number of instances of one class related
to ONE instance of the other class
Specified for each end of the association
Associations and aggregations are bi-
directional by default, but it is often
desirable to restrict navigation to one
direction
If navigation is restricted, an arrowhead is
added to indicate the direction of the navigation

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

Example: Multiplicity and Navigation
Multiplicity
Student 1 0..* Schedule
Navigation

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
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 !
What Gets Inherited?
A subclass inherits its parent’s attributes,
operations, and relationships
A subclass may:
Add additional attributes, operations,
relationships
Redefine inherited operations
Common attributes, operations, and/or
relationships are shown at the highest
applicable level in the hierarchy
Inheritance leverages the similarities among classes

Example: What Gets Inherited
GroundVehicle
owner Person
Superclass weight
(parent) licenseNumber 0..* 1
register( )
generalization
Car Truck Trailer

Subclass size tonnage
getTax( )

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

In

A single paradigm
Facilitates architectural and code reuse
Models more closely reflect the real world
More accurately describe corporate data and
processes
Decomposed based on natural partitioning
Easier to understand and maintain
Stability
A small change in requirements does not mean
massive changes in the system under
development
Class Diagram for the Sales Example
Sale
seller buyer item sold shipping mechanism

Salesperson Customer Product Vehicle
Corporate Individual Truck Train

Effect of Requirements Change
Suppose you need a
new type of shipping
vehicle ... Sale
seller buyer item sold shipping mechanism

Salesperson Customer Product Vehicle
Corporate Individual Truck Train Airplane
Change involves adding a new subclass


Stereotypes
Classify and extend the UML notational
elements
Define a new model element in terms of
another model element
May be applied to all modeling elements
Represented with name in guillemets or as
a different icon
<<boundary>>
MyBoundaryClass
MyBoundaryClass

Example: Stereotypes
<<boundary>>
<<boundary>>
Sample boundary class (stereotype)
<<trace>> Stereotype of ‘dependency relation’
DesignClass Stereotype of <<Processor>>
These create new symbols using

accustomed graphics.
<<Processor>>
Processor #1 Processor #1

Notes
A note can be added to any UML element
Notes may be added to add more
information to the diagram
It is a ‘dog eared’ rectangle
The note may be anchored to an element
with a dashed line
There can be up to one
MaintainScheduleForm per
MaintainScheduleForm user session.

Tagged Values
Extensions of the properties, or specific
attributes, of a UML element
Some properties are defined by UML
Persistence
Location (e.g., client, server)
Properties can be created by UML
modelers for any purpose
PersistentClass
{persistence} anObject : ClassA
{location=server}

Constraints
Supports the addition of new rules or
modification of existing rules
Member 1
Professor Department
1..*
{subset}
Department Head
1 1
This notation is used to capture two relationships between Professor-type objects

and Department-type objects; where one relationship is a subset of another….
Shows how UML can be tailored to correctly modeling exact relationships….

Review: Introduction to Object Orientation
What are the four basic principles of object
orientation? Provide a brief description of
each.
What is an Object and what is a Class?
What is the difference between them?
What is an Attribute?
What is an Operation?
What is an Interface? What is
Polymorphism?
What is a Component?
(continued)
Review: Introduction to Object Orientation (cont.)
What is a Package?
What is Subsystem? How does it relate to
a Component? How does it relate to a
package? How does it relate to a class?
Name the 4 basic UML relationships and
describe each.
Describe the strengths of object orientation.
Name and describe some general UML
mechanisms.
What are stereotypes? Name some
common uses of stereotypes.
The Three Models of OO Development
The three models are used to describe
a system from different view points:
The Class model for the objects in the
system and their relationships
The State model for the life history of
objects
The Interaction model for the
interactions amongst the objects.
Each model applies during all stages
of development.
Class Model
Describes the static structure of

the objects and their relationships.
Defines the context for software
development.
Contains Class Diagrams.
Class Diagram: is a graph whose
nodes are classes and whose arcs
are relationships among classes.

State Model
Describes the aspects of an object

that change over time.
Specifies and implements control
with State diagrams.
State Diagram: is a graph whose
nodes are states and whose arcs
are transitions between states
caused by events.

Interaction Model
Describes how the objects in a system
cooperate to achieve broader results.
Starts with Use Cases that are elaborated
with Sequence and Activity Diagrams.
Use Case: focuses on the functionality of
the system, ie. What it does for the user?
Sequence Diagram: shows the objects
that interact and the time sequence of
their interactions.
Activity Diagram: elaborates important
processing steps.

ch11 Intro To OO & Modeling Concept

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

ch11 Intro To OO & Modeling Concept

Uploaded by

Copyright:

Available Formats

Object Oriented Analysis and Design

Using the UML

Introduction to Object Orientation

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

How does an object encapsulate?

BankAccount Security RealEstate

Savings Checking Stock Bond

Decreasing Elements at the same level of the hierarchy

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

Software entity Linked List

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

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

Class and Object Name

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

Professor Smith Professor Mellon

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

Attribute Attribute Value

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

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

Realization relationship (stay tuned for realization relationships)

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

Source File <<EXE>> <<DLL>>

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

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

OO Principles: Encapsulation and Modularity

OO Principles: Encapsulation and Modularity

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

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

One or more 1..*

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

Student 1 0..* Schedule

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

Subclasses Withdraw() GetInterest()

Airplane Helicopter Bird Wolf Horse

Use multiple inheritance only when needed, and

Inheritance leverages the similarities among classes

Car Truck Trailer

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