Concept Description#

Concept Description
status: valid

In this section concepts for the Process Management are discussed. Inputs for these concepts are the requirements of ISO26262 Part-2, ISO/SAE21434 Clause 5 and ASPICE Requirements from PA 3.1 Process definition process attribute, additionally including the requirements of the different stakeholders for the Process Management process.

Key concept#

A suitable standard process for developing software in an Open-Source environment is developed. The standard process aka process description is based on building blocks as shown here: Introduction. The central building blocks is the ‘workflow’ representing activities. Workflows have inputs and outputs, roles executing them and guidances to support the execution. Especially process requirements are defined to support automatic checks from tools designed for process deployment and implementation. Finally workflows are linked to standard requirements to show compliance with them.

Inputs#

  1. Stakeholders for the Process Management?

  2. Which building blocks are required?

  3. Which activities are required?

Stakeholders for the Process Management#

  1. Contributor (rl__contributor)

    • Contributes workflows, work products, guidances to grow the process content

    • Creates, Maintains Strategy

    • Defines, Monitors, Improves Strategy, Process Description and Implementation

  2. Process Community (rl__process_community)

    • Verifies that the contribution including strategy and definitions fulfills the project policies

    • Approves contributions

  3. Project Lead (rl__project_lead)

    • Supports all activities

  4. External Auditor (rl__external_auditor)

    • Supports all activities, especially during iterative audits

Standard Requirements#

Also requirements of standards need to be taken into consideration:

  • ISO 26262

  • ASPICE

  • ISO SAE 21434

Building blocks#

The required building blocks for the process description are defined here: Templates. They are complemented by requirements here: Process Requirements.

Activities for process management#

In general strategy, process descriptions and improvements are discussed during public Process Community Meetings. The Meeting schedules are available in the public calendar here: <https://calendar.google.com/calendar/u/0/r/month>. So every Contributor (rl__contributor) can join them discuss topics from interest there.

Creation/Maintenance of the Process Management Strategy#

The process management strategy is part of the Process description.

The process (meta) model (see Introduction) summarizes the strategy.

Further strategical concepts are defined here: General concepts.

Every Contributor (rl__contributor) can join the community meetings and contribute using standard pull requests.

Strategy changes are approved by the Process Community Member (rl__process_community).

Definition/Approval of the Process Description#

The process description is defined here: Process description.

Process areas as part of that representing the process definitions.

Every Contributor (rl__contributor) can join the community meetings and contribute using standard pull requests.

Process Description are approved by the Process Community Member (rl__process_community).

Regular audits supported by External Auditor (rl__external_auditor) ensure compliance with existing standards.

Monitoring/Improving of the Process Description Implementation#

The process strategy and description implementation is monitored and improvements are triggered, if required.

Every Contributor (rl__contributor) can propose improvements using the project ISSUE Tracking system.

Improvements are approved by the Process Community Member (rl__process_community).