Automotive Linux Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

>>
> Starting the discussion on the AR I took two weeks back.
>
> My experience is it is good to have requirements structure aligned
> with the architecture structure.
>
> Tizen architecture is split into 'domains' and further down to
> 'subdomains'.
> However, for this purpose, domain level structure might be enough.
>
> The structure could be:
>
> D: App Framework
> D: Applications
> D: Automotive
> D: Base
> D: Graphics & UI Framework
> D: Location
> D: Messaging
> D: Mobile
> D: Multimedia
> D: Network & Connectivity
> D: Platform Development
> D: SDK
> D: Security
> D: Social & Content
> D: System
> D: Telephony
> D: Testing
> D: Web Framework
>
> We had originally agreed to use this structure in the AGL "reference
> architecture" that comes with the spec.
>

Proposed Use Cases to start analysis
  * Auxiliary port
  * Parking aid
  * Media player
  * Bluetooth audio
  * Climate Control

Automotive Linux Wiki

User Tools

Site Tools

Page Tools