What does a student learn in
New York, Grade 8, Computer Science & Digital Fluency ?

Students test two different simulations or computer models side by side, then explain how changing the starting data or assumptions shifts the results. The goal is to understand why two models can answer the same question differently.

Students gather real data, like survey answers or measurements, and use it inside a program or spreadsheet to produce a result, a chart, or a working model.

Students take a set of data and turn it into a chart or graph designed to make a clear point. They decide how to present the numbers so the audience sees what they want them to see.

Students write code where each function or procedure has a clear name that tells anyone reading it exactly what that chunk of code is supposed to do.

When the same steps repeat in a program with small differences, students rewrite that code as a single reusable block that accepts inputs to handle each variation.

Students write step-by-step instructions that tell a computer how to complete a task, then test and improve those instructions until they work better.

A variable is a labeled container in code that holds a value and updates as the program runs. Students write or modify a program where at least one variable tracks something that changes, like a score, a count, or a name.

Students write or remix a program that uses loops, conditions, or similar controls together to make something work or create something new.

Students read through a short program and figure out what it will do before it runs, then use that prediction to spot and fix errors. The focus is on code that makes decisions or repeats steps.

Students design something on a computer, then improve it based on what users say they want. They keep notes on each round of changes so they can show how the project evolved over time.

Students identify which personal details and online accounts need to stay private, such as passwords, location data, and payment information, and think through who or what might put those things at risk.

Students learn the difference between physical locks, software settings, and everyday habits that keep devices and data safe, then practice matching the right safeguard to the right situation.

Security safeguards involve real trade-offs. Students look at choices like passwords, filters, or encryption and explain what each one protects against and what it costs in convenience, speed, or access.

Cryptography (scrambling data to keep it private) is not foolproof. Students explain why encryption can fail or be cracked, and what that means for keeping information safe.

Students learn what to do when a phone, computer, or app sends a security warning or starts acting strangely. That includes steps to take before a problem hits, like keeping software updated, and what to do after, like changing passwords or reporting the issue.

Students practice typing on a keyboard with the right hand position and posture, working toward faster, more accurate keyboarding over time.

Students use shared digital tools, like a shared document or slide deck, to build something together with classmates and revise it based on each other's feedback.

Students learn to pick the right search tool for the job, not just default to one search engine, and judge whether the results it returns are actually useful and trustworthy.

Students pick the right app or tool to build something digital, like a slide deck, video, or website, then improve and share it.

Students use what they already know about one tool or app to figure out how a new one works, instead of starting from scratch every time something changes.

Once something is posted online, it can be copied, shared, and stored by others, often permanently. Students learn why what they post shapes how others see them and how it can affect their privacy for years to come.

Students learn what respectful, safe behavior online looks like and practice recognizing when something crosses the line. They also learn specific steps to handle cyberbullying, harassment, or other harmful situations.

Students look at how a technology (like social media or a fitness tracker) helps people in some ways and causes problems in others, then explain the tradeoffs.

Students look at a real law (like a privacy rule or copyright protection) and explain how it shapes what engineers can build or what people can do online.

Students look at real news stories or everyday tech situations and name the ethical questions they raise, such as who owns personal data or whether an algorithm treats people fairly.

Students learn to spot the difference between public and private data and talk through real issues that come up when companies or apps collect it, like who can see it and how it gets used.

Students look at who built a computer system and what data it was trained on, then ask whose needs might get ignored or who might get treated unfairly as a result.

Students look at an app or device and judge how well it works for people with different needs, like someone who can't hear audio or needs larger text to read the screen.

Students look at real jobs in computer science, from writing software to designing networks, and learn what those roles actually involve day to day.

Students sketch or prototype a screen layout, then check whether it's easy to use, works for people with disabilities, and looks appealing enough that someone would actually want to use it.

Students plan and build a project that uses both physical parts (like a circuit or sensor) and the code that controls them. The two pieces have to work together to do something useful.

When a device, app, or connection stops working, students follow a step-by-step process to figure out what went wrong and fix it, rather than guessing at random.

Students map out rules for how data travels from one device to another across a network with multiple stops. Think of it like writing the directions a package must follow to reach the right address when several routes are possible.

Students learn how files and information saved on a distant computer or server travel back to their device over a network. Think of it as borrowing a book from a library you never visit in person.