Release 2 Scoresheet

Release 2 product is worth 25% of the course grade.  15 pts of this is the "Group" grade, the customer's evaluation of the finished product.  The other 10 pts is an individual grade.  The individual grade has two parts:  Developer documentation and Job Assignment documentation. 

Submission Instructions

Collect the items below and bind them with a report cover or a small three-ring binder.  Put your team logo on the cover.  Presentation matters.  Order the items as follows:
  1. Title page - "Release 2 Report", date, student name, job assignment, team name.
  2. Checklist - create a checklist page by copy and pasting the developer documentation checklist below.
  3. Developer documentation items, in the order shown on the checklist.
  4. Job Assignment documentation items: self-evaluation followed by supporting evidence.
  5. You may include additional documentation that seems relevant to you.  Place it after the above items.



Developer Documentation Name: _____________________________


The purpose of this documentation is to provide evidence of the technical work products you created as an individual.
___
 Source code for the current release
(Each developer must "own" a distinct, identifiable part of the product source code).
___ Unit tests
(Test code and scaffolding that tests the source code above).
___ System Test Case(s) documentation and optionally, automated test scripts
___ Review or Inspection Documentation
(Documentation for any reviews you performed of someone else's work.)
___ Basis path test documentation for at least one significant method.
___ List of defects repaired. (Trac custom query: Owner is <student> Type is "defect")
___ List of action items completed. (Trac custom query: Owner is <student> Type is "task")
Show percent completed on time.



Job Assignment Documentation

Write a self-evaluation that describes how well you have performed your job assignment duties.  This is an important part of your grade so use your best written English and prepare an organized, coherent, and professional self-evaluation.

One approach would be to copy and paste the list of responsibilities for your job from the job assignments page, then write a response beneath each item that explains the extent to which you fulfilled that responsibility.  You may add any additional job duties you performed that aren't on the original list. 

A second (or additional) approach would be to organize your evaluation around the project plan document that you administrate (e.g., QA Plan, Change Control Plan, etc.).  Discuss how successful you have been at planning, controlling, and tracking the processes you are responsible for managing. Describe any modifications to the process plans that would improve your team's performance during release 2.

Follow the self-evaluation with printed documentation that provides evidence to support your self-evaluation. You must provide tangible evidence of your accomplishments.  You should submit work for which you are the primary author or coordinator not work that resulted from collaborative effort.  For items that are too voluminous to make printouts, include a reference to the wiki page.

The list below gives examples of the kinds of evidence that might be presented for each job assignment. This list is representative but not exhaustive.  You may have more, fewer, or different items than shown. 


Based on the developer and job assignment documentation you provided, give yourself a final letter grade (on an A-F scale, plus/minus allowed) for your contribution to the PROJECT (not the course).  Evaluate yourself, not your team. Assign a SINGLE grade, not a range. You need to judge yourself clearly, objectively, and accurately. Your assessment must be based on accomplishments, not effort. Explain your evaluation of yourself (perhaps referring to evidence above).


QA Manager ___________

___  Formal release criteria have been met - printout of empirical evidence.
___  Printout completed Release Checklist.
___  Printout of all defects from Trac (Use "Custom Query" for Type is Defect).
___  Every integration defect has a regression test that includes a cross reference to the defect number. (Provide evidence, such as "grep" for "Defect" in the Test folder).
___  Code Inspection Summary Reports. (Each developer has at least one module reviewed, and also participates in at least one review.)
___  System Test Matrix. Cross reference every requirement (functional and non-functional) to a test case.
___  System Test Results History (functional and non-functional)
___  Coverage Test Report
___  Quality Assurance Retrospective (due at Final Exam).

Test Manager ___________
___  Printout of repository file hierarchy showing structure of test scaffolding. (Annotate as necessary).
___  Printout of "master" testing scripts. (Annotate as necessary).
___  Printout of execution of unit and integration test scripts..
Demonstration
___  Live Demonstration of run of instructor selected System Tests (with GUI) on the deployed system. May be manual instead of automated.
___  Live Demonstration of run of automated System Tests (via Costello). One per team member.
___  Live Demonstration of automated run of all unit tests in isolation from a fresh checkout on a clean machine.
___  Live Demonstration of automated run of all integration tests with a console UI (or test driver) from a fresh checkout on a clean machine.


Analyst ___________
___  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 System Tests and the released software. One way to do this would be to create a hand drawn traceability checklist, listing all the requirement numbers, and then columns for each of the above documents.
___  Requirements Rationale (Section 6.2 in SRS)


Implementation Manager ___________
___  Integration / Implementation plan is current. Includes planned/actual completion dates and estimated/actual LOC counts.
___  Daily Build reports posted.
___  Software deployed according to Deployment Plan.
___  Ant script for daily build.
___  (Optional) Other scripts for developer build.
Demonstration
___  Live Demonstration of Netbeans build and execution for both trunk and maintenance branch from a fresh checkout on a clean machine.
___  Live Demonstration of automated daily build procedure for trunk.
___  Live Demonstration of deployment to a clean machine.


Design Manager ___________
___  Current class diagram and javadocs posted that have a cross reference to the date or source code revision.
___  Requirements traceability matrix.
___  Printout of all design change requests.
___  Design Metrics report from JDepends (or other tool).  Writeup of interpretation of results and suggestions for design refactorings.
___  Design Rationale (aka "Design Issues List")


Change Manager ___________
___  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.
___  Evidence of any uncontrolled changes.  (See QA Plan section 5.5.2)


Project Manager/Change Manager ___________
___  Team web page (including visibility) is current and accurate and organized according to instructor template.
___  Printouts of weekly progress reports and project journal (or substitute).
___  Project Retrospective Report (due at Final Exam)
___  Performance Appraisals [html] (due at Final Exam)