SlideShare a Scribd company logo
Business Analysis
Training
Introduction to OOA and UML – Part 2
Page 2Classification: Restricted
Agenda
• Sequence Diagram (Cont…)
• Interaction Diagram
• State Diagram
• Activity Diagram
Page 3Classification: Restricted
Sequence Diagrams
Page 4Classification: Restricted
Class Roles or Participants
Class roles describe the way an object will behave in context. Use the UML
object symbol to illustrate class roles, but don't list object attributes.
Basic Sequence Diagram Symbols and Notations
Page 5Classification: Restricted
Basic Sequence Diagram Symbols and Notations
Activation or Execution Occurrence
Activation boxes represent the time an object needs to complete a task.
When an object is busy executing a process or waiting for a reply message,
use a thin gray rectangle placed vertically on its lifeline.
Page 6Classification: Restricted
Basic Sequence Diagram Symbols and Notations
Messages
Messages are arrows that represent communication between objects. Use
half-arrowed lines to represent asynchronous messages. Asynchronous
messages are sent from an object that will not wait for a response from the
receiver before continuing its tasks..
Page 7Classification: Restricted
Basic Sequence Diagram Symbols and Notations
Lifelines
Lifelines are vertical dashed lines that indicate the object's presence over
time.
Page 8Classification: Restricted
Basic Sequence Diagram Symbols and Notations
Destroying Objects
Objects can be terminated early using an arrow labeled "<< destroy >>" that
points to an X. This object is removed from memory. When that object's
lifeline ends, you can place an X at the end of its lifeline to denote a
destruction occurrence.
Loops
A repetition or loop within a sequence diagram is depicted as a rectangle.
Place the condition for exiting the loop at the bottom left corner in square
brackets [ ].
Page 9Classification: Restricted
Types of Messages in Sequence Diagram
Synchronous Message
A synchronous message requires a response before the interaction can
continue. It's usually drawn using a line with a solid arrowhead pointing
from one object to another.
Page 10Classification: Restricted
Types of Messages in Sequence Diagram
Asynchronous Message
Asynchronous messages don't need a reply for interaction to continue. Like
synchronous messages, they are drawn with an arrow connecting two
lifelines; however, the arrowhead is usually open and there's no return
message depicted.
Page 11Classification: Restricted
Types of Messages in Sequence Diagram
Page 12Classification: Restricted
Types of Messages in Sequence Diagram
Page 13Classification: Restricted
Types of Messages in Sequence Diagram
Page 14Classification: Restricted
Types of Messages in Sequence Diagram
Page 15Classification: Restricted
Caller Phone Recipient
Picks up
Dial tone
Dial
Ring notification Ring
Picks up
Hello
Sequence Diagram (make a phone call)
Page 16Classification: Restricted
Sequence Diagram : Object interaction
Self-Call: A message that an
Object sends to itself.
Condition: indicates when a
message is sent. The message is
sent only if the condition is true.
Iteration
Condition
A B
Synchronous
Asynchronous
Transmission
delayed
Self-Call
[condition]
remove()
*[for each]
remove()
Page 17Classification: Restricted
Sequence Diagrams – Object Life Spans
• Creation
• Create message
• Object life starts at that point
• Activation
• Symbolized by rectangular stripes
• Place on the lifeline where object is
activated.
• Rectangle also denotes when object
is deactivated.
• Deletion
• Placing an ‘X’ on lifeline
• Object’s life ends at that point
Activation
bar
A
B
Create
X
Deletion
Return
Lifeline
Page 18Classification: Restricted
Sequence Diagrams – Example
Page 19Classification: Restricted
The second interaction diagram is collaboration diagram. It shows the
object organization. Here in collaboration diagram the method call
sequence is indicated by some numbering technique.
Collaboration Diagrams
Page 20Classification: Restricted
Collaboration Diagram : Example
Page 21Classification: Restricted
• Shows the relationship between objects and the order of messages passed
between hem.
• The objects are listed as rectangles and arrows indicate the messages being
passed
• The numbers next to the messages are called sequence numbers. They
show the sequence of the messages as they are passed between the objects.
• Convey the same information as sequence diagrams, but focus on object
roles instead of the time sequence.
Interaction Diagrams : Collaboration diagrams
Page 22Classification: Restricted
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.
Unpaid
Start End
Paid
Invoice created paying Invoice destroying
Page 23Classification: Restricted
State Diagrams: (Traffic light example)
Yellow
Red
Green
Traffic Light
State
Transition
Event
Star
t
Page 24Classification: Restricted
Activity Diagram
Overview
• Activity diagram is another important diagram in UML to describe dynamic
aspects of the system.
• Activity diagram is basically a flow chart to represent the flow form one
activity to another activity. The activity can be described as an operation of
the system.
• So the control flow is drawn from one operation to another. This flow can
be sequential, branched or concurrent. Activity diagrams deals with all type
of flow control by using different elements like fork, join etc.
Page 25Classification: Restricted
Purpose of an Activity Diagram
• Draw the activity flow of a system.
• Describe the sequence from one activity to another.
• Describe the parallel, branched and concurrent flow of the system.
Page 26Classification: Restricted
Elements of Activity Diagram
Page 27Classification: Restricted
Activity Diagram : Example
Page 28Classification: Restricted
Page 29Classification: Restricted
Page 30Classification: Restricted
Activity Diagram : Example
Page 31Classification: Restricted
Page 32Classification: Restricted
UML Modeling Tools
• Rational Rose (www.rational.com) by IBM
• TogetherSoft Control Center, Borland
(http://www.borland.com/together/index.html)
• ArgoUML (free software) (http://argouml.tigris.org/ )
OpenSource; written in java
• Others
(http://www.objectsbydesign.com/tools/umltools_byCompany.html )
Page 33Classification: Restricted
Reference
1. UML Distilled: A Brief Guide to the Standard Object Modeling Language
Martin Fowler, Kendall Scott
2. IBM Rational
http://www-306.ibm.com/software/rational/uml/
3. Practical UML --- A Hands-On Introduction for Developers
http://www.togethersoft.com/services/practical_guides/umlonlinecourse/
4. Software Engineering Principles and Practice. Second Edition;
Hans van Vliet.
5. http://www-inst.eecs.berkeley.edu/~cs169/
Page 34Classification: Restricted
•Requirements Management
•Requirement Prioritization
•MoSCoW Analysis
•Time Boxing
•Voting Technique
•Verifying and Validating Requirements
•Verifying Requirements
•Validate Requirements
•Key Requirements Management Practices
•The Requirements Baseline
•Requirements Version Management
•Requirements Change Control
•Impact Analysis of Requirements
•Requirements Attributes
•Requirements status tracking
•Requirements Traceability
•Requirements Traceability Matrix
Topics to be covered in next session
Page 35Classification: Restricted
Thank you

More Related Content

PPSX
Introduction to OOA and UML
PPSX
Introduction to OOA and UML - Part 1
PPSX
Unified Modeling Language - UML - Complete Guide - Part 2
PPSX
Unified Modeling Language - UML - Complete Guide - Part 1
PPSX
Introduction to OOA and UML
PPSX
UML Training for Business Analysts
PPSX
Introduction to UML
PPSX
Introduction to OOA and UML - Part 2
Introduction to OOA and UML
Introduction to OOA and UML - Part 1
Unified Modeling Language - UML - Complete Guide - Part 2
Unified Modeling Language - UML - Complete Guide - Part 1
Introduction to OOA and UML
UML Training for Business Analysts
Introduction to UML
Introduction to OOA and UML - Part 2

What's hot (18)

DOCX
Behavioural modelling
PPTX
UML Diagram @ Software engineering discussion
PPT
Fundamentals of Software Engineering
PPT
PPT
Intro Uml
PPT
UML- Unified Modeling Language
PPT
Intro to relational model
PPT
Uml - An Overview
PPT
Ch 5 O O Data Modeling
PPT
UML Diagram Assignment Help, UML Diagram Homework Help
PPT
The Database Environment Chapter 4
PDF
Types of UML diagrams
PPTX
Enhanced ER(database)
PPTX
Uml Presentation
PPTX
UML Diagram - Use-Case diagram, Activity Diagram, Sequence Diagram, Er Diagra...
PPTX
Ooad static diagram
PDF
Object oriented software engineering concepts
PPT
Object Oriented Dbms
Behavioural modelling
UML Diagram @ Software engineering discussion
Fundamentals of Software Engineering
Intro Uml
UML- Unified Modeling Language
Intro to relational model
Uml - An Overview
Ch 5 O O Data Modeling
UML Diagram Assignment Help, UML Diagram Homework Help
The Database Environment Chapter 4
Types of UML diagrams
Enhanced ER(database)
Uml Presentation
UML Diagram - Use-Case diagram, Activity Diagram, Sequence Diagram, Er Diagra...
Ooad static diagram
Object oriented software engineering concepts
Object Oriented Dbms
Ad

Similar to Introduction to OOA and UML - Part 2 (20)

PPT
Lecture11 use case sequence diagram
PPTX
08.Sequence Diagrams.pptx in cS to describe
PDF
Activity Diagram part8
PPT
umlpresentation-140519151641-phpapp02.ppt
PDF
CS8592 Object Oriented Analysis & Design - UNIT III
PPT
4 Activity & Statechart diagram.ppt4 Activity & Statechart diagram.ppt4 Activ...
PPT
Slide 4 Interaction Diagram
PPT
OOAD-Unit-3.ppt UML and ANALYSISI AND DESIGN
PDF
SE_Lec 09_ UML Behaviour Diagrams
DOCX
Case tool lab-Reg2013 by Karthick Raja
PDF
CS8592-OOAD Lecture Notes Unit-3
PPTX
An introduction to uml
PDF
Interaction overview & Timing diagram
PPTX
Basic Behavioral Modeling
PPTX
UML - Activity Diagrams (1) for cs.pptx
PPTX
Use case model
PPTX
Architectural Modeling
PPT
CASE Tools lab.ppt
PPT
Uml lecture
PPT
Ooad sequence diagram lecture
Lecture11 use case sequence diagram
08.Sequence Diagrams.pptx in cS to describe
Activity Diagram part8
umlpresentation-140519151641-phpapp02.ppt
CS8592 Object Oriented Analysis & Design - UNIT III
4 Activity & Statechart diagram.ppt4 Activity & Statechart diagram.ppt4 Activ...
Slide 4 Interaction Diagram
OOAD-Unit-3.ppt UML and ANALYSISI AND DESIGN
SE_Lec 09_ UML Behaviour Diagrams
Case tool lab-Reg2013 by Karthick Raja
CS8592-OOAD Lecture Notes Unit-3
An introduction to uml
Interaction overview & Timing diagram
Basic Behavioral Modeling
UML - Activity Diagrams (1) for cs.pptx
Use case model
Architectural Modeling
CASE Tools lab.ppt
Uml lecture
Ooad sequence diagram lecture
Ad

More from Shwetha-BA (14)

PPSX
Requirement Elicitation Techniques
PPSX
Role of BA in Testing
PPSX
Requirements Management
PPSX
Workflow Diagram
PPSX
Enterprise Analysis
PPSX
Software Development Life Cycle – SDLC
PPSX
Introduction to Business Analysis
PPSX
Business Aanalysis Resume/Interview preparation
PPS
Solution Evaluation (BA Role)
PPSX
Requirements Management
PPSX
Requirement Elicitation Techniques
PPSX
Enterprise Analysis
PPSX
Software Development Life Cycle - SDLC
PPSX
Introduction to Business Analysis
Requirement Elicitation Techniques
Role of BA in Testing
Requirements Management
Workflow Diagram
Enterprise Analysis
Software Development Life Cycle – SDLC
Introduction to Business Analysis
Business Aanalysis Resume/Interview preparation
Solution Evaluation (BA Role)
Requirements Management
Requirement Elicitation Techniques
Enterprise Analysis
Software Development Life Cycle - SDLC
Introduction to Business Analysis

Recently uploaded (20)

PPT
Teaching material agriculture food technology
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
PPTX
sap open course for s4hana steps from ECC to s4
PDF
Encapsulation theory and applications.pdf
PDF
Approach and Philosophy of On baking technology
PPTX
Spectroscopy.pptx food analysis technology
PPTX
ACSFv1EN-58255 AWS Academy Cloud Security Foundations.pptx
PDF
Chapter 3 Spatial Domain Image Processing.pdf
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PPTX
Understanding_Digital_Forensics_Presentation.pptx
PDF
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
PPTX
Programs and apps: productivity, graphics, security and other tools
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PDF
Unlocking AI with Model Context Protocol (MCP)
PDF
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
PPT
“AI and Expert System Decision Support & Business Intelligence Systems”
Teaching material agriculture food technology
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
sap open course for s4hana steps from ECC to s4
Encapsulation theory and applications.pdf
Approach and Philosophy of On baking technology
Spectroscopy.pptx food analysis technology
ACSFv1EN-58255 AWS Academy Cloud Security Foundations.pptx
Chapter 3 Spatial Domain Image Processing.pdf
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
NewMind AI Weekly Chronicles - August'25 Week I
Mobile App Security Testing_ A Comprehensive Guide.pdf
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
The Rise and Fall of 3GPP – Time for a Sabbatical?
Understanding_Digital_Forensics_Presentation.pptx
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Programs and apps: productivity, graphics, security and other tools
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Unlocking AI with Model Context Protocol (MCP)
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
“AI and Expert System Decision Support & Business Intelligence Systems”

Introduction to OOA and UML - Part 2

  • 2. Page 2Classification: Restricted Agenda • Sequence Diagram (Cont…) • Interaction Diagram • State Diagram • Activity Diagram
  • 4. Page 4Classification: Restricted Class Roles or Participants Class roles describe the way an object will behave in context. Use the UML object symbol to illustrate class roles, but don't list object attributes. Basic Sequence Diagram Symbols and Notations
  • 5. Page 5Classification: Restricted Basic Sequence Diagram Symbols and Notations Activation or Execution Occurrence Activation boxes represent the time an object needs to complete a task. When an object is busy executing a process or waiting for a reply message, use a thin gray rectangle placed vertically on its lifeline.
  • 6. Page 6Classification: Restricted Basic Sequence Diagram Symbols and Notations Messages Messages are arrows that represent communication between objects. Use half-arrowed lines to represent asynchronous messages. Asynchronous messages are sent from an object that will not wait for a response from the receiver before continuing its tasks..
  • 7. Page 7Classification: Restricted Basic Sequence Diagram Symbols and Notations Lifelines Lifelines are vertical dashed lines that indicate the object's presence over time.
  • 8. Page 8Classification: Restricted Basic Sequence Diagram Symbols and Notations Destroying Objects Objects can be terminated early using an arrow labeled "<< destroy >>" that points to an X. This object is removed from memory. When that object's lifeline ends, you can place an X at the end of its lifeline to denote a destruction occurrence. Loops A repetition or loop within a sequence diagram is depicted as a rectangle. Place the condition for exiting the loop at the bottom left corner in square brackets [ ].
  • 9. Page 9Classification: Restricted Types of Messages in Sequence Diagram Synchronous Message A synchronous message requires a response before the interaction can continue. It's usually drawn using a line with a solid arrowhead pointing from one object to another.
  • 10. Page 10Classification: Restricted Types of Messages in Sequence Diagram Asynchronous Message Asynchronous messages don't need a reply for interaction to continue. Like synchronous messages, they are drawn with an arrow connecting two lifelines; however, the arrowhead is usually open and there's no return message depicted.
  • 11. Page 11Classification: Restricted Types of Messages in Sequence Diagram
  • 12. Page 12Classification: Restricted Types of Messages in Sequence Diagram
  • 13. Page 13Classification: Restricted Types of Messages in Sequence Diagram
  • 14. Page 14Classification: Restricted Types of Messages in Sequence Diagram
  • 15. Page 15Classification: Restricted Caller Phone Recipient Picks up Dial tone Dial Ring notification Ring Picks up Hello Sequence Diagram (make a phone call)
  • 16. Page 16Classification: Restricted Sequence Diagram : Object interaction Self-Call: A message that an Object sends to itself. Condition: indicates when a message is sent. The message is sent only if the condition is true. Iteration Condition A B Synchronous Asynchronous Transmission delayed Self-Call [condition] remove() *[for each] remove()
  • 17. Page 17Classification: Restricted Sequence Diagrams – Object Life Spans • Creation • Create message • Object life starts at that point • Activation • Symbolized by rectangular stripes • Place on the lifeline where object is activated. • Rectangle also denotes when object is deactivated. • Deletion • Placing an ‘X’ on lifeline • Object’s life ends at that point Activation bar A B Create X Deletion Return Lifeline
  • 19. Page 19Classification: Restricted The second interaction diagram is collaboration diagram. It shows the object organization. Here in collaboration diagram the method call sequence is indicated by some numbering technique. Collaboration Diagrams
  • 21. Page 21Classification: Restricted • Shows the relationship between objects and the order of messages passed between hem. • The objects are listed as rectangles and arrows indicate the messages being passed • The numbers next to the messages are called sequence numbers. They show the sequence of the messages as they are passed between the objects. • Convey the same information as sequence diagrams, but focus on object roles instead of the time sequence. Interaction Diagrams : Collaboration diagrams
  • 22. Page 22Classification: Restricted 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. Unpaid Start End Paid Invoice created paying Invoice destroying
  • 23. Page 23Classification: Restricted State Diagrams: (Traffic light example) Yellow Red Green Traffic Light State Transition Event Star t
  • 24. Page 24Classification: Restricted Activity Diagram Overview • Activity diagram is another important diagram in UML to describe dynamic aspects of the system. • Activity diagram is basically a flow chart to represent the flow form one activity to another activity. The activity can be described as an operation of the system. • So the control flow is drawn from one operation to another. This flow can be sequential, branched or concurrent. Activity diagrams deals with all type of flow control by using different elements like fork, join etc.
  • 25. Page 25Classification: Restricted Purpose of an Activity Diagram • Draw the activity flow of a system. • Describe the sequence from one activity to another. • Describe the parallel, branched and concurrent flow of the system.
  • 32. Page 32Classification: Restricted UML Modeling Tools • Rational Rose (www.rational.com) by IBM • TogetherSoft Control Center, Borland (http://www.borland.com/together/index.html) • ArgoUML (free software) (http://argouml.tigris.org/ ) OpenSource; written in java • Others (http://www.objectsbydesign.com/tools/umltools_byCompany.html )
  • 33. Page 33Classification: Restricted Reference 1. UML Distilled: A Brief Guide to the Standard Object Modeling Language Martin Fowler, Kendall Scott 2. IBM Rational http://www-306.ibm.com/software/rational/uml/ 3. Practical UML --- A Hands-On Introduction for Developers http://www.togethersoft.com/services/practical_guides/umlonlinecourse/ 4. Software Engineering Principles and Practice. Second Edition; Hans van Vliet. 5. http://www-inst.eecs.berkeley.edu/~cs169/
  • 34. Page 34Classification: Restricted •Requirements Management •Requirement Prioritization •MoSCoW Analysis •Time Boxing •Voting Technique •Verifying and Validating Requirements •Verifying Requirements •Validate Requirements •Key Requirements Management Practices •The Requirements Baseline •Requirements Version Management •Requirements Change Control •Impact Analysis of Requirements •Requirements Attributes •Requirements status tracking •Requirements Traceability •Requirements Traceability Matrix Topics to be covered in next session