A launch date that will not move, and a coverage figure nobody can produce.
Requirements moved out of spreadsheets into items linked to the components and tests that satisfy them, with coverage computed live — and not one CAD tool was replaced.
- Solvane Medical
- Programme Lynx
- 🧩Modèles
- 📋Exigences système
- exigences184
- tests_verification151
- 🧱Nomenclature
- 🗂️Dossier de conception
EXG-044 — Débit sanguin régulé à ±5 %
- reference
- LYNX-EXG-044
- type_exigence*
- Performance
- criticite*
- Critique
- composant_satisfaisant*
- CMP-07 — Pompe péristaltique
- test_de_verification*
- TST-081 — Essai de régulation de débit
- statut*
- Vérifiée
- couverture_enfants
- 100 %
Le débit sanguin doit rester dans une bande de ±5 % de la consigne sur toute la plage de fonctionnement. Vérifié par l'essai TST-081 sur trois unités de série, à trois consignes.
| Name | type_test* | resultat* | statut* |
|---|---|---|---|
| TST-081 — Essai de régulation de débit | Performance | Conforme | Vérifiée |
| TST-082 — Dérive sur 6 heures | Endurance | Conforme | Vérifiée |
| TST-090 — Reprise après alarme | Sécurité | En cours | À rejouer |
The customer's workspace, anonymised. Real structure, fields and states.
Anonymised at the customer's request. The company, the device and every figure are changed. The constraint, the launch pressure and the model are as they were.
The requirements exist. Whether they are covered is a matter of opinion.
A backbone beside the CAD, not instead of it.
Requirements in spreadsheets
One file per discipline, updated by hand. A requirement can be satisfied twice, or not at all, and the file will not say.
A requirement is an item
Typed, owned, revisable, and linked to the components and tests that answer it. One place, not one file per discipline.
A launch date that will not move
Any tool that needs a quarter to be useful is not a candidate. The decision window is measured in weeks.
Coverage is computed
The share of requirements with a verified test rolls up the tree. Gaps appear on day one instead of at submission.
The CAD stack is not negotiable
The team will not migrate its design tools before a launch. Anything asking them to is refused on the spot.
CAD stays where it is
Components reference the CAD artefacts rather than containing them. Nothing in the design stack had to move.
Five objects, and the only new habit is linking instead of copying.
- Solvane Medical
- Programme Lynx
- 🧩Modèles
- 📋Exigences système
- exigences184
- tests_verification151
- 🧱Nomenclature
- 🗂️Dossier de conception
EXG-044 — Débit sanguin régulé à ±5 %
- reference
- LYNX-EXG-044
- type_exigence*
- Performance
- criticite*
- Critique
- composant_satisfaisant*
- CMP-07 — Pompe péristaltique
- test_de_verification*
- TST-081 — Essai de régulation de débit
- statut*
- Vérifiée
- couverture_enfants
- 100 %
Le débit sanguin doit rester dans une bande de ±5 % de la consigne sur toute la plage de fonctionnement. Vérifié par l'essai TST-081 sur trois unités de série, à trois consignes.
| Name | type_test* | resultat* | statut* |
|---|---|---|---|
| TST-081 — Essai de régulation de débit | Performance | Conforme | Vérifiée |
| TST-082 — Dérive sur 6 heures | Endurance | Conforme | Vérifiée |
| TST-090 — Reprise après alarme | Sécurité | En cours | À rejouer |
What we modelled
Requirement, component, test
The chain a spreadsheet cannot hold: what satisfies this requirement, and what proves it.
Coverage, by requirement type
The figure that used to be an opinion. The right-hand column is computed from the links, not typed.
| Type d'exigence | Exigences | Tests liés | Couverture |
|---|---|---|---|
| Performance | 48 | 48 | 100 % |
| Fonctionnelle | 86 | 81 | 94 % |
| Sécurité | 31 | 31 | 100 % |
| Interopérabilité | 19 | 12 | 63 % |
ƒ Couverture is computed by Koddex, not typed by anyone.
One requirement, in full
Débit sanguin régulé à ±5 %
LYNX-EXG-044- type_exigence
- Performance
- composant_satisfaisant
- CMP-07 — Pompe péristaltique
- test_de_verification
- TST-081
- couverture_enfants
- 100 %verified children / total children
What the graph computes
The number the launch review asks for. Previously an estimate; now a value that cannot disagree with the links under it.
Effort spent proving something nobody asked for. A spreadsheet hides this entirely.
Requirements linked to the components and tests that answer them, with coverage computed.
Coverage stopped being something people argued about.
| Before | After | |
|---|---|---|
| Where a requirement lives | A row in one of several files | An item, linked both ways |
| Coverage | An estimate before each review | A computed column |
| Gaps | Found at submission | Visible on day one |
| The CAD stack | A migration nobody would sign | Referenced, untouched |
| Audit history | File modification dates | Per user, per item, per attribute |
Three things worth knowing before you defend this internally.
It is not a CAD tool
Geometry stays in the design stack. Koddex references the artefact and holds the requirement, the test and the link — which is exactly why it could be adopted before a launch.
Coverage only counts what is linked
A requirement with no test attached counts as uncovered, which is the point — but it means the first weeks show a worse figure than the spreadsheet did.
Importing is not free
Moving a requirement set out of spreadsheets is quick; deciding what each row actually meant, where two files disagreed, is not.
Frequently asked questions
Do we have to replace our CAD tools?
No, and that was the condition of the engagement. Components reference the CAD artefacts rather than containing them, so the design stack is untouched and the requirement backbone sits beside it.
Why did coverage get worse at first?
Because it became real. A computed figure counts only requirements with a verified test attached; the spreadsheet counted rows somebody had marked done. The gap between the two was the point of the exercise.
Is this fast enough before a launch?
The model and the first import are a matter of days. What takes longer is settling the requirements the spreadsheets disagreed about — and that work has to happen either way, before or during the submission.