Model-based systems engineering
The model behind Holarch.
Holarch is a model-based systems engineering (MBSE) workbench. Everything in a project is an entity in one model, built on the Lifecycle Modeling Language (LML) and linked by typed relationships. Documents, diagrams, matrices and reports are views of that model, so a change made in one place shows in every view.
Class and relationship names as Holarch uses them.
What the model gives you
An LML foundation
The default schema follows the Lifecycle Modeling Language: classes such as Requirement, Statement, Action, Asset, Conduit, Input/Output, Test Case, Risk and Decision, with attributes and typed relationships between them.
Entities, attributes and relationships
Each entity has a number, name, description, labels and the attributes of its class. Relationships are typed and always have an inverse: "A decomposed by B" also means "B decomposes A".
One source of truth
Documents, FFBDs, SysML diagrams, the interface register, the RVTM, the risk matrix, charts and framework products all read the same entities. Edit an item in any view and the others update.
Traceability end to end
Trace needs to requirements, requirements to functions and components, functions to interfaces and items, and requirements to the test cases that verify them. The traceability matrix shows gaps.
Suspect links
When a requirement's text or key attributes change, its downstream links are flagged as suspect for review, with a diff of what changed.
Model checks
68 rule-based checks find orphans, actions with no performer, unbalanced inputs and outputs, requirements without "shall", and requirements that are not allocated or not verified.
Every relationship in one place
- The Database lists every entity with a query language, filters and saved queries.
- The inspector shows an entity's attributes and its relationships, grouped by type, with Add for each relationship.
- The Entity View opens one item with all of its attributes, relationships and comments.
Find gaps in the trace
- Put any two sets of entities on the axes of a traceability matrix and pick the relationship.
- Click a cell to add or remove a link. Rows and columns without links are highlighted.
- The RVTM rolls verification up per requirement: verified, failed, not run or unverified.
Built on the same model
Your own schema
Add classes, subclasses, attributes, labels and relationships for a project, and define workflows such as allowed status transitions. Other projects keep the default schema.
SysML diagrams
Block definition, internal block, parametric, state machine, use case, activity, sequence, package and requirement diagrams draw entities from the model.
DoDAF and UAF products
Framework products are views of the same entities, so they stay current as the model changes.
Baselines and history
Take project and document baselines, compare them with a word diff, and restore earlier versions.
Open formats
Export projects as JSON, requirements as ReqIF, CSV or Excel, reports as DOCX, and the schema as JSON. Import Word, Excel, CSV and ReqIF.
AI that reads the model
AI tools work on the entities and relationships of your project and preview every change. AI assistance