Each team must submit a notebook/binder with the following items (preferably in the order given):
Cover page with team name, member names, current date, and project name
An index page that lists contents -- can be numbered or tab delimited:
Description of project -- provide a definitive list of what functionality exists, what shortcomings there are, and future improvements
Class Diagrams / Schema / Design Documents
Output captures demonstrating project behavior
Notes from team meetings
Test plans and results
A list of system requirements in order for your project to do do what it needs to do (please list necessary hardware and software -- think about what would be needed if your project were to be set up on a different machine by another team)
Any additional documents that show how your team worked through its development process and that you feel would be relevant to another team that might assume your work at a later date
A printout of the Subversion directory and sub-directories your team used. A printout of the log from Subversion.
Reference page (list any references you used in putting together the work your team performed)
A CD with your source code (organized so it is easy to find things) and a readme.txt file that describes how to run your program (if a password is necessary for something, be sure and include it). NOTE: the assumption is your program will be run from the server on which it resides.
NOTE: Your notebook/binder will be kept by the instructor for accreditation purposes.
Each team will have 25 to 30 minutes to present its results on the 20th of March. Include in your presentation the following:
overview of project (what it is and why it was needed -- be sure and introduce each team member to the audience)
screen captures of program as you deem necessary
source code samples as you deem necessary
execution of your product
time for questions from the audience (leave at least five minutes for this)
NOTE: visual aids / prepared slides are required -- the customer will be present for your demonstration as will members of the faculty and Professional Advisory Board
NOTE 2: please run through your presentation ahead of time so you have an idea of how much time it will take and so it will be organized
Each member of each team MUST present some facet of the project. Please dress in a semi-formal manner (button up shirt, preferably slacks, no tennis shoes -- gals can wear a blouse and skirt or dress (or button up shirt and slacks if you prefer). Try and remember to speak clearly to your audience, maintain eye contact, and avoid constantly reading from your slides (slides are there for the audience - NOT YOU). You will be evaluated on your presentation as a team. Please be sure and read through *this document (Senior Project Oral Presentation Rubric)* to help with your presentation. Furthermore, the following two documents will be used to evaluate your project as a whole, so make sure you address the items in them as you progress through the quarter.
Each individual must submit to me via email a document (.rtf, .doc, or .pdf format) that contains the following:
An evaluation of each team member that includes a grade you feel they deserve (use 0.0-4.0) based on that team member's contribution
An evaluation of your contribution and the grade you feel you deserve
What you learned (or had to learn) for the project -- this can include technical aspects and/or team dynamics. Is there anything you would do differently if you could start over with the knowledge you have now?
NOTE: This evaluation will be viewed by the instructor ONLY. Please be honest, frank, and professional. It is your ethical responsibility to do so as a member of the Computer Science Department. Do not discuss your evaluation with other members of the class.
Use this document as a template for evaluating each team member (including yourself). Place all member evals into a single document, please: team_member_eval_form.txt
NOTE: Extra weight will be given to what team captains have to say regarding item 1
This document is subject to change as necessary to clarify submission items.