Artifact: System Use-Case Statechart Diagram
This artifact is the formal representation of the use-case block state-based behavior.
Domains: Systems Requirements
Purpose
  • To capture a formal representation of the use-case block behavior.
  • To provide the means to verify and validate a use-case through model execution.
Relationships
Description
Main Description

A Statechart Diagram describes the state-based behavior of a block. It aggregates the information from both the activity diagram (functional flow) and the sequence diagrams (interactions with the environment), and adds the event-driven block behavior to the diagram. As the "language" of statecharts is formally defined, the correctness and completeness of the resulting behavior can be verified/validated through model execution.

Statechart diagrams are finite state machines that are extended by the notation of Hierarchy and Concurrency. Basically, a statechart diagram is comprised of a set of states joined by transitions and various connectors. An event may trigger a transition from one state to another. Actions can be performed on transitions and on state entry/exit.

The Use-Case Block Statechart Diagram must reflect the functional flow captured in the use-case black-box activity diagram as well as the associated use-case black-box sequence diagrams.

Tailoring
Impact of not havingIf the use case behavior is not captured through the Black-Box Statechart Diagram, it is not possible to verify/validate the completeness and correctness of the functional system requirements that are allocated to the use case.
Representation OptionsThis diagram is usually represented as a UML/SysML state machine diagram.