Computer Systems Project Proposal Checklist

1. A subject area that you are interested in and that you can write a program for.

2. The program should be able to be completed in certain levels of complexity.
   (The following are approximate measurements) -
   • 1st quarter: a preliminary program that works at a level analogous to a CS1 end of year project. For example - your program simulates a simple dialogue with another person, you talking to the computer person.
   • 2nd quarter: stage 2 of your program's evolution, you've expanded your program's complexity to work at an increased level of sophistication. Now your program's computer person seems to learn and adapt the conversation based on what you've been saying (inputting).
   • 3rd quarter: stage 3 of your program's evolution, further expansion of your program's sophistication and abilities.

3. You should be able to write down or describe exactly what your program's behavior may look like at each of these levels of development.

4. Areas for projects that are not recommended. Subject areas involving
   • violence - guns, shooting, blood, etc.
   • gambling scenarios - poker, casino gambling games
   • group projects - evaluating the work of individual group members is often "murky". Who is doing what? Who is writing up reports and documentation?
     Each member must have their own project proposal
   • Website programs - how can the website be evaluated? What are various levels of sophistication that are possible for this website. For example, what would the 1st quarter version look like, what would the 2nd quarter look like, and what would the 3rd quarter version look like.
     You'll need to have users of the website, large numbers of users, for example Intranet2 - the current student website.
   • others...