Seven parts. One model.
Its core is the intent layer: one verified, versioned model of a product, the processes around it and the knowledge behind them.
People and agents work with all seven through the 42 commands of one tool, and the tool describes itself to an agent that has never seen it.
Model
One verified, versioned model of the product, its processes and the knowledge behind them, such as requirements, regulations, decisions and open questions.
A domain agent reads one verified source, not scattered documents.
46 kinds of elements in nine layers, joined by 176 types of relation.
- Strategy
- Structure
- Behaviour
- Views
- Screens and scenarios
- Knowledge
- Infrastructure
- Implementation
- Operations
Check
More than 200 automated consistency rules. Contracts and code are checked against the model.
Probabilistic output gets a deterministic judge.
213 rules, each with a fixed severity. None can be switched off, so a model that passes means the same everywhere.
Trace
From regulation and requirement to code. Every step of the chain is written in the model, so the answer to why comes with its evidence.
Audit evidence comes without extra work.
One chain of a sample model, from a requirement to the specification generated for it:
- Requirementparts used are recorded
- Decisionparts used is optional
- Element of the modelvisit completed
- Scenarioa visit is completed with parts used
- Generated specificationcompleting-a-visit.feature
Change
A change, by engineer or agent, is accepted only if its declared impact matches the measured one.
A company can delegate only what it can check.
A change can carry 13 kinds of assertion about itself. See one change fail and its correction hold.
Generate
Specifications, contracts, database schemas, scenarios and documentation come from the model.
Specification and artefacts cannot drift apart, because they come from one source.
Files generated from the 14 elements of a sample model:
- 1Scenario specifications
- 4Database schema
- 2Sequence diagrams
- 1Code ownership
- 15Catalogue
- 4Documentation
Reconstruct
The model is built from scratch or from the code of an existing system. Every legacy behaviour is kept, changed or dropped by decision.
The knowledge in a legacy system does not retire with the people who built it.
With Teqsa we also build a heating-equipment manufacturer's field service system for a second country, with every legacy behaviour kept, changed or dropped by decision. See the field service system.