Integrating creativity workshops into structured requirements processes

ABSTRACT

Requirements engineering is a creative process in which stakeholders and designers work together to create ideas for new systems that are eventually expressed as requirements. This paper describes RESCUE, a scenario-driven requirements engineering process that includes workshops that integrate creativity techniques with different types of use case and system context modelling. It reports a case study in which RESCUE creativity workshops were used to discover stakeholder and system requirements for DMAN, a future air traffic management system for managing departures from major European airports. The workshop was successful in that it provided new and important outputs for subsequent requirements processes. The paper describes the workshop structure and wider RESCUE process, important results and key lessons learned.

REFERENCES

• 1: Andrews D.C., 1991, 'JAD: A Crucial Dimension for Rapid Applications Development', Journal of Systems Management, March 1991, 23--31.
• 2: Boden M.A., 1990, The Creative Mind, Abacus, London
• 3: Chung L., Nixon B., Yu E. and Mylopoulos J., 2000, 'Non-Functional Requirements in Software Engineering', Kluwer Academic Publishers.
• 4: Daupert, D. (2002) The Osborn-Parnes Creative Problem Solving manual. Available from www.ideastream.com/create.
• 5: Floyd, C., Mehl, W.-M., Reisin, F.-M., Schmidt, G., & Wolf, G. (1989). Out of Scandinavia: Alternative Approaches to Software Design and System Development. Human-Computer Interaction, 4(4), 253--350.
• 6: Gick M.L. & Holyoak K.J., 1983, 'Schema Induction & Analogical Transfer', Cognitive Psychology 15, 1--38.
• 7: Jonathan Hammond , Rosamund Rawlings , Anthony Hall, Will It Work?, Proceedings of the 5th IEEE International Symposium on Requirements Engineering, p.102-109, August 27-31, 2001
• 8: Hargadon A. & Sutton R.I., 2000, Building an Innovation Factory, Harvard Business Review, May-June 2000.
• 9: Isaksen, G. & Dorval, K. (1993) Changing views of creative problem solving: Over 40 years of continuous improvement. ICN Newsletter. 3 (1).
• 10: Koestler, A., 1964, The Act of Creation, London Hutchinson.
• 11: Neil Maiden , Alexis Gizikis, Where Do Requirements Come From?, IEEE Software, v.18 n.5, p.10-12, September 2001 [doi>10.1109/52.951486]
• 12: Maiden N.A.M., Jones S. Flynn M., 2003a, 'Innovative Requirements Engineering Applied to ATM', Proceedings Joint Eurocontrol/FAA ATM'2003 Conference, June 2003, Budapest.
• 13: Neil Maiden , Sara Jones , Mary Flynn, Integrating RE Methods to Support Use Case Based Requirements Specification, Proceedings of the 11th IEEE International Conference on Requirements Engineering, p.369, September 08-12, 2003
• 14: 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
• 15: Maiden N.A.M. & Rugg G., 1996, 'ACRE: Selecting Methods For Requirements Acquisition, Software Engineering Journal 11(3), 183--192.
• 16: Neil Maiden , Alistair Sutcliffe, Exploiting reusable specifications through analogy, Communications of the ACM, v.35 n.4, p.55-64, April 1992 [doi>10.1145/129852.129857]
• 17: Lena Mamykina , Linda Candy , Ernest Edmonds, Collaborative creativity, Communications of the ACM, v.45 n.10, October 2002 [doi>10.1145/570907.570940]
• 18: L. Nguyen , J. Carroll , P. A. Swatman, Supporting and Monitoring the Creativity of IS Personnel during the Requirements Engineering Process, Proceedings of the 33rd Hawaii International Conference on System Sciences-Volume 7, p.7008, January 04-07, 2000
• 19: Obsorn A.F., 1953, 'Applied Imagination: Principles and Procedures of Creative Problem Solving', Charles Scribener's Sons, New York.
• 20: Pennell L. & Maiden N.A.M., 2003, 'Creating Requirements -- Techniques and Experiences in the Policing Domain', Proceedings REFSQ'2003 Workshop, June 2003, Velden Austria.
• 21: Poincare H., 1982, The Foundations of Science: Science and Hypothesis, The Value of Science, Science and Method, Univ. Press of America, Washington 1982
• 22: James Robertson, Eureka! Why Analysts Should Invent Requirements, IEEE Software, v.19 n.4, p.20-22, July 2002 [doi>10.1109/MS.2002.1020281]
• 23: Suzanne Robertson , James Robertson, Mastering the requirements process, ACM Press/Addison-Wesley Publishing Co., New York, NY, 1999
• 24: Ross B.H., 1987, 'This is Like That: The Use of Earlier Problems and the Separation of Similarity Effects', Journal of Experimental Psychology: Learning, Memory and Cognition 13(4), 629--639.
• 25: Alistair Sutcliffe , Neil Maiden, The Domain Theory for Requirements Engineering, IEEE Transactions on Software Engineering, v.24 n.3, p.174-196, March 1998 [doi>10.1109/32.667878]
• 26: Vicente, K., Cognitive work analysis, Lawrence Erlbaum Associates, 1999.

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:
analogical reasoning, creativity workshops, models of creativity, requirements, storyboarding