WEB L120 MW 10:45-11:35
Instructor: Thomas C. Henderson
(n): a designer or builder of engines
Engineer (vt): to lay out, construct, or manage as an engineer
Engineering (n): the art of managing engines
This course is the senior capstone project course. According to the CS department class catalog this course involves:
This course is the capstone experience for graduating Computer Science seniors. It involves the development of significant software systems by small, self-selected student teams, with emphasis on applying sound, disciplined software engineering practice. Projects are defined and selected at the beginning of the semester, after which progress is demonstrated through documentation, meetings, and demos. The class culminates in a Demo Day at which students present their projects to faculty, students and project sponsors.
Because of the prerequisites for the course, we assume that you have had lots of opportunities to learn sound, disciplined software engineering practice. Now here's your chance to show off a little on a significant project. Show us what you can do!
· Thomas C. Henderson, Professor
· E-Mail: firstname.lastname@example.org
· Phone: 801-581-3601
· Fax: 801-581-5843
· Office Hours: By appointment 2871 WEB (arrange by email).
· TA: None
Recommended (Not Required) Book for
class: Software Project Survival Guide, McConnell
You can contact me with questions by email at: email@example.com
The prerequisite is successful completion of CS 4000.
This offering of the course will be structured in terms of deliverables.
Teams carry forward from CS4000.
The course is largely lecture-free. Instead, each group will meet regularly with the instructor. Attendance at these update meetings will be mandatory.
Each team must turn in a Weekly Management Report by 9am Monday each week; this is done by posting it on the team web page.
In addition to the update meetings, you will be required to maintain and make available information concerning alpha and beta versions of the project.
Appeals of Grades and other Academic Actions
If a student believes that an academic action is arbitrary or capricious he/she should discuss the action with the involved faculty member and attempt to resolve. If unable to resolve, the student may appeal the action in accordance with the following procedure:
Students can use whatever platform they like to develop their projects.
The schedule for
deliverables must be submitted to the instructor and approved by the
second week of class (29 Aug 2018)
Bi-Weekly Meetings, Logs, Participation
Project Web Page
Final Project & Demo
Grades will be based on these percentages except for the following: