Reverse EngineeringIn production

Legacy ECU code in. ASPICE-ready design documents out.

A fault-tolerant C/C++ parser: no build system, no compiler.

Reverse Engineering Scan tab

One run on the bundled demo project

  • 154

    C files scanned

  • 1,302

    functions documented

  • 1,867

    types

  • 1,041

    component interfaces

  • 389

    exact design↔code trace links

  • 1,757

    diagrams generated

  • 3.7

    seconds — scan and static analysis

3.7 s covers scan and static analysis only — not document generation, diagram rendering or engineer review.

The problem

The code shipped. The design documents didn’t.

  • ASPICE demands evidence

    SWE.2 and SWE.3 require architecture and detailed design.

  • Manual documentation doesn’t scale

    Stale after the next merge.

  • Legacy code won’t even build

    Compiler-based tools stop there.

How it works

Four steps from source to documents.

  1. Group

    Proposes a component tree from your folders.

  2. Scan

    Reads C/C++ without compiling it.

  3. Analyze

    Call graph, interfaces, metrics and deterministic IDs.

  4. Generate

    SAD, SDD, diagrams and the trace matrix.

Product tour

From scan to document — inside the tool.

Scan tab: functions and log
Functions with document IDsScan log: 154 files, 151 warnings
SDD Preview: Markdown beside the rendered document
Markdown and rendered preview, side by sideExport straight to Word
SAD Preview: logical architecture and component tables
Architecture from the real include and call structureJudgement calls marked To be determined
RE4A Reverse Engineering — Generate
Generate tab: document, ReqIF and Enterprise Architect exports
One hub for every output

The parser

It reads the code the compiler refuses.

The issue log from that run

0errors

151warnings

Each carries its file, line, offending code and a fix hint. No silent guessing.

RE4A Reverse Engineering — Issues
Issues tab of the scan
No build system, no compilerAUTOSAR Classic macro patternsFault tolerant, not silent

What you get

Seven outputs from one run.

Native Open XML Word output — no Office automation.

RE4A Reverse Engineering — Output folder
  • SAD.md / .docx
  • SDD.md / .docx
  • traceability.csv / .md / .docx
  • diagrams/**.puml + .png
  • metrics.csv
  • issues.csv
  • model.xml

Traceability

Design traced to code — to the file and line, both ways.

Synthetic sample
Design elementKindSource fileLineCounterpartDirectionStatus
HwCore_IF_001SAD interface · providedHwCore.c139HwCore_SDD_API_001design to codeExact
HwCore_SDD_API_001SDD APIHwCore.c139HwCore_IF_001code to designExact
HwCore_IF_002SAD interface · providedHwCore.c164HwCore_SDD_API_002design to codeExact
HwCore_SDD_API_002SDD APIHwCore.c164HwCore_IF_002code to designExact
StartupMain_IF_001SAD interface · requiredStartupMain.c963StartupMain_SDD_API_008design to codeExact
StartupMain_SDD_API_008SDD APIStartupMain.c963StartupMain_IF_001code to designExact

Integrations

Exports to Word, Enterprise Architect and ReqIF.

  • Stable IDs

    Unchanged elements keep their IDs across runs.

  • A command-line interface

    The same run, from the command line.

  • Exports

    Diagrams also ship as editable PlantUML source.

  • Push to Polarion or codeBeamer

    One-way and idempotent: re-runs never delete.

Polarion · codeBeamer — one-way push

Export to Enterprise ArchitectEnterprise Architect export dialog
Export to ALM (ReqIF)ALM export dialog

AI-assist

Let AI draft the prose. Opt-in, and off by default.

0 bytes of source code leave the machine in the default configuration.

Data policy for AI draftingIn the default configuration, drafts run on a local Ollama model. An opt-in provider receives scanned metadata only, never source code.Source codeDefault: localOllamaMetadata onlyOpt-in provider

What this page does not claim

  • Traceability is design↔code, to the file and line — not requirement-to-test traceability.
  • 3.7 s is scan and static analysis only, never an end-to-end time.
  • Figures come from one 154-file demo project on a laptop.
  • Judgement calls are marked To be determined.

Evaluate it

Bring a legacy source tree — even one that won’t build.

We scan it with you and walk through the output.