process: solve building errors

Ref: closes #310

Author: PandaeDo

process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst

@@ -52,7 +52,7 @@ Process Requirement Attributes
       * last part of the feature tree
       * keyword describing the content of the requirement.
 
-   The naming convention is defined here: :need:`SCORE_doc__naming_conventions`
+   The naming convention is defined here: <SCORE_doc__naming_conventions>
 
 .. gd_req:: Requirement attribute: title
    :id: gd_req__requirements_attr_title

process/process_areas/safety_analysis/guidance/safety_analysis_guideline.rst

@@ -90,7 +90,7 @@ The analysis considers single faults that can mitigate a safety requirement.
 |    :argument: "Calling app gets error information"
 |    :status: valid
 
-The example is also used in the building blocks <:ref:`score_building_block_example`>.
+The example is also used in the building blocks <score_building_block_example>.
 
 
 Step-by-Step-approach DFA:
@@ -126,4 +126,4 @@ So it could be shown that the analysis was done and no fault model is applicable
 |    :argument:
 |    :status: valid
 
-The example is also used in the concept description <:ref:`safety_analysis_feature_example`> and also in the building blocks <:ref:`building_block_example`>.
+The example is also used in the concept description <score_building_block_example> and also in the building blocks <:ref:`building_block_example`>.

process/process_areas/safety_analysis/guidance/safety_analysis_process_reqs.rst

@@ -50,7 +50,7 @@ Process Safety Analysis Attributes
       * keyword descirbing the level of analysis
       * keyword describing the content of the Safety Analysis
 
-   The naming convention is defined here: :ref:`naming_convention_needs`
+   The naming convention is defined here: :need:`here <SCORE_doc__naming_conventions>`
 
 .. gd_req:: Safety Analysis attribute: title
    :id: gd_req__saf_attr_title
@@ -244,5 +244,5 @@ Process Requirements Checks
 
    It shall be checked that Safety Analysis (Safety != QM) can only be linked against elements with the same ASIL.
 
-.. needextend:: "process_areas/safety_analysis" in docname
+.. needextend:: docname is not None and "process_areas/safety_analysis" in docname
    :+tags: safety_analysis

process/workflows/index.rst

@@ -21,7 +21,6 @@ Workflows
 
    process_management
    quality_management
-   safety_analysis
 
 
 S-CORE Workflow list

process/workflows/safety_analysis.rst

@@ -99,25 +99,6 @@ Product development
 Platform development
 ^^^^^^^^^^^^^^^^^^^^
 
-.. workproduct:: Feature Safety Analysis
-   :id: wp__feature_safety_analysis
-   :status: draft
-   :tags: safety
-   :complies: std_wp__iso26262__analysis_851, std_wp__iso26262__software_752
-
-   Bottom-Up Safety Analysis with e.g. FMEA method, verifies the feature architecture (as part of SW Safety Concept)
-   - Detection and prevention mitigations linked to Software Feature Requirements or Assumptions of Use
-
-.. workproduct:: Feature DFA
-   :id: wp__feature_dfa
-   :status: draft
-   :tags: safety
-   :complies: std_wp__iso26262__analysis_751, std_wp__iso26262__software_753
-
-   Dependent Failure Analysis on platform/feature level
-   - Detection and prevention mitigations linked to Software Feature Requirements or Assumptions of Use
-   Perform analysis on interactions between safety related and non-safety related modules or modules with different ASIL of one feature. Including potential influences from the rest of the SW platform.
-
 .. workproduct:: Platform Build Configuration
    :id: wp__platform_sw_build_config
    :status: draft
@@ -140,26 +121,6 @@ Platform development
 Component development
 ^^^^^^^^^^^^^^^^^^^^^
 
-.. workproduct:: Component Safety Analysis
-   :id: wp__sw_component_safety_analysis
-   :status: draft
-   :tags: safety
-   :complies: std_wp__iso26262__analysis_851, std_wp__iso26262__software_752, std_wp__isopas8926__4524
-
-   Bottom-Up Safety Analysis with e.g. FMEA method, verifies the component architecture (as part of SW Safety Concept)
-   - Detection and prevention mitigations linked to Software Component Requirements or Assumptions of Use
-
-.. workproduct:: Component DFA
-   :id: wp__sw_component_dfa
-   :status: draft
-   :tags: safety
-   :complies: std_wp__iso26262__analysis_751, std_wp__iso26262__software_753
-
-   Dependent Failure Analysis on component/module level
-   - Detection and prevention mitigations linked to Software Component Requirements or Assumptions of Use
-   Perform analysis of safety related and non-safety related sub-elements or sub-elements with different ASIL.
-   Perform analysis on interactions between safety related and non-safety related sub-components or sub-components with different ASIL of one component. Including potential influences from the other components in the component's module.
-
 .. workproduct:: Module Build Configuration
    :id: wp__module_sw_build_config
    :status: draft