Skip to content
This repository was archived by the owner on Apr 17, 2019. It is now read-only.

requirements overview.md

lang edited this page Mar 5, 2015 · 1 revision

Overview of IRIS Feature Requirements

IRIS stands for "Infrastructure and Release Information System", and it is supposed to be a information center of all Tizen development cycles and the runtime infrastructure services.

As the user interfaces, IRIS will provide web based applications as the first stage. And the web applications will be designed as [SPA][1], and the operation of server data will be through Ajax HTTP requests. Please see the document of architecture design for more details.

Because the API oriented design, we can also provide command line tool in the future for advanced users.

As the requirements from Tizen developers and managers, IRIS will provide the following features:

  • snapshot-table
  • pkgdb
  • change-tracker

Besides the above scheduled features, maybe other features like blow can also be provided:

  • changes-reports
  • system-quality-trending

Each feature will be implemented as a standalone SPA, and all of the online SPA links will be listed in the portal page.

For each scheduled feature, please see its corresponding document for more details.

Roles in Tizen Development

We need to analyze the user requirements based on the different roles of users accordingly. There are mainly the following 4 types of roles:

  • Developers - Tizen developers of runtime packages
  • RE - Release Engineer
  • PM - Managers
  • QA - Testing team

[1]: http://en.wikipedia.org/wiki/Single-page_application [SPA]

Clone this wiki locally