CSC220 Project Specifications 2010

From CSclasswiki
Jump to: navigation, search

--Thiebaut 14:21, 22 November 2010 (UTC)


FireFlyTrail.jpg




Specifications

The list below provides specifications, advice, and requirements for the CSC220 Project. It is a continually evolving list, so make sure to visit this page often.

  • Your final project code should use the 220a_project database. Feel free to use your own database when testing, but the final version should work with the 220a_database. Do not wait until the last minute to make the switch!
  • Document all your files. A program should be documented well enough for somebody to understand what it does and adapt it to another environment. If a README file is required for additional information, then make it part of your project.
  • Everybody in the class should have a working version of the project (whatever that version is supposed to do) in his/her 220a-xx account. This applies to members of large teams.
  • Projects should be easily migrated from one account to another, or from one computer to another, assuming that computer has a similar java and php environment.
  • If your project requires special features from the server it runs on, document it well (one of the teams requires the ability for Php to include remote php files specified by a URL, for example).
  • There should be one wiki page per team, explaining how their project operates. This wiki page should have a section that covers background material, i.e. information about projects or research similar to what you are accomplishing in your project. You should explain how your project differs from the research you found and are reporting on your page.
    • Every new page created for the team wiki should have a name starting with "CSC220"
    • Every new page created for the team wiki should have the following lines at the bottom of the page:
<br />
<br />
<br />
<br />
<br />
[[Category: CSC220]][[Category: Classes]]
  • It should be clear from your wiki and from your program for somebody to adapt your code to a different map (different campus, different town, etc.)

Regular Meetings

  • I will meet once a week with each team to check on progress performed during the week.