Downloaded from https://www.everyspec.com ADS-79D-HDBK systems with less impact. The degree of scrutiny applied to the verification effort should be in step with the effects that could be generated by an improperly operating system. In the civil arena, a Functional Hazard Assessment (FHA) supplies the basis for determining the criticality of any given component within the system. A similar approach which provides a documented basis for the level of rigor needed when certifying HUMS, and the Ground Station specifically, is recommended to ensure that the cost of certifying a particular system is not out of line with the system‘s potential impact should a failure occur.
For more information regarding this section see RTCA D0-178B, section 2.2. K.6.1 Ground Station Verification. The Verification Process is designed to ensure that the developed system satisfies its requirements. In other words, it answers the question ―Does the system do what we said it should do?‖ In normal practice, the customer and developers collaborate on the requirements defined for the system. The developer then begins implementing a system to satisfy those requirements, and the customer is then responsible for accepting the developed system and validating that it performs as required in the actual target environment.
In contrast to verification, validation is the process of answering the question ―Does the system do what it is supposed to do?‖ This section of the document provides guidelines for verification of the system, which is usually performed by the developer of the system prior to delivery to the customer. The next major section covers the issues involved with validation. K.6.1.1 Ground Station Requirements-Based Verification. For systems that have been designed using requirement-based development, requirements-based verification is a perfect fit.
By verifying that the requirements for the system have been implemented, this phase of the process provides the necessary proof that the system performs as intended and as specified. Test Procedures, in the form of a Software Test Plan, which verify specific requirements, can be developed early-on in the development process, independently of the design and implementation of the software. Traceability between the design (requirements) and test (procedures) can be established and maintained to show full compliance of the system to its design.
Test Reports can be developed to document the results of the verification process, and highlight any product deficiencies down to the design/requirement level if necessary. K.6.1.2 Ground Station Software Verification Procedures and Cases. By focusing on requirements-based verification, software verification cases and procedures can be developed early-on and in parallel with software development (process shown in Figure K-16). Since the requirements for the system are established up-front, verification activities can proceed without the need for significant input from the actual software until the time that integration activities are performed.
In a typical development cycle, once the requirements for that cycle have been established, the development and verification teams can proceed independently and meet up at the integration and formal verification stages. 220