Function Development with PREEvision PREEvision User Day 2019 V6 | 2018-02-06 Agenda u Overview Function Development Today Function Development in the Future Summary and Next Steps 2/36 Overview Top Level Automotive Design Flow Data Management, Collaboration, Platform Management, Safety, Change Management Requirements Engineering and Management Functional SOA Software Architecture Design Design Design Physical Physical Physical COM Architecture Architecture System Design Evaluation Design Design WH WH Series Architecture Design Design Test Engineering and Management 3/36 Overview Top Level Automotive Design Flow Data Management, Collaboration, Platform Management, Safety, Change Management Requirements Engineering and Management Functional SOA Software Architecture Design Design Design Physical Physical Physical COM Architecture Architecture System Design Evaluation Design Design WH WH Series Architecture Design Design Legend: Tasks of Function Designer/ Test Engineering and Management System Responsible Interactions 4/36 Overview Function Development Flow in Detail Function Designer/ SW Architect SW Developer Component Supplier Test Engineer System Responsible Functional System SW Comp. SW Software Architecture Architecture Architecture Component Design Design Design Design SW E/E Architect Implemen- Component tation Physical Physical and System COM Architecture System Test Design Design Design HW Component Implemen- WH WH Series HW Design tation Architecture Design Design Component Specifications: Legend: Tasks of u REQ SPEC DOC Function Designer/ u REQIF WH Architect Communication Designer Component System Responsible Responsible u ARXML u TEST SPEC DOC Interactions 5/36 u … Overview Functional Architecture Design and Physical System Design Tasks of the Function Designer: Tasks of the System Responsible: u Functional Architecture Design u Physical System Design u Logical function design from the sensors to u Map function components to HW components the actuators u Define component software and component u Behavior design of logical function hardware needs from system perspective components u Define communication needs u Functional safety concept u Define wiring harness needs u Functional diagnostics concept u Define system variants u Provide system test specifications u Implementation Planning and Tracking u Plan stepwise implementation in line with vehicle network and component releases u Provide staged system and component Function Designer/ System Responsible specifications 6/36 Agenda Overview u Function Development Today Function Development in the Future Summary and Next Steps 7/36 Function Development Today Physical Architectures Today: Design Space for Function Development Physical Architecture Design E/E Architecture: SW Architecture: Software Platform: u Onboard u Signal-oriented u AUTOSAR Classic Design Workflow AUTOSAR Classic „service oriented“ u Service-oriented (only for Ethernet and Diagnostics) Design Workflow AUTOSAR Classic „signal oriented“ AUTOSAR Classic E/E Architect 8/36 Function Development Today Feature List, Feature Model or Feature Dependencies as Starting Point Functional Architecture Design u The Function Designer considers and extends the Feature Model Feature Model of the vehicle family under development: u Vehicle features - can be experienced by the vehicle user u Safety features u Technical features u Feature Dependencies u Most relevant are: u Exclusive OR (Xor) u Needs (Req) u Optional u Feature Chains u Needs/needed by Function Designer/ System Responsible 9/36 Function Development Today Logical Architecture Design and Mapping of Functions to Components Functional Architecture Design AUTOSAR Classic Ports are used: u Sender/Receiver Ports and interfaces Physical System u Client/Server Ports and interfaces Design Example: u Distributed function u implemented with a CAN network u specified with Sender/Receiver Ports. The Function Designer defines … u … the logical functions from Onboard the sensors to the actuators u … the functional safety and functional diagnostics concept Function Designer/ u System Responsible … the mapping of the functions to the E/E components. 10/36 Function Development Today Logical Architecture Design and Mapping of Functions to Components Functional Architecture Design u The result is the System/Component Matrix: Component System X System Y System Z … ECU A X X Sensor A11 Component System X System Y System Z … Senser A12 X ECU A Function Y1 Function Z3 ECU A1 X X Sensor A11 Actuator A11 X Senser A12 Sense Z1 Sensor A21 X ECU A1 Function X3 Function Z2 ECU A2 X Actuator A11 Actuation X4 Actuator A21 X Sensor A21 Sense X1 … ECU A2 Function X2 Actuator A21 Actuation X5 … Function Designer/ System Responsible Note: u Unclear Responsibilities become obvious! 11/36 Function Development Today Logical Architecture Design Functional Architecture Design Dedicated Modeling Concepts in the Logical Architecture: u Different block types > Sense, Logical Function, Actuation > Building Block, Logical Domain > Environment Function, … u Type/Instance concept u Activity Chain > they can overlag > often used to map Functionality to Customer Features Function Designer/ u Logical Function Package System Responsible u Ports and Assembly Connections > Sender/Receiver Ports, Client/Server Ports > Environment Ports, … 12/36 Function Development Today Behavior of Logical Functions Functional Architecture Design u The Function Designer defines also the behavior of the Logical Functions. u This is supported with UML State Diagrams. u Data Elements of Sender Receiver interfaces assigned to Ports of the Logical Function can be used in the Transition Conditions of the State Machine. u Also the Behavior of Software Components can be specified with State Diagrams. u Further UML Diagrams for behavior specification are on the PREEvision Roadmap! Function Designer/ System Responsible 13/36 Function Development Today Wiring Needs for Physical Systems Physical System Design u The System Responsible has to define the needs for the Wiring Harness Design u especially the wiring needs for sensors and actuators u possible with the Schematics Layer u In the Schematics Diagram the needed pins of the components and the schematic connections can be specified. u Of course, the pins of the components need to be coordinated with the Component Responsible. u Also variants have to be considered. Function Designer/ System Responsible 14/36 Function Development Today Interaction with Component Specification Component HW Design u The Component Responsible defines: Component Diagram: u … the internal component structure u … the headers and the pins of the component Component Responsible 15/36 Function Development Today Variants of Logical and Physical Systems Functional Architecture Design u Design Space is always a Product Line u Widely accepted Variant Management Approach: u Take care only for the differences of the variants, … u … not for the commonalities (default) u By defining Variation Points with u Variation Point Sets and u Variant Conditions u based on System Constants and Literals Compact Class Function Designer/ System Responsible Common Compact Class only Middle Class only Middle Class 16/36 Function Development Today Design Workflows (1/2) Alternative 1 Design Workflow AUTOSAR Classic „signal oriented“ Functional Software SW to HW COM Architecture Design Mapping Design Design u Abstract functional design No direct contribution to the vehicle u Concrete SW design Often done at suppliers, often only top compositions defined by OEM u SW to HW mapping Clearly the OEMs responsibility u Communication design Clearly the OEMs responsibility u Abstract logical function design: u Independent of implementation and highly reusable! u … but often we see low motivation to maintain. 17/36 Function Development Today Design Workflow (2/2) Alternative 2 Communication Functional Design Function to HW Architecture Mapping Design Software Design u Concrete functional design Direct contribution to the vehicle, high motivation to maintain u Function to HW mapping Clearly the OEMs responsibility u Communication design Clearly the OEMs responsibility u High level SW design Mostly done for the complete vehicle by the OEM (top compositions per ECU) u Detailed SW design Optional: for inhouse development needed, ohterwise at the supplier u Concrete logical function design – including deployment aspects – drives communication u Communication design and SW component design in parallel u The more agile approach: u Detailed SW design can be changed as long as network communication is not affected! 18/36 Agenda Overview Function Development Today u Function Development in the Future Summary and Next Steps 19/36 Function Development in the Future Physical Architectures in the Future: A bigger Design Space (1/2) Physical Architecture E/E Architecture: SW Architecture: Software Platform: Design u Onboard u Signal-oriented u AUTOSAR Adaptive AUTOSAR Adaptive u Offboard u Service-oriented u AUTOSAR Classic u Other Platforms u High Performance Computers AUTOSAR Classic E/E Architect 20/36 Function Development in the Future Physical Architectures in the Future: A bigger Design Space (2/2) Functional Architecture Design Many new options for Function Development Physical u Use and integrate Services in the Backend System Design u Run Algorithms with high performance needs on the High Performance Computers u Update Functions over the air on AUTOSAR Adaptive ECUs u Run safety relevant Functions on AUTOSAR Classic ECUs u Provide remote Diagnostics