Software Release Criteria

The following formal criteria that must be met before a software release can be allowed or the Acceptance Test carried out. A late penalty applies if the criteria are not satisfied by the due date. Attach to this form empirical documentation for each item.
    1. [ ] 100% of functional System Tests for all features in the Staged Delivery Plan are passing. May be manual or automated.

    2. [ ]  At least 80% of System Tests for non-functional requirements in the SRS are passing. May be manual or automated.
    3. [ ] Automated coding style checker (CheckStyle) reports 0 errors and warnings.  Exceptions can be negotiated with instructor in advance.

    4. [ ] Javadoc tools reports 0 errors and warnings. 
      Exceptions can be negotiated with instructor in advance.

    5. [ ] There are ___ unchecked items in the Detailed Design Quality Assurance Checklist (attach explanation).

    6. [ ] There are ___ unchecked items in the High Level Design Quality Assurance Checklist (attach explanation).

    7. [ ] ____% of automated integration tests for all non-GUI classes in the system are passing.

    8. [ ] A test coverage tool shows that statement coverage from functional tests for both GUI and non-GUI classes is at least ____%.  Exceptions can be negotiated with instructor in advance.

    9. [ ] The absolute value of the slope of the code growth curve for the week prior to release must be less than ____%. (Based on data from daily build reports).
      10.  
    10. [ ] ____% of all critical severity reported defects have been fixed.
      11.  
    11. [ ] ____% of all major severity reported defects have been fixed.

    12. [ ] The number of defects reported must be at least ____% of predicted.
      13.  
    13. [ ] The slope of the defects reported curve for the five days prior to release must be less than ____%.
      14.  

Explanation of any items not checked goes here.