In-class presentation/demo: 15 minute presentation to give an overview
of your project, show a demo of your working prototype in action, show us your code and
your compilation process, talk about interesting programming environments, libraries, etc. that
you used for your project. Note your class mates will be asked to rate the quality of your prototype, the perceived difficulty of what you did and the quality of your presentation A single tar or zip file containing all your source code and related documents. This should include a description
of your development environment and everything someone would need to know to compile your program(s), a users guide describing how to use your product, your project plan documents and design documents (including all versions including some document that indicated the changes since the design document was originally submitted). You should also include a file Bibliography which sources of useful information you used for your project (books, web sites, etc.). Include any other related files like the Power point file from your demo if applicable, etc. You must include a file README
that describes the rest of things in your tar/zip file. IMPORTANT: One file only in tar or zip format sent in email.
IMPORTANT: You must leave a copy of the README file out of the zip or tar file and you must link to both the README and the tar/zip file from your web page.
HTML page providing overview of your project. Also include links here to any information you found especially helpful (books, web sites, etc.) and a link to your tar/zip file. Final time tracking submission (this may be in the
tar/zip file as long as it is clearly identified in the README Hard copies of your README, your final design documents and your project plan documents (electronic copies also in the tar/zip file). You should turn in a reaction paper (hardcopy please). It must have the following sections:
React to working in a team: What have you learned that will make you a better team member in the future (either by positive or negative example)?Describe some frustrations of working in a team. Describe some of the best moments of working in your team.
Critique your team's initial estimates: What percentage of your initial plans did you actually implement? Give it a number between 1 and 10 (with 10 being we did everything).Discuss how your teams project plans and design specifications changed over the course of the project.
Based on the experience you've had so far, how long do you think it would take to produce a user-friendly, thoroughly tested, product level version of your project (programming system product vs programming system). Could your team do it or would you need more/different people?
Grade each of your team members: Give them each a number between 0 (worst) and 10 (best) in the following categories: 1) reliability in delivering what they promised, 2) commitment to participate and help the team, 3) actual useful contributions delivered and 4) pleasant to work with. Please also give concrete examples of the team members behaviour to support your scores. These scores will have an impact on your team member's grades but individual reviews will be kept confidential.