E/E–Engineering with PREEvision – Status and Trends · 2018-11-29 · PREEvision as EEA/WH...
Transcript of E/E–Engineering with PREEvision – Status and Trends · 2018-11-29 · PREEvision as EEA/WH...
V1.0 | 2018-11-20
9th Vector Congress, 20th to 21st of November 2018, Stuttgart
E/E Development with PREEvision – Status and Trends
2
E/E Development with PREEvision – Status
E/E Development with PREEvision – Trends
E/E Development with PREEvision – Outlook
Agenda
3
Our Mission: From a Fragmented Tool Landscape to an Integrated SolutionE/E Development with PREEvision – Status
Tool Landscape Approach:Multiple Tools and Interfaces
> “Best in Class”> Various, not connected data silos> File based collaboration
Integrated Tool Approach:PREEvision E/E Engineering Environment
> Integrated and Model Based Design> Central backbone as “Single Point of Truth”> Data based collaboration
4
PREEvision – From an Architecture Tool to an Integrated Engineering BackboneE/E Development with PREEvision – Status
2010 “Architecture Use Case”
Evaluation of electric/electronic architectures and their architecture alternatives
Today PREEvision is the industrial standard for Architecture Design in the automotive industry
2018 Integrated Engineering Backbone
Data Model: ~4,5k classes, ~2,5k attributes, ~2,2k relations
~500 PY invested since 2010, competitive in each use case
>1.200 end users at >100 customers
More and more customers are striving step by step to the full vision of an integrated engineering backbone with PREEvision
5
E/E Development with PREEvision – Status
E/E Development with PREEvision – Trends
E/E Development with PREEvision – Outlook
Agenda
6
The Automotive E/E Development Workflow – OverviewE/E Development with PREEvision – Trends
Data Management, Collaboration, Variant/PL Management, Safety, Change Management
Requirements Engineering and Management
Test Engineering and Management
FunctionalArchitectureDesign
SOADesign
SoftwareDesign
PhysicalArchitectureEvaluation
PhysicalArchitectureDesign
PhysicalSystemDesign
COMDesign
WH SeriesDesign
WHArchitectureDesign
7
The Automotive E/E Development Workflow – Trend 1 “E/E-A WH-A/D”E/E Development with PREEvision – Trends
Data Management, Collaboration, Variant/PL Management, Safety, Change Management
Requirements Engineering and Management
Test Engineering and Management
FunctionalArchitectureDesign
SOADesign
SoftwareDesign
PhysicalArchitectureEvaluation
PhysicalArchitectureDesign
PhysicalSystemDesign
COMDesign
WH SeriesDesign
WHArchitectureDesign
8
The Automotive E/E Development Workflow – Trend 1 “E/E-A WH-A/D”E/E Development with PREEvision – Trends
Benefits PREEvision: One tool for the complete design flow at the OEM
Full collaboration between all stakeholders Model based Change Management High consistency E/E-A and WH-A PREEvision as EEA/WH Backbone
One process implementation
One variant management
High efficiency by synthetization and automation from WH Architecture to WH Series Design
9
The Automotive E/E Development Workflow – Trend 2 “FD ASR SW/COM”E/E Development with PREEvision – Trends
Data Management, Collaboration, Variant/PL Management, Safety, Change Management
Requirements Engineering and Management
Test Engineering and Management
FunctionalArchitectureDesign
SOADesign
SoftwareDesign
PhysicalArchitectureEvaluation
PhysicalArchitectureDesign
PhysicalSystemDesign
COMDesign
WH SeriesDesign
WHArchitectureDesign
10
The Automotive E/E Development Workflow – Trend 2 “FD ASR SW/COM”E/E Development with PREEvision – Trends
Benefits PREEvision: Seamless from Functional Architecture to
Service/Software Architecture and Communication Design
One approach for the top-down function oriented development approach
Combination of SysML/UML editors with the rich PREEvision Automotive Data Model
Collaboration for large and distributed teams
11
The Automotive E/E Development Workflow – Trend 3 “Model Based RQE”E/E Development with PREEvision – Trends
Data Management, Collaboration, Variant/PL Management, Safety, Change Management
Model Based Requirements Engineering and Management
Test Engineering and Management
FunctionalArchitectureDesign
SOADesign
SoftwareDesign
PhysicalArchitectureEvaluation
PhysicalArchitectureDesign
PhysicalSystemDesign
COMDesign
WH SeriesDesign
WHArchitectureDesign
12
The Automotive E/E Development Workflow – Trend 3 “Model Based RQE”E/E Development with PREEvision – Trends
Benefits PREEvision: Model based definition of requirements in the model and/or diagrams
Unique Id‘s for artifacts/attributes, responsibility possible on artifact level
Usage of model semantics to manage the variation of the requirements
Model consistency check are performed on model semantics
The requirement export is always based on consistent data PREEvision as “Single Point of Truth”
Requirement documents are created automatically based on the model
OEM/Supplier collaboration supported (“HIS process”)
13
E/E Development with PREEvision – Status
E/E Development with PREEvision – Trends
E/E Development with PREEvision – Outlook
Agenda
14
Quo Vadis, PREEvision?E/E Development with PREEvision – Outlook
Good status with the integrated, model based and collaborate approach.Focus topics in future releases: usability, robustness and performance
Requirements Engineering and Requirements Management
Function Driven DesignSystem Design
Unique with the Logical System Architecture and Activity Chains.Focus topics in upcoming releases: Completion of the UML Diagrams (Message Sequence, Activity, Requirement), Simulation, ...
Wiring HarnessDesign
Focus on OEM WH/Series Design and the collaboration OEM/Tier1 in concept phases.Focus topics in upcoming releases: usability, performance, additional automationand synthesis features, VEC support, ...
AUTOSARSystem, Service and Software
Design
Consequent support of AUTOSAR / Adaptive AUTOSARFocus topics in upcoming releases: Consistency Checks, Ethernet, Vector ToolchainPREEvision DaVinci DEV/CFG and CANoe/VTT, Software Platform Management
Strong commitment from Vector to our customers and the market to follow the selected path full continuity, ongoing investments, highly passionate team
Continuous efforts to complete the supported use cases and ensure well performing and robust global backbone capabilities for large and globally distributed user groups
Adequate team size (E2018: >200 people globally), significant further growth in 2019
15 © 2018. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.0 | 2018-11-20
Author:Georg ZimmermannVector Germany
For more information about Vectorand our products please visit
www.vector.com
16
Version History
VNo Change Author Date0.1 Initial version Zn 2018-11-18
0.2 Findings Cr, Lh, Srf and Jma considered Zn 2018-11-19
1.0 Last refinements Zn 2018-11-20
17
Supported Use Cases
E/E Backbone,Collaboration Platform,
File Management
Design of SafetyRelevant Systems
Product LineEngineering
ArchitectureDesign
Requirements Engineering and Requirements Management
AUTOSARSystem and Software
Design
Communication Design(AUTOSAR and Legacy)
Hardware ComponentDevelopment
Function Driven DesignSystem Design
Test Engineering andTest Management
E/E Backbone,Collaboration Platform,
File Management
Variant Managementand
Product Line Engineering
ArchitectureDesign
Requirements Engineering and Requirements Management
AUTOSARSystem, Service and Software
Design
Communication Design(AUTOSAR and Legacy Formats)
Hardware ComponentDevelopment
Function Driven DesignSystem Design
Test Engineering andTest Management
Wiring HarnessDesign
Change and Release Management
Design of SafetyRelevant Systems
18
Supported Use Cases
E/E Backbone,Collaboration Platform,
File Management
Design of SafetyRelevant Systems
Product LineEngineering
ArchitectureDesign
Requirements Engineering and Requirements Management
AUTOSARSystem and Software
Design
Communication Design(AUTOSAR and Legacy)
Hardware ComponentDevelopment
Function Driven DesignSystem Design
Test Engineering andTest Management
E/E Backbone,Collaboration Platform,
File Management
Variant Managementand
Product Line Engineering
ArchitectureDesign
Requirements Engineering and Requirements Management
AUTOSARSystem, Service and Software
Design
Communication Design(AUTOSAR and Legacy Formats)
Hardware ComponentDevelopment
Function Driven DesignSystem Design
Test Engineering andTest Management
Wiring HarnessDesign
Change and Release Management
Design of SafetyRelevant Systems
19
Stromlaufplan (SLP)
Bordnetz-topologie (BNT)
System-schaltplan (SSP)
20
Design Workflow for Service-oriented Architectures in AUTOSAR Adaptive
21
Model based Requirements engineering
22