Skip to content

Commit 51598bb

Browse files
authored
Merge pull request #424 from etas-contrib/proper_general_workflow_description
process introduction explanation
2 parents 8347c13 + f84c6b7 commit 51598bb

File tree

39 files changed

+1104
-72
lines changed

39 files changed

+1104
-72
lines changed

process/index.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Workflow activities are supported by guidances.
4444
General Concepts
4545
~~~~~~~~~~~~~~~~
4646

47-
General concepts like traceability of work products, life cycle model, building blocks can be found here:
47+
The general concepts like traceability of work products, life cycle model, building blocks can be found here:
4848

4949
.. toctree::
5050
:maxdepth: 1
@@ -64,7 +64,7 @@ The process description for the project (e.g. requirements, architecture, safety
6464
Process Role definition
6565
~~~~~~~~~~~~~~~~~~~~~~~
6666

67-
General roles not part of any process area.
67+
The general roles that are not part of any process area and the project roles list can be found here:
6868

6969
.. toctree::
7070
:maxdepth: 1
@@ -74,7 +74,7 @@ General roles not part of any process area.
7474
Work Products
7575
~~~~~~~~~~~~~
7676

77-
General work products not part of any process area and work product overview list.
77+
The general work products that are not part of any process area and the work product overview list can be found here:
7878

7979
.. toctree::
8080
:maxdepth: 1
@@ -84,7 +84,7 @@ General work products not part of any process area and work product overview lis
8484
Workflows
8585
~~~~~~~~~
8686

87-
General workflows not part of any process area and workflow overview list.
87+
The general workflows that are not part of any process area and workflow overview list can be found here:
8888

8989
.. toctree::
9090
:maxdepth: 1
@@ -94,7 +94,7 @@ General workflows not part of any process area and workflow overview list.
9494
Standards
9595
---------
9696

97-
The the standard references the project's processes are derived from can be found here:
97+
The standard references the project's processes are derived from and the coverage of the requirements and the work products from the standards can be found here:
9898

9999
.. toctree::
100100
:maxdepth: 1

process/introduction/_assets/score_process_model.drawio.svg

Lines changed: 979 additions & 4 deletions
Loading

process/introduction/index.rst

Lines changed: 23 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -28,16 +28,19 @@ Introduction
2828

2929
Motivation
3030
----------
31-
| The process model aims to establish organization rules for developing
32-
| open source software in the automotive industry, which can be used in safety and security context.
31+
32+
The process model aims to establish organization rules for developing
33+
open source software in the automotive industry, which can be used in safety and security context.
3334

3435
Objectives
3536
----------
36-
| The process model shall provide processes, which conform to state-of the art standards
37-
| * ASPICE
38-
| * ISO 26262
39-
| * ISO 21434
40-
| * ISO PAS 8926
37+
38+
The process model shall provide processes, which conform to state-of the art standards
39+
40+
* :ref:`ASPICE<standard_aspice_pam4>`
41+
* :ref:`ISO 26262<standard_iso26262>`
42+
* :ref:`ISO 21434<standard_isosae21434>`
43+
* :ref:`ISO PAS 8926<standard_isopas8926>`
4144

4245
Approach
4346
--------
@@ -47,7 +50,7 @@ Approach
4750
3. We aim to develop the process in conformance to the targeted standards (compare figure below).
4851
4. We aim to establish traceability from the begin (compare :ref:`general_concepts_traceability`).
4952
5. We aim to verify conformity and traceability by tool automation as much as possible (compare figure below).
50-
6. We aim for an iterative collaboration model initiated by change requests (compare :need:`gd_guidl__change_change_request`)
53+
6. We aim for an iterative collaboration model initiated by change requests (compare :need:`gd_guidl__change_change_request`).
5154

5255

5356
.. figure:: _assets/score_process_model.drawio.svg
@@ -56,3 +59,15 @@ Approach
5659
:alt: Overview process model
5760

5861
Overview process model
62+
63+
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.
64+
65+
Workflows also establish connections to :ref:`work products<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 :ref:`standards<external_standards>` and :ref:`requirements<process_req>` of these standards, ensuring compliance and traceability.
66+
67+
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 :need:`Requirements process getting started<doc_getstrt__req_process>`, :need:`Requirement concept description<doc_concept__req_process>` as examples.
68+
69+
The model further integrates an comprehensive guideline (within the "Guidance" section), :ref:`templates<folder_templates>`, checklists and methods for each workflow to support the consistent and efficient execution of processes. See the :need:`Requirement process guideline<gd_guidl__req_engineering>`, the :need:`requirement inspection checklist<doc__feature_name_req_inspection>` and :need:`verification methods<gd_meth__verification_methods>` as examples.
70+
71+
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.
72+
73+
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.

process/process_areas/architecture_design/architecture_workflow.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,10 @@
1414
1515
.. _arch_workflow:
1616

17-
Architecture Workflow
18-
=====================
17+
Architecture Workflows
18+
######################
19+
20+
For a detailed explanation of workflows and their role within the process model, please refer to the :ref:`processes_introduction`.
1921

2022
.. workflow:: Create/Maintain Feature architecture
2123
:id: wf__cr_mt_featarch

process/process_areas/architecture_design/architecture_workproducts.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@
1414
1515
.. _arch_workproducts:
1616

17-
Architecture Workproducts
18-
=========================
17+
Architecture Work Products
18+
##########################
1919

2020
.. workproduct:: Feature Architecture
2121
:id: wp__feature_arch

process/process_areas/change_management/change_management_workflow.rst

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,10 @@
1414
1515
.. _chm_change_workflows:
1616

17-
Workflow Change Management
18-
##########################
17+
Change Management Workflows
18+
###########################
19+
20+
For a detailed explanation of workflows and their role within the process model, please refer to the :ref:`processes_introduction`.
1921

2022
.. workflow:: Create Change Request
2123
:id: wf__change_create_cr

process/process_areas/change_management/change_management_workproducts.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
# SPDX-License-Identifier: Apache-2.0
1313
# *******************************************************************************
1414
15-
Work Products Change Management
15+
Change Management Work Products
1616
###############################
1717

1818
.. workproduct:: Platform Change Management Plan

process/process_areas/configuration_management/configuration_workflow.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,11 @@
1313
# *******************************************************************************
1414
1515

16-
Workflows Configuration Management
16+
Configuration Management Workflows
1717
##################################
1818

19+
For a detailed explanation of workflows and their role within the process model, please refer to the :ref:`processes_introduction`.
20+
1921
The main work product is the configuration management plan, which is a part of the platform management plan.
2022
Thus the work flow :need:`wf__platform_cr_mt_platform_mgmt_plan` applies.
2123

process/process_areas/configuration_management/configuration_workproducts.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
# SPDX-License-Identifier: Apache-2.0
1313
# *******************************************************************************
1414
15-
Work Products Configuration Management
15+
Configuration Management Work Products
1616
######################################
1717

1818
.. workproduct:: Platform Configuration Management Plan

process/process_areas/documentation_management/documentation_workflow.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,11 @@
1212
# SPDX-License-Identifier: Apache-2.0
1313
# *******************************************************************************
1414
15-
16-
Workflow Documentation Management
15+
Documentation Management Workflow
1716
#################################
1817

18+
For a detailed explanation of workflows and their role within the process model, please refer to the :ref:`processes_introduction`.
19+
1920
The main work product is the documentation management plan, which is a part of the platform
2021
management plan. Thus the work flow :need:`wf__platform_cr_mt_platform_mgmt_plan` applies.
2122

0 commit comments

Comments
 (0)