.. _fsd305:


FSD305: System Integration Test Specification
#############################################

.. list-table:: Header
   :header-rows: 0

   * - Title
     - FSD305: System Integration Test Specification
   * - Version
     - V16
   * - Products
     - Safety Simplifier
   * - Requirements
     - 61508-2:7.5
   * - Purpose
     - Specify the E/E/PE system integration tests
   * - Input
     - :ref:`fsd114`
   * - Output
     - :ref:`fsd305`




Description
************

The system integration tests are covered in :ref:`FSD124` and :ref:`FSD150`.
See design requirements pass/references in :ref:`FSD120`.

Motivations
************

.. Unsure why these are N/A but they are according to RISE (Johan feedback 20250704)

.. motivation:: EN-61508-2 clause 7.5.2.1
   :id: MOTIVATION_305_001
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.
      
   .. previously:
   .. The system is integrated according to the integration test specifications
   .. as specified in :ref:`FSD124` and :ref:`FSD150`.

.. motivation:: EN-61508-2 clause 7.5.2.2
   :id: MOTIVATION_305_002
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.

   .. previously:
   .. The system is tested according to the integration test specifications
   .. as specified in :ref:`FSD124` and :ref:`FSD150`.


.. motivation:: EN-61508-2 clause 7.5.2.3
   :id: MOTIVATION_305_003
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.

   .. previously:
   .. See :ref:`FSD300`.

.. motivation:: EN-61508-2 clause 7.5.2.4
   :id: MOTIVATION_305_004
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.

   .. previously:
   .. Each test in E/E/PE system integration test specification has a test instruction and pass/fail criteria.
   .. The test results are documented in above mentioned test reports.

.. motivation:: EN-61508-2 clause 7.5.2.5
   :id: MOTIVATION_305_005
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.

   .. previously:
   .. If a modification of a safety function is required, the template Modification of safety function shall be
   .. applied when approving the modification. After approval to proceed with the modification, standard
   .. functional safety project procedure is followed (update of requirements specification, validation and
   .. verification activities, reviews etc.).

.. motivation:: EN-61508-2 clause 7.5.2.6
   :id: MOTIVATION_305_006
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.


   .. previously:
   .. \a), \c), \d), \e), \f) See :ref:`FSD107`.

   .. \b), \d) See :need:`MOTIVATION_305_002`.

   .. \g) If an integration test fails, the reason for failure shall be identified.
   .. If the reason for failure can be solved, modified, debugged etc.
   .. this action can be taken and then the integration test shall be performed again.
   .. Any change in the hardware or software requires the modification routines described
   .. in Management of functional safety. Depending on the extent of the change, one or more project
   .. phases must be re-worked. If a design change can't solve the integration failure, the integration
   .. procedure and the pass/fail criteria shall be evaluated.

.. motivation:: EN-61508-2 clause 7.5.2.7
   :id: MOTIVATION_305_007
   :tags: fsd305
   :status: N/A

   Not applicable at subsystem level.


   .. previously:
   .. See :ref:`FSD303`.