Use case · Engineering · Project management · Quality
Run the V-model faster, from the first requirement to validation.
In the V-model, the left branch breaks the system down into requirements, architecture and specifications, and the right branch integrates and verifies it level by level against them. Koddex holds every phase in one shared model, with each requirement linked to its test and AI agents working on each phase, so teams bring new products to market up to 30% faster.
Standard cycle· 0 loops
Koddex AI agents· 0 loops
Watch it in 60 seconds
Agents on the V
The agent runs the loop. You sign the gate.
Assigned to every phase
You assign each phase of the V to an agent: it checks requirements, design and tests as the work happens, instead of waiting for the design review.
It catches the failure
When a test fails, the agent traces the cause back to the design element and requirement involved.
It iterates until every check passes
It proposes a fix on a branch and re-runs the checks until they pass, and an engineer approves the release. Teams spend 50% less time on repetitive engineering tasks.
AI verification engineer
Agent settings · Koddex
- Structure a customer specification
- Allocate requirements to the system
- Write test skeletons from requirements
- Run impact analysis on every change
- Draft change requests for review
Review gates: each one is a frozen baseline in Koddex
SRR Requirements review
Every requirement has an owner and a way to prove it.
PDR Preliminary design
Each requirement points to the element that carries it.
CDR Critical design
The BOM, interfaces and specifications are frozen together as one baseline.
TRR Test readiness
Every requirement has its test and its criterion.
SAR System acceptance
Test results are recorded on the requirements and the acceptance dossier is generated from them.
ORR Operational readiness
Every delivered configuration can be shown, and field returns are traced to their requirement in seconds.
Verification is not validation
Verification checks that the system was built right, against its requirements. Validation checks that the right system was built, against the customer need. Koddex keeps both in the same model.
Verification
Does the system meet its requirements?
Checked against the written specification, requirement by requirement.
In Koddex: Each requirement is linked to its method, test and result, and coverage is computed.
Validation
Does it solve the customer's problem?
Checked against the customer need, on the integrated system.
In Koddex: Each customer need is linked to its requirements and its acceptance evidence.
The verification matrix, generated from the requirements
Each requirement records how it will be verified, so Koddex builds the verification matrix (VCRM) from the data and exports it in one click.
I
Inspection
Visual check of the item or its documentation, the cheapest method.
A
Analysis
Calculation, simulation or model shows compliance.
D
Demonstration
Operate the system to show the function works, without instrumented measurement.
T
Test
Instrumented measurement against a quantified criterion, the most expensive and most conclusive method.
VCRM preview
| Requirement | Statement | Method | Evidence | Status |
|---|---|---|---|---|
| REQ-214 | Payload 35 kg at 2 m/s | T | TC-088 | Pass |
| REQ-215 | Fire class V-0 on housing | A | SIM-12 | Stale since rev C |
| REQ-230 | Emergency stop reachable | D | DEMO-04 | Not run |
| REQ-241 | Label CE visible | I | INS-19 | Pass |
Every phase of the V works on the same data
When a requirement or design element changes on the left branch, Koddex shows at once which tests must be re-run, which baselines are affected and which customers are concerned.
01
Concept & requirements
Requirements management
02
Architecture & design
Model canvas + BOM
03
Specifications & implementation
Connected BOM, revisions, variants
04
Integration & verification
Interfaces, coverage and traceability
05
Validation & deployment
Controlled releases and baselines
06
Operations & next V
Impact analysis + knowledge continuity
A defect caught late costs up to 1,000 times more.
Impact analysis checks each change before it is committed, so problems are found during design instead of during integration or in the field.
Requirements
Design
Integration and test
Operations
Relative cost to correct a defect by lifecycle phase, log scale. Order-of-magnitude figures taught in systems engineering curricula (NASA Systems Engineering Handbook; MIT 16.842).
What changes when the V runs in Koddex
- Seconds
- from a field defect to the requirement and test concerned, instead of days
- 0
- traceability matrices rebuilt by hand before a review
- Minutes
- to an audit-ready baseline with its evidence
- −0%
- time to market for a new product
Related use cases
Glossary
Further reading
- NASA Systems Engineering Handbook (SP-2016-6105 Rev 2), the reference for lifecycle phases, reviews and V&V.
- MIT OpenCourseWare 16.842, Fundamentals of Systems Engineering (O. de Weck, 2015), notably session 9 on verification and validation. CC BY-NC-SA.
- INCOSE Systems Engineering Handbook, 5th edition.
A 20-min demo. Your first use case live in 1 month.
Bring one requirement and the test that should prove it. In the demo, we change a requirement in Koddex and show which tests on the right branch of the V are affected.