Merge pull request #112 from eclipse-score/aschemmel-tech-tailor-out-hsi

Remove HSI work product

Author: aschemmel-tech

process/folder_templates/modules/module_name/docs/safety_mgt/module_safety_plan.rst

@@ -176,13 +176,6 @@ Component <name> Workproducts List
           - :need:`doc__component_name_requirements`
           - doc :ndf:`copy('status', need_id='doc__component_name_requirements')` & WP below
 
-        * - :need:`wp__hsi`
-          - <Link to process>
-          - <automated>
-          - <Link to issue>
-          - <Link to WP>
-          - <automated>
-
         * - :need:`wp__requirements__inspect`
           - :need:`gd_chklst__req__inspection`
           - :ndf:`copy('status', need_id='gd_chklst__req__inspection')`
@@ -280,10 +273,6 @@ If the OSS element is classified as a
           - <Link to issue>
           - Always needed (for Q and QR classification) and also improves process Id 5
 
-        * - :need:`wp__hsi`
-          - n/a
-          - OSS needing special HW is an extreme exception.
-
         * - :need:`wp__requirements__inspect`
           - n/a
           - Checklist used in Pull Request Review

process/general_concepts/score_review_concept.rst

@@ -42,9 +42,6 @@ In this project there are inspections on the following work products, which are
         * - :need:`wp__requirements__comp`
           - :need:`gd_chklst__req__inspection`
 
-        * - :need:`wp__hsi`
-          - :need:`gd_chklst__req__inspection`
-
         * - :need:`wp__requirements__feat_aou`
           - :need:`gd_chklst__req__inspection`
 
@@ -60,11 +57,11 @@ In this project there are inspections on the following work products, which are
         * - :need:`wp__sw_implementation`
           - :need:`gd_chklst__impl_inspection_checklist`
 
-Note that for testcases on unit, component and feature level (as defined in `REPLACE_doc__verification_plan`)
-also a review checklist is provided for guidance, but no formal inspection is required. The same is true for Safety Analysis and DFA.
-The independence of testing respectively of test case review is covered by the use of GitHub also for the review of test cases.
+Note that for test cases also a review checklist is provided for guidance, but no formal inspection is required.
+The same is true for Safety Analysis and DFA.
+The independence of testing respectively of test case review is covered by the use of version managment tool also for the review of test cases.
 Which means that at least the test case definition or the test case review is performed by
-another person as the author of the verified work product.
+another person as the author of the verified work product (see :need:`gd_req__verification__independence`).
 
 Inspection Conduct
 ^^^^^^^^^^^^^^^^^^

process/process_areas/safety_management/guidance/guideline_safety_management.rst

@@ -115,3 +115,5 @@ Safety Management Guideline
    :complies: std_req__iso26262__management_6481, std_req__iso26262__management_6482
 
    | The safety package shall be generated progressively and automatically compiling the work products.
+   | One of the checks to perform on the platform safety package is to check completeness of the
+   | process compliance to standards, which can be seen from standard linkage charts in :ref:`external_standards`.

process/process_areas/safety_management/workproducts.rst

@@ -135,3 +135,14 @@ Work products
    * Feature/Component
 
    It belongs to the Safety Plan.
+
+.. workproduct:: Tailoring Document Platform
+   :id: wp__tailoring_platform
+   :status: valid
+   :complies: std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522
+
+   This work product "definition" links to all the work products which can be tailored out
+   in the platform safety plan for your project if following the same approach as S-CORE,
+   to be able to demonstrate completeness as described in :need:`gd_guidl__saf_package`.
+   It is not really a work product definition,
+   but this is the best way to link to the tailored standard work products.

process/workproducts/index.rst

@@ -80,15 +80,6 @@ Platform development
    Build configuration capable to create the SEooC Library for the reference HW, platform level.
    Note: Embedded software in the sense of the Iso (i.e. deployed on the production HW) is not part of our delivery.
 
-.. workproduct:: Hardware-software interface document
-   :id: wp__hsi
-   :status: draft
-   :tags: safety
-   :complies: std_wp__iso26262__software_652, std_wp__isopas8926__4522
-
-   | The document shall specify the hardware and software interaction and be consistent with the safety concept.
-   | It shall include the platform's hardware parts that are controlled by software and hardware resources that support the execution of the software.
-
 
 Component development
 ^^^^^^^^^^^^^^^^^^^^^