Computers, networks, and safe use
Students start the year learning how the machines and networks they use every day actually work. They troubleshoot common problems and practice keeping accounts, devices, and personal data safe.
What does a student learn in
This is the year computer work shifts from using tools to building them. Students write real programs that solve problems, break big tasks into smaller steps, and test their code until it works. They look at how data, networks, and apps shape daily life, and weigh the trade-offs in privacy, fairness, and access. By spring, students can plan, code, and explain a working program that does something useful.
- Programming
- Algorithms
- Data and patterns
- Networks and the internet
- Ethics in technology
- Problem solving
- Testing and debugging
Year at a glance
How the year usually goes. Every school and district set their own curriculum, so treat this as a guide, not official pacing.
- 1
- 2
Thinking like a programmer
Students take a real problem and break it into smaller steps a computer can handle. They write and test code, fix what does not work, and build up the habits behind any programming language.
- 3
Working with data
Students gather data, clean it up, and put it into charts that show a pattern worth talking about. They use the numbers to back up a claim instead of guessing.
- 4
Building a real project
Students work in teams to design something that solves a problem they picked. They plan together, split the work, test with real users, and revise based on feedback.
- 5
Computing in the wider world
Students step back and look at how technology shapes jobs, privacy, fairness, and daily life. They weigh trade-offs and present their thinking with clear reasoning and examples.
Mastery Learning Standards
The required skills a student should display by the end of Grade 9.
Concepts
Concepts
- High School
Identify, select, and apply hardware, software
Students choose the right hardware and software for a given task, then work through a fix when something breaks. The focus is on matching tools to the job and solving problems when the technology stops cooperating.
- High School
Explain how computer networks and the Internet enable communication…
Networks and the Internet let computers share information with each other across the world. Students explain how that system works, including how data travels securely and how it makes communication and collaboration possible.
- High School
Collect, transform, and represent data
Students gather raw data, clean or reorganize it, and use software tools to spot patterns. Then they back up a claim with what the data actually shows.
- High School
Design, develop, and analyze algorithms and programs to solve problems…
Students write and test programs that solve real problems or automate repetitive work. They also study how those programs behave to figure out what's working and what isn't.
- High School
Investigate the social, ethical, legal
Students examine how technology shapes everyday life, from privacy and data use to laws and global access. They think through the real consequences of digital tools on people, communities, and society.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software High School | Students choose the right hardware and software for a given task, then work through a fix when something breaks. The focus is on matching tools to the job and solving problems when the technology stops cooperating. | OH-CSDF.C1.9-12 |
| Explain how computer networks and the Internet enable communication… High School | Networks and the Internet let computers share information with each other across the world. Students explain how that system works, including how data travels securely and how it makes communication and collaboration possible. | OH-CSDF.C2.9-12 |
| Collect, transform, and represent data High School | Students gather raw data, clean or reorganize it, and use software tools to spot patterns. Then they back up a claim with what the data actually shows. | OH-CSDF.C3.9-12 |
| Design, develop, and analyze algorithms and programs to solve problems… High School | Students write and test programs that solve real problems or automate repetitive work. They also study how those programs behave to figure out what's working and what isn't. | OH-CSDF.C4.9-12 |
| Investigate the social, ethical, legal High School | Students examine how technology shapes everyday life, from privacy and data use to laws and global access. They think through the real consequences of digital tools on people, communities, and society. | OH-CSDF.C5.9-12 |
Practices
Practices
- High School
Foster an inclusive computing culture that values diverse perspectives and…
Students learn to build computing spaces where people with different backgrounds and experiences are included and heard. That means working with a range of people and making sure no one is left out of the collaboration.
- High School
Collaborate around computing — divide work, share ideas
Students work together to build a program or digital project: splitting up tasks, sharing ideas, and folding in feedback until the final product reflects the whole group's thinking.
- High School
Identify and define problems that can be solved with computation and decompose…
Students take a real-world problem, decide whether a computer could help solve it, and break it into smaller pieces that are easier to tackle one at a time.
- High School
Use abstractions to simplify complexity, generalise solutions
Students take a complicated program or system and find the patterns that make it easier to describe, reuse, or explain. Instead of rewriting the same logic repeatedly, they build general solutions that work across many situations.
- High School
Create computational artifacts — programs, simulations, models — by applying…
Students write programs or build simulations by testing, adjusting, and testing again until the work does what they want. The process is a loop, not a straight line.
- High School
Systematically test computational artifacts and refine them based on evidence…
Students run tests on programs or apps they've built, look at what breaks or confuses users, and fix those problems. The goal is a program that actually works the way it's supposed to.
- High School
Communicate clearly with appropriate vocabulary, visualizations
Students explain how a program or algorithm works using plain language, labeled diagrams, or real data. The goal is clear enough that someone outside the class can follow what the program does and why it matters.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… High School | Students learn to build computing spaces where people with different backgrounds and experiences are included and heard. That means working with a range of people and making sure no one is left out of the collaboration. | OH-CSDF.P1.9-12 |
| Collaborate around computing — divide work, share ideas High School | Students work together to build a program or digital project: splitting up tasks, sharing ideas, and folding in feedback until the final product reflects the whole group's thinking. | OH-CSDF.P2.9-12 |
| Identify and define problems that can be solved with computation and decompose… High School | Students take a real-world problem, decide whether a computer could help solve it, and break it into smaller pieces that are easier to tackle one at a time. | OH-CSDF.P3.9-12 |
| Use abstractions to simplify complexity, generalise solutions High School | Students take a complicated program or system and find the patterns that make it easier to describe, reuse, or explain. Instead of rewriting the same logic repeatedly, they build general solutions that work across many situations. | OH-CSDF.P4.9-12 |
| Create computational artifacts — programs, simulations, models — by applying… High School | Students write programs or build simulations by testing, adjusting, and testing again until the work does what they want. The process is a loop, not a straight line. | OH-CSDF.P5.9-12 |
| Systematically test computational artifacts and refine them based on evidence… High School | Students run tests on programs or apps they've built, look at what breaks or confuses users, and fix those problems. The goal is a program that actually works the way it's supposed to. | OH-CSDF.P6.9-12 |
| Communicate clearly with appropriate vocabulary, visualizations High School | Students explain how a program or algorithm works using plain language, labeled diagrams, or real data. The goal is clear enough that someone outside the class can follow what the program does and why it matters. | OH-CSDF.P7.9-12 |
Common Questions
What does a high school computer science year usually cover?
Students learn how computers and networks work, how to write programs that solve problems, and how to work with data. They also look at the bigger picture: how technology affects people, jobs, privacy, and fairness.
My teen has never coded before. Is that a problem?
No. Most courses start from the basics and build up. Encourage steady practice over big bursts. Twenty minutes a few nights a week beats a long weekend session.
How can I help at home if I don't know how to code?
Ask students to explain what their program is supposed to do and where it broke. Talking through the problem out loud is half the work. Free sites like Code.org and Khan Academy give short practice problems if extra reps are needed.
What does mastery look like by the end of the year?
Students should be able to take a real problem, break it into smaller pieces, write a working program, test it, and explain their choices. They should also be able to discuss tradeoffs around privacy, security, and the impact of a tool on different users.
How should I sequence the year?
Start with small programs and problem decomposition so students get early wins. Layer in data work and networks once they can read and trace code. Save the heavier ethics and impact discussions for after students have built enough artifacts to ground the conversation in real examples.
Which skills usually need the most reteaching?
Debugging and testing. Many students treat a program as done the moment it runs once. Building a habit of testing edge cases and reading error messages carefully pays off across every later unit.
Does my student need a special computer at home?
No. A basic laptop or Chromebook with a browser is enough for most coursework. Many tools run online, so a steady internet connection matters more than a powerful machine.
How much group work should I plan for?
A fair amount. Pair programming and small project teams are part of the practices students are expected to develop. Build in clear roles and short check-ins so one student doesn't end up doing all the typing while the other watches.
How do I know my student is ready for the next course?
They can write a program of around 50 to 100 lines on their own, find and fix their own bugs, and talk about what their code does in plain language. Comfort with loops, variables, and functions is the clearest signal.