[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- David Harel
- From play-in scenarios to code: Achievable Dream
- IEEE Computer Magazine V34n1(Jan 2001)pp53-60
- =IDEAs USER REQUIREMENTS PURPOSE SAFETY LIVENESS MODEL DESIGN TEST REACTIVE TOOLS
Rhapsody Statecharts MSC LSCs XUML
- p54 Sidebar: HISTORY SA/SD
- p55 Sidebar: HISTORY OOAD
- Also compare
- 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.
- Sequence charts model requirements but statecharts model the system..
- play_in_scenario := simulated system with GUI that lets user play with scenarios
and teach both good and bad ones.
- anti_scenarios := Things that must not happen.
- XUML := eXecutable UML, class diagrams+State charts.
- MSC := Message Sequence Chart, telecommunications standard, states what might happen but does not state what must and what must not happen.
- LSC::= Live Sequence charts, show possible and necessary sequences, can express both liveness and safety requirements, hot and cold elements.
- hot_condition in LSC := when part of scenario is entered the condition has to be true, or the system has failed catastrophically.
- 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.
- inter-object vs intra-object models.
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]