Welcome To
AP Computer Science Principles
Embedded Files
UNIT OUTLINE
Quarter 1
Quarter 2
Quarter 3
Quarter 4
Unit 1 - Drawing
Build programs from scratch using variables, methods, conditionals, and loops.
Unit 3 - Big Ideas
Study topics like data, networking, and cybersecurity to prepare for the AP Exam.
Unit 5 - Objects
Learn about Object Oriented Programming to develop more flexible and interactive programs.
Unit 7 - Space Shooter
Your final project is designing an interactive "space shooter" style game
Unit 2 - Roboquest
Solve a series of puzzle-like challenges to help guide Karel the Robot to achieve various tasks
Unit 4 - Arrays
Build even more complex programs using collections of data
Unit 6 - Create
Complete your AP Performance Task by designing and coding a program of your own design.
HOMEWORK
Many of you will be able to complete your work in class, but the expectation is that sometimes you'll be doing work at home. This can include watching videos, doing readings, studying for tests, or finishing a project from class. To code at home, you'll need access to a computer running Windows or MacOS; your chromebook will not work for coding.
Make sure you have a system in place to code at home before the first time you need to do so. If you cannot secure access to a computer, please talk to me so we can make arrangements. If we haven't discussed it in advance, it won't be an excuse for late work. My lab is open after school on most Wednesdays for additional lab time and tutoring.
GRADING
In this course, we use TOTAL POINTS for grading, rather than categories like minor and major. This means you can easily calculate your grade at any moment. In the sections below, the percentages of your grade are just approximations; it will vary a bit each quarter.
PROJECTS
25%
CODE QUIZZES
25%
TESTS
50%
ETHOS
If you want to be a pianist, you'll spend much more time practicing on your own or with a teacher than you do giving performances.
In class, you'll be spending most of your time writing code, but your grades are based primarily on your tests. You will have tons of opportunity to build your skills.
In the end, you are graded on your actual demonstrated ability. This means it's really important for you to master the skills during projects, not just "turn them in."
LATE WORK
A late assignment has a 20% penalty.
Two weeks after the deadline, late work has a 50% penalty.
If you are absent during a class period, the work isn't late. You just turn it in the next time you are in class.
If you are absent the class before an assignment is due, you are still expected to make it up and have it ready on the due date. All projects are posted very far in advance.
CODING QUIZZES
FORMAT
Write program from a blank processing assignment
Short duration (~15 minutes)
Simpler versions of existing projects
In the middle of units, roughly 1-2 per quarter
REDO POLICY
For each assessment, the next day in class will be designated for make-ups (if absent) or redo (if you did poorly)
If you are not in school during the next class, or need to redo an exam you were intially absent for, you'll need to come after school on Wednesday during the next programming club.
Students may only attempt to redo an assessment once.
On a redo, you can recieve a maximum of an 80%. This isn't a 20% penalty, but simply a cap of 80%. So for example, if you earn a 87% on a redo, your grade is an 80%.
TESTS
TESTS
Taken on Schoology or AP Classroom
Longer duration (30-90 minutes)
Multiple Choice Format
Two per quarter
NO REDOS
Tests cannot be retaken, but all tests are cumulative so you'll have a chance to prove your skill on the next one.
PROTIPS
DON'T FALL BEHIND
The course is much easier if you stay on track or ahead of the lessons. Falling behind isn't directly penalized beyond small late penalties, but it rarely works out well. Things just build up, like a snow on a mountainside rolling into an avalanche. You'll find that the tests become more challenging and you'll have difficulty understanding the lectures. So if you are lost, get help early and catch up as soon as you can.
KNOW WHAT YOU ARE DOING
Your projects exist to help you learn. That's the whole point. Your code can't be magic - you need to understand how it works, and how to replicate it.
GETTING STUCK IS NORMAL
When you work on a project, you'll spend 80% of your time on the hardest 20% of the code. That's normal. You'll spend a lot of time frustrated and stuck on a problem. Working through that tough part is where the learning happens. You will need to learn to be patient, methodical, and tenacious to code.
DON'T RELY ON OTHERS
It's okay to get help from friends, myself, or a student intern, but you can't become reliant on others to do your work for you. Remember, you'll primarily be assessed on your work on quizzes and tests. You need to be able to do this stuff on your own.
Page updated
Google Sites
Report abuse