Computers, networks, and safe habits
Students start the year learning how computers and networks actually work. They set up tools, troubleshoot common problems, and practice safer habits online when sharing files or messaging others.
This is the year computing shifts from using tools to building them. Students write real programs, break big problems into smaller pieces, and work with data to spot patterns and back up claims. They also weigh how technology affects privacy, jobs, and daily life. By spring, students can plan, code, and test a working program or data project and explain how it works to someone else.
Students start the year learning how computers and networks actually work. They set up tools, troubleshoot common problems, and practice safer habits online when sharing files or messaging others.
Students collect numbers and information, clean it up, and turn it into charts they can explain. They look for patterns and back up what they say with the data instead of a hunch.
Students break big problems into smaller steps and write code to solve them. They learn to spot patterns across problems so the same idea can be reused in a new project.
Students build real projects, often in teams. They share the work, give and take feedback, then test their programs over and over to fix bugs and make them easier to use.
Students look at how technology shapes daily life, jobs, and privacy. They weigh the trade-offs of a tool or app and present their thinking with clear evidence to an audience.
Students learn to pick the right hardware and software for a given task, then work through common problems when something stops working.
Students learn how data travels across networks and the Internet, from a message sent to a friend to a file stored in the cloud. The focus is on how those connections stay secure and why the rules that govern them matter.
Students gather raw data, clean or reorganize it, and display it in a chart or table. Then they use software to spot patterns and back up any conclusions with numbers from the data itself.
Students write and test programs that solve real problems or automate repetitive tasks. They also study how their code works, looking for ways to make it faster or more reliable.
Students examine how computers, apps, and online systems shape daily life, including who benefits, who gets left out, and what legal or ethical questions arise when technology spreads across communities and countries.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software High School | Students learn to pick the right hardware and software for a given task, then work through common problems when something stops working. | TX-CSDF.C1.9-12 |
| Explain how computer networks and the Internet enable communication… High School | Students learn how data travels across networks and the Internet, from a message sent to a friend to a file stored in the cloud. The focus is on how those connections stay secure and why the rules that govern them matter. | TX-CSDF.C2.9-12 |
| Collect, transform, and represent data High School | Students gather raw data, clean or reorganize it, and display it in a chart or table. Then they use software to spot patterns and back up any conclusions with numbers from the data itself. | TX-CSDF.C3.9-12 |
| Design, develop, and analyze algorithms and programs to solve problems… High School | Students write and test programs that solve real problems or automate repetitive tasks. They also study how their code works, looking for ways to make it faster or more reliable. | TX-CSDF.C4.9-12 |
| Investigate the social, ethical, legal High School | Students examine how computers, apps, and online systems shape daily life, including who benefits, who gets left out, and what legal or ethical questions arise when technology spreads across communities and countries. | TX-CSDF.C5.9-12 |
Students practice working with people who have different backgrounds and viewpoints, and think about how the technology they build or use affects everyone, not just people like themselves.
Students work with others to build something on a computer, splitting up tasks, sharing ideas, and revising based on feedback from the group.
Students look at a real problem, decide whether a computer can help solve it, and break it into smaller pieces a program could handle one step at a time.
Students take a complicated program or system and strip it down to what matters, ignoring the rest. That simplified version becomes a tool they can reuse or explain to solve bigger problems.
Students write programs or build simulations by testing their work, fixing what breaks, and improving it in repeated rounds. The focus is on the process of building and revising, not just the finished product.
Students run planned tests on a program or app, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier to use.
Students explain how a program, algorithm, or digital tool works by using the right terms, visuals, and evidence. The goal is a clear explanation someone else can actually follow.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… High School | Students practice working with people who have different backgrounds and viewpoints, and think about how the technology they build or use affects everyone, not just people like themselves. | TX-CSDF.P1.9-12 |
| Collaborate around computing — divide work, share ideas High School | Students work with others to build something on a computer, splitting up tasks, sharing ideas, and revising based on feedback from the group. | TX-CSDF.P2.9-12 |
| Identify and define problems that can be solved with computation and decompose… High School | Students look at a real problem, decide whether a computer can help solve it, and break it into smaller pieces a program could handle one step at a time. | TX-CSDF.P3.9-12 |
| Use abstractions to simplify complexity, generalise solutions High School | Students take a complicated program or system and strip it down to what matters, ignoring the rest. That simplified version becomes a tool they can reuse or explain to solve bigger problems. | TX-CSDF.P4.9-12 |
| Create computational artifacts — programs, simulations, models — by applying… High School | Students write programs or build simulations by testing their work, fixing what breaks, and improving it in repeated rounds. The focus is on the process of building and revising, not just the finished product. | TX-CSDF.P5.9-12 |
| Systematically test computational artifacts and refine them based on evidence… High School | Students run planned tests on a program or app, find what breaks or confuses users, and fix it. The goal is a version that works correctly and is easier to use. | TX-CSDF.P6.9-12 |
| Communicate clearly with appropriate vocabulary, visualizations High School | Students explain how a program, algorithm, or digital tool works by using the right terms, visuals, and evidence. The goal is a clear explanation someone else can actually follow. | TX-CSDF.P7.9-12 |
Students learn to write programs, work with data, and understand how networks and the internet move information. They also look at how computing affects people, from privacy to jobs to access. The work mixes hands-on coding with bigger conversations about ethics and impact.
No. Students start where they are and build up through small projects. Most courses begin with simple programs and grow into longer ones over the year.
Ask students to walk through what their program is supposed to do and where it broke. Explaining a bug out loud often fixes it. Showing interest in the project matters more than knowing the language.
Students can take a real problem, break it into smaller steps, write a working program, and test it. They can also explain their choices and talk about who their program helps or leaves out.
Start with short programs that build fluency with variables, loops, and functions. Move into data and algorithms by the middle of the year, then finish with longer projects that pull in networks, ethics, and user testing. Revisit debugging and decomposition in every unit.
Decomposition and debugging. Students often try to write a whole program at once instead of breaking it into pieces, and they guess at fixes instead of reading error messages. Plan short, repeated practice on both across the year.
It varies, but most homework involves working on code or writing about a project. Encourage breaks every 30 to 40 minutes. A short conversation about what students built that day is often more useful than extra screen time.
Most teachers grade a mix of the final artifact, each student's contribution, and a short reflection. Asking students to explain their part of the code is a good check. Rotating roles across projects helps every student practice each skill.
Students should be able to read unfamiliar code, write a program of about 100 lines that solves a real problem, and explain how data moves through a network. They should also be able to discuss the tradeoffs of a tool they use every day.