User Tools
eg-requirements-specification
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
eg-requirements-specification [2018/11/07 06:53] ToshikazuOhiwa |
eg-requirements-specification [2018/11/07 13:34] waltminer |
||
|---|---|---|---|
| Line 7: | Line 7: | ||
| * Priorities and criteria of developing AGL UCB which OEMs can judge whether their in-vehicle software meet the specifications or not. | * Priorities and criteria of developing AGL UCB which OEMs can judge whether their in-vehicle software meet the specifications or not. | ||
| - | The System Architecture Team Charter which defines the membership requirements, roles, responsibilities, deliverables and more can be found [[agl-sat-charter|here]]. | + | This expert group has been created from meeting held in the Dresden AMM 2018 (slides available here). |
| + | * [[|Proposal Requirements Specification EG]] | ||
| + | |||
| ===== Meetings ===== | ===== Meetings ===== | ||
| - | The System Architecture Team meets every other Thursday. Meeting schedule, agenda, and minutes can be found [[agl-sat-meetings|here]]. | + | The Requirements Specification Expert Group meetings are TBD. Meeting schedule, agenda, and minutes can be found [[eg-requirements-specification:meetings| here]]. |
| ===== EG Members ===== | ===== EG Members ===== | ||
| - | There are two types of members in the System Architecture Team: Core Members and Expert Group Members. | + | TBD |
| - | + | ||
| - | + | ||
| - | ==== Core Members ==== | + | |
| - | + | ||
| - | The SAT shall have at least 5 but no more than 10 Core Members. | + | |
| - | * Core Members are invited through an open invitation to join the SAT from the SC Coordinator to the Steering Committee (SC). | + | |
| - | * Steering Committee (SC) Members may nominate themselves or others to join the SAT. | + | |
| - | * For the time being multiple members of SC member companies may participate in the SAT. In matters requiring a vote only one vote per company shall be permitted. | + | |
| - | + | ||
| - | * Nobuhiko Tanibata - Denso | + | |
| - | * Yuichi Kusakabe - Fujitsu TEN | + | |
| - | * Michael Fabry - Microchip | + | |
| - | * Tadao Tanikawa - Panasonic | + | |
| - | * Dominig Ar Foll - Intel | + | |
| - | * Fulup Ar Foll - Renesas / IoT.bzh | + | |
| - | * Takeshi Hoshina - Toyota | + | |
| - | + | ||
| - | + | ||
| - | ==== Expert Group Members ==== | + | |
| - | + | ||
| - | Each Expert Group is represented on the System Architecture Team by their technical lead or other delegate. System Architecture Team membership from the Expert Groups will change dynamically as Expert Groups are created and dissolved. Expert Group membership in the System Architecture Team is not limited by corporate affiliation. In other words, Expert Groups may be chaired by individuals that represent SAT Core Member Companies or multiple Expert Groups may be chaired by individuals from the same company. In these cases it is permissible to have more than one individual from a company to be members of the System Architecture Team. | + | |
| - | + | ||
| - | * [[eg-connectivity | Connectivity Expert Group]] - SAT Representative TBD | + | |
| - | + | ||
| - | * [[eg-app-fw | Application Framework and Security EG]] - SAT Representative TBD | + | |
| - | + | ||
| - | * [[eg-ciat | Continuous Integration and Test EG]] - Jan-Simon Moeller (LF) | + | |
| - | + | ||
| - | * [[eg-ui-graphics | UI and Graphics EG]] - Nobuhiko Tanibata (Denso) | + | |
| - | ===== Work in Progress ===== | + | ===== Documents ===== |
| - | These projects are being overseen by the System Architecture Team | + | Version 1 of the requirements specification can be downloaded [[https://docs.automotivelinux.org/docs/architecture/en/dev/reference/AGL_Specifications/agl_spec_v1.0_final.pdf | from the AGL Documentation site]]. |
| - | - [[project-security-fw|Security Framework for AGL and Tizen IVI]] - Develop security use cases and review Tizen IVI Application Framework against those use cases | + | The EG will create version 2 using the AGL Confluence site. The first step is to get the document into Confluence to begin editing. |
| - | - [[agl-roadmap | AGL Road Map]] | + | |
eg-requirements-specification.txt · Last modified: 2020/03/10 17:43 by waltminer
Page Tools
