Merge pull request eclipse-score#184 from eclipse-score/change_to_das_v130

Upgrade Doc-as-code and initial setup of process management

Author: aschemmel-tech

MODULE.bazel

@@ -50,4 +50,4 @@ bazel_dep(name = "buildifier_prebuilt", version = "8.2.0.2")
 ###############################################################################
 bazel_dep(name = "aspect_rules_lint", version = "1.5.3")
 bazel_dep(name = "score_tooling", version = "1.0.2")
-bazel_dep(name = "score_docs_as_code", version = "1.2.0")
+bazel_dep(name = "score_docs_as_code", version = "1.3.0")

process/index.rst

@@ -14,10 +14,10 @@
 
 .. _process_description:
 
-Process
-=======
+Process description
+===================
 
-Processes are the basis to describe the way of working within the S-CORE project.
+Processes are the basis to describe the way of working within a project.
 
 Introduction
 ------------
@@ -31,20 +31,20 @@ Introduction
 
 Process Model
 -------------
-The S-CORE process model is described by workflows, executed by roles and is creating work products.
+The project process model is described by workflows, executed by roles and is creating work products.
 Workflow activities are supported by guidances.
 
 .. figure:: _assets/score_process_area_overview.drawio.svg
   :width: 100%
   :align: center
-  :alt: Process area overview for **S-CORE** platform
+  :alt: Process area overview for the **Project**
 
-  Process area overview for **S-CORE** platform
+  Process area overview for **Project**
 
 General Concepts
 ~~~~~~~~~~~~~~~~
 
-General concepts like traceability of work products, life cycle model, buidling blocks can be found here:
+General concepts like traceability of work products, life cycle model, building blocks can be found here:
 
 .. toctree::
    :maxdepth: 1
@@ -54,7 +54,7 @@ General concepts like traceability of work products, life cycle model, buidling
 Process Areas
 ~~~~~~~~~~~~~
 
-The process description for the S-CORE project (e.g. requirements, architecture, safety management) can be found here:
+The process description for the project (e.g. requirements, architecture, safety management) can be found here:
 
 .. toctree::
    :maxdepth: 1
@@ -64,6 +64,8 @@ The process description for the S-CORE project (e.g. requirements, architecture,
 Process Role definition
 ~~~~~~~~~~~~~~~~~~~~~~~
 
+General roles not part of any process area.
+
 .. toctree::
    :maxdepth: 1
 
@@ -72,6 +74,8 @@ Process Role definition
 Work Products
 ~~~~~~~~~~~~~
 
+General work products not part of any process area and work product overview list.
+
 .. toctree::
    :maxdepth: 1
 
@@ -80,6 +84,8 @@ Work Products
 Workflows
 ~~~~~~~~~
 
+General workflows not part of any process area and workflow overview list.
+
 .. toctree::
    :maxdepth: 1
 
@@ -88,7 +94,7 @@ Workflows
 Standards
 ---------
 
-The the standard references the S-CORE project's processes are derived from can be found here:
+The the standard references the project's processes are derived from can be found here:
 
 .. toctree::
    :maxdepth: 1

process/introduction/_assets/score_process_model.drawio.svg

@@ -12,6 +12,8 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
+.. _process_areas:
+
 Process Areas
 #############
 
@@ -26,6 +28,7 @@ Process Areas
    implementation/index.rst
    platform_management/index.rst
    problem_resolution/index.rst
+   process_management/index.rst
    quality_management/index.rst
    release_management/index.rst
    requirements_engineering/index.rst

process/process_areas/index.rst

@@ -0,0 +1,23 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Guidance
+########
+
+.. toctree::
+   :maxdepth: 1
+
+   process_management_guideline
+   process_management_templates
+   process_management_reqs

process/process_areas/process_management/guidance/index.rst

@@ -0,0 +1,122 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+
+Guideline
+#########
+
+.. gd_guidl:: Process Management Guideline
+   :id: gd_guidl__process_management
+   :status: valid
+   :tags: process_management
+   :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311
+
+This document describes the general guidances for Process Management based on the concept which is defined :need:`[[title]]<doc_concept__process_management>`.
+
+General Hints
+=============
+
+The detailed implementation of all process areas defined in the process description for
+the project shall be described in the
+:ref:`Workflow Platform Management <workflow_platform_management>`.
+
+Templates
+---------
+
+The process and strategy description shall use the following templates:
+:ref:`process_management_templates`.
+
+Requirements
+------------
+
+For the process descriptions the following mandatory requirements exist:
+
+.. needtable:: Overview of mandatory process description requirements
+   :tags: process_management
+   :filter: "mandatory" in tags and "attribute" in tags and "process_management" in tags and is_external == False
+   :style: table
+   :columns: title
+   :colwidths: 30
+
+
+.. _workflow_process_management_requirements:
+
+
+Activities for Process Management
+=================================
+
+This section describes in detail which steps need to be performed for the process
+Management.
+
+.. list-table:: Activities for Process Management
+   :header-rows: 1
+   :widths: 10,60,30,30
+
+   * - Step
+     - Description
+     - Responsible
+     - Approver
+   * - :ref:`1. <pm_create_maintain_strategy>`
+     - Create/Maintain Process Management Strategy
+     - :need:`[[title]] <rl__contributor>`
+     - :need:`[[title]] <rl__process_community>`
+   * - :ref:`2. <pm_define_approve_process_description>`
+     - Define/Approve Process Description
+     - :need:`[[title]] <rl__contributor>`
+     - :need:`[[title]] <rl__process_community>`
+   * - :ref:`3. <pm_monitor_improve_process>`
+     - Monitor/Control Process Implementation
+     - :need:`[[title]] <rl__contributor>`
+     - :need:`[[title]] <rl__process_community>`
+
+
+.. _pm_create_maintain_strategy:
+
+Create/Maintain Process Strategy
+--------------------------------
+
+:need:`[[title]] <rl__contributor>` (as author, submitter) creates and maintains the
+process management strategy. They create Pull request (PR) for contributions.
+
+The potential contribution is discussed during the public Process Community Meetings
+or standard pull request reviews and if decided to implement,
+:need:`[[title]] <rl__process_community>` approves the Pull Request to include
+the contribution in the process strategy.
+
+
+.. _pm_define_approve_process_description:
+
+Define/Approve Process Description
+----------------------------------
+
+:need:`[[title]] <rl__contributor>` (as author, submitter) creates and maintains the
+process description. They create Pull request (PR) for contributions.
+
+The potential contribution is discussed during the public Process Community Meetings
+or standard pull request reviews and if decided to implement,
+:need:`[[title]] <rl__process_community>` approves the Pull Request to include
+the contribution in the process description.
+
+.. _pm_monitor_improve_process:
+
+Monitor/Improve Process
+-----------------------
+
+If potential improvements are detected, the :need:`[[title]] <rl__contributor>` triggers
+an ISSUE for improvement by using the
+`Issue Template Improvement <https://github.com/eclipse-score/process_description/blob/main/.github/ISSUE_TEMPLATE/2-improvement.yml>`_.
+
+The potential improvement is discussed during the public Process Community Meetings
+and if decided to implement, a pull request to follow :ref:`pm_create_maintain_strategy`
+or :ref:`pm_define_approve_process_description` must be created.

process/process_areas/process_management/guidance/process_management_guideline.rst

@@ -0,0 +1,114 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _process_management_requirements:
+
+
+Process Requirements
+====================
+
+
+.. gd_req:: Process Model Building Blocks
+   :id: gd_req__process_management_build_blocks
+   :status: valid
+   :tags: done_automation, attribute, mandatory
+   :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description
+   :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311
+
+   The process model building blocks are defined. Compare also the process model
+   overview here: :ref:`processes_introduction`.
+
+   Following building blocks are defined:
+
+      * Workflow
+      * Work Product
+      * Role (includes Team)
+
+   Additionally there shall be the following additions for workflows:
+
+      * Getting Started
+      * Concept
+      * Guidance
+
+   Additionally there shall be the following details for guidance:
+
+      * Guideline
+      * Template
+      * Checklist
+      * Method
+      * Process Requirements
+
+   Additionally there shall be the following additions for standard compliance:
+
+      * Standard Work Products
+      * Standard Requirements
+
+   Additionally there shall be the following additions to allow deployment examples or
+   templates for later deployment for work products:
+
+      * Document
+
+
+Process Building Blocks Attributes
+----------------------------------
+
+.. gd_req:: Building blocks attributes
+   :id: gd_req__process_management_build_blocks_attr
+   :status: valid
+   :tags: manual_prio_1, attribute, mandatory
+   :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description
+   :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311
+
+   Each building block shall have defined attributes as defined here:
+   :ref:`process_management_templates`.
+
+   Some have further constraints as defined here:
+
+   * The UID attribute must be unique.
+   * The STATUS attribute shall have a status: <draft|valid>
+   * The SAFETY attribute shall have level: <QM | ASIL_B>
+   * The SECURITY attribute shall have level: <YES|NO>
+   * Each building block shall have a description
+
+
+Process Building Blocks Linkage
+-------------------------------
+
+.. gd_req:: Building blocks linkage
+   :id: gd_req__process_management_build_blocks_link
+   :status: valid
+   :tags: manual_prio_1, attribute, mandatory
+   :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description
+   :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311
+
+   Each building block shall have defined links as defined here:
+   :ref:`process_management_templates`.
+
+
+Process Building Blocks Checks
+------------------------------
+
+.. gd_req:: Building blocks check
+   :id: gd_req__process_management_build_blocks_check
+   :status: valid
+   :tags: done_automation
+   :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description
+   :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311
+
+   It shall be checked, that all attributes defined here
+   :ref:`process_management_templates` are provided and correctly linked by the user.
+
+
+.. needextend:: docname is not None and "process_areas/process_management" in docname
+   :+tags: process_management