The ReqLens pipeline, end to end
Every stage in order, from a raw requirement through to release reporting. The fastest route to understanding how the whole product fits together.
The order below is a suggestion, not a sequence you have to follow. Start wherever is useful to you.
- Requirement Studio: rough to testable
How elaboration works in ReqLens: what it adds to a raw requirement, why every change needs approval, and how edits propagate to everything downstream.
Everything downstream reads from what this stage produces.
Practitioner4 min read - Breaking a requirement into features
How ReqLens finds feature boundaries in a large requirement, why boundary detection and enrichment are separate steps, and what that separation protects.
Practitioner4 min read - From requirements to use cases
Use cases expose the paths a requirement implies but does not state. How ReqLens generates them, and why alternate flows are where the value sits.
Practitioner3 min read - Generating test cases from requirements
How to turn an elaborated requirement into test coverage you can defend, using TestCraft, and the design principles that make generated coverage trustworthy.
Practitioner4 min read - Running a test cycle: a TestExecute guide
Why blocked is a first-class result rather than a kind of failure, what a run record needs to stay meaningful, and how execution feeds readiness.
Practitioner4 min read - Tracking defects across the pipeline
Defects do not only come from testing. How ReqLens tracks where a defect was found, separates severity from priority, and makes rejection reasons useful.
Practitioner4 min read - Reporting coverage and traceability
How ReqLens turns pipeline evidence into reports a steering group can act on, and why end-to-end traceability is generated rather than assembled by hand.
Where the whole chain becomes a number somebody can act on.
Practitioner3 min read - Connecting Jira and Azure DevOps
What the connectors import, how run results are pushed back as a single maintained comment, and the decisions behind dedupe, credentials, and eligibility.
Practitioner4 min read - Workspaces, roles and permissions
Three roles, ranked rather than listed, and what each can do. How project access resolves, and why some things belong to the workspace rather than a person.
Foundation3 min read