Business design · Publisher: Legra
Connect business goals to the people, actions, and tests that deliver them.
For teams designing how their business works. Build a shared model of use cases, expected outcomes, personas, and Stories. Connect each action to the concepts it uses and the tests that describe a correct result.
Both contribute to the outcome: A quote supported by checked information.
What this use case is intended to help your team achieve.
Business owners and delivery teams need a common account of what should happen. Connect the intended result to the people responsible and the work they may perform. Each contributing use case should explain how it helps deliver the wider outcome.
When a requirement changes, review the affected Stories, concepts, and tests together. Agree what success looks like before promoting the change. The expected result is a reviewed model that remains connected to the work it describes.
Break a broad capability into smaller, reusable use cases. Outcomes explain why the work matters. A Story describes an action for one persona; its inputs, outputs, and tests make the expectation concrete.
Define the outcome → Connect the contributing work → Describe actions and tests → Review a proposed change.
See Executable Use Cases for the execution model.
A lending team wants quotes based on checked application information. It defines the income check, the officer who performs it, and the evidence the check needs. A test describes the expected answer for supplied inputs. The team reviews changes on a branch before sharing the updated model.
Semantic Modelling supplies the concepts and constraints used by these definitions. Business specifications by example describes the shared tester. Read Business Intent for the connected approach.
Curated public overview. Legra is pre-MVP; this page is not a live registry record. Read about package adoption.