Students are expected to contribute to learning by asking questions and making
relevant comments in class and on the class newsgroup. Quality is more important than quantity.
Disruptive activity contributes negatively. Please make sure all disruptive devices are disabled while
in class. If you have a good reason for wanting to be disturbed in class, please contact me to make the
appropriate arrangements.
Project Reports:
The sequence of three project reports serves to systematically document the project.
Some details are outlined in the guide for Capstone project proposals (Reading 1). Further details will
follow in class. Students are strongly encouraged to continually seek feedback on their working drafts
from their project advisors, Capstone instructor, academic advisors, and others.
Source code and demo:
Well packaged and documented source code is an important component of the
Capstone project. The code will be evaluated on not only how well it functions but also on aspects such
as clarity and elegance. The source code does not have to be released under any specific license (although
a free software license1
is strongly recommended); however, no legal encumbrances (such as nondiscolsure agreements) will be
entertained. All code must be submitted electronically (only) as outlined in the Submission Instructions
section below.
Final Oral Presentation:
Every student must make an oral presentation of his or her work on a date near
the end of the semester. The date will be selected to ensure good attendance by department faculty
and others, and will be announced in the first few weeks.