Getting comfortable with computers
Students learn the parts of a computer and how to fix small problems on their own, like a frozen screen or a missing file. They build habits for working together and being kind online.
This is the stretch when students move from clicking through apps to building simple programs of their own. Students write step-by-step instructions a computer can follow, fix the parts that go wrong, and use spreadsheets or charts to spot patterns in data. They also learn how the internet moves information between computers and why passwords and kind online behavior matter. By spring, students can plan, build, and debug a small project like a game or animation that solves a problem they chose.
Students learn the parts of a computer and how to fix small problems on their own, like a frozen screen or a missing file. They build habits for working together and being kind online.
Students see how messages and files travel between computers and why some information should stay private. They practice sharing work with classmates and giving each other helpful feedback.
Students gather numbers and facts, then turn them into charts and tables that tell a clear story. They look for patterns and use what they find to answer real questions.
Students break a big task into smaller steps and write code that makes the computer do the work. They test their programs, find the bugs, and fix them until the program runs the way they planned.
Students think about how apps, games, and websites affect people, including who gets left out. They share their own projects and explain the choices behind them using clear words and pictures.
Students figure out which tools (a keyboard, an app, a printer) fit the job at hand, then work through basic fixes when something stops working.
Students learn how the internet connects computers so people can send messages, share files, and work together, and why keeping that data secure matters. Think of it as understanding the rules of the road for information moving between devices.
Students gather information, organize it into charts or graphs, and look for patterns. Then they use what they see in the data to back up an argument or answer a question.
Students write step-by-step instructions a computer can follow to solve a problem or build something new, then test those instructions to see if they work.
Students look at how computers and apps affect real people's lives, including questions about fairness, privacy, and who has access to technology.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 3-5 | Students figure out which tools (a keyboard, an app, a printer) fit the job at hand, then work through basic fixes when something stops working. | MA-CSDF.C1.3-5 |
| Explain how computer networks and the Internet enable communication… Grades 3-5 | Students learn how the internet connects computers so people can send messages, share files, and work together, and why keeping that data secure matters. Think of it as understanding the rules of the road for information moving between devices. | MA-CSDF.C2.3-5 |
| Collect, transform, and represent data Grades 3-5 | Students gather information, organize it into charts or graphs, and look for patterns. Then they use what they see in the data to back up an argument or answer a question. | MA-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 test those instructions to see if they work. | MA-CSDF.C4.3-5 |
| Investigate the social, ethical, legal Grades 3-5 | Students look at how computers and apps affect real people's lives, including questions about fairness, privacy, and who has access to technology. | MA-CSDF.C5.3-5 |
Students learn to work with classmates who have different backgrounds and ideas, and practice making group projects feel welcoming to everyone involved.
Students work with others to build something on a computer, splitting up the tasks and using each other's ideas to improve the final result.
Students look at a big problem, decide whether a computer could help solve it, and break it into smaller steps a program could handle one at a time.
Students take a complicated problem and find the parts that repeat or stay the same, then use that pattern to write 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 adjusting is part of the process, not a sign something went wrong.
Students run their program or app, look for what breaks or confuses a user, and fix it. They repeat that cycle until the project works the way it's supposed to.
Students explain how a program or app works using the right words, labeled diagrams, or real examples. They describe what it does and how it affects people, clearly enough that someone unfamiliar with it would understand.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 3-5 | Students learn to work with classmates who have different backgrounds and ideas, and practice making group projects feel welcoming to everyone involved. | MA-CSDF.P1.3-5 |
| Collaborate around computing — divide work, share ideas Grades 3-5 | Students work with others to build something on a computer, splitting up the tasks and using each other's ideas to improve the final result. | MA-CSDF.P2.3-5 |
| Identify and define problems that can be solved with computation and decompose… Grades 3-5 | Students look at a big problem, decide whether a computer could help solve it, and break it into smaller steps a program could handle one at a time. | MA-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 stay the same, then use that pattern to write a simpler solution that works in more than one situation. | MA-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 adjusting is part of the process, not a sign something went wrong. | MA-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 a user, and fix it. They repeat that cycle until the project works the way it's supposed to. | MA-CSDF.P6.3-5 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 3-5 | Students explain how a program or app works using the right words, labeled diagrams, or real examples. They describe what it does and how it affects people, clearly enough that someone unfamiliar with it would understand. | MA-CSDF.P7.3-5 |
Students learn to use computers as tools and as things they can build with. They write small programs, work with data, send information over networks, and talk about how technology affects people. Much of the work happens in pairs or small groups.
No. Most of the hands-on work happens at school. At home, talking through everyday tech questions helps more than extra screen time. Try asking how a website knows their name, or how a game decides what happens next.
Ask a student to teach a parent how their program works. Explaining the steps out loud is where the real learning happens. Free sites like Scratch and Code.org are good for ten or fifteen minutes of tinkering after school.
Students should know not to share passwords, addresses, or photos with strangers, and should tell an adult when something online feels off. At home, keep the conversation open. Ask what apps they use and who they talk to there.
A common path starts with hardware and basic troubleshooting, moves into algorithms and programming, then brings in data and networks once students can build simple programs. Save the heavier ethics and impact discussions for after students have built something themselves.
Decomposition and debugging. Students often try to solve a whole problem at once instead of breaking it into smaller steps, and they guess at fixes instead of testing one change at a time. Short, repeated practice with both habits pays off all year.
Students can plan a small program, test it, fix what does not work, and explain their choices to someone else. They can read a simple chart of data and say what it shows. They can also describe a few ways computing affects people outside the classroom.
A lot of it. Pair programming and small group projects are core to the practices, not extras. Rotating roles, such as driver and navigator, keeps one student from doing all the typing while the other watches.
By the end of fifth grade, a student should be able to log in independently, save and find their work, write a short program with loops, and talk about a tech problem without panicking. If those feel solid, the next grade will build on them.