Scribd
Upload
25 views13 pages

Uml Diagrams Tutorial

Uploaded by

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

Uml Diagrams Tutorial

Uploaded by

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

UML DIAGRAMS

Sequence Diagrams Tutorial


Use Case Diagram Tutorial
Flow Chart Diagram Tutorial
Sequence Diagram
What is Sequence Diagram ?

 In simpler words, a sequence diagram shows how different parts of a


system work in a ‘sequence’ to get something done.
 Sequence diagrams are commonly used in software development to
illustrate the behavior of a system or to help developers design and
understand complex systems. They can be used to model both simple
and complex interactions between objects, making them a useful tool for
software architects, designers, and developers.
Sequence Diagram Notations:
1.Lifeline (Objects)

 Lifeline Notation:

 A sequence diagram is made up of several of these lifeline notations that


should be arranged horizontally across the top of the diagram. No two lifeline
notations should overlap each other. They represent the different objects or
parts that interact with each other in the system during the sequence.
2. Activation Bars

 Activation Bars

 The activation bar is the box placed on the lifeline. It is used to indicate that
an object is active during an interaction between two objects. The length of
the rectangle indicates the duration of the objects staying active.
 In a sequence diagram, an interaction between two objects occurs when one
object sends a message to another. The use of the activation bar on the
lifelines of the Message Caller (the object that sends the message) and the
Message Receiver (the object that receives the message) indicates that both
are active during the exchange of the message.
3. Message Arrows

 An arrow from the Message Caller to the Message Receiver specifies a message
in a sequence diagram. A message can flow in any direction; from left to
right, right to left, or back to the Message Caller itself. While you can
describe the message being sent from one object to the other on the arrow,
with different arrowheads you can indicate the type of message being sent or
received.
4. Reflexive message

 When an object sends a message to itself, it is called a reflexive message. It


is indicated with a message arrow that starts and ends at the same lifeline .
Use cases Diagram

 What is a Use Case Diagram ?

 A use case describes how a user uses a system to accomplish a particular goal.
A use case diagram consists of the system, the related use cases and actors
and relates these to each other to visualize: what is being described?
(system), who is using the system? (actors) and what do the actors want to
achieve? (use cases), thus, use cases help ensure that the correct system is
developed by capturing the requirements from the user's point of view.
A use case (or set of use cases) has
these characteristics:
 Organizes functional requirements
 Models the goals of system/actor (user) interactions
 Describes one main flow of events (main scenarios) and possibly other
exceptional flows (alternatives), also called paths or user scenarios
Cont…

 Actor
 Actors are usually individuals involved with the system defined according to
their roles. The actor can be a human or other external system.
 Use Case
 A use case describes how actors uses a system to accomplish a particular goal.
Use cases are typically initiated by a user to fulfill goals describing the
activities and variants involved in attaining the goal.
 Relationship
 The relationships between and among the actors and the use cases.
 System Boundary
 The system boundary defines the system of interest in relation to the world
around it.
How to Draw a Use Case Diagram?

 How to Draw a Use Case Diagram?


 A Use Case model can be developed by following the steps below.
 Identify the Actors (role of users) of the system.
 For each category of users, identify all roles played by the users relevant to
the system.
 Identify what are the users required the system to be performed to achieve
these goals.
 Create use cases for every goal.
 Structure the use cases.
 Prioritize, review, estimate and validate the users.
Structuring Use Cases

 UML defines three stereotypes of association between Use Cases:


 <<include>> Use Case
 Include relationships should be used for common and mandatory behaviors
that are relevant to the main goal of your use cases.
 <<extend>> Use Case
 Extend relationships should be used for optional and conditional behaviors
that are not essential to the main goal of your use cases

You might also like