Model-based Management of Software Platforms

Transcription

1 Model-based Management of Software Platforms Vector Congress, 20th of November 2018, Stuttgart V

2 Agenda Project and Platform Driven Development Reasons for Variants Platform Process Summary

3 Project and Platform Driven Development Independent Software Projects Software Project 1 Software Project 2 Software Project 3 Halogen Halogen Xenon Clone & Own Xenon Clone & Own LED Vehicle 1 Vehicle 2 Vehicle 3 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 2/10

4 Project and Platform Driven Development Common Software Platform Benefits High quality by continuous improvements and multiple usage High flexibility and agile creation of new variants and alternatives Software Platform: One Software for Everything Halogen Halogen Software Project 1 Software Project 2 Software Project 3 Challenges Long term commitment to platform Tailoring of projects by variant management Xenon Xenon LED Vehicle 1 Vehicle 2 Vehicle 3 3/10

5 Reasons for Variants Functional Variants Halogen Xenon LED Variant 1 Vehicle 1 Product Management Task Definition of feature model Definition of variants Variant 2 Task of Architects Vehicle 2 Variant 3 Definition of functional architecture and interfaces Vehicle 3 Variant 4 Variant 5 Definition of SW architecture and variant concepts Mandatory guidelines for detailed SW design of functional components, e.g. exterior lighting 4/10

6 Reasons for Variants Technology Variants AUTOSAR Classic AUTOSAR Classic AUTOSAR Classic AUTOSAR Adaptive Technology variants need abstraction concepts driven by: > SW platforms (AUTOSAR Classic, Adaptive, ) Logical Function Architecture Vehicle 1 Vehicle 2 Service oriented Architecture (SOA) AUTOSAR Classic SW Architecture SW Component Behavior HW Network Architecture AUTOSAR Adaptive SW Architecture SW Class Architecture & SW Component Behavior > HW abstraction (drivers for LED cluster, ) Vehicle 3 5/10

7 Platform Process Teamwork: SW Achitecture, Design and Implementation Function Designer SW Architect SW Designer Implementation in C: variation by #ifdef Implementation in C++: variant pattern, e.g. inheritance 6/10

8 Platform Process Platform Releases and Project Releases Platform Releases R1 R2 R3 R4 Reuse Update Update Update Project 1 Releases Reuse Merge Reuse Project 2 Releases Reuse Update Update Project 3 Releases Branch (Top-down approach) 7/10

9 Platform Process PREEvision Engineering Backbone Platform approach needs engineering backbone Full traceability Change and release management Organization of teamwork Data management > Domain language > Reuse and branch > Product line management SW Architect SW Designer SW Supplier Integration of supplier SWCs > Important for central computing platforms PREEvision has core functionality to support Model-based Management of Software Platforms 8/10

10 Summary Model-based Management of Software Platforms 1. Runtime Platform 2. SW Platform 3. Architecture 4. Methods & Processes 5. Roles & Organization 6. PREEvision as Engineering & Collaboration Tool 9/10

11 For more information about Vector and our products please visit Author: Dr.-Ing. Clemens Reichmann Vector Germany