Command control system testing.

CFR · 2024-01-01 · US · Title 14

(a) (2) Each acceptance and preflight test must follow a written test plan that specifies the procedures and test parameters for the test and the testing sequence. A test plan must include instructions on how to handle procedural deviations and how to react to test failures. (3) If hardware or software is redesigned or replaced with a different (4) After a command control system passes all acceptance tests, if a component is replaced with an identical component, the system must undergo testing to ensure that the new component is installed properly and is operational. (b) (2) Acceptance testing must include functional testing, system interface validation testing, and integrated system-wide validation testing. (3) Each acceptance test must measure the performance parameters that demonstrate whether the requirements of § 417.303 are satisfied. (4) Any computing system, software, or firmware that performs a software safety critical function must undergo validation testing and satisfy § 417.123. If command control system hardware interfaces with software, the interface must undergo validation testing. (c) (2) (3) (i) (ii) (4) (i) Verify the performance of each element of the system from the flight safety system displays and controls to each command transmitter site; (ii) Measure all system performance parameters received and transmitted using measuring equipment that does not physically interface with any elements of the operational command control system; (iii) Verify the perform

official document · source cfr-2024 · id 14:§ 417.305