Requirements Workspace¶
Purpose¶
Translate the approved vision into concrete requirements and constraints. The requirements should be specific enough that planning, architecture, design, testing, release, and governance can trace back to them.
This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.
What belongs here¶
| Artifact | Project File Name | Template | Completed Example |
|---|---|---|---|
| Requirements Overview | requirements_overview.md |
Template | Completed example |
| Functional Requirements | functional_requirements.md |
Template | Completed example |
| Non Functional Requirements | non_functional_requirements.md |
Template | Completed example |
| Constraints | constraints.md |
Template | Completed example |
| Use Cases | use_cases.md |
Template | Completed example |
| Traceability Matrix | traceability_matrix.md |
Template | Completed example |
| Requirements Review | requirements_review.md |
Template | Completed example |
| Requirements Readiness Summary | requirements_readiness_summary.md |
Template | Completed example |
Start from templates¶
Requirements Overview
Open the reusable template for requirements_overview.md.
Functional Requirements
Open the reusable template for functional_requirements.md.
Non Functional Requirements
Open the reusable template for non_functional_requirements.md.
Constraints
Open the reusable template for constraints.md.
Use Cases
Open the reusable template for use_cases.md.
Traceability Matrix
Open the reusable template for traceability_matrix.md.
Requirements Review
Open the reusable template for requirements_review.md.
Requirements Readiness Summary
Open the reusable template for requirements_readiness_summary.md.
Working pattern¶
- Open the relevant template.
- Create the same-named file in
docs/project-workspace/requirements/. - Replace template guidance with project-specific evidence.
- Compare the result with the LMU/COICP example when available.
- Record open risks, assumptions, and unresolved questions.
- Finish with the review or readiness artifact for this stage.
Evidence quality bar¶
| Quality | What It Means |
|---|---|
| Specific | Names actual project facts, stakeholders, systems, scenarios, risks, and decisions. |
| Traceable | Connects back to earlier stages and forward to later stages. |
| Reviewable | Gives another reviewer enough evidence to challenge or approve the work. |
| Current | Reflects the project’s actual state rather than old intent. |
| Governable | Makes AI use, exceptions, risks, release posture, and limitations visible. |
Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.