Quality
Which tests the requirements demand
Derived from the requirement spec, customer requirements and standards: which tests the product must pass, with a source per requirement.
How you work it in Colleag
- 1
Ask the colleague to derive the test needs from the requirements.
- 2
The colleague reads the requirement spec, customer requirements and the standards you have uploaded.
- 3
Review the list: every test points at the requirement and the source behind it.
- 4
Approve; the list becomes the basis for test plan and control programme.
A worked example
“Which tests must the X200 pass for the utility-grid customer?”
A list per requirement: EMC, environmental and safety tests with the standard and requirement line behind each, and the requirements pointing at no test flagged. The source stands per row so the auditor can follow it.
Screenshot from Colleag. The example uses invented figures.
The material
- Requirement spec and customer requirements in the workspace
- Standards you have uploaded
- Earlier test reports
You approve
Everything the colleague produces is a proposal with sources. Nothing is published, sent or saved to the archive without a human approving it, and every figure traces to its material.
Curious what it feels like?
We run pilot programs with a few manufacturing companies at a time. Tell us about your business and we will show what the colleagues can do with your documents and your data.