Final Exam

Exam Results

  • The final will not be "curved" - the scores received on the final will be your actual scores for this exam. The stats are:
    • Mean: 76.9
    • Median: 81.0
  • Note: Some of the exams were light in scanning. Be assured that we used the originals for grading. If you would like your originals back, you can get them from the front office of CSE1 starting Monday morning.

Regrade policy: Exams are graded collectively by the course staff - your TAs can not deal with specific exam grading issues.

  • For non-frivolous grading issues, you may submit a regrade request by Monday, June 17th, 12:00pm (noon). This is so we as a course staff can process the request in time to submit grades on Tuesday.
  • In order for your a regrade request to be considered you must:
    1. Understand the grading rubric: only the "checked" items are applied to you. Read all of the rubric items carefully to understand how the full rubric was applied to the problem in question.
    2. Initiate the regrade request through Gradescope.
    3. Explain concisely and clearly why you think your particular answer should be regraded.
    4. Test your solutions fully using the reference solution programs for Problems 2 and 3 (fountain-p2-p3.zip) and 4 and 5 (club154-p4-p5.zip).
  • Please note that regrade requests will result in the entire exam being re-examined, and may result in a lower score if we find other grading inconsistencies.

Final Exam Information

  • Date/Time: Monday June 10th, 2:30PM – 4:20PM
  • Location: GUG 220
  • Make note of your seat PRIOR to attending the exam. Here is the seating chart (same as it was for the midterm in GUG 220)

Details to be aware of "Day of" Exam:

  • The exam will start promptly at 2:30, and there will be a seating chart (coming soon), so please arrive by 2:20 so we can distribute exams and start on time.
  • If you arrive for the exam and find someone else in your seat, ask them to move/double-check their seat, and check with a TA/instructor if needed. Students are expected to make a reasonable effort to sit in their assigned seat. Students who demonstrate an egregious disregard for the seating assignments will receive a 5-point penalty.
  • We will distribute the exam early and you can read and fill out the cover page of the exam, but you should not open the exam until you are told to begin. At the end when time is called, you are required to stop writing and close your exam. Students who open the exam before being told to begin and students who make changes to their exam after time is called will receive a 10% penalty. Students who do not close their exam booklet when time is called may also receive a 10% penalty. Students that continue to write (anything) on their exam after time is called will receive a 10% penalty.
  • We will ask to check your UW ID card during the exam so please have it ready.
  • You must work alone and may not use any computing devices of any kind including calculators. Cell phones, music players, and other electronic devices may NOT be out during the exam for any reason.
  • The exam will be worth a total of 100 points.

Topics

The exam will have programming, "mechanical", and short answer questions related to material covered in readings, lectures, sections, labs, and HW throughout the quarter, with an emphasis on Modules 3, 4, and 5. While examples are not guaranteed to be the same format as the final this quarter, some types of problems that have been on previous midterms to help guide your studying include:

  • HTML/CSS
    • Writing CSS given HTML and screenshot/text specifications
    • Given HTML/CSS, sketch the result page appearance
    • CSS query selectors: identifying selectors for specified elements or identifying elements selected by a provided list of selectors (example)
  • JS programming: DOM manipulation, event listeners/handling, animation, etc.
  • JS programming: using AJAX/fetch from a PHP web service
    • Review Practice Final 1 and Practice Final 2 JS/fetch problems
  • PHP programming: Writing a web service with GET/POST parameters and text/JSON responses (usually includes basic file/directory processing)
    • Review Practice Final 1 and Practice Final 2 PHP web service problems
  • Writing SQL Queries
  • Using PDO with PHP and SQL
    • Review Practice Exam 2 SQL/PDO problem and Section 18 exercises
  • Various short answer, including:
    • basic understanding of regex
    • different storage technologies (e.g. local storage, cookies, databases, text files)
    • accessibility
    • tradeoffs between technologies
    • order of program excecution in JS and PHP

The following topics are guaranteed not to be included:

  • Memorization of web-related jargon and terminology
  • Git/Command Line Tools
  • JS frameworks or libraries
  • CSS animations
  • Python/Flask
  • SQL Joins (these were included in some previous exams)

Useful Study Resources

Practice Exams

These 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 general style of questions as on the practice tests. However, we do not promise that the real exam will exactly match the practice tests 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'.

Midterm Exam

Exam Results

NOTE: Your score on Canvas is your final score for the exam - remember that your score will only include the better of either 6A or 6B, but not both (Unfortunately Gradescope itself can’t account for this)

Regrade policy: Exams are graded collectively by the course staff - your TAs can not deal with specific exam grading issues.

  • For non-frivolous grading issues, you may submit a regrade request by Wednesday, May 15th, 11:00pm.
  • Regrade requests are to be initiated through Gradescope by attaching a short, clear note on the part of the exam that you think was graded incorrectly explaining why you would believe the question should be regraded.
  • Note: You are expected to test your solutions fully before submitting your regrade request.
  • Please note that a regrade requests will result in the entire exam being re-examined.

Midterm Exam Information

  • Date/Time: Friday May 3rd, 5:15PM – 6:30PM
  • Location: GUG 220
  • Make note of your seat PRIOR to attending the exam. Here is the seating chart for the midterm in GUG 220

Topics

The exam will have programming, "mechanical", and short answer questions related to material covered in readings, lectures, sections, labs, and HW up through Monday April 30th. While examples are not guaranteed to be the same format as the midterm this quarter, some types of problems that have been on previous midterms to help guide your studying include:

  • Writing HTML and/or CSS from screenshot/text specifications
    • See CSS Basics and Page Layout on CSBS for a number of practice problems
  • Identifying and fixing HTML/CSS/JS validation issues
    • Example: Problem 1 of Practice Midterms 1 and 2
  • CSS query selectors
    • Writing selectors for specified elements or identifying elements selected by a list of selectors) (example)
  • JS programming: DOM manipulation, event listeners/handling, timers, UI validation, etc.
    • (e.g. Section problems from Weeks 2 and 3, JavaScript probelms on practice midterms)
  • Short answer responses and "Mechanical/Mystery" including:
    • JS scoping/program execution (example)
    • JSON mystery (accessing keys/values) (example)
    • Understanding the DOM tree given HTML (see Practice Midterms 2 and 3)
    • General use of languages and technologies we have used in class (e.g. separation of languages, basic accessibility principles we have discussed, etc.) (you can find some short answer questions from practice exams)

Useful Study Resources

Practice Midterms

These 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 general style of questions as on the practice tests. However, we do not promise that the real exam will exactly match the practice tests in terms of questions, difficulty level, timing, or exact concepts needed to solve each problem. You are responsible for knowing all class material listed under 'Topics'.