process: define safety_management plan: finding fixes

Ref: closes #333

docs/platform_management_plan/safety_management.rst

@@ -15,7 +15,7 @@
 .. document:: Platform Safety Plan
    :id: doc__platform_safety_plan
    :status: draft
-   :safety: ASIL-B
+   :safety: ASIL_B
    :tags: platform_management
 
 Safety management / Platform Safety Plan
@@ -37,10 +37,10 @@ And:
 * to plan the safety activities
 * to coordinate and track the progress of safety activities in accordance with the safety plan
 * to ensure a correct progression of the safety activities throughout the safety lifecycle
-* to plan to create a comprehensible safety case in order to provide the argument for the achievement of functional safety
-* to judge whether the SW achieves functional safety (i.e. the functional safety assessment, audit, confirmation reviews)
+* to plan to create a comprehensible safety case (collection of the safety related work products)
+* to judge whether the SW achieves functional safety process conformance (i.e. the functional safety audit, confirmation reviews)
 
-Objectives and scope
+Objectives and Scope
 ++++++++++++++++++++
 
 Functional Safety Management Goals
@@ -50,9 +50,9 @@ Functional Safety Management Goals
 
 in detail
 
-* to plan all Functional Safety related activities and work products
+* to plan all functional safety related activities and work products
 * to monitor and facilitate all activities
-* to measure and report Functional Safety Status based on well-defined metrics
+* to measure and report functional safety status based on well-defined metrics
 
 Functional Safety Management Scope
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -66,7 +66,7 @@ Regarding the platform specifics:
 
 * the highest ASIL in the project is ASIL B
 * all safety activities from a procedural point of view are developed according to ASIL B
-* all safety related SW in the project is developed according to Iso 26262 ASIL B
+* all safety related SW in the project is developed according to ISO 26262 ASIL B
 
 The SW platform functionality consists of features, which are based on a set of requirements and are developed in parallel.
 These features are developed into SW components contained in "modules", which are another set of SEooCs (initiated by a contribution request).
@@ -81,7 +81,7 @@ Tailoring of safety activities:
 * Module SEooC specific tailoring is documented in the module development Safety Plans - this may be based on SEooC specifics or because component qualification according to ISO 26262 part 8 clause 12 (or ISO PAS 8926) is selected.
 * In case of a change request on an existing feature (i.e. a contribution request), the subsequent safety planning will be done based on an impact analysis.
 
-The following ISO26262 defined safety work products are not relevant for the SCORE SW platform development:
+The following  ISO 26262 defined safety work products are not relevant for the SCORE SW platform development:
 
 Because these are in responsibility of the system integrator: :need:`std_wp_iso26262__management_11`,
 :need:`std_wp_iso26262__system_2`, :need:`std_wp_iso26262__system_3`, :need:`std_wp_iso26262__system_4`,
@@ -121,7 +121,7 @@ Because in the SCORE SW platform no ASIL decomposition is planned: :need:`std_wp
 Approach
 ++++++++
 
-Safety culture
+Safety Culture
 ^^^^^^^^^^^^^^
 
 The safety of the project S-CORE is inherent. It relies on the personal dedication and integrity of every person who is involved in the project.
@@ -183,9 +183,9 @@ One important aspect to this is, that we ensure the identity of the committer by
 Functional Safety Ressources
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-A dedicated Safety Manager is elected by :need:`rl__project_lead` for all the S-CORE SEooCs development.
+A dedicated safety manager is elected by :need:`rl__project_lead` for all the S-CORE SEooCs development.
 
-The Safety Manager, supported by the Project Manager (i.e. the :need:`rl__technical_lead`),  will ensure that
+The safety manager, supported by the project manager (i.e. the :need:`rl__technical_lead`),  will ensure that
 safety activities are actively planned, developed, analyzed, verified and tested and managed throughout the life cycle of the project.
 As all the implementation of safety functions takes place within module development, there is a safety manager appointed in the module's safety plan.
 
@@ -223,12 +223,12 @@ The status report includes at least the defined Quality Criteria defined below i
 Examples for valid escalation causes are:
 
 * Safety issues cannot be resolved on module level or with the available resources.
-* There are conflicting points-of-view between the Project Manager and the Safety Manager
+* There are conflicting points-of-view between the project manager and the safety manager
 
 Functional Safety Management Life Cycle
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The safety lifecycle of the S-CORE project is initiated at the project set-up and driven and maintained by the Safety Manager supported by the :need:`rl__process_community`.
+The safety lifecycle of the S-CORE project is initiated at the project set-up and driven and maintained by the safety manager supported by the :need:`rl__process_community`.
 Note that the Eclipse Foundation also defines `project phases <https://www.eclipse.org/projects/handbook/#starting-project-phases>`_.
 Eclipse definition is more about the process maturity for the whole project, if we are in Mature Phase, we latest will have the project lifecycle as defined in our process description.
 Nevertheless, Safety Development and even Safety Case release is independent from Mature and Incubation Phase as the completeness and appropriateness of the platform process and artefacts
@@ -256,7 +256,7 @@ Functional Safety Tool Management
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The platform management plan defines :doc:`tool_management`
 
-Functional Safety Work products
+Functional Safety Work Products
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The work products relevant for a module development is defined within each module safety management plan. See :need:`gd_temp__module_safety_plan`.
 Generic project wide work products are defined below.
@@ -268,7 +268,7 @@ The platform management plan defines :doc:`quality_management`
 Platform Safety Plan
 ++++++++++++++++++++
 
-Functional Safety Management SW Platform work products
+Functional Safety Management SW Platform Work Products
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 .. list-table:: SW Platform work products
@@ -456,14 +456,14 @@ Functional Safety Management SW Platform work products
       - :ref:`standard_iso26262` & :need:`doc__platform_safety_plan`
       - valid
 
-Functional Safety Management Feature specific work products
+Functional Safety Management Feature Specific Work Products
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-See feature tree documents (created by using :need:`GD_TEMP__feature_safety_wp`):
+See feature tree documents (created by using :need:`gd_temp__feature_safety_wp`):
 
 <link to document for every feature>
 
-Functional Safety work products status charts
+Functional Safety Work Products Status Charts
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 .. needpie:: Stakeholder Requirements