Developing use cases and scenarios in the requirements process

ABSTRACT

Scenarios are often used for discovering requirements using established techniques, but how such scenarios are initially developed is not so well understood. This experience paper reports the application of one scenario-based approach - RESCUE - to discover requirements for DMAN, an air traffic management system for the UK's National Air Traffic Services. A retrospective analysis of the DMAN use cases, scenarios and requirements artifacts revealed the importance of diverse information sources in the specification of use cases that enabled systematic requirements discovery. Results were used to explore 3 research questions that arose in previous studies. The paper reports lessons from this experience and offers guidelines that practitioners can apply in their requirements processes and academics can use to inform their research.

REFERENCES

• 1: Alexander I. F. & Maiden N.A.M. (Eds), 2004, Scenarios, Stories and Use Cases, John Wiley.
• 2: Thomas A. Alspaugh , Annie I. Antón , Tiffany Barnes , Bradford W. Mott, An Integrated Scenario Management Strategy, Proceedings of the 4th IEEE International Symposium on Requirements Engineering, p.142-149, June 07-11, 1999
• 3: Baddeley, A.D., 1990, Human memory: Theory and Practice, Lawrence Erlbaum Associates, Hove.
• 4: Camille Ben Achour , Colette Rolland , Carine Souveyet , Neil A. Maiden, Guiding Use Case Authoring: Results of an Empirical Study, Proceedings of the 4th IEEE International Symposium on Requirements Engineering, p.36-43, June 07-11, 1999
• 5: Alistair Cockburn, Writing Effective Use Cases, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 6: Ivar Jacobson , Grady Booch , James Rumbaugh, The unified software development process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 7: Jones S.V. & Maiden N.A.M., 2004, RESCUE Process Manual Version 4, Technical Report, Centre for HCI Design, City University, London.
• 8: Dean Leffingwell , Don Widrig, Managing software requirements: a unified approach, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 9: Neil Maiden , Sharon Manning , Suzanne Robertson , John Greenwood, Integrating creativity workshops into structured requirements processes, Proceedings of the 2004 conference on Designing interactive systems: processes, practices, methods, and techniques, August 01-04, 2004, Cambridge, MA, USA [doi>10.1145/1013115.1013132]
• 10: Maiden N.A.M., Jones S.V., Manning S., Greenwood J. & Renou L., 2004, Model-Driven Requirements Engineering: Synchronising Models in an Air Traffic Management Case Study, Proceedings CaiSE'2004, Springer-Verlag LNCS 3084, 368--383.
• 11: Alistair Mavin , Neil Maiden, Determining Socio-Technical Systems Requirements: Experiences with Generating and Walking through Scenarios, Proceedings of the 11th IEEE International Conference on Requirements Engineering, p.213, September 08-12, 2003
• 12: Suzanne Robertson , James Robertson, Mastering the requirements process, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1999
• 13: Colette Rolland , Carine Souveyet , Camille Ben Achour, Guiding Goal Modeling Using Scenarios, IEEE Transactions on Software Engineering, v.24 n.12, p.1055-1071, December 1998 [doi>10.1109/32.738339]
• 14: Vicente, K., 1999, Cognitive Work Analysis, Lawrence Erlbaum Associates.
• 15: Klaus Weidenhaupt , Klaus Pohl , Matthias Jarke , Peter Haumer, Scenarios in System Development: Current Practice, IEEE Software, v.15 n.2, p.34-45, March 1998 [doi>10.1109/52.663783]
• 16: Yin R., 2003, Case Study Research: Design and Methods, Sage Publications.
• 17: Eric S. K. Yu , John Mylopoulos, Understanding “why” in software process modelling, analysis, and design, Proceedings of the 16th international conference on Software engineering, p.159-168, May 16-21, 1994, Sorrento, Italy

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Elicitation methods (e.g., rapid prototyping, interviews, JAD)

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

General Terms:
Design, Human Factors

Keywords:
requirements, scenarios, use cases