Skip to main content
Article thumbnail
Location of Repository

Learning how to discover requirements

By Ljerka Beus-Dukic and Ian Alexander


Requirements engineering (RE) is traditionally taught in academia using an RE process which starts from a well-defined problem. Our approach focuses on the early stages of requirements discovery where students have to learn both about the application domain and about what stakeholders feel is the problem. The approach comprises all the basic elements of requirements, and ways to discover them using many small discovery cycles. In this position paper we outline the rationale for our approach and reflect on our initial experiences with teaching undergraduate RE module using this approach

Topics: UOW3
Publisher: IEEE
OAI identifier:
Provided by: WestminsterResearch

Suggested articles


  1. (1996). Co-operative Inquiry, Research into the Human Condition,
  2. (2009). Discovering Requirements: How to Specify Products and Services,
  3. (2000). Managing Software Requirements: A Unified Approach,
  4. (1999). Mastering the Requirements Process,
  5. (1998). Requirements Engineering as a Cooperative Inquiry, Requirements Engineering 3:130-137,
  6. (2000). Requirements Engineering: A Roadmap, In:
  7. (1998). Requirements Engineering: Processes and Techniques,
  8. (2003). Teaching Requirements Engineering through Role Playing: Lessons Learnt,
  9. (2005). Use and Abuse Cases,
  10. (2002). Writing Better Requirements,

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.