Integrations

We do not sell a closed workflow. Accemic measures things on real hardware that other tools cannot measure, and hands the results to the tools you already trust.

An integration connects data and workflow; it does not automatically transfer qualification, certification or assurance status between tools. Each integration page therefore identifies the producing tool, receiving tool, transferred artifacts, identifier mapping, integrity checks and the assurance boundary; tested version combinations are stated where a released integration record exists, and pages without one describe demonstrated interoperability, not a supported version matrix.

Why that is the right shape

The tools that carry tool qualification - DO-330 TQL, ISO 26262 - represent decades of investment. Replacing them is neither realistic nor useful. What is useful is giving them data they could not previously get: coverage from the optimized executable under test, and timing from real silicon.

So the integration direction is deliberate. Accemic contributes target-derived coverage or timing evidence to established toolchains; Accemic sits upstream, and our output is an input to your existing chain. Each integration page identifies the artifacts transferred, identifier mapping, integrity checks and the boundary of any qualification or assurance claim - and names tested versions where a released integration record exists.

For toolchain partners

Accemic can be integrated as an upstream measurement service, an embedded trace source or a workflow-level acceptance component. Before implementation, we define the transferred artifacts, identifier mapping, integrity checks and the boundary of each assurance claim.

Live trace processing adds another benefit: instead of exposing only a human trace UI, the integration can expose structured execution evidence directly to downstream tools and automated development workflows.

CEDARtools.Forge extends the same principle from individual metrics to the development loop: existing tools remain in place, while their results and Accemic’s target evidence become inputs to an independent acceptance decision.

Discuss a toolchain integration

Documented partner integrations

Razorcat TESSY - Hyper Coverage

Unit-level coverage from TESSY, integration-level coverage from CEDARtools^®, merged into one picture. Presented jointly at Embedded World Conference 2026.

TimeWeaver - AbsInt

Measured execution times from real hardware feeding AbsInt’s hybrid WCET analysis. Joint paper at ERTS² 2024, and a bundle you can buy as one thing.

Documented interoperability

Teamscale - CQSE

Coverage data captured with Accemic CEDARtools^® can be transferred to Teamscale and used there for further quality analysis, visualization and test-gap analysis.

In such a toolchain the roles are the ones described above: Accemic performs the hardware-level capture of execution and coverage data, and Teamscale can serve as the downstream analysis and target system for the imported results.

Teamscale is a trademark of CQSE GmbH. It is named here solely to describe technical interoperability. There is no corporate affiliation and no express endorsement unless separately stated.

Perfetto Trace Viewer

CEDARtools.SmartTrace writes a captured trace in the .pftrace format of the open-source Perfetto viewer, which runs in the browser: function calls become slices on the timeline, traced memory accesses appear as instant events. Currently beta.

Everything else: open formats

HTML, CSV, AsciiDoc, LCOV, and Teamscale’s native line coverage format. Standard formats are used where they can represent the required result; Accemic-specific metadata is supplied separately where a standard format cannot express observation validity, MC/DC independence evidence, mapping status or provenance. The integration documentation identifies both parts.

If your chain is something we have not seen, we first look at the target format, identifier mapping, versioning and integrity checks - for many chains that assessment ends in a small export script rather than a project. Tell us what you use.