A path, not a paragraph
A use case is modelled as an ordered path across the components that serve it. That makes the requirement structural: you can see which components are load-bearing for it and which are not involved at all.
Coverage becomes visible
When paths are modelled, gaps show up — a step with no component to serve it, or a component no use case passes through. Both are worth knowing before build starts.
Feeds simulation and review
Paths give the simulation a realistic set of flows to exercise, and give a reviewer a concrete question to assess the architecture against rather than a general impression.
What this covers in the product
Every capability below is part of this area of Yantra Studio.
- Use cases
- Use case path editor
Questions
How is a use case different from a sequence diagram?
A sequence diagram models the ordered interaction in detail. A use case path models which components a capability depends on, at a coarser grain.
Can gaps be detected?
Yes — steps without a serving component, and components no path reaches, are both visible.
Does it connect to simulation?
Paths describe realistic flows, which is what a workload simulation needs to be meaningful.
Related capabilities
-
Interactions, in order, as a first-class model
Model interactions as sequence diagrams with participants, steps, segments and activations, and present a diagram as an ordered walkthrough.
-
Simulate the architecture before you build it
Run workload simulations against your architecture, detect bottlenecks, score resilience, inject failure with chaos scenarios and get ranked recommendations.
-
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.