Final Exam Information

Stats:

MEDIAN 77
AVG 73.94

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 for a regrade. Slip your exam under Allison's office door (CSE 438). 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 a copy of your typed-in solution code so the instructor can 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 we 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. So it is possible that a regrade request will result in you receiving a lower mark than what you started with.
  • All final exam regrade requests must be submitted by 1/9/15.

Midterm Exam Information

Stats:

MEDIAN 34
AVG 32.58
CURVE 6

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 for a regrade. Slip your exam under Allison's office door (CSE 438) or give it to her after lecture. 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 a copy of your typed-in solution code so the instructor can 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 we 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. So it is possible that a regrade request will result in you receiving a lower mark than what you started with.
  • All final exam regrade requests must be submitted by 11/25/14.

Midterm Exam Information

Topics:

The exam will have approximately 3-4 questions about topics such as:

  • HTML/CSS interpretation (given a piece of HTML/CSS code, draw what it would look like in the browser)
  • HTML/CSS programming (given a screenshot of a page, write the HTML/CSS to recreate that appearance)
  • PHP (write PHP code to produce a certain web page often involving query parameters and/or file processing, may involve cookies or sessions)
  • SQL (write a query to find certain information in the world, simpsons, or imdb database)

The following topics are guaranteed NOT to be required to solve any problems on the final exam:

  • memorization of web-related jargon and terminology
  • basic internet/WWW info from Chapter 1
  • Javascript
  • how to insert/update/delete data from a database
  • how to design a database (book Appendix A)
  • object-oriented PHP
  • regular expressions

Resources:

You are permitted to bring and use any of the following resources on your final exam:

  • your course textbook (Web Programming Step by Step, second or first edition)
  • any other textbook related to web programming (HTML5 in a Nutshell, JavaScript for Dummies, etc.)
  • writing utensils, standard office supplies

You are not permitted to use any other resources on the final exam, such as:

  • practice exams or their solution keys
  • printed homework solutions
  • section/lab handouts
  • any other papers or documents
  • any electronic devices such as calculators, computers, mobile phones, tablets, laptops, music players

We realize that you may not be happy that the rules don't allow you to bring many resources. We will bring a small number of loaner copies of the textbook that you may be able to use during the exam. But there may be a waiting queue to use them, so you may want to have your own copy with you if you believe you will need it.

If you are found looking at a forbidden resource during the test, you will be penalized.

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 listed under 'Topics' above.

  • Your textbook has a helpful Appendix A that contains "cheat sheets" of the syntax of each language we have learned.
  • Some of the older practice exams have slight stylistic differences from how the course is taught today, because HTML and other languages have changed over time. For example, prior to HTML5 the initial <!DOCTYPE> tag was longer and contained more information. You can generally ignore these differences and assume that you should write your answers in the most modern style.
Valid HTML5 Valid CSS JavaScript Lint
This document and its content are copyright © Marty Stepp, 2013. All rights reserved. Any redistribution, reproduction, transmission, or storage of part or all of the contents in any form is prohibited without the author's expressed written permission.