Functional requirements and journeys
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
capture what the system must do as use cases or user journeys.
Planned topics
- A user journey follows one actor through steps toward a goal across channels.
- A use case: actor, goal, main flow, alternative and failure flows.
- Keep them at the level the business can validate; avoid design details.
- Give each a stable ID for traceability.
Draft outline details
Demonstration
journey FR-014 "Customer returns an online order to a store": steps, system touch points, failure flow (item not in order history), linked capabilities.
Check your understanding
Why include failure flows?
Show answer
Real behavior and risk live there, and they drive design.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.