|
|
Key
These lines were removed. This word was removed.
These lines were added. This word was added.
|
View page history
|
There are 1 changes. View first change.
| | *Title* "From Play-In Scenarios to Code: An Achievable Dream" |
| | |
| | *Authors* David Harel |
| | |
| | *Reference* |
| | | IEEE Press, 53-60. Also, Proc. Fundamental Approaches to Software Engineering_ (FASE;invited paper),Lecture Notes in Computer Science, Vol. 1783 (Tom Maibaum, ed.), Springer-Verlag, March 2000, pp. 22-34.) |
| | | IEEE Press, 53-60. Also, Proc. Fundamental Approaches to Software Engineering\_ (FASE;invited paper), Lecture Notes in Computer Science, Vol. 1783 (Tom Maibaum, ed.), Springer-Verlag, March 2000, pp. 22-34.) |
| | |
| | *Year* 2001 |
| | |
| | *URL* [http://www.wisdom.weizmann.ac.il/~harel/SCANNED.PAPERS/PlayInToCode.pdf] |
| | |
| | *My Summary* |
| | The paper describes a development methodology for reactive systems, i.e. real-time systems, that uses "play-in" techniques that specify the system's behavior through different scenarios pluged in by means of a graphical user interface. Through this high-level user-friendly requirements capture method, the full model of a system, and from there to final implementation, can be obtained. The language that this technique is based on is "live sequence charts", or LSC, which can be viewed as an extension to sequence diagrams, extension that addresses the deficiencies and drawbacks of the sequence diagrams, like the inability of specifying unwanted scenarios. |
| | |
| | *Methods* |
| | The author makes use of Structured-Analysis/Structured Design (SA/SD) and executable UML (XUML) for modeling the system's structure and behavior, and LSC or temporal logic of specifying requirements. |
| | |
| | *Systems Integration Relevance* |
| | Trying to move from a waterfall design approach to a incremental model, with various cycles of activity taking place, in which true verification checks the model against the requirements, is of a paramount importance in order for our methodology to be accepted and successful at the same time. |
| | |
| | *Keywords* |
| | Use Cases, Requirements, LCS, Temporal Logic, Verification, System Design, System Model, SA/SD, XUML, UML, Rhapsody |
|
|
