This is part 2 of the following series:

  1. Originating requirements
  2. Use cases (this document)
  3. Product requirements specification
  4. Logical and physical architecture

The document captures the high-level use cases requested by the stakeholders. To contribute more contents, review and trace each item back to the Originating requirements. Then, elaborate further in the system-level specifications.

How to use this document

The document captures missing stakeholder requirements, adds additional detail, and as a precursor to capturing engineering level requirements. Well thought out use cases allow engineering level specifications, especially functional behavior of the syste, to be created more efficiently. The document also help identify various requirements categories that need to be detailed.

This document is shared with the stakeholders to gain alignment prior to further requirements definition and analysis.

System engineering V-model. Use cases helps capture missing high-level requirements.

ucd-1: Autonomous operation

The autonomy stack supports continuous automated vehicle motion.
Vehicle operatorucd-1: Autonomous operationAutonomy stack
Use case diagram "ucd-1: Autonomous operation"

Pre-conditions

Main event flow

  1. The localization system computes a valid pose estimate.
  2. The localization system publishes the most recent pose estimate for downstream consumers.
  3. The planning system generates a trajectory from the current pose.
  4. The control system computes a control command from the selected trajectory.
  5. The vehicle actuators receive the control command.

Post-conditions

Alternate flow

Linked requirements