Release 2 Scoresheet
Team:
|
Due Date :
|
Submission Date:
|
Release 2 product is worth 15% of the course grade. Half of this
is Job Assignment documentation and the other half is individual work
product documentation. (For simplicity, a score of 10
points is the max for each component).
Job Assignment Documentation
QA Manager ___________
|
Score _____
|
___ 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 - both functional and non-functional
requirements
___ (Stage 2) Metrics Summary Report (QA Plan section 5).
Test Manager ___________
|
Score ____ |
___ Test Matrix (spec to test cases)
___ Unit Test Directory Listing shows every Stage 1.1 & 2
defect
reported in
Defect Tracking Tool has a unit test which reveals it.
___ Live Demonstration of automated run of all System Tests
(with
GUI) on the deployed system.
___ 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). (Stage 2)
Analyst ___________
|
Score _____
|
___ Staged Delivery Plan
___ User Manual
___ Release Notes
___ Consistency Check: All the above are consistent and match the
released software.
Design / Implementation Manager ___________
|
Score _____
|
___ Live Demonstration of build procedure (Stage 2: automated,
e.g., Ant) on a clean machine/account.
___ Current class diagram and javadocs posted.
___ Daily Build reports posted.
Change Manager ___________
|
Score _____
|
___ Source Code Repository well organized, with separate branch
for maintenance release.
___ All Revision Log entries (for this Stage) have meaningful
comments.
___ Submitted Change Requests all processed and posted.
___ Documentation/evidence of no uncontrolled changes.
| Project Manager ___________ |
Score _____
|
___ Team web page (including visibility) is current and accurate.
Penalties
Schedule (all)
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)
___ Moderate defects * -1
___ Minor defects * -.3
___ Total
1 Late Days do not
include weekends.
In special cases the instructor may decide it is appropriate to assign
penalties individually.
Individual Work Products (in binder)
|
Developer Name
|
|
______ |
______ |
______ |
______ |
______ |
______ |
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.) |
|
|
|
|
|
|
JUnit tests
(JUnit code that tests the source code above).
|
|
|
|
|
|
|
System Test Case(s) documentation
|
|
|
|
|
|
|
White box test (basis path) documentation (Stage 2)
|
|
|
|
|
|
|
Average(10)
|
|
|
|
|
|
|
| Penalties |
|
|
|
|
|
|
| Score(10) |
|
|
|
|
|
|