genivi korea summit 2013 genivi development model€¦ · genivi korea summit 2013 ... a proper...

19-Nov-13Dashboard image reproduced with the permission of Visteon and 3M Corporation

GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries

Copyright © GENIVI Alliance 2013 1

GENIVI Korea Summit 2013GENIVI Development Model

Pavel KonopelkoSoftware Architect / SAT Lead

Visteon

• Reflecting on the history

– Problems to be solved and the attempts on solution

• Current approach

– Organization, processes and artifacts

• Looking into the future

– Improvements being worked upon

Contents

19-Nov-13GENIVI is a registered trademark of the GENIVI Alliance in the USA and other countries


Reflecting on the history


Copyright © GENIVI Alliance 20133

A proper development model needs to address at

least two aspects:

1. Solving the right problem

– Understand and control the system scope and design constraints—GENIVI Software Platform is a part of a bigger system

2. Solving the problem right

– Organize the available development resources in a way that is efficient and compatible with open-sources development practices

Two Dimensions of Development Model



Software Platform in the Big Picture

Vehicle

Electronic Control Unit

System on Chip

Software Platform

Software

Applications



• Distributed, evolutionary approach

– More robust in face of uncertainty

– More waste and therefore less resource efficiency

• Centralized, requirements-driven approach

– Works best under known and stable conditions

– Better utilization of development resources

‘Pure’ Open-Source vs. Full Control



• In early 2009 GENIVI started by chartering several Working Groups and put together a process task force

• In early 2010 the “GENIVI Component Development” (GCD) process was finalized and put into action

• It was based on centralizeddecision making, was ratherheavy-weight and wassoon abandoned

• The approach to systemscopes based on UMLhas proven more viable

First Attempt: GENIVI Component Development



• By mid 2010, after a performance assessment it was realized that the progress is rather slow

• The Board decided to simplify the organization, refine the existing Working Groups into more fine grained Expert Groups with dual leadership, move the decision power down the organization hierarchy and streamline the process

• This new organization structureand the strong orientationtowards the complianceprogram found wide adoptionand are currently in use

Second Attempt: Tuning Organization



• From the very beginning, GENIVI assumed that the software projects launched within the alliance will be only accessible to the alliance members

• In early 2012, several board members attended the Open Source Think Tank held in Napa valley

• The most important feedback was “to be more open and less paranoid”

• In October 2012, a fully openproject hosting platform hostedby the Linux Foundation wascreated and all existing projectsmigrated to it

Recent Attempt: Opening up the Code



Current approach





Development Teams

SystemArchitectureTeam

BaselineIntegrationTeam

Compliance Specification

CE Connectivity EG

HMI-Application

Framework EG

Location-Based Services EG

Media and Graphics EG

Networking EG

System Infrastructure

EG

Korea REG

• Each development team typically have its

mailing list and holds weekly conference calls

– All technical issues are discussed in one place on [email protected]

• Each team typically arranges several face-to-

face meeting per year

• Two times a year all participants meet during

GENIVI All Member Meetings

• SAT has sub-teams for security and compliance

• Each Expert Group hosts multiple projects

Team Working Mode



CE Connectivity EG Scope



Bluetooth

• Hands-Free Profile (HFP)• Advanced Audio Distribution Profile (A2DP)• Audio/Video Remote Control Profile (AVRCP)• Device ID Profile (DID)• Dial-up Networking Profile (DUN)• File Transfer Profile (FTP)• Headset Profile (HSP)• Object Push Profile (OPP)• Personal Area Networking Profile (PAN)• Phone Book Access Profile (PBAP)• Message Access Profile (MAP)• Low Energy

iPod• iPod Out• iAP

Media Playback• Media Pipeline• Audio Management• Video Audio Sync• Phonetic Database

Out of GENIVI Scope

Other EG

Device management• Device Detection• Device Identification• Device Classification

AV• HDMI inc Wireless• MHL• 3.5mm Jack• AV USB• Composite Video• MiraCast

Thunderbolt

SATAeSATA

In CEC Scope

AV• DVI• LVDS• VGA

1394 Firewire

WiFi

DLNA/UPnP• WiFi

NFC• NFC• Charging

Media Playback• Media Indexing• Playback Control• Playlist management• Media Source Abstraction• Metadata Enhancement

USB• Wireless Dongle• WiMax• Wifi

Smart Device• Common APi• Mirrorlink• IVILink

Digital Rights management

= Active project

USB• Mass Storage• Multimedia

Portable Devices• MTP, PTP.

= Not currently active

TCP/IP• USB• Bluetooth• WiFi

Wireless Charging

HMI & Application Framework EG Scope



HMI Framework - G1• Popup Manager

• Driver Workload Assessor

• Localization Management

• Push Message Centre

• Asset Manager

• I/O Abstractions for Applications

Out of GENIVI Scope

Other EG

In HMI&AF Scope

System Infrastructure• Certificate Manager (App FWk)• Service Discovery (App FWk)

• User Management and Personalization• Software Management

TBA - Not currently active

Networking• Vehicle Interface

Speech Services• Speech Output Service

• Speech Input Services

• Speech Dialogue Service

LBS• Navigation

Reference HMI

G4 - SDK

Media & Graphics• Layer Manager• Graphics API

active

HMI tool chain

Specific Application Frameworks

G5 - App Store

G5 App Store Client

Application Framework - G1/G2• Application Manager

• Interface Access Manager

• Service Discovery - (Led by EG-SI)

• Certificate Manager (EG-SI/Security)

• Communication - (Big list Handling & Data Binding)

• Unified API - (G2)

• GENIVI Reference App Framework - (G2)

Security• Interface Access Manager

• Certificate manager

G3 – Foreign Frameworks

Graphics Description & Processing Pipeline• Rendering technologies

• Graphics asset formats

Korea REG Scope



Vehicle Web API• Vehicle Web API requirements

• Reference implementation

• W3C Vehicle API Standardization

Out of GENIVI Scope

Other EG

KREG Scope

Networking• Vehicle Interface• INCM/AMB• DLT• Browser Framework• Connection Manager

Regional requirements• Multi profile IVI (include Instrument cluster)

• Asian LBS requirements

Car Data Logging• Data logging requirements

• Code implementation which working with DLT

daemon/client

LBS• Navigation

Car data server• OEM CRM/telematics server• Sync protocol

SI• Persistence Manager

= Active project


Media and Graphics- Web and Radio Tunner

Radio Web API• Coordination with Native Web API

• Radio Web API requirements

W3C standardization• Automotive BG

: Tizen, QNX, …



Location Based Services EG Scope

NavigationCore

• Route Calculation

• Route Guidance

• Location Input

• MapMatchedPosition

MapDataService

• API to access NDS Databases

Speech

• Voice Generation

• Voice Recognition

Out of GENIVI Scope

Other EG

MapViewer

• Map Rendering

• Map Configuration

GNSSService

• GPS

• GLONASS

• Galileo

• ...

HMI

In LBS Scope

SensorsService

• Odometer

• Vehicle Speed

• Inclination

• Gyroscope

• ...

TrafficIncidentsService

• Traffic Information

over multiple delivery channels

(RDS /TMC, TPEG, XM/SIRIUS)

LayerManagement

• Layer Rendering and

Compositing

POIService

• POI on Local Database

• POI on Online Servers

= Active project


Tuner

• Analog Radio Tuner (AM, FM)

• Digital radio tuner (DAB, DMB, ..)

• ...

EnhancedPositionService

• DeadReckoning

• ...

More Services

• ADASHorizon

• Roadside Assistance

• Fleet Management

• Emergency Call

• TrafficFlowService

Media & Graphics EG Scope



Layer Management• Window Manager

• Rendering Service• Graphicsystem

Audio• Audio Management• Video Audio Sync• Audio Routing

Media Playback• Playback Control• Playlist management• Media Source Abstraction

Out of GENIVI Scope

Other EG

AV• HDMI inc Wireless• MHL• AV USB• Composite Video• MiraCast

Thunderbolt

SATAeSATA

In MG Scope

AV• DVI• LVDS• VGA• 3.5mm Jack

1394 Firewire

WiFi

DLNA/UPnP• WiFi

NFC• NFC• Charging

Media Playback• Media Pipeline• Audio Management• Video Audio Sync

USB• Wireless Dongle• WiMax• Wifi

Smart Device• Common APi• Mirrorlink• Livio• IVILink• VNC - TBC

Digital Rights management

= Active project

USB• Mass Storage• Multimedia• Portable Devices• MTP, PTP.


TCP/IP• USB• Bluetooth• WiFi

Tuner• Station Management• Data & Traffic Services• Hybrid&Internet Radio

Networking EG Scope



Browser• Download Manager

• Bookmark Management• HMI Browser API• Certificate Management• Port Abstraction • NSAP Plugin Concept• Tab Support • Web API / HTML5 Application support• W3C• DeviceAPIs• Vehicle Web API

HMI• Popup Manager

Out of GENIVI Scope

Other EG

ConnMan• Session API• Advanced routing • Network abstraction

• IPv4,IPv6, DHCP• Supports Bluetooth, WiFi , Etherrnet

via plugins for BlueZ, oFono…• NTP support• NwDataTransfer Thunderbolt

HMI Widgets

In NW Scope

Ethernet Phy

Ethernet based Vehicle Networking• Audio/Video Transmission

• Ethernet AVB

Bluetooth• Bluetooth Sack• Bluetooth Hands Free

DUMM• Download Manager• Messaging Manager• Upload Manager

Inter Node Communication• Node 2 Node communication• Autosar Vehicle ECU• FrancaIDL• Common API

= Active project


Services Framework• Communication Middleware• Distributed Applications • Franca IDL • Global Discovery/Connectivity

DLNA/UPnP

File Server

wpa_supplicant libcurl

Vehicle Interface• Automotive Message

Broker

Vehicle-to-X• V2I• V2V• V2V2I

System Infrastructure EG Scope



Lifecycle

• Start-up / shut-down, system & appl.• Running states and modes• Resource Control and Health Monitoring

Networking EG and AUTOSAR• For Inter Node Communication• Ethernet Command-and-Control

combined with IPC + IDL

Out of GENIVI Scope

Other EG

User Management • Profile Manager• User Identification• Data Import/Export

In SI Scope

Miscellaneous Libraries• libc/libusb/quota, ...

Basic OS Linux Kernel Features & Versions

Persistence• Reqs: Flash lifetime, robustness

• Persistence Client Library: Key-value storage API

• Evaluate filesystems/backends

• Persistence Administration Service

• Support & Guidelines for SQLite and similar

Inter Process Communication & IDL• D-Bus Optimization• IPC Common API• Franca IDL and Tools

= Active project


Bootloader

VehicleProcessor

Virtualization

Software Management• Download/Installation/deinstallation• Firmware Updates / External Device• OTA update

AutomotiveDiagnostic Log and Trace

VehicleSoftware Stack (i.e. AUTOSAR, ...)

Vehicle Diagnostics• Vehicle service• Diagnostic trouble codes, • etc.

HMI and Application Frameworks EG• Lots of topics around Lifeycle, SW loading, User mgmt, and Persistence.

Just about every GENIVI topic and component...• For Lifecycle and other interaction

Team Responsibilities

19-Nov-13Copyright © GENIVI Alliance 2009

GENIVI is a trademark of the GENIVI Alliance 20

Software

Platform

Requirements

Component

Architecture

Design

Component

Specification

Component

Design

Implementation

System Test

Integration Test

Component

(Black Box) Test

Unit (White Box)

Test

Vehicle

Requirements

and Use Cases

Acceptance TestAll EGs

and SAT

All EGs

and BIT

Individual EG

GENIVI Development Activities and Artifacts

Baselines

Compliance Program

Software Projects

• Yocto meta-ivi layer

• www.yoctoproject.org

• Baserock morphology

• www.baserock.org

• Yocto meta-ivi layer

• www.yoctoproject.org

• Baserock morphology

• www.baserock.org

• Platform Compliance Specification

• Component requirements and specifications

• UML model

• Platform Compliance Specification

• Component requirements and specifications

• UML model

• 17 public projects addressing IVI functionality and tools

• projects.genivi.org

• 17 public projects addressing IVI functionality and tools

• projects.genivi.org



• Baselines aim to implement GENIVI Compliance

Specification and serve a dual purpose:

– To prove that that the specification is feasible

– To provide EGs with development and testing environment

• Compliance Specification is generated from the

UML model

– Works in progress is typically stored in the Wiki

• Software projects include both platform

components and proofs of concept

GENIVI Artifacts in Details





Development Phases in EGs

Need

• Based on feature or technology to be supported

• Produces a scope description

Vehicle Level

• Produces vehicle-level actors, use cases and requirements

Software Platform

• Produces component architecture and software platform level requirements

Component

• Produces Component Specification (including the API and behavior)

Source Code

• Produces component implementation

Placeholder

Component

Abstract

Component

Specific

Component



Compliance Release Cycles

ReleaseX+1

ReleaseXM

atu

rity

Ch

eck

Co

mp

liance

Fre

eze

Co

mp

liance

Re

ad

y

Proposal C

Proposal B

Proposal A

Proposal D

Proposal E

Expert Groups start working

on the Proposals A to E

targeting the Release X

Proposal G

Proposal F

Proposals D and E miss the

Compliance Freeze and

Maturity Check milestones

respectively and move into

the Release X+1 along with

new Proposals F and G

Proposals A, B and C are

completed, reviewed and

approved in time and are

included into Release X

Baseline Release Cycle



Looking into the future



• Improve the baseline and IVI component quality

by introducing automated testing for both

functionality and performance

• Tighten the feedback loop between production

programs using GENIVI and the work in the

Expert Groups

• Grow the developer community and accelerate

platform adoption by reference applications and

support for specific boards

Future Directions



Introducing Compliance Testing

19-Nov-13Copyright © GENIVI Alliance 2009

GENIVI is a trademark of the GENIVI Alliance 28

Software

Platform

Requirements

Component

Architecture

Design

Component

Specification

Component

Design

Implementation

System Test

Integration Test

Component

(Black Box) Test

Unit (White Box)

Test

Vehicle

Requirements

and Use Cases

Acceptance Test

Test harness

Reference application

Out of scope for compliance testing

• Executable compliance test suite would help:

– Reducing cost of product quality assurance by software platform implementers (e.g. OSVs, Tier-1s)

– Reducing cost of acceptance testing by software platform customers (e.g. Tier-1s, OEMs)

– Increasing quality of the specifications, code and baselines produced by GENIVI

• Some tests are best expressed as sample

applications

• Improved quality of all GENIVI-based software

Benefits of Compliance Testing





Compliance Change Management

BoD � SAT21-day review, formal approval [Bylaws]BoD � SAT21-day review, formal approval [Bylaws]

SAT � EGCompliance Release Process [Wiki]SAT � EGCompliance Release Process [Wiki]

EG � ProjectAd hoc, differs across EGsEG � ProjectAd hoc, differs across EGs

BoD

SAT

EG

Project Project

EG

Project Project

Change management of the Platform Compliance Specification:

Common process

definition is

under discussion

감사합니다!Thank You!

질문?Questions?



genivi korea summit 2013 genivi development model€¦ · genivi korea summit 2013 ... a proper...

Documents