Logo
NeoArc Studio

Use Case Block

Document use cases with actors, preconditions, main flow steps, alternative flows, postconditions, and exception handling.

The Use Case block documents system interactions from an actor's perspective. It captures the complete flow including preconditions, step-by-step main flow, alternative paths, expected outcomes, and exception handling.

When to Use

Block Properties

PropertyRequiredDescription
Use Case IDNoUnique identifier (e.g., UC-001)
NameYesDescriptive title
ActorNoPrimary user or system initiating the use case
DescriptionNoBrief overview of the use case
PreconditionsNoConditions that must be true before execution
Main FlowNoNumbered sequence of steps in the primary scenario
Alternative FlowsNoVariations from the main flow
PostconditionsNoSystem state after successful completion
ExceptionsNoError conditions and handling
PriorityNoCritical, High, Medium, Low
StatusNoProposed, Approved, In Development, Implemented, Deprecated
Related Use CasesNoLinks to dependent or related use cases
NotesNoAdditional context or constraints

Use Case Status

Example: Customer-Facing Use Case

A typical e-commerce checkout use case.

Example: Administrative Use Case

A back-office administration use case.

Example: System Integration Use Case

A use case involving external system interaction.

Best Practices

PracticeDescription
Actor PerspectiveWrite from the actor's perspective using active voice
Atomic StepsKeep main flow steps atomic and sequential
Alternative PathsDocument all realistic alternative paths
Error HandlingInclude error handling for each potential failure
Related LinksLink related use cases for complete coverage
Consistent NamingUse consistent naming for actors across use cases
Measurable ConditionsSpecify measurable preconditions and postconditions
Stakeholder ReviewReview with stakeholders before marking as approved