Scribd
Upload
74 views26 pages

Object Oriented Analysis (UML)

The document discusses object-oriented analysis and design using the Unified Modeling Language (UML). It describes the Unified Process, a software development lifecycle model. The major phases are Inception, Elaboration, Construction, and Transition. Use case diagrams, activity diagrams, and sequence diagrams are discussed as key artifacts to model system functionality and logic. Use case diagrams capture actor interactions and system functions while activity diagrams show workflow and sequence diagrams display message flows between objects.

Uploaded by

Naglaa Mostafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
74 views26 pages

Object Oriented Analysis (UML)

The document discusses object-oriented analysis and design using the Unified Modeling Language (UML). It describes the Unified Process, a software development lifecycle model. The major phases are Inception, Elaboration, Construction, and Transition. Use case diagrams, activity diagrams, and sequence diagrams are discussed as key artifacts to model system functionality and logic. Use case diagrams capture actor interactions and system functions while activity diagrams show workflow and sequence diagrams display message flows between objects.

Uploaded by

Naglaa Mostafa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

SYSTEMS ANALYSIS & DESIGN

OBJECT ORIENTED ANALYSIS


(UML)
by
Roslina Abd Hamid
Faculty of Computer Systems & Software
Enginering
[email protected]
Chapter Description

Expected Outcomes

• To explain on Use Case Diagram and how to model system functionality


• To know how activity diagram represent system logic
• To know how sequence diagram represent system logic

References

• J.A Hoffer, J.F. George, and J.S. Valacich, "Modern Systems Analysis and Design", 7/E,
Addison-Wesley, 2014
• Kenneth E. Kendall, Julie E. Kendall.,“Systems Analysis and Design ”, Pearson, 2014
• D. Jeya Mala and S. Geeta, "Object Oriented Analysis & Design Using UML", McGrawHill, 2013
• Alan Dennis, Barbara Haley Wixom, David Tegarden, "Systems Analysis and Design With UML
: An Object-Oriented Approach ", John Wiley, 2010
• Klaus Pohl, "Requirement Engineering Fundamentals", Santa Barbara, CA : Rocky Nook, 2011
SDLC Object Oriented

Object oriented software development life cycle


model namely Unified Process or Rational
Unified Process (RUP).
The model was proposed by Booch, Jacobson
and Rumbaugh.
It is an iterative process to add or update the
components based on feedbacks from the
previous iteration.
SDLC Object Oriented

RUP has four major phases:


1.Inception
2.Elaboration
3.Construction
4.Transition
SDLC Object Oriented

One of the artifact during Inception phase is


Primary Use Case Diagram.
In this phase, communication with customers
takes place to elicit requirements.
Use Case Diagram captures the functional
requirements of the system.
SDLC Object Oriented

At the end of Elaboration phase, we can get


artefacts such as:
Use Case Description
Detailed Use Case Diagram
Sequence diagram
Activity Diagram
State Diagram
Etc.
Class

Class is a logical entity as a template for creating


similar kinds of objects. It shares common
properties of objects.

Example of real classes such as: car, student,


courses etc.
Object

An object is an instance of a class that has a


well-defined collection of state and behaviours.
Each object has a unique identity to distinguish it
from all other objects in the same domain.
Use Case Diagram

Use Case Diagram is used to gain better


understanding the functionality of the system at a
very high level.
A use case diagram is drawn when gathering and
defining requirements for the system.
Use Case Diagram

Components of Use Case Diagram:


Actor :stick figures represent a role that a user
can play while interacting with the
system.
It also can represent another system in
which the current system interacts.

Actor1
Use Case Diagram

Components of Use Case Diagram:


Use Case: represents a system functionality
can extend another use case
can include another use case
Is placed inside the system boundary
Labelled as verb-noun phrase

UseCase1
Use Case Diagram

Components of Use Case Diagram:


Boundary: Represent the scope of the system.
Labelled system’s name inside or on
top.

System name
Use Case Diagram

Components of Use Case Diagram:


Association relationship:
links an actor with the use case(s)
with which it interacts

Include relationship :
represents the inclusion of the
functionality of one use case within
another
Use Case Diagram

Components of Use Case Diagram:

Include relationship :
represents the inclusion of the
functionality of one use case within
another
<<include>>
Use Case Diagram

Components of Use Case Diagram:


Extend relationship :
represents the extension of the use
case to include optional behaviour.

<<extend>>
Use Case Diagram

Components of Use Case Diagram:

Generalization relationship:
represents a specialized use case to
a more generalized one.
Use Case Diagram

Room Reservation
Register as Member

Book Room

Manage Booking
Customer Manager

Approve Transaction

Manage Room
Activity Diagram

Activity diagram show the conditional logic for the


sequence of system activities in order to
complete a business process.
Also show the logic of a use case.
Model work flow and business processes.
Model the sequential and concurrent steps in a
computation process.
Activity Diagram

Components of activity diagram:


Activity : a behavior that an object carries out
Transition : a movement from one activity to
another
Branch : a diamond symbol containing
transitions to different paths of
activities.
Activity Diagram

Synchronization bar: horizontal or vertical bars


denoting parallel or concurrent
paths of activities
Fork: the beginning of parallel
activities
Join: the end of parallel activities
Swimlanes : columns representing different
organizational units of the system
Activity Diagram
Sequence Diagram

Sequence Diagram is a dynamic modelling.


It captures the time sequence of message flow
from one object to another.
• Generic form displays all possible
sequences of interactions – sequences
corresponding to all the scenarios of a use
case.
• Instance form displays the sequence for
only one scenario.
Sequence Diagram

Components of Sequence Diagram:


Actor : a person or system (external) that
derives benefit from system
Objects : placed across the top of the diagram
Lifeline : the life of an object during a
sequence.
Messages : convey message from one object to
another.
Sequence Diagram

Activation: the time period during which an object


performs an operation
Synchronous message: a type of message in which
the caller has to wait for the receiving
object to finish executing the called
operation before it can resume execution
itself
Simple message: a message that transfers control
from the sender to the recipient without
describing the details of the
communication
Sequence Diagram

Asynchronous message: a message in which the


sender does not have to wait for the
recipient to handle the message

.
Sequence Diagram

You might also like