Why Nastavia Is Moving Requirements Engineering to NaviMArc
Requirements engineering must serve several audiences at once. Business owners need to express their needs and review proposed requirements. Subject-matter experts need enough detail to assess completeness and accuracy. Technical teams need a specification they can use to design and implement a solution. Throughout this process, decisions, dependencies and changes must remain traceable.
Nastavia has migrated its requirements engineering approach to NaviMArc, the Nastavia Machine-Actionable Architecture, to bring these needs together within a common specification model. Its first complex Terms of Reference delivery, covering both Stakeholder Requirements Specification (StRS) and System Requirements Specification (SyRS) levels, provided an opportunity to apply the approach in a real, multi-stakeholder business environment.
The central idea is straightforward: a specification can have a formal, machine-actionable foundation while remaining accessible to the people who define, review and approve it.
NaviMArc uses a canonical XML representation to preserve object identity, classification, hierarchy, relationships and traceability. Requirements therefore retain an explicit place and meaning within the model. This structure provides a controlled foundation for generating working views, examining dependencies and carrying requirements forward into subsequent engineering activities.
Business stakeholders interact with that foundation through familiar tools. NaviMArc is designed around bidirectional projection between the canonical specification and Microsoft Excel or Google Sheets. Requirements appear as ordinary tables that people can filter, review, edit and comment on. Structured model data can be rendered into these working views, while controlled changes made in the views can be synchronized back into the canonical model.
This matters because collaborative review is an essential part of requirements engineering. A formal structure becomes much more useful when business owners and specialists can participate through tools they already understand. NaviMArc brings that participation into the specification architecture itself.
Tables also have their limits. Context, rationale and explanatory material often need connected prose. NaviMArc accommodates this through embedded Markdown blocks, keeping narrative content alongside structured requirements within the same architecture. The specification can therefore preserve both the formal relationships between requirements and the explanations needed to interpret them.
This approach also creates a useful foundation for AI-assisted development. Explicit identities, classifications and relationships give downstream tools a more controlled basis for processing specifications. Human review remains essential, but more of the specification’s structure is available directly for tools to use.
For Nastavia, the value is practical: business collaboration and formal requirements engineering can operate around the same persistent source of truth. Documents and tables become useful representations of that specification, supporting different audiences and stages of work.
The successful delivery demonstrates the principle behind NaviMArc: machine-actionable requirements can remain approachable for business stakeholders. By combining familiar working tools with a controlled semantic foundation, Nastavia is strengthening the connection between business intent, collaborative review and technical execution.