Practice packs
A practice pack carries the principles, viewpoints and standards of an established way of working, so a new model starts inside the practice rather than being retro-fitted to it at review.
Budget attached to the design
Cost is estimated against the components in the model, which means the number moves when the architecture does — and a design conversation can include what an option costs while the option is still open.
Checked at review
Principle compliance evaluates the model against the practice, and the result is available at review time along with validation findings and non-functional results.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Practice Pack
- Budget
- Principle Compliance
- Policy & Standards
Questions
What is in a practice pack?
The principles, viewpoints and standards that define a way of working, applied to the model.
How is budget calculated?
Against the components in the model, so the estimate changes as the architecture does.
Is principle compliance enforced?
It is evaluated and reported alongside validation at review time.
Related capabilities
-
Non-functional requirements attached to the architecture
Track non-functional requirements against the architecture, report technical debt, view the model through stakeholder viewpoints and check principle compliance.
-
Diagrams that go through review, not around it
Put architecture diagrams through a real approval workflow: draft, review, approved, with reviewers, an audit log and validation gates that block submission.
-
Standards that are enforced, not published
Define naming standards, validate the model against them, produce a health report, and enforce the same rules in CI so violations fail the build.