usecase-driven-design

To create a use-case driven design document, follow a structured workflow that captures use cases, scenarios, domain models, state models, system boundaries, exceptions, and pre/post-conditions. Each step's output is saved as an individual Markdown file, then consolidated into a final unified design document.

Use-case driven design is a systematic approach to software design that captures requirements through structured use cases and scenarios. You need it for software projects requiring stepwise artifact generation, traceability between design phases, and consolidation into a unified deliverable.

You manage stepwise artifacts by saving each design phase output—such as domain models, state models, and use cases—as separate Markdown files. A confirmation procedure between steps ensures traceability and validates completion before progressing to the next stage.

Yes, you can integrate state models and system boundaries into a single design document. The workflow processes these elements step-by-step, saves them to individual Markdown files, and combines all generated artifacts into one consolidated final design document.

The best way to structure a requirements analysis workflow is using a seven-step process that guides you from initial use case capture through domain and state modeling to final consolidation. This approach ensures systematic capture and traceable, step-by-step artifact generation.

No specific frameworks or dependencies are required to run the use-case driven design workflow. You only need to create initial use case lists in Markdown files, such as docs/usecase/step1-usecases.md, and save subsequent step outputs as separate Markdown files before final consolidation.