Computers, networks, and safe habits
Students learn how computers, devices, and the internet actually work together. They practice troubleshooting common problems and build habits that keep their accounts and personal information safer online.
This is the stretch when students stop using technology and start building with it. Students write short programs that loop and make decisions, break bigger problems into smaller pieces, and test their work until it actually runs. Students also look at how the internet moves data around and what that means for privacy and online behavior. By spring, students can plan, code, and debug a small project and explain how it works to someone else.
Students learn how computers, devices, and the internet actually work together. They practice troubleshooting common problems and build habits that keep their accounts and personal information safer online.
Students gather information, clean it up, and turn it into charts and tables. They look for patterns and learn to back up what they say with evidence from the numbers.
Students write programs to solve problems and automate small tasks. They break big problems into smaller pieces, test their code, and fix what does not work.
Students design and build their own apps, games, or simulations in teams. They share ideas, give feedback, and improve their projects through several rounds of testing.
Students look at how technology shapes daily life, from social media to artificial intelligence. They weigh the benefits and the harms and think about who is helped or left out.
Students pick the right tools for a job, whether that means choosing an app, adjusting a device setting, or figuring out why something stopped working. The focus is on matching the hardware and software to what the task actually needs.
Students learn how the internet works as a system of connected computers that pass data back and forth. They explain how networks let people share files, send messages, and keep information secure while doing it.
Students gather raw information, organize it into charts or tables, and use software tools to spot patterns. Then they back up a claim with what the data actually shows.
Students write step-by-step instructions a computer can follow to solve a problem or automate a repetitive task, then test and improve those instructions until the program does what it should.
Students look at how technology shapes daily life, from privacy and online safety to who gets access and who doesn't. They consider the benefits and the problems that come with those choices.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 6-8 | Students pick the right tools for a job, whether that means choosing an app, adjusting a device setting, or figuring out why something stopped working. The focus is on matching the hardware and software to what the task actually needs. | OH-CSDF.C1.6-8 |
| Explain how computer networks and the Internet enable communication… Grades 6-8 | Students learn how the internet works as a system of connected computers that pass data back and forth. They explain how networks let people share files, send messages, and keep information secure while doing it. | OH-CSDF.C2.6-8 |
| Collect, transform, and represent data Grades 6-8 | Students gather raw information, organize it into charts or tables, and use software tools to spot patterns. Then they back up a claim with what the data actually shows. | OH-CSDF.C3.6-8 |
| Design, develop, and analyze algorithms and programs to solve problems… Grades 6-8 | Students write step-by-step instructions a computer can follow to solve a problem or automate a repetitive task, then test and improve those instructions until the program does what it should. | OH-CSDF.C4.6-8 |
| Investigate the social, ethical, legal Grades 6-8 | Students look at how technology shapes daily life, from privacy and online safety to who gets access and who doesn't. They consider the benefits and the problems that come with those choices. | OH-CSDF.C5.6-8 |
Students practice working with others who have different backgrounds and viewpoints to solve computing problems. The goal is making sure everyone feels like they belong in a tech class, not just some students.
Students work with others to plan, build, and improve a computing project. They split up the tasks, share ideas along the way, and use feedback from the group to make the final product better.
Students look at a real problem, decide whether a computer could help solve it, and then break it into smaller steps a program could actually handle.
Students take a complicated problem and strip it down to the parts that matter, then write a solution that works for more than one situation. This is the core of how programmers think.
Students write programs or build simulations by testing their work, finding what breaks, and revising until it does what they intended. The process repeats until the project works.
Students run planned tests on their programs or digital projects, find what breaks or confuses users, and fix it. The goal is a program that works correctly and is easy for someone else to use.
Students explain how a program, app, or algorithm works using the right words, diagrams, or data. The goal is a clear explanation someone else could follow, not just a vague description.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 6-8 | Students practice working with others who have different backgrounds and viewpoints to solve computing problems. The goal is making sure everyone feels like they belong in a tech class, not just some students. | OH-CSDF.P1.6-8 |
| Collaborate around computing — divide work, share ideas Grades 6-8 | Students work with others to plan, build, and improve a computing project. They split up the tasks, share ideas along the way, and use feedback from the group to make the final product better. | OH-CSDF.P2.6-8 |
| Identify and define problems that can be solved with computation and decompose… Grades 6-8 | Students look at a real problem, decide whether a computer could help solve it, and then break it into smaller steps a program could actually handle. | OH-CSDF.P3.6-8 |
| Use abstractions to simplify complexity, generalise solutions Grades 6-8 | Students take a complicated problem and strip it down to the parts that matter, then write a solution that works for more than one situation. This is the core of how programmers think. | OH-CSDF.P4.6-8 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 6-8 | Students write programs or build simulations by testing their work, finding what breaks, and revising until it does what they intended. The process repeats until the project works. | OH-CSDF.P5.6-8 |
| Systematically test computational artifacts and refine them based on evidence… Grades 6-8 | Students run planned tests on their programs or digital projects, find what breaks or confuses users, and fix it. The goal is a program that works correctly and is easy for someone else to use. | OH-CSDF.P6.6-8 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 6-8 | Students explain how a program, app, or algorithm works using the right words, diagrams, or data. The goal is a clear explanation someone else could follow, not just a vague description. | OH-CSDF.P7.6-8 |
Students learn how computers and networks work, how to write simple programs, and how to handle data. They also look at how technology affects people and society, including questions about privacy, online safety, and fair use of information.
No. Most students start middle school with very different experience levels. Teachers begin with the basics of breaking a problem into steps, and students build up to writing small programs over the year. Curiosity matters more than prior coding.
Ask students to explain what their program is supposed to do and where it is getting stuck. Talking through the steps out loud is half the work. Free sites like Scratch, Code.org, and Khan Academy give short projects that take 10 to 20 minutes.
A common path starts with hardware, networks, and digital citizenship in the fall, moves into data and basic programming in the winter, and finishes with a larger project in the spring that pulls everything together. Revisit ethics and impact throughout, not just as one unit.
Decomposition and debugging. Students often try to write a whole program at once instead of breaking it into small pieces and testing as they go. Build in short debugging routines early so students get used to reading errors and tracing code line by line.
Students should be able to plan and write a working program with loops, conditionals, and variables, collect and chart a small set of data, and explain how the internet moves information between devices. They should also be able to talk about the impact of a technology choice on real people.
Most practice can be done in 15 to 30 minutes a few times a week. Coding projects do not have to be long to be useful. Short, focused sessions where students finish one small feature work better than long stretches of frustration.
Grade the process, not just the finished product. Look at how students planned the problem, how they tested and revised, and how they explain their code. A short code walkthrough or written reflection often shows more than the program itself.
Students look at real situations: sharing passwords, copying code or images, AI-generated work, and how data gets collected online. The goal is for students to think before they click and to explain the tradeoffs of a choice, not just memorize rules.