Computers, tools, and safe habits
Students learn the parts of a computer and how to pick the right tool for a task. They practice basic troubleshooting and the habits that keep accounts and personal information safe.
This is the stretch when students stop just using computers and start thinking like the people who build them. Students break a problem into smaller steps, write simple programs that loop and make decisions, and fix the bugs when something goes wrong. They also learn how the internet moves information around, why passwords matter, and what counts as fair use online. By spring, they can plan, code, and test a small project that solves a problem they picked themselves.
Students learn the parts of a computer and how to pick the right tool for a task. They practice basic troubleshooting and the habits that keep accounts and personal information safe.
Students learn how devices talk to each other across the Internet. They look at how messages travel, how to collaborate online, and what makes a password or a website trustworthy.
Students gather information, sort it into tables and charts, and look for patterns. They practice backing up an idea with what the numbers actually show.
Students write step-by-step instructions to make a program do what they want. They break a big problem into smaller pieces, test their code, and fix what is not working.
Students look at how technology shapes daily life, who it helps, and who gets left out. They talk through fairness, credit for other people's work, and the choices behind the apps they use.
Students learn which hardware and software tools fit a given task, then practice basic troubleshooting when something goes wrong. Think choosing the right app for a project or restarting a device that freezes.
Students learn how computers connect to each other through networks and the internet to send messages, share files, and keep information private. Think of it as the invisible wiring that lets devices talk to each other across a classroom or across the world.
Students gather information, organize it into charts or graphs, and use those visuals to spot patterns and explain what the data shows.
Students write step-by-step instructions a computer can follow to solve a problem or make something new, then check whether those instructions actually work.
Students look at how computers and apps affect real people's lives, from privacy and fairness to rules about what's allowed online. They think through both the good and the problems that come with living in a digital world.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 3-5 | Students learn which hardware and software tools fit a given task, then practice basic troubleshooting when something goes wrong. Think choosing the right app for a project or restarting a device that freezes. | OH-CSDF.C1.3-5 |
| Explain how computer networks and the Internet enable communication… Grades 3-5 | Students learn how computers connect to each other through networks and the internet to send messages, share files, and keep information private. Think of it as the invisible wiring that lets devices talk to each other across a classroom or across the world. | OH-CSDF.C2.3-5 |
| Collect, transform, and represent data Grades 3-5 | Students gather information, organize it into charts or graphs, and use those visuals to spot patterns and explain what the data shows. | OH-CSDF.C3.3-5 |
| Design, develop, and analyze algorithms and programs to solve problems… Grades 3-5 | Students write step-by-step instructions a computer can follow to solve a problem or make something new, then check whether those instructions actually work. | OH-CSDF.C4.3-5 |
| Investigate the social, ethical, legal Grades 3-5 | Students look at how computers and apps affect real people's lives, from privacy and fairness to rules about what's allowed online. They think through both the good and the problems that come with living in a digital world. | OH-CSDF.C5.3-5 |
Students practice working with others who have different backgrounds and ideas, and learn why hearing from everyone makes technology and problem-solving better.
Students work with others to plan and build a computer project, splitting up tasks and combining their ideas to finish something none of them could do as well alone.
Students look at a big task, like building a game or sorting a list, and break it into smaller steps a computer could handle one at a time.
Students learn to spot patterns in a problem and use them to build a simpler solution that works in more than one situation, like writing one set of steps that solves a whole group of similar puzzles instead of solving each one separately.
Students write and test programs or build simple simulations, then revise them based on what works and what doesn't. The process repeats until the project does what they intended.
Students run their program or app, look for what breaks or confuses people, and fix it. Testing is part of the work, not just the last step.
Students explain how a program or digital tool works using the right words, pictures, or examples. They describe what it does and how it affects people, clearly enough that someone else can follow.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 3-5 | Students practice working with others who have different backgrounds and ideas, and learn why hearing from everyone makes technology and problem-solving better. | OH-CSDF.P1.3-5 |
| Collaborate around computing — divide work, share ideas Grades 3-5 | Students work with others to plan and build a computer project, splitting up tasks and combining their ideas to finish something none of them could do as well alone. | OH-CSDF.P2.3-5 |
| Identify and define problems that can be solved with computation and decompose… Grades 3-5 | Students look at a big task, like building a game or sorting a list, and break it into smaller steps a computer could handle one at a time. | OH-CSDF.P3.3-5 |
| Use abstractions to simplify complexity, generalise solutions Grades 3-5 | Students learn to spot patterns in a problem and use them to build a simpler solution that works in more than one situation, like writing one set of steps that solves a whole group of similar puzzles instead of solving each one separately. | OH-CSDF.P4.3-5 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 3-5 | Students write and test programs or build simple simulations, then revise them based on what works and what doesn't. The process repeats until the project does what they intended. | OH-CSDF.P5.3-5 |
| Systematically test computational artifacts and refine them based on evidence… Grades 3-5 | Students run their program or app, look for what breaks or confuses people, and fix it. Testing is part of the work, not just the last step. | OH-CSDF.P6.3-5 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 3-5 | Students explain how a program or digital tool works using the right words, pictures, or examples. They describe what it does and how it affects people, clearly enough that someone else can follow. | OH-CSDF.P7.3-5 |
Students learn how computers and the internet work, how to write simple programs, and how to collect and make sense of data. They also practice solving problems by breaking them into smaller steps and talking through how computing affects people.
It helps, but it is not required. Most thinking skills can be practiced without a screen by writing step-by-step instructions for a snack recipe, sorting objects by rules, or planning a route on a map. A library computer once a week covers the rest.
Give a small task and ask for clear steps in order, like how to brush teeth or feed a pet. Talk about what could go wrong at each step and how to fix it. That is the same thinking students use when they write a program.
Start with hardware and basic troubleshooting so students can name parts and ask better questions. Move into networks and online safety, then data, then programming and algorithms. Save impacts of computing for the end so students can ground it in things they have built.
Students can plan a short program, test it, fix what is broken, and explain what each part does. They can read a small data set, spot a pattern, and make a claim from it. They can also describe how a network moves information and why passwords matter.
Debugging and decomposition. Students often want to rewrite the whole program when one line is wrong, and they bundle big problems into one step instead of breaking them up. Build short routines around finding the bug and naming the subproblems before coding.
Much of this work happens off the screen. Students draw flowcharts, act out algorithms, sort cards, and talk through problems with a partner. Coding time is focused and tied to a clear task, not open browsing.
Students talk about strong passwords, what to share online, and how to treat people in a chat or comment. They also look at who benefits and who gets left out when a tool is designed a certain way. These talks come up alongside the projects, not as a separate unit.
Pairs or small groups divide the work, share drafts, and give each other feedback before turning anything in. Roles rotate so the same student is not always typing or always planning. Use a short rubric for teamwork so feedback stays specific.
A ready student can plan a multi-step program, test it against examples, and explain choices in plain language. They can pull a pattern from a small data set and back up a claim with it. They can also describe how the internet sends a message from one device to another.