Finite State History Modeling and Its Precise UML-Based Semantics

  • Dirk Draheim
  • Gerald Weber
  • Christof Lutteroth
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4231)


This paper discusses the notion of a state history diagram. The concept is directly motivated by a new analysis technique, form-oriented analysis, which is tailored to an important class of interactive systems including web applications. A combined UML metamodeling and framework approach is used to give precise semantics to state history diagrams and the artifacts of form-oriented analysis.


State Machine Class Diagram Operational Semantic State History State Transition Diagram 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Atkinson, C., Kühne, T.: Strict profiles: Why and how. In: Evans, A., Kent, S., Selic, B. (eds.) UML 2000. LNCS, vol. 1939, pp. 309–322. Springer, Heidelberg (2000)Google Scholar
  2. 2.
    Atkinson, C., Kühne, T.: The Essence of Multilevel Metamodeling. In: Gogolla, M., Kobryn, C. (eds.) UML 2001. LNCS, vol. 2185, pp. 19–33. Springer, Heidelberg (2001)CrossRefGoogle Scholar
  3. 3.
    Draheim, D., Weber, G.: Form-Oriented Analysis - A New Methodology to Model Form-Based Applications. Springer, Heidelberg (2005)MATHGoogle Scholar
  4. 4.
    Draheim, D., Weber, G.: Modelling Form-Based Interfaces with Bipartite State Machines. Journal Interacting with Computers 17(2), 207–228 (2005)CrossRefGoogle Scholar
  5. 5.
    Gamma, E., et al.: Design Patterns. Addison-Wesley, Reading (1995)Google Scholar
  6. 6.
    Harel, D.: Statecharts: a Visual Formalism for Complex Systems. In: Science of Computer Programming, pp. 231–274. Elsevier Science Publishers B.V., Amsterdam (1987)Google Scholar
  7. 7.
    Harel, D., Naamad, A.: The Statemate Semantics of Statecharts. ACM Transactions on Software Engineering and Methodology 5(4), 293–333 (1996)CrossRefGoogle Scholar
  8. 8.
    IEEE Std 830-1993. Recommended Practice for Software Requirements Specifications. Software Engineering Standards Committee of the IEEE Computer Society, New York (1993)Google Scholar
  9. 9.
    Warmer, J., Kleppe, A.: The Object Constraint Language. Addison-Wesley, Reading (1999)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Dirk Draheim
    • 1
  • Gerald Weber
    • 2
  • Christof Lutteroth
    • 2
  1. 1.Institute of Computer Science, A5-6University of MannheimMannheimGermany
  2. 2.Department of Computer ScienceThe University of AucklandAucklandNew Zealand

Personalised recommendations