Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Chapter 7 System Models.
1 Copyright © 2013 Elsevier Inc. All rights reserved. Chapter 1 Embedded Computing.
0 - 0.
Addition Facts
State Diagram 1. State diagram: Shows the behavior of one object. They describe all of the possible states that a particular object can get into and how.
Requirements Diagrams With UML Models
NCKU EE RTES LAB.1 Unified Modeling Language - Events and State Machines.
State Charts Mehran Najafi. Reactive Systems A reactive, event-driven, object is one whose behavior is best characterized by its response to events dispatched.
Addition 1’s to 20.
Test B, 100 Subtraction Facts
Week 1.
UML State chart/machine diagram State machine diagram is a behavior diagram which shows discrete behavior of a part of designed system through finite state.
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
Object-oriented modeling Class/Object Diagrams
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
1 Chapter 4 Dynamic Modeling and Analysis (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis H.K. Tsang, Clarence.
1 CS 691z/791z Topics in Software Engineering Chapter 13: Activity Diagrams & Chapter 19: Basic Statecharts [Arlow and Neustadt, 2002] March 8, 2007.
1 © Wolfgang Pelz UML2 UML Part 3. 2 © Wolfgang Pelz UML2 Chapter Ten State Machine Diagrams.
1 CS/CPE 426 Senior Projects Chapter 21: State Machines Chapter 22:Advanced State Machines [Arlow and Neustadt 2005] March 24, 2009.
THE OBJECT-ORIENTED DESIGN WORKFLOW Statechart Diagrams.
Advanced Behavioral Modeling
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 10: Statecharts.
SE-565 Software System Requirements More UML Diagrams.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Lecture 4 Finite State Machine CS6133 Software Specification and Verification.
Chapter 10 State Machine Diagrams
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
Business Informatics Group Institute of Software Technology and Interactive Systems Vienna University of Technology Favoritenstraße 9-11/188-3, 1040 Vienna,
Object-Oriented Modeling Using UML CS 3331 Section 2.3 of Jia 2003.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Information System Design IT60105
Software Engineering Design & Modeling Statechart Diagram.
UML Discussion on State Machines Perfectly static system is intensely uninteresting Because nothing ever happens.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
OMT Modeling 1. Object Model : presented by the object model and the data dictionary. 2. Dynamic Model: presented by the state diagrams and event flow.
Systems Analysis and Design in a Changing World, Fourth Edition
States.
CS3773 Software Engineering Lecture 06 UML State Machines.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 10: Statecharts.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Modeling Object Lifecycles and State-Dependent Behavior ©SoftMoore ConsultingSlide 1.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Procedural Activity Patrick Bailey Keith Vander Linden Calvin College.
® IBM Software Group © 2009 IBM Corporation Module 11: Creating State Machine Diagrams Essentials of Modeling with IBM Rational Software Architect V7.5.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Advanced UML State Diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
UML Chapter 17.
UML StateChart Diagrams
State Machine Diagrams
Business System Development
UML Activity Diagrams & State Charts
UML State machine diagram
System models October 5, 2005.
States.
Object Oriented System Design
CS/CPE 426 Senior Projects
Advanced State Chart diagrams
CS/CPE 426 Senior Projects
Dynamic Modeling Lecture # 37.
States.
CS 791Z State Machines & Advanced State Machines
UML State Diagrams.
Appendix 3 Object-Oriented Analysis and Design
Behavioral Diagrams P. P. Mahale
Presentation transcript:

Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”

 Dynamic view – statechart diagrams ◦ role ◦ basic concepts ◦ advanced concepts ◦ examples 2

 Statechart diagram, also called state machine, is one of the five UML diagrams used to model dynamic nature of a system. It defines different states of an object during its lifetime and these states are changed by events.  Statechart diagram describes the flow of control from one state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered  Statechart diagrams are useful to model reactive systems. Reactive system can be defined as a system that responds to external or internal events. 3

 State - is a circumstance in which an object is situated in its life cycle, when it meets a certain condition, performs an operation or waits for an event to occur.  Transition is a relationship between two states, indicating that the object being in the first state will perform certain actions and move to the other state, whenever a specific event occurs and certain conditions are met.  Initial state is the initiation of the statechart diagram  Final state is the termination of the statechart diagram 4

5 Initial state Final state State Transition

Sections of graphical symbol of state:  name section – place for the state name  internal operations section - lists the internal operations performed when an object achieves a certain state. Type of the internal operation is identified by one of the keywords: ◦ entry - an operation automatically performed on the object the moment it achieves the state (there may be only one within a state), ◦ exit - operation performed when an object leaves the state (there may be only one within a state), ◦ do - operation performed continuously on the object being in a given state (there can be many such operation within a state) 6

Sections of graphical symbol of state:  internal transitions section - indicates specific cases of transitions, execution of which does not lead to a change of state. Internal transitions do not have their own graphical symbol but are specified in the state area  decomposition section – informs about decomposition of the state into sub-states 7

8 Internal operations section Name section Decomposition section

Classification of states:  Simple state - a state that does not contain any sub-states or orthogonal regions  Composite state - a state, which contains either sub-states or is divided into orthogonal regions  Sub-state – a state machine into which a composite state is decomposed (a sub-state can be either direct or indirect depending on the level of decomposition) 9

10 Substate of the decomposed composite state ‘Received’

 Orthogonal region – concept used for showing states and transitions within in a composite state, which are activated concurrently. Transitions can cross composite states boundaries. All orthogonal regions must be realized in order for the state to be completed.  Pseudo-state is an abstract category of statechart diagram modeling, which allows for organizing complex transitions by the use of fork node, join node, junction, decision node, termination, etc. 11

12 Pseudo-state (junction point)

13 Orthogonal region

Transition types:  simple - occurring between the source and target state,  return - where the source and target states are the same state,  internal – constituting one of the elements of a state,  local - indicating transitions between any sub-states of a composite state,  external - leaving a composite state and directed to another state or pseudo-state,  high level or group - leaving composite states and indicating the necessity of leaving all sub-states of this composite state before transition,  complex – chain of transitions joined or forked, linked by a junction or decision node,  automatic – without any associated event or condition. 14

Types of state machines:  Protocol state machines- concentrate on a specific object and present available and permitted transitions between the states of this object  Behavioral state machines- present transitions between states of many objects in a wider context of system, subsystem or use case behavior 15

 Events - stimuli sent by objects, which initiate transitions from one state to another  There are five types of events: ◦ signal – asynchronous stimulus transmitted between two objects (e.g. signal from a sensor), ◦ call event – calling operations of one object by another object (e.g. login, register), ◦ time event – event, which occurs after a certain period of time (e.g. after (3 hrs.)), ◦ status change event – event, which occurs at a certain point of time (e.g. when (date = 1 July) ◦ deferred event – event, which is not supported within a given state but added to the deferred events queue (e.g. summary of Receivables /defer) 16

17

18  Determination of the type of created state machine and identification of objects  Identification of possible states of a state machine  Determination of the hierarchy of states, sub- states and orthogonal regions  Linking the states and their sub-states with transitions  Application of adequate pseudo-states