Final Exam Info
| ||raw ||curved ||% of class|
|MEDIAN ||74 || |
|AVG ||71.4 || |
|STDEV ||14.1 || |
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. We have posted solutions to every exercise that you can use to type in your own code to see whether it works. These are found within the Final Exam Answer Key document.
- Submit your exam for a regrade. Slide it under Marty Stepp's office door, CSE 636. 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 the instructor (or post on Webster, and give us the URL) a copy of your typed-in solution code to the instructor to run it to verify its correctness. Because regrades are time-consuming and difficult to judge, we can 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 submitted by you first.
- Also note: When you submit an exam for a regrade, we will regrade your entire exam. If we notice anywhere that you were mistakenly given too many points, we 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.
- We will not accept any regrade requests where the reason for regrading is essentially, "The grader didn't see my answer that was written on (the back side of the page / my scratch paper / elsewhere on the page)." Because it is too easy to add answers to these places after the exam, unfortunately we must trust that the grader was able to find all of your work and grade it appropriately. If this was not the case, we must assume that you did not sufficiently clearly label where the grader was supposed to look to find your work, and therefore that you are responsible for any such grading mistake.
- All final exam regrade requests must be submitted by the end of the first week of Autumn 2011 quarter.
The exam will have approximately 7 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)
- 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
- 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)
- sessions and cookies
- web security
- how to design a database (book Appendix A)
- how to take a web site "live" (book Ch. 13)
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.
- You may want to print out the "cheat sheets" found at the top of the Homework page to use as references during your exam. You can also bring your textbook.