theoretical foundations of the uml
play

Theoretical Foundations of the UML Lecture 17: Introduction to - PowerPoint PPT Presentation

Theoretical Foundations of the UML Lecture 17: Introduction to Statecharts Joost-Pieter Katoen Lehrstuhl fr Informatik 2 Software Modeling and Verification Group moves.rwth-aachen.de/teaching/ss-20/fuml/ June 22, 2020 Joost-Pieter Katoen


  1. Theoretical Foundations of the UML Lecture 17: Introduction to Statecharts Joost-Pieter Katoen Lehrstuhl für Informatik 2 Software Modeling and Verification Group moves.rwth-aachen.de/teaching/ss-20/fuml/ June 22, 2020 Joost-Pieter Katoen Theoretical Foundations of the UML 1/34

  2. Outline Background 1 Ingredients of Statecharts 2 Mealy Machines State Hierarchy Orthogonality Broadcast Communication Some Small Examples Priority and Nondeterminism Semantics of Statecharts 3 Formal Definition of UML Statecharts 4 Joost-Pieter Katoen Theoretical Foundations of the UML 2/34

  3. Overview Background 1 Ingredients of Statecharts 2 Mealy Machines State Hierarchy Orthogonality Broadcast Communication Some Small Examples Priority and Nondeterminism Semantics of Statecharts 3 Formal Definition of UML Statecharts 4 Joost-Pieter Katoen Theoretical Foundations of the UML 3/34

  4. Statecharts MSCs are a visual modelling formalism for requirements Statecharts is a visual modelling formalism for describing the behaviour of discrete-event systems automata + hierarchy + communication + concurrency =/ CFM Joost-Pieter Katoen Theoretical Foundations of the UML 4/34

  5. Statecharts MSCs are a visual modelling formalism for requirements Statecharts is a visual modelling formalism for describing the behaviour of discrete-event systems automata + hierarchy + communication + concurrency Developed by David Harel in 1987 professor at Weizmann Institute (Israel); co-founder of I-Logix Inc. Extensively used in embedded systems, automotive and avionics Variants: UML Statecharts, Stateflow, hierarchical state machines supported by Statemate toolset, and Matlab/Simulink Joost-Pieter Katoen Theoretical Foundations of the UML 4/34

  6. Overview Background 1 Ingredients of Statecharts 2 Mealy Machines automata = State Hierarchy Orthogonality Broadcast Communication Some Small Examples Priority and Nondeterminism Semantics of Statecharts 3 Formal Definition of UML Statecharts 4 Joost-Pieter Katoen Theoretical Foundations of the UML 5/34

  7. What are Statecharts? Statecharts constitute a visual formalism for: [Harel, 1987] Describing states and transitions in a modular way reflects the system architecture Joost-Pieter Katoen Theoretical Foundations of the UML 6/34

  8. What are Statecharts? Statecharts constitute a visual formalism for: [Harel, 1987] Describing states and transitions in a modular way ← ¥! Enabling clustering of states Joost-Pieter Katoen Theoretical Foundations of the UML 6/34

  9. What are Statecharts? Statecharts constitute a visual formalism for: [Harel, 1987] Describing states and transitions in a modular way Enabling clustering of states Orthogonality, i.e., concurrency Refinement, and Joost-Pieter Katoen Theoretical Foundations of the UML 6/34

  10. What are Statecharts? Statecharts constitute a visual formalism for: [Harel, 1987] Describing states and transitions in a modular way Enabling clustering of states Orthogonality, i.e., concurrency Refinement, and Encouraging “zoom“ capabilities for moving easily back and forth between levels of abstraction Joost-Pieter Katoen Theoretical Foundations of the UML 6/34

  11. What are Statecharts? Statecharts := Mealy machines + State hierarchy + Broadcast communication + Orthogonality Joost-Pieter Katoen Theoretical Foundations of the UML 7/34

  12. Mealy machines [Mealy, 1953] Definition (Mealy machine) A Mealy machine A = ( Q, q 0 , Σ , Γ , δ , ω ) with: Q is a finite set of states with initial state q 0 ∈ Q Σ is the input alphabet Γ is the output alphabet δ : Q × Σ → Q is the deterministic (input) transition function, and ω : Q × Σ → Γ is the output function accept St te no - output but has - Joost-Pieter Katoen Theoretical Foundations of the UML 8/34

  13. Mealy machines [Mealy, 1953] Definition (Mealy machine) A Mealy machine A = ( Q, q 0 , Σ , Γ , δ , ω ) with: Q is a finite set of states with initial state q 0 ∈ Q Σ is the input alphabet Γ is the output alphabet δ : Q × Σ → Q is the deterministic (input) transition function, and ω : Q × Σ → Γ is the output function Intuition A Mealy machine (or: finite-state transducer) is a finite-state automaton that produces output on a transition, based on current input and state. Joost-Pieter Katoen Theoretical Foundations of the UML 8/34

  14. Mealy machines [Mealy, 1953] Definition (Mealy machine) A Mealy machine A = ( Q, q 0 , Σ , Γ , δ , ω ) with: Q is a finite set of states with initial state q 0 ∈ Q Σ is the input alphabet Γ is the output alphabet δ : Q × Σ → Q is the deterministic (input) transition function, and ω : Q × Σ → Γ is the output function Intuition A Mealy machine (or: finite-state transducer) is a finite-state automaton that produces output on a transition, based on current input and state. Moore machines In a Moore machine ω : Q → Γ , output is purely state-based. Joost-Pieter Katoen Theoretical Foundations of the UML 8/34

  15. Mealy machines Mealy machines No final (accepting) states Transitions produce output Deterministic input transition function ⇒ Acceptance of input words is not important, but the generation of output words from input words is important Example In in . I a o ) w fr , ° Joost-Pieter Katoen Theoretical Foundations of the UML 9/34

  16. Limitations of Mealy machines No support for hierarchy all states are arranged in a flat fashion no notion of substates Realistic systems require complex transition structure and huge number of states scalability problems yields unstructured state diagrams No notion of concurrency need for modeling independent components No notion of communication between automata. Joost-Pieter Katoen Theoretical Foundations of the UML 10/34

  17. Scalability A bit unstructured Mealy machine An equivalent statechart Joost-Pieter Katoen Theoretical Foundations of the UML 11/34

  18. Scalability A bit unstructured Mealy machine An equivalent statechart State hierarchy yields modular, hierarchical and structured models. Joost-Pieter Katoen Theoretical Foundations of the UML 11/34

  19. Orthogonality Two independent components parallel composition f Mealy machine for Image | | Sound - → Number of states is exponential in size of concurrent components Joost-Pieter Katoen Theoretical Foundations of the UML 12/34

  20. Orthogonality Two independent components Statechart for Image | | Sound I I Concurrency modeled by independence Joost-Pieter Katoen Theoretical Foundations of the UML 13/34

  21. Combined with state hierarchy Switching on and o ff the television 4 I 0 Joost-Pieter Katoen Theoretical Foundations of the UML 14/34

  22. Broadcast Turn o ff sound on switching a tv channe - • Output is broadcast that can be received by any other component When pushing button 1, channel switches to its state channel 1, while generating signal sm on which component SM switches o ff the sound. Joost-Pieter Katoen Theoretical Foundations of the UML 15/34

  23. Concurrency Example concurrency in statecharts Active As long as node X is active, nodes S and T are active Node S is active when either node A or B is active Node T is active if one of C, D or E is active Joost-Pieter Katoen Theoretical Foundations of the UML 16/34

  24. Concurrency Example concurrency in statecharts Exit behaviour When node X exits, both nodes S and T exit When Y exits, X starts, S starts in A , and T starts in C On the occurrence of event e , node X exits (regardless of current state in S or T ) Joost-Pieter Katoen Theoretical Foundations of the UML 17/34

  25. Swapping two variables Swapping the value of variables x and y If nodes A and C are active, assume x = 1 , y = 2 On occurrence of event e , B and D are active, and x = 2 , y = 1 ⇒ In Harel’s statecharts, memory is shared, i.e., concurrent components have access to shared variables. Joost-Pieter Katoen Theoretical Foundations of the UML 18/34

  26. Priority What if event e occurs when A and C are active? Co ] - so go Solution: Add a priority mechanism that decides whether: inter-level transitions (such as C → E ), or intra-level transitions (such as A → B ) prevail in case both are enabled. Joost-Pieter Katoen Theoretical Foundations of the UML 19/34

  27. Nondeterminism What if event e and e ′ occur in A ? Solution: Choice is resolved nondeterministically, i.e., the next state is either B or C , but not both. Joost-Pieter Katoen Theoretical Foundations of the UML 20/34

  28. Overview Background 1 Ingredients of Statecharts 2 Mealy Machines State Hierarchy Orthogonality Broadcast Communication Some Small Examples Priority and Nondeterminism Semantics of Statecharts 3 Formal Definition of UML Statecharts 4 Joost-Pieter Katoen Theoretical Foundations of the UML 21/34

  29. Semantic problems with Statecharts Synchrony hypothesis (or: zero response time) Self-triggering Transition e ff ect is contradicting its cause Note: [von der Beeck, 1994] Due to all these problems, hundred(s) (!) of di ff erent semantics for Statecharts have been defined in the literature. Joost-Pieter Katoen Theoretical Foundations of the UML 22/34

  30. Synchrony hypothesis Event may yield chain of reactions I =\ = • 0 o Note: O If A 1 , B 1 and C 1 are active and event a occurs, a chain of reactions occurs: transition t 1 triggers t 2 , and t 2 triggers t 3 Joost-Pieter Katoen Theoretical Foundations of the UML 23/34

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend