Monitoring and control in scenario-based requirements analysis

ABSTRACT

Scenarios are an effective means for eliciting, validating and documenting requirements. At the requirements level, scenarios describe sequences of interactions between the software-to-be and agents in the environment. Interactions correspond to the occurrence of an event that is controlled by one agent and monitored by another.This paper presents a technique to analyse requirements-level scenarios for unforeseen, potentially harmful, consequences. Our aim is to perform analysis early in system development, where it is highly cost-effective. The approach recognises the importance of monitoring and control issues and extends existing work on implied scenarios accordingly. These so-called input-output implied scenarios expose problematic behaviours in scenario descriptions that cannot be detected using standard implied scenarios. Validation of these implied scenarios supports requirements elaboration. We demonstrate the relevance of input-output implied scenarios using a number of examples.

References

1. R. Alur, G.J. Holzmann, and D. Peled, "An analyzer for message sequence charts", Software Concepts and Tools, vol. 17, no. 2, pp. 70(77), 1996.]]
2. R. Alur and M. Yannakakis, "Model checking of message sequence charts", in 10th International Conference on Concurrency Theory, 1999, LNCS 1664, pp. 114--129.]]
3. R. Alur, K. Etessami, and M. Yannakakis. Inference of message sequence charts, in 22nd International Conference on Software Engineering, 2000.]]
4. H. Ben-Abdallah, S. Leue: MESA: Support for Scenario-Based Design of Concurrent Systems , in 4th Intl. Conf. on Tools and Algorithms for the Construction and Analysis of Systems, 1998.]]
5. G. Berry and G. Gonthier. The synchronous programming language ESTEREL: Design, semantics, implementation. Sci. of Comp. Prog., 19(2):87--152, 1992.]]
6. R. Chatley, J. Kramer, J. Magee and S. Uchitel, Model-based Simulation of Web Applications for Usability Assessment, in ICSE Workshop on Bridging the Gaps between Software Engineering and Human-Computer Interaction, 2003.]]
7. M. Feather, "Language Support for the Specification and Development of Composite Systems", ACM Trans. on Programming Languages and Systems 9(2), Apr. 87, 198--234.]]
8. Harel, D. Marelly, R. Come, Let's Play: Scenario-Based Programming Using LSCs and the Play-Engine, Springer, New York. 2003.]]
9. C. Heitmeyer, R.D. Jeffords and B. G. Labaw, "Automated Consistency Checking of Requirements Specifications", ACM Trans. on Software Eng. and Methodology 5, 3, July 1996, 231--261.]]
10. International Telecommunications Union Telecommunication Standardisation Sector, Message Sequence Charts, 1996.]]
11. M. Jackson, Software Requirements & Specifications - A Lexicon of Practice, Principles and Prejudices. ACM Press, Addison-Wesley, 1995.]]
12. A. van Lamsweerde and L. Willement, Inferring Declarative Requirements Specifications from Operational Scenarios. IEEE Transactions on Software Engineering, 24 (12). 1089--1114, 1998.]]
13. A. van Lamsweerde, Requirements Engineering in the Year 00: A Research Perspective, 22nd International Conference on Software Engineering, Limerick, 2000.]]
14. E. Letier and A. van Lamsweerde, Agent-Based Tactics for Goal-Oriented Requirements Elaboration, in 24th Intl. Conference on Software Engineering, 2002.]]
15. S. Leue, L. Mehrmann, M. Reza: Synthesizing ROOM Models from Message Sequence Chart Specifications, 13th IEEE Conference on Automated Software Engineering, 1998.]]
16. A. Muscholl, D. Peled, and Z. Su, Deciding properties of message sequence charts," in Foundations of Software Sci. and Comp. Structures, 1998.]]
17. J. Niu, J. Atlee, N. Day, Template Semantics for Model-Based Notations, IEEE Transactions on Software Engineering, 29(10) 866--882, 2003.]]
18. D.L. Parnas and J. Madey, "Functional Documents for Computer Systems", Science of Computer Programming, Vol. 25, 1995, 41--61.]]
19. Sutcliffe A.G., Maiden N.A.M., Minocha S. & Manuel D. (1998), Supporting Scenario Based Requirements engineering, IEEE Transactions on Software Engineering, 24(12), pp 1072--1088.]]
20. Object Management Group, Unified Modelling Language, 2002.]]
21. S. Uchitel, J. Kramer, and J. Magee, Incremental elaboration of scenario-based specifications and behavior models using implied scenarios, ACM Transactions on Software Engineering and Methodology, pp 37--85, 13(1), 2004.]]
22. Whittle, J. and Schumann, J. "Generating Statechart Designs from Scenarios" in 22nd International Conference on Software Engineering, 2000.]]
23. P. Zave and M. Jackson, "Four Dark Corners of Require-ments Engineering", ACM Transactions on Software Engineering and Methodology, 1997, 1--30.]]

Index Terms

• Software and its engineering

  • Software creation and management

    • Designing software

      • Requirements analysis