Certification Runs on Evidence
DO-178C and DO-278A are objective-based. Each objective demands artifacts: a requirement, a test that exercises it, a record that it ran, a measurement proving the code was reached, and an unbroken chain linking all four. Assembling that chain by hand across disconnected point tools is where programs lose months.
Qt Group supplies the whole chain:
-
Axivion verifies the code obeys its coding standard and the implementation still matches the intended architecture.
-
Coco measures how much of the code the tests actually reached.
-
Squish verifies the interface behaves as specified, on the target.
-
Test Center links every result to the requirement it satisfies and keeps the record audit-ready.
Four tools, one supplier, one evidence chain.
DO-330 Tool Qualification
Tool qualification per DO-330 is required whenever the design assurance processes in DO-178C or DO-278A are eliminated, reduced, or automated by the use of the tool unless the output of the tool is verified.
Qt Group provides Tool Qualification Kits for Axivion, Coco, and Squish.
Each kit is scoped to the customer's actual toolchain, target, and applicable standard, and produces the artifacts a certification authority expects, including a validation test suite run in the customer's own environment. Qualification is repeatable, so a tool upgrade does not force the exercise to be redone by hand.
The kits also support ISO 26262, IEC 61508, IEC 62304, and EN 50716, which matters to suppliers working across aerospace, automotive, industrial, and rail programs from one codebase.
Built for Defense Programs
Defense procurement applies constraints that civil aviation does not, and they are usually settled before the technical evaluation begins.
-
Offline installation for air-gapped networks. Axivion, Squish, Coco, and Test Center all offer offline installers and run inside the customer's own network. Programs handling classified data can develop and test without a route to the outside.
-
No requirement to hand over code. Analysis, coverage, testing, and results all stay on customer infrastructure. There is no vendor-hosted service to upload source, test artifacts, or results to, and no need to disclose project detail that classification or export control may prohibit disclosing.
-
Evidence that outlives the contract. Governments generally own the system and often the code, while the commercial entities developing and sustaining it change over a service life measured in decades. Tooling and evidence have to survive that handover. Repeatable qualification, retained test history, and architecture definitions that live with the codebase rather than in someone's head are what make that possible.
-
Component reuse across programs. Verified architectural integrity is what allows a component qualified on one program to be credibly reused on the next, instead of being re-verified from scratch.
Success Stories
Read what our customers say about our products.
“What’s really key for us, having to do end-to-end integration testing and not normally having access to all the source code, is a tool like Squish that can talk to an application on Linux and one on Windows…it provides exactly what we need.”
“With the Axivion Suite, we have significantly reduced our integration effort and integration risk.”
“We have found issues in things manual testers didn’t get to.”