CS 4911 - Design Project - Summer, 2007

Course Information

Name: Design Project
Number: CS4911
Meeting Times: Section A, MWF, 1320 - 1430, CoC Room 101

Catalog Description

Contact Information

Professor: Bob Waters
Office: CoC 111
E-mail: Bob Waters

Resources

Team Swiki: http://swiki.cc.gatech.edu/cs4911-su07

Prerequisites

CS2340

Objectives

Students will develop and demonstrate their abilities to work in a team on a substantial software project. Clear expression of ideas in the form of presentations and documentation is essential. There are three conceptual parts to the project efforts expected of each team:

     1. Define the problem
     2. Design and implement a solution
     3. Deliver the system to the customer

Course Organization

Projects will be done by teams of four or five students. You may choose your own teammates. However, you may be asked to add a member if the number of students in the class does not readily divide into groups of this size.
Each team will have a faculty advisor and a customer.

The job of the customer is to negotiate the project requirements with the team and to provide ongoing input about proposed solutions.
The faculty advisor will meet with the team on a weekly basis to monitor progress, make sure the team is following a coherent process, and assist with team organizational problems.

Each team will present a midterm report and a final demo and report to their advisor, their customer, and the rest of the class. Each student in the class must present during the term, either at the midterm or the final presentation.

Attendance at presentations is mandatory.
Each class date missed where a presentation is given results in a letter grade reduction of the student’s presentation grade.
Missing your own presentation (it happens) results in loss of letter grade from your final course average.

Deliverables

Description or Template	Due Date	Weight	Grading Criteria
Status Reports	Weekly (each Friday)	3%
Project Planning	05/30 (Product Backlog, Iteration 1 Backlog) 06/14 Iteration 2 Backlog 07/07 Iteration 3 Backlog, Final Product Backlog	4%	Criteria
Project Requirements: Project Vision and Use Cases	05/30 Vision initial 06/04 Iteration 1 Use Cases Detailed 06/18 Iteration 2 Use Cases Detailed 07/25 Iteration 3 Use Cases Detailed 07/25 Vision final	10%	Criteria
Project Design: Conceptual Architecture, Rationale and Detailed Design	06/04 Initial Conceptual Architecture and Iteration 1 Design 06/27 Iteration 2 Design 07/25 Final Conceptual Architecture and Detailed Design	14%	Criteria
Iteration 2 Design Review and Demo	07/03 -- 07/07	5%	Criteria
System Acceptance Test Plan and Report	07/02 Test Plan 07/25 Test Report	5%	Criteria
Midterm (Iteration 1) Design Review Presentation	06/11 -- 06/16	5%	Criteria
Final Presentation and Demo	07/23 -- 07/27	10%	Criteria
Delivery Documentation	07/27	4%	Criteria
Individual Design Analysis	07/27	10%	Criteria
Customer Delivery/Advisor Grade	08/03	30%
Peer and Self Evaluation	07/27	NA

Projects

Class Schedule


Week	Date	Topic	Deliverable(s) Due	Other Information
1	05/14	Course Overview Software Lifecycles		Week 1 should be for getting your team organized and selecting a project. Make contact with your customer, develop an idea of what the the project is supposed to do, create your team swiki pages and decide on team roles.
	05/16	Status reports sample format Project Planning Requirements (Vision and Use Cases)
	05/18	Architecture and Design Overview Giving Presentations and Conducting Design Reviews System Acceptance Test Plans Final Team Assignments	*Status Report #1*
2	05/21	No Class		Start writing your project vision. Coordinate with the customer so that you get a prioritized list of the key features. Take the prioritized list of features and create a Project Backlog. From this, plan out the next timeboxed iteration that will completed end of week 4. Then create the iteration backlog. for the first iteration.
	05/23	No Class
	05/25	No Class	*Status Report #2*
3	05/28	HOLIDAY		Begin work on the System Acceptance test plan. What tests will you run to show that the system built is the same as the system requested? Create Conceptual Architecture for overall set of features Identified by customer and record the rationale.
	05/30	No Class	Vision Document Product Backlog and Iteration 1 Backlog
	06/01	No Class	*Status Report #3*
4	06/04	No Class	Iteration 1 Use Cases Detailed Iteration 1 Design Updated
	06/06	No Class
	06/08	No Class	*Status Report #4*
5	06/11	Presentations		Begin 2d Iteration, use product backlog to take next highest priority set of features and create iteration backlog. Detail Iteration 2 Use Cases. T2, T4, T5
	06/13	Presentations	Iteration 2 Backlog	T9, T12, T13
	06/15	Presentations	*Status Report #5*	T14
6	06/18	No Class	Iteration 2 Use Cases Detailed
	06/20	No Class
	06/22	No Class	*Status Report #6*
7	06/25	No Class
	06/27	No Class	Iteration 2 Design Updated
	06/29	No Class	*Status Report #7*
8	07/02	Iteration 2 Demos	Each team come at your time to class and plan to spend about 25 minutes demoing your Iteration 2 product and doing a small design review with me. System Acceptance Test Plan	Begin Last Iteration, use product backlog to take next highest priority set of features and create the iteration backlog. Detail Iteration 3 Use Cases. T2 1320 T4 1355
	07/04	Holiday
	07/06	Iteration 2 Demos	*Status Report #8* Iteration 3 Backlog Final Product Backlog	T5 1320 T9 1355
9	07/09	Iteration 2 Demo		T12 1320 T13 1355
	07/11	Iteration 2 Demos		T14 1320
	07/13	No Class	*Status Report #9*
10	07/16	No Class
	07/18	No Class
	07/20	Final Presentations	*Status Report #10*	T2, T4
11	07/23	Final Presentations		T5, T9
	07/25	Final Presentations	Final Vision Document Final Conceptual Architecture Final Detailed Design Final Use Cases Final Test Report	T12, T13
	07/27	Final Presentations	*Status Report #11* Individual Design Assessment Customer Delivery Documentation	T14
12	07/30		Peer and Self Evaluation to advisors, Final Customer Delivery and Demos