Software Eng

+
Software Engineering
Chapter 4
System Modeling
Topics covered
What is UML and why we use UML?
How to use UML diagrams to design software system?
What UML Modeling tools we use today?
Modeling
Describing a system at a high level of abstraction
A model of the system
Used for requirements and specifications
What is UML and Why we use UML?
UML Unified Modeling Language
Language: express idea, not a methodology
More description about UML:
It is a industry-standard graphical language for specifying,

visualizing, constructing, and documenting the artifacts of
software systems
The UML uses mostly graphical notations to express the OO

analysis and design of software projects.
Simplifies the complex process of software design
Why we use UML?
Use graphical notation: more clearly than natural language

(imprecise) and code (too detailed).
Help acquire an overall view of a system.
UML is not dependent on any one language or technology.
How to use UML diagrams to

design software system?
Types of UML Diagrams:
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
State Diagram
This is only a subset of diagrams but are most widely used
Use-Case Diagrams
A use-case diagram is a set of use cases
A use case is a model of the interaction between
External users of a software product (actors) and
The software product itself
More precisely, an actor is a user playing a specific role
describing a set of user scenarios
capturing user requirements
Use-Case Diagrams
Boundary
Actor
Use Case
Library System
Borrow
Employee
Client
Order Title
Fine Remittance
Supervisor
Use-Case Diagrams
Actors: A role that a user plays with respect to the system, including
human users and other systems. e.g., inanimate physical objects (e.g.
robot); an external system that needs some information from the
current system.
Use case: A set of scenarios that describing an interaction between a

user and a system, including alternatives.
System boundary: rectangle diagram representing the boundary

between the actors and the system.
Use-Case Diagrams
Association:
communication between an actor and a use case; Represented by a

solid line.
Generalization:
relationship between one general use case and a special use case
(used for defining special alternatives) Represented by a line with a
triangular arrow head toward the parent use case.
Use-Case Diagrams
Include: a dotted line labeled <<include>> beginning at base use
case and ending with an arrows pointing to the include use case.
The include relationship occurs when a chunk of behavior is similar
across more than one use case. Use include in stead of copying the
description of that behavior.
<<include>>
Extend: a dotted line labeled <<extend>> with an arrow toward

the base case. The extending use case may add behavior to the
base use case. The base class declares extension points.
<<extend>>
Use-Case Diagrams
Use cases in the MHC-PMS involving

the role Medical Receptionist
Use-Case Diagrams
Both Make Appointment

and Request Medication
include Check Patient
Record as a subtask
(include)
The extension point is

written inside the base case
Pay bill; the extending
class Defer payment adds
the behavior of this
extension point. (extend)
Pay Bill is a parent use case

and Bill Insurance is the
child use case.
(generalization)
Class diagram
A class diagram depicts classes and their interrelationships
Used for describing structure and behavior in the use cases
Provide a conceptual model of the system in terms of entities

and their relationships
Used for requirement capture, end-user interaction
Class diagram
Each class is represented by a rectangle subdivided into

three compartments
Name
Attributes
Operations
Modifiers are used to indicate visibility of attributes and

operations.
+ is used to denote Public visibility (everyone)
# is used to denote Protected visibility (friends and
derived)
- is used to denote Private visibility (no one)
By default, attributes are hidden and operations are visible.
Class diagram
Account_Name
- Customer_Name
- Balance
+addFunds( )
+withDraw( )
+transfer( )
Name
Attributes
Operations
OO Relationships
There are two kinds of Relationships

Generalization (parent-child relationship)
Association (student enrolls in course)
+ OO Relationships: Generalization
Supertype
Example:
Customer
Regular
Customer
Subtype1
Loyalty
Customer
Subtype2
-Inheritance is a required feature of object orientation
-Generalization expresses a parent/child relationship among

related classes.
-Used for abstracting details in several layers
OO Relationships: Association
Represent
relationship between instances of classes
Student
enrolls in a course
Courses have students
Courses have exams
Etc.
Association
Role
has two ends
names (e.g. enrolls)

Multiplicity (e.g. One course can have many students)
Navigability (unidirectional, bidirectional)
Association: Multiplicity
Multiplicity
Symbol
Meaning
One and only one
0..1
Zero or one
M..N
From M to N (natural language)
From zero to any positive integer
0..*
From zero to any positive integer
1..*
From one to any positive integer
Class diagram
Interaction Diagrams
show
how objects interact with one another
UML
supports two types of interaction

diagrams
Sequence
diagrams
Collaboration diagrams
Sequence Diagram(make a phone call)
Caller
Phone
Recipient
Picks up
Dial tone
Dial
Ring notification
Ring
Picks up
Hello
+ Collaboration diagrams
+ The difference between
sequence diagram and

collaboration diagram?
Collaboration diagrams are equivalent to sequence diagrams.

All the features of sequence diagrams are equally applicable
to collaboration diagrams
Use a sequence diagram when the transfer of information is

the focus of attention
Use a collaboration diagram when concentrating on the

classes
Sequence Diagram
Collaboration Diagram
State Diagrams (Billing Example)

State Diagrams show the sequences of states an object goes through
during its life cycle in response to stimuli, together with its responses
and actions; an abstraction of all possible behaviors.
End
Start
Unpaid
Invoice created
Paid
paying
Invoice destroying
+
State Diagrams (Traffic light example)
Traffic Light
State
Transition
Red
Yellow
Green
Event
Start
Key points
A model is an abstract view of a system that ignores system

details.
UML is a standardized specification language for object modeling
Several UML diagrams:
use-case diagram: a number of use cases (use case models the interaction between
actors and software)
Class diagram: a model of classes showing the static relationships among them
including association and generalization.
Sequence diagram: shows the way objects interact with one another as messages are
passed between them. Dynamic model
State diagram: shows states, events that cause transitions between states. Another
dynamic model reflecting the behavior of objects and how they react to specific
event
+
Thanks!

Software Eng

Uploaded by

Copyright:

Available Formats

Software Eng

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

Software Eng

Uploaded by

Copyright:

Available Formats

+

What is UML and why we use UML?

How to use UML diagrams to design software system?

What UML Modeling tools we use today?

Describing a system at a high level of abstraction

A model of the system

Used for requirements and specifications

What is UML and Why we use UML?

UML Unified Modeling Language

Language: express idea, not a methodology

What is UML and Why we use UML?

More description about UML:

It is a industry-standard graphical language for specifying,

The UML uses mostly graphical notations to express the OO

Simplifies the complex process of software design

What is UML and Why we use UML?

Why we use UML?

Use graphical notation: more clearly than natural language

Help acquire an overall view of a system.

UML is not dependent on any one language or technology.

How to use UML diagrams to

Types of UML Diagrams:

Use Case Diagram

This is only a subset of diagrams but are most widely used

A use-case diagram is a set of use cases

A use case is a model of the interaction between

External users of a software product (actors) and

The software product itself

More precisely, an actor is a user playing a specific role

describing a set of user scenarios

capturing user requirements

Use case: A set of scenarios that describing an interaction between a

System boundary: rectangle diagram representing the boundary

communication between an actor and a use case; Represented by a

Extend: a dotted line labeled <<extend>> with an arrow toward

Use cases in the MHC-PMS involving

Both Make Appointment

The extension point is

Pay Bill is a parent use case

A class diagram depicts classes and their interrelationships

Used for describing structure and behavior in the use cases

Provide a conceptual model of the system in terms of entities

Used for requirement capture, end-user interaction

Each class is represented by a rectangle subdivided into

Modifiers are used to indicate visibility of attributes and

By default, attributes are hidden and operations are visible.

There are two kinds of Relationships

-Inheritance is a required feature of object orientation

-Generalization expresses a parent/child relationship among

relationship between instances of classes

has two ends

names (e.g. enrolls)

One and only one

From M to N (natural language)

From zero to any positive integer

From zero to any positive integer

From one to any positive integer

how objects interact with one another

supports two types of interaction