University of Utah

School of Computing

Senior Capstone Project

CS 4500 Fall Semester, 2018
WEB L120 MW 10:45-11:35
Instructor: Thomas C. Henderson

Announcements

Week 2 (Aug 27-29)

Individual logs must be on the team websites and give data from week one by Monday (27 Aug 2018)

Logs and WMR's are due every week by Monday 9am, unless Monday is a holiday; then they are due the next day at 9am

The team Weekly Management Reports (WMR's) should be on the team website and the first one is due by Monday (27 Aug 2018)
Demo Day will be held on 7 December from 9am to noon in the Catmull Gallery in the Warnock Engineering Building.

Week 1 (Aug 20-22)

Teams must set meeting time with instructor by the end of the first class (20 Aug 2018)
Create team web site and send team URL to tch@cs.utah.edu by Friday (24 Aug 2018).
Send team URL to tch@cs.utah.edu by Friday (24 Aug 2018).
Send the name of the team and team members names and email addresses to tch@cs.utah.edu by Wednesday (22 Aug 2018).
Attendance required in class all Week 1 (20,22 Aug 2018).

Overview of Course / Links

Course Objectives

Engineer (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!

Instructor

· Thomas C. Henderson, Professor

· E-Mail: tch@cs.utah.edu

· 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: tch@cs.utah.edu

Prerequisites

The prerequisite is successful completion of CS 4000.

Course Description

This offering of the course will be structured in terms of deliverables.

Teams

Teams carry forward from CS4000.

Meetings

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.

Deliverables

In addition to the update meetings, you will be required to maintain and make available information concerning alpha and beta versions of the project.

Policy and Appeals Procedure

See Academic misconduct page as well as the Code of Student Rights and Responsibilities, SoC policies page, or the Class Schedule for more details.

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:

Appeal to Department Chair who should be notified in writing within 40 working days; chair must notify student of a decision with 15 days. If faculty member or student disagrees with decision, then,
Appeal to Academic Appeals Committee (see flyers posted in MEB and EMCB for members of committee). See II Section D, Code of Student Rights and Responsibilities for details on Academic Appeals Committee hearings.

Software Used to Support Class

Students can use whatever platform they like to develop their projects.

Assignments

The schedule for deliverables must be submitted to the instructor and approved by the second week of class (29 Aug 2018)

Grade

Bi-Weekly Meetings, Logs, Participation	10%
Documents	10%
Project Web Page	10%
Final Project & Demo	70%

Grades will be based on these percentages except for the following:

If a deliverable is missing, that will cause drop in class grade by one letter grade (i.e., grade for class on all work - 1 letter grade)
For each deliverable, there will be 2 fixit rounds allowed; i.e., if I ask for a modification, you can make them and still get an A.
Individuals logs will be counted toward their grade only - not the group.