Computing tools and teamwork
Students get set up with the hardware, software, and habits they will use all year. They learn to troubleshoot common problems and work in teams where every voice counts.
What does a student learn in
This is the year computer science shifts from using tools to building them. Students write programs that solve real problems, breaking each one into smaller pieces and testing the code until it works. They also dig into bigger questions about how networks move data, how to spot patterns in a dataset, and how technology shapes society. By spring, students can plan, build, and explain a working program or data project from start to finish.
- Writing programs
- Algorithms
- Working with data
- Networks and the internet
- Ethics in tech
- Debugging and testing
- Collaboration
Year at a glance
How the year usually goes. Every school and district set their own curriculum, so treat this as a guide, not official pacing.
- 1
- 2
Networks and online safety
Students look at how the internet actually moves information from one device to another. They practice keeping accounts, passwords, and personal data secure when sharing work online.
- 3
Working with data
Students gather real data, clean it up, and turn it into charts and tables. They use that evidence to spot patterns and back up the claims they make.
- 4
Programming and problem solving
Students break bigger problems into smaller pieces and write programs to solve them. They test their code, fix what is broken, and use feedback to make the next version better.
- 5
Computing and society
Students step back and look at how technology shapes daily life, jobs, and rights. They weigh the trade-offs of new tools and explain their thinking with clear evidence.
Mastery Learning Standards
The required skills a student should display by the end of Grade 11.
Concepts
Concepts
- High School
Identify, select, and apply hardware, software
Students learn to pick the right tools for a job, whether that means choosing software, setting up hardware, or figuring out why something stopped working. The focus is on solving real computing problems, not just knowing what things are called.
- High School
Explain how computer networks and the Internet enable communication…
Networks connect computers so they can send and receive information. Students explain how the internet makes that possible, including how data stays secure when it travels between devices.
- High School
Collect, transform, and represent data
Students gather raw data, clean it up, and turn it into a chart or table. Then they use software to spot patterns and back up a claim with numbers.
- High School
Design, develop, and analyze algorithms and programs to solve problems…
Students write programs that solve real problems or automate repetitive tasks. Along the way, they test their code, spot what breaks, and improve it.
- High School
Investigate the social, ethical, legal
Students look at how technology shapes everyday life, then weigh the trade-offs: who benefits, who gets left out, and what rules should govern it.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software High School | Students learn to pick the right tools for a job, whether that means choosing software, setting up hardware, or figuring out why something stopped working. The focus is on solving real computing problems, not just knowing what things are called. | IL-CSDF.C1.9-12 |
| Explain how computer networks and the Internet enable communication… High School | Networks connect computers so they can send and receive information. Students explain how the internet makes that possible, including how data stays secure when it travels between devices. | IL-CSDF.C2.9-12 |
| Collect, transform, and represent data High School | Students gather raw data, clean it up, and turn it into a chart or table. Then they use software to spot patterns and back up a claim with numbers. | IL-CSDF.C3.9-12 |
| Design, develop, and analyze algorithms and programs to solve problems… High School | Students write programs that solve real problems or automate repetitive tasks. Along the way, they test their code, spot what breaks, and improve it. | IL-CSDF.C4.9-12 |
| Investigate the social, ethical, legal High School | Students look at how technology shapes everyday life, then weigh the trade-offs: who benefits, who gets left out, and what rules should govern it. | IL-CSDF.C5.9-12 |
Practices
Practices
- High School
Foster an inclusive computing culture that values diverse perspectives and…
Students learn to build computing spaces where people with different backgrounds and experiences are included and heard. That means recognizing whose voices are missing and changing how groups work together to fix it.
- High School
Collaborate around computing — divide work, share ideas
Students work in groups to plan, build, and refine a computing project, splitting up tasks and incorporating each other's feedback along the way.
- High School
Identify and define problems that can be solved with computation and decompose…
Students look at a real problem and decide whether a computer could help solve it. Then they break that problem into smaller pieces a program can actually handle.
- High School
Use abstractions to simplify complexity, generalise solutions
Students practice breaking a complex problem into simpler patterns or rules that work across many situations, then use those patterns to write cleaner code or design a system that handles more than one case.
- High School
Create computational artifacts — programs, simulations, models — by applying…
Students write programs or build simulations by drafting, testing, and revising their work in repeated cycles until the result does what they intended.
- High School
Systematically test computational artifacts and refine them based on evidence…
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 for real people to use.
- High School
Communicate clearly with appropriate vocabulary, visualizations
Students explain how programs, algorithms, or tech systems work using clear language, labeled diagrams, and real examples. The goal is an audience that has never seen the code or process before.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… High School | Students learn to build computing spaces where people with different backgrounds and experiences are included and heard. That means recognizing whose voices are missing and changing how groups work together to fix it. | IL-CSDF.P1.9-12 |
| Collaborate around computing — divide work, share ideas High School | Students work in groups to plan, build, and refine a computing project, splitting up tasks and incorporating each other's feedback along the way. | IL-CSDF.P2.9-12 |
| Identify and define problems that can be solved with computation and decompose… High School | Students look at a real problem and decide whether a computer could help solve it. Then they break that problem into smaller pieces a program can actually handle. | IL-CSDF.P3.9-12 |
| Use abstractions to simplify complexity, generalise solutions High School | Students practice breaking a complex problem into simpler patterns or rules that work across many situations, then use those patterns to write cleaner code or design a system that handles more than one case. | IL-CSDF.P4.9-12 |
| Create computational artifacts — programs, simulations, models — by applying… High School | Students write programs or build simulations by drafting, testing, and revising their work in repeated cycles until the result does what they intended. | IL-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 for real people to use. | IL-CSDF.P6.9-12 |
| Communicate clearly with appropriate vocabulary, visualizations High School | Students explain how programs, algorithms, or tech systems work using clear language, labeled diagrams, and real examples. The goal is an audience that has never seen the code or process before. | IL-CSDF.P7.9-12 |
Common Questions
What does a high school computer science year actually cover?
Students learn how computers, networks, and the internet work, write programs to solve problems, and work with real data to find patterns. They also look at how technology affects people, including privacy, fairness, and security.
My teen has never coded before. Will they fall behind?
No. Most courses start with the basics of writing simple programs and build up from there. At home, sit with them for ten minutes while they try a free site like Code.org or Khan Academy, and ask them to explain one line of code back to you.
How should I sequence the year if students come in with very different backgrounds?
Start with shared ground in problem-solving and small programs before pushing into data and networks. Mixed-skill pairs work well early on, since stronger coders gain from explaining and newer students gain from seeing the thinking out loud.
How can I help at home if I don't know anything about coding?
Ask students to walk through what their program is supposed to do, step by step, as if writing instructions for a younger sibling. That kind of plain-language explanation is half the work, and it does not need a parent who codes.
Which topics tend to need the most reteaching?
Loops, functions, and the difference between a variable and its value trip up a lot of students. Debugging habits also need direct teaching, since many students change code at random instead of reading error messages and testing one thing at a time.
What does mastery look like by the end of the year?
Students can take a real problem, break it into smaller parts, write a program that solves it, and test and fix it based on what goes wrong. They can also speak clearly about how their program works and where data for it came from.
Is it a problem if my teen uses AI tools to write code?
Only if they copy without understanding. Ask them to read the code line by line and explain what each part does, or to change one small thing and predict what will happen. If they cannot, they are not learning yet.
How much should group work count in this course?
A fair amount. Real software is built by teams, so students need practice dividing work, reading each other's code, and giving useful feedback. Build in short solo checkpoints so grades reflect what each student actually knows.
How do I know my student is ready for a college or career path in tech?
They should be able to start a project from a blank screen, stick with a bug for more than five minutes, and talk about the ethical side of a tool they built or use. Comfort with not knowing the answer yet matters as much as any specific language.