System
An optimal system design is fundamental for the successful realization of an ADF. An architecture framework for an ADF is made up of several standardized viewpoints, typically including functional, logical and physical architecture. The optimal physical architecture at the end of the definition process should be selected that implements all the stakeholder and function requirements, whilst also considering fulfilment of additional non-functional requirements that concern both the execution and evolution of the system. It is also important to identify the required interfaces between ADF, other vehicle function(s), backend solutions (including cloud services) and communication with other vehicles. A standardized logical interface layer aids in minimizing the overall development effort. With increasing complexity of the in-vehicle hardware and software, planning and performing early verification of the architecture aids in reducing the development risk and associated cost while ensuring the overall safety of the system design.
In the context of ADF, software is not static. The vehicle and the ADF should be designed in such a way as to allow for a safe and seamless update process for the user. Feature updates or software updates are an intrinsic part of the life cycle of ADF, whether for feature enhancements, security patches, or regulatory compliance. While ADFs are designed with the capability to accommodate software updates throughout their lifecycle, manufacturers also need to establish a robust framework for managing software updates that ensure compliance with both international and national regulations, including type approval requirements. Implementation of updates has been traditionally done physically, with customers having to visit the dealership for servicing. With Over the Air (OTA) updates, manufacturers have the flexibility to distribute and deliver the updates on a large scale, utilizing wireless internet connectivity to make requests to OEM cloud service via V2N to download the latest firmware or software.
The System Design category attempts to provide key considerations and guidelines for an optimal design of the supporting platform, including establishing a suitable design framework to choose the right functional, physical, logical architecture for the system, under the two sub-topics: architecture, and the implementation of updates. The architecture topic aims at highlighting fundamental steps in the development of architecture at the vehicle level. The implementation of updates topic aims to present a set of guidelines aimed at implementing software updates for the ADF.
- Requirement – Identification of V2X Interactions
- Requirement – Data Driven Development
- Requirement – Core Technical Requirements
- Requirement – Sensor Constraints and Minimal Risk Manoeuvre Design
- Ethics – Adherence to Ethical Standards
- Ethics – Compliance with Laws and Traffic Rules
- HVI – Correct Positioning of HMI
- HVI – Guidelines for the Design of HVI (in ADF)
- SOTIF – Triggering Events
- SOTIF – Driver Monitoring System
- SOTIF – Identification and Evaluation of Risks
- SOTIF – Functional and System Specification
- Cyber Security – Incident Response
- Cyber Security – Requirements Evolution through Development
- Cyber Security – Derivation of Requirements
- Cyber Security – Threat Analysis and Risk Assessment
- Cyber Security – Security by Design
- Cyber Security – Organisational Processes
- System – Rationale for chosen Physical Architecture
- System – Evaluation of Architecture Interaction within ODD
- System – Verification of Architecture Response within ODD Limits
- System – Consideration of Architecture and External Elements
- System – Safety, Security, and Maintainability Requirements in Architecture Selection
- System – Rationale for allocating Logical to Physical Architecture
- System – Quality and Safety Standards of Development Tools
- System – Adherence to International Standards in Software Update Processes
- System – Defined OTA and Software Update Strategy
- System – Compatibility of Hardware/Software for Vehicle Lifetime
- System – Identification of Software Safety Requirements at Function Level
- System – Consideration of Safety Criticality for Updates
- System – User Notification for Updates
- System – Management of Failed Updates
- System – Strategy for Ensuring Update Authenticity
- System – Method for Authorized Owner to Accept or Reject Updates
- Requirement – Identification of V2X interactions for AD Vehicles
- — Cross-References after this —
- Ethics – Consistent Consideration of ADF Benefits
- Ethics – Addressing Dilemma Scenarios in ADF Development
- Ethics – Manufacturer Documentation and Responsibility
- Ethics – Compliance with Data Protection Measures
- SDB – Availability of Tool Chain for Scenario Application
- Simulation – Research on state-of-the-art Simulation Technology
- Vdata – Data Collection for Analysis of Incidents and Accidents
- V2X – V2X Security Mechanisms for Vehicle Applications
- V2X – Suitability of V2X Technologies for Vehicle Applications
- V2X – Backward Compatibility in V2X System Evolution
- Testing – Definition Safety Validation
- Testing – Test Concept Planning
- Testing – Testing ODD
- Testing – Feasibility of Tests