DO178B Software Verification Process

6.1 Software Verification Process Objectives
6.2 Software Verification Process Activities
6.3 Software Reviews and Analysis
6.3.1 Reviews and Analysis of the High-Level Requirements
6.3.2 Reviews and Analysis of the Low-Level Requirements
6.3.4 Reviews and Analysis of the Source Code
  a. Compliance with the low-level requirements
  b.Compliance with the software architecture
  c. Verifiability
  d. Conformance to standards
  Bu alan için "Static Code Analysis" aracı kullanılabilir.
  e. Traceability
  f. Accuracy and consistency
6.3.5 Reviews and Analysis of the Outputs of the Integration Process
6.3.6 Reviews and Analysis of the Test Cases,Procedures and Results 

Final Run For Score Nedir?

Açıklaması şöyle. Yani gerçek uçuş sisteminde koşarak, doğrulama sonuçları ve delilleri üretmek.

How to prepare for the final “run for score” in your DO-178C project…

As you approach the end of the Verification stage of your project, you’ll need to prepare for your final run for score, which will produce comprehensive verification results and compliance evidence for your final software baseline in the context of your final product.

This means that the test environment should be the same as the final flight system, including all hardware and with all software components integrated. The final run for score is typically performed after the Verification milestone (SOI#3), but is necessary to produce the compliance artifacts you’ll need for certification.

The most efficient strategy when preparing for the final run for score is to ensure that when you go ahead with it, you’ll collect all of the results you need to.

This includes results for all of your requirements-based tests and the evidence you need to show that you have achieved 100% data coupling and control coupling coverage and structural coverage of your final code (through either tests or manual analysis and justification) at the required coverage granularities for your DAL.
Your requirements-based test results should be collected from the final code as it will be written in your product. This means that, if you have instrumented your code to support coverage analysis, you will need to run your requirements-based tests on code that has not been instrumented and collect your coverage results separately.

For large projects, running a final “run for score” may take weeks or even months.