CSc 309 Release Planning Logistics

Spring 2009

PT = Peer Team Testing - During Lab (1 hr) Procedures for Release 2!

  • Reviewing team randomly selects one person from the development team. Developer walks through the deployment plan and demonstrates deploying the application on the production web server.
  • Reviewing team divides into two subteams: System testers (3) and Defect Seeders (2).
  • System testers study the System Test documentation and verify consistency with the SRS and User Prototype.
  • System testers perform the System Tests to see if the software performs as specified. Note any discrepancies on a Defect Log and submit to instructor.
  • With assistance from a developer, Defect Seeders check out the repository and create a running version of the application on a local workstation. Seeders secretly insert one or two defects into the working copy of the code. Development team does regression testing to see if their test suite can identify the seeded defects.
  • (At instructor discretion) The development team will walkthrough the defect repair procedure using a defect found by the system testers or for an instructor specified enhancement.

RC = Release Criteria approval

  • Each team must show the instructor the empirical evidence that they have met the Release Criteria before they may meet with the Customer for Acceptance Testing. (Estimate 30 min.)
  • The instructor will review the Release 1 Scoresheet to verify all items are complete and to observe the "live demonstration" items.(Estimate 30 min.)
  • Each developer submits their release 1 binder for the instructor to grade.

AT = Customer Acceptance Test

  • The team must find an available, quiet, CSC lab room and schedule a time with the Customer and Instructor for the Customer Acceptance test.
  • The team's web application should be deployed on the production system. The Customer will provide the team with her own test data and ask them to run their system with this data. (Estimate 1 hr).
  • It is not required that all team members attend the Acceptance Test; only the Analyst is required to attend. However most students find it very illuminating to watch the customer user your software so everyone is invited. It may be helpful to have one or more team members (developers) available nearby in the event problems are encountered that require a developer to fix.
  • The Customer will decide whether to accept or reject the product. (In some cases, the Customer may need to spend additional time with the application after the meeting before making a final decision).

Schedule

June 1-5

M Tu W Th F
8
9
10 OH OH OH
11 PT3, PT4 RC3 LEC LEC
12 PT2, PT1 LAB Project Retrospective
13 RC 1
14
15 RC2 AT1
16 RC4AT3
17 AT4

PT = Peer team testing
RC = approve Release Criteria
AT = Acceptance Test
OH = office hour
LEC = Lecture
CSL = Computer Systems Lab 14-235
XX = unavailable

1= C4
2= Crosshair
3= Marker
4= BluGoo

Scoring

Score from Customer Acceptance Test (15 possible) _ _

Penalties

_ _Number days late * -3 = _ _

Acceptance Test defects found
_ _ Critical defects (product rejected)
_ _ Major defects * -1 = _ _
_ _ Minor defects * -.3 = _ _
_ _ Trivial defects * -.05 = _ _

_ _ Subtotal

Total (Score - penalties) _ _

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