After you have defined your project it is time to define your organization’s quality metrics. Step two: defining risks and requirements.
Requirements define the needs of the project’s stakeholders. They are used during testing to validate that what has been built matches the business objectives of the project. Risks allow you to define project hazards which can be used to direct your testing effort.
An overview of risks & requirements
You can start defining requirements and risks by clicking Define > Requirements or Define > Risks in the header.
The requirements and risks overviews provide you with a list of defined requirements or risks for the active project.
Adding a risk
You can add a risk by clicking Add risk on the top right of the risk overview.
A popup will appear allowing you to specify the risk properties: Classification (optional), Name (required), Description (optional) and Tags (optional).
Press Save to add the new risk.
Adding a requirement
You can add a requirement by clicking Add requirement on the top right of the requirement overview.
A popup will appear allowing you to specify the requirement properties: Type (optional), Name (required), Description (optional) and Tags (optional).
Press Save to add the new requirement.