Project Description: The senior project is a semester long project to be done individually or in a group of no more than three classmates. The goal of the project is to investigate, design, implement and test a significant software project. The project will be presented to your classmates, the department, and representatives of the industrial community. The project should solve a significant and complex problem, dealing with constraints and trade-offs in the solution. The project should bring together and interconnect the application of several subject areas. The project must be testable.

Projects must be approved by the instructor. When approving the project, the instructor will consider issues such as size and complexity, true design activity, availability of facilities, and adequate student preparation of the project. In order to assure an interconnection of several subject areas, at least three areas of computer science must be present. Area include, but are not limited to: algorithms and data structures, programming languages, computer architecture, numeric and symbolic computation, operating systems, software methodology and engineering, databases and information retrieval, artificial intelligence and robotics, and human-computer interaction.

Projects must have a customer who will provide a description of software that will be useful. The customer will sign-off on the specifications and the final product. The customer may be a faculty member, staff, or administrator at the college or a professional.

A list of some possible project areas follow. These may help you to decide who you would like to approach as a potential customer and what you might offer to do for them.

1. Database Management System
2. Text Editor
3. Word Processor
4. Language Design
5. Compiler
6. Interpreter
7. Virtual/Simulated Computer
8. Neural Computing Network
9. Operating System (Kernel, Shell, etc.)
10. Mathematical Modelling
11. Management Information System (Payroll, etc.)
12. Vehicle Simulation
13. Network Operating System
14. Machine Vision
15. Graphical User Interface
16. Computer Aided Software Engineering (CASE) Tools
17. Video Game
18. Computer Chess
19. Personal Calendar/Electronic Diary
20. Programming Tools
21. Computer Network Simulation
22. Real-Time Process Simulation/Control
23. Spelling Checker
24. Touch-Tone Student Registration/Grade System
25. Personal Finances Management
26. Automatic Bank Teller
27. Accounts Receivable/Payable
28. Manufacturing Process Simulation
29. Object-Oriented Design Tools
30. Mutiprocessor/Parallel Simulation
31. Optimization Tools

• Dr. Sabin is interested in the creation of a database to store alumni contact information. This project would include creating the database and a web-based user information for data entry and retrieval.
• Dr. Eastman is interested in having the pioneer robot programmed so that it can give someone a tour of the department and perhaps guide someone to their destination.
• Dr. Glenn is interested in the development of a client/server system that allows users to play solitaire Yahtzee and records a play-by-play account of the game (what dice were rolled, which were chosen to reroll, etc.). The recorded information would then be used to answer queries of the form "what did human players do in situations like ___". (Yahtzee could be replaced by any similar game.)
• Dr. Binkley has several interests including the development of an applet that would administer a user study, software that would gather dependence metric values over a program, and the distribution of subclass objects created in a program and the distribution of functions called through indirect function pointers by gathering dynamic data and analyzing it with some nice graphs and stats, etc. to see what the distributions looked line.

Policies: Deadlines will be strictly enforced. Papers will be due at the beginning of the class period on the due date. A late penalty of 10% for each 24 period a docement is late will be used. Presentation must be presented when the presenters are called. If the presenter is abscent (and has not arranged an alternative time prior to the class) or is not ready, the presenter will recieve a grade of zero for that presentation.

Description	Assign Date	Due Date	Portion of Project Grade
Requirements Specification Documentation	9/8/2008	9/24/2008	13%
Planning Documentation	9/24/2008	10/15/2008	10%
Design Documentation	10/15/2008	10/29/2008	12%
Test Plan Documentation	10/29/2008	12/3/2008	10%
Final Presentation and Demonstration		12/19/2008	15%
Final Project Document	12/3/2008	12/19/2008	40%