Deliverable: #5 - Project completion
Documentation: 8:00am Monday March 28th
Presentation: Wednesday 30th March / Friday 1st April in class
Voting: By 8:00am Saturday 2nd April
Walk through: To be decided (on or before April 4th)

Description:

Do a demo. Save the world.

Requirements:

  1. Title page, including project name, team name, and each team members name and Quest IDs.
  2. Final status report (max 2 pages).
  3. Demo description (max 2 pages).
  4. Project documentation (Pages unspecified).
  5. Parts 1-4 must be compiled in a single PDF document.
  6. Perform eight minute demo.

Only one team member should submit document to learn.uwaterloo.ca by 0800 on Monday 28 March. File naming scheme: cs446-d5_<project-name>.pdf * (use - instead of space in file names)

Required documentation:

Before the final demonstration a status report and demo summary must be submitted. The status report should detail the functionality your app embodies and list to what extent proposed functionality remains unimplemented potentially with explanation as to why it was dropped. The intent of this report isn’t to punish groups who did not implement everything they proposed but rather to help us understand the challenges your group faced while working on your project.

Project documentation should also be submitted at this time. I should serve as an adjunct to the in-class presentation, describing the languages, internal architecture and design employed within your deliverable. Tools and/or public domain software, and interface standards employed by your team must also be described and acknowledged within this document.

Demo:

The demonstrations will be strictly limited to six minutes with two minutes for questions and discussion (8 minutes per group total). The demonstrations should both demonstrate what the system looks like from the user’s perspective and describe some of the technical underpinnings / challenges you faced creating your system. It may also present the risks and benefits associated with using your application.

Delivery is important: please practice your demonstration before you come and if you are worried about hooking up your laptop / mobile device toe the projector show up early and try it out in advance. Treat this demo as you would treat a demonstration to your product team on a co-op job. The demo should show the major scenarios your tool supports (including the ones you proposed at the outset of the course).

If it is deemed necessary, additional time may be requested by the TA's (outside of the class hours) to review and discuss individual projects with team members, to ensure that in the marking of them, they are themselves sufficiently familiar with them. The time and length of such meetings are to be arranged between the team and the TA's wishing to further review a deliverable.

Assessment:

The presentation, and supporting documentation is worth 8% of your final grade. The TA and instructor will individually grade the final deliverable in terms of the technical complexity of the completed system, the polish that has been applied to the system, and the functional and non-functional properties of the deliverable, employing as background as submitted documentation. This final grading of each project will be worth an additional 30% of your final grade.

Voting:

Each team may vote on the most successful team. Voting will be conducted as follows. Each individual will identify the name of the team whose project they deem best using swag.uwaterloo.ca/~ijdavis/cgi-bin/register.cgi. Voting will close Saturday 2nd April shortly after 8am, and once closed no further votes will be accepted. Members may not vote for their own project, and if found to have done so will incur a 2% penalty. Only individuals who vote will be eligible for a bonus. The votes each team recieve will subsequently be made public, but voter identities will not be revealed. The winning group will receive a 2% bonus on their overall assignment mark at the end of the course. In the event of ties this bonus will be split evenly.

A further 2% bonus will be awarded to any group who can provide a link to their app in a curated app store prior to the final exam (e.g., Blackberry World, iOS App Store, Windows Phone Store).

Walk through:

At least one TA will meet collectively with each team, at a time to be mutually determined, to review in detail the software developed, its architecture, construction, the management of this project, and the contribution of individuals within the team to it. They may also review the history of activity relating to this software development, as reflected in the commit history associated with the source control system being used. To the extent that this is possible members of the team will be mentored by the TA on the strengths and weaknesses of the system they have developed.

Confidentiality:

The development of your project is a confidential corporate exercise. Distinct teams may not collaborate on the production of any deliverable. Information contained within a team's final deliverable should not be shared with other teams, prior to its presentation to all teams. Any matter may be discussed during the final presentation.