CSCI 450/590
Fall, 1999
Team Responsibilities and Reports
Software Engineering Team:
The SE team carries out the software development for the project. It will decide upon a
development process and methodology, project standards, and set up, manage, and
execute its schedule.
1] It is responsible for submitting to upper Management (Instructor) each week a Report
Book containing, cumulatively, two Project Plan Summaries, one for program
development and one for document development (‘documentation’ is used in the wide
sense in that it includes any document other than one that has code.). There must also be
an analysis of the amount of progress toward the quality goals.
It will compose these summaries from weekly, personal Project Plan Summaries from
each team member concerning his or her own activities. To provide the data for these,
each member will record each week in her or his Engineering Workbook two Defect
Recording Logs, one for programs and one for documents, a Time Log, a Job Number
Log, and a Weekly Activity Summary. These forms are to contain only data pertaining to
the work on the project.
2] The SE team must also include in the Report Book each week a Project Schedule , in
the form of an annotated Gantt chart or similar, that indicates milestone (including
review/inspection) dates, planned and accomplished. This schedule must specify the
assigned tasks and expended effort of each team member. There must also be a
discussion of the amount of progress toward the uncompleted milestones including, in
particular, project completion.
*> The SE team must submit its Report Book weekly to upper management. Each team
member must submit her or his Engineering Workbook to upper Management on the due
date of the project’s deliverables.
Quality Assessment Team:
1] The QA board will collect, until the product delivery date, copies of the weekly
Project Plan Summaries and Project Schedules developed by the SE team it assesses. On
the basis of this, and other periodic data it wishes to collect from the assessed team, it
will prepare a Process Quality Assessment Report that evaluates the successes and
failures and overall quality of the observed software development process and
recommends changes to it. The Report must also include the Summaries, Schedule sheets
and other data it collects. The QA board must also include in an appendix to the Report a
Weekly Assessment Activity Summary for each member throughout the project.
*> The QA board will submit its Process Quality Assessment Report to upper
Management by December 9, 1999.
Acceptance Testing Team:
1] The AT team will interact with the SE team during the development of the
Requirements Specification, although the latter has the major responsibility for
developing the Specifications. The AT team will prepare a Specifications Evaluation
Report concerning the Specifications that the SE team develops. This report is
cumulative over all increments of the products that the SE team develops. The AT team
may share this report with the SE team.
2] It must develop a Formal Test Plan, and corresponding tests, for carrying out the
acceptance testing of the products delivered by the SE team. This may not be shared with
the SE team. The AT team will execute these tests and prepare a final Acceptance
Evaluation Report based on the results of the tests. This report must consist of the Test
Plan, the test results and a section concerning the acceptability of the products relative to
the requirements. The AT team must also include a Weekly Acceptance Activity
Summary for each member throughout the project in an appendix to the Report.
*> The AT team must submit to upper Management its Specifications Evaluation Report
whenever its SE team completes the Specifications of any increment of the deliverables.
It must submit its Acceptance Evaluation Report to upper Management by December 9,
1999.