Getting started with computers
Students learn the parts of a computer, how to log in, and what to do when something goes wrong. They start working in small groups and practice sharing ideas about how technology fits into daily life.
This is the stretch when computers shift from something students click to something they can actually build with. Students write simple programs with loops and steps, then test them and fix what breaks. They start asking how the internet moves information, how to spot a safe site, and why a password matters. By spring, students can plan a short program, debug it when it stalls, and explain a chart they made from real data.
Students learn the parts of a computer, how to log in, and what to do when something goes wrong. They start working in small groups and practice sharing ideas about how technology fits into daily life.
Students see how the internet moves information between devices and people. They practice safe habits with passwords and personal information, and talk about what makes online behavior kind and fair.
Students collect numbers and facts about real things, then sort them into charts and graphs on a computer. They look for patterns and use what they find to back up a simple claim.
Students write step-by-step instructions to make a character move, a game work, or a task repeat. They break big problems into smaller pieces, test their code, and fix the parts that do not behave as expected.
Students design their own programs, animations, or simulations and improve them based on feedback from classmates. They explain how their project works and think about who it helps and who it might leave out.
Students learn which hardware and software tools fit different jobs, then practice fixing common problems when something stops working.
Students learn how computers connect to each other through networks and the internet to send messages, share files, and keep information private while it travels.
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 that a computer can follow to solve a problem or complete a task. They test and adjust those instructions until the program does what they intended.
Students look at how computers and apps affect everyday life, including who benefits, who gets left out, and what rules should govern how they're used.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 3-5 | Students learn which hardware and software tools fit different jobs, then practice fixing common problems when something stops working. | NJ-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 while it travels. | NJ-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. | NJ-CSDF.C3.3-5 |
| Design, develop, and analyze algorithms and programs to solve problems… Grades 3-5 | Students write step-by-step instructions that a computer can follow to solve a problem or complete a task. They test and adjust those instructions until the program does what they intended. | NJ-CSDF.C4.3-5 |
| Investigate the social, ethical, legal Grades 3-5 | Students look at how computers and apps affect everyday life, including who benefits, who gets left out, and what rules should govern how they're used. | NJ-CSDF.C5.3-5 |
Students practice working with classmates who have different backgrounds and ideas, and learn why including everyone makes group tech work better.
Students work with classmates to plan and build a computing project, splitting up tasks and combining each person's ideas into one finished product.
Students break a big problem into smaller pieces to figure out which parts a computer could help solve. This skill shows up any time a project feels too large to tackle all at once.
Students take a complicated problem and find the parts that repeat or connect, then use that pattern to build a simpler solution that works in more than one situation.
Students write programs or build simple simulations, then test and improve them in repeated rounds. Each cycle of fixing and refining is part of the process, not a sign something went wrong.
Students test their programs or projects step by step, look for what goes wrong, and fix it. The goal is a final version that works the way it was meant to.
Students explain how a program works or why a technology affects their lives, using the right words, diagrams, or examples to make their thinking clear to someone else.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 3-5 | Students practice working with classmates who have different backgrounds and ideas, and learn why including everyone makes group tech work better. | NJ-CSDF.P1.3-5 |
| Collaborate around computing — divide work, share ideas Grades 3-5 | Students work with classmates to plan and build a computing project, splitting up tasks and combining each person's ideas into one finished product. | NJ-CSDF.P2.3-5 |
| Identify and define problems that can be solved with computation and decompose… Grades 3-5 | Students break a big problem into smaller pieces to figure out which parts a computer could help solve. This skill shows up any time a project feels too large to tackle all at once. | NJ-CSDF.P3.3-5 |
| Use abstractions to simplify complexity, generalise solutions Grades 3-5 | Students take a complicated problem and find the parts that repeat or connect, then use that pattern to build a simpler solution that works in more than one situation. | NJ-CSDF.P4.3-5 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 3-5 | Students write programs or build simple simulations, then test and improve them in repeated rounds. Each cycle of fixing and refining is part of the process, not a sign something went wrong. | NJ-CSDF.P5.3-5 |
| Systematically test computational artifacts and refine them based on evidence… Grades 3-5 | Students test their programs or projects step by step, look for what goes wrong, and fix it. The goal is a final version that works the way it was meant to. | NJ-CSDF.P6.3-5 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 3-5 | Students explain how a program works or why a technology affects their lives, using the right words, diagrams, or examples to make their thinking clear to someone else. | NJ-CSDF.P7.3-5 |
Students learn to use computers as tools and as things they can build with. They write simple programs, work with data, and talk about how the internet and apps affect people. Most of the work happens in small projects, not worksheets.
No. School is where the hands-on work happens. At home, talking about how a website, game, or app was made, or sketching out the steps for a chore on paper, builds the same thinking.
Ask students to explain the steps of something they know well, like making a sandwich or feeding a pet, in order, with no skipped steps. Then ask what would break if you swapped two steps. That is the same thinking behind writing a program.
Start with hardware, file basics, and safe online habits so the rest of the work has a foundation. Move into algorithms and simple programs in the middle of the year, then bring in data projects and discussions about the impact of technology toward the end.
Debugging. Students often guess at fixes instead of testing one change at a time. Build in short routines where they predict what a program will do, run it, and compare. The same habit helps with data work and troubleshooting a frozen device.
No. Students do learn to handle files, log in safely, and use common tools, but the bigger goal is problem solving. They break a problem into smaller parts, plan steps, test, and explain their thinking.
Students talk about strong passwords, what is okay to share, and how to spot when something online feels off. At home, the most useful thing is a regular conversation about what they saw or made online that day.
Students can take a problem, break it into smaller steps, build a working program or data project, test it, and explain what it does and who it affects. They can also troubleshoot common device issues without panicking.
Pairs and small groups are the norm. Students divide a project into parts, give each other feedback, and put the pieces together. Rotating roles like coder, tester, and presenter keeps one student from doing all the work.