13.07.2015 Views

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The second part <strong>of</strong> the V-cycle involves a series <strong>of</strong> evaluation activities to ensurethe suitability <strong>of</strong> the final product. These activities are known as ‘verification’ and‘validation’. Verification is the process <strong>of</strong> ensuring that the final product meets therequirements (that is, the product was built correctly). Validation is the process <strong>of</strong>ensuring that the requirements are sufficiently correct and complete (that is, theright product has been built).Figure 34: Simplistic representation <strong>of</strong> aircraft development processVerification and validation activities include testing the individual items <strong>of</strong>equipment (and s<strong>of</strong>tware), and then progressively integrating the equipment intosystems for more sophisticated testing activities, until the aircraft is evaluated as acomplete entity. Verification and validation also include methods such as peerreviews, modelling and other analyses. The V-cycle is an iterative rather than afixed process as the verification and validation activities can lead to design changesthroughout the cycle.As indicated in Figure 34, safety assessment activities are a key part <strong>of</strong> a goodsystem development process. <strong>In</strong>itial safety assessment activities help evaluate theinitial design and derive requirements, and a final system safety assessmentprovides assurance that the resulting system meets the safety requirements.It is generally accepted that, for all but the simplest systems, it is impossible toguarantee the correctness <strong>of</strong> all the system requirements and associatedassumptions. <strong>In</strong> order to reduce the potential effect <strong>of</strong> errors in the requirements orsubsequent design implementation, systems are designed with fault-tolerant featuresin their architecture, such as redundancy and dissimilarity.- 89 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!