UML Statechart semantics Speaker: Fei Mo Tutor: Priv.-Doz. Dr. Thomas Noll Lehrstuhl für Informatik 2 RWTH Aachen SS 07.

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

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.
State Charts Mehran Najafi. Reactive Systems A reactive, event-driven, object is one whose behavior is best characterized by its response to events dispatched.
Behavioral Modeling: State Diagrams CIS 4800 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College Copyright © 2009 John Wiley & Sons,
Statecharts Semantics
Vered Gafni – Formal Development of Real Time Systems 1 Statecharts Semantics.
Week 6Fall 2001 CS5991 The STATEMATE Semantics of Statecharts D. Harel and A. Naamand Ahmad Alsawi 1-4 Bob Chen 5-8 Dapeng Xie 9-11.
CS 290C: Formal Models for Web Software Lecture 4: Implementing and Verifying Statecharts Specifications Using the Spin Model Checker Instructor: Tevfik.
ESE Einführung in Software Engineering 7. Modeling Behaviour Prof. O. Nierstrasz.
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
Introduction to Software Engineering 7. Modeling Behaviour.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Slide 6B.1 Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction to Object-Oriented Systems Analysis and Design with.
CS 425/625 Software Engineering System Models
Statecharts: A Visual Formalism for Complex Systems Jeff Peng Model-based Design Lab.
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.
CS 290C: Formal Models for Web Software Lecture 2: Modeling States with Statecharts Instructor: Tevfik Bultan.
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.
An Introduction to Rational Rose Real-Time
Unified Modeling Language
Lecture 6 Template Semantics CS6133 Fall 2011 Software Specification and Verification.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Ch.2 Part A: Requirements, State Charts EECE **** Embedded System Design.
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.
NJIT Modeling Behavior in State Chart Diagrams Chapter 29 Rafael Mello.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Systems Analysis and Design in a Changing World, Fifth Edition
Guide to State Transition Diagram. 2 Contents  What is state transition diagram?  When is state transition diagram used?  What are state transition.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
StateCharts Peter Marwedel Informatik 12 Univ. Dortmund Germany.
Ch. 2. Specification and Modeling 2.1 Requirements Describe requirements and approaches for specifying and modeling embedded systems. Specification for.
Session 22 Modeling the Extended Features of the Statechart Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 27, 2011 Presented.
7 Systems Analysis and Design in a Changing World, Fifth Edition.
Information System Design IT60105
1 Kyung Hee University Statecharts Spring Kyung Hee University Specifying Objects’ Behaviour  Interaction diagrams show message-passing behaviour.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part VI: Design Continuous Activity Diagams State Diagrams.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML State Diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
States.
CS3773 Software Engineering Lecture 06 UML State Machines.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 26. Review UML behavioral Diagrams – Sequence diagram.
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.
MCS 270 Spring 2014 Object-Oriented Software Development.
Chapter 3: Introducing the UML
Modeling Object Lifecycles and State-Dependent Behavior ©SoftMoore ConsultingSlide 1.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Test Generation from UML Specifications Michael A. Gray American University Washington, DC.
1 IS 0020 Program Design and Software Tools Unified Modeling Language Lecture 13 April 13, 2005.
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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Advanced UML State Diagrams.
Systems Analysis and Design in a Changing World, Fourth Edition
Evolution of UML.
Object-Oriented Analysis and Design
State Machine Diagrams
Business System Development
UML Activity Diagrams & State Charts
States.
Object Oriented System Design
SS 2018 Software Verification ML, state machines
Chapter 20 Object-Oriented Analysis and Design
Dynamic Modeling Lecture # 37.
States.
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

UML Statechart semantics Speaker: Fei Mo Tutor: Priv.-Doz. Dr. Thomas Noll Lehrstuhl für Informatik 2 RWTH Aachen SS 07

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

Introduction formulate the semantics of UML Statechart We show how the Extended hierarchical Automata represent statecharts We show the Statechart in STATEMATE

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

Fundamentals Hierarchy Humans not capable to understand systems containing more than ~5 objects. Most actual systems require more objects Behavioral hierarchy Structural hierarchy Timing behavior.

Introducing hierarchy super-state S sub-states

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

Semantik of UML Statechart State a condition during the life of an object or an interaction Simple State rectangle with rounded corners The name tab The action label entry exit do include

Composite State State Composite State

Composite states – concurrent substates - using -and- relationship each substate separated from others by dotted line – disjoint substates - using -or- relationship transitions between substates Example of concurrent substates

Configuration A maximum set of states (C) that the system can be simultaneously in C contains root state If C contains OR-state A, it must contain only one of A’s substates If C contains AND-state A, it must contain all of A’s substates Basic configuration is a maximal set of basic states that the system can be in simultaneously Subconfiguration

Semantik of UML Statechart Event Triggers the transition Can be either internally or externally generated Conditions: Guards the transition from being taken unless it is true when event occurs

Semantik of UML Statechart Transition Simple transition a relationship between two states source state of t1 is a directly or transitively nested substate of the source state of t2 -> t1 is higher than t2 Start and end transitions

Semantik of UML Statechart Transition The exact sequence of actions first: the exit actions of all states left by the transition are executed starting the deepest one in the hierarchy next: the action associated to the transition is performed finally: the entry actions of states entered by the transition starting with the highest one in the hierarchy

Semantik of UML Statechart Transition Transitions to and from Concurrent States multiple source states and target states

Semantik of UML Statechart example s0 refined: s1, s2, and s3 composite state: s0, s1, s4 s5; concurrent state: s1 Configurations "System states“: {s1; s6; s8}; {s2}; {s3} Transition fire: source state is in the current configuration trigger is offered by the external environment the guard is satisfied

Semantik of UML Statechart Initial subconfiguration {n8, n6} – b -> t6; next subconfiguration: {n5, n6}; sequence – a -> t3, t2; {n9, n7}; ; if s8 active: no t1 (s8 lower than s4) – e ∈ Π\{a, b}, No transtion, configuration does not change

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

Extended hierarchical Automata Definition Sequential Automaton A sequential automaton A is a 4-tuple is a finite set of states is the initial state is a finite set of transition labels (labels have a particular structure) is the transition relation

Extended hierarchical Automata Definition Extended hierarchical Automata An EHA consists of a set of sequential automata An EHA is a 5-tuple F is a finite set of sequential automaton E is a finite set of events V is the set of variables ρ is refinement function

Extended hierarchical Automata UML Statechart example

Extended hierarchical Automata Extended hierarchical Automata example Extended Hierarchical Automata can represent statecharts

Extended hierarchical Automata the refinement function ρ; ρ(S) = {TV, USER}, ρ(OFF) = {POWER}, ρ(ON) = {IMAGE,SOUND} ρ(s) = ∅ for any other state s in EHA: dotted arrows. Initial states: indicated by thick boxes. Non-inter-level transitions: represented in the obvious way.

Extended hierarchical Automata The source restriction of transition on: STB Join transitions: a set of states target determinator (TD) transition from ON to STB -> off 1 TD of the transition off1: {STB}; TD of the transition on: {SHW, SND}.

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

Statechart with STATEMATE STATEMATE system structurefunctionAction Module-charts Activity-charts Statecharts

Statechart with STATEMATE In Conf. {S,S1,A,B,D,E} Event a trigers a/b Event b trigers b/c? what with Event d?

Contents Introduction Fundamentals Semantik of UML Statechart Extended Hierarchical Automata Statechart with STATEMATE Summary

UML Statechart Semantics Can describe the behavior of instances of a model element. Describe sequences of states (rounded boxes) and transitions (arrows). Can describe behavior of use cases and subsystems. Extended Hierarchical Automata can represent statecharts Can be used in STATEMATE to descript separated actions as a more universal design methodology

References [1] Unified Modeling Language Document Set. Version1. 1, Rational Software Corporation, [2] OMG Unified Modeling Language Specification, version 2.1.1, Object Management Group, Inc., [3] Mikk E, Lakhnech Y, Petersohn C, Siegel M. On formal semantics of Statecharts as supported by STATEMATE. In: Duke D, 1997 [4] Evans A, eds. Proceedings of the 2nd BCS-FACS Northern Formal Methods Workshop. London: Springer-Verlag, [5] Harel D, Naamad A. The STATEMATE semantics of statecharts[J]. ACM Transactions on Software Engineering and Methodology, 1996.

Thanks!