0% found this document useful (0 votes)
58 views26 pages

CH 06

This document discusses behavioral modeling techniques including sequence diagrams, communication diagrams, state machines, and CRUDE matrices. It provides guidelines for creating these models, describes how they are used to represent object interactions and state changes, and emphasizes the importance of verifying models for consistency.

Uploaded by

Lim Soong XIan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
58 views26 pages

CH 06

This document discusses behavioral modeling techniques including sequence diagrams, communication diagrams, state machines, and CRUDE matrices. It provides guidelines for creating these models, describes how they are used to represent object interactions and state changes, and emphasizes the importance of verifying models for consistency.

Uploaded by

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

Chapter 6:

Behavioral Modeling
Learning Objectives
 Understand the rules and style guidelines for sequence and
communication diagrams and behavioral state machines.
 Understand the processes used to create sequence and
communication diagrams, behavioral state machines and
CRUDE matrices.
 Be able to create sequence and communication diagrams,
behavioral state machines and CRUDE matrices.
 Understand the relationship between the behavioral models
and the structural and functional models.
Introduction
 Behavioral models describe the internal behavior of a system
 Behavioral model types:
 Representations of the details of a business process identified
by use-cases
Interaction diagrams (Sequence & Communication)
Shows how objects collaborate to provide the functionality defined
in the use cases.
 Representations of changes in the data
Behavioral state machines
 Focus (for now) is on the dynamic view of the system, not on
how it is implemented
Behavioral Models
 Analysts view the problem as a set of use cases supported by
a set of collaborating objects
 Aids in organizing and defining the software
 Behavioral models depict this view of the business processes:
How the objects interact and form a collaboration to support the
use cases
An internal view of the business process described by a use case
 Creating behavioral models is an iterative process which
may induce changes in other models
Interaction Diagrams
 Objects—an instantiation of a class
 Patient is a class
 Mary Wilson is an instantiation of the patient class (object)
 Attributes—characteristics of a class
 Patient class: name, address, phone, etc.
 Operations—the behaviors of a class, or an action that an object can
perform
 Messages—information sent to objects to tell them to execute one of
their behaviors
 A function call from one object to another
 Types
 Sequence Diagrams—emphasize message sequence
 Communication Diagrams—emphasize message flow
Sequence Diagrams
 Illustrate the objects that participate in a single use-case
 A dynamic model
 Shows the sequence of messages that pass between objects
 Aid in understanding real-time specifications and complex use-
cases
 Generic diagram shows all scenarios for a use-case
 Instance diagrams show a single scenario
Sequence Diagram Syntax
More Sequence Diagram Syntax
Sample Sequence Diagram
Guidelines for Creating
Use-Case Diagrams
 Order messages from left to right, top to bottom
 Name actors and objects the same if they represent the same
idea
 Place the initiator of the scenario on the left of the diagram
 Multiple objects of the same class: name each
 Only show return values when they are not obvious
 Justify messages near the arrowhead for improved readability
Building Sequence Diagrams
• Set the context
• Identify actors and objects that interact in the use-case
scenario
• Set the lifeline for each object
• Add messages by drawing arrows
• Shows how they are passed from one object to another
• Include any parameters in parentheses
• Obvious return values are excluded
• Add execution occurrence to each object’s lifeline
• Validate the sequence diagram
• Ensures that it depicts all of the steps in the process
Communication Diagrams
 Depict the dependencies among the objects
 An object diagram that shows message passing relationships
 Emphasize the flow through a set of objects
Communication Diagram Syntax
Sample Communication Diagram
Guidelines for Creating
Communication Diagrams
 Use the diagram to identify the objects involved in a use-
case
 Do not use a communication diagram to model process flow
 Do not use a communication diagram to show message
sequence
Building Communication
Diagrams
 Set the context
 Identify objects, actors and associations between them
 Lay out the diagram
 Add the messages
 Validate the model
Behavioral State Machines
 Objects may change state in response to an event
 Different states are captured in this model
 Shows the different states through which a single object passes during
its life
 May include the object’s responses and actions
 Example: patient states
 New patient—has not yet been seen
 Current patient—is now receiving treatment
 Former patient—no longer being seen or treated
 Typically used only for complex objects
Components of
State Machines
 States—values of an object’s attributes at a point in time
 Events—the cause of the change in values of the object’s
attributes
 Transitions—movement of an object from one state to another
 May include a guard condition to flag that a condition is true and allow
the transition
State Machine Syntax
Sample State Machine
Guidelines for Creating
Behavioral State Machines
 Use only for complex objects
 Draw the initial state in the upper left corner
 Draw the final state in the bottom right corner
 Use simple, but descriptive names for states
 Look out for “black holes” and “miracles”
 Ensure guard conditions are mutually exclusive
 Ensure transitions are associated with messages and
operations
Building a
Behavioral State Machine
• Set the context
• Identify the states of the object
• Initial
• Final
• Stable states during its lifetime
• Lay out the diagram—use a left to right sequence
• Add the transitions
• Identify the triggers (events that cause the transition)
• Identify the actions which execute
• Identify the guard conditions
• Validate the model—ensure all states are reachable
CRUDE Analysis
 Helps to identify object collaborations
 Labels object interaction in 5 possible ways:
 Create—can one object create another?
 Read—can one object read the attributes of another?
 Update—can one object change values in another?
 Delete—can one object delete another object?
 Execute—can one object execute the operations of another?
 Utilizes a matrix to represent objects and their interactions
 Most useful as a system-wide representation
Sample CRUDE Matrix
Verifying & Validating
Behavioral Models
 Actors must be consistent between models
 Messages on sequence diagrams must match associations on
communication diagrams
 Every message on a sequence diagram must appear on an
association in a communication diagram
 Guard conditions on a sequence diagram must appear on a
communication diagram
 Sequence of messages must correspond to the top down ordering
of messages being sent
 State transitions must be associated with a message on a sequence
diagram
 Entries in a CRUDE matrix imply messages being sent
Summary
 Behavioral Models—provide a detailed view of how object
collaborations support use-cases
 Interaction Diagrams
 Sequence diagrams
 Communication diagrams
 Behavioral State Machines—depicts the states of complex
objects during its lifetime
 CRUDE Analysis—helps to identify potential collaborations
 Verifying & Validating behavioral models—ensures the
completeness and consistency of the models

You might also like