Eureka! Why Analysts Should Invent Requirements
IEEE Software
Supporting and Monitoring the Creativity of IS Personnel during the Requirements Engineering Process
HICSS '00 Proceedings of the 33rd Hawaii International Conference on System Sciences-Volume 7 - Volume 7
Integrating creativity workshops into structured requirements processes
DIS '04 Proceedings of the 5th conference on Designing interactive systems: processes, practices, methods, and techniques
Developing use cases and scenarios in the requirements process
Proceedings of the 27th international conference on Software engineering
Using a Creativity Workshop to Generate Requirements for an Event Database Application
REFSQ '08 Proceedings of the 14th international conference on Requirements Engineering: Foundation for Software Quality
Thesis proposal on "Requirement Engineering Process for Service Oriented Software Development"
Proceedings of the 11th International Conference on Product Focused Software
| Hi-index | 0.00 |
Requirements is too often seen as a "stenographer's task", one where the requirements engineer passively listens and records while the stakeholders state their needs. However, this approach relies on stakeholders knowing what they need, and what they want. Experience tells us that except for rare visionaries, people do not know what they want until they see it. Many of the useful products that we take for granted today, did not come about from the stakeholders' imagination, but from an invention. In this tutorial we explain and illustrate how to use creative techniques to invent requirements that result in more useful, usable and competitive products. We provide a guide for invention, and show participants how to use this guide to invent innovative requirements for a familiar system.