Remove Technical Lead Role

process/folder_templates/features/feature_name/index.rst

@@ -84,7 +84,7 @@ Specification
 
    .. note::
       A CR shall specify the stakeholder requirements as part of our platform/project.
-      Thereby the :need:`rl__technical_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
+      Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
 
 
 

process/folder_templates/modules/module_name/component_name/docs/index.rst

@@ -72,7 +72,7 @@ Specification
 
    .. note::
       A CR shall specify the component requirements as part of our platform/project.
-      Thereby the :need:`rl__module_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
+      Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
 
 
 

process/process_areas/architecture_design/guidance/architecture_guideline.rst

@@ -166,7 +166,7 @@ Following roles should be included in the review:
 
 * :need:`[[title]] <rl__safety_manager>`
 * :need:`[[title]] <rl__security_manager>`
-* :need:`[[title]] <rl__technical_lead>`
+* :need:`[[title]] <rl__project_lead>`
 * :need:`[[title]] <rl__committer>`
 
 .. _create_component_architecture:

process/process_areas/change_management/change_management_concept.rst

@@ -54,7 +54,7 @@ Stakeholders for the Change Requests
    * Approves all change request activities besides changes closing
    * Is responsible to initiate the the closure of the change request
 
-#. :need:`Technical Lead <rl__technical_lead>`, :need:`Module Lead <rl__module_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 
    * Supports all change request activities
    * Approves the closing of the change request
@@ -106,8 +106,7 @@ by authorized persons.
 
 Authorized person includes
 
-#. :need:`Technical Lead <rl__technical_lead>`
-#. :need:`Module Lead <rl__module_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 #. :need:`Safety Manager <rl__safety_manager>`
 #. :need:`Security Manager <rl__security_manager>`
 #. :need:`Quality Manager <rl__quality_manager>`
@@ -124,7 +123,7 @@ monitored.
 The Change Request implementation must be tracked until it is closed.
 
 The status of the Change Request must be communicated by the
-:need:`Technical Lead <rl__technical_lead>` or :need:`Module Lead <rl__module_lead>` until
+:need:`Project Lead <rl__project_lead>` until
 the implementation is completed and confirmed.
 
 .. _chm_closing:

process/process_areas/change_management/change_management_roles.rst

@@ -21,8 +21,7 @@ Contributing Roles:
 
    * :need:`Contributor <rl__contributor>`
    * :need:`Committer <rl__committer>`
-   * :need:`Technical Project Lead <rl__technical_lead>`
-   * :need:`Module Project Lead <rl__module_lead>`
+   * :need:`Project Lead <rl__project_lead>`
    * :need:`Safety Manager <rl__safety_manager>`
    * :need:`Security Manager <rl__security_manager>`
    * :need:`Quality Manager <rl__quality_manager>`

process/process_areas/change_management/change_management_workflow.rst

@@ -23,7 +23,7 @@ Workflow Change Management
    :tags: change_management
    :responsible: rl__contributor
    :approved_by: rl__committer
-   :supported_by: rl__technical_lead, rl__module_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
+   :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record
@@ -41,7 +41,7 @@ Workflow Change Management
    :status: valid
    :tags: change_management
    :responsible: rl__contributor
-   :approved_by: rl__technical_lead, rl__module_lead
+   :approved_by: rl__project_lead
    :supported_by: rl__committer, rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request
@@ -64,7 +64,7 @@ Workflow Change Management
    :tags: change_management
    :responsible: rl__contributor
    :approved_by:  rl__committer
-   :supported_by: rl__technical_lead, rl__module_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
+   :supported_by: rl__project_lead, rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :contains: gd_guidl__change_change_request, gd_temp__change_feature_request, gd_temp__change_component_request, gd_temp__change_impact_analysis, gd_temp__component_classification, gd_temp__change_decision_record
@@ -89,7 +89,7 @@ Workflow Change Management
    :status: valid
    :tags: change_management
    :responsible: rl__committer
-   :approved_by: rl__technical_lead, rl__module_lead
+   :approved_by: rl__project_lead
    :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__issue_track_system, wp__feat_request, wp__cmpt_request
    :output: wp__issue_track_system, wp__feat_request, wp__cmpt_request

process/process_areas/change_management/guidance/change_management_guideline.rst

@@ -93,15 +93,15 @@ This section describes in detail which steps need to be performed for a Change R
    * - :ref:`2. <chm_analyze_change_request>`
      - Analyze Change Request
      - :need:`[[title]] <rl__contributor>`
-     - :need:`[[title]] <rl__technical_lead>`, :need:`[[title]] <rl__module_lead>`
+     - :need:`[[title]] <rl__project_lead>`
    * - :ref:`3. <chm_imp_mon_change_request>`
      - Implement and Monitor Change Request
      - :need:`[[title]] <rl__contributor>`
      - :need:`[[title]] <rl__committer>`
    * - :ref:`4. <chm_close_change_request>`
      - Close Change Request
      - :need:`[[title]] <rl__committer>`
-     - :need:`[[title]] <rl__technical_lead>`, :need:`[[title]] <rl__module_lead>`
+     - :need:`[[title]] <rl__project_lead>`
 
 
 .. _chm_create_change_request:
@@ -172,7 +172,7 @@ When ready to review and to analyze, the author sets the status to "in review" m
 
 Analyze Change Request
 ----------------------
-The projects :need:`[[title]] <rl__technical_lead>` or :need:`[[title]] <rl__module_lead>` supported by
+The projects :need:`[[title]] <rl__project_lead>` supported by
 :need:`[[title]] <rl__committer>` (includes Safety, Security and Quality Manager) analyzes the change
 request together with the :need:`[[title]] <rl__contributor>` and takes a decision with
 the submitting/authoring contributor for accepting or rejecting it.
@@ -241,8 +241,8 @@ When ready to implement, the author sets the status to "in implementation" manua
   | * The **Development** section should be used to link to an pull request
   | * The **Create a branch** action may used to create automatically a linked pull request
 
-During the implementation of the change the responsible lead :need:`[[title]] <rl__technical_lead>`
-or :need:`[[title]] <rl__module_lead>` reports regularly the status to the affected
+During the implementation of the change the responsible lead :need:`[[title]] <rl__project_lead>`
+reports regularly the status to the affected
 projects teams.
 
 The author has the freedom to cancel the change request at any time by setting the status to "rejected".
@@ -262,7 +262,7 @@ is sufficient before the status is changed to closed. To check, if it is suffici
 Further the effectiveness of the implemented measure is confirmed and the availability
 of the required reports, as well as verification results, if applicable.
 
-When confirmed, the :need:`[[title]] <rl__technical_lead>` or :need:`[[title]] <rl__module_lead>`
+When confirmed, the :need:`[[title]] <rl__project_lead>`
 sets the status to "closed" manually, if not done automatically.
 
 .. note::

process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst

@@ -53,7 +53,7 @@ Estimates for realization
 [Describe here which stakeholder and which roles of the stakeholder are involved to execute the Change Request]
 
    .. note::
-      Typically the :need:`Technical Project Leads <rl__technical_lead>` or :need:`Module Leads <rl__module_lead>` are involved
+      Typically the :need:`Project Leads <rl__project_lead>` are involved
       for planning and approval activities. As well as :need:`Safety Manager <rl__safety_manager>` or :need:`Security Manager <rl__security_manager>`
       are responsible for Change Request which has impact on functional safety or security.
 

process/process_areas/configuration_management/configuration_concept.rst

@@ -42,7 +42,7 @@ Inputs
 Stakeholders
 ^^^^^^^^^^^^
 
-#. :need:`Technical Lead <rl__technical_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 
    * for creating a module or a platform release a baseline of all configuration items is needed
 

process/process_areas/configuration_management/configuration_getstrt.rst

@@ -19,7 +19,7 @@ Getting Started
    :id: doc_getstrt__configuration_process
    :status: valid
 
-In case you are appointed as a :need:`Technical Lead <rl__technical_lead>` by the :need:`rl__project_lead` in the project:
+In case you are appointed as a :need:`rl__project_lead` in the project:
 
 * On platform level, process community provides a draft configuration management plan,
   based on the template :need:`gd_temp__config_mgt_plan`, just set it to "valid"

process/process_areas/configuration_management/configuration_roles.rst

@@ -21,8 +21,7 @@ Contributing Roles:
 
    * :need:`Contributor <rl__contributor>`
    * :need:`Committer <rl__committer>`
-   * :need:`Technical Lead <rl__technical_lead>`
-   * :need:`Module Project Lead <rl__module_lead>`
+   * :need:`Project Lead <rl__project_lead>`
 
 A detailed overview of the responsibility for the steps of the configuration management is listed here:
 

process/process_areas/configuration_management/guidance/configuration_templates.rst

@@ -115,7 +115,7 @@ Branches are used as a means of parallel development. In the <project name> proj
 * main branch - a "remote" branch (named "main") which contains all the latest file versions checked by CI, reviewed, accepted and merged.
 * release branch - a "remote" branch derived from main branch which is used to prepare a release,
   no functional code changes are allowed, only bug fixes and verification based improvements.
-  Only the technical lead is allowed to approve a merge into a release branch. The branch name is given as defined in :need:`doc_concept__rel_process`.
+  Only the project lead is allowed to approve a merge into a release branch. The branch name is given as defined in :need:`doc_concept__rel_process`.
 
 The "remote" branch is not "local" to the developer but resides on the "remote" version management server.
 

process/process_areas/documentation_management/documentation_concept.rst

@@ -51,7 +51,7 @@ Stakeholders
 
    * planning and status reporting of work products and their documentation for the platform
 
-#. :need:`Module Lead <rl__module_lead>`
+#. :need:`Module Lead <rl__project_lead>`
 
    * planning and status reporting of work products and their documentation for modules
 

process/process_areas/documentation_management/documentation_roles.rst

@@ -22,7 +22,7 @@ Contributing Roles:
    * :need:`Contributor <rl__contributor>`
    * :need:`Committer <rl__committer>`
    * :need:`Project Lead <rl__project_lead>`
-   * :need:`Module Project Lead <rl__module_lead>`
+   * :need:`Module Project Lead <rl__project_lead>`
    * :need:`Safety Manager <rl__safety_manager>`
    * :need:`Security Manager <rl__security_manager>`
    * :need:`Quality Manager <rl__quality_manager>`

process/process_areas/platform_management/guidance/platform_management_guideline.rst

@@ -25,7 +25,7 @@ This document describes the general guidances for Platform Management based on t
 General Hints
 =============
 
-The detailed implementation of the Platform Management Plan for **S-CORE** is described in the `[[title]]<REPLACE_doc__platform_mgt_plan>`.
+A template of the Platform Management Plan for <Project> is described in the `[[title]]<gd_temp__platform_mgmt_plan>`.
 
 An iterative and incremental development model shall be used.
 
@@ -48,7 +48,7 @@ Activities for Platform Management Plan
 Create/Maintain Platform Management Plan
 ----------------------------------------
 
-The platform management is created and maintained by the :need:`Technical Lead <rl__technical_lead>`.
+The platform management is created and maintained by the :need:`Project Lead <rl__project_lead>`.
 As it is a container, this activity is valid for all addressed plan documents.
 
 It may consider:
@@ -109,7 +109,7 @@ Training pathes are described. These may include:
 Monitor/Improve Platform Management Plan
 ----------------------------------------
 
-:need:`Technical Lead <rl__technical_lead>` is responsible for the monitoring of the
+:need:`Project Lead <rl__project_lead>` is responsible for the monitoring of the
 work products and activities against the platform management plan. If deviations are detected,
 the plan must be adjusted. Deviations may include estimates, resources, schedules, plans,
 interfaces, etc. as defined in the scope of work.

process/process_areas/platform_management/platform_management_concept.rst

@@ -44,13 +44,9 @@ Inputs
 Stakeholders for the Platform Management Plan
 *********************************************
 
-#. :need:`Technical Lead <rl__technical_lead>`
+#. :need:`Project Lead <rl__project_lead>`
 
-   * Plans, Develops, Controls and Adjust all platform project activities
-
-#. :need:`Module Lead <rl__module_lead>`
-
-   * Plans, Develops, Controls and Adjust all module project activities
+   * Plans, Develops, Controls and Adjust all platform, module project activities
 
 #. :need:`Committer <rl__committer>`
 #. :need:`Contributor <rl__contributor>`
@@ -78,12 +74,12 @@ Activities for the Platform Management Plan
 Create/Maintain Platform Management Plan
 ========================================
 
-The platform management is created and maintained by the :need:`Technical Lead <rl__technical_lead>`.
+The platform management is created and maintained by the :need:`Project Lead <rl__project_lead>`.
 As it is a container, this activity is valid for all addressed plan documents.
 
 Monitor/Improve Platform Management Plan
 ========================================
 
-:need:`Technical Lead <rl__technical_lead>` is responsible for the monitoring of the
+:need:`Project Lead <rl__project_lead>` is responsible for the monitoring of the
 work products and activities against the platform management plan. If deviations are detected,
 the plan must be adjusted.

process/process_areas/platform_management/platform_management_getstrt.rst

@@ -20,8 +20,8 @@ Getting Started
    :status: valid
    :tags: platform_management
 
-In case you want to manage contributions to **S-CORE** consider to:
+In case you want to manage contributions to <Project> consider to:
 
-* Contact the :need:`Technical Lead <rl__technical_lead>` for your contribution to establish planning and reporting
+* Contact the :need:`Project Lead <rl__project_lead>` for your contribution to establish planning and reporting
 * Make familiar with the management, development and supporting process descriptions in :ref:`process_description`
-* Make familiar with the relevant sections of the `Platform Management Plan <REPLACE_doc__platform_mgt_plan>`, especially `REPLACE_doc__project_mgt_plan`
+* Make familiar with the relevant sections of the `Platform Management Plan <gd_temp__platform_mgmt_plan>`

process/process_areas/platform_management/platform_management_roles.rst

@@ -15,63 +15,11 @@
 Roles
 #####
 
-.. role:: Technical Lead
-   :id: rl__technical_lead
-   :status: valid
-
-   The Technical Leads approve feature requests and perform the project management of the SCORE platform.
-
-   Required skills
-
-   * Degree: Master's degree in electrical engineering/computer science/mathematics, or similar degree, or comparable work experience
-   * Know-How of project management
-   * Technical know-how of embedded systems
-   * Preferred training: Basic and Management specific safety and security trainings
-
-   Experience
-
-   * 2 years of experience in project management or similar position
-
-   Responsibility
-
-   * Review and approval of contributions, e.g. Feature Requests, which add or modify SCORE platform features
-   * Project management of the platform development - i.e. filling the project management role as defined by ISO26262
-   * High-level project control and coordination between multiple software modules
-   * Escalation instance for software module project leads (external to S-CORE), safety managers and committers
-   * Planning the releases of the S-CORE SW platform and modules
-
-   Authority
-
-   * Decisions in the technical lead circle
-   * Approving the releases of the S-CORE SW platform and modules
-
-
-.. role:: Module Project Lead
-   :id: rl__module_lead
-   :status: valid
-   :tags: project_management
-   :contains: rl__committer
-
-   The Module Project Leads perform the project management on module level.
-   If a module is developed in a sub-project of S-CORE they have the eclipse project lead role for this.
-
-   For Module Project Leads the same required skills, experiences apply as for the Technical Leads.
-
-   Responsibility
-
-   * Review and approval of contributions, e.g. Feature Requests, which add or modify module features
-   * Project management of the module development - i.e. filling the project management role as defined by ISO26262
-   * High-level project control and coordination between multiple software components within the module
-   * Escalation instance for software module contributor, safety managers and committers within the module
-   * Planning the releases of the module
-
-   Authority
-
-   * Decisions in the technical lead circles of the module
-   * Approving the releases of module
+For platform management no additional roles need to be defined.
 
 Contributing Roles:
 
+   * :need:`Project Lead <rl__project_lead>`
    * :need:`Process Community <rl__process_community>`
    * :need:`Safety Manager <rl__safety_manager>`
    * :need:`Security Manager <rl__security_manager>`

process/process_areas/platform_management/platform_management_workflow.rst

@@ -21,7 +21,7 @@ Workflow Platform Management
    :id: wf__platform_cr_mt_platform_mgmt_plan
    :status: valid
    :tags: platform_management
-   :responsible: rl__technical_lead
+   :responsible: rl__project_lead
    :approved_by: rl__process_community
    :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__policies, wp__issue_track_system
@@ -39,16 +39,16 @@ Workflow Platform Management
    :id: wf__platform_mr_im_platform_mgmt_plan
    :status: valid
    :tags: platform_management
-   :responsible: rl__technical_lead
+   :responsible: rl__project_lead
    :approved_by: rl__process_community
    :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager
    :input: wp__platform_mgmt, wp__project_mgt, wp__document_mgt_plan, wp__config_mgt_plan
    :output: wp__issue_track_system
    :contains: gd_temp__platform_mgmt_plan, gd_guidl__platform_mgmt_plan, gd_guidl__documentation, gd_chklst__documentation_review
    :has: doc_concept__platform_process, doc_getstrt__platform_process
 
-   The :need:`Technical Lead <rl__technical_lead>` is responsible for the monitoring and reporting
+   The :need:`Project Lead <rl__project_lead>` is responsible for the monitoring and reporting
    of the work products and activities against the platform management plan.
 
-   The :need:`Technical Lead <rl__technical_lead>` is responsible to adjust the plan,
+   The :need:`Project Lead <rl__project_lead>` is responsible to adjust the plan,
    if deviations are detected.

process/process_areas/platform_management/platform_management_workproducts.rst

@@ -28,7 +28,7 @@ Work Products Platform Management
    * all work products can be uniquely identified and reproduced in a controlled manner at any time
    * relations and differences between versions can be traced
    * contributions are managed, analysed and controlled including changes of the work products during the project life cycle
-   * documents are concise, clearly structured, understandable for intended users, verifiable, maintainable, and organized according to S-CORE procedures to facilitate information retrieval
+   * documents are concise, clearly structured, understandable for intended users, verifiable, maintainable, and organized according to <Project> procedures to facilitate information retrieval
 
 .. workproduct:: Project Management Plan
    :id: wp__project_mgt