how to get ISO 26262 certification when your test suite wasn't built for compliance from day one?
We're a 22-person NEV startup and our software team is made of 6 people. We built and tested the HMI stack in about 10 months which felt like a win. We thought the hard part was done. Then we hit ISO 26262 ASIL-B certification.
The software works and test results are clean. but the traceability documentation, requirements mapped to test cases mapped to evidence artifacts has to be produced manually. We don't have a dedicated QA team and we don't have a technical writer with embedded experience. We have engineers who build things, and for the last 11 weeks some of them have been producing spreadsheets for auditors instead.
The manufacturing partner is waiting on us and our commercial pilot keeps slipping because we can't give anyone a confident timeline.
We started looking at whether any tooling could help, polarion, codebeamer, doors next are the obvious ones for requirements traceability, askui has a docgen layer that claims to generate traceability output from existing test artifacts rather than re-entering everything manually. We’re still evaluating, nothing deployed yet.
What I haven't figured out yet is that most of these tools assume you set up the requirements traceability infrastructure before the project, not 10 months in when you're trying to certify something already built.
Has anyone gone through ASIL certification at a startup without a compliance team already in place? specifically curious how you handled the traceability documentation when the test suite existed but wasn't built with certification in mind from day one.