#Requirements Overview
Requirements define what needs to be built, fixed, or improved in a project. They act as the foundation for test case creation and help teams ensure that every important change is properly validated through testing.
In Hawzu, requirements are closely tied to test cases and coverage, enabling clear traceability from planning to validation.
#Core Concepts
#What Are Requirements?
Requirements represent planned or requested work such as:
- New features or functionality
- Bug fixes or corrective changes
- Enhancements to existing behavior
- Performance or quality improvements
Each requirement can be linked to one or more test cases, making it easy to track what has been tested and what still needs coverage.
#Requirement Lifecycle
Requirements typically move through multiple stages as a project evolves.
While exact statuses may vary by project, a requirement usually progresses from definition to implementation and validation.
Tracking requirement status helps teams:
- Understand what is planned vs completed
- Coordinate development and testing efforts
- Monitor readiness for release
#Requirements and Test Cases
Requirements are designed to work closely with test cases:
- A requirement can be linked to multiple test cases
- Test cases can validate one or more requirements
- Coverage views show which requirements are tested
- Unlinked requirements highlight testing gaps
This relationship ensures clear traceability and accountability.
#Accessing Requirements
To access requirements:
- Open a project
- Select Requirements from the project sidebar
The Requirements page lists all requirements associated with the project.
#Viewing Requirements
The Requirements view allows you to:
- Browse all project requirements
- View requirement titles and descriptions
- See how many test cases are linked to each requirement
- Quickly identify requirements without coverage
You can sort and scan requirements to understand progress and testing readiness at a glance.
#Why Requirements Matter
Using requirements in Hawzu helps teams:
- Ensure every feature or fix is validated
- Avoid missing test coverage for critical work
- Improve collaboration between product, development, and QA
- Track testing completeness with confidence
- Support audits and compliance needs
#Best Practices
- Create requirements early in the project lifecycle
- Keep requirement descriptions clear and focused
- Link test cases consistently
- Review uncovered requirements regularly
- Use coverage insights before major releases
#Permissions
Access to requirements depends on your project role:
- Project Manager – Full access
- Project Coordinator – Full access
- Project Member – View and link test cases
- Project Viewer – Read-only access
Requirement visibility respects project access controls.
#Next Steps