Requirements Workflow
The requirements workflow governs how SPECLAN specifications progress from initial creation through to approval. This process ensures consistent quality, facilitates stakeholder reviews, and maintains clear accountability.
Overview
Every specification begins as a draft and must pass through a structured review before becoming approved. The Requirements Engineer owns this process and is responsible for the specification's quality, completeness, and readiness for development.
draft ──> review ──> approved
Workflow Stages
Draft
The initial working state where the Requirements Engineer develops the specification.
Who owns it: Requirements Engineer
What happens:
- Content can be freely edited and revised
- No formal review process is active
Review
The specification is submitted for stakeholder review and feedback.
Who owns it: Requirements Engineer (with reviewer participation)
What happens:
- The Requirements Engineer submits the draft for review
- The Requirements Engineer tracks and responds to all feedback
- Multiple review cycles may occur until approval criteria are met
Approved
The specification has passed review and is ready for implementation.
Who owns it: Transitions to the implementation team
What happens:
- The specification is still editable — this is the last chance to refine before development starts
- Once the spec moves to in-development, it becomes locked and changes require a formal Change Request
- Ownership responsibility transitions to the development team
- The specification serves as the authoritative reference for development
Transition Criteria
| From | To | Requirements |
|---|---|---|
| draft | review | All mandatory fields completed; submitted by spec owner |
| review | approved | All review feedback addressed; approval criteria met |
Related Topics
- Status Lifecycle -- Full status progression reference
- Development Workflow -- What happens after approval
- Change Requests -- How to modify specifications in development or later