Computing tools and teamwork
Students get set up with the hardware, software, and troubleshooting habits they will lean on all year. They also learn how to share work, give feedback, and keep a team moving when projects get messy.
What does a student learn in
This is the year computing shifts from using tools to building them. Students write programs that solve real problems, break big tasks into smaller steps, and test their code until it works the way they meant. Along the way, they look at how data gets collected and shared, and who that helps or hurts. By spring, students can plan, code, and explain a working program of their own.
- Programming
- Algorithms
- Data analysis
- Networks and the internet
- Ethics in computing
- Debugging
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, internet, and safety
Students look at what actually happens when a message, photo, or password travels across the internet. They practice keeping accounts and data safer at home and at school.
- 3
Working with data
Students gather real data, clean it up, and turn it into charts that tell a clear story. They start backing up claims with numbers instead of guesses.
- 4
Programs and problem solving
Students break bigger problems into smaller steps and write programs that handle each step. They test their code, fix what breaks, and keep improving it based on what they notice.
- 5
Computing in the real world
Students step back and weigh how apps, algorithms, and AI affect people, jobs, and communities. They practice explaining a project clearly to an audience that is not in computer science class.
Mastery Learning Standards
The required skills a student should display by the end of Grade 10.
Concepts
Concepts
- High School
Identify, select, and apply hardware, software
Students learn to pick the right hardware and software for a job, then fix things when something breaks. That means matching tools to real tasks and knowing basic steps to solve common computer problems.
- High School
Explain how computer networks and the Internet enable communication…
Students learn how networks and the Internet move data between devices, and why security measures like encryption matter when that data is shared across systems.
- High School
Collect, transform, and represent data
Students gather raw data, clean or reshape it, and display it in a chart or table. Then they use software to spot patterns and back up a conclusion with numbers.
- High School
Design, develop, and analyze algorithms and programs to solve problems…
Students write and test programs that solve real problems or automate repetitive tasks. They also look back at their code to figure out where it breaks or slows down.
- High School
Investigate the social, ethical, legal
Students look at how technology shapes real life: who benefits, who gets left out, and what rules should exist. They examine privacy, fairness, and the laws that try to keep up with how fast computing changes the world.
| Standard | Definition | Code |
|---|---|---|
| Identify, select, and apply hardware, software High School | Students learn to pick the right hardware and software for a job, then fix things when something breaks. That means matching tools to real tasks and knowing basic steps to solve common computer problems. | VT-CSDF.C1.9-12 |
| Explain how computer networks and the Internet enable communication… High School | Students learn how networks and the Internet move data between devices, and why security measures like encryption matter when that data is shared across systems. | VT-CSDF.C2.9-12 |
| Collect, transform, and represent data High School | Students gather raw data, clean or reshape it, and display it in a chart or table. Then they use software to spot patterns and back up a conclusion with numbers. | VT-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 look back at their code to figure out where it breaks or slows down. | VT-CSDF.C4.9-12 |
| Investigate the social, ethical, legal High School | Students look at how technology shapes real life: who benefits, who gets left out, and what rules should exist. They examine privacy, fairness, and the laws that try to keep up with how fast computing changes the world. | VT-CSDF.C5.9-12 |
Practices
Practices
- High School
Foster an inclusive computing culture that values diverse perspectives and…
Students practice working and problem-solving with people who have different backgrounds and viewpoints. The goal is a classroom culture where everyone can participate in computing.
- High School
Collaborate around computing — divide work, share ideas
Students work with others to build a program or digital project: splitting up the tasks, sharing ideas along the way, and folding in each other's feedback before the final version is done.
- High School
Identify and define problems that can be solved with computation and decompose…
Students spot a real-world problem that a computer could help solve, then break it into smaller pieces that are easier to tackle one at a time.
- High School
Use abstractions to simplify complexity, generalise solutions
Students take a complicated program or system and strip it down to its key parts, then use that simplified version to solve similar problems or explain how the system works.
- High School
Create computational artifacts — programs, simulations, models — by applying…
Students build programs, simulations, or models by writing, testing, and revising code in repeated cycles until the work does what they intend.
- High School
Systematically test computational artifacts and refine them based on evidence…
Students run planned tests on programs or apps they build, then use what goes wrong to fix and improve the work. The goal is a program that behaves correctly and is easy for others to use.
- High School
Communicate clearly with appropriate vocabulary, visualizations
Students explain how a program, algorithm, or data set works using precise vocabulary, charts or diagrams, and real examples. The goal is a clear explanation any audience can follow, not just other programmers.
| Standard | Definition | Code |
|---|---|---|
| Foster an inclusive computing culture that values diverse perspectives and… High School | Students practice working and problem-solving with people who have different backgrounds and viewpoints. The goal is a classroom culture where everyone can participate in computing. | VT-CSDF.P1.9-12 |
| Collaborate around computing — divide work, share ideas High School | Students work with others to build a program or digital project: splitting up the tasks, sharing ideas along the way, and folding in each other's feedback before the final version is done. | VT-CSDF.P2.9-12 |
| Identify and define problems that can be solved with computation and decompose… High School | Students spot a real-world problem that a computer could help solve, then break it into smaller pieces that are easier to tackle one at a time. | VT-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 its key parts, then use that simplified version to solve similar problems or explain how the system works. | VT-CSDF.P4.9-12 |
| Create computational artifacts — programs, simulations, models — by applying… High School | Students build programs, simulations, or models by writing, testing, and revising code in repeated cycles until the work does what they intend. | VT-CSDF.P5.9-12 |
| Systematically test computational artifacts and refine them based on evidence… High School | Students run planned tests on programs or apps they build, then use what goes wrong to fix and improve the work. The goal is a program that behaves correctly and is easy for others to use. | VT-CSDF.P6.9-12 |
| Communicate clearly with appropriate vocabulary, visualizations High School | Students explain how a program, algorithm, or data set works using precise vocabulary, charts or diagrams, and real examples. The goal is a clear explanation any audience can follow, not just other programmers. | VT-CSDF.P7.9-12 |
Common Questions
What does high school computer science cover this year?
Students learn how computers, networks, and the internet work, and they write programs that solve real problems. They also work with data, build small projects, and think about how technology affects people. Coding is part of it, but so is privacy, fairness, and good teamwork.
Does a student need to already know how to code?
No. Courses start with the basics of writing instructions a computer can follow, then build up to longer programs over the year. Students who arrive with experience get pushed further on harder problems and bigger projects.
How can a parent help at home without knowing how to code?
Ask students to walk through what their program is supposed to do, step by step, in plain language. Explaining the logic out loud catches more bugs than staring at the screen. A five-minute talk-through at the kitchen table goes a long way.
What should a year-long course sequence look like?
A common arc is hardware and networks first, then programming basics, then data, then a longer project that pulls it together. Ethics and impact questions work best woven into each unit rather than saved for the end. Leave room for two or three iteration cycles on the final project.
Which topics usually need the most reteaching?
Loops, functions, and the idea of a variable holding a changing value trip up a lot of students. Debugging is another one. Most students need direct practice reading error messages and testing one change at a time.
How much screen time does this class involve?
Most of the work happens on a computer, but a fair amount of class time is spent planning on paper, talking through problems with a partner, and testing ideas. Students are building things on the screen, not scrolling.
What does mastery look like by the end of the year?
By spring, students can take a messy real-world problem, break it into smaller parts, and write a working program that solves it. They can also explain their code to someone else and discuss who it helps or harms. Clear thinking matters as much as clean code.
How is student work graded when projects look so different?
Most teachers grade on a rubric that looks at problem decomposition, working code, testing, and how clearly the student explains their choices. The finished product matters less than the thinking behind it. Two very different projects can both earn full marks.
How do teachers handle group projects fairly?
Assign clear roles, rotate them across projects, and collect short individual reflections at each checkpoint. Version history from the coding tool shows who contributed what. Grading the process alongside the product keeps one strong coder from carrying a group.
How does a parent know a student is ready for the next course?
Ask them to show a project they built this year and explain what it does, what broke along the way, and how they fixed it. Students who can talk about their own debugging are ready for more. Students who can only describe what the teacher told them to do need another round of practice.