Release 1 Scoresheet

Team:              

Due Date :

Submission Date: 

Release 1 product is worth 20% of the course grade.  Half of this is the "Group" grade, the customer's evaluation of the finished product.  The other half is an individual grade.  The individual grade has two parts:  Job Assignment documentation and Developer documentation.  Each student will self-evaluation of their own work.

Job Assignment Documentation


QA Manager ___________
 Score _____
___  All integration defects are recorded in Trac
___  Every integration defect has a regression test that includes a cross reference to the defect number.
___  Code Inspection Documentation (Each developer has at least one module reviewed, and also participates in at least one review.)
___  Completed Release Checklist
___  Formal release criteria have been met - empirical evidence is attached.
___  System Test Results
___  Coverage Test Report
___  Software deployed according to Deployment Plan.
___  (Stage 2) Metrics Summary Report (QA Plan section 5).


Test Manager ___________
 Score ____
___  System Test Matrix (cross reference every requirement to a test case)
___  Live Demonstration of run of instructor selected System Tests (with GUI) on the deployed system. May be manual instead of automated.
___  Live Demonstration of automated run of all unit tests in isolation.
___  Live Demonstration of automated run of all integration tests with a console UI (or test driver).


Analyst ___________
 Score _____
___  Staged Delivery Plan
___  SRS, User Manual and/or UI Prototype (as appropriate)
___  Release Notes (including Known Issues)
___  Consistency Check: All the above are consistent and match the released software.


Design / Implementation Manager ___________
 Score _____
___  Live Demonstration of automated build procedure.
___  Live Demonstration of deployment to a clean machine.
___  Current class diagram and javadocs posted.
___  Daily Build reports posted.
___  Integration / Implementation plan is current, with estimated/actual LOC counts.


Project Manager/Change Manager ___________
 Score _____
___  Source Code Repository well organized.
___  Live Demonstration of creating a maintenance branch for this release in the repository.
___  All Revision Log entries (for this Stage) have meaningful comments.
___  Submitted Change Requests all processed and posted.
___  No uncontrolled changes.
___  Team web page (including visibility) is current and accurate.
___  Draft features list for next stage delivery plan.

Developer Documentation
Source code
(Each developer must "own" a distinct, identifiable part of the product source code).
Code Inspection Documentation
(Each developer has at least one module reviewed, and also participates in at least one review.)
Unit tests
(Test code and scaffolding that tests the source code above).
System Test Case(s) documentation
White box test documentation (Stage 2)


Penalties

Schedule (all, except QA mgr)
Number days late1 ____  * -1  = ______

Cost (Project Mgr)
(Actual hours -  Hours budgeted ) / Hours budgeted) * 10  =  ____

Quality (QA Mgr)
Acceptance Test defects found
___ Critical defects (product rejected)
___ Major defects  * -1
___ Minor defects * -.3
___ Trivial defects * -.05

___ Total

1 Late Days do not include weekends.
In special cases the instructor may decide it is appropriate to assign penalties individually.