SE311 · Chapter 2 · Annotated SlidesRequirements Inception
Original
Overview

Requirements Inception

Why inception matters, business requirements (problems, objectives, success metrics), the vision statement, scope and limitations, the Vision and Scope document, stakeholders, and scope representations: context diagrams, ecosystem maps, feature trees and event lists.

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 32 slides
  1. 1 Slide 1
  2. 2 Requirements Inception
  3. 3 Why Requirements Inception?
  4. 4 Why Requirements Inception?
  5. 5 1. Business Requierments
  6. 6 Business Requirements
  7. 7 Business Objectives
  8. 8 Business Problems & Objectives
  9. 9 Example:
  10. 10 Business Problems & Objectives
  11. 11 Success Metrics
  12. 12 Vision Statement
  13. 13 Vision and Scope Document
  14. 14 2. Scope and Limitations
  15. 15 2. Scope and Limitation
  16. 16 2. Scope and Limitations
  17. 17 2. Scope and Limitations
  18. 18 Scope & Limitations
  19. 19 Vision and Scope Document
  20. 20 Stakeholders?
  21. 21 Vision and Scope Document
  22. 22 Scope Representation Techniques
  23. 23 Context Diagrams
  24. 24 Context Diagrams
  25. 25 Ecosystem Maps
  26. 26 Ecosystem Maps
  27. 27 Feature Trees
  28. 28 Feature Trees
  29. 29 Event Lists
  30. 30 Event Lists
  31. 31 Final Remarks
  32. 32 Requirements Inception
Slide 1 / 32

Slide 1

Slide 1: Slide 1
Slide 2 / 32

Requirements Inception

Slide 2: Requirements Inception
Slide 3 / 32

Why Requirements Inception?

Slide 3: Why Requirements Inception?

Notes

  1. Inception establishes a shared understanding of the product’s context, problem, solution, boundaries and benefits.

Exam angle

PredictionQ1

The primary goal of requirements inception is to:

Slide 4 / 32

Why Requirements Inception?

Slide 4: Why Requirements Inception?
Slide 5 / 32

1. Business Requierments

Slide 5: 1. Business Requierments
Slide 6 / 32

Business Requirements

Slide 6: Business Requirements
Slide 7 / 32

Business Objectives

Slide 7: Business Objectives
Slide 8 / 32

Business Problems & Objectives

Slide 8: Business Problems & Objectives
Slide 9 / 32

Example:

Slide 9: Example:
Slide 10 / 32

Business Problems & Objectives

Slide 10: Business Problems & Objectives
Slide 11 / 32

Success Metrics

Slide 11: Success Metrics

Notes

  1. Success metrics: measurable indicators that the objectives were achieved.

Slide 12 / 32

Vision Statement

Slide 12: Vision Statement

Notes

  1. Vision statement: a short summary of the long-term purpose: For [customer] who [need], the [product] is a [category] that [benefit]. Unlike [alternative], our product [differentiator].

Slide 13 / 32

Vision and Scope Document

Slide 13: Vision and Scope Document

Notes

  1. Vision and Scope document = the main OUTPUT of inception: business requirements, vision, scope and limitations, business context (stakeholders, priorities).

Exam angle

PredictionQ1

The primary output of requirements inception is the:

PredictionQ2

List four components of a Vision and Scope document.

Compare with the model answer

Business requirements (background, opportunity, objectives, success metrics), the vision statement, scope and limitations (major features, scope of initial and later releases, what is excluded), and business context (stakeholder profiles, project priorities, deployment considerations); also business risks and assumptions.

Slide 14 / 32

2. Scope and Limitations

Slide 14: 2. Scope and Limitations

Notes

  1. Scope: what is in the release. Limitations: what is explicitly OUT.

Slide 15 / 32

2. Scope and Limitation

Slide 15: 2. Scope and Limitation
Slide 16 / 32

2. Scope and Limitations

Slide 16: 2. Scope and Limitations
Slide 17 / 32

2. Scope and Limitations

Slide 17: 2. Scope and Limitations
Slide 18 / 32

Scope & Limitations

Slide 18: Scope & Limitations
Slide 19 / 32

Vision and Scope Document

Slide 19: Vision and Scope Document
Slide 20 / 32

Stakeholders?

Slide 20: Stakeholders?

Notes

  1. Trap A stakeholder is not just whoever purchases the system.

Exam angle

PredictionQ1

A stakeholder is anyone who will purchase the completed software.

Slide 21 / 32

Vision and Scope Document

Slide 21: Vision and Scope Document
Slide 22 / 32

Scope Representation Techniques

Slide 22: Scope Representation Techniques
Slide 23 / 32

Context Diagrams

Slide 23: Context Diagrams

Notes

  1. Context diagram: the system as ONE circle, external entities around it, data flows in and out. Shows the boundary, NOT internals.

Exam angle

PredictionQ1

A context diagram does NOT show:

Slide 24 / 32

Context Diagrams

Slide 24: Context Diagrams
Slide 25 / 32

Ecosystem Maps

Slide 25: Ecosystem Maps

Notes

  1. Ecosystem map: all the systems that interact with this one, including indirect ones (no data flows detail).

Slide 26 / 32

Ecosystem Maps

Slide 26: Ecosystem Maps
Slide 27 / 32

Feature Trees

Slide 27: Feature Trees
Slide 28 / 32

Feature Trees

Slide 28: Feature Trees
Slide 29 / 32

Event Lists

Slide 29: Event Lists

Notes

  1. Event list: external events (business, signal, temporal) the system must respond to.

Exam angle

PredictionQ1

"At 2 a.m. every night the system backs up data" is which kind of event?

Slide 30 / 32

Event Lists

Slide 30: Event Lists
Slide 31 / 32

Final Remarks

Slide 31: Final Remarks
Slide 32 / 32

Requirements Inception

Slide 32: Requirements Inception