Docs/Project management
Requirements
Capture constraints and connect them to the engineering work that satisfies them.
What belongs in Requirements
Use Requirements for statements the project or design is expected to satisfy. Keep them specific enough that a later test, inspection, analysis or demonstration could provide meaningful evidence.
- Performance targets and limits
- Safety or regulatory constraints
- Interface constraints
- User or stakeholder needs translated into engineering requirements
Link requirements
Requirements become more useful when linked to the work and engineering records they influence. Links preserve traceability without copying the requirement text into every other system.
Free-plan behaviour
The current Free plan allows up to 12 requirements per project. Pro removes that count limit. Other integration-link restrictions can also depend on plan entitlements.