Search the California Content Standards

Standard:
Develop plans that describe a program’s sequence of events, goals, and expected outcomes.

Descriptive Statement:
Creating a plan for what a program will do clarifies the steps that will be needed to create the program and can be used to check if a program runs as expected. Students create a planning document to illustrate their program's sequence of events, goals, and expected outcomes of what their program will do. Planning documents could include a story map, a storyboard, or a sequential graphic organizer, to illustrate their program's sequence of events, goals, and expected outcomes of what their program will do. Students at this level may complete the planning process with help from the teacher. For example, students could create a storyboard or timeline that represents a family's history, leading to their current location of residence. Students could then create a plan for a program that animates the story of family locations. (HSS 2.1.1) (CA CCSS for ELA/Literacy W.K.3, W.1.3, W.2.3)

Standard:
Give attribution when using the ideas and creations of others while developing programs.

Descriptive Statement:
Computing makes it easy to reuse and remix others' creations, and this comes with a level of responsibility. Students credit artifacts that were created by others, such as pictures, music, and code. Credit could be given orally if presenting their work to the class, or in writing if sharing work on a class blog or website. Proper attribution at this stage does not require formal citation, such as in a bibliography or works cited document. For example, when creating an animation of the sun, moon, and stars using a blocks-based language, students could draw their own sun and use an image of the moon and stars from a website or a teammate. When students present the model to the class, they can orally give credit to the website or peer for the contributions. (CA CCSS for ELA/Literacy SL.K.5, SL.1.5, SL.2.5) (NGSS.1-ESS1-1) (CA Model School Library Standards 2.3.b, 2.4.2.a)

Standard:
Describe the steps taken and choices made during the iterative process of program development.

Descriptive Statement:
Program developers make choices and iterate to continually refine their product. At this stage, students explain or write about the goals and expected outcomes of the programs they create and the choices that they made when creating programs. Students could use coding journals, discussions with a teacher, class presentations, or blogs. For example, students could use a combination of images, verbal reflections, a physical model, and/or written text to show the step-by-step process taken to develop a program such as cutting and pasting coding commands into a journal, using manipulatives that represent different commands and control structures, and taking screenshots of code and adding to a digital journal. This iterative process could be documented via a speech, journal, one on one conference with teacher or peer, small group conference, or blog. (CA CCSS for ELA/Literacy SL.K.5, SL.1.5, SL.2.5) (CA NGSS: K-2-ETS1.2)

Standard:
Explain the functions of common hardware and software components of computing systems.

Descriptive Statement:
A computing system is composed of hardware and software. Hardware includes the physical components of a computer system. Software provides instructions for the system. These instructions are represented in a form that a computer can understand and are designed for specific purposes. Students identify and describe the function of hardware, such as desktop computers, laptop computers, tablet devices, monitors, keyboards, mice, trackpads, microphones, and printers. Students also identify and describe common software applications such as web browsers, games, and word processors. For example, students could create drawings of a computing system and label its major components with appropriate terminology. Students could then explain the function of each component. (VAPA Visual Arts 2 5.0) (CA CCSS for ELA/Literacy SL.K.5, SL.K.6, SL.1.5, SL.1.6, SL.2.5, SL.2.6) Alternatively, students could each be assigned a component of a computing system and arrange their bodies to represent the system. Students could then describe how their assigned component functions within the system. (P.E.K.1, 1.1)

Standard:
Describe basic hardware and software problems using accurate terminology.

Descriptive Statement:
Problems with computing systems have different causes. Accurate description of the problem aids users in finding solutions. Students communicate a problem with accurate terminology (e.g., when an app or program is not working as expected, a device will not turn on, the sound does not work, etc.). Students at this level do not need to understand the causes of hardware and software problems. For example, students could sort hardware and software terms on a word wall, and refer to the word wall when describing problems using "I see..." statements (e.g., "I see the pointer on the screen is missing", "I see that the computer will not turn on"). (CA CCSS for ELA/Literacy L.K.5.A, L.1.5.A, SL K.5, SL1.5, SL 2.5) (Visual Arts Kinder 5.2) Alternatively, students could use appropriate terminology during collaborative conversations as they learn to debug, troubleshoot, collaborate, and think critically with technology. (CA CCSS for ELA/Literacy SL.K.1, SL.1.1, SL.2.1)

Standard:
Collect and present data in various visual formats.

Descriptive Statement:
Data can be collected and presented in various visual formats. For example, students could measure temperature changes throughout a day. They could then discuss ways to display the data visually. Students could extend the activity by writing different narratives based on collected data, such as a story that begins in the morning when temperatures are low and one that begins in the afternoon when the sun is high and temperatures are higher. (CA CCSS for ELA/Literacy RL.K.9, RL.1.9, RL.2.9, W.K.3, W.1.3, W.2.3). Alternatively, students collect peers' favorite flavor of ice cream and brainstorm differing ways to display the data. In groups, students can choose to display and present the data in a format of their choice. (CA CCSS for Mathematics K.MD.3, 1.MD.4, 2.MD.10)

Standard:
Work respectfully and responsibly with others when communicating electronically.

Descriptive Statement:
Electronic communication facilitates positive interactions, such as sharing ideas with many people, but the public and anonymous nature of electronic communication also allows intimidating and inappropriate behavior in the form of cyberbullying. Responsible electronic communication includes limiting access to personably identifiable information. Students learn and use appropriate behavior when communicating electronically (often called "netiquette"). For example, students could share their work on a classroom blog or in other collaborative spaces online, taking care to avoid sharing information that is inappropriate or that could personally identify themselves to others. (CA CCSS for ELA/Literacy W.K.6, W.1.6, W.21.6) Alternatively, students could provide feedback to others on their work in a kind and respectful manner. They could learn how written words can be easily misinterpreted and may seem negative when the intention may be to express confusion, give ideas, or prompt further discussion. They could also learn to identify harmful behavior on collaborative spaces and intervening to find the proper authority to help. (CA CCSS for ELA/Literacy W.K.5, W.1.5, W.2.5) (HSS 1.1.2)

Standard:
Explain why people use passwords.

Descriptive Statement:
Passwords protect information from unwanted use by others. When creating passwords, people often use patterns of familiar numbers and text to more easily remember their passwords. However, this may make the passwords weaker. Knowledge about the importance of passwords is an essential first step in learning about cybersecurity. Students explain that strong passwords are needed to protect devices and information from unwanted use. For example, students could play a game of guessing a three-character code. In one version of the game, the characters are only numbers. In the second version, characters are numbers or letters. Students describe why it would take longer to guess the correct code in the second case. Alternatively, students could engage in a collaborative discussion regarding passwords and their importance. Students may follow-up the discussion by exploring strong password components (combination of letters, numbers, and characters), creating their own passwords, and writing opinion pieces indicating reasons their passwords are strong. (CA CCSS for ELA/Literacy SL.K.1, SL.1.1, SL 2.1, W.1.1, W.2.1)

Standard:
Observe intellectual property rights and give appropriate attribution when creating, remixing, or combining programs.

Descriptive Statement:
Intellectual property rights can vary by country, but copyright laws give the creator of a work a set of rights and prevents others from copying the work and using it in ways that they may not like. Students consider common licenses that place limitations or restrictions on the use of others' work, such as images and music downloaded from the Internet. When incorporating the work of others, students attribute the work. At this level, students could give attribution by including credits or links directly in their programs, code comments, or separate project pages. For example, when making a program to model the life cycle of a butterfly, students could modify and reuse an existing program that describes the life cycle of a frog. Based on their research, students could identify and use Creative Commons-licensed or public domain images and sounds of caterpillars and butterflies. Students give attribution by properly citing the source of the original piece as necessary. (CA NGSS: 3-LS-1-1) (CA CCSS for ELA/Literacy W.3.8, W.4.8, W.5.8) Alternatively, when creating a program explaining the structure of the United States goverment, students find Creative Commons-licensed or public domain images to represent the three branches of government and attribute ownership of the images appropriately. If students find and incorporate an audio file of a group playing part of the national anthem, they appropriately give attribution on the project page. (HSS.3.4.4)

Standard:
Perform different roles when collaborating with peers during the design, implementation, and review stages of program development.

Descriptive Statement:
Collaborative computing is the process of creating computational artifacts by working in pairs or on teams. It involves asking for the contributions and feedback of others. Effective collaboration can often lead to better outcomes than working independently. With teacher guidance, students take turns in different roles during program development, such as driver, navigator, notetaker, facilitator, and debugger, as they design and implement their program. For example, while taking on different roles during program development, students could create and maintain a journal about their experiences working collaboratively. (CA CCSS for ELA/Literacy W.3.10, W.4.10, W.5.10) (CA NGSS: 3-5-ETS1-2)