Roles#
S-CORE Management Roles#
Project Lead
|
status: valid
|
||||
The Project Leads decide about strategy, addition of modules and election of all other roles. Required skills
Experience
Responsibility
Authority
|
|||||
Technical Lead
|
status: valid
|
||||
The Technical Leads approve feature requests and perform the project management of the S-CORE platform. Required skills
Experience
Responsibility
Authority
|
|||||
Quality Manager
|
status: valid
|
||||
The quality managers shall be responsible for the planning and coordination of the quality activities, i.e. the quality management. |
|||||
Security Manager
|
status: draft
|
||||
The security managers shall be responsible for the planning and coordination of the security activities. |
|||||
Module Project Lead
|
status: valid
|
||||
The module Project Leads perform the project management on module level. If a module is developed in a sub-project of S-CORE they have the eclipse project lead role for this. |
|||||
S-CORE process roles#
Process Community Member
|
status: valid
|
||||
The process community members are responsible for the definition of the process architecture of the project integrated management system and how they processes interact. The approval and release of the process is done by the safety, quality and security managers and the technical leads (for the parts which affect them). |
|||||
S-CORE development roles#
Infrastructure Tooling Community Member
|
status: valid
|
||||
The infrastructure and tooling community members are responsible for the infrastructure and tooling setup for development namely github, bazel, sphinx-needs, but also the rest of the tool chain. |
|||||
Contributor
|
status: valid
|
||||
(Eclipse) Open Source Role, person(s) who provide(s) possible contribution(s) as pull request(s) to the main line. Any contributor which contributes code, tests or documentation to S-CORE. Note Follows the processes defined by the Process Community Member (rl__process_community) |
|||||
Committer
|
status: valid
|
||||
(Eclipse) Open Source Role, person(s) who accept(s) possible contribution(s) as pull request(s) to the main line and maintains the product. Note Defines and enforces processes. |
|||||
Testing Community Member
|
status: valid
|
||||
The testing community members are responsible for the test case development from component to platform level. They shall be included in any requirements reviews. They can also improve independence argumentation when involved in the development of unit testing on safety critical units. In this way the testing community takes a supportive role for unit testing |
|||||
S-CORE cross functional teams#
Platform Team
|
status: valid
|
||||
The platform team is responsible for all artifacts within the platform SEooC. Additionally it is also responsible for the overall process including its support by tooling. |
|||||
Module Team
|
status: valid
|
||||
The module team is responsible for all artifacts within the module SEooCs. Each module has only one responsible team but a team may also be responsible for several (small) modules. |
|||||