Each team will submit a written report and give a presentation, to demonstrate progress made since the beginning of the semester on the project. Include a reviewof the project work done last semester, in particular, the project goals, the miniproject, risk-analysis, and project planning. If you have refined any of these, in light of the further work done during this semester, be sure to include the updates in your report. Below is more detailed description of what should be included in the written and oral reports. 

Additionaly, each team member will submit a peer evaluation of every other team member and a self-evaluation, relating to the effective functioning of the team, using the provided evaluation form (doc, pdf). You will be asked to do the same with the second and the final reports. 

Recall from the syllabus that the first progress report is worth 20% of your final grade, based on:  50% on the technical merit of the design (common grade for the team); 25% on the quality and clarity of the report (common grade for the team); and 25% on the quality and clarity of the presentation (individual grades within a team may vary). Further, the self and peer evaluations are worth 10% of individual grades for the entire semeser.

Written Report:

The report should contain:

• [what] An overview of the projected functionalities, main components, and physical appearance of the final product. This should include a comprehensive description of the use-cases your product will support; use cases can be described textually or graphically, but each must be accompanied by a narrative that describes the context and goal of the use case. 

• [how]  A description of the proposed approaches (designs, algorithms, hardware needed, etc) to realizing the projected functionalities. Special attention should be given to the interfaces that your product will consume and provide. More specifically, it is expected that you document the interaction between your product, the user, and any associated products by way of message sequence charts - or a similar notation. The point here is to clearly describe the realization of functionality in your product, including the use of functionality that resides elsewhere.

• [quality]  A description of your plans for determining that your product functions correctly. You must describe plans for unit testing, integration testing, and system level testing. For transit projects, unit testing is expected to be integrated into the development cycle of your product. For all projects, system level testing must commence before the end of March 2011 - the month of April 2011 will be devoted primarily to testing and refinment of your product.

• [risk-analysis and mitigation]  Identify the key obstacles that you expect toward achieving your goal. We are interested in technical obstacles that are specific to your project, not generic obstacles like illness. Each risk that you identify must be accompanied by a mitigation plan involving your approach to tracking the status of each risk and resolving the risk. As part of the risk analysis, include what is the minimum system functionality that you will be able to deliver by the end of the semester.

• [project plan] Provide a refinement of the project plan and a weekly schedule that you developed before for achieving your goals. The schedule should provide a detailed set of objectives for each week and you must describe how you will evaluate whether each objective is met. The plan must identify the responsibility of each team member - for each objective a responsible team member should be identified as well as another team member whose job it is to "audit" progress to determine whether the objective has been achieved. For transit projects, the goal is to complete development by the end of March 2011. System and field testing will be the primary focus during April 2011 along with preparation for deployment of products. Your plans should reflect these overall goals.

In writing your report follow the best practices you have learned in previous courses for technical writing. The class web page under the heading, "On Technical Communication" has several links that may be helpful to you.

Submit your written report, one per team, via the web handin (Teams 1 and 6 to cse488 and 2-5 to cse486 handin) by midnight Feb. 25, 2011.

Oral Report:

You must prepare a PowerPoint presentation for your project using PowerPoint. Your presentation should take 20 minutes.. Presentations will be made in AvH 347, during the schedule class time (8:00-9:15 a.m.) on February 22 and 24, starting with team 1 and proceeding, in order, through team 6.

Submit your PowerPoint presentation, one per team, via the web handin (Teams 1 and 6 to cse488 and 2-5 to cse486 handin) by midnight Feb. 25, 2011.