CS 70

Final Proficiency Check Retries for All Groups

If you received a “not demonstrated” for any of this semester's CS 70 proficiency checks, you may retake them here for the final time.

You can remind yourself of the learning objectives for these proficiency checks (especially the ones that you got wrong the first or second time) here:

When you feel you're ready to retake the proficiency checks, click the links below to go to Gradescope. Once you begin each proficiency check, you must complete it in one sitting and you may not refer to this webpage or any other resources (see the rules and reminders below).

  • Group 0: Course Policies
    • PC 0A — Late Work
    • PC 0B — Proficiency Checks
    • PC 0C — Academic Honesty
    • PC 0D — Getting Help
  • Group 1: Numeric Types and Memory Models
    • PC1A — Memory Diagrams
    • PC1B — Numeric Types Fundamentals
    • PC1C — Promotion and Conversion
    • PC1D — Using Numeric Types
  • Group 2: Statically Sized Arrays of Primitives
    • PC 2A — Array Definition
    • PC 2B — Array Characteristics
    • PC 2C — Use Arrays
    • PC 2D — Array Errors
  • Group 3: Compilation
    • PC 3A — Compilation Stages
    • PC 3B — Compilation Commands
    • PC 3C — Program Organization
    • PC 3D — #include Guards
  • Group 4: References and Pointers
  • Group 5: Object Lifetime
    • PC 5A — Model Objects
    • PC 5B — Lifetime Timing
    • PC 5C — Pointers to Classes
    • PC 5D — Constructors and Destructors
  • Group 6: Iterators
    • PC 6A — Iterator Definition
    • PC 6B — Using Iterators
    • PC 6C — Iterator Interface
    • PC 6D — Invalid Iterators
  • Group 7: Complexity
    • PC 7A — Measuring Cost
    • PC 7B — Asymptotic Complexity
    • PC 7C — Complexity Analyses
    • PC 7D — Amortized Bounds
  • Group 8: Trees
    • PC 8A — Binary Search Trees
    • PC 8B — Random and Randomized Trees
    • PC 8C — 2–3–4 and Red–Black Trees
    • PC 8D — BST Complexity
  • Group 9: Hash Tables
    • PC 9A — Hash Functions
    • PC 9B — Hash Table Operations
    • PC 9C — Collision Resolution Strategies
    • PC 9D — Hash Table Complexity
  • Group 10: Concluding Topics
    • PC 10A — Heaps and Priority Queues
    • PC 10B — Inheritance and Subtype Polymorphism
    • PC 10C — User-Defined Type Conversion
    • PC 10D — Choosing Data Structures

Completing the Proficiency Checks

We have written these proficiency checks to be short (~5 minutes each), but there is no (real) time limit. Gradescope has a time limit of two hours per check, but that limit is there so that you will get a splash screen to confirm that you're ready to start the check—we do not expect you to use that much time!

However, you must start and end each proficiency check in a single sitting without interruption by other activities that would expose you to another person. No email, checking your phone, going to the dining hall, etc. Eating, resting, stretching, and other activities are encouraged if it helps you do your best!

Once you open a proficiency check assignment in Gradescope, your session has started. You may not leave and come back to it at a different time. So be sure not to open it until you're ready to complete it!

Grading

Each proficiency check will be graded either “demonstrated” or “not demonstrated” to indicate whether you have met expectations for that topic. If you have not passed a check, that means we all have more work to do! That's an indication that you should study that topic more intensely and take advantage of office/grutoring hours to fill any gaps in your understanding.

We believe that grading should reflect and reward learning and growth, so your first proficiency check is not your only chance to prove your proficiency. You will have two additional opportunities to demonstrate proficiency in this topic by answering different questions:

  • A second try later in the semester (see the Schedule)
  • A third try during final exam week

Resources

You may not use any resources while you are completing this assignment, including course webpages, textbooks, your own notes, a compiler, Internet resources, and so on.

A Note on Academic Integrity

We believe that these untimed proficiency checks, which you are allowed to take at any point during the week, allow each student to best demonstrate their learning through frequent, low-stakes assessment at the time that works best for them. This flexibility is only possible if we all truly commit to meeting our community's academic-integrity expectations. You may study for this proficiency check with other people in the class. You must complete this proficiency check on your own. You cannot share or distribute this proficiency check with anyone. You cannot discuss the check question(s) with anyone in the class until after the due date (including the optional late day). You can never discuss the exam with anyone who is not in CS 70. You cannot use resources (e.g., notes, a computer) not explicitly described above.

If you have any questions about the rules, ask before you start the proficiency check.

Failure to report a violation will be considered the same as if you had committed a violation yourself. All academic dishonesty cases will be referred to, and will follow the procedures of, your home campus.

(When logged in, completion status appears here.)