Where Do Requirements Come From?
IEEE Software
Integrating creativity workshops into structured requirements processes
DIS '04 Proceedings of the 5th conference on Designing interactive systems: processes, practices, methods, and techniques
Creative requirements: invention and its role in requirements engineering
Proceedings of the 28th international conference on Software engineering
Can Requirements Be Creative? Experiences with an Enhanced Air Space Management System
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Inventing Requirements: Experiences with an Airport Operations System
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
A framework for understanding creativity in requirements engineering
Information and Software Technology
Inventing Requirements with Creativity Support Tools
REFSQ '09 Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
| Hi-index | 0.03 |
The early stages of the RE process involve developing understanding of a problem situation, the problem domain, and the requirements for achieving improvements in the problem situation. How requirements engineers work to develop this understanding is poorly understood. The findings from several field studies of the RE process show that the process is creative and opportunistic, involving adaptive and responsive exploration of the problem space. The question of how to support and monitor the process remains. We have approached this problem by examining the complexity of the requirements models in a number of laboratory-based studies. By recording the RE process using a design rationale notation and analyzing the complexity of the requirements models, we have traced the oscillations in complexity throughout the process; we have called this the catastrophe-cycle of the requirements modeling process. We discuss the usefulness of design rationale in supporting and monitoring the RE process, examine the implications of this research for managing the creative and insight-driven RE process, and highlight areas for future research.