KomAInu Individual
Drop in a spec and start on your own requirements today. No demo, no setup.
See KomAInu IndividualEvery requirement covered. And the proof to show it.
KomAInu proves, requirement by requirement, that each one is covered by the right tests, and shows exactly where it is not. Evidence you can put in front of an auditor.
The work is done. Proving it is another job.
Your tests ran and your requirements were reviewed. But showing that every single requirement is covered, by the right test, still means going through them one by one.
One requirement without proof is all an auditor needs to find.
Then the finding lands on your desk, the certification date slips, and weeks go into proving what you had already done.
Evidence that builds itself, and holds.
The matrix, built for you.
Every requirement linked to the tests that verify it, with the reason for each link, so the coverage is proven, not declared.
Every gap before the audit.
Missing, weak and false-positive coverage shown requirement by requirement, while there is still time to fix it.
The impact of each change, instantly.
When a requirement moves, see which tests and links it touches instead of reopening the whole matrix.
Evidence ready for the authority.
Coverage and traceability exported in a form your quality team and the certification authority can review.
Start alone, or bring the whole team.
KomAInu Enterprise
Connected to your tools, in our EU cloud or on your premises, air-gapped if needed.
See KomAInu EnterpriseV&V as a Service
Our teams run reviews, test design and evidence alongside your team.
See V&V as a ServiceForward Deployed Engineering
We install the models on your infrastructure and build the workflow you need.
See Forward Deployed Engineering
Where IVVQ teams start.
- Build the traceability matrix for a milestone.
- Prepare a DO-178C, ISO 26262 or EN 50128 audit.
- Run an impact analysis after a spec change.
- Take over a program mid-way.
What makes it different.
Deterministic
The same results on every run, so every output can be reviewed and audited.
Human in the loop
Nothing is approved without an engineer. KomAInu proposes, you decide.
Fits your workflow
DOORS, Polarion, Jira, Xray, GitHub: it plugs into the tools you already use.
Your data stays in Europe
European company, hosted in the EU, or on your premises and air-gapped.
Built by critical-software engineers
Made by software engineers who shipped critical software under DO-178C.
Questions from IVVQ teams.
What is IVVQ?
IVVQ stands for Integration, Verification, Validation and Qualification: the activities that prove critical software meets every requirement before certification. Our IVVQ guide covers it in detail.
How does KomAInu build the traceability matrix?
It reads your requirements and your tests, proposes the links between them with the evidence for each link, and flags requirements with no or weak coverage. Engineers review and approve the links.
Will a certification authority accept the evidence?
The authority assesses your process and your evidence, not the tool. KomAInu produces traceability and coverage evidence that engineers review and sign, so it fits into your existing verification process.
How does it compare to DOORS or Orcanos?
DOORS and Orcanos store and manage traceability that people create. KomAInu proposes the links and finds the gaps, and works alongside the tool you already use. See our Orcanos comparison for details.
Is KomAInu a qualified tool under DO-330?
No, and it does not need to be. Like a colleague's work, everything KomAInu proposes is reviewed and approved by your engineers, so verification credit rests on your reviewed process.
Can it run on premises or air-gapped?
Yes. KomAInu Enterprise runs in our EU cloud, on your premises, or fully air-gapped, with the model you choose.
Your next audit? See the gaps before they do.
Drop in your requirements and tests. See which requirements are covered, which are weak and which have no test at all.
Lumen Rail › Door control
Dashboard
78%
covered
Covered115
Partial21
Uncovered12
Tests linked
212
Tests missing
33
Requirements 148
- DCU-SYS-014The door control unit shall prevent door opening while train speed is above 3 km/h.4 tests
- DCU-SYS-022The doors shall reopen when an obstacle is detected during closing.1 tests