Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
V0.0 | 2017-09-14
PREEvision 8.5
AUTOSAR System and Software Design with PREEvision
RELEASED
2
u AUTOSAR System and Software Design with PREEvision
Integrated AUTOSAR System Design
PREEvision roadmap
Agenda
3
OVERVIEW
AUTOSAR System and Software Design with PREEvision
4
Overview
AUTOSAR System and Software Design with PREEvision
AUTOSAR in PREEvision
Software Architecture
Network Topology
Communication
5
Overview
AUTOSAR System and Software Design with PREEvision
6
Overview
AUTOSAR System and Software Design with PREEvision
u Multi user support
u Lock concept on artifact level to prevent access conflicts
u All users have always access to up-to-date information
u Version and configuration management
7
AUTOSAR
AUTOSAR System and Software Design with PREEvision
8
AUTOSAR Workflow (theory)
AUTOSAR System and Software Design with PREEvision
VFB
Virtual Function Bus
SWC1
SWC2 SWC3
ECU1
SWC1
SWC2
ECU2
SWC3
System Description*
Extract of System Description* ECU Configuration Description (ECUC)*
Software Component Description*
*
SWC1 SWC2
Basic Software (BSW)
RTE
Complete SW functionality of the vehicle is defined as a system of SWCs...
..and distributed to ECUs
An extract is created for each ECU...
The ECU is configured based on the ECU Extract.
ECU1
SWC1
SWC2
9
u Virtual function bus design
u Topology design
u Software/Hardware mapping
u Data mapping and signal routing
u CAN, CAN FD, LIN, FlexRay design
AUTOSAR System Design Workflow
AUTOSAR System and Software Design with PREEvision
10
Design Workflow for Service Oriented Architectures
AUTOSAR System and Software Design with PREEvision
u Service definition and service interface design
u Virtual function bus (derived from service definition)
u Switched topology definition
u Deployment of service provider and service consumer
u Communication design
u VLAN configuration
u Switch configuration
u Socket communication
11
Format Use Case AUTOSAR version
System Description
Import Export Update
3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
ECU Extract Export 3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
ECU System Description
Export 4.0.3, 4.1.1, 4.2.1, 4.2.2
Software Component (and other custom extracts)
Import Export Update
3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
AUTOSAR Import
AUTOSAR System and Software Design with PREEvision
* Limited support
12
Service and SOA Design
AUTOSAR System and Software Design with PREEvision
u Graphical diagrams to design and understand service oriented architectures
u Service Architecture Diagram
u Service Diagram
u Definition of the Service Interface and derivation of the Software Architecture for AUTOSAR Classic
u Ethernet Explorer for the design of Ethernet communication
13
Software Design
AUTOSAR System and Software Design with PREEvision
u Graphical diagrams to model SW architecture
u Library to define SW components, interfaces, data types, etc.
u TPI (Type-Prototype-Instance) concept
u Engineering tools to merge/split/move SW Components, automatic connection of ports, propagation of port interfaces
u Dedicated editors and views for ports, connections, interfaces, etc.
14
Hardware Network Design
AUTOSAR System and Software Design with PREEvision
u Graphical diagrams to model HW architecture
u Reuse of HW components
u Engineering tools to change type of HW components, change type of bus, …
15
SW Component Mapping
AUTOSAR System and Software Design with PREEvision
u Mapping of SW Components to HW Components
u Mappings are objects and support variant management
u Graphical visualization of mappings in diagrams
u Mapping editor
16
Data Mapping and Signal Routing
AUTOSAR System and Software Design with PREEvision
u Signal router to automatically create signals, data mappings and signal routes (including gateways entries)
u Various routing options and delta routing
17
Network Communication Design
AUTOSAR System and Software Design with PREEvision
u Frame/PDU/Signal layout editor
u Protocol specific bus editors for CAN, CAN FD, LIN and FlexRay
u Dedicated editors for Frames, Signals, etc.
u Support of legacy formats (LDF, DBC, FIBEX)
18
Format Use Case AUTOSAR version
System Description
Import Export Update
3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
ECU Extract Export 3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
ECU System Description
Export 4.0.3, 4.1.1, 4.2.1, 4.2.2
Software Component (and other custom extracts)
Import Export Update
3.2.2*, 4.0.3, 4.1.1, 4.2.1, 4.2.2
AUTOSAR Export (Supplier Integration)
AUTOSAR System and Software Design with PREEvision
u Consistency checks
u Generation of specification documents
u Export / Import of AUTOSAR System Description, System Extract, ECU System Description, ECU Extract, SW Component.
u Update of several formats
* Limited support
19
WORKFLOW
AUTOSAR System and Software Design with PREEvision
20
Vector AUTOSAR Tool Chain
AUTOSAR System and Software Design with PREEvision
System Description
SW Component Description
AUTOSAR
System Design
PREEvision
System Description
ECU Extract
ECU System
Description
SW Component Description
SW Component Description
RTE Configuration BSW Configuration
DaVinci Configurator Pro
SWC Detailed Design
(RTE Configuration)
DaVinci Developer
ECUC
ECU Extract
System scope
ECU scope
Soft
ware
Inte
gra
tion P
ackage
Bus simulation
CANoe
Implementation
Model based impl. tool
Up
date
Ch
an
ge
man
ag
em
en
t
Custom Extract
21
SWC Design – Which tool to use?
AUTOSAR System and Software Design with PREEvision
PREEvision DaVinci Developer
Tool type Database authoring tool, customizable functionality File-based authoring tool, predefined functionality
AUTOSAR Coverage SWCs, Data Mapping, Communication SWCs, Data Mapping
Scope One ECU, subsystem or complete vehicle One ECU
Tool chain integration Master authoring tool, covers all relevant architecture levels beyond AUTOSAR (e.g. requirements, functional architecture, …) , direct mapping of AUTOSAR design objects to these architecture levels
Master authoring tool or backend ARXML file editor, uses generic AUTOSAR concepts to link with e.g. requirements
Version/Variant management approach
Integrated version/variant management Version/variant management with external file-based CM tool
Multi-User approach Integrated multi-user approach with roles and rights Multi-user approach with external file-based CM tool, supported by AUTOSAR model diff/merge function
User Type OEM or TIER1, using a centralized data backbone for ECU development with platform approach
TIER1, decentralized project teams, file-based platform approach using CM repository
“the fast lane to RTE” “the engineering backbone”
22
AUTOSAR System and Software Design with PREEvision
u Integrated AUTOSAR System Design
PREEvision roadmap
Agenda
23
Integrated Requirements Management
Integrated AUTOSAR System Design
u Requirements import and assessment
u Specification of customer feature catalog
u Specification of abstract logical architecture representing future software and hardware implementations
u Modeling of control sequences realizing a customer feature as activity chains
u Mapping of requirements to SWCs
u Generation of requirements documents
24
Integrated Project and Release Management
Integrated AUTOSAR System Design
u Integrated project planning and tracking
u Integrated change management
u Branch, compare & merge support
25
Integrated Variant Management
Integrated AUTOSAR System Design
u Product line support
u Integrated feature model and resolver for feature based derivation of products
u Configurable propagation rules and consistency checks
Products
Feature Model
26
Integrated Product Line Management and Reuse
Integrated AUTOSAR System Design
u Support of multiple product lines
u Reuse of artifacts in different product lines
27
Integrated Quality Assurance
Integrated AUTOSAR System Design
u Integrated test data management
u Requirements based testing
u Feature tests
u Component tests
u Integration and system tests
28
AUTOSAR System and Software Design with PREEvision
Integrated AUTOSAR System Design
u PREEvision roadmap
Agenda
29
u PV 8.5 (End of July 2017)
u Enhancements > Enhancements on the Ethernet workflow
> Better integration in the Vector AUTOSAR Tool Chain
u PV 8.5 SP1 (September 2017)
u Use case support > ContainerPDU and SecuredPDU design
u PV 9.0 (Middle 2018)
u UI Enhancements > Use Case AUTOSAR Network Explorer
> Enhancements on the Ethernet workflow
u Consistency checks for Software Component Design
u Use case support > Diagnostics Communication Design (CAN Tp, Ethernet DoIP)
u AR format > AUTOSAR 4.3
u AUTOSAR Adaptive
PREEvision roadmap
30 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.0 | 2017-09-14
For more information about Vector and our products please visit www.vector.com
Author: Jörg Schäuffele, Marcelino Varas, Markus Helmling Vector Germany