CSE 4904 Computer Science Design Lab Fall 2008University of ConnecticutDepartment of Computer Science & EngineeringCSE 4904— Computer Science Design LabGeneral InformationRead this sheet carefully, and save it for future reference.InstructorName: Chun-Hsi (Vincent) HuangOffice: 259 ITEBPhone: 486-5472Email: [email protected]: http://www.cse.uconn.edu/~huangCourse descriptionThis course focuses on the design and implementation of complex software and/or hardware systems to solveproblems. Students will, in groups or individually, apply their coursework/experience to formalize a problem,make decisions, resolve the problem and communicate their work via presentations to peer students. The instructoroffers comments/advice on student projects, coordinates meetings, serves as hands-on manager, evaluates studentprojects and maintains a webpage as the repository of class materials, student presentation slides, etc.Textbook and MaterialsThere is no required textbook for this course. Suggested references, however, will be posted to the course webpage.Meetings and MilestonesThe class meets from 3:30-5:30PM on Wednesdays. The meeting formats, schedules and project milestones willbe finalized in the second week.Week of Task(s) Meeting Type Meetig PlaceAug. 27 Group Formation, Project Identification Class MONT 221Sep. 3 Finalizing Project Scopes and Class Milestones Class MONT 221Sep. 10 Group Presentations: Milestone I Class MONT 221Sep. 17 Coordinator Meeting - Report (Phase I) Discussion Discussion ITEB 201/259Sep. 24 Group Presentations: Milestone II Class MONT 221Oct. 1 Coordinator Meeting - Report (Phase II) Discussion Discussion ITEB 201/259Oct. 8 Lecture/Comments Class MONT 221Oct. 15 Group Presentations: Milestone III Class MONT 221Oct. 22 Coordinator Meeting - Midterm Report (Phase III) Discussion Discussion ITEB 201/259Oct. 29 Lecture/Comments Class MONT 221Nov. 5 Coordinator Meeting - Report (Phase IV) Discussion Discussion ITEB 201/259Nov. 12 Group Presentations: Milestone IV Class MONT 221Nov. 19 Coordinator Meeting - Final Report (Phase V) Discussion Discussion ITEB 201/259Nov. 26 Thanksgiving Recess - -Dec. 3 Group Presentations: Milestone V Class MONT 2211Preliminary milestones are set as follows.Milestone I: Preliminary Specs and Initial Project PlansMilestone II: Final Specs and Detailed Project PlansMilestone III: Implementation and Test PlansMilestone IV: Integration PlansMilestone V: Final Project DemonstrationCourse evaluationThe following table indicates the grade breakdown which I will use in the evaluation. I reserve the right to makeadjustments to the breakdown if I feel it is necessary.40% Efforts: Class Participation, Group Interaction and Presentations60% Outcomes: Final Demonstration, Project Codes, Documentation, etc.Incomplete (I) gradesWe will follow the University Policy on Incomplete Grades. Take the time to familiarize yourself with the contentsof the related pages.Generally, incomplete (“I”) grades are not given. However, very rarely, circumstances truly beyond the student’scontrol prevents him or her from completing work in the course. In such cases the instructor can give a grade of“I”. The student will be given instructions and a deadline for completing the work, usually no more than 30 dayspast the end of the semester. University and department policy dictate that “I” grades can be given only if thefollowing conditions are met:• An Incomplete will only be given for missing a small part of the course.• An Incomplete will only be given when the student misses work due to circumstances beyond his/her control.• An Incomplete will only be given when the student is passing the course except for the missed material.• An Incomplete is to be made up with the original course instructor within the time specified by the appro-priate University regulation (see appropriate document above), and usually within the following semester.• An Incomplete will not be given to allow the student to informally re-take the entire course, and have thatgrade count as the grade of the original course.Incompletes can not be given as a shelter from poor grades. It is the student’s responsibility to make atimely resignation from the course if he or she is doing poorly for any reason. The last day to resignthe course is October 27.Course ProcessThe following is a tentative outline of the course process:• Problem (Project) Identification; Group Formation• Development of Project Specification• Interactions and Feedback Collections• Exploration of Design Alternatives• Detailed Design and Testing• Implementation and Integration• Team Interactions and Dynamics• Setting and Meeting Milestones• Evaluation2WWW homepageThere is a web site for the course. Students are expected to visit the web site on a regular basis. The URL