State transition modeling

Slides:



Advertisements
Similar presentations
UML: The Unified Modeling Language Excertos do livro: The Unified Modelling Language User Guide by Grady Booch, James Rumbaugh and Ivar Jacobson.
Advertisements

NCKU EE RTES LAB.1 Unified Modeling Language - Events and State Machines.
Concepts & Notations. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
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.
ESE Einführung in Software Engineering 7. Modeling Behaviour Prof. O. Nierstrasz.
Introduction to Software Engineering 7. Modeling Behaviour.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
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.
Unified Modeling Language Unit 4. Dynamic Modeling.
March R. McFadyen1 Statechart Diagram A Statechart Diagram describes states for an object how/why an objects’ state changes A Statechart Diagram.
THE OBJECT-ORIENTED DESIGN WORKFLOW Statechart Diagrams.
State Change Modelling. Aim: To introduce the concept and techniques for describing the changes in state that may occur to an object in its lifetime.
Nov 2002 R. McFadyen1 Statechart Diagrams - Ch 29 Example: Suppose we have a class Copy, representing copies of books. We can consider two states:
UML Notations Activity diagrams State diagrams Class diagrams Use-case diagrams.
Advanced Behavioral Modeling
CS451 Introduction to Software Engineering Behavioral Modeling.
Lecture 4 Finite State Machine CS6133 Software Specification and Verification.
Timed UML State Machines Ognyana Hristova Tutor: Priv.-Doz. Dr. Thomas Noll June, 2007.
Chapter 10 State Machine Diagrams
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
State diagrams Interaction diagrams –Sequence diagrams –Collaboration diagrams Object orientation Part 4: Dynamic Modeling.
1 Software Engineering Dr. K. T. Tsang Lecture 8 State modeling
Behavioral diagrams Lecture p4 T120B pavasario sem.
Object-Oriented Modeling Using UML CS 3331 Section 2.3 of Jia 2003.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
Sequence & Statechart Diagrams Month Day, Year. Agenda Training Plan Overview Actors and Use Case Diagrams Sequence Diagrams Diagram Elements Evolution.
1 A Student Guide to Object- Oriented Development Chapter 7 State Diagrams.
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 state charts 1 object states an object state is a condition or situation during the life.
Software Engineering Design & Modeling Statechart Diagram.
1 Kyung Hee University Statecharts Spring Kyung Hee University Specifying Objects’ Behaviour  Interaction diagrams show message-passing behaviour.
UML Discussion on State Machines Perfectly static system is intensely uninteresting Because nothing ever happens.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 19 – Activity Diagrams.
Dynamic Models. Outline Dynamic Models Statecharts –States –Transitions –Composite states Interaction Diagrams –Sequence Diagrams The time order of interactions.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
State Modeling. Introduction A state model describes the sequences of operations that occur in response to external stimuli. As opposed to what the operations.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
UML: The Unified Modeling Language Excertos do livro: The Unified Modelling Language User Guide by Grady Booch, James Rumbaugh and Ivar Jacobson.
States.
CS3773 Software Engineering Lecture 06 UML State Machines.
Dynamic Modeling Grady Booch, James Rumbaugh, and Ivar Jacobson, The Unified Modeling Language User Guide, 2 nd edition, Addison Wesley, 2005.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 26. Review UML behavioral Diagrams – Sequence diagram.
MCS 270 Spring 2014 Object-Oriented Software Development.
Modeling Object Lifecycles and State-Dependent Behavior ©SoftMoore ConsultingSlide 1.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
State Modeling. Introduction A state model describes the sequences of operations that occur in response to external stimuli. As opposed to what the operations.
® IBM Software Group © 2009 IBM Corporation Module 11: Creating State Machine Diagrams Essentials of Modeling with IBM Rational Software Architect V7.5.
UML Review: State Machines. Sept. 17, 2003Lecture 5: CS660 Fall Overview States Transitions Activities Modeling object lifeline Creating well-structured.
Embedded Systems Software Engineering
Modeling with UML – Class Diagrams
Activity Diagram.
Embedded Systems Software Engineering
UML Chapter 17.
Passing from design to implementation
State Machine Model.
State Diagram – Advanced Concepts
Marlon Dumas Institute of Computer Science
Object-Oriented Static Modeling of the Banking System - I
Activity and State Transition Diagram
State Machine Diagrams
CSC 422 Kutztown University Dr. Spiegel
UML State machine diagram
States.
Object Oriented System Design
Activity Diagrams.
Dynamic Modeling Lecture # 37.
Marlon Dumas Institute of Computer Science
States.
CHAPTER 2 Object-Oriented Modeling Using UML (Continued)
UML State Diagrams.
Presentation transcript:

State transition modeling Jarosław Kuchta Embedded Systems Software Engineering State transition modeling GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Basic concepts (1) state – a situation during an object life time, when it satisfies some condition, performs some activity, or waits for some event event – occurring of some situation which is important in some context; time of an event is atomic GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Basic concepts (2) action – an atomic operation execution; atomic in the current time scale activity – operation executed by an object staying in some state until it is interrupted by an event GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Basic concepts (3) state transition – a relationship between two states of an object; the object in the first state will perform certain actions and enter the second state when a specified event occurs and specified conditions are satisfied state machine – an abstract machine performing object state transitions on events; represented by state transition diagram GUT - INTEL 2015/16 Embedded Systems Software Engineering

State transition diagram event state transition Switch On ● Off On initial state Shut down state Switch off ◉ final state GUT - INTEL 2015/16 Embedded Systems Software Engineering

State transition signature event [guard condition] / action expression GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Event categories Call event Signal event Change event Time event GUT - INTEL 2015/16 Embedded Systems Software Engineering

Call event operation name (parameter list) An event occurring when an operation should be performed operation name (parameter list) GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Signal event «signal» Mouse pos: Point «signal» «signal» «signal» «signal» MouseDown MouseUp MouseMove MouseRoll btn: Button btn: Button dist: Point GUT - INTEL 2015/16 Embedded Systems Software Engineering

Change event An event occurring when some condition is satisfied when condition expression GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Time event An event occurring: after some time interval after time expression in some time moment when time expression GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Guard condition Boolean expression containing: triggered event parameters object properties and states when an object is in some state (in state name) Guard condition is checked after triggering an event, and before firing a state transition GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Action expression A sequence of operation calls sequentially executed Operations are separated with semicolons Operations arguments can use triggered event parameters GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Transition example MouseDown (btn, loc) [loc in Window] / object := Window.FindObject (loc); object.Select () GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Entry & exit actions Data maintenance entry / connect to data base exit / disconnect data base do/ check unused records include / internal state machine get progress / display progress GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Compound states Sequential substates Concurrent substates GUT - INTEL 2015/16 Embedded Systems Software Engineering

Sequential and concurrent substates Diagnostics Diagnosing ● ◉ Diagnosing Circuit 1 Pass Diagnosing Circuit 2 Pass ● Passed Fail Fail ● ◉ Diagnosing Circuit 3 Pass Diagnosing Circuit 4 Pass Failed Fail Fail GUT - INTEL 2015/16 Embedded Systems Software Engineering

Concurrent states synchronization State A1 State A2 Initialization Finalization State B1 State B2 Synchronization bar GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Activity diagram A special state transition diagram when: state nodes represent actions or sub-activities state transitions are fired just after the preceding activities are finished GUT - INTEL 2015/16 Embedded Systems Software Engineering

Activity diagram example [operation = get balance] ● Authorization Choose operation Display balance [operation = withdraw] [operation = exit] Entering amount ◉ Check balance [balance positive] [balance negative] Counting money Preparing check Taking money GUT - INTEL 2015/16 Embedded Systems Software Engineering

Concurrent activities Object 1 Object 2 Object 3 Initialization Activity A1 Activity B1 Activity C1 Activity A2 Activity C2 Finalization “swimlines" GUT - INTEL 2015/16 Embedded Systems Software Engineering

Embedded Systems Software Engineering Bibliography Grady Booch, James Rumbaugh, Ivar Jacobson: Unified Modeling User Guide (book, PDF) GUT - INTEL 2015/16 Embedded Systems Software Engineering