NOTE: All exams on this page are now password-protected so that other instructors may use them. If you are an instructor using our materials, please email us to get the password to this area of the site.
Final Exam Info
Regrade Policy:
If you disagree with the grading, such as if you think your solution actually does work, or that your solution is more nearly correct than it was given credit for, the procedure for regrades is the following:
- If your complaint is about the correctness of your solution to a programming question, type in your code and view it in your browser. Fix any trivial syntax problems. Run it for yourself and see how nearly correct your solution is.
- Submit your exam to Marty for a regrade. Slide it under his office door, CSE 466. You must include a cover page with a brief written explanation of what specifically you think was misgraded and why. If your complaint is about overly harsh grading on a programming question, you should also email a copy of your typed-in code to Marty so that he can run it to verify its correctness. Marty will not accept any exam for a regrade unless it includes this cover page, and he will not re-evaluate grading of the correctess of any programming questions without a typed copy of your solution being emailed by you first.
- Also note: When you submit an exam for a regrade, Marty will regrade your entire exam. If he notices anywhere that you were mistakenly given too many points, he will also correct this, up to a maximum of -2 for the entire exam. So it is possible that a regrade request will result in you receiving a slightly lower mark than what you started with.
- All final exam regrade requests must be submitted to Marty by July 1.
Topics:
The exam will have approximately 5-6 questions about topics such as:
- HTML/CSS interpretation (given a piece of HTML/CSS code, what would it look like?)
- HTML/CSS programming (given a screenshot of a page, write the HTML/CSS to recreate that appearance)
- JavaScript/DOM/Prototype (given a description of a page's event-driven behavior, write the JavaScript code to implement that behavior)
- Ajax/XML (given a particular source of XML data, use Ajax to fetch and process the data)
- PHP (write PHP code to produce a certain web page or web service, often involving query parameters and/or file processing)
- SQL (write a query to find certain information in the
world
, simpsons
, or imdb
database)
- PHP+HTML+SQL (write PHP code to perform a SQL query and display its results in some way)
The following topics are guaranteed NOT to be tested on the final exam:
- basic internet/WWW info from Chapter 1
- regular expressions (you may use them, but no problem will require them)
- Scriptaculuous
- sessions and cookies
- web security
- object-oriented JavaScript/PHP
- how to design a database (book Appendix A)
- how to take a web site "live" (book Ch. 13)
Past Exams:
These practice tests are intended to give you a general idea of the kinds of questions you may see on the real exam. The real exam will have a similar number and general style of questions as on the practice tests. However, we do not promise that the real exam will exactly match the practice test in terms of questions, difficulty level, or exact concepts needed to solve each problem. You are responsible for knowing all class material covered in lecture/lab/homework.