 |
|
|
|
|
|
|
||
|
|
||||||
Overview. For this part of the project, you are to develop the final version of the web site for your client. You must have final graphics, elements and functionality for all of the pages on your site.
All pages must conform to your specifications. I will compare your pages to your specification document to ensure that the pages meet the specifications.
You must meet with your client at least once. You are responsible for arranging the meeting. The meeting must be to examine and test the web site that you have developed. The client must give her/his final approval to the site.
Documents. For this part of the project you must produce the final web pages based on your specifications. I must be able to look at a feature on the web page and trace it back to a specification and then back to the planning chart item that it relates to.
Your document must have a cover page that contains the name of the project, the contact person for the project and the your names. You must include all past projects in the packet that you turn in. This means planning charts, flow charts and specifications. All documents must be completely updated to reflect your final web site.
You must include hard copies of all significant scripts (both javascript and perl) that you use in your web site. You do not need to include html pages that contain no scripts.
You must include a 1-2 page write-up describing what scripts you used on both the client side and server side. You should highlight any scripts that you believe were innovative or complicated.
You must include a page signed and dated by both you and the client and turned in to me by the due date that indicates your client's final approval of your web site.
In addition to the above documents, each person on the team must turn in a write up that describes what they did on the project, what percentage of the project they believe that they personally completed, what percentage of the project each other member of the team did, what grade they believe the team should receive for the project and what grade they believe each member of the project (including themselves) deserve. This page is not part of the project write up, but will be handed in individually to me.
Grading. Grades for the final project will be based on the items given below.
Accuracy of the implemementation. I will evaluate how closely the web pages correspond to the specifications, flow charts, and planning charts. There must be no major features in the web site that are not reflected on the documents (and vice versa).
Amount of client-side scripting. The more useful scripting that you have in the web site the higher your grade. Of course the amount of scripting is ultimately determined by the client, but you can always add client-side scripting for rollovers, pop-up menus, etc. You will not recieve above a "C" grade if there is no scripting in your site. To receive a "C" grade, you must use client-side scripts in at least 4 different places for 4 different purposes. If you use client-side scripting to provide rollovers on 4 different pages, for example, that will count as 1 script. More scripting will garner higher grades.
Amount of server-side scripting. The web site that you submit to me to grade must have server-side scripting (i.e., cgi scripts) included. I understand that you may not deliver these scripts to the client due to various administrative constraints. There must be at least one cgi script used in the site. In general, the more constructive server-side scripting (or the more sophisticated), the higher your grade for the project. To receive a "C" grade you must have a single significant server-side script. More scripting will garner higher grades.
|
|
Last updated on
05 Dec 2008
by
John
Barr
|
 |