Skip to content

What does a student learn in ?

This is the stretch where students stop using computers and start building with them. Students write real programs, break big problems into smaller steps, and work with data to spot patterns and back up a claim. They also dig into how the internet moves information and what that means for privacy and fairness online. By spring, students can plan, code, and test a small project, then explain how it works and who it affects.

  • Programming
  • Problem solving
  • Data and patterns
  • Networks and internet
  • Online safety
  • Ethics in tech
  • Teamwork on projects
Source: Illinois Illinois Learning Standards
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. 1

    Devices, networks, and safe habits

    Students learn how computers, phones, and the internet actually work behind the screen. They practice basic troubleshooting and talk about staying safe and private online.

  2. 2

    Working with data

    Students gather information, sort it, and turn it into charts or tables that tell a clear story. They learn to back up a claim with what the numbers actually show.

  3. 3

    Thinking like a programmer

    Students break big problems into smaller steps and write simple programs to solve them. Expect to hear about loops, conditions, and fixing code that almost works.

  4. 4

    Building and testing projects

    Students design their own apps, games, or simulations and improve them based on feedback from classmates. They learn that the first version is almost never the final one.

  5. 5

    Computing in the real world

    Students look at how technology shapes daily life, from social media to AI tools. They discuss fairness, privacy, and who gets left out when tech is designed poorly.

Mastery Learning Standards
The required skills a student should display by the end of Grade 8.
Concepts
  • Identify, select, and apply hardware, software

    Grades 6-8

    Students figure out which devices, programs, and settings will get a job done, then fix what goes wrong when things break. This covers choosing the right tool for the task and working through common tech problems step by step.

  • Explain how computer networks and the Internet enable communication…

    Grades 6-8

    Students explain how the internet connects devices around the world so people can share files, send messages, and work together, and why encryption and other safeguards keep that data from falling into the wrong hands.

  • Collect, transform, and represent data

    Grades 6-8

    Students gather raw information, organize it into charts or tables, and use software tools to spot patterns. Then they make a claim backed by what the data actually shows.

  • Design, develop, and analyze algorithms and programs to solve problems…

    Grades 6-8

    Students write and test step-by-step instructions that tell a computer what to do, then check whether those instructions actually solve the problem they set out to fix.

  • Investigate the social, ethical, legal

    Grades 6-8

    Students look at how computers, apps, and digital tools affect real people's lives, including questions about fairness, privacy, and who gets left out. They think through problems that don't have easy answers.

Practices
  • Foster an inclusive computing culture that values diverse perspectives and…

    Grades 6-8

    Students practice working on tech projects with classmates who have different backgrounds and viewpoints. The goal is to build habits of listening, sharing credit, and making sure everyone has a real role in the work.

  • Collaborate around computing — divide work, share ideas

    Grades 6-8

    Students work in groups to plan, build, and improve a digital project. They split up tasks, share ideas, and use each other's feedback to make the final product better.

  • Identify and define problems that can be solved with computation and decompose…

    Grades 6-8

    Students break a big, messy problem into smaller pieces a computer could actually handle. They figure out which parts can be solved with code and which parts need to be tackled in what order.

  • Use abstractions to simplify complexity, generalise solutions

    Grades 6-8

    Students take a complicated program or system and strip it down to the parts that matter, then use that simplified version to solve similar problems or explain how the system works.

  • Create computational artifacts — programs, simulations, models — by applying…

    Grades 6-8

    Students write and revise programs or simulations in repeated cycles, testing what works and fixing what doesn't until the project does what they intended.

  • Systematically test computational artifacts and refine them based on evidence…

    Grades 6-8

    Students run planned 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 real people to use.

  • Communicate clearly with appropriate vocabulary, visualizations

    Grades 6-8

    Students explain how a program, app, or algorithm works by using the right words, diagrams, or data to back up their points. Clear communication matters as much as writing the code itself.

Common Questions
  • What does a middle school computer science year actually cover?

    Students learn how computers and networks work, how to write small programs, and how to work with data. They also look at how technology affects people, like privacy, online safety, and fairness. By the end of eighth grade, they should be able to plan and build a simple program from start to finish.

  • My child says they want to learn to code. What can we do at home?

    Free sites like Scratch, Code.org, and Khan Academy let students build games and animations in a web browser. Twenty minutes a few times a week is plenty. Ask them to show what they made and explain one part that was tricky to figure out.

  • How do I help if my child gets stuck on a coding project?

    Resist the urge to fix it. Ask what the program is supposed to do, what it actually does, and where those two things first disagree. That habit, called debugging, is half of what computer science is.

  • How should I sequence the year across these five concept areas?

    A common path is hardware and networks in the fall, programming and algorithms through the winter, and data plus societal impact in the spring. Weave collaboration and ethics into every unit instead of saving them for the end. Each unit should finish with something students built and can explain.

  • Which skills usually need the most reteaching?

    Decomposing a problem into smaller steps and testing work in a planned way. Students often want to write the whole program at once and run it once at the end. Short, frequent build-and-test cycles fix more than any single lesson on syntax.

  • Does my child need their own computer for this class?

    No. Schools provide what students need during class. At home, a phone or tablet is fine for most practice sites, and the public library has computers for longer projects. Time spent talking through a problem out loud matters more than the device.

  • How much should I worry about screen time if it is coding?

    Building something is different from scrolling, but eyes and posture still get tired. Aim for breaks every 30 minutes and a clear stopping point. Ask students to sketch their plan on paper before they open the laptop, which cuts screen time and usually improves the project.

  • How do I grade a project when students worked in teams?

    Grade the artifact and the individual contribution separately. Ask each student to submit a short written or recorded explanation of what they built, what they tested, and what they would change. That gives evidence of individual thinking even when the code was shared.

  • How do I know students are ready for high school computer science?

    By the end of eighth grade, students should be able to read a short program and predict what it does, write one that uses variables and loops, and explain a basic privacy or ethics question in their own words. If they can plan, build, test, and talk about a small project, they are ready.