Requirements, models & knowledge

Write it down once, connect it forever

Business model, requirements, diagrams and documentation are first-class records in Studio, with explicit traces between them. When something changes, you can see what else is affected.

Business first, then the system

From business actors to system requirements

Describe the business (actors, processes, rules) before the software. Then capture system actors, use cases and functional and non-functional requirements, each with a state, a priority, a risk and an owner.

  • Lifecycles with explicit transitions: draft, in review, approved, baselined
  • Decisions, risks and standards as records too
  • Revisions of every change, with who and why
Requirements, use cases and actors of a Development
BPMN

Model processes in standard BPMN

A full BPMN 2.0 modeler (bpmn-js) runs inside Studio. Diagrams are records with revisions and moderation, and their elements can link to the actors, rules and use cases they represent.

  • Safe SVG previews you can open with clickable links
  • Embed any diagram in an article or a description
A BPMN diagram of claim intake in Divengine Studio
UML

UML as text, rendered in your browser

Write PlantUML in a split editor and see the diagram live: use cases, classes, sequences, states, components. The engine runs in the browser, and bound elements link to real records.

More notations are on the roadmap: Mermaid, DMN, ArchiMate, CMMN, IFML and Excalidraw.

A UML use case diagram written in PlantUML
Knowledge base

Documentation that knows what it talks about

Write articles in a tree per Development: overviews, architecture, how-tos, onboarding. Mention [[REQ-0001]] or [[UC-0002]] and the text links to the record, which lists the article under “Mentioned in”.

  • Hierarchy of articles with sections and sub-articles
  • Diagrams embedded in the text, always up to date
  • Access follows the Development
A knowledge article linking to requirements and use cases
Traceability

Traces you decide, not guesses

A trace is an explicit, typed link between two records, with a rationale. Studio never infers them, so you can trust them in a review or an audit.

Typed

Refines, realizes, implements, verifies, depends on, mitigates… with rules about what can link to what.

Everywhere

Requirements, models, tests, tasks, articles, repositories and databases.

Verification

Tests that verify a requirement show up in readiness and coverage.

Baselined

Baselines freeze the traces too, not only the documents.

Then prove it works

Requirements earn their place when tests verify them.