diff --git a/.github/ISSUE_TEMPLATE/1-bugfix.yml b/.github/ISSUE_TEMPLATE/1-bugfix.yml new file mode 100644 index 0000000000..ee16ca0ea4 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/1-bugfix.yml @@ -0,0 +1,82 @@ +# ******************************************************************************* +# 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 +# ******************************************************************************* + +name: Problem Report +description: Issue to track a bug +title: "Bug: Your bugfix title" +labels: ["codeowner_review"] +body: + - type: markdown + attributes: + value: "## Bug Ticket creation" + - type: textarea + attributes: + label: Description + description: Short Description of the Bug + validations: + required: true + - type: dropdown + attributes: + label: Error Occurrence Rate + options: + - Single Event + - Sporadic + - Highly Intermittent + - Reproducible + - type: textarea + attributes: + label: How to reproduce + description: How to reproduce? + - type: textarea + attributes: + label: Supporting Information + description: | + During which operational state did the issue occur + Observations / Screenshots / Traces + validations: + required: false + - type: dropdown + attributes: + label: Classification + options: + - minor + - major + - critical + - blocker + default: 0 + validations: + required: true + - type: dropdown + attributes: + label: Affected Version + options: + - 0.5 + - 1.0 + default: 0 + validations: + required: true + - type: dropdown + attributes: + label: Expected Closure Version + options: + - 0.5 + - 1.0 + default: 0 + validations: + required: false + - type: checkboxes + attributes: + label: Category + options: + - label: Safety Related + - label: Security Related diff --git a/.github/ISSUE_TEMPLATE/2-improvement.yml b/.github/ISSUE_TEMPLATE/2-improvement.yml new file mode 100644 index 0000000000..fa14031a1d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/2-improvement.yml @@ -0,0 +1,52 @@ +# ******************************************************************************* +# 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 +# ******************************************************************************* + +name: "Improvement / Task" +description: Issue to track a improvement / task +title: "Improvement: Your Improvement title" +labels: ["codeowner_review"] +body: + - type: textarea + attributes: + label: What + description: | + - Goal of the Improvement / Task + - If Req/Architecture is affected, the template of + [Change Management](https://eclipse-score.github.io/process_description/main/process_areas/change_management/guidance/change_management_impact_analysis_template.html) needs to be used + validations: + required: true + - type: textarea + attributes: + label: How + description: Details on implementation approach + validations: + required: false + - type: textarea + attributes: + label: Estimates for realization + description: | + - Estimate the effort, resources, risk for the realization + - Impact to users of the feature + validations: + required: true + - type: checkboxes + attributes: + label: Category + options: + - label: Affects Detailed Design + - type: checkboxes + attributes: + label: Requirements / Architecture + options: + - label: Requirements / Architecture are not affected by this change? + required: true diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000000..d8944ceeaf --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,14 @@ +# ******************************************************************************* +# 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 +# ******************************************************************************* + +blank_issues_enabled: false diff --git a/process/process_areas/platform_management/platform_management_workflow.rst b/process/process_areas/platform_management/platform_management_workflow.rst index b947839c84..bf62655555 100644 --- a/process/process_areas/platform_management/platform_management_workflow.rst +++ b/process/process_areas/platform_management/platform_management_workflow.rst @@ -25,7 +25,7 @@ Workflow Platform Management :approved_by: rl__process_community :supported_by: rl__safety_manager, rl__security_manager, rl__quality_manager :input: wp__policies, wp__issue_track_system - :output: wp__platform_mgmt, wp__project_mgt, wp__document_mgt_plan, wp__config_mgt_plan + :output: wp__platform_mgmt, wp__project_mgt, wp__document_mgt_plan, wp__config_mgt_plan, wp__prm_plan :contains: gd_temp__platform__mgmt_plan, gd_guidl__platform__mgmt_plan, gd_guidl__documentation, gd_chklst__documentation__review, gd_temp__documentation :has: doc_concept__platform__process, doc_getstrt__platform__process diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst index b16297b64f..a11880e0f4 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_checklist.rst @@ -86,5 +86,5 @@ Problem Checklist - * - 13 - - If the Problem report is not closed and pending solution measures are open, escalated to the :need:`rl__safety_manager`? + - If the Problem report is not closed and pending solution measures are open, escalated to the :need:`rl__safety_manager` or :need:`rl__security_manager`? - 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 27b2f1ba71..ecf4155543 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_guideline.rst @@ -25,12 +25,13 @@ This document describes the general guidances for Problem Resolution based on th General Hints ============= -The detailed implementation of the Problem Resolution for **S-CORE** is described in the `[[title]]`. +The detailed implementation of the Problem Resolution for the project shall be described in the :ref:`Workflow Platform Management `. Templates --------- -To create problem reports, **S-CORE** provides the following template: :need:`[[title]]`. +To create problem reports, the project shall provide the following template: :need:`[[title]]`. +An example template for the issue trackings system GitHub can be found here: (to be updated later) Attributes ---------- @@ -52,31 +53,32 @@ A more detailed description can be found here: :ref:`prm_process_requirements` Activities for Problem Resolution ================================= -This section describes in detail which steps need to be performed for a Problem resolution. - -Refer to the `Problem Resolution Plan ` for examples -how to create problem reports. +This section describes in detail which steps need to be performed for a Problem Resolution. .. list-table:: Activities for Problem Resolution :header-rows: 1 - :widths: 10,60,30 + :widths: 10,60,30,30 * - Step - Description - Responsible + - Approver * - :ref:`1. ` - Create Problem Report - :need:`[[title]] ` + - :need:`[[title]] ` * - :ref:`2. ` - - Analyse Problem Report + - Analyze Problem Report - :need:`[[title]] ` + - :need:`[[title]] ` * - :ref:`3. ` - Initiate and Monitor Problem Resolution - :need:`[[title]] ` + - :need:`[[title]] ` * - :ref:`4. ` - Close Problem Resolution - :need:`[[title]] ` - + - :need:`[[title]] `, :need:`[[title]] ` .. _prm_create_problem_report: @@ -94,18 +96,18 @@ The description should reflect the problem root cause and impact in detail. Copy therefore the :need:`Problem Template ` into the created Problem Report (Issue Tracking System). -Set the status of the Problem to "open", when ready to review and analyse set to "in review". +Set the status of the Problem to "open", when ready to review and analyze set to "in review". .. _prm_analyze_problem_report: -Analyse Problem Report +Analyze Problem Report ---------------------- -The **S-CORE** :need:`[[title]] ` analyzes the problem together with the +The projects :need:`[[title]] ` analyzes the problem together with the :need:`[[title]] ` and takes a decision for accepting or rejecting it. If accepted, the status is set to "in implementation" and :need:`[[title]] ` -can start with the iniation of the Problem Resolution, otherwise the status is set to "rejected". +can start with the initiation of the Problem Resolution, otherwise the status is set to "rejected". The author has the freedom to cancel it at any time by setting the status to "rejected". @@ -119,7 +121,7 @@ Initiate and Monitor Problem Resolution Therefore further activities needs to be planned and linked to the Problem Report. During the resolution the responsible lead :need:`[[title]] ` or -:need:`[[title]] ` reports regularly the status to the affected **S-CORE** teams. +:need:`[[title]] ` reports regularly the status to the affected projects teams. The author has the freedom to cancel it at any time by setting the status to "rejected". diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst index 7fd8114ef5..46449bf0c1 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst @@ -26,7 +26,7 @@ Problem Attributes :id: gd_req__problem__attr_uid :status: valid :tags: done_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a unique ID. It shall be in an integer number. @@ -35,7 +35,7 @@ Problem Attributes :id: gd_req__problem__attr_status :status: valid :tags: manual, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a status: @@ -50,7 +50,7 @@ Problem Attributes :id: gd_req__problem__attr_title :status: valid :tags: manual, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 Reason for Problem Report @@ -59,21 +59,21 @@ Problem Attributes :id: gd_req__problem__attr_impact_description :status: valid :tags: manual, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Exact description of the Problem, including potential cause and impact of the problem. Record especially, if functional safety or cybersecurity may affected here. - Record potential affected parties, and if it may requried to notify them about the potential + Record potential affected parties, and if it may required to notify them about the potential problem. .. gd_req:: Problem attribute: analysis results :id: gd_req__problem__attr_anaylsis_results :status: valid :tags: manual, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP2 Record analysis results (e.g. reason for rejection, safety, security, quality impact) as comments. @@ -82,17 +82,17 @@ Problem Attributes :id: gd_req__problem__attr_stakeholder :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP5 - Assign responsible stakeholder for analysing the problem + Assign responsible stakeholder for analyzing the problem Assign responsible stakeholder to resolve the problem .. gd_req:: Problem attribute: classification :id: gd_req__problem__attr_classification :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Each Problem shall have a classification identifier: @@ -102,23 +102,11 @@ Problem Attributes * critical * blocker -.. gd_req:: Problem attribute: category - :id: gd_req__problem__attr_category - :status: valid - :tags: prio_3_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr - :complies: std_req__aspice_40__SUP-9-BP1 - - Each Problem shall have a category identifier: - - * User - * Bug - .. gd_req:: Problem attribute:: safety affected :id: gd_req__problem__attr_safety_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a safety relevance identifier: @@ -132,7 +120,7 @@ Problem Attributes :id: gd_req__problem__attr_security_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a security relevance identifier: @@ -146,7 +134,7 @@ Problem Attributes :id: gd_req__problem__attr_milestone :status: valid :tags: manual, problem_resolution, attribute, mandatory - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP6 Milestone until the Problem must be implemented (used for prioritization) @@ -159,7 +147,7 @@ Problem Resolution Checks :id: gd_req__problem__check_mandatory :status: valid :tags: prio_2_automation, problem_resolution, attribute, check - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 It shall be checked if all mandatory attributes for each Problem @@ -175,7 +163,7 @@ Problem Resolution Checks :id: gd_req__problem__check_closing :status: valid :tags: prio_1_automation, problem_resolution, attribute, check - :satisfies: wf__problem__create_pr, wf__problem__analyse_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr + :satisfies: wf__problem__create_pr, wf__problem__analyze_pr, wf__problem__initiate_monitor_pr, wf__problem__close_pr :complies: std_req__aspice_40__SUP-9-BP1 ISSUEs related to Problem Reports shall not automatically closed, if linked ISSUEs or PRs are closed or merged and diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_template.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_template.rst index 62505e8fd6..5c6fd5a717 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_template.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_template.rst @@ -19,22 +19,20 @@ Problem Report Template .. gd_temp:: Problem Template :id: gd_temp__problem__template - :status: valid + :status: draft :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP3, std_req__aspice_40__SUP-9-BP4, - -Parts of the Problem Template shall be created automatically by the defined Issue Tracking System, -this is currently planned here: https://github.com/eclipse-score/score/issues/869. +Will be reworked, after this PR with ISSUE_TEMPLATES is merged Problem status -------------- [“open”, “in review”, “in implementation”, “closed”, “rejected”] -If possible, use for problem status the properties of the selected Issue Tracking System -(for implementation see here `REPLACE_doc__platform_problem_resolution_plan`) +If possible, use for problem status the properties of the selected Issue Tracking System. +(Update here with example from GitHub, after this PR is merged) | (to be filled out during :need:`wf__problem__create_pr`) -| (to be updated during :need:`wf__problem__analyse_pr`) +| (to be updated during :need:`wf__problem__analyze_pr`) | (to be updated during :need:`wf__problem__initiate_monitor_pr`) Problem submitter @@ -42,7 +40,7 @@ Problem submitter [Who is the reporter of the problem?] If possible, use for problem submitter the properties of the selected Issue Tracking System -(for implementation see here `REPLACE_doc__platform_problem_resolution_plan`) +(for implementation see here: to be update with Example later) (to be filled out during :need:`wf__problem__create_pr`) @@ -56,7 +54,7 @@ Problem description | Is notification required due to determined impact on affected parties? | (to be filled out during :need:`wf__problem__create_pr`) -| (to be updated during :need:`wf__problem__analyse_pr`) +| (to be updated during :need:`wf__problem__analyze_pr`) Problem supporting information ------------------------------ @@ -73,7 +71,7 @@ Problem analysis results | Especially document rejection Reason | Determine the safety/security impact, if applicable -(to be filled out during :need:`wf__problem__analyse_pr`) +(to be filled out during :need:`wf__problem__analyze_pr`) Problem stakeholder ------------------- @@ -83,30 +81,23 @@ Problem stakeholder Add affected feature, if possible If possible, use for problem stakeholder the properties of the selected Issue Tracking System -(see implementation here `REPLACE_doc__platform_problem_resolution_plan`) +(Update here with example from GitHub, after this PR is merged) (to be filled out during :need:`wf__problem__create_pr`) Problem category ---------------- -[User, Bug] - -[Safety affected, Security affected, Quality affected] - -User: +[Safety affected, Security affected] * Problems relating to requirements, design, ore code found by user of the platform. - -Bug: - * Problems found by contributor based on component, feature or platform integration tests. * Problems or gaps found by Quality Management activities as defined in the Quality Management Plan. -Safety, Security, Quality: Additional qualifier to highlight, if safety, security or quality is affected +Safety, Security: Additional qualifier to highlight, if safety or security is affected If possible, use for problem category the properties of the selected Issue Tracking System -(for implementation see here `REPLACE_doc__platform_problem_resolution_plan`) +(Update here with example from GitHub, after this PR is merged) (to be filled out during :need:`wf__problem__create_pr`) @@ -117,27 +108,38 @@ Problem classification Classify the problem severity -| Use minor, if the impact is not significant of the project -| The problem does not restrict usage of features in a significant manner +| Use **minor**, if the impact is not significant of the project + +* The problem does not restrict usage of features in a significant manner + | Resolution may be scheduled to any planned future SW release -| Use major, if the impact does effect the quality of the project -| The problem can be solved with work-arounds for affected features +| Use **major**, if the impact does effect the quality of the project + +* The problem can be solved with workarounds for affected features + | Resolution shall be scheduled to next planned future SW release -| Use critical, if the impact does not prohibit to use the project, but quality cannot be guaranteed -| The problem affects a complete feature, that they are partly or complete not behave as expected +| Use **critical**, if the impact does not prohibit to use the project, but quality cannot be guaranteed + +* The problem affects a complete feature, that they are partly or complete not behave as expected + | Resolution shall be scheduled to next planned future SW release or to a new planned intermediate release, if urgent resolution is required -| Use blocker, if the impact prohibits using the project -| The problem affects more than one feature, that they are partly or complete not behave as expected -| Safety or Security risks identified +| Use **blocker**, if the impact prohibits using the project + +* The problem affects more than one feature, that they are partly or complete not behave as expected OR +* Safety or Security risks identified + | Resolution shall be provided upon availability +.. note:: + In case of doubt, a safety or security relevant problem shall always classified as **blocker**. + Determine if Urgent resolution is required? (yes, no, only valid for critical, blocker) | (to be filled out during :need:`wf__problem__create_pr`) -| (to be updated during :need:`wf__problem__analyse_pr`) +| (to be updated during :need:`wf__problem__analyze_pr`) Problem expected closure date ----------------------------- @@ -145,7 +147,7 @@ Problem expected closure date [Milestone when the problem should be resolved] If possible, use for problem closure date the properties of the selected Issue Tracking System -(for implementation see here `REPLACE_doc__platform_problem_resolution_plan`) +(Update here with example from GitHub, after this PR is merged) (to be filled out during :need:`wf__problem__create_pr`) @@ -154,7 +156,7 @@ Problem solutions [What are measures to solve the problem?] -Specifiy the measures to resolve the problem, based on a rationale +Specify the measures to resolve the problem, based on a rationale Verify the effectiveness of the implemented measure diff --git a/process/process_areas/problem_resolution/problem_resolution_concept.rst b/process/process_areas/problem_resolution/problem_resolution_concept.rst index 2caf6e53cf..d862ba5f48 100644 --- a/process/process_areas/problem_resolution/problem_resolution_concept.rst +++ b/process/process_areas/problem_resolution/problem_resolution_concept.rst @@ -26,10 +26,10 @@ including the requirements of the different stakeholders for the Problem Resolut Key concept *********** -A Problem Report is the **ONLY** way to report (compare `REPLACE_doc__contr_guideline`) -deviations of an expected result for existing features in the **S-CORE** project. -Deviations include problems found by user, bugs found during verification activites by tester, -quality issues found by quality checks, safety anomalies, vulnerabilites or any other malfunction. +A Problem Report is the **ONLY** way to report deviations of an expected result for +existing features in the project. Deviations include problems found by user, +bugs found during verification activities by tester, quality issues found by quality +checks, safety anomalies, vulnerabilities or any other malfunction. Inputs ****** @@ -44,11 +44,11 @@ Stakeholders for the Problem Report #. :need:`Contributor ` - * Contributes features and components to grow the **S-CORE** content + * Contributes features and components to grow the project content #. :need:`Committer ` - * Verifies that the contribution fulfills the **S-CORE** policies + * Verifies that the contribution fulfills the project policies * Approves the contribution Standard Requirements @@ -63,7 +63,7 @@ Also requirements of standards need to be taken into consideration: Problem Report Categories ************************* -User: Problems relating to requirements, design, or code found by user of the platform. +User: Problems relating to requirements, architecture, implementation, or code found by user of the platform. Bug: Problems found by contributor based on component, feature or platform integration tests including verification and quality assurance activities. diff --git a/process/process_areas/problem_resolution/problem_resolution_getstrt.rst b/process/process_areas/problem_resolution/problem_resolution_getstrt.rst index 917b2e22a0..8194d85851 100644 --- a/process/process_areas/problem_resolution/problem_resolution_getstrt.rst +++ b/process/process_areas/problem_resolution/problem_resolution_getstrt.rst @@ -20,9 +20,24 @@ Getting Started :status: valid :tags: problem_resolution -In case you want to report a Problem to **S-CORE** consider to: +This document describes the steps to create a problem report, and further to analyze, +resolve, and to control the problem until closure. Where a problem is defined as a +deviation of an expected result. -* Create your Problem Report according to :need:`wf__problem__create_pr` -* Make familiar with the development and supporting process descriptions in :ref:`process_description` -* Make familiar with the relevant sections of the `Platform Management Plan `, here especially with `Problem Resolution Plan ` -* In case of any questions, contact the :need:`Technical Lead ` for your problem to establish reporting and planning +Therefore guidelines :need:`gd_temp__problem__template`, +:need:`gd_guidl__problem__problem` and a :need:`doc_concept__problem__process` +are available. + +General Workflow +**************** + +The workflows are defined in the :ref:`problem_workflows` section. + +For every problem identified, the following workflows are executed: + +* Create your problem report according to :need:`wf__problem__create_pr` +* Analyze your problem report according to :need:`wf__problem__analyze_pr` +* Initiate problem resolution and monitor it until closure according to :need:`wf__problem__initiate_monitor_pr` +* Close the problem resolution according to :need:`wf__problem__close_pr` + +In addition create a problem resolution plan as part of the platform management plan according to :need:`wf__platform__cr_mt_platform_mgmt_plan`. diff --git a/process/process_areas/problem_resolution/problem_resolution_workflow.rst b/process/process_areas/problem_resolution/problem_resolution_workflow.rst index dcbcaf706c..d187a75f4d 100644 --- a/process/process_areas/problem_resolution/problem_resolution_workflow.rst +++ b/process/process_areas/problem_resolution/problem_resolution_workflow.rst @@ -12,6 +12,7 @@ # SPDX-License-Identifier: Apache-2.0 # ******************************************************************************* +.. _problem_workflows: Workflow Problem Resolution ########################### @@ -33,8 +34,8 @@ Workflow Problem Resolution To start the review and the analysis the Problem status is changed to "in review" -.. workflow:: Analyse Problem Report - :id: wf__problem__analyse_pr +.. workflow:: Analyze Problem Report + :id: wf__problem__analyze_pr :status: valid :responsible: rl__contributor :approved_by: rl__committer @@ -44,7 +45,7 @@ Workflow Problem Resolution :contains: gd_temp__problem__template, gd_chklst__problem__cr_review, gd_guidl__problem__problem :has: doc_concept__problem__process, doc_getstrt__problem__process - The Problem Report is analysed. + The Problem Report is analyzed. Until the template is not filled out properly, the Problem may be set back to “open” from the :need:`Committer `.