Tizen Platform Architecture Overview
- 1 Tizen Architecture Overview
- 2 Tizen Domains
- 2.1 Applications, 
- 2.2 Web Framework, 
- 2.3 App Framework, 
- 2.4 Base, 
- 2.5 System, 
- 2.6 Security, 
- 2.7 Multimedia, 
- 2.8 Graphics & UI Framework, 
- 2.9 Network & Connectivity, 
- 2.10 Telephony, 
- 2.11 Messaging, 
- 2.12 Social & Content, 
- 2.13 Location, 
- 2.14 Platform Development, 
- 2.15 SDK, 
- 2.16 Automotive, 
- 2.17 Test APIs
Tizen Architecture Overview
|Web Applications||Native Applications||IVI Profile||Mobile Profile||Plat- form Develop- ment||S D K||T e s t A P I s|
|Web API||Native API|
|App Framework||Graphics & UI Framework||Multimedia||Location||Messaging||Web Framework|
|Security||System||Base||Network & Connectivity||Social & Content||Telephony|
|Linux kernel and device drivers|
Domains in Tizen group related functionality together. Access rights as defined in Tizen Governance are based on domains. Here is a summary of the current set of domains. The goal is to have one subpage per domain with more information. The domain architects, integrators, developers and reviewers can be found by following the external link after each domain name.
The domain and maintainer of a specific project in Gerrit can be found either via the "Access" link in Gerrit or in the "git-trees" file. The two are kept in sync automatically.
The description of the domains is tentative and still needs to be confirmed by the Tizen architects.
Reference applications, both native and web.
Web runtime and Web API implementation.
Application installation and life cycle management.
Everything required to boot a minimal Tizen system which provides a command line and system service management.
Additional services and components that are not required for the goals defined for the base system and that do not fall into one of the other domains.
Technology and tools which enable the implementation of a secure system. All Tizen developers, not just those working in the security domain, are responsible for security of their components.
Components handling graphic and sound data and playback. The graphics rendering itself is in the "Graphics & UI Framework" domain.
Responsible for rendering images and UI elements on a screen.
Core technology for exchanging data. This is the foundation on which the higher-level protocols in the other domains are built.
Core technology for speech and sound transmission.
Storage and transmission of messages (SMS, MMS, email, chat).
Storage and transmission of personal information management (PIM) data, excluding messages and multimedia files. Integration with social media web sites.
Location tracking and location-based services.
Tools and libraries required to build and develop the system software. In contrast to components in the Base and System domain, a Tizen device must be functional without the Platform Development components installed.
Tools and libraries for third-party application developers.
Anything specific to the IVI profile.
Tizen test tools and infrastructure for both native and web components. Not currently hosted on tizen.org and therefore does not have a public list of involved people.