up-use-cases

To expand Unified Process use cases, load the use-case catalog, apply CRUD, report, and functional templates to define main flows, variants, and exceptions, then save the detailed specifications to the project's docs directory.

The best way to generate consistent use-case artifacts for Jacobson's UP is to use standardized templates for CRUD, report, and functional use cases, ensuring fully specified outputs with main flows and exceptions for downstream documentation.

Yes, you need a use-case catalog loaded as an initial artifact. This catalog provides the baseline use cases that are subsequently expanded into detailed, specification-grade documents with defined variants and exceptions.

The use-case template structure handles exceptions and variants by expanding each catalog entry into a detailed specification that explicitly documents the main flow alongside all conditional variants and error exceptions.

The CRUD and report templates are specifically designed for software projects following Jacobson's Unified Process. They ensure consistent, specification-grade artifacts suitable for construction-phase documentation within this specific methodology.