Skip to content
Learning Standards Standards

What does a student learn in ?

This is the year computing shifts from using tools to building them. Students write real programs, break big problems into smaller pieces, and test their code until it works. They look at how networks move data, how to keep it safe, and how technology shapes the people who use it. By spring, students can plan, build, and explain a working program or data project from start to finish.

  • Programming
  • Algorithms
  • Data analysis
  • Networks and security
  • Ethics in tech
  • Problem solving
Source: Rhode Island Rhode Island Core 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

    Computers, networks, and safe use

    Students start the year learning how computers and the internet actually work. They set up accounts safely, troubleshoot common problems, and look at how data moves between devices.

  2. 2

    Working with data

    Students gather data from real sources, clean it up, and turn it into charts and tables. They look for patterns and back up claims with what the numbers actually show.

  3. 3

    Writing programs that solve problems

    Students break bigger problems into smaller steps and write code to solve them. They learn to plan an algorithm before writing it and to use shortcuts that keep code simple.

  4. 4

    Testing, fixing, and improving projects

    Students build longer projects with a partner or team. They test their work, take feedback, and revise it until it runs the way a real user would expect.

  5. 5

    Computing and the wider world

    Students look at how technology affects jobs, privacy, and fairness. They present a project to an audience and explain the choices they made and who their work helps or hurts.

Mastery Learning Standards
The required skills a student should display by the end of Grade 10.
Concepts

  • Identify, select, and apply hardware, software

    RI-CSDF.C1.9-12
    High School

    Students match the right hardware and software to a task, then work through problems when something stops working. Think choosing a program, adjusting settings, or figuring out why a file won't open.

  • Explain how computer networks and the Internet enable communication…

    RI-CSDF.C2.9-12
    High School

    Students explain how the internet moves data between devices and how security measures protect that data in transit. They connect those ideas to everyday tools like email, shared documents, and video calls.

  • Collect, transform, and represent data

    RI-CSDF.C3.9-12
    High School

    Students gather real data, clean it up, and display it in charts or graphs. Then they use software to spot patterns and back up their conclusions with numbers.

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

    RI-CSDF.C4.9-12
    High School

    Students write code that solves a real problem or automates a repetitive task, then look back at how the program works to spot what could be improved.

  • Investigate the social, ethical, legal

    RI-CSDF.C5.9-12
    High School

    Students examine how computing technologies shape everyday life, from privacy and data use to laws and global access. They look at real cases where technology helped or harmed people, then form their own reasoned positions.

Practices

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

    RI-CSDF.P1.9-12
    High School

    Students learn to work with people who have different backgrounds and viewpoints, and to build technology and projects that include everyone, not just the most visible users.

  • Collaborate around computing — divide work, share ideas

    RI-CSDF.P2.9-12
    High School

    Students work in teams to build software, apps, or other computing projects. They split up tasks, share ideas, and revise each other's work until the final product comes together.

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

    RI-CSDF.P3.9-12
    High School

    Students look at a real problem, decide whether a computer can help solve it, then break it into smaller pieces that are each easier to tackle on their own.

  • Use abstractions to simplify complexity, generalise solutions

    RI-CSDF.P4.9-12
    High School

    Students take a complicated program or system and find the patterns that let them describe or solve it with simpler, reusable pieces. Instead of rewriting code from scratch each time, they build general solutions that work across many problems.

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

    RI-CSDF.P5.9-12
    High School

    Students build programs, simulations, or models by writing code, testing it, and revising it based on what they find. The work moves in cycles, not a straight line from start to finish.

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

    RI-CSDF.P6.9-12
    High School

    Students run planned tests on their programs or digital projects, then fix what breaks or confuses users. The goal is a finished product that works correctly and is easy for others to use.

  • Communicate clearly with appropriate vocabulary, visualizations

    RI-CSDF.P7.9-12
    High School

    Students explain how a program, algorithm, or tech system works using the right words, clear visuals, and real examples. The goal is an audience that actually understands, not just a teacher who already does.

Common Questions
  • What should students be able to do by the end of this course?

    Students should be able to write a working program, fix common computer problems, and explain how the internet moves data. They should also know how to talk about the trade-offs of technology, like privacy, bias, and access, with real examples.

  • Does a student need to be good at math to do well in this class?

    Strong math helps, but it is not the gatekeeper. Most of the work is about breaking a problem into smaller steps and testing ideas until they work. Patience and a willingness to debug matter more than being fast at arithmetic.

  • How can someone help at home if a student gets stuck on code?

    Ask the student to read the code out loud, line by line, and explain what each part is supposed to do. Most bugs show up the moment a student has to put the logic into plain words. No coding background is needed to listen.

  • How should the year be sequenced across these five concept areas?

    Start with hardware and networks so later programming work has context, then move into data and algorithms once students can talk about how information is stored and moved. Save larger projects with social and ethical analysis for the second half, when students have the vocabulary to argue a position with evidence.

  • Which skills usually need the most reteaching?

    Decomposition and debugging. Students often try to write a whole program at once and then cannot tell which part is broken. Repeated short cycles of plan, code, test, and revise build the habit faster than long projects.

  • How much screen time at home should support this class?

    Ten to twenty minutes of focused practice on a coding site or a small personal project beats an hour of passive watching. Ask the student to show one thing they built or fixed that week and explain how it works.

  • What does mastery of the practices look like in student work?

    A student who has met the practices can take a messy problem, break it into parts, build a draft, test it with real input, and explain what they changed and why. Look for evidence of revision, not just a finished product.

  • How can a student be ready for a college computing course or a tech job after this?

    Readiness shows up in three habits: writing code that another person can read, working on a shared project without falling apart, and explaining technical choices in plain language. A small portfolio of finished projects, even simple ones, carries more weight than a grade.