University of Utah

School of Computing

Software Engineering Laboratory

CS 4500 Spring Semester, 2010
WEB 2230 TH 2:00-3:20
Instructor: Thomas C. Henderson

Announcements

Week 2 (Jan 18-22)

Weekly Management Report due Tuesday 19 Jan at noon
Project Plan due 29 Jan 2010.
Team meetings are held in my office 2871 WEB.

Week 1 (Jan 11-15)

Teams must be formed by the end of the first class (12 Jan 2010)
Subscribe to cs4500 by Friday (15 Jan 2010).

This list is in the Sympa list of lists in the CADE

Send the name of the team and team members to tch by Wednesday (13 Jan 2010).

Please send team URL as well no later than Thursday (14 Jan 2010).

Attendance required in class all Week 1 (12,14 Jan 2010).
Bids for projects are due by 15 Jan 2010 (midnight); see bid document.

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 software engineering lab course. According to the CS department class catalog this course involves:

Development of significant software systems by small student groups, with emphasis on applying sound, disciplined software engineering practice.

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: The Principles of Project Management, Williams
You can contact me with questions by email (Sympa list for teach-cs4500 in CADE)
Subscribe! to the class mailing list: (Sympa list in CADE)

Prerequisites

The prerequisite is successful completion of CS 3500.

Course Description

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

Teams

Teams must have 3 or 4 members and must be formed by the end of class (12 Jan 2010).

Bids

Each team must submit 3 bids on projects by 15 Jan 2010.

Possible Projects

There are 2 possible types of projects:

Industry Sponsored: Descriptions given by local companies who act as clients (see project descriptions in industry); any team working on a project in cooperation with an external sponsor (other professor, company, etc.) must follow the guidelines for an industrial project.
Self Sponsored: A team may propose a project; this will require approval, and Prof. Henderson will act as client.

Meetings

Once teams are formed, and projects are picked, the rest of the course will be largely lecture-free. Instead, each group will meet whenever requested to meet by Professor Henderson, or after requesting a meeting and arranging a meeting time. Attendance at these update meetings will be mandatory.

Each team must turn in a Weekly Management Report by Monday noon 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 the following deliverables during the semester (details on formats of documents, etc. can be found in Guidelines link above):

Bids on 3 projects
Project Plan
Staged Releases
Product Release
Final Report

Note that you must deliver reports in a format that I approve. You can use the guidelines in the recommended text for the class.

Software Used to Support Class

Students can use whatever platform they like to develop their projects. A UNIX environment is available in the CADE lab, and an NT environment is available in the NT lab. Your choice of platform and development environment should be justified in your group meetings.

Assignments

Each team will be assigned a project, hopefully from their ordered list of preferences. Each of the sponsors will present their projects on the first day of class to help you choose your preferences. The schedule for assignments is as follows:
Â

Date	Particularly Appropriate Reading	Assignments	Assignments Due
		Team meeting with prof every 2 weeks
Week 1: Jan 11-15	Chapters 1-2	(1) Form team (2) Make bids (3) Create project website	(1) Team formed (2) Bids submitted (15 Jan by midnight; see bid info)
Week 2: Jan 18-22	Chapters 3	(1) Project Plan
Week 3: Jan 25-29	Chapters 4		(1) Project Plan (Friday 29 Jan)
Week 4: Feb 1-5
Week 5: Feb 8-12		(1) Stage 1 Release
Week 6: Feb 15-19
Week 7: Feb 22-26
Week 8: Mar 3-5
Week 9: Mar 10-12		(1) Stage 2 Release	(1) Stage 1 Release (Friday 12 March)
Week 10: Mar 17-19
Week 11: Mar 22-26		Have fun!	Spring Break
Week 12: Mar 29 - Apr 2		(1) Stage 3 Release	(1) Stage 2 Release (Friday 2 April)
Week 13: Apr 5-9
Week 14: Apr 12-16		(1) Product Release	(1) Stage 3 Release (2) Formal Presentation to Industry Sponsor (Friday 16 April)
Week 15: Apr 19-23		(1) Final Report (2) Demo	(1) Product Release (Friday 23 April)
Week 16: Apr 26-28			(1) Final Report (2) Demo (Thursday, 29 April)
29 April 2009			Demo Day 9-noon WEB 130

Grade

Bi-Weekly Meetings	10%
Documents	30%
Project Web Page	20%
Final Project & Demo	40%

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.