GENIVI Korea Summit 2013 Compliance Program & …...• Part IV: Introduce the process of submitting...

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 2013Compliance Program & Works with GENIVI

Pavel KonopelkoSoftware Architect / SAT Lead

Visteon

John LehmannSr. Marketing Manager / Board Member

Mentor Graphics

• Part I: Introduce basic concepts of the platform

compliance

– 8 slides: Team collaboration; Software model; goals of compliance; structure of the compliance specification; components types and examples (3); platform compliance artifacts

• Part II: Introduce the history of platform

compliance releases including 5.0 (Gemini)

– 10 slides: history timeline; 5.0 UML overview & highlights (2); release statistics (5); Gemini references (2)

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

Copyright © GENIVI Alliance 20132

Outline (1/2)

• Part III: Introduce Works with GENIVI

– 4 slides: Compliance programs; WwG vs. Platform; WwG goals; WwG components as of October 2013

• Part IV: Introduce the process of submitting and

reviewing applications

– 3 slides: Process; Rules, Participants

• Part V: Conclusions and future directions

– 4 slides, TBD: Compliance Road Map, Towards Automation, Database, Tools



Outline (2/2)

PART I

Introduce basic concepts of the platform compliance



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



Team Collaboration

GENIVI Software Model

Software Platform

Middleware

Kernel

Product-Specific Software

HMI

Applications

Product-

Specific

Product-

Specific





Goals of Platform Compliance

Compliant Platforms

All Platforms

systemd

upstart

linux-3.0

linux-2.6.35

19-Nov-13 8

Structure of Compliance Specification

• Compliance Specification is a list of components

– 3 component types: Placeholder, Abstract, Specific:

– 2 component priorities: P1 (mandatory), P2 (desired):

• Compliant implementation must include all P1 components



• Placeholder Component

Component that is defined only by a set of requirements that its specific implementation has to fulfill. The requirements are typically specified as informal textual statements about the component responsibilities and the services it provides.

• Abstract Component

Component that is defined by its provided and required interfaces as well as its behavior, but does not refer to any specific implementation. Interfaces are defined by their operation signatures. Behavior can be defined in any convenient way.

• Specific Component

Component that is ultimately defined by its implementation available in form of the source code.



Component Types



Component Type by Example

Placeholder Component:

* Component shall produce whizz

whenever given a whizzable bang

as an input.

Abstract Component:

whizz_t produce(bang_t arg);

// pre: arg != 0

// post: is_whizzable(arg) implies result != 0

Specific Component:

whizz_t produce(bang_t arg)

{

setup_whizzer(MAGIC);

return make_whizz(arg);

}

Component Examples



• Placeholder components:

– Browser (requirements on rendering, caching, etc.)

– SpeechOutputService (requirements on TTS engine)

• Abstract components:

– OpenGL-ES (as specified by the Khronos Group)

– SensorsService (API to access vehicle sensor data)

• Specific components:

– Linux Kernel (from kernel.org, version 3.0 or later)

– Automotive DLT (from projects.genivi.org, version 2.2 or later)

Compliance Specification DocumentCompliance Specification Document

Platform Compliance Specification



Specific Components:Abstract Components:Placeholder Components:

Embedded Software

Platform Requirements

Links to component

specification documents and

reference implementations

Links to component

implementations

Component

Specification

Component

Implementation

Component

Implementation

UML Model

Code Repositories

PART II

Introduce the history of platform compliance releases including 5.0 (Gemini)





Platform Compliance History

Architecture Implementation report released

January 2010

July 2011

Borg / Cassini:Compliance 1.0

released

Discovery:Compliance 2.0

released

April 2012

October 2012

Excalibur:Compliance 3.0

released

Foton:Compliance 4.0

released

April 2013

October 2013

Gemini:Compliance 5.0

released



GENIVI Software Platform 5.0

• Introduced new components

– Near Field Communication (NFC) Stack

– Media Indexing and Playback

– Mirror Link and Smart Device Link

– Node Health Monitor, Node Resource Manager

• Reworked existing components

– Echo Cancellation and Noise Reduction (ECNR)

– Navigation interfaces

– Speech-related services

• Cleaned up the specification



Highlights from Release 5.0

• Introduced new components:

– ECNR Controller, ECNR Engine (Placeholder)

– Media Indexer, Media Playback Control (Placeholder)

– MirrorLink, SmartDeviceLink (Placeholder)

– Node Health Monitor, Node Resource Manager (Placeholder)

– SpeechDialogService, SpeechInputService, SpeechOutputService (Placeholder)

– INC Transport Protocol (Abstract)

– Near Field Communication Stack (Abstract)

– popup manager (Abstract)19-Nov-13



Changes since Previous Release 1/5

• Introduced new components (continued):

– Tuner Middleware (Abstract)

• Promoted existing components:

– Bluetooth Media Playback (from Placeholder to Abstract)

• Changed existing components:

– CE Device Manager (Placeholder—revised requirements)

– Graphics Backend Server (Placeholder—defined reference implementation)




• Changed existing components (continued):

– EnhancedPositionService, GNSSService, SensorsService (Abstract—increased minimum required version)

– MapViewer, NavigationCore (Abstract—increased minimum required version)

– OpenGL-ES (Abstract—defined reference implementation)

– Profile Manager (Abstract—increased minimum required version)

– FUSE (Specific—changed priority)




• Removed obsolete components:

– Echo Cancellation Engine, Noise Reduction Engine (Placeholder—replaced by ECNR Engine and ECNR Controller)

– INC Messenger (Placeholder—replaced by INC Transport Protocol, Abstract)

– Indexing Engine (Placeholder—replaced by Media Indexer)

– Speech Engine (Placeholder—replaced by SpeechDialogService, SpeechInputService, SpeechOutputService)




• Removed obsolete components (continued):

– Tuner (Placeholder—replaced by Tuner Middleware, Abstract)






Component Types by Release

27 25 24 25 24

5 12 1622 27

3030 29

2630

0

10

20

30

40

50

60

70

80

90

1.0 2.0 3.0 4.0 5.0

Specific Abstract Placeholder



Component Modifications in 2.0

0 2 4 6 8 10 12

Specific

Abstract

Placeholder

Added

Removed

Changed




0 2 4 6 8 10 12

Specific

Abstract

Placeholder

Added

Removed

Changed

• Compliance documents:

– https://collab.genivi.org/wiki/display/genivi/GENIVI+Compliance+Release+5.0+documents

• UML model repository:

– https://svn.genivi.org/uml-model/genivi/tags/Release_5.0_Gemini

• Baselines:

– https://collab.genivi.org/wiki/display/genivi/Baseline+Integration+Team#BaselineIntegrationTeam-GENIVIbaselines



Gemini References

• Projects and Baselines maintained by GENIVI:

– http://projects.genivi.org/

• GENIVI Releases Summary:

– https://collab.genivi.org/wiki/display/genivi/GENIVI+Releases

• Compliance Team and procedures:

– https://collab.genivi.org/wiki/display/genivi/Compliance+Team



General References

PART III

Introduce Works with GENIVI





GENIVI Compliance Programs

Compliance Program Today

Platform Compliance

Works with GENIVI

Started in 2010http://genivi.org/compliant

-products

19 companies

60 platforms

Today: 5th incarnation of

specification

Started in 2013

after 12 months trial

period and 5 submissions

WwG vs. Platform Compliance

Software Platform

Middleware

Kernel

Product-Specific Software

HMI

Applications

Product-

Specific

Product-

Specific Platform Compliance

Works with

GENIVI Compliance



• Platform:

– PlaceholderComponent

• Requirement level

– AbstractComponent

• Behavior, APIs

– SpecificComponent

• Actual code (owned or adopted from upstream)

• Beyond platform (WwG)

– Other SW components of an IVI system



It‘s all about components ... (and requirements)

Sp

ecifica

tion

Ev

olu

tion

• Each component and requirement is assigned a priority

– Components and requirements:

• P1 = mandatory. Disclosure is mandated.

• P2 = optional. Disclosure is desired (but not mandatory)

– Requirements:

• P3 = Purely optional. No disclosure needed.

– Used for roadmap items etc



Compliance: Priorities



Platform Compliance Program Goals

Define a set of standardized components and requirements

for OS platform, middleware, and frameworks

Provide source code level compliance and interoperability

Allow multiple distributions to be compliant, public or

commercial distros

Allow some differentiation while still meeting compliance



WwG Compliance Program Goals

Extend compliance beyond platform (applications)

Allow compliance registrations of Abstract- and

Placeholder Component implementations

Increase confidence in GENIVI platform by registering

software based on it

Works with GENIVI:October 2013



Jungo – Multimedia player

(with disclaimer) Arynga – CarSync

(with disclaimer) Cinemo – DVD Playback Engine

Tuxera – exFAT component

Wind River – iPod connectivity solution accelerator

PART IV

Introduce the process of submitting and reviewing applications



Compliance Application and Review Process

Applicant verify that their software product fulfills GENIVI Compliance Specification

Applicant fills out GENIVI Compliance Statement and submits it for review

Reviewers assigned by GENIVI clarify all questions related to the submission with the applicant

GENIVI Compliance Approval Group decides on whether the application is compliant

On applicant’s discretion, compliant products are listed under http://www.genivi.org/compliant-products



Compliance

Explanation document

describes the process

and evaluation criteria

Compliance

Statement

• Compliance is claimed for a given release• Approved compliance never expires

• Implementation of components and requirements for a specific platform (needs to specify HW)

• Does not automatically propagate to new releases

• 2 years period of accepting applications for a given release

• Inputs for approvals

– Platform

• Spreadsheet

– Works with GENIVI

• Spreadsheet (based on platform)

• Lists of build and runtime dependencies



Some Rules ....

Compliance Program Participants



PART V

Conclusions and future directions



Compliance Road Map



Complexity , Effort (+cost)

Str

ictn

ess

Manual

Verification

Manual

Verification +

Registration

Automated

Verification +

Registration

Automated

Functional +

Non-functional

Verification

Compliance

Authority

Compliance

Today

Compliance

by end of

2013.

Some

thoughts

and plans

• Started as a part of WwG: project to make

review process easier

– Work is still in progress. Target: Q4 2013.

• Content:

– Compliance database

– IT infrastructure

• Web server

– Set of Web-based tools ([PHP] scripts)

• Parsers for inputs (spreadsheets and dependency graphs)

• Analysis tools: spot obvious discrepancies– E.g. Missing P1‘s



Towards Automation: Database and Tools

19-Nov-13 44

Database



Platform compliance

Platform compliance

submissions

Implementation: packages

(primarily baselines)

WwG compliance

submissions

Approval Process



Tools

• File upload and input parsers

– Spreadsheet

– Dependency graphs

• Analysis tools

– Problem spotting

– Generating issues

• Review tools

– Generating and closing issues

– Approval processing

• Program is going official after the trial period

– 6 + 6 months

– Used for learning

• About the applications

• About the supporting infrastructure

– Announcing the results today

Works with GENIVI



• Expect the unexpected ☺

– We needed to adjust some rules

• Submissions

– A kernel component

– Multimedia stacks

– FOTA solutions

– CE connectivity

– AVB stack

– SDK with codecs

Lessons learned



감사합니다!Thank You!

질문?Questions?



GENIVI Korea Summit 2013 Compliance Program & …...• Part IV: Introduce the process of submitting...

Documents

Transcript of GENIVI Korea Summit 2013 Compliance Program & …...• Part IV: Introduce the process of submitting...