-
Notifications
You must be signed in to change notification settings - Fork 16
process introduction explanation #424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 2 commits
e10101c
ec90e14
cc4327c
ff626d9
8f0b390
c13b8cb
b8c9824
1d05c55
f2add6a
16acdbc
7bfcb78
4ec8283
a88e54d
81401a7
0be4e09
440c1eb
f84c6b7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,16 +28,19 @@ Introduction | |
|
|
||
| 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. | ||
|
|
||
| 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 | ||
| | * ASPICE | ||
| | * ISO 26262 | ||
| | * ISO 21434 | ||
| | * ISO PAS 8926 | ||
|
|
||
| The process model shall provide processes, which conform to state-of the art standards | ||
|
|
||
| * :ref:`ASPICE<standard_aspice_pam4>` | ||
| * :ref:`ISO 26262<standard_iso26262>` | ||
| * :ref:`ISO 21434<standard_isosae21434>` | ||
| * :ref:`ISO PAS 8926<standard_isopas8926>` | ||
|
|
||
| Approach | ||
| -------- | ||
|
|
@@ -47,7 +50,7 @@ Approach | |
| 3. We aim to develop the process in conformance to the targeted standards (compare figure below). | ||
| 4. We aim to establish traceability from the begin (compare :ref:`general_concepts_traceability`). | ||
| 5. We aim to verify conformity and traceability by tool automation as much as possible (compare figure below). | ||
| 6. We aim for an iterative collaboration model initiated by change requests (compare :need:`gd_guidl__change_change_request`) | ||
| 6. We aim for an iterative collaboration model initiated by change requests (compare :need:`gd_guidl__change_change_request`). | ||
|
|
||
|
|
||
| .. figure:: _assets/score_process_model.drawio.svg | ||
|
|
@@ -56,3 +59,15 @@ Approach | |
| :alt: Overview process model | ||
|
|
||
| Overview process model | ||
|
|
||
| The process model is structured around the concept of :ref:`workflows<workflows>`, which form the core of each :ref:`process<process_areas>`. 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 :ref:`work products<work_products>`, which are the tangible outputs or artifacts generated during process execution. Each work product is associated with or requested by relevant :ref:`standards<external_standards>` and :ref:`requirements<process_req>` of these standards, ensuring compliance and traceability. | ||
|
||
|
|
||
| To facilitate onboarding and understanding, the process model provides dedicated sections for a "Getting Started", a detailed "Concept Description", and comprehensive guideline (within the "Guidance" section) 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 :need:`Requirements process getting started<doc_getstrt__req_process>`, :need:`Requirement concept description<doc_concept__req_process>` and :need:`Requirement process guideline<gd_guidl__req_engineering>` as examples. | ||
|
|
||
| The model further integrates :ref:`templates<folder_templates>`, checklists (see :need:`requirement inspection checklist<doc__feature_name_req_inspection>` as example) and methods (see :need:`verification methods<gd_meth__verification_methods>` as example) to support the consistent and efficient execution of processes. | ||
|
||
|
|
||
| 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 :ref:`traceability<general_concepts_traceability>` according to the :ref:`meta model of the building blocks<general_concepts_building_blocks>` from the beginning and leverages tool automation to verify conformity and traceability as much as possible. Tools are evaluated and :ref:`qualified<tools_template>` by Committers, used by Contributors to execute workflows, and must fulfill defined process requirements to support efficient and compliant process execution. | ||
masc2023 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
Uh oh!
There was an error while loading. Please reload this page.