View
215
Download
1
Category
Preview:
Citation preview
Behavioral Modeling: State Diagrams
CIS 4800Kannan Mohan
Department of CISZicklin School of Business, Baruch College
Copyright © 2009 John Wiley & Sons, Inc.Copyright © 2005 Pearson EducationCopyright © 2009 Kannan Mohan
Learning Objectives
• Explain how statecharts can be used to describe system behaviors
• Use statecharts to model object and system behaviors
• Explain how state charts are different from other diagrams that we have seen so far
Analysis and Design so far…• Use case diagrams– What? Shows functionalities of the system that provides
measurable value to actors
– Why? Must understand functionality of the system from the perspective of one or more actors that interact with the system
• Class diagrams – What? Shows elements in the system, static structure,
things and relations
– Why? Must represent elements that are to be remembered by the system; Used to understand the system structure; Interaction of classes fulfill functionalities
Analysis and Design so far…• Interaction diagrams (Sequence and communication) – What? Represents sequence of interactions among a set of
objects
– Why? Must capture interactions among objects in a chronological order – this represents how a use case is executed in a particular scenario; Use case realization
• State diagrams– What? Show the possible interesting states that objects of a
class can have and the events that cause the transitions to and from those states
– Why? Must capture ‘temporal’ evolution of an object in response to interactions
State Diagrams
• A dynamic model that shows the different states through which a single object passes during its life in response to events, along with its responses and actions
• Typically not used for all objects– Just for complex ones
• Does an object behave differently to stimuli from environment and other objects when it is in different states?
Simple Statechart for a Printer
Sample State Diagram for Patient Class
Parts of a State Chart
• Pseudo state – starting point of a statechart
• State – condition that occurs during an object’s life when it satisfies some criteria, performs some action, or waits for an event
• Transition – movement of object from one state to another state
• Message event – trigger for the transition
Vending Machine Example
Seminar
State Details• Based on attribute values
• Specifies the response of an object to input events– Response qualitatively different in different states
– E.g.: Solvent customer places order
State Details• Response to input events may be an
action or change of state–E.g.: Place order, become insolvent
• Often associated with value of an object satisfying some condition–Customer credit limit balance – change in
the value of this attribute might dictate state of solvency
State Transition Details• If an event occurs, the transition is fired
• A transition can lead to the same state
• A state transition may have an action and/or a guard condition associated with it
• An ACTION is behavior that occurs when the state transition occurs
• A GUARD CONDITION is a Boolean expression of attribute values that allows a state transition only if the condition is true
Concurrency• Concurrency – condition of being in more than one
state at a time
• Objects in a system are inherently concurrent
• Concurrency within an object can be represented by multiple subsets of states, each with their own initial state
• Differentiated by different state variables
Concurrent States for a Printer in the On State
Nested States• Composite states – state containing
multiple levels and transitions–Can contain nested states and transition paths
Developing State charts
• Review class diagram and select classes that require statecharts
• For each selected class in group, brainstorm to list all status conditions you can identify
• Begin building statechart fragments by identifying transitions that cause object to leave identifying state
• Sequence these state-transition combinations in correct order
Developing State charts (contd.)
• Review paths and look for independent, concurrent paths
• Look for additional transitions– Take every pairwise combination of states and
look for valid transition between states
• Expand each transition with the appropriate message event, guard-condition, and action-expression
• Review and test each statechart
Summary• What is the purpose of state diagrams?
• Develop state diagrams for specific classes in a given case.
• What are concurrent and nested state diagrams?
• What are the relationships between the diagrams that we have seen so far?– For example, how is a transition in a state chart
related to a message in a sequence diagram?
Recommended