Scribd
Upload
2 views29 pages

Module 3

Module 3 covers dynamic and implementation UML diagrams, including system sequence, collaboration, state machine, and activity diagrams. It emphasizes the importance of sequence diagrams for visualizing interactions and messages between system components, detailing their construction and use cases. Additionally, it introduces communication diagrams, focusing on object relationships and message sequences for functionality realization.

Uploaded by

sriramravichandran2006
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
2 views29 pages

Module 3

Module 3 covers dynamic and implementation UML diagrams, including system sequence, collaboration, state machine, and activity diagrams. It emphasizes the importance of sequence diagrams for visualizing interactions and messages between system components, detailing their construction and use cases. Additionally, it introduces communication diagrams, focusing on object relationships and message sequences for functionality realization.

Uploaded by

sriramravichandran2006
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/ 29

Module 3

Dynamic and Implementation


UML Diagrams
Prepared By
Pavithra A
AP/IT
KRCE
MODULE 3
• Dynamic Diagrams – UML interaction diagrams – System sequence
diagram – Collaboration diagram –State machine diagram and
Modeling – Activity diagram -Implementation Diagram– UML package
diagram – Component and Deployment Diagrams

• SELF STUDY TOPIC : Logical Architectures and Layers

• CO3--Construct and implement various dynamic UML diagrams.


Static modelling
• The static Modelling is used to represent the static constituents of a
software such as class, objects interfaces and relationship among
them.
• The static modelling is done using
• Class Diagram
• Object Diagram
Dynamic Diagram
• Dynamic Modelling represents behavior, workflow, states and so on.
• Dynamic modelling done using
• Usecase modelling
• Interaction modelling
• Sequence diagram
• Communication diagram or collaboration diagram
• State Modelling
• State chart diagram
• Activity diagram
Sequence Diagram
• Sequence diagrams are visually represent the interactions between
objects or components in a system over time.
• They focus on the order and timing of messages or events exchanged
between different system elements.
• The diagram captures how objects communicate with each other
through a series of messages, providing a clear view of the sequence
of operations or processes.
Why use Sequence diagram?
• Visualizing dynamic behavior
• Clear Communication
• Usecase Analysis
• Designing System Architecture
• Documenting System Behavior
• Debugging & trouble shooting
Example
Notations used in Sequence
diagram
• Actors
• Lifeline or timeline
• Box ,Activation box
• Messages – synchronous and Asynchronous Messages
• Create Message
• Delete Message
• Self Message
• Reply Message
• Found Message
• Lost Message
• Guards
Actor
• We use actors to depict various roles including human users and
other external subjects.
• We represent an actor in a UML diagram using a stick person
notation.
• We can have multiple actors in a sequence diagram.
Lifeline

A lifeline is a named element


which depicts an individual
participant in a sequence
diagram. So basically each
instance in a sequence
diagram is represented by a
lifeline. Lifeline elements are
located at the top in a
sequence diagram.
Messages
• Communication between objects is depicted using messages. The
messages appear in a sequential order on the lifeline.
• We represent messages using arrows.
• Lifelines and messages form the core of a sequence diagram.
• Represent messages using arrows.
• Lifelines and messages form the core of a sequence diagram
Types of Messages
• Synchronous • Asynchronous
Create Message
Delete Message
Self Message
Found Message
Lost Image
Guards
• When we need to restrict the flow of messages on the pretext of a
condition being met.
• Guards play an important role in letting software developers know the
constraints attached to a system or a particular process.
How to draw sequence diagram ?
Step 1: Identify the Scenario
Step 2: List the Participants
Step 3: Define Lifelines
Step 4: Arrange Lifelines
Step 5: Add Activation Bars
Step 6: Draw Messages
Step 7: Include Return Messages
Step 8: Indicate Timing and Order
Step 9: Include Conditions and Loops
Step 10: Consider Parallel Execution
Step 11: Review and Refine
Step 12: Add Annotations and Comments
Step 13: Document Assumptions and Constraints
Step 14: Tools
Example for sequence Diagram
When to use Sequence Diagram?
• One particular scenario of a use case
• The events that are generated by the external actors
• Sequence of those events
• Events among the interacting objects of the system.
Communication Diagram
• Speaking of communication diagrams, they are also called
collaboration diagrams, which are UML structures used for the
definition of interacting objects.
• They are concerned with the relationship between two objects and
the sequence of messages passed between the two to realize a
specific functionality.
Notations
• Objects / participants
• Multiple Objects
• Actors
• Messages
• Self Message
• Link
• Return Message
Steps to create communication
diagram
Step 1: Identify the purpose
Step 2: Define the Objects
Step 3: Establish Relationships
Step 4: Define Messages
Step 4: Illustrate Interactions
Step 5: Review and Refine
Step 6: Document and Validate
Example

You might also like