Roles#
SCORE Management Roles#
Project Lead
|
status: valid
security: yes
safety: yes
|
||||
The Project Leads decide about strategy, addition of modules and election of all other roles. |
|||||
Technical Lead
|
status: valid
security: yes
safety: yes
|
||||
The Technical Leads approve feature requests and perform the project management on SCORE platform level. |
|||||
Safety Manager
|
status: valid
security: no
safety: yes
|
||||
The safety managers support the planning, development and coordination of the safety activities, i.e. the safety management. |
|||||
Quality Manager
|
status: valid
security: no
safety: no
|
||||
The quality managers shall be responsible for the planning and coordination of the quality activities, i.e. the quality management. |
|||||
Security Manager
|
status: draft
security: yes
safety:
|
||||
The security managers shall be responsible for the planning and coordination of the security activities. |
|||||
Module Project Lead
|
status: valid
security: yes
safety: yes
|
||||
The module Project Leads perform the project management on module level. If a module is developed in a sub-project of SCORE they have the eclipse project lead role for this. |
|||||
SCORE process roles#
Process Community Member
|
status: valid
security: yes
safety: yes
|
||||
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). |
|||||
SCORE development roles#
Infrastructure Tooling Community Member
|
status: valid
security: yes
safety: yes
|
||||
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
security:
safety:
|
||||
(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 SCORE. Note Follows the processes defined by the Process Community Member (RL_process_community) |
|||||
Committer
|
status: valid
security: yes
safety: yes
|
||||
(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. |
|||||
SCORE cross functional teams#
Platform Team
|
status: valid
security: yes
safety: yes
|
||||
The platform team is responsible for all artefacts within the platform SEooC. Additionally it is also responsible for the overall process including its support by tooling. |
|||||
Module Team
|
status: valid
security: yes
safety: yes
|
||||
The module team is responsible for all artefacts within the module SEooCs. Each module has only one responsible team but a team may also be responsible for several (small) modules. |
|||||
SCORE external roles#
External Assessor
|
status: valid
security: no
safety: yes
|
||||
The external assessor performs safety confirmation measures like safety audit, assessment and confirmation reviews. |
|||||