Requirements#
Diagnostic and Fault Management#
SOVD Standard
|
status: valid
security: YES
safety: QM
|
||||
The SOVD implementation shall conform to the SOVD standard as defined in ISO/DIS 17978 (or the latest available draft or final publication). |
|||||
SOVD Server
|
status: valid
security: YES
safety: QM
|
||||
The diagnostic system shall include a central SOVD server that exposes diagnostic functionality via a standard REST interface. |
|||||
SOVD Configuration
|
status: valid
security: YES
safety: QM
|
||||
The system shall provide configuration management for SOVD components, including protocol parameters and security settings. |
|||||
SOVD Server Configuration Integration
|
status: valid
security: YES
safety: QM
|
||||
The SOVD server shall integrate with the S-CORE Configuration Manager to support runtime access and modification of configuration data. |
|||||
SOVD Server Authentication Integration
|
status: valid
security: YES
safety: QM
|
||||
The SOVD server shall enforce access control and validate client credentials. |
|||||
SOVD Gateway
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a SOVD gateway to route diagnostic requests between different network domains and protocols. |
|||||
SOVD Client
|
status: valid
security: YES
safety: QM
|
||||
The system shall provide a SOVD client to allow external applications to communicate with the SOVD server. |
|||||
SOVD Client Deployment Core
|
status: valid
security: YES
safety: QM
|
||||
The SOVD client shall be designed as a reusable core component that can be deployed in off-board, on-board, or cloud environments. |
|||||
Diagnostic Service Application
|
status: valid
security: YES
safety: QM
|
||||
The diagnostic system shall include a base service application (AKA routine) that is triggered by the SOVD Server and used to derive custom service applications. |
|||||
OEM Diagnostic Plug In
|
status: valid
security: YES
safety: QM
|
||||
The diagnostic system shall provide a plug-in mechanism to include OEM-specific features. |
|||||
Diagnostic Fault Library
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a fault reporting library that provides an interface for applications and platform components to report diagnostic faults including metadata. |
|||||
Fault Library Catalog
|
status: valid
security: YES
safety: QM
|
||||
The fault library shall provide the ability to define faults via a component fault catalog for the scope of the respective parent component. |
|||||
Fault Library Debouncing
|
status: valid
security: YES
safety: QM
|
||||
The fault library shall support configurable error debouncing. |
|||||
Diagnostic Fault Manager
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a central diagnostic fault manager that aggregates data from fault libraries, provides DTC status to the SOVD server, and interfaces with a persistent diagnostic database. |
|||||
Fault Catalog Aggregation
|
status: valid
security: YES
safety: QM
|
||||
The Diagnostic Fault Manager shall be configureable via the aggregated fault catalog derived from all fault libraries in the system. |
|||||
Diagnostic Database
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a diagnostic database to store DTCs, occurrence counts, and associated metadata for fault events. |
|||||
Diagnostic Database Persistence
|
status: valid
security: YES
safety: QM
|
||||
The diagnostic database shall store all diagnostic data persistently. |
|||||
Classic Diagnostic Adapter
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a classic diagnostic adapter to translate SOVD requests into UDS commands. |
|||||
Classic Diagnostic Adapter ODX Configuration
|
status: valid
security: YES
safety: QM
|
||||
The classic diagnostic adapter shall support configuration via ODX files that describe the UDS command mappings and behavior per ECU. |
|||||
UDS to SOVD Proxy
|
status: valid
security: YES
safety: QM
|
||||
The system shall include a proxy to translate UDS diagnostic requests to SOVD protocol requests. |
|||||
UDS2SOVD Proxy ODX Configuration
|
status: valid
security: YES
safety: QM
|
||||
The UDS2SOVD proxy shall support configuration via standardized ODX files to define which SOVD services are exposed via the UDS interface. |
|||||
Diagnostic system internal communication
|
status: valid
security: YES
safety: QM
|
||||
All internal communication between diagnostic components that do not use UDS or SOVD protocols shall be implemented using the S-CORE::COM middleware. |
|||||