Introduction#
Process Meta Model
|
status: valid
|
||||
Motivation#
The process model aims to establish organization rules for developing open source software in the automotive industry, which can be used in safety and security context.
Objectives#
The process model shall provide processes, which conform to state-of the art standards
Approach#
We aim for a process model as common basis for process documentation (compare figure below).
We work code centric (trace text as code) and iteratively.
We aim to develop the process in conformance to the targeted standards (compare figure below).
We aim to establish traceability from the begin (compare Traceability concept).
We aim to verify conformity and traceability by tool automation as much as possible (compare figure below).
We aim for an iterative collaboration model initiated by change requests (compare Change Request Guideline (gd_guidl__change_change_request)).
Fig. 1 Overview process model#
The process model is structured around the concept of workflows, which form the core of each process. Each workflow defines the sequence of activities required to achieve specific objectives within the project. The activities linked from these workflows are directly linked to roles, ensuring that responsibilities and accountabilities are clearly assigned throughout the process.
Workflows also establish connections to work products, which are often inputs and the tangible outputs or artifacts generated during process execution. Each work product is associated with or requested by relevant standards and requirements of these standards, ensuring compliance and traceability.
To facilitate onboarding and understanding, the process model provides dedicated sections for a “Getting Started” and a detailed “Concept Description” for each process. These resources help Contributors, Committers and other Users quickly familiarize themselves with the process, understand key concepts, and apply best practices throughout process execution and should be read in this order. See Requirements process getting started (doc_getstrt__req_process), Requirement concept description (doc_concept__req_process) as examples.
The model further integrates an comprehensive guideline (within the “Guidance” section), templates, checklists and methods for each workflow to support the consistent and efficient execution of processes. See the Requirement process guideline (gd_guidl__req_engineering), the requirement inspection checklist (doc__feature_name_req_inspection) and verification methods (gd_meth__verification_methods) as examples.
Additionally, the process model incorporates traceability mechanisms, allowing for the verification of conformity to standards such as ASPICE, ISO 26262, and others. The relationships between workflows, roles, work products, and supporting materials are visualized in the process model diagram above, providing a clear overview of how all elements interact to support process development and continuous improvement within the organization.
The process model follows a code-centric, iterative approach that establishes traceability according to the meta model of the building blocks from the beginning and leverages tool automation to verify conformity and traceability as much as possible. Tools are evaluated and qualified by Committers, used by Contributors to execute workflows, and must fulfill defined process requirements to support efficient and compliant process execution.