Title: SE2: Software Design and Architecture.
Course ID: CS 446, SE 464, ECE 452, CS 646
Deliverable: #4 - Project Status Report
Due: 8:00am Monday March 7th

Preamble:

All teams are expected to use a suitable source control system when developing their software, so that the record of software commits can if requested be made available to those marking this project.

Description:

Each team will submit a second project status report, documenting the progress they have made on implementing their project, the problems encountered, and solutions proposed. Estimates of the amount of work completed on each activity described in the original project proposal should also be provided. New activities may be introduced if deemed necessary. Significant prior events, and up coming ones should also be reported.

It will be assumed that all team members are given opportunity to review this report before it is submitted, and as such reflects the consensus of the team.

Project status reports will be marked (as part of the collective project documentation) at the end of the project. They will not be marked on any issue relating to the reported progress of lack of progress within a project, but rather on their ability to provide a professional and accurate high level overview of how each project is progressing, be that good or bad. They will be marked as if the reader was an external stake holder in the reported project.

Any glaring inconsistencies in project reporting will serve to make stake holders suspicious of the management of a project. To reflect such a negative contribution to the overall project documentation marks may be deducted.

Project status reports may also serve as a tool, for the instructor and TA's should they be asked to assist any project team, or (based on the report) feel the need to.

Project status reports may be one or two pages, but should not exceed this limit. Remember, the purpose of a status report is to provide an accurate high level overview of progress. It is not intended to be a journal.

Only one team member should submit this document to CS446 through learn.uwaterloo.ca by 0800 on March 7, 2016. PDF only. File naming scheme: cs446-d4_<project-name>.pdf (use ‘_’ instead of space in file names)

Assessment:

This project status report accounts for 1% of your final grade.

Confidentiality:

Project status reporting is a confidential corporate exercise. Distinct teams may not collaborate on the production of any one status report. Information contained within a team's status report should not be shared with other teams.