CS 492
Senior Design Project II
Description:
A technical project emphasizing engineering design principles on a
specific topic in any field of computer science or engineering to be
carried out by the team of senior students under the supervision of a
faculty member. Students continue the project they started in CS 491
course, with the same team. Two formal reports summarizing the low
level design and the implementation of the project and an oral
presentation, including a demo, are required.
Credit units: 3, Prerequisite: CS 491.
Low-Level Design Report: {Due: 5pm, Monday, 3rd week of Spring semester}
The high-level design produced at the end of CS 491 course is refined
into the detailed low-level design document.
The report must be available on the web page of the project.
The following apply to software-oriented projects for the most part; for hardware projects, the tasks are somewhat different, and the contents of the report must be decided in consultation with the project advisor.
During analysis, we describe the purpose of the system. This results in the identification of application objects that represent user concepts. In system design, we describe the system in terms of its architecture, such as its subsystem decomposition, its global control flow, and its persistency management. During system design, we also define the hardware/software platform on which we build the system. This results in the selection of off-the-shelf components that provide a higher level of abstraction than the hardware. Through object design, we close the gap between the application objects and the off-the-shelf components by identifying additional solution objects and refining existing objects.
A sample way to organize low-level or object design document would be as follows:
1. Introduction 1.1 Object design trade-offs 1.2 Interface documentation guidelines 1.3 Definitions, acronyms, and abbreviations 1.4 References 2. Packages 3. Class Interfaces 4. GlossaryReference: Bernd Bruegge and Allen H. Dutoit, Object-Oriented Software Engineering, Prentice-Hall, 2000, ISBN: 0-13-489725-0.
Final Report: {Due: 5pm, Thursday, 13th week of Spring semester}
The final report is the culmination of the project.
The final architecture and design of your system as well as the final
status of the project is presented in this report. The report is to be
accompanied by the software/hardware system itself along with a User's
Manual including installation instructions.
Presentation and Demo: {Last week of Spring semester}
Students are to present their work at the end of Spring semester. They
are required to turn up on time and are properly prepared. Computer
projectors will be available if they want to use them. Each team will
have 25 minutes for their presentations.
It is strongly suggested that team members practice their talk at
least a couple of times beforehand, to ensure they can get the major
points across in the given time.
The team is required to dedicate 5-10 minutes of their time for a
demonstration of their project. Students may bring their own hardware or
use the PC available in room of presentation.
Return of materials {Due: 5pm last day of Spring Semester}
Students are required to return all materials which they may have
borrowed from their supervisor, including books, research papers,
notes, software, etc. by 5pm on the last day of the semester.
Additionally the supervisor may require copies of any software that
was developed as part of the project to be handed in at the same
time. Failure to do this may mean that graduation is delayed!
Grading
Total grade has three components:
The letter grades will be assigned according to the following table:
Range Grade 90-100 A 85-89 A- 80-84 B+ 75-79 B 70-74 B- 65-69 C+ 60-64 C 55-59 C- 50-54 D+ 45-49 D 0-44 F
Project Evaluation Form: Excel file, PDF file.