As students learn CS in grade 7, they will be introduced to VEX robotics and they will experiment with apps controlled by devices. By exploring how physical devices interact with their environment, students investigate, design, and create new products, cultivating a maker mindset. It will be important that students pre-plan on paper and collaborate before trying out their ideas. Planning will not only be about the “neat” thing they hope to create, but also the “why”. It is important that students consider the reason they are creating this innovation, bias that could be included, and the needs of their users.
Current topics include:
how a robot is an example of a computing system
vocabulary related to physical computing (CPU, sensors)
applying systems thinking to understanding and debugging robotics
programming (and reprogramming) robots to perform a task using ROBOTC
In Grade 7, the focus moves from individual creativity to professional collaboration and system design. Students learn how to build technology that is meant to be shared, used by a variety of people, and built by a team.
Here are the vocabulary terms introduced by the specific standards we've mapped to Grade 7, defined for parents and teachers:
Procedure (The "Shortcut"): A named set of instructions that can be used over and over again. Instead of writing the same 10 steps every time a character "Dances," a student creates a Procedure called "Dance" and simply calls that name whenever it’s needed.
Documentation (The "Manual"): Written notes or comments within a project that explain how the code works. This is essential so that a teammate (or the student themselves, weeks later) can understand the "why" behind the work.
Intellectual Property (The "Ownership"): Creative work - like a song, an image, or a piece of code - that belongs to the person who made it. Students learn that even if something is online, they must respect the creator's rights.
Attribution (The "Shout-Out"): Giving credit to the original creator when you use their work in your own project. It’s like a bibliography, but for digital artifacts.
Packet (The "Suitcase"): Large files aren't sent across the internet all at once. They are broken into tiny "suitcases" called packets. These packets travel separate paths and get put back together in the right order at the destination.
Redundancy (The "Backup Path"): The internet is designed with many overlapping connections. If one cable is cut or a "router" stops working, redundancy ensures the data can find a different path to its destination so the system stays resilient.
Usability (The "Ease of Use"): A measure of how easy and satisfying a technology is to use. If a website is confusing or the buttons are hard to find, it has "low usability."
Inclusion (The "All-Access Pass"): Designing technology so that everyone, regardless of their background or physical ability, can participate and benefit from it.
Students will learn to write "Professional Shortcuts." Instead of writing long, repetitive code, students learn to use Procedures. These are named sets of instructions that can be reused throughout a program. This makes their work cleaner, more organized, and much easier for a teammate to read and understand.
Students will learn to respect "Digital Ownership." Children investigate Intellectual Property and the ethics of the internet. They learn that code, art, and music belong to their creators. They practice Attribution, which is the professional way to give a "shout-out" or credit to others when they learn from or "remix" existing work.
Students will learn how the Internet stays "Resilient." Students go behind the scenes of the web to see how it survives. They model how information is broken into tiny Packets to travel across the world and how Redundancy (having multiple backup paths) keeps the internet running even if a piece of hardware breaks or a connection fails.
Students will learn to design for "Everyone." A major goal this year is Inclusion. Students collaborate to audit existing technology and suggest improvements. They look for ways to make systems more accessible - such as adding voice controls or closed captions - ensuring that design choices don't accidentally leave anyone out.
Students will learn to be "Inclusive Collaborators." Computing in Grade 7 is about productive teamwork. Students practice sharing ideas during the planning phase and giving and receiving kind, constructive feedback. They learn that a diversity of perspectives leads to better, fairer, and more innovative technology.
Students will learn to "Refine through Feedback." Students learn that the first version of a program is rarely the final one. They practice gathering feedback from real users and then making purposeful changes to improve a tool's Usability. They learn that "fixing" a design based on someone else's needs is a hallmark of a great engineer.
Students will learn to "Engineer Fairness." Students become critics of the algorithms they see in daily life. They look for hidden biases and learn how to modify a plan to make it more equitable - like adjusting a search tool to include more diverse results or adding language options to a help-bot.
TIP: You can support your Grade 7 student by encouraging "The User Perspective." When you use a new app or see a website together, ask: "Who do you think this was designed for?" or "If we were a team building this, what Procedures would we need to create to make this work smoothly for everyone?"
The CSTA Standards do not break the 45 Middle School standards into specific grades. Here, we list the CSTA standards that are most connected to the grade 6 theme, "Computer Science is Collaborative". Italicized standards are not yet met. Underlined standards are partially met and we underline the parts that are met.
In Grade 7, the focus shifts to the "team". Students learn that the best solutions are built when we collaborate, respect intellectual property, and design for everyone.
COLLABORATION & PROFESSIONALISM:
MS-PRO-PD-12: Use procedures to structure code for clarity and reusability.
MS-PRO-PD-13: Use reference documentation in program development.
MS-PRO-PD-14: Justify the importance of attribution and intellectual property.
MS-PRO-PD-15: Develop a program utilizing inclusive collaboration practices.
MS-PRO-TR-20: Refine a computing technology based on user feedback to improve usability and accessibility.
NETWORKING & DESIGN:
MS-SYS-NT-34: Model how information in a network is broken down into packets, transmitted, and reassembled.
MS-SYS-NT-35: Explain how the resilience of the internet depends on interconnected devices and redundancy.
MS-SYS-IM-36: Collaborate to improve the design of a computing system to meet the needs of diverse users.
MS-ALG-IM-09: Evaluate which human-centered design principles are present or missing in existing technologies.
MS-ALG-IM-11: Modify an algorithm to address a specific societal impact, ethical issue, or bias.