Platform
For product managers, project leads and compliance in fast-moving development
- Generated reports
- Continuous compliance insights
- Graph analysis
Your whole system’s traceability, in one place.
APEQS Platform connects to your Git repositories and brings every requirement, implementation and test into one shared graph. You can see what is linked, what is missing and what changed, and turn it into evidence for your compliance work without assembling it by hand.
Explorer: see the chain, one question at a time
Explorer is the graph view in APEQS Platform. Follow a requirement from the standard it addresses to the code that implements it and the tests linked to it. Each view answers one question, so the graph stays readable as the system grows.
Metamodel: your rules, checked everywhere
Your metamodel defines what a complete chain looks like, for example that every implementation must be linked to a test. It lives in your repo as
ttim.yaml, and APEQS Platform checks every connected repo against it and shows where the chain breaks.Reports you don’t have to write
Reports are generated from the graph, for auditors, assessors and managers who will never open a repo. Each report shows which repos and commit it was built from, and when.
APEQS does not certify anything. It gives you the evidence, and your people make the compliance argument.
Coverage and gaps
See which requirements have no implementation linked, which tests are not linked to any requirement, and which links no longer match the metamodel.
Coverage in APEQS is link coverage: it shows what is connected, not whether a test passed. When something is unknown, it is shown as unknown, never as zero.
What changed, and what it affects.
Because everything lives in Git, every requirement has a history. You can see who changed it, when, and which version of the code it belongs to.
When a requirement or a piece of code changes, APEQS Platform shows which other requirements and tests it is linked to, so you know what to review before you release.
Works next to what you already have
APEQS Platform starts beside your existing ALM, in one team and one repo, with no migration. Developers keep working in their own repo and editor with APEQS DevKit, and the graph stays current as a by-product of their work.