A006 - CDRL Metrics.docx
DOCX document 16 KB Posted
- Attached to
- Air Vehicle Planning System V
- Solicitation number
- FA4600-11-R-0028
About this file
CDRL A006
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Metrics The following table enumerates the set of metrics that shall be delivered as part of the CDRL A006. Contractor format may be used so long as all information required is provided.
| Measure |
| Purpose |
| Sample Questions Addressed |
| CDRL |
Requirements Tested
| The SCRs Tested measure counts the number of SCRs that have been successfully tested. The measure addresses the degree to which required functionality has been successfully demonstrated against the specified requirements as well as the amount of testing that has been performed. This measure provides an excellent measure of test progress. This measure is also known as “Breadth of Testing”. |
| - What SCRs are/were validated by what tests? |
- How many SCRs are/were directly testable?
- Are/Were the SCRs being tested as scheduled?
- Has the testing been successful?
- What requirements (functions) are behind schedule?
- How much of the functionality has been tested?
- Software Test Plan (STP)
Automated Unit Test Coverage
| The Automated Unit Test Coverage measures the percentage of executable code exercised by automated unit test tools. Unit testing is critical to findings defects early in the development cycle. A nonexistent or lightly used unit test regime is indicative of immature software development practices and will likely result in defects being undetected until product integration or deployment. |
| - Are unit tests being developed along with source code? |
| - Software Test Plan (STP) |
File details come from the government source that posted it. Updated .