Analysis¶

Start here when you need the requirements and decisions behind the implementation.

The documents have different authority. Domain defines the canonical domain language and boundaries. ADRs record accepted architectural decisions. Drivers, ASRs, stories, journeys and BDD scenarios describe requirements; they do not override an ADR or prove that a capability has been implemented. When implementation status matters, use the status notes in the Domain document and verify the current service or client documentation.

For the assignment-oriented narrative, begin with the Report Path; this section remains the canonical detailed analysis behind it.

Page	Use it for
Drivers	Product goals, constraints, and architecture priorities.
ASRs	Prioritized quality attributes and the measurable scenarios that test them.
Journeys	End-to-end user flows across the product.
User Stories	Role–goal–benefit backlog, priorities, and explicit non-goals.
BDD	Epic-as-Feature acceptance scenarios in Given / When / Then form.
Domain	Canonical vocabulary, bounded contexts, aggregates, and events.
ADRs	Accepted architectural decisions and their trade-offs.