On This Page
Overview
The purpose of the project is to use most of the techniques you have learned from this course. The finished project is a web site utilizing JavaScript and PHP. You may choose any project as long as it meets the requirements discussed below.
The project must be a real application in the sense that the site must be hosted somewhere on the Internet. You can either arrange your own hosting or use WebHawks. For more information on using WebHawks, see: How To Use WebHawks
You are free to apply homework assignments toward the final project. However, the final project must be work that you have produced and not material simply copied from another source. If you do copy small portions from another source, you must cite the source and have permission to copy the material.
The final project presentation will count as the final exam for the course. You must demonstrate your completed project to the instructor during the scheduled final exam time.
^ top
Project Requirements
As a JavaScript and PHP project, your project must meet these requirements:
- At least one function embedded in an HTML page (either the head section or the body section) (2)
- At least one function in an external JavaScript (
*.js) file (2)
- At least one array (2)
- At least one use of all these control structures:
while or do-while loop (1)
for loop (1)
if or if-else (1)
- At least one use of all the following event handlers:
onload (1)
onclick (1)
onmouseover (1)
onmouseout (1)
onsubmit (1)
- At least one
Date object method call (1)
- At least one
Math object method call (1)
- At least one page displaying animation using JavaScript (5)
- At least one page with a JavaScript rollover menu using images (3)
- At least one form field validated on the client using JavaScript (5)
- At least one regular expression (2)
- At least one cookie that gets saved and retrieved (5)
- A project report as described below (4)
- All your Web site pages must function correctly as described in Project Evaluation Criteria section below (10)
You may NOT use any third-party libraries or frameworks without permission in writing from the instructor.
^ top
Project Report
The project report consists of the following information.
- Your name
- You project's name
- A brief introduction describing the purpose of your project
- One paragraph is sufficient
- The URL entry point for your project on the Internet
- A description of each page of your project Web site including:
- Your JavaScript animation page, including a description of the animation
- Your form validation page, describing valid and invalid values
- Your cookie setting and retrieval pages, including values that are set and retrieved
In addition, you should explain any unusual coding (that we did not cover in class) used to meet the specifications. If you do not, then I may miss how you achieved some specification and you will not get the credit you deserve.
Also, if your site is password protected in some way, please provide me a way to login such as a guest username and password.
You can see an example report at: READMEproj.txt. As you can see, the report can be as short as 1-2 pages.
^ top
Project Presentation
- You must demonstrate your project on the day of the final.
- You must attend at the scheduled time or you will receive a zero (0) and fail the course
- Except by prior arrangement with the instructor
- While you must present your project, you do not have to demonstrate it in front of the class
- When everyone else is done, you can present it to the instructor individually
Suggested Presentation Flow
- State your name and your project's name.
- Briefly describe the purpose of your project
- Demonstrate and discuss each project page including:
- Animation page
- Form page and validation techniques used
- Cookie pages and cookie values set and retrieved
Feel free to refer to or display your written report during the presentation.Point out as many of the cool features as possible so we can all enjoy them.
- Summarize the project.
When the demonstration is over, or your time is up, then quickly summarize the program's purpose. Then pause for about 10 seconds to give us a chance to applaud!
^ top
Project Evaluation Criteria
The instructor will evaluate your final project using the following criteria. Each criteria represents a specific achievement of your project and has a scoring guide. The scoring guide explains the possible scores you can receive.
Some scoring guides have a list of indicators. These indicators are a sign of meeting, or a symptom of not meeting, the specific criterion. Note that a single indicator may not always be reliable or appropriate in a given context. However, as a group, they show the condition of meeting the criterion.
For information on grading policies, including interpretation of scores, see the course information page.
Required Features
Points as shown in parentheses for each demonstrated feature in the specifications. (50 points, including the Web Site Functionality and Project Reporting and Presentation points described below)
Web Site Functionality
- 10: Demonstrates mastery of a Web site using JavaScript:
- Has extra features or demonstrates techniques beyond the course
- Meets all project requirements (see above) with particularly elegant solutions
- Runs with no error conditions reported by the browser
- 8: Has all the functionality expected of a professional Web site using JavaScript:
- Demonstrates many techniques from the course
- Meets all project requirements (see above)
- Runs with no error conditions reported by the browser
- May have one minor error in the JavaScript on a page
- 6: Has most of the functionality expected of a Web site using JavaScript:
- Demonstrates some techniques from the course
- Meets all but one of the project requirements (see above)
- May have 2-3 minor errors
- Project not available on the Internet
- 4: Has some of the functionality expected of a Web site using JavaScript:
- Demonstrates some techniques from the course
- Meets at least 1/2 of the project requirements (see above)
- Implementation seems excessively complicated.
- May have JavaScript warnings or errors in the browser
- 2: Serious functional problems but shows some effort and understanding:
- Meets at least 1/2 of the of the functional requirements (see above)
- Has a major error (detected by the browser) or many minor errors
- Demonstrates few techniques from the course
- 0: Web site does not run or was not presented by the specified time
Project Reporting and Presentation
- 4: Project is reported clearly and completely:
- Student presents information in a logical and interesting sequence
- All requirements of the project were presented
- Written report was presented to instructor before the project was presented
- All project-reporting requirements were turned in
- Report is well-written and grammatically correct
- 3: Project presentation or report has minor problems:
- Student presents information in a logical sequence
- All but one of the project requirements were presented
- Some minor project-reporting requirements are missing
- Report contains spelling errors, but is otherwise clearly written
- 2: Project presentation or report has significant problems:
- Audience has difficulty following presentation because student jumps around
- At least 1/2 of the project requirements were presented
- At least 1/2 of the project-reporting requirements were turned in
- Report only submitted electronically and without a paper copy
- 1: Project presentation or report is unclear or incomplete:
- Audience cannot understand presentation because there is no logical sequence of information
- Less than 1/2 of the project requirements were presented
- Less than 1/2 of the project report was completed
- 0: No project report submitted or was not presented at the specified time
Maximum Score: 50
^ top
What to Turn In
Bring a written copy of the project report to class.
Before the presentation, submit to WebCT a .zip file with all your files placed in their correct directories. Include the following:
- The written report document as README.txt
- All JavaScript, HTML, CSS and image files
- Any other file needed to make your project work
You must submit all the files needed for your project to work properly. Do not assume that the instructors has any files. Your project must work as submitted.
^ top
Adding Your Project to the Hall of Fame
You decide whether or not to add your project to the Hall of Fame. To do so, you need to tell the instructor that it is OK in your README.txt file. For example:
Want Fame? You have my permission to publish my project in the Hall of Fame.
If you change your mind later, then email the instructor.
Also, please note the following:
- You should have a valid URL for your project so that people can look around and see what you did
- WebHawk sites are removed at the end of the quarter and thus cannot be used as the web address in the Hall of Fame
- The instructor will occasionally test the supplied URLs and remove those that are no longer working
- If a user needs to login to access your site, you need to provide a way to register or provide a guest login and password
^ top
Home
| Blackboard
| Announcements
| Schedule
| Room Policies
| Course Info
Help
| FAQ's
| HowTo's
| Links
Last Updated: December 26 2007 @17:43:20
|