GENIVI Korea Summit 2013 Compliance Program & Works with GENIVI

Transcription

1 GENIVI Korea Summit 2013 Compliance Program & Works with GENIVI John Lehmann Sr. Marketing Manager / Board Member Mentor Graphics Pavel Konopelko Software Architect / SAT Lead Visteon Dashboard image reproduced with the permission of Visteon and 3M Corporation 1

2 Outline (1/2) 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) 2

3 Outline (2/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 3

4 PART I Introduce basic concepts of the platform compliance 4

5 Team Collaboration System Architecture Team CE Connectivity EG Korea REG HMI- Application Framework EG System Infrastructure EG Compliance Specification Location-Based Services EG Baseline Integration Team Networking EG Media and Graphics EG 5

6 GENIVI Software Model Product-Specific Software HMI Applications Software Platform Middleware Kernel Product- Specific Product- Specific 6

7 Goals of Platform Compliance upstart systemd Compliant Platforms All Platforms linux-3.0 linux

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 8

9 Component Types 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. 9

10 Component Type by Example Abstract Component: Specific Component: whizz_t produce(bang_t arg) { setup_whizzer(magic); return make_whizz(arg); } whizz_t produce(bang_t arg); // pre: arg!= 0 // post: is_whizzable(arg) implies result!= 0 Placeholder Component: * Component shall produce whizz whenever given a whizzable bang as an input. 10

11 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) 11

12 Platform Compliance Specification Compliance Specification Document Placeholder Components: Embedded Software Platform Requirements Abstract Components: Links to component specification documents and reference implementations Specific Components: Links to component implementations UML Model Component Specification Code Repositories Component Implementation Component Implementation 12

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

14 Platform Compliance History Architecture Implementation report released January 2010 Discovery: Compliance 2.0 released April 2012 Foton: Compliance 4.0 released April 2013 July 2011 Borg / Cassini: Compliance 1.0 released October 2012 Excalibur: Compliance 3.0 released October 2013 Gemini: Compliance 5.0 released Copyright GENIVI Alliance

15 GENIVI Software Platform

16 Highlights from Release 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 16

17 Changes since Previous Release 1/5 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) 17

18 Changes since Previous Release 2/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) 18

19 Changes since Previous Release 3/5 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) 19

20 Changes since Previous Release 4/5 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) 20

21 Changes since Previous Release 5/5 Removed obsolete components (continued): Tuner (Placeholder replaced by Tuner Middleware, Abstract) 21

22 Component Types by Release Specific Abstract Placeholder 22

23 Component Modifications in 2.0 Placeholder Abstract Added Removed Changed Specific

24 Component Modifications in 3.0 Placeholder Abstract Added Removed Changed Specific

25 Component Modifications in 4.0 Placeholder Abstract Added Removed Changed Specific

26 Component Modifications in 5.0 Placeholder Abstract Added Removed Changed Specific

27 Gemini References Compliance documents: ompliance+release+5.0+documents UML model repository: Baselines: ntegration+team#baselineintegrationteam- GENIVIbaselines 27

28 General References Projects and Baselines maintained by GENIVI: GENIVI Releases Summary: eleases Compliance Team and procedures: e+team 28

29 PART III Introduce Works with GENIVI 29

30 GENIVI Compliance Programs Compliance Program Today Platform Compliance Started in products 19 companies 60 platforms Today: 5 th incarnation of specification Works with GENIVI Started in 2013 after 12 months trial period and 5 submissions 30

31 WwG vs. Platform Compliance Product-Specific Software HMI Applications Software Platform Middleware Kernel Product- Specific Product- Specific Works with GENIVI Compliance Platform Compliance 31

32 Platform: It s all about components... (and requirements) PlaceholderComponent Requirement level AbstractComponent Behavior, APIs SpecificComponent Actual code (owned or adopted from upstream) Beyond platform (WwG) Other SW components of an IVI system Specification Evolution 32

33 Compliance: Priorities 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 33

34 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 34

35 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 35

36 Works with GENIVI:October 2013 Tuxera exfat component Jungo Multimedia player Wind River ipod connectivity solution accelerator (with disclaimer) Arynga CarSync (with disclaimer) Cinemo DVD Playback Engine 36

37 PART IV Introduce the process of submitting and reviewing applications 37

38 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 Compliance Explanation document describes the process and evaluation criteria Reviewers assigned by GENIVI clarify all questions related to the submission with the applicant Compliance Statement GENIVI Compliance Approval Group decides on whether the application is compliant On applicant s discretion, compliant products are listed under 38

39 Some Rules... 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 39

40 Compliance Program Participants 40

41 PART V Conclusions and future directions 41

42 Compliance Road Map Compliance Today Strictness Manual Verification Manual Verification + Registration Automated Verification + Registration Automated Functional + Non-functional Verification Compliance by end of Compliance Authority Some thoughts and plans Complexity, Effort (+cost) 42

43 Towards Automation: Database and Tools Started as a part of WwG: project to make review process easier Work is still in progress. Target: Q 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 43

44 Database Platform compliance Platform compliance submissions Implementation: packages (primarily baselines) WwG compliance submissions Approval Process 44

45 Tools File upload and input parsers Spreadsheet Dependency graphs Analysis tools Problem spotting Generating issues Review tools Generating and closing issues Approval processing 45

46 Works with GENIVI Program is going official after the trial period months Used for learning About the applications About the supporting infrastructure Announcing the results today 46

47 Lessons learned Expect the unexpected We needed to adjust some rules Submissions A kernel component Multimedia stacks FOTA solutions CE connectivity AVB stack SDK with codecs 47

48 감사합니다! Thank You! 질문? Questions? 48