Roles#

SCORE Management Roles#

Project Lead
status: valid
security:
safety:
status: valid

The Project Leads decide about strategy, addition of modules and election of all other roles.

Required skills

  • Degree: Master’s degree in electrical engineering/computer science/mathematics, or similar degree, or comparable work experience

  • Solid understanding of project management

  • Technical know-how of embedded systems

  • Preferred training: Basic and Management specific safety and security trainings

Experience

  • 3 years of experience in project or line management

Responsibility

Authority

  • Ultimate decisions on escalated topics

  • Election and replacement of all role’s personnel

  • Decide on addition/removal of modules repositories or split-off of projects

Technical Lead
status: valid
security:
safety:

The Technical Leads approve feature requests and perform the project management of the SCORE platform.

Required skills

  • Degree: Master’s degree in electrical engineering/computer science/mathematics, or similar degree, or comparable work experience

  • Know-How of project management

  • Technical know-how of embedded systems

  • Preferred training: Basic and Management specific safety and security trainings

Experience

  • 2 years of experience in project management or similar position

Responsibility

  • Review and approval of contributions, e.g. Feature Requests, which add or modify SCORE platform features

  • Project management of the platform development - i.e. filling the project management role as defined by ISO26262

  • High-level project control and coordination between multiple software modules

  • Escalation instance for software module project leads (external to S-CORE), safety managers and committers

  • Planning the releases of the S-CORE SW platform and modules

Authority

  • Decisions in the technical lead circle

  • Approving the releases of the S-CORE SW platform and modules

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
status: valid
tags: project_management
safety: yes
security: 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
status: valid
tags: development
safety: yes
security: 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)

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
status: valid
tags: cross_functional
safety: yes
security: 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.