diff --git a/process/folder_templates/features/feature_name/index.rst b/process/folder_templates/features/feature_name/index.rst index eb822b045d..bdfecfaa9e 100644 --- a/process/folder_templates/features/feature_name/index.rst +++ b/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). diff --git a/process/folder_templates/modules/module_name/component_name/docs/index.rst b/process/folder_templates/modules/module_name/component_name/docs/index.rst index f0af123528..56de20e6fd 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/index.rst +++ b/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). diff --git a/process/process_areas/architecture_design/guidance/architecture_guideline.rst b/process/process_areas/architecture_design/guidance/architecture_guideline.rst index dd52dcce91..e1215a2842 100644 --- a/process/process_areas/architecture_design/guidance/architecture_guideline.rst +++ b/process/process_areas/architecture_design/guidance/architecture_guideline.rst @@ -166,7 +166,7 @@ Following roles should be included in the review: * :need:`[[title]] ` * :need:`[[title]] ` -* :need:`[[title]] ` +* :need:`[[title]] ` * :need:`[[title]] ` .. _create_component_architecture: diff --git a/process/process_areas/change_management/change_management_concept.rst b/process/process_areas/change_management/change_management_concept.rst index 35bfa2f8c6..959320dfe4 100644 --- a/process/process_areas/change_management/change_management_concept.rst +++ b/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 `, :need:`Module Lead ` +#. :need:`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 ` -#. :need:`Module Lead ` +#. :need:`Project Lead ` #. :need:`Safety Manager ` #. :need:`Security Manager ` #. :need:`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 ` or :need:`Module Lead ` until +:need:`Project Lead ` until the implementation is completed and confirmed. .. _chm_closing: diff --git a/process/process_areas/change_management/change_management_roles.rst b/process/process_areas/change_management/change_management_roles.rst index f1b87b088a..55914f8a7f 100644 --- a/process/process_areas/change_management/change_management_roles.rst +++ b/process/process_areas/change_management/change_management_roles.rst @@ -21,8 +21,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` - * :need:`Technical Project Lead ` - * :need:`Module Project Lead ` + * :need:`Project Lead ` * :need:`Safety Manager ` * :need:`Security Manager ` * :need:`Quality Manager ` diff --git a/process/process_areas/change_management/change_management_workflow.rst b/process/process_areas/change_management/change_management_workflow.rst index ce908edc66..b848cfaf7e 100644 --- a/process/process_areas/change_management/change_management_workflow.rst +++ b/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 diff --git a/process/process_areas/change_management/guidance/change_management_guideline.rst b/process/process_areas/change_management/guidance/change_management_guideline.rst index 2c1320ab47..06c7e97477 100644 --- a/process/process_areas/change_management/guidance/change_management_guideline.rst +++ b/process/process_areas/change_management/guidance/change_management_guideline.rst @@ -93,7 +93,7 @@ This section describes in detail which steps need to be performed for a Change R * - :ref:`2. ` - Analyze Change Request - :need:`[[title]] ` - - :need:`[[title]] `, :need:`[[title]] ` + - :need:`[[title]] ` * - :ref:`3. ` - Implement and Monitor Change Request - :need:`[[title]] ` @@ -101,7 +101,7 @@ This section describes in detail which steps need to be performed for a Change R * - :ref:`4. ` - Close Change Request - :need:`[[title]] ` - - :need:`[[title]] `, :need:`[[title]] ` + - :need:`[[title]] ` .. _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]] ` or :need:`[[title]] ` supported by +The projects :need:`[[title]] ` supported by :need:`[[title]] ` (includes Safety, Security and Quality Manager) analyzes the change request together with the :need:`[[title]] ` 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]] ` -or :need:`[[title]] ` reports regularly the status to the affected +During the implementation of the change the responsible lead :need:`[[title]] ` +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]] ` or :need:`[[title]] ` +When confirmed, the :need:`[[title]] ` sets the status to "closed" manually, if not done automatically. .. note:: diff --git a/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst b/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst index ed4b8161ae..5810bdf6d3 100644 --- a/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst +++ b/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 ` or :need:`Module Leads ` are involved + Typically the :need:`Project Leads ` are involved for planning and approval activities. As well as :need:`Safety Manager ` or :need:`Security Manager ` are responsible for Change Request which has impact on functional safety or security. diff --git a/process/process_areas/configuration_management/configuration_concept.rst b/process/process_areas/configuration_management/configuration_concept.rst index b56fc67be7..a8f9f0f5ab 100644 --- a/process/process_areas/configuration_management/configuration_concept.rst +++ b/process/process_areas/configuration_management/configuration_concept.rst @@ -42,7 +42,7 @@ Inputs Stakeholders ^^^^^^^^^^^^ -#. :need:`Technical Lead ` +#. :need:`Project Lead ` * for creating a module or a platform release a baseline of all configuration items is needed diff --git a/process/process_areas/configuration_management/configuration_getstrt.rst b/process/process_areas/configuration_management/configuration_getstrt.rst index df4a4486c3..af123fee9f 100644 --- a/process/process_areas/configuration_management/configuration_getstrt.rst +++ b/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 ` 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" diff --git a/process/process_areas/configuration_management/configuration_roles.rst b/process/process_areas/configuration_management/configuration_roles.rst index e217a3507f..3eb4ecffe9 100644 --- a/process/process_areas/configuration_management/configuration_roles.rst +++ b/process/process_areas/configuration_management/configuration_roles.rst @@ -21,8 +21,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` - * :need:`Technical Lead ` - * :need:`Module Project Lead ` + * :need:`Project Lead ` A detailed overview of the responsibility for the steps of the configuration management is listed here: diff --git a/process/process_areas/configuration_management/guidance/configuration_templates.rst b/process/process_areas/configuration_management/guidance/configuration_templates.rst index 3dc1086e0e..46afef2f13 100644 --- a/process/process_areas/configuration_management/guidance/configuration_templates.rst +++ b/process/process_areas/configuration_management/guidance/configuration_templates.rst @@ -115,7 +115,7 @@ Branches are used as a means of parallel development. In the 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. diff --git a/process/process_areas/documentation_management/documentation_concept.rst b/process/process_areas/documentation_management/documentation_concept.rst index 39943cf51a..65c19e4d87 100644 --- a/process/process_areas/documentation_management/documentation_concept.rst +++ b/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 ` +#. :need:`Module Lead ` * planning and status reporting of work products and their documentation for modules diff --git a/process/process_areas/documentation_management/documentation_roles.rst b/process/process_areas/documentation_management/documentation_roles.rst index 75b6bf13ec..26e85e7e31 100644 --- a/process/process_areas/documentation_management/documentation_roles.rst +++ b/process/process_areas/documentation_management/documentation_roles.rst @@ -22,7 +22,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` * :need:`Project Lead ` - * :need:`Module Project Lead ` + * :need:`Module Project Lead ` * :need:`Safety Manager ` * :need:`Security Manager ` * :need:`Quality Manager ` diff --git a/process/process_areas/platform_management/guidance/platform_management_guideline.rst b/process/process_areas/platform_management/guidance/platform_management_guideline.rst index f11417e6ef..e092447444 100644 --- a/process/process_areas/platform_management/guidance/platform_management_guideline.rst +++ b/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]]`. +A template of the Platform Management Plan for is described in the `[[title]]`. 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 `. +The platform management is created and maintained by the :need:`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 ` is responsible for the monitoring of the +:need:`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. diff --git a/process/process_areas/platform_management/platform_management_concept.rst b/process/process_areas/platform_management/platform_management_concept.rst index ae094d88f9..f8325688dc 100644 --- a/process/process_areas/platform_management/platform_management_concept.rst +++ b/process/process_areas/platform_management/platform_management_concept.rst @@ -44,13 +44,9 @@ Inputs Stakeholders for the Platform Management Plan ********************************************* -#. :need:`Technical Lead ` +#. :need:`Project Lead ` - * Plans, Develops, Controls and Adjust all platform project activities - -#. :need:`Module Lead ` - - * Plans, Develops, Controls and Adjust all module project activities + * Plans, Develops, Controls and Adjust all platform, module project activities #. :need:`Committer ` #. :need:`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 `. +The platform management is created and maintained by the :need:`Project Lead `. As it is a container, this activity is valid for all addressed plan documents. Monitor/Improve Platform Management Plan ======================================== -:need:`Technical Lead ` is responsible for the monitoring of the +:need:`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. diff --git a/process/process_areas/platform_management/platform_management_getstrt.rst b/process/process_areas/platform_management/platform_management_getstrt.rst index 11f6ee3b6c..75d8ace0ff 100644 --- a/process/process_areas/platform_management/platform_management_getstrt.rst +++ b/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 consider to: -* Contact the :need:`Technical Lead ` for your contribution to establish planning and reporting +* Contact the :need:`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 `, especially `REPLACE_doc__project_mgt_plan` +* Make familiar with the relevant sections of the `Platform Management Plan ` diff --git a/process/process_areas/platform_management/platform_management_roles.rst b/process/process_areas/platform_management/platform_management_roles.rst index e3866f2e5c..d7eebca0fb 100644 --- a/process/process_areas/platform_management/platform_management_roles.rst +++ b/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 ` * :need:`Process Community ` * :need:`Safety Manager ` * :need:`Security Manager ` diff --git a/process/process_areas/platform_management/platform_management_workflow.rst b/process/process_areas/platform_management/platform_management_workflow.rst index 43386c9f01..4f2764cacf 100644 --- a/process/process_areas/platform_management/platform_management_workflow.rst +++ b/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,7 +39,7 @@ 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 @@ -47,8 +47,8 @@ Workflow Platform Management :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 ` is responsible for the monitoring and reporting + The :need:`Project Lead ` is responsible for the monitoring and reporting of the work products and activities against the platform management plan. - The :need:`Technical Lead ` is responsible to adjust the plan, + The :need:`Project Lead ` is responsible to adjust the plan, if deviations are detected. diff --git a/process/process_areas/platform_management/platform_management_workproducts.rst b/process/process_areas/platform_management/platform_management_workproducts.rst index f6fcf9201f..26e255d4e5 100644 --- a/process/process_areas/platform_management/platform_management_workproducts.rst +++ b/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 procedures to facilitate information retrieval .. workproduct:: Project Management Plan :id: wp__project_mgt diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst index 8e055da3ec..e9d3bd7b16 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst @@ -83,7 +83,7 @@ This section describes in detail which steps need to be performed for a Problem * - :ref:`4. ` - Close Problem Resolution - :need:`[[title]] ` - - :need:`[[title]] `, :need:`[[title]] ` + - :need:`[[title]] ` .. _prm_create_problem_report: @@ -237,8 +237,8 @@ When ready to implement, the author sets the status to "in implementation" manua | * The automatically created branch name reflects the issue UID and the title as | * **126-bug-stkh_req__archdes_example_req-has-no-content** -During the resolution the responsible lead :need:`[[title]] ` or -:need:`[[title]] ` reports regularly the status to the affected +During the resolution the responsible lead :need:`[[title]] ` +reports regularly the status to the affected projects teams. Escalations topics should be documented in the description, if possible. diff --git a/process/process_areas/problem_resolution/problem_resolution_concept.rst b/process/process_areas/problem_resolution/problem_resolution_concept.rst index b9ceb9a958..9a3ecbf80f 100644 --- a/process/process_areas/problem_resolution/problem_resolution_concept.rst +++ b/process/process_areas/problem_resolution/problem_resolution_concept.rst @@ -53,7 +53,7 @@ Stakeholders for the Problem Report * Approves all problem resolution activities besides problem closing * Is responsible to initiate the the closure of the problem reported -#. :need:`Technical Lead `, :need:`Module Lead ` +#. :need:`Project Lead ` * Supports all problem resolution activities * Approves the closing of the problem resolution @@ -106,8 +106,7 @@ by authorized persons. Authorized person includes -#. :need:`Technical Lead ` -#. :need:`Module Lead ` +#. :need:`Project Lead ` #. :need:`Safety Manager ` #. :need:`Security Manager ` #. :need:`Quality Manager ` @@ -124,7 +123,7 @@ monitored. The Problem Resolution implementation must be tracked until it is closed. The status of the Problem Report must be communicated by the -:need:`Technical Lead ` or :need:`Module Lead ` until +:need:`Project Lead ` until the implementation is completed and confirmed. .. _prm_closing: diff --git a/process/process_areas/problem_resolution/problem_resolution_roles.rst b/process/process_areas/problem_resolution/problem_resolution_roles.rst index acec91ecdc..3e2e200e0b 100644 --- a/process/process_areas/problem_resolution/problem_resolution_roles.rst +++ b/process/process_areas/problem_resolution/problem_resolution_roles.rst @@ -21,8 +21,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` - * :need:`Technical Lead ` - * :need:`Module Project Lead ` + * :need:`Project Lead ` * :need:`Safety Manager ` * :need:`Security Manager ` * :need:`Quality Manager ` diff --git a/process/process_areas/problem_resolution/problem_resolution_workflow.rst b/process/process_areas/problem_resolution/problem_resolution_workflow.rst index 27309d68f9..cc054c8eec 100644 --- a/process/process_areas/problem_resolution/problem_resolution_workflow.rst +++ b/process/process_areas/problem_resolution/problem_resolution_workflow.rst @@ -22,7 +22,7 @@ Workflow Problem Resolution :status: valid :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__prm_plan :output: wp__issue_track_system :contains: gd_temp__problem_template, gd_chklst__problem_cr_review, gd_guidl__problem_problem @@ -39,7 +39,7 @@ Workflow Problem Resolution :status: valid :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__prm_plan :output: wp__issue_track_system :contains: gd_temp__problem_template, gd_chklst__problem_cr_review, gd_guidl__problem_problem @@ -60,7 +60,7 @@ Workflow Problem Resolution :status: valid :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__prm_plan :output: wp__issue_track_system :contains: gd_temp__problem_template, gd_chklst__problem_cr_review, gd_guidl__problem_problem @@ -83,7 +83,7 @@ Workflow Problem Resolution :id: wf__problem_close_pr :status: valid :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__prm_plan :output: wp__issue_track_system diff --git a/process/process_areas/quality_management/quality_concept.rst b/process/process_areas/quality_management/quality_concept.rst index 74f584f486..50c3bd15d6 100644 --- a/process/process_areas/quality_management/quality_concept.rst +++ b/process/process_areas/quality_management/quality_concept.rst @@ -79,4 +79,4 @@ or in a continuous manner. Only 100% compliant work products / releases will be Every person who contributes shall be trained according to Quality aspects. The committers will help to ensure the Quality by following the workflows which are defined in the different process areas. The Quality Manager is responsible for the Quality related workflows. The Quality Manager shall be independent from the development organization with a escalation -to the Project Lead Circle and the Technical Lead Circle. +to the Project Lead Circle. diff --git a/process/process_areas/release_management/guidance/release_guideline.rst b/process/process_areas/release_management/guidance/release_guideline.rst index 7509e67e34..e6f7bf5cbe 100644 --- a/process/process_areas/release_management/guidance/release_guideline.rst +++ b/process/process_areas/release_management/guidance/release_guideline.rst @@ -106,8 +106,8 @@ Tracking and Communication 2. **Communication**: * Regularly update all stakeholders on the release status as part of the project lead circle. - * Hold periodic meetings to discuss progress, issues, and dependencies within the tech lead circle. - * meeting definition and schedule is defined in the projects's platform managemnt plan, as defined in :need:`gd_guidl__platform_mgmt_plan`. + * Hold periodic meetings to discuss progress, issues, and dependencies within the project lead circle. + * meeting definition and schedule is defined in the projects's platform management plan, as defined in :need:`gd_guidl__platform_mgmt_plan`. Templates diff --git a/process/process_areas/release_management/guidance/release_templates.rst b/process/process_areas/release_management/guidance/release_templates.rst index 83b3edc295..7cf2389d75 100644 --- a/process/process_areas/release_management/guidance/release_templates.rst +++ b/process/process_areas/release_management/guidance/release_templates.rst @@ -104,7 +104,7 @@ Templates | Release for | ------------------------------------------------------- | - | 1. Link this issue to the correct milestone and assign to the technical lead + | 1. Link this issue to the correct milestone and assign to the project lead | 2. Check respective Verification report on the release candidate's baseline | 3. Check bugfixes or justify failed tests | 4. Check the safety package completeness (includes "valid" documents and work products status, supported by the safety manager) diff --git a/process/process_areas/release_management/release_concept.rst b/process/process_areas/release_management/release_concept.rst index 98132f800f..254584ded9 100644 --- a/process/process_areas/release_management/release_concept.rst +++ b/process/process_areas/release_management/release_concept.rst @@ -47,36 +47,30 @@ Platform Release Plan The platform release plan provides a reliable plan on what software modules can be expected in the upcoming platform release. The platform release plan is reflected by feature requests which are -demanded. Therefore it is of importance that the *Technical Leads* on platform level are aligned with -the various software module *Technical Leads* and to align the platform release +demanded. Therefore it is of importance that the *Project Leads* on platform level are aligned with +the various software module *Project Leads* and to align the platform release plan properly with the module release plan as the platform release plan has a clear dependency on its output. -#. :need:`Tech Lead Circle ` +#. :need:`Project Lead Circle ` * Defines and proposes scope of individual module release * Creates and maintains the platform release plan * Aligns module release timeline with platform release plan - -#. :need:`Project Lead Circle ` - * Approves the platform release plan Platform Release ================ -The Platform Release contains the full *S-CORE* scope which spans over many modules. The releases -are proposed by the *Technical Leads* and approved by *Project Leads*. Every software module +The Platform Release contains the full scope which spans over many modules. The releases +are proposed and approved by *Project Leads*. Every software module has its own repository which contains multiple components, their requirements, architecture, implementation and tests. -#. :need:`Tech Lead Circle ` +#. :need:`Project Lead Circle ` * Define and proposes scope of release * Writes platform release notes - -#. :need:`Project Lead Circle ` - * Approves the platform release notes * Adds and removes software modules to the platform * Releases the platform @@ -85,15 +79,12 @@ Module Release Plan =================== The module release plan gives a guidance when certain features can be expected on a module level. -It is created by the respective *Tech Leads* and *Project Leads* of the module. +It is created by the respective *Project Leads* of the module. -#. :need:`Tech Lead Circle ` +#. :need:`Project Lead Circle ` * Define and proposes scope of individual module Release * Creates and maintains the module release plan - -#. :need:`Project Lead Circle ` - * Approves the module release plan Module Release @@ -102,12 +93,9 @@ Module Release Each software module needs to have its dedicated release and the accompanying release notes. Only released software modules can be included into a platform release. -#. :need:`Tech Lead Circle ` - - * Provides the software module release notes - #. :need:`Project Lead Circle ` + * Provides the software module release notes * Approves the module release notes * Adds and removes Software modules to the Platform * Releases the module diff --git a/process/process_areas/release_management/release_roles.rst b/process/process_areas/release_management/release_roles.rst index 437196db68..f45ba2c002 100644 --- a/process/process_areas/release_management/release_roles.rst +++ b/process/process_areas/release_management/release_roles.rst @@ -19,7 +19,7 @@ For Release Management no additional roles need to be defined. Contributing Roles: - * :need:`Technical Lead ` + * :need:`Committer ` * :need:`Project Lead ` A detailed overview of the responsibility for the steps of the Release Management process diff --git a/process/process_areas/release_management/release_workflow.rst b/process/process_areas/release_management/release_workflow.rst index c4fd7616a7..60f9afbbfd 100644 --- a/process/process_areas/release_management/release_workflow.rst +++ b/process/process_areas/release_management/release_workflow.rst @@ -20,33 +20,33 @@ Workflow Release Management .. workflow:: Create/Maintain Module Release Note :id: wf__rel_mod_rel_note :status: valid - :responsible: rl__technical_lead + :responsible: rl__committer :approved_by: rl__project_lead :input: wp__module_safety_package, wp__module_sw_release_plan, wp__verification_module_ver_report :output: wp__module_sw_release_note :contains: gd_temp__rel_mod_rel_note, gd_guidl__rel_management :has: doc_concept__rel_process, doc_getstrt__release_process - The module release note is created for each release by the module technical lead. It may be updated + The module release note is created for each release by the module project lead. It may be updated later in case of bugs found after the release is published. .. workflow:: Create/Maintain Platform Release Note :id: wf__rel_platform_rel_note :status: valid - :responsible: rl__technical_lead + :responsible: rl__committer :approved_by: rl__project_lead :input: wp__platform_safety_package, wp__platform_sw_release_plan, wp__verification_platform_ver_report :output: wp__platform_sw_release_note :contains: gd_temp__rel_plat_rel_note, gd_guidl__rel_management :has: doc_concept__rel_process, doc_getstrt__release_process - The platform release note is created for each release by the technical lead circle. It may be updated + The platform release note is created for each release by the project lead circle. It may be updated later in case of bugs found after the release is published. .. workflow:: Plan Module Release :id: wf__rel_mod_rel_plan :status: valid - :responsible: rl__technical_lead + :responsible: rl__committer :approved_by: rl__project_lead :input: wp__issue_track_system, wp__platform_mgmt :output: wp__module_sw_release_plan @@ -58,7 +58,7 @@ Workflow Release Management .. workflow:: Plan Platform Release :id: wf__rel_plat_rel_plan :status: valid - :responsible: rl__technical_lead + :responsible: rl__committer :approved_by: rl__project_lead :input: wp__issue_track_system, wp__platform_mgmt :output: wp__platform_sw_release_plan diff --git a/process/process_areas/requirements_engineering/requirements_concept.rst b/process/process_areas/requirements_engineering/requirements_concept.rst index ab41b10a01..318e0382ec 100644 --- a/process/process_areas/requirements_engineering/requirements_concept.rst +++ b/process/process_areas/requirements_engineering/requirements_concept.rst @@ -34,7 +34,7 @@ Inputs Stakeholders for the requirements ================================= -#. :need:`Tech Lead Circle ` +#. :need:`Project Lead Circle ` * Define specification and content for the platform * Creation of a project timeline diff --git a/process/process_areas/requirements_engineering/requirements_roles.rst b/process/process_areas/requirements_engineering/requirements_roles.rst index 70be862ccc..89771c32f3 100644 --- a/process/process_areas/requirements_engineering/requirements_roles.rst +++ b/process/process_areas/requirements_engineering/requirements_roles.rst @@ -21,6 +21,7 @@ Contributing Roles: * :need:`Contributor ` * :need:`Committer ` + * :need:`Project Lead ` * :need:`Safety Manager ` * :need:`Security Manager ` diff --git a/process/process_areas/requirements_engineering/requirements_workflow.rst b/process/process_areas/requirements_engineering/requirements_workflow.rst index 0130cde34a..f3c03acacc 100644 --- a/process/process_areas/requirements_engineering/requirements_workflow.rst +++ b/process/process_areas/requirements_engineering/requirements_workflow.rst @@ -21,7 +21,7 @@ Workflow Requirements Engineering :status: valid :tags: requirements_engineering :responsible: rl__contributor - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager :input: wp__policies, wp__issue_track_system :output: wp__requirements_stkh, wp__requirements_sw_platform_aou @@ -36,21 +36,21 @@ Workflow Requirements Engineering :status: valid :tags: requirements_engineering :responsible: rl__contributor - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__security_manager :input: wp__requirements_stkh, wp__issue_track_system :output: wp__requirements_feat :contains: gd_temp__req_feat_req, gd_temp__req_formulation :has: doc_concept__req_process, doc_getstrt__req_process - Depending on the stakeholder requirements feature requirements can be derived. This can be done by any contributor and will be approved by a technical lead. If needed safety and security managers can provide support. + Depending on the stakeholder requirements feature requirements can be derived. This can be done by any contributor and will be approved by a project lead. If needed safety and security managers can provide support. .. workflow:: Create/Maintain Feature AoUs :id: wf__req_feat_aou :status: valid :tags: requirements_engineering :responsible: rl__contributor - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__security_manager :input: wp__requirements_feat, wp__feature_arch, wp__issue_track_system :output: wp__requirements_feat_aou, wp__platform_safety_manual diff --git a/process/process_areas/safety_management/index.rst b/process/process_areas/safety_management/index.rst index c4d22af2d7..a74c432007 100644 --- a/process/process_areas/safety_management/index.rst +++ b/process/process_areas/safety_management/index.rst @@ -38,7 +38,7 @@ Inputs Stakeholders ^^^^^^^^^^^^ -#. :need:`Technical Lead ` +#. :need:`Project Lead ` * planning of development for module and for platform projects * status reporting of safety activities @@ -92,9 +92,9 @@ Getting started :status: valid -In case you are appointed as a :need:`Safety Manager ` by the :need:`rl__project_lead` in the S-CORE project: +In case you are appointed as a :need:`Safety Manager ` by the :need:`rl__project_lead` in the project: -* Contact the :need:`Technical Lead ` for your SEooC to establish planning and reporting (the TL should already have established a Github project for planning) +* Contact the :need:`Project Lead ` for your SEooC to establish planning and reporting (the TL should already have established a Github project for planning) * Create your safety plan according to :need:`wf__cr_mt_safety_plan` * Make familiar with your role description and the other workflows of safety management (see below) * Make familiar with the development and supporting process descriptions in :ref:`process_description` plus the relevant sections of the `Platform Management Plan ` diff --git a/process/process_areas/safety_management/workflows.rst b/process/process_areas/safety_management/workflows.rst index 5ef9015b02..df7447c0ad 100644 --- a/process/process_areas/safety_management/workflows.rst +++ b/process/process_areas/safety_management/workflows.rst @@ -19,7 +19,7 @@ Workflows :id: wf__cr_mt_safety_plan :status: valid :responsible: rl__safety_manager - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :input: wp__platform_mgmt, wp__issue_track_system, wp__sw_component_class, wp__tailoring :output: wp__module_safety_plan, wp__platform_safety_plan :contains: gd_guidl__saf_plan_definitions, gd_temp__feature_safety_wp, gd_temp__module_safety_plan @@ -104,7 +104,7 @@ Workflows :id: wf__mr_vy_safety :status: valid :responsible: rl__safety_manager - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :input: wp__module_safety_plan, wp__platform_safety_plan, wp__module_safety_package, wp__platform_safety_package, wp__audit_report, wp__fdr_reports :output: wp__issue_track_system, wp__module_sw_release_note, wp__platform_sw_release_note :contains: gd_guidl__saf_plan_definitions diff --git a/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst b/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst index 4d5f7e777f..36c2bedab6 100644 --- a/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst +++ b/process/process_areas/security_management/guidance/security_management_checklist_security_plan.rst @@ -75,7 +75,7 @@ The purpose of this security plan review checklist is to report status of the re - * - 9 - - Is a security manager and a technical/module lead appointed for the project? + - Is a security manager and a project lead appointed for the project? - [YES | NO ] - diff --git a/process/process_areas/security_management/guidance/security_management_guideline.rst b/process/process_areas/security_management/guidance/security_management_guideline.rst index 86db7bceae..8328c2f11e 100644 --- a/process/process_areas/security_management/guidance/security_management_guideline.rst +++ b/process/process_areas/security_management/guidance/security_management_guideline.rst @@ -84,7 +84,7 @@ Security Management Guideline **Planning security activities:** - In the security plan the nomination of the security manager and the technical/module lead is documented. + In the security plan the nomination of the security manager and the project lead is documented. The planning of security activities is done using issues in the :need:`wp__issue_track_system` as specified in the :need:`wp__platform_mgmt`. diff --git a/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst b/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst index 1b0b2d51f2..e77c8acafd 100644 --- a/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst +++ b/process/process_areas/security_management/guidance/security_management_module_security_plan_template.rst @@ -38,7 +38,7 @@ Module Security Plan Template +---------------------------+--------------------------------------------------------------+ | Security Manager | | +---------------------------+--------------------------------------------------------------+ - | Project Manager | | + | Project Manager | | +---------------------------+--------------------------------------------------------------+ | **4. Tailoring** @@ -48,7 +48,7 @@ Module Security Plan Template | - : - | | **5. Security Module Work Products** - | One set of workproducts for the module and one set for each component of the module: + | One set of work products for the module and one set for each component of the module: .. list-table:: Module Work Products :header-rows: 1 diff --git a/process/process_areas/security_management/guidance/security_management_security_manual_template.rst b/process/process_areas/security_management/guidance/security_management_security_manual_template.rst index 2d447a5acd..2d40afc0ae 100644 --- a/process/process_areas/security_management/guidance/security_management_security_manual_template.rst +++ b/process/process_areas/security_management/guidance/security_management_security_manual_template.rst @@ -61,7 +61,7 @@ Assumptions on the User | As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform EooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform EooC security package. | Additionally the components of the platform may have additional specific assumptions how they are used. These are part of every module documentation: . Assumptions from components to their users can be fulfilled in two ways: | 1. There are assumption which need to be fulfilled by all SW components, e.g. "every user of an IPC mechanism needs to make sure that he provides correct data (e.g. including appropriate security (access) control)" - in this case the AoU is marked as "platform". -| 2. There are assumption which can be fulfilled by a security control realized by some other Project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module EooC stand-alone - in this case the AoU is marked as "module". An example would be the "JSON read" which requires "The user shall provide a string as input which is not corrupted due to HW or QM SW errors." - which is covered when using together with safe S-CORE platform persistency feature. +| 2. There are assumption which can be fulfilled by a security control realized by some other Project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module EooC stand-alone - in this case the AoU is marked as "module". An example would be the "JSON read" which requires "The user shall provide a string as input which is not corrupted due to HW or QM SW errors." - which is covered when using together with safe platform persistency feature. List of AoUs on the user of the platform features or the module of this security manual: diff --git a/process/process_areas/security_management/security_management_concept.rst b/process/process_areas/security_management/security_management_concept.rst index b677839eb7..857a970233 100644 --- a/process/process_areas/security_management/security_management_concept.rst +++ b/process/process_areas/security_management/security_management_concept.rst @@ -41,12 +41,9 @@ Inputs Stakeholders for the Security Management **************************************** -#. :need:`Technical Lead ` +#. :need:`Project Lead ` * approving security audit - -#. :need:`Technical Lead `, :need:`Module Lead ` - * planning of development for platform/nodule projects * status reporting of security activities * approving security plan, security package diff --git a/process/process_areas/security_management/security_management_getstrt.rst b/process/process_areas/security_management/security_management_getstrt.rst index f525d2b632..bcc7ffd857 100644 --- a/process/process_areas/security_management/security_management_getstrt.rst +++ b/process/process_areas/security_management/security_management_getstrt.rst @@ -23,7 +23,7 @@ Getting Started In case you are appointed as a :need:`Security Manager ` by the :need:`rl__project_lead` in the development project: -* Contact the :need:`Technical Lead ` (TL) for your Component OoC (Out-of-Context) to establish planning and reporting +* Contact the :need:`Project Lead ` (TL) for your Component OoC (Out-of-Context) to establish planning and reporting * Create your security plan according to :need:`wf__cr_mt_security_plan` * Make familiar with your role description and the other workflows of security management (see :doc:`security_management_roles` or :doc:`security_management_workflow`) * Make familiar with the concept :need:`doc_concept__security_management_process` and the :need:`wp__platform_security_plan` diff --git a/process/process_areas/security_management/security_management_workflow.rst b/process/process_areas/security_management/security_management_workflow.rst index c87cffec35..58f36272c5 100644 --- a/process/process_areas/security_management/security_management_workflow.rst +++ b/process/process_areas/security_management/security_management_workflow.rst @@ -20,7 +20,7 @@ Workflow Security Management :id: wf__cr_mt_security_plan :status: valid :responsible: rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager :input: wp__platform_mgmt, wp__issue_track_system, wp__tailoring :output: wp__module_security_plan, wp__platform_security_plan @@ -35,7 +35,7 @@ Workflow Security Management :id: wf__cr_mt_security_package :status: valid :responsible: rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager :input: wp__module_security_plan, wp__platform_security_plan, wp__issue_track_system :output: wp__module_security_package, wp__platform_security_package @@ -52,7 +52,7 @@ Workflow Security Management :id: wf__p_fs_audit_security :status: valid :responsible: rl__external_auditor - :approved_by: rl__security_manager, rl__project_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager :input: wp__module_security_plan, wp__platform_security_plan, wp__module_security_package, wp__platform_security_package :output: wp__audit_report_security @@ -87,7 +87,7 @@ Workflow Security Management :id: wf__cr_mt_security_manual :status: valid :responsible: rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager :input: wp__requirements_feat_aou, wp__requirements_feat, wp__feature_arch, wp__feature_fmea, wp__feature_dfa, wp__requirements_comp_aou, wp__requirements_comp, wp__component_arch, wp__sw_component_fmea, wp__sw_component_dfa :output: wp__platform_security_manual, wp__module_security_manual @@ -102,7 +102,7 @@ Workflow Security Management :id: wf__cr_mt_security_sbom :status: valid :responsible: rl__committer - :approved_by: rl__security_manager, rl__technical_lead, rl__module_lead + :approved_by: rl__security_manager, rl__project_lead :supported_by: rl__infrastructure_tooling_community, rl__process_community, rl__security_team, rl__contributor :input: wp__issue_track_system, wp__module_security_plan, wp__platform_security_plan, wp__module_security_package, wp__platform_security_package :output: wp__sw_platform_sbom, wp__sw_module_sbom @@ -116,7 +116,7 @@ Workflow Security Management :id: wf__mr_vy_security :status: valid :responsible: rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__security_team :input: wp__issue_track_system, wp__module_security_plan, wp__platform_security_plan, wp__module_security_package, wp__platform_security_package, wp__audit_report, wp__fdr_reports, wp__sw_platform_sbom, wp__sw_module_sbom :output: wp__issue_track_system, wp__module_sw_release_note, wp__platform_sw_release_note @@ -134,7 +134,7 @@ Workflow Security Management :id: wf__consult_exe_sec_training :status: valid :responsible: rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__quality_manager :input: wp__module_security_plan, wp__platform_security_plan, wp__policies, wp__process_description :output: wp__training_path diff --git a/process/process_areas/tool_management/tool_management_roles.rst b/process/process_areas/tool_management/tool_management_roles.rst index a93965aaf3..04f90d435d 100644 --- a/process/process_areas/tool_management/tool_management_roles.rst +++ b/process/process_areas/tool_management/tool_management_roles.rst @@ -20,8 +20,7 @@ For tool management no additional roles need to be defined. Contributing Roles: * :need:`Infrastructure, Tooling Community ` - * :need:`Technical Lead ` - * :need:`Module Project Lead ` + * :need:`Project Lead ` * :need:`Safety Manager ` * :need:`Security Manager ` diff --git a/process/process_areas/tool_management/tool_management_workflow.rst b/process/process_areas/tool_management/tool_management_workflow.rst index 533080df5c..adc50b03cd 100644 --- a/process/process_areas/tool_management/tool_management_workflow.rst +++ b/process/process_areas/tool_management/tool_management_workflow.rst @@ -76,7 +76,7 @@ Workflow Tool Management :id: wf__tool_approve_tool_verification_report :status: valid :responsible: rl__safety_manager, rl__security_manager - :approved_by: rl__technical_lead, rl__module_lead + :approved_by: rl__project_lead :supported_by: rl__infrastructure_tooling_community :input: wp__tool_verification_report :output: wp__tool_verification_report diff --git a/process/process_areas/verification/guidance/verification_guideline.rst b/process/process_areas/verification/guidance/verification_guideline.rst index 59812b3332..b1f1059ae1 100644 --- a/process/process_areas/verification/guidance/verification_guideline.rst +++ b/process/process_areas/verification/guidance/verification_guideline.rst @@ -105,7 +105,7 @@ Reporting of failing test cases Any failing test case requires an ISSUE. The passing rate of safety-critical test cases need to be 100% in order to release the affected component. -In case of a lower pass rate than 100% for QM level tests, the :need:`rl__technical_lead` and +In case of a lower pass rate than 100% for QM level tests, the :need:`rl__project_lead` and :need:`rl__project_lead` can decide, if the platform is in a releasable state. The accepted minimal path rate is defined in the :need:`wp__verification_plan`. Due to the high degree of automation, a it is recommended that a path rate lower 95% is not acceptable. diff --git a/process/process_areas/verification/verification_concept.rst b/process/process_areas/verification/verification_concept.rst index c5256258b6..c8e7a75e58 100644 --- a/process/process_areas/verification/verification_concept.rst +++ b/process/process_areas/verification/verification_concept.rst @@ -39,15 +39,18 @@ Inputs Stakeholder =========== -#. :need:`Technical Lead ` +#. :need:`Project Lead ` * Set the scope of platform and testing * Status reporting of verification activities * Defining release content * Judge the releasable software state in case of failing test cases. + * Set the scope of platform and testing + * Status reporting of verification activities + * Defining release content - This may need involvement of :need:`rl__project_lead`, - :need:`rl__safety_manager`, and :need:`rl__security_manager` + This may need involvement of + :need:`rl__safety_manager` and :need:`rl__security_manager` #. :need:`SW developer/Architects ` @@ -64,12 +67,6 @@ Stakeholder * Review and approve verification artifacts * Get support by the :need:`rl__safety_manager` for safety-critical artifacts -#. :need:`Technical Lead ` - - * Set the scope of platform and testing - * Status reporting of verification activities - * Defining release content - #. :need:`Infrastructure/Tooling Developer ` * Enables execution of test cases in CI @@ -95,7 +92,7 @@ Stakeholder .. _verification_concept_types_methods: Verification Methods -===================== +==================== A verification is based on different methods. An overview of the different methods that are applicable are: diff --git a/process/process_areas/verification/verification_roles.rst b/process/process_areas/verification/verification_roles.rst index 36a4949769..4631cb5833 100644 --- a/process/process_areas/verification/verification_roles.rst +++ b/process/process_areas/verification/verification_roles.rst @@ -33,3 +33,6 @@ With focus on testability, requirements getting reviewed by: The tool verification and qualification is handled by: * :need:`rl__infrastructure_tooling_community`. + +Approval is handled by: + * :need:`Project Lead ` diff --git a/process/process_areas/verification/workflows.rst b/process/process_areas/verification/workflows.rst index 7c198c736e..9c00ae9d56 100644 --- a/process/process_areas/verification/workflows.rst +++ b/process/process_areas/verification/workflows.rst @@ -114,7 +114,7 @@ Workflow Verification :status: valid :tags: verification :responsible: rl__committer, rl__testing_community - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__infrastructure_tooling_community :input: wp__requirements_stkh, wp__platform_mgmt, wp__tool_verification_report :output: wp__verification_plan @@ -131,7 +131,7 @@ Workflow Verification :status: valid :tags: verification :responsible: rl__committer, rl__testing_community - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__infrastructure_tooling_community :input: wp__verification_plan, wp__requirements_stkh, wp__platform_mgmt, wp__feature_arch, wp__requirements_feat, wp__requirements_feat_aou, @@ -153,7 +153,7 @@ Workflow Verification :status: valid :tags: verification :responsible: rl__committer, rl__testing_community - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__infrastructure_tooling_community :input: wp__verification_plan, wp__requirements_comp, wp__requirements_comp_aou, wp__component_arch, wp__module_sw_release_note, wp__platform_mgmt, @@ -177,7 +177,7 @@ Workflow Verification :status: valid :tags: verification :responsible: rl__committer, rl__testing_community - :approved_by: rl__technical_lead + :approved_by: rl__project_lead :supported_by: rl__safety_manager, rl__infrastructure_tooling_community :input: wp__verification_plan, wp__requirements_stkh, wp__requirements_feat, wp__requirements_feat_aou, wp__feature_arch, wp__platform_sw_release_note, wp__platform_mgmt, diff --git a/process/roles/index.rst b/process/roles/index.rst index c8ff21012f..e08ad325e9 100644 --- a/process/roles/index.rst +++ b/process/roles/index.rst @@ -23,7 +23,8 @@ Project Management Roles :status: valid :tags: process_management - The Project Leads decide about strategy, addition of modules and election of all other roles. + The Project Leads decide about strategy, approve feature requests and perform the + project management of the . Required skills @@ -40,13 +41,15 @@ Project Management Roles * Decisions about strategical topics * Filling the Project Lead role according to the `Eclipse Foundation Project Handbook `_ - * Election of all roles in the project, including the :need:`Safety Manager ` on SW platform and module level - * Approval of release planning and releases + * Review and approval of contributions, e.g. Feature Requests, which add or modify features + * Project management of the development - i.e. filling the project management role as defined by ISO26262 + * High-level project control and coordination between multiple software modules + * Escalation instance + * Planning and Approval the releases of the Authority * Ultimate decisions on escalated topics - * Election and replacement of all role's personnel * Decide on addition/removal of modules repositories or split-off of projects Project Process roles @@ -59,7 +62,7 @@ Project Process roles :contains: rl__committer The process community members are responsible for the definition of the process architecture of the project integrated management system and how they processes interact. - The approval and release of the process is done by the safety, quality and security managers and the technical leads (for the parts which affect them). + The approval and release of the process is done by the safety, quality and security managers and the project leads (for the parts which affect them). Project Development roles ------------------------- @@ -120,7 +123,7 @@ Project Feature teams :id: rl__platform_team :status: valid :tags: cross_functional - :contains: rl__technical_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer, rl__infrastructure_tooling_community, rl__process_community + :contains: rl__project_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer, rl__infrastructure_tooling_community, rl__process_community The platform team is responsible for all artifacts within the platform SEooC. Additionally it is also responsible for the overall process including its support by tooling. @@ -128,7 +131,7 @@ Project Feature teams :id: rl__module_team :status: valid :tags: cross_functional - :contains: rl__module_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer + :contains: rl__project_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer The module team is responsible for all artifacts within the module SEooCs. Each module has only one responsible team but a team may also be responsible for several (small) modules.