Enabling Feature-Rich HMI Requirements for an open UI ... · Automotive Linux Summit 2012 Eva Brucherseifer 20.09.2012 21/22 Conclusion l Open UI Framework enables —software reuse

Enabling Feature-Rich HMIRequirements for an open UI Framework

basysKom embedded software engineering

l Software Engineering— Partner for the development of innovative quality products

l Expertise in...— Embedded R&D — Embedded architecture design, middleware, HMI— Open source standards & Linux stack

l Located in Germany, Darmstadt + Nürnberg

l Our role in Projects:— advisor for consulting on strategic and operational selection of

embedded technology and development processes— solution delivery R&D including delivery of full components or services

requiring specialist knowhow

Automotive Linux Summit 2012 3

The new digital lifestyle is changing user demand...This affects the software stack

I High demand for new digital lifestyle features in HMI

I Head unit needs to interact with other devices– Smartphone– Cloud

I Software features as a business model– Pay per use– Apps

Automotive Linux Summit 2012 Eva Brucherseifer

20.09.2012 4/22

New Requirements to Automotive Software

l 1 – Reduce time to market

l 2 – Increase flexibility— OS independency— Device independency

l 3 – Improve quality of software— Usability— Security— Stability— Scalability

l Sustainable Software Architecture


20.09.2012 5/22

Solution: Reuse of Open Software

l Reusable building blocks

l Standardized APIs

l Increase software quality + documentation

l Platform independent

l Open technology, reused by many

STANDARD

REUSEOPENOPEN UI FRAMEWORK


Why reuse software for HMI?

Why open?

And what does „open“ mean anyway?

Selection Criteria


20.09.2012 7/22

Why do we need a standardized UI framework?

l HMI developers want to focus on HMI — Stable & easy APIs

l Middleware logic and framework codeis a siginificant amount of software— Reuse

l HMI Implementation process

A— Complete HMI spec— Waterfall implementation

B— Agile HMI development in standard environment— Quick turnarounds

Features


20.09.2012 8/22

Why open?

l Control to the customer— No technology lock-in— No vendor lock-in— Possibility to influence the technology by contributing

l Different Quality— Used by many => suitable for many use cases, generic APIs— Ideas from worldwide communities enrich the technology

l Future-Safe— Licenses ensure future availability— Lifecycle: by investing into technology, increasing the market— Protects Investments


20.09.2012 9/22

Measure for Future Safety: Open Governance

l Open Governance Index— Published by VisionMobile in 2011

l 4 Criteria— Access— Development— Derivatives— Community

l 8 projects rated, range from 23% to 84%


20.09.2012 10/22

Selection Criteria for an Open UI Framework

l All source code under open source license

l Significant market share

l Ecosystem giving choice of IVSs

l Open governance implemented

l Support for HMI+touch implementation


Open UI Frameworks

I Android

I Web / HTML5

I Qt


20.09.2012 12/22

Required functionality of UI framework

l UI rendering optimized for Embedded hardware

l Easy creation of applications

l Access to platform functionality— Classical: file system, network, etc.— New: location, bluetooth, sound, video, etc.— Domain specific: mobile, car, tv, etc.

l Ability to add access to custom middleware

l Tools— IDE, toolchain support, debugging, translation


20.09.2012 13/22

Additional Qualities

l Clear & stable APIs reuse

l Easy coding amount of developers

l Little code per feature maintainability

l Can be extended easy middleware access

l Optimized for embedded fast

l Optimized for graphics designers can „code“

l No vendor lockin used by many

l Open source OEMs can influence


20.09.2012 14/22

AndroidTechnical Criteria

l No standalone framework, can only be used with Android platform

l Good Java APIsincluding a full set of APIs to access the systemgood documentation

l Native implementation

l Includes HTML5 support

l custom frameworks in C not well supportednon-standard glibclittle documentationglue code required (JNI)

l Build system Android

Java APIsApps

Custom Middleware


20.09.2012 15/22

AndroidNon-Technical Criteria

l Governance... Google!— Open governance index 23%— Little transparency— Trademarks heavily controlled

l Custom HMI requires significant effort, if possible at all

l Very few low level/middleware developers

l Many apps through Google market place

l Many Java developers


20.09.2012 16/22

HTML5Technical Criteria

l HTML5 + JavaScript: UI + application logic

l Very suitable for web / graphic designers

l (multi-)touch support not very well supported

l Runtime system

l Many JavaScript libraries available

l Open rendering engines:— WebKit + Backend UI Framework

(EFL, Qt, GtK, Android, Chrome, iOs, Windows...)— Gecko (firefox)

l Implementation fragmented

l Different level of feature implementation Linux

Graphics Toolkit

WebKit

appsHTML5 CSS3 JavaScript


20.09.2012 17/22

HTML5Technical Criteria

l Full HTML5 platforms— Tizen— WebOS— Firefox OS— Google Chrome OS

l Optimization and platform integration not straight forward

l Integration of custom middleware not straight forward

Linux

Graphics Toolkit

Web Rendering Engine

appsHTML5 CSS3 JavaScript

Cust

om M

iddl

ewar

e


20.09.2012 18/22

HTML5Non-Technical Criteria

l HTML5 + JavaScript APIs very standardized

l Platform & domain specific APIs missing

l Long standardization process

l Implementation specific interpretation of standards=> UI needs to handle differences

l many web developers available

l Not many webkit / gecko developers available

l Open Governance Index Webkit: 68%

l Open Governance Index Mozilla: 65%


20.09.2012 19/22

QtTechnical Criteria

l Toolkit dedicated for crossplatform application & UI development

l Very compact framework on top of Linux

l Optimized for embedded through plugins

l Hybrid use — Native Qt C++— QML descriptive UI language for touch, with JavaScript, runtime— HTML5 trough QtWebKit

l C++ => integration with middleware straight forward

l High-quality, stable and well-tested framework APIs

l standard mobile & domain specific APIs uncomplete


20.09.2012 20/22

QtNon-Technical Criteria

l Ownership: Nokia => Digia

l Ecosystem of ISVs exists

l Developers available

l Very good tool support

l LGPL

l Open governance index at 53%— Decision making process not fully open

l Used in the market since many years, in many different segments

l Very popular in mid-size companies


20.09.2012 21/22

Conclusion

l Open UI Framework enables— software reuse through standardized APIs— Quick HMI creation— Fast time-to-market of new use cases and OEM revenue models

l 3 Frameworks target different development cases— Android:

if full mobile platform without much need to customize is required— HTML5

currently: as addon for, hybrid systemsfull platforms and domain specific APIs in development

— Qtvery quick creation of custom HMI and middleware integrationready to go straigt forward toolkit with good tool support

l Standard Car API required


I Dr.-Ing. Eva Brucherseifer

Managing Director

basysKom GmbHRobert-Bosch-Str. 764293 DarmstadtGermany

[email protected]+49 (6151) 870 589 101

www.basyskom.com

Documents

Enabling Feature-Rich HMI Requirements for an open UI ... · Automotive Linux Summit 2012 Eva Brucherseifer 20.09.2012 21/22 Conclusion l Open UI Framework enables —software reuse