This document discusses requirement elicitation and definition. It defines a requirement as a statement of a customer need that a product must fulfill, and defines elicitation as identifying requirements through interviews, workshops, focus groups and other methods. It notes that stakeholders are individuals affected by or able to influence a project, and lists potential stakeholders as customers and user classes. Finally, it outlines common elicitation techniques like interviews and workshops, and the process of preparing, performing and following up on elicitation activities.

1. Requirement Elicitation

3. Requirement Definition
 “[A requirement is a] statement of a customer need or objective, or of a condition or
capability that a product must possess to satisfy such a need or objective. A property that
a product must have to provide value to a stakeholder.” (Wiegers & Beatty)

4. Structure

5. Structure

6. Structure

7. Elicitation

8. Requirement Development Framework

9. Structured Approach

10. Structured Approach

11. “[Elicitation is the] process of identifying,
discovering requirements from various
sources through interviews, workshops, focus
groups, observations, document analysis, and
other mechanisms.”

12. Key Action

13. Stakeholders
“[A stakeholder is an] individual, group, or
organization that is actively involved in a
project, is affected by its process or
outcome, or can influence its process or
outcome.”

14. Stakeholders

15. Potential Stakeholders

16. Customer

17. User Classes

18. Elicitation techniques

19. Elicitation techniques
 Interviews
 Workshops
 Focus Groups
 Observations
 Questionnaires
 Document Analysis
 System Interface Analysis
 User Interface Analysis

20. Elicitation activities

21. Preparing for elicitation

22. Performing elicitation

23. Following up

24. Organise categories