45ck Purpose
Assemble BA outputs into a coherent, reusable requirements or analysis pack.
Use when
- elicitation and analysis outputs exist but are fragmented
- a formal document or pack is needed
- traceability and reviewability matter
Inputs
- project or problem context
- goals and constraints
- known stakeholders, systems, and documents
- level of formality required
Procedure
- Gather all existing artifacts and normalise terminology.
- Organise content into background, scope, models, catalogue, and open issues.
- Structure requirements into a navigable hierarchy.
- Link requirements back to needs, stakeholders, and sources.
- Insert diagrams, glossary, assumptions, and traceability references.
- Flag unresolved contradictions and decisions pending.
- Produce a review-ready package.
Outputs
- requirements document structure
- requirements catalogue
- glossary
- source/traceability notes
- open issues register
Guardrails
- Explicitly separate fact, inference, and assumption.
- Prefer evidence-backed conclusions over polished speculation.
- Where conflict exists, record it rather than smoothing it away.
- Produce artifacts that can be inspected, edited, and reused.
Completion criteria
- deliverable pack exists
- tradeoffs are explicit
- unknowns are logged
- next decisions are obvious