Merge pull request #14 from eclipse-score/masc2023_fix_warnings

fix links from process_description to score

Author: masc2023

process/index.rst

@@ -90,7 +90,7 @@ How To Contribute
 
 How to contribute to the S-CORE project (e.g. naming convention, folder structure, IDE setup) can be found here:
 
-:ref:`SCORE_contribute`
+:need:`SCORE_doc__contr_guideline`
 
 Standards
 ---------

process/process_areas/architecture_design/guidance/architecture_guideline.rst

@@ -106,8 +106,8 @@ Based on this template the feature architecture shall describe the concept of th
 
 For this step following guidances are available:
 
-* :ref:`Branch Naming Conventions <SCORE_branch_naming>`
-* :ref:`Git Guidelines <SCORE_git_guidelines>`
+* :need:`Branch Naming Conventions <SCORE_doc__naming_conventions>`
+* :need:`Git Guidelines <SCORE_doc__git_coding_guidelines>`
 * :need:`[[title]] Feature Architecture <gd_temp__arch__feature>`
 
 .. _model_feature_architecture:
@@ -178,8 +178,8 @@ Based on the *feature architecture* the concept for the *component architecture*
 
 For this step following guidances are available:
 
-* :ref:`Branch Naming Conventions <SCORE_branch_naming>`
-* :ref:`Git Guidelines <SCORE_git_guidelines>`
+* :need:`Branch Naming Conventions <SCORE_doc__naming_conventions>`
+* :need:`Git Guidelines <SCORE_doc__git_coding_guidelines>`
 * :need:`[[title]] <gd_temp__arch__comp>`
 
 .. _allocate_component_requirements:

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -105,7 +105,7 @@ Attributes of Architectural Elements
       * last part of the feature tree
       * keyword describing the content of the requirement.
 
-   The naming convention is defined here: :ref:`SCORE_naming_convention_needs`
+   The naming convention is defined here: :need:`SCORE_doc__naming_conventions`
 
 .. gd_req:: Architecture attribute: security
    :id: gd_req__arch_attr_security

process/process_areas/requirements_engineering/guidance/requirements_guideline.rst

@@ -69,7 +69,7 @@ For all requirements following mandatory attributes need to be defined:
 
 
 * Title and description: For the formulation of requirements following template shall be used :need:`[[title]]<gd_temp__req__formulation>`
-* ID: The naming convention for the ID is defined :ref:`here <SCORE_naming_convention_needs>`.
+* ID: The naming convention for the ID is defined :need:`here <SCORE_doc__naming_conventions>`.
 * Furthermore the requirements need to be versioned. Therefore a hash value of the requirement will to be calculated. The concept is described: :ref:`traceability concept for requirements`
 * For the remaining attributes only predefined values can be used. A more detailed description can be found here: :ref:`attributes of the requirements`
 
@@ -133,8 +133,8 @@ In this step the parent requirements shall be created. Stakeholder- and feature
 
 Therefore following guidelines are available:
 
-* :ref:`Branch Naming Conventions <SCORE_branch_naming>`
-* :ref:`Git Guidelines <SCORE_git_guidelines>`
+* :need:`Branch Naming Conventions <SCORE_doc__naming_conventions>`
+* :need:`Git Guidelines <SCORE_doc__git_coding_guidelines>`
 * :ref:`Requirement Templates <requirement templates>`
 
 .. _review_parent_requirement:
@@ -159,8 +159,8 @@ In an upcoming step the child requirements shall be derived from the parent requ
 
 Following guidelines are available:
 
-* :ref:`Branch Naming Conventions <SCORE_branch_naming>`
-* :ref:`Git Guidelines <SCORE_git_guidelines>`
+* :need:`Branch Naming Conventions <SCORE_doc__naming_conventions>`
+* :need:`Git Guidelines <SCORE_doc__git_coding_guidelines>`
 * :ref:`Requirement Templates <requirement templates>`
 
 .. _review_child_requirement:

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: :ref:`SCORE_naming_convention_needs`
+   The naming convention is defined here: :need:`SCORE_doc__naming_conventions`
 
 .. gd_req:: Requirement attribute: title
    :id: gd_req__requirements_attr_title

process/process_areas/requirements_engineering/requirements_getstrt.rst

@@ -71,7 +71,7 @@ Additionally tooling is provided to assist the :need:`[[title]] <rl__contributor
    :filter: "ide" in tags and type == "tool_req" and is_external == False
    :colwidths: 70,30
 
-A *HowTo* which describes the setup of the development environment for Sphinx Needs is available :ref:`here <SCORE_setting_up_dev_env>`.
+A *HowTo* which describes the setup of the development environment for Sphinx Needs is available :need:`here <SCORE_doc__develop_environment>`.
 
 For all RST files also a linter is configured, it will be automatically run in the CI upon check-in.
 Locally it can be run via