SE311 · Chapter 3 · Annotated SlidesThe Requirements Elicitation Process
Original
Overview

The Requirements Elicitation Process

Elicitation goals and sources of requirements, the process (plan, prepare, perform, follow up), classifying customer input, knowing when you are done, challenges and best practices.

How to read this page

Every original slide is shown unchanged. Yellow marks on a slide point to a numbered note: hover or tap a mark to jump to its note, and hover a note to see its marks. Questions tagged Past exam appeared on a real paper; Prediction questions are likely angles, not confirmed. Pick an answer to each question: a wrong pick tells you why it is wrong, so you can try again.

All 19 slides
  1. 1 Slide 1
  2. 2 Outline
  3. 3 Elicitation Goals
  4. 4 Sources of Requirements
  5. 5 Sources of Requirements - Stakeholders
  6. 6 Requirements Elicitation Process
  7. 7 Planning for Elicitation
  8. 8 Prepare for Elicitation
  9. 9 Prepare for Elicitation
  10. 10 Performing Elicitation Activities
  11. 11 Following up after Elicitation
  12. 12 Following up after Eliciation
  13. 13 Classifying Customer Input
  14. 14 When are we done?
  15. 15 Elicitation Challenges
  16. 16 Final Remarks
  17. 17 Requirements Elicitation Best Practices
  18. 18 Slide 18
  19. 19 Slide 19
Slide 1 / 19

Slide 1

Slide 1: Slide 1
Slide 2 / 19

Outline

Slide 2: Outline
Slide 3 / 19

Elicitation Goals

Slide 3: Elicitation Goals

Notes

  1. Elicitation: discovering requirements from stakeholders and other sources (not just "gathering").

Slide 4 / 19

Sources of Requirements

Slide 4: Sources of Requirements

Notes

  1. Sources: stakeholders and users, documents, existing systems, regulations, competitors, problem reports.

Slide 5 / 19

Sources of Requirements - Stakeholders

Slide 5: Sources of Requirements - Stakeholders
Slide 6 / 19

Requirements Elicitation Process

Slide 6: Requirements Elicitation Process
Slide 7 / 19

Planning for Elicitation

Slide 7: Planning for Elicitation
Slide 8 / 19

Prepare for Elicitation

Slide 8: Prepare for Elicitation
Slide 9 / 19

Prepare for Elicitation

Slide 9: Prepare for Elicitation
Slide 10 / 19

Performing Elicitation Activities

Slide 10: Performing Elicitation Activities
Slide 11 / 19

Following up after Elicitation

Slide 11: Following up after Elicitation
Slide 12 / 19

Following up after Eliciation

Slide 12: Following up after Eliciation
Slide 13 / 19

Classifying Customer Input

Slide 13: Classifying Customer Input

Notes

  1. Classify input as: business requirement, user requirement, business rule, functional, quality attribute, external interface, constraint, data definition, solution idea.

Slide 14 / 19

When are we done?

Slide 14: When are we done?

Notes

  1. Done when: users can’t think of more use cases; new ideas are out of scope or low priority; proposed requirements repeat earlier ones; ideas are future, not current; the remaining issues are understood.

Exam angle

PredictionQ1

When do you know you are done with elicitation? Give two signs.

Compare with the model answer

Users can’t think of any more use cases or user stories; new suggestions are out of scope or already captured (repeating earlier requirements); remaining ideas are “nice to have” for future releases; the team can explain the requirements well enough to build and test.

Slide 15 / 19

Elicitation Challenges

Slide 15: Elicitation Challenges

Notes

  1. Challenges: stakeholders unavailable, don’t know what they want, use jargon, conflict; scope creep; solution ideas disguised as requirements.

Slide 16 / 19

Final Remarks

Slide 16: Final Remarks
Slide 17 / 19

Requirements Elicitation Best Practices

Slide 17: Requirements Elicitation Best Practices

Notes

  1. Best practices: define scope first, identify user classes, select product champions, use several techniques, document as you go.

Slide 18 / 19

Slide 18

Slide 18: Slide 18
Slide 19 / 19

Slide 19

Slide 19: Slide 19