CS 3351 A

Studio Design Project

Coordinating Instructor:

Beginning on Monday, May 22, there will be no regular class meetings.  Scheduled class hours are to be used for group meetings and for two presentations later in the term.

 

Final Presentation Schedule -- as of 7/16

Monday, July 24
Wednesday, July 26
Friday, July 28
Teams 6, 8 & 10
Teams 1, 2, 3 & 4  
Teams 5, 7 & 9, 
The presentations will be at our usual class time on these days, 1:20 - 2:30 PM.

Final Presentation Description

Like your midterm presentations, these presentations should be about 15 minutes long, to leave a little time for questions.  This time, 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.
 

Course Description and Information

From the catalog CS 3351 Studio Design Project.  A project-oriented laboratory course used to familiarize
                                   students with software engineering methods in a realistic environment.

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

  4.  
Course organization: Course Schedule:
  • Week of May 15: group formation and project selection
  • Week of May 22: work with customer to develop a requirements specification
  • Week of May 29: complete a project plan and begin development of a design document
  • Week of June 19: Mid-Term presentations
  • Week of July 24: Final presentations
  • Process Document

    HTML version of the Lightweight Software Process document

    Recommended Text

    On Time, Within Budget,  E.M. Bennatan, Wiley, 1995.

    Team Information

    Teams & Advisors

    Team #
     Members
     Advisor
     Project
    1
     Sengbush, Tharayil, Zegarelli, Chung, Freeman
     McCracken
    Motorola 
    2
     Blick, Harrell, Greene, Shows 
     Eiselt
     Deloitte Consulting 
    3
     Holland, Bentley, Dailey, Jednaszewski
     Hodgins
    Vacation/Sick Leave Reprots 
    4
     Mundy, Anderson, Durden, Lytle, Sayler
    Mackenzie
     Aware Home #1
    5
     Warzecha, Faulkner, Fiorentino, Medlin, Yang
    Mark 
    Center for Rehabilitation Technology 
    6
     Dand, Homier, Magid, Swartley, Wong
     Tew
    Dental Office Support System 
    7
     Robertson, Woo, Chum 
     Bobick
    Aware Home #2
    8
     Nathanson, Bos, Nelson, Nguyen, Sotack
     Leahy
    Web development for GTRI EMTEF 
    9
     Rominger, Kolli, Mahmood
    Guzdial
    Squeak: Movie/Play Authoring Tool
    10
     Hensey, Geist, Peachy, Chalk, Bradshaw
    Potts 
    Web-based groupware suite
     

    Descriptions of Project Ideas