Scenario-based requirements analysis techniques for real-time software systems: A comparative evaluation

Requirements Engineering

Volumn 10, Issue 1, 2005, Pages 22-33

  Saiedian, Hossein ^a   Kumarakulasingam, Prabha ^a   Anan, Muhammad ^b  

^a UNIVERSITY OF KANSAS   (United States)

^b SPRINT NEXTEL   (United States)

Author keywords

Real time; Requirements engineering; Scenario based; Time automata

Indexed keywords

AUTOMATA THEORY; CONSTRAINT THEORY; REAL TIME SYSTEMS; RESPONSE TIME (COMPUTER SYSTEMS); SEMANTICS; SOFTWARE ENGINEERING; SYSTEMS ANALYSIS;

REAL TIME SOFTWARE SYSTEMS; SCENARIO BASED ANALYSIS; TIME AUTOMATA;

REQUIREMENTS ENGINEERING;

EID: 13644270959     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s00766-004-0192-6     Document Type: Article

References (16)

1. Jacobson I, Christerson M, Jonsson P, Overgaard, G (1992) Object-oriented software engineering use case driven approach. Addison-Wesley, Reading, MA
2. Weidenhaupt K, Pohl K, Jarke M, Haumer P (1998) Scenarios in system development: Current practice. IEEE Softw 15(2):34-45
3. Ekelin C, Jonsson J (1996) Real-time system constraints: Where do they come from and where do they go? In: Proceedings of the International Workshop on Real-Time Constraints, Alexandria, VA, October 1999, pp 53-57
4. Amyot D, Mussbacher G (2000) On the extension of UML with use case maps concepts. In: Proceedings of UML2000, York, UK, October 2000. Lecture notes in computer science, vol 1939. Springer, Berlin Heidelberg New York, pp 16-31
5. Glinz M (2000) Improving the quality of requirements with scenarios. In: Proceedings of the Second World Congress for Software Quality (2WCSQ), Yokohama, September 2000, pp 55-60.
6. Glinz M (2000) Problems and deficiencies of UML as a requirements specification language. Proceedings of the 10th International Workshop on Software Specifications and Design (IWSSD-10), San Diego, November 2000, pp 11-22.
7. Glinz M (2000) A lightweight approach to consistency of scenarios and class models. In: Proceedings 4th IEEE International Conference on Requirements Engineering. Schaumburg, IL, June 2000, pp 49-58
8. Harel D (1987) StateCharts: A visual formalism for complex systems. Sci Comput Program 8:231-274
9. Regnell B, Andersson M, Bergstrand J (1996) A hierarchical use case model with graphical representation. In: Proceedings of ECBS96, IEEE International Symposium and Workshop on Engineering of Computer-Based Systems, March 1996.
10. Message Sequence Chart (MSC) (1993) ITU-T Recommendation Z.120, International Telecommunication Union
11. Buhr R, Casselman R (1996) Use case maps for object-oriented systems. Prentice Hall
12. Hsia P, Samuel J, Gao J, Kung D (1994) Formal approach to scenario analysis. IEEE Softw 11(2):33-41
13. Leveson N, Heimdhal H, Hildreth H, Reese J (1994) Requirements specifications for process-control systems: Lessons learned and steps to the future. IEEE Trans Softw Eng 20(9):684-706
14. Some S, Dssouli R, Vaucher J (1995) From scenarios to timed automata: building specifications from users requirements. Asia Pacific Software Engineering Conference, December 1995
15. Barbacci M, Carriere S, Feller P, Klien M, Kazman R, Lipson H, Longstaff T, Weinstock C (1998) Steps in an architecture tradeoff analysis method: quality attribute models and analysis. Technical Report TR-97-029. Software Engineering Institute, Pittsburgh, PA
16. Jacobson I, Christerson M, Jonsson P, Overgaard, G (1992) Object-oriented software engineering use case driven approach. Addison-Wesley, Reading, MA