Management Of Software Platforms - Vector · Product Management Task Definition of feature model Definition of variants Task of Architects Definition of functional architecture and

V1.3 | 2018-11-19

Vector Congress, 20th of November 2018, Stuttgart

Model-based Management of Software Platforms

Project and Platform Driven Development

Reasons for Variants

Platform Process

Summary

Agenda

© 2018. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.3 | 2018-11-19

Independent Software ProjectsProject and Platform Driven Development

Vehicle 1

Benefits: Independent release planning

Different SW suppliers possible

Flexible SW architectures and functions

Independent design and development processes

Consequences: Multiple development

Multiple maintenance

Multiple quality assurance of similar functions

„Clone & Own“

„Clone & Own“

Vehicle 2 Vehicle 3

Software Project 1 Software Project 2 Software Project 3

Halogen Halogen

Xenon

Xenon

LED

2/10


Benefits High quality by continuous

improvements and multiple usage

High flexibility and agile creation of new variants and alternatives

Challenges Long term commitment to platform

Tailoring of projects by variant management

Common Software PlatformProject and Platform Driven Development

Software Platform: One Software for Everything

Software Project 1

Software Project 3

Vehicle 1 Vehicle 2 Vehicle 3

Software Project 2

Xenon

LED

Halogen

Halogen

Xenon

3/10


Functional VariantsReasons for Variants

Halogen

Product Management Task Definition of feature model Definition of variants

Task of Architects Definition of functional architecture and

interfaces Definition of SW architecture and variant

conceptsMandatory guidelines for detailed SW design of functional components, e.g. exterior lighting

Xenon LED

Vehicle 3

Vehicle 1

Vehicle 2

Variant 1

Variant 2Variant 3

Variant 5

Variant 4

4/10


Technology VariantsReasons for Variants

AUTOSARClassic

Technology variants need abstraction concepts driven by:

> SW platforms (AUTOSAR Classic, Adaptive, …)

> HW abstraction (drivers for LED cluster, …)

AUTOSARClassic

AUTOSAR Adaptive

Vehicle 3

Vehicle 1

Vehicle 2

AUTOSAR Classic

Logical Function Architecture

Service oriented Architecture (SOA)

AUTOSAR ClassicSW Architecture

AUTOSAR Adaptive SW Architecture

SW Component Behavior SW Class Architecture & SW Component Behavior

HW Network Architecture

5/10


Teamwork: SW Achitecture, Design and ImplementationPlatform Process

SW Architect

SW Designer

Implementation in C: variation by „#ifdef…“

Implementation in C++:variant pattern, e.g.

inheritance

Function Designer

6/10


Platform Releases and Project ReleasesPlatform Process

Platform Releases

Project 1Releases

Project 2Releases

Project 3Releases

R2 R3 R4

Reuse

Update

Branch (Top-down approach)

Merge

Reuse Update

R1

Reuse

Update

Reuse

Update Update

7/10


Platform approach needs engineering backbone Full traceability Change and release management Organization of teamwork

Data management> Domain language> Reuse and branch> Product line management

Integration of supplier SWCs> Important for central computing platforms

PREEvision has core functionality to support Model-based Management of Software Platforms

PREEvision Engineering BackbonePlatform Process

SW Architect SW Designer SW Supplier

8/10


6. PREEvision as Engineering & Collaboration Tool

Model-based Management of Software PlatformsSummary

5. Roles & Organization

4. Methods & Processes

3. Architecture

2. SW Platform

1. Runtime Platform

9/10


Author:Dr.-Ing. Clemens ReichmannVector Germany

For more information about Vectorand our products please visit

www.vector.com

Management Of Software Platforms - Vector · Product Management Task Definition of feature model Definition of variants Task of Architects Definition of functional architecture and

Documents