CS 3911 - Design Project

Spring Semester 2002
Section A - MWF 3:00 - 4:00 PM - Room 101 College of Computing
Section B - MWF 4:00 - 5:00 PM - Room 102 College of Computing


INSTRUCTOR:

Allison Elliott Tew

  • Office:  112 College of Computing
  • Phone:  (404) 385-0595
  • Email:   allison@cc.gatech.edu
  • Office Hours:  Open door policy and by appointment

    OVERVIEW


    GENERAL INFORMATION

    General Catalog Course Description:
    Prerequisite(s): CS 2340
    Intensive team-based project experience in the specification, design, and implementation of software and/or hardware for subsequent use in research, industry, and teaching.

    Course Objectives:
    Students will develop and demonstrate their abilities to work in a team on a substantial software project.  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:

    CLASS SCHEDULE
     
    Week Date Topic Deliverable Due Teams
    1
    1/4
    Course Overview    
     2
    1/7
    Course Overview (Take 2)    
     
    1/9
    Projects Overview    
     
    1/11
    Introduction to Effective Teamwork & Project Team Formation     
    3
    1/14
    Software Lifecycle & Requirements Elicitation (PPT)  Team Information  
     
    1/16
    Requirements Analysis & Projet PLan Overview (PPT)    
     
    1/18
    No class    
     4
    1/21
    Holiday!    
     
    1/23
    Design Overview (PPT)    
     
    1/25
    No class    
    5
    1/28
    No class    
     
    1/30
    Midterm Presentation Preparation Requirements Document & Project Plan  
     
    2/1
    No class    
    6
    2/4 - 2/8
    No class    
     7
    2/11 - 2/15
    No class    
    8
    2/18
    No class    
     
    2/20
    Midterm Presentations   Design Document  Section A - 3:00: 2, 3, and 5

     Section B - 4:00: 11 and 12
     
    2/22
    Midterm Presentations     Section A - 3:00: 4, 7, and 8

     Section B - 4:00:  9 and 10
    9
    2/25
    Midterm Presentations     Section A - 3:00: 1 and 6
     
    2/27
    No class    
     
    3/1
    No class    
     10
    3/4 - 3/8
    Holiday!    
     11
    3/11
    No class    
     

    3/13

    Testing Overview    

     

    3/15

    No class    
     12
    3/18 - 3/22
    No class    
     13
    3/25 - 3/29
    No class    
    14
    4/1 - 4/5
    No class    
     15
    4/10
    Final Presentation Preparation & Course Wrap-up    
     16
    4/15
    Final Presentations    Section A - 3:00 1 and 8

     Section B - 4:00 9 and 10

     
    4/17
    Final Presentations    Section A- 3:00 3 and 7

     Section B - 4:00 11 and 12

    4/19
    Final Presentations    Section A - 3:00 4 and 5
    17
    4/22
    Final Presentations    Section A - 3:00 2 and 6
    4/24
    Demo and Customer Delivery    
    4/26
    No class    
    18
    4/29 - 5/3
    Finals Week (No Exam)    



    TEAM INFORMATION
    Team numbers are available below.  General class information will be sent to via e-mail to the aliases for all teams, which will be set up to address your GT accounts.  Be sure your GT account forwards your mail to wherever you actually want to read it.

    Given that your team number is N, you have the following resources available:

    Team # Members Project Faculty Advisor
    1

    Dipika Jain

    Andrew Truong

    Ryan Dawe

    Robert Raines

    IE Advising Project  Ed Omeicinski

    Tim Miller

    Alex Bazala

    Tal Mekel

    MyCoC Web Project   Greg Turk
    3

    Samir Kaushal

    Borna Safabakhsh

    Nina Safabakhsh

    Aware Home  Gregory Abowd
    4

    KyungSoo Im

    Sangita Kumar

    Shuo Wang

    CHMSR Web Project   Chris Shaw
    5

    Chris Ingram 

    Max Hwang 

    John May

    CoC Advising Project Allison Elliott Tew 
    6

    Jeff Kwasha 

    Shaun McCarty

    Nathan Pettigrew

    QoS Wireless Project Santosh Pande 
    7

    Ali Faiz 

    William Bell

    Matthew Reeves

    My Radio  Ken Mackenzie
    8

    Jennifer Bryan

    Dahl Groenke

    Seth Lemoine

    High School Student Organizations Project  Yannis Smaragdakis
    9

    Chris Heilman

    "holland" Joseph King

    Moose Crossing Amy Bruckman
    10

    Cliff Duffer

    Michael Brown

    Nick Rodriguez

    Rashaan Griffith

     Karsten Schwan
    11 

    Gil Nowell

    Dan Orzechowski

    Wiewiek Sunarko

    Sam Yi

    Jim Xu 
    12  

    Robert Jameson 

    Oliver Dodd 

    Eric Price

    Ivan Raikov

     Mike McCracken  
     
    PROJECT IDEAS              Develop a well designed and tested Web site for the Center for Human-Machine Systems Research
                (CHMSR).  Unlike GVU, who is interdisciplinary, CHMSR is a 'wholly owned subsidiary of ISyE.

    DELIVERABLES


    Requirements Document
    Details:  TBA

    Project Plan
    Details:  TBA

    Design Document
    Details:  TBA

    Midterm Presentation
    These presentations are meant to provide a progress report and to make sure that the team, their advisor, and the course coordinator have a clear view of the current status and plans for the project.    Each presentation should include at least the following components:

    1. A concise statement of the goal or vision for the project and a brief description of the requirements derived from the goal.
    2. What has been accomplished so far.
    3. What the schedule looks like for the rest of the term.
      • It is strongly suggested that your schedule should be for an iterative development approach, so this presentation should include you plans for development iterations.
      • Remember also that a good test plan should be executed on anything that is implemented, so your schedule should include a realistic amount of time for testing.
    4. A discussion of any problems or risks the team is facing.
    Everyone on the team must have a part either in this presentation or the one at the end of the term, so half of the team should do part of each.  Since there is more to present at the end of the term, a 5 person teams should use only two presenters this time.
     

    Final Presentation
    Each presentation should include at least the following components:
     

    1. A concise statement of the goal or vision for the project and a brief description of the requirements derived from the goal.
    2. A description of what you accomplished during the semester and a demonstration, if feasible.
    3. A discussion of how well the results matched your initial plan, including the reasons for any significant deviations from the plan.
    4. A few words about what you learned from this experience.
    Since everyone on each team is supposed to do a part of one of the two presentations, be sure that the team members who didn't present at mid-term do the major part of this one.  It's ok for someone to be part of both, but not as the primary presenter.

    Delivering the Project to your Customer
    The final requirement for the semester includes scheduling a meeting of the whole project team with the customer.  Attendance by the faculty advisor at this meeting is strongly encouraged, but not required.  The agenda for this meeting should include:
     

    1. A brief presentation of what you have accomplished relative to the requirements, probably taken from your final presentation to the class.  This presentation need not be a formal, stand-up one unless your customer is actually a group.
    2. A demonstration of the operation of your software to the customer.
    3. An opportunity for the customer to try out the software.
    4. Discussion with the customer of the strengths, weaknesses and opportunities for extension of the software.
    5. Hand over of the source code and documentation of the software.  Remember that documentation can include such things as test results, in addition to a user manual that describes the features of your system.
    I will send the customer a request for feedback on your efforts as a whole and on the quality/professionalism of this delivery meeting.  Since customer feedback will be considered in the grading process, those groups which include graduating seniors should schedule this meeting as early in the last week of class as possible.

    Evaluations
    Each team member will complete a set of self and peer evaluations for each team member.  You will be asked to evaluate the effort and performance of the individuals in your group to both the instructor and your faculty advisor.  This feedback will be a significant factor in determining an individual's grade.


    Georgia Tech Disclaimer
    This page is maintained by: allison@cc.gatech.edu
    Last Modified on Friday, 11 January, 2002.