Requirements by Use Case

The following pages are a hierarchy of requirements sorted by SCMS use cases. A use case contains all requirements that must be implemented from an end entities (EE) perspective to fulfill a major feature of the SCMS. A use case might comprehend multiple steps from a system's architecture perspective that can be run without interference with each other to return a partial result of the overall use case. In general, steps need to be executed in the given order to fulfill the use case. For example, Use Case 3: OBE Pseudonym Certificates Provisioning describes all necessary processes to equip an OBE with pseudonym certificates. It comprehends five steps that are coherent but self-contained: 

• Step 3.1: Request for Pseudonym Certificates
• Step 3.2: Pseudonym Certificate Generation
• Step 3.3: Initial Download of Pseudonym Certificates
• Step 3.4: Schedule Generation of Subsequent Batch of Pseudonym Certificates
• Step 3.5: Top-off Pseudonym Certificates

This format supports end-to-end implementation as well as testing better than a pure listing of requirements.

On-board Equipment (OBE) Use Cases

The following chapters are about OBE requirements. These are the main use cases for OBEs, but there are requirements throughout all chapters for OBEs. For example, in 11. Backend Management are requirements about what an OBE needs to do if a root CA is revoked or a new root CA is introduced to the system.

• Use Case 2: OBE Bootstrapping (Manual)

• Use Case 3: OBE Pseudonym Certificates Provisioning

• Use Case 8: Global Misbehavior Detection and Revocation

• Use Case 19: OBE Identification Certificate Provisioning

Road-side Equipment (RSE) Use Cases

The following chapters are about RSE requirements. These are the main use cases for RSEs, but there are requirements throughout all chapters for RSEs. For example, in 11. Backend Management are requirements about what an RSE needs to do if a root CA is revoked or a new root CA is introduced to the system.

• Use Case 12: RSE Bootstrapping (Manual)
• Use Case 13: RSE Application Certificate Provisioning
• Use Case 16: RSE Application and OBE Identification Certificate Revocation

Common EE Use Cases

Both EE types should implement the following chapters:

• Use Case 5: Misbehavior Reporting
• Use Case 6: CRL Download
• Use Case 11: Backend Management (CA compromise recover strategy)
  
• Use Case 18: Provide and Enforce Technical Policies
• Use Case 20: EE Re-Enrollment

Backend Use Cases

Features specific only to the SCMS (no relevance to end entities) as well as deployment and management requirements are listed in the following use cases:

• Use Case 1: SCMS Component Setup
• Use Case 7: CRL Broadcast
• Use Case 11: Backend Management
  

Requirement Status

All requirements are listed with all details including their status of implementation (e.g., SCMS-500 - Getting issue details... STATUS ) and a JIRA link is given for traceability reasons. Statuses given are: