Use Case Sequence Diagram

Definition

A use case sequence diagram is a bottom-level requirement diagram work product that is a bottom-level sequence diagram that documents a use case or use case path in terms of the interactions between a blackbox business enterprise, contact center, data center, application, or component and the externals (e.g., roles, organizations, applications, systems) and the externals with which it interfaces.

Objectives

The typical objectives of a use case sequence diagram is to:

• Document how something interacts with its context.

Benefits

The typical benefits of a use case sequence diagram are to:

• TBD

Contents

The typical contents of a use case sequence diagram are:

• TBD

Stakeholders

The typical stakeholders of a use case sequence diagram are:

• Producers:
  • Requirements Team
• Evaluators:
  • Project Manager
  • Technical Leader
• Approvers:
  • Project Manager
  • Technical Leader
  • Customer Representative
• Maintainers:
  • Requirements Team
• Users:
  • Architecture Team

Phases

• Business Strategy: Completed
• Business Optimization: Not Applicable
• Initiation: Completed
• Construction: Maintained
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

Use case sequence diagrams can typially be started if the following preconditions hold:

• The business strategy phase or initiation phase has started.
• The requirements team is adequately staffed and trained in requirements analysis.

Inputs

The typical inputs to a use case sequence diagram include:

• Work Products:
  • Application Vision Statement
  • Context Diagram
  • Domain Object Diagram
  • Use Case Diagram
• Stakeholders:
  • TBD

Guidelines

• TBD

Conventions

Use case sequence diagrams are typically constrained by the following conventions:

• Work Flow
• Content and Format Standard
• Inspection Checklist

Examples

• Example Use Case Sequence Diagram