Devices, networks, and safe habits
Students learn how computers, phones, and the internet actually work behind the screen. They practice troubleshooting common problems and start thinking about passwords, privacy, and what to share online.
This is the stretch where students move from using computers to building with them. They write real programs that loop, make decisions, and solve a problem broken into smaller steps. Students also start asking harder questions about data, privacy, and who gets left out when technology is designed. By spring, students can plan a project with a partner, write and debug a working program, and explain how their choices affect the people who use it.
Students learn how computers, phones, and the internet actually work behind the screen. They practice troubleshooting common problems and start thinking about passwords, privacy, and what to share online.
Students gather information, sort it, and turn it into charts and graphs that show patterns. They practice backing up a claim with the numbers behind it instead of a hunch.
Students break a problem into smaller steps and write programs that solve it. They learn to plan before they code, test as they go, and fix bugs when the program does the wrong thing.
Students work in teams to design a game, app, or simulation from scratch. They divide the work, give each other feedback, and revise their project until it runs the way they intended.
Students look at how technology shapes daily life, from social media to jobs to who has access. They debate questions about fairness, copyright, and the choices behind the apps they use.
Students figure out which devices, programs, and fixes fit a given task, then choose and use the right ones. They also work through basic tech problems when something stops working.
Students learn how the internet moves data between computers and why some of that data is encrypted to keep it private. This covers how networks let people share files, send messages, and work together across devices.
Students gather raw data, clean or reorganize it, and display it in charts or tables. Then they use software tools to spot patterns and back up their conclusions with numbers.
Students write step-by-step instructions a computer can follow to solve a real problem or automate a repetitive task, then test whether those instructions actually work.
Students look at how computers and software affect real people's lives, from privacy and fairness to laws and global access. They think through who benefits, who might be left out, and what responsibilities come with building or using technology.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software Grades 6-8 | Students figure out which devices, programs, and fixes fit a given task, then choose and use the right ones. They also work through basic tech problems when something stops working. | CT-CSDF.C1.6-8 |
| Explain how computer networks and the Internet enable communication… Grades 6-8 | Students learn how the internet moves data between computers and why some of that data is encrypted to keep it private. This covers how networks let people share files, send messages, and work together across devices. | CT-CSDF.C2.6-8 |
| Collect, transform, and represent data Grades 6-8 | Students gather raw data, clean or reorganize it, and display it in charts or tables. Then they use software tools to spot patterns and back up their conclusions with numbers. | CT-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 real problem or automate a repetitive task, then test whether those instructions actually work. | CT-CSDF.C4.6-8 |
| Investigate the social, ethical, legal Grades 6-8 | Students look at how computers and software affect real people's lives, from privacy and fairness to laws and global access. They think through who benefits, who might be left out, and what responsibilities come with building or using technology. | CT-CSDF.C5.6-8 |
Students practice working with people who have different backgrounds and viewpoints when solving computing problems. The goal is to make sure technology and the people building it welcome everyone.
Students work with others to build a program or digital project: splitting up tasks, sharing ideas, and folding in each other's feedback before the final product comes together.
Students look at a real problem, decide whether a computer could help solve it, and break it into smaller pieces that are easier to tackle one at a time.
Students take a complicated problem and strip it down to what matters, then write a rule or formula that solves that type of problem, not just the one in front of them.
Students write programs or build simulations by testing, fixing, and improving their work in repeated rounds. Each cycle makes the project closer to what they want it to do.
Students run tests on a program or app they built, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier for someone else to use.
Students explain how a program or algorithm works using the right words, diagrams, or data to back up their points. Clear explanations help others understand, question, and build on computing ideas.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… Grades 6-8 | Students practice working with people who have different backgrounds and viewpoints when solving computing problems. The goal is to make sure technology and the people building it welcome everyone. | CT-CSDF.P1.6-8 |
| Collaborate around computing — divide work, share ideas Grades 6-8 | Students work with others to build a program or digital project: splitting up tasks, sharing ideas, and folding in each other's feedback before the final product comes together. | CT-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 break it into smaller pieces that are easier to tackle one at a time. | CT-CSDF.P3.6-8 |
| Use abstractions to simplify complexity, generalise solutions Grades 6-8 | Students take a complicated problem and strip it down to what matters, then write a rule or formula that solves that type of problem, not just the one in front of them. | CT-CSDF.P4.6-8 |
| Create computational artifacts — programs, simulations, models — by applying… Grades 6-8 | Students write programs or build simulations by testing, fixing, and improving their work in repeated rounds. Each cycle makes the project closer to what they want it to do. | CT-CSDF.P5.6-8 |
| Systematically test computational artifacts and refine them based on evidence… Grades 6-8 | Students run tests on a program or app they built, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier for someone else to use. | CT-CSDF.P6.6-8 |
| Communicate clearly with appropriate vocabulary, visualizations Grades 6-8 | Students explain how a program or algorithm works using the right words, diagrams, or data to back up their points. Clear explanations help others understand, question, and build on computing ideas. | CT-CSDF.P7.6-8 |
Students move past clicking and typing into building things. They write small programs, work with data in spreadsheets, learn how networks and the internet actually move information, and think through the ethics of what they post and share. Expect more project work and less worksheet work.
Ask students to explain what their program is supposed to do, then ask what it actually does. That gap is where learning happens. Free tools like Scratch, Code.org, and Khan Academy let students practice for 15 minutes a night, and parents only need to listen.
A school device is usually enough for class work. At home, any computer or borrowed library machine works for short practice sessions. A reliable internet connection matters more than a fancy laptop, since most coding tools run in a browser.
Start with the basics of how computers and networks work, then move into data and spreadsheets, then into programming with loops and conditionals. Save the bigger impact and ethics conversations for projects later in the year, when students have artifacts of their own to critique.
Debugging and breaking a big problem into smaller steps. Students often want to rewrite the whole program when one line is wrong. Building a habit of testing small pieces, reading error messages, and explaining bugs out loud pays off more than any single coding concept.
Pairs tend to work better than groups of three or four, since one keyboard forces real conversation. Rotate the driver and the navigator every 10 to 15 minutes. Mixed-experience pairs work well as long as the more experienced partner is coached to explain, not just type.
Class time covers passwords, privacy settings, and how to spot scams or misinformation. At home, the most useful thing is a regular conversation about what students are seeing and sharing online, including in games and group chats. Ask, do not just monitor.
Most grades come from projects: a working program, a data analysis, a short write-up explaining choices. Students are usually scored on whether the artifact works, whether they can explain how it works, and whether they revised it based on testing and feedback.
By spring, students should be able to read a short program and predict what it will do, fix a simple bug without help, and use a spreadsheet to answer a question with data. They should also be able to talk about the trade-offs of a piece of technology, not just whether they like it.