Computers, tools, and teamwork
Students get comfortable with the parts of a computer and how to pick the right tool for a task. They practice working in groups, sharing ideas, and trying simple fixes when something goes wrong.
This is the stretch when computers stop being something students click on and start being something they can build with. Students write simple programs, break a big problem into smaller steps, and fix what isn't working. They also learn how the internet moves information between people and why passwords and kind online behavior matter. By spring, students can plan, build, and test a small project like a game or animation, and explain how it works.
Students get comfortable with the parts of a computer and how to pick the right tool for a task. They practice working in groups, sharing ideas, and trying simple fixes when something goes wrong.
Students learn how computers talk to each other across the internet and why some information needs to stay private. They practice safer habits like strong passwords and thinking before they share.
Students collect information, sort it into tables and charts, and look for patterns. They start using what they find to back up a claim with real evidence.
Students break big problems into smaller steps and write simple programs to solve them. They test their code, fix what breaks, and improve it based on what they notice.
Students think about how technology shapes daily life, who it helps, and who it can leave out. They share their own projects and explain the choices they made.
Students figure out which devices, apps, and tools fit a specific task, then work through basic fixes when something stops working.
Students learn how computers connect to each other through networks and the internet to share information, send messages, and work together. They also look at how data is kept private and safe when it travels between devices.
Students gather information, organize it into charts or graphs, and use what they see to explain a pattern or back up an answer. The focus is on reading the data closely enough to say something true about it.
Students write step-by-step instructions a computer can follow to solve a problem or build something new, then check whether those instructions actually work.
Students look at how computers and apps affect everyday life, including who benefits, who might be left out, and what rules should apply. They think through real questions about fairness, privacy, and responsibility.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 3-5 | Students figure out which devices, apps, and tools fit a specific task, then work through basic fixes when something stops working. | PA-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 share information, send messages, and work together. They also look at how data is kept private and safe when it travels between devices. | PA-CSDF.C2.3-5 |
| Collect, transform, and represent data Grades 3-5 | Students gather information, organize it into charts or graphs, and use what they see to explain a pattern or back up an answer. The focus is on reading the data closely enough to say something true about it. | PA-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 build something new, then check whether those instructions actually work. | PA-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 might be left out, and what rules should apply. They think through real questions about fairness, privacy, and responsibility. | PA-CSDF.C5.3-5 |
Students practice working with classmates who have different backgrounds and ideas, making sure everyone's voice counts when solving a problem or building something on a computer.
Students work with partners or a small group to plan, build, and improve a computing project, splitting up tasks and combining their work into one finished product.
Students look at a real problem, decide whether a computer could help solve it, and then break it into smaller steps that are easier to tackle one at a time.
Students find the pattern in a problem and use it to write one solution that works in many situations, instead of solving the same type of problem over and over from scratch.
Students write programs or build digital projects by trying something, testing it, fixing what doesn't work, and trying again until it does what they want.
Students run their program or project, look for what breaks or confuses people, and fix it. Testing is part of the work, not the end of it.
Students explain how a program or digital tool works by using the right words, pictures, or data to back up what they say. The explanation is clear enough that someone else could understand it without guessing.
| 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, making sure everyone's voice counts when solving a problem or building something on a computer. | PA-CSDF.P1.3-5 |
| Collaborate around computing — divide work, share ideas Grades 3-5 | Students work with partners or a small group to plan, build, and improve a computing project, splitting up tasks and combining their work into one finished product. | PA-CSDF.P2.3-5 |
| Identify and define problems that can be solved with computation and decompose… Grades 3-5 | Students look at a real problem, decide whether a computer could help solve it, and then break it into smaller steps that are easier to tackle one at a time. | PA-CSDF.P3.3-5 |
| Use abstractions to simplify complexity, generalise solutions Grades 3-5 | Students find the pattern in a problem and use it to write one solution that works in many situations, instead of solving the same type of problem over and over from scratch. | PA-CSDF.P4.3-5 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 3-5 | Students write programs or build digital projects by trying something, testing it, fixing what doesn't work, and trying again until it does what they want. | PA-CSDF.P5.3-5 |
| Systematically test computational artifacts and refine them based on evidence… Grades 3-5 | Students run their program or project, look for what breaks or confuses people, and fix it. Testing is part of the work, not the end of it. | PA-CSDF.P6.3-5 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 3-5 | Students explain how a program or digital tool works by using the right words, pictures, or data to back up what they say. The explanation is clear enough that someone else could understand it without guessing. | PA-CSDF.P7.3-5 |
Students learn to use computers as tools: typing, saving files, fixing common problems, and sharing work online safely. They also write simple programs, work with data like charts and tables, and talk about how technology affects people. Most of the work happens through small projects, not lectures.
A regular laptop or tablet is plenty. Ask students to show what they made, explain the steps, and talk through what went wrong before it worked. Short, free programming sites like Scratch or Code.org give 10 to 15 minutes of practice that goes a long way.
An algorithm is a clear set of steps to get something done, like a recipe. Students break a task into smaller steps, put them in order, and test if the steps work. Making a sandwich, giving directions to school, or programming a character to move across a screen all count.
Most teachers start with computing basics and safe use of devices, then move into networks and data in the middle of the year, and finish with longer programming projects. Ethics and impact threads through every unit, not as a standalone block. Build in time to revisit earlier skills inside later projects.
It is closer to building something than watching something. Making a game, animating a story, or sorting data is active work and tends to leave students tired in a good way. Still, keep sessions short and ask what was built, not just what was used.
Debugging is the big one. Students often want to start over instead of finding the one step that broke. Decomposing a problem and using loops or repeated steps also take time. Plan to revisit these inside new projects rather than teaching them once and moving on.
Students learn to protect passwords, recognise that not everything online is true, and think before posting about themselves or others. They also learn that the work people put online belongs to someone, so giving credit matters. These conversations work best when they come up during real projects.
By the end of the year, students should plan and build a small program with a few steps and a loop, test it, and explain what it does. They should also be able to read a simple chart, spot a pattern in data, and discuss one way technology affects daily life.
Most early frustration comes from one stuck step, not from being bad at it. Sit nearby, ask what was tried, and praise the fix more than the finished product. Pick one small project they care about, like a birthday card animation, and let them tinker without a deadline.