|
Date
Due
|
Assignment
|
Comments
|
|
Th 1/11
|
Handout assignments for Release 1
|
Project Plan – Ben
Detailed Schedule - Tony J., Albert
Lines of Code – Ben and Chris
Change Control Plan – Tony T.
Quality Assurance Plan – Tony J.
|
|
Tu 1/16
|
Rough Drafts Of Documents Due
|
Training Plan – Albert
|
|
Th 1/18
|
Stage 1 Release Date
Assign Release 2 modules
|
TBD
|
|
Tu 1/23
|
Web Page-Project Tracking Documents
are kept updated, software process definitions are documented
and progress is tracked against estimates. Also, Project
Planning Documents on web
|
TBD
|
|
Th 1/25
|
Code walkthroughs are documented;
LOC estimates and actual are accounted for each other
and project standards
|
TBD
|
|
Th 2/1
|
Customer Acceptance Test ; Requirements
traceability exists from spec to test cases, All asserts
remain in code for Release 2, Source code adheres to
Coding Standard
|
TBD
|
|
Tu 2/6
|
Stage 2 Release must be sent
to customer
|
TBD
|
|
Th 2/8
|
Integral Test results: functional
PSP form for size and cost submitted for each module;
checklist is completed, release signoff form is signed
by all parties
|
TBD
|
|
Tu 2/13
|
Stage 2 Release Date
|
TBD
|
|
Th 2/15
|
All items in Release 2 checklist apply
to Release 3
|
TBD
|
|
Tu 2/20
|
Optional: known defect list
|
TBD
|
|
Th 2/22
|
All test cases are documented.
Unit test results: asserting testing
|
TBD
|
|
Tu 2/27
|
White-box testing, Black-box
testing
|
TBD
|
|
Th 3/1
|
Integration test results, Regression
test results
|
TBD
|
|
Tu 3/6
|
Stage 3 Release must be sent
to customer
|
TBD
|
|
Th 3/8
|
PSP form for size, cost, and
quality submitted for each module in release
|
TBD
|
|
Tu 3/13
|
Stage 3 Release Date
|
TBD
|
|
Th 3/15
|
Final Project Submission
|
TBD
|
