Specification Management
One connected model for product behavior
Each specification describes one part of the feature and connects it to the wider model.
Requirements
User Interfaces
Data Model
API Operations
Work in a branch-aware specification context
Prepare features and corrections in an isolated project branch.
Inherited artifacts stay linked to Main until changed. Stable identities retain explicit inherited, forked, created, or deleted branch states.
People and agents read the effective state of the selected branch.
Make product relationships explicit
Link existing UI, data, and API specifications to a requirement, or create them in its context.
Requirement relations capture behavior dependencies; unit links connect specifications to implementation. Change Requests retain affected revisions.
Follow these relations to assess a feature’s impact.
Connected context
User Interface
Data Entity
API Operation
Software Unit
See the model from the angle the task requires
Move between structured tables and visual views without separating the diagram from the underlying product context.
Traceability Table
More views
REQ-1: connected screens, data entities and the technician assignment API.
Connected Specifications
More views
Assign a technician to a visit: the requirement and its connected specification keys.
User Interfaces Diagram
Entity Relationship Diagram
More views
Visit revision 2 compared with Previous: the added warranty decision rule remains readable.
Preserve what was true at every stage
Stable artifact identities connect current definitions with historical revisions.
Lock reviewed versions, create revisions, compare history, and roll back when needed.
Change Requests reference affected revisions, preserving the context behind each change.
