[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)

Harel01

  1. David Harel
  2. From play-in scenarios to code: Achievable Dream
  3. IEEE Computer Magazine V34n1(Jan 2001)pp53-60
  4. =IDEAs USER REQUIREMENTS PURPOSE SAFETY LIVENESS MODEL DESIGN TEST REACTIVE TOOLS Rhapsody Statecharts MSC LSCs XUML
  5. p54 Sidebar: HISTORY SA/SD
  6. p55 Sidebar: HISTORY OOAD
  7. See [HarelGery97] [Harel92] etc..
  8. Also compare [UchitalKramerMagee02]
  9. Users play with a system that models structure and teaches it the correct behaviors. These are represented internally by hidden formal models ( LSCs) and then super-compiled into the working code with links back to model and requirements.
  10. Sequence charts model requirements but statecharts model the system..
  11. play_in_scenario := simulated system with GUI that lets user play with scenarios and teach both good and bad ones.
  12. anti_scenarios := Things that must not happen.
  13. XUML := eXecutable UML, class diagrams+State charts.
  14. MSC := Message Sequence Chart, telecommunications standard, states what might happen but does not state what must and what must not happen.
  15. LSC::= Live Sequence charts, show possible and necessary sequences, can express both liveness and safety requirements, hot and cold elements.
  16. hot_condition in LSC := when part of scenario is entered the condition has to be true, or the system has failed catastrophically.
  17. cold_condition in LSC = when part of scenario is entered the condition has to be true, or the chart will terminate or exit to a higher level.
  18. inter-object vs intra-object models.

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.



To see the complete bibliography (1Mb+) select:[Bibliography]