preevision at porsche (update 2018) · 4/26 m. kühl / dr. m. görber eey2 where we came from (see...

2/26

M. Kühl / Dr. M. Görber EEY2

PREEvision at Porsche (Update 2018)Markus KühlEEY2

3/26


Overview (Porsche Update 2018)Continuous Integration and Design Traceability by combining logical and software architecture

Use of Logical Architecture @ PorscheFrom functional concepts to signalcommunication requirements

From Logical to Software ArchitectureEnabling Autosar Development forhighly integrated ECUs

1

2

3

Agenda

Summary & Outlook4

4/26


Where we came from (see VeCo 2014 presentation)…

Use cases of PREEvision @ Porsche Modeling tool for highly specialized E/E Architecture tasks, e.g.

Development of Functional Architectures for Porsche specific functionsAnalysis of resulting impacts on networking, interfaces and devicesNetwork Topology Development ProcessDocumentation of feature-function oriented wiring harnessesCompatibility Analysis (e.g. ECU interfaces vs. K-Matrix)Feature Oriented Release Management (e.g. ECU used by feature)

5/26


PREEvision @ Porsche in 2018

Rollout as modeling tool to Porsche Development Departments for logical (functional) architecture design purposes in a new E/E Architecture generationSoftware Architecture Development Tool (Autosar) for High Performance Cluster ECU

PREEvision is now highly integrated into our function-oriented development process

6/26


Todays Presentation Focus

Logical Architecture

CommunicationLayer & API

Technical Architecture

Software Architecture

Requirements

Feature List

LA Freeze

ReleaseSWA

Layer Architecture as of PREEvision 9.0

7/26


From Feature to Logical Architecture

…

…

8/26


Identification of Logical Function Blocks

Car Feature under Development

Feature Owner x

Identification of function blocks is a manual process done with help of deeper investigations (paper or tool + simulation based using SysML diagrams upcoming in PREEvision 9.0ff)

M

Logical Function Block as core items

of a car feature

Draft Concept of a car feature

Feature List

FunctionBlock1

FunctionBlock2

Hierarchy

SubFunction Block 1-n

Function Block Owner 1 Function Block Owner 2 Function Block Owner 1

9/26


Identification of Logical Function Blocks

Car Feature under Development

Referenced functionblocks or services

ClampControl

HMISubfunction

ConnectBackend

Subfunction

FunctionBlock1

FunctionBlock2

Hierarchy

SubFunctionBlock 1-n

EnergyManager Service

Logical FunctionBlock as

stakeholderfunctions or services

Smart ActuatorFunction

Block

10/26


2. Logical Architecture by Example

On-board Service

Logical FunctionalBlock (Concept C)

Logical Functional Block (Sens/Act Layer)

Physical Values(Sens/Act)

Logical Hierarchy

Backend Service

Logical Function Block (Compute Layer)


11/26


Interface Specification

12/26


2. Technical Architecture (Mapping of Logical Functions -> Topology)

PerformanceComputer 1

Offboard System x Offboard System y

Connectivity Unit

Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor

OffboardComputational

Layer

PerformanceLayer

Smart Sensor & Actuator Layer

Smart Device

Smart Device

Smart Device

Smart Device

FunctionBlock1FunctionBlock1

M


Block

M

ClampControl


M

ConnectBackend

SubfunctionM

13/26


Communication Analysis


Offboard System x Offboard System y

Connectivity Unit

Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor


Smart Actuator

Smart Sensor

Smart Actuator

Smart Sensor

OffboardComputational

Layer

PerformanceLayer

Smart Sensor & Actuator Layer

Smart Device

Smart Device

Smart Device

Smart Device

FunctionBlock1FunctionBlock1

M


Block

M

ClampControl


M

ConnectBackend

SubfunctionM

Service & Classic Communication

Sign

al C

omm

unic

atio

n Signal Voting Process and Communcation Design are done in an external tool chain today (SBT/Busnet).

Function Blocks and Interface Specification finally approved within PREEvision are exported to SBT / Busnet.

Voting State and final Communication Matrix are synced back to PREEvision

14/26


How to derive Software Architecture from Logical Architecture

Logical Architecture is in our approach focused on the development of an end-2-end architecture of all car functions to be integrated. Activity chains therefore are used to model a certain car function from data acquisition (e.g. sensor, computed data from 3rd party car function or backend systems) to one or more final logical block (e.g. HMI, other function blocks)

Besides certain common design processes (e.g. communication matrix & Service API design, analysis processes like functional safety, timing path) we make use of LA function blocks that are mapped to one electronic control unit (e.g. Performance Computer) to generate core parts of the Software Architecture for the device under development.

Patterns used to generate & synchronize SWA from LA: Single Function Block conversion to single Atomic Software Component (SWC)

Multiple Function Block conversion merged to one Atomic SWC

One Function Block conversion to two Atomic SWC

Additional Autosar SWA aspects are manually modeled in SWA layer or generated via metrics (e.g. Internal Behavior, Service Needs, Diagnostic Data)

15/26


LA > SWA Conversion Pattern by Example

Logical Functional Block (discrete IO @ ECU1)



Logical Function Block (Compute Layer @

ECU1)

„external“ logicalfuntion block

„external“ logicalfunction block

Logical Functional Block (Sub-bus @ ECU1

Sens/Act Layer)

Step 1: Execute model consistency check

Step 2: Identify logical function blocks for conversion, create Atomic SWC for each conversion

Step 3: Transfer ports from logical function blocks to SWC (creation of technical interfaces)

Step 4: Convert external ECU communication into Composition Delegation Ports

Step 5: Connect compatible interfaces

16/26



M

17/26



M

M

18/26



M

19/26


LA>SWA Block Merge Conversion (Step 2, after Model Check Step 1)

1:1

n:1

LA Layer

SWA Layer

20/26


LA>SWA Block Merge Conversion (Step 3)

LA Layer

SWA Layer A

A

21/26


LA>SWA Block Merge Conversion (Step 4 – Assembly Connector + Structure)

External Communication = Delegation Port (tagged)Discrete IO = Delegation Port (tagged)

+

22/26


How things come together…

Feature Listt2017 2018 2019 2020

Com& API

…CM Freeze 1 CM2 CM3

Feature …Feature x …

Technical Architecture

…AM Freeze 1 AM2 AM3

Logical Architecture FB FB FB FB


FunctionBlocks

Com + API …

SWA Freeze 1 SWA2 SWA3 SWA4

23/26


LA>SWAConversion

Concurrent Development & Continuous Integration LA>SWA

Logical Architecture Dev.

Communcation & ServiceAPI Dev.


Dev.

LA Freeze 1.e

ExternalInterfaceFreeze

LA Freeze 1.i

Continuous LA Development ongoing

InternalInterfaceFreeze

Approval (SBT)

& Comm Dev.COM Release 1

1st Reuse Check-In

Product Line ECU1 [Freeze 1]

2nd Reuse Check-In

LA B

lock

(s)

LA B

lock

(s)

ExternalInterface

InternalInterface

SWA Modeling

Release Bundle

ARXML SysDesc

ARXML ECU Ex

Product Line ECU1 [Freeze 1 NI]

Approval (SBT)

LA Freeze 2.e LA Freeze 2.i

Product Line ECU1 [Freeze 2]

Product Line Reuse + Branch

ExternalInterfaceFreeze

InternalInterfaceFreeze

& Comm Dev.

LA B

lock

(s)

LA B

lock

(s)

LA>SWAConversion

1st Reuse Check-In

2nd Reuse Check-In

ExternalInterface

InternalInterface

…

…

…

24/26


Approval Process Lifecycle for Logical Function Blocks

UnderDevelopment

Development Finished

In Approval(Domain Architect)

approved(Domain Architect)

In Approval(EE Architecture)Released

(EE Architecture)

Transition: Roles able to switch Lifecycle State

Domain ArchitectEE Architect

Function OwnerEE Architect

EE Architect

Domain ArchitectFunction Owner

Domain Architect

Domain Architect

EE Architect

Domain Architect

[Edit] -> all [Edit] -> Domain Architect, EE Architect

[Block/Port Edit] -> Roles allowed to edit function blocks, ports and interfaces

[Edit] -> Domain Architect, EE Architect

[Edit] -> EE Architect

[Edit] -> EE Architect[Edit] -> EE Architect

EE Architect

EE Architect

EE Architect

EE Architect

LA>SWA ExternalInterfaceFreeze

LA>SWA InternalInterfaceFreeze

25/26


Summary & Outlook

Successfully introduced function oriented development process on top PREEvision utilizing Logical Architecture concepts

Communication interfaces (signals..) specified in PREEvision, but approval process and communication design is still carried out in an external tool chain

Autosar Design Process for one of our Performance ECUs in close loop with development of logical architecture

Next steps:

Optimize Autosar Design flow with introduction of Explorer based Editors

Introduce SysML notation / methods especially in early design phases (PV9.0ff)

Formalization of function block & interface approval process within PREEvision (Vote & Review)

Integration of approval process for communication interfaces in existing tool chain

Implementation of Viewer Web-Apps for quick model access

26/26


Thanks for you attention!

preevision at porsche (update 2018) · 4/26 m. kühl / dr. m. görber eey2 where we came from (see...

Documents