Computer Science Standards
Results
Showing 1 - 6 of 6 Standards
Standard Identifier: K-2.CS.3
Grade Range:
K–2
Concept:
Computing Systems
Subconcept:
Troubleshooting
Practice(s):
Testing and Refining Computational Artifacts, Communicating About Computing (6.2, 7.2)
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)
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 Identifier: K-2.NI.5
Grade Range:
K–2
Concept:
Networks & the Internet
Subconcept:
Cybersecurity
Practice(s):
Communicating About Computing (7.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)
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 Identifier: 3-5.CS.3
Grade Range:
3–5
Concept:
Computing Systems
Subconcept:
Troubleshooting
Practice(s):
Testing and Refining Computational Artifacts (6.2)
Standard:
Determine potential solutions to solve simple hardware and software problems using common troubleshooting strategies.
Descriptive Statement:
Although computing systems vary, common troubleshooting strategies can be used across many different systems. Students use troubleshooting strategies to identify problems that could include a device not responding, lacking power, lacking a network connection, an app crashing, not playing sounds, or password entry not working. Students use and develop various solutions to address these problems. Solutions may include rebooting the device, checking for power, checking network availability, opening and closing an app, making sure speakers are turned on or headphones are plugged in, and making sure that the caps lock key is not on. For example, students could prepare for and participate in a collaborative discussion in which they identify and list computing system problems and then describe common successful fixes. (CA CCSS for ELA/Literacy SL.3.1, SL.4.1, SL.5.1) Alternatively, students could write informative/explanatory texts, create a poster, or use another medium of communication to examine common troubleshooting strategies and convey these ideas and information clearly. (CA CCSS for ELA/Literacy W.3.2, W.4.2, W.5.2)
Determine potential solutions to solve simple hardware and software problems using common troubleshooting strategies.
Descriptive Statement:
Although computing systems vary, common troubleshooting strategies can be used across many different systems. Students use troubleshooting strategies to identify problems that could include a device not responding, lacking power, lacking a network connection, an app crashing, not playing sounds, or password entry not working. Students use and develop various solutions to address these problems. Solutions may include rebooting the device, checking for power, checking network availability, opening and closing an app, making sure speakers are turned on or headphones are plugged in, and making sure that the caps lock key is not on. For example, students could prepare for and participate in a collaborative discussion in which they identify and list computing system problems and then describe common successful fixes. (CA CCSS for ELA/Literacy SL.3.1, SL.4.1, SL.5.1) Alternatively, students could write informative/explanatory texts, create a poster, or use another medium of communication to examine common troubleshooting strategies and convey these ideas and information clearly. (CA CCSS for ELA/Literacy W.3.2, W.4.2, W.5.2)
Standard Identifier: 6-8.CS.3
Grade Range:
6–8
Concept:
Computing Systems
Subconcept:
Troubleshooting
Practice(s):
Testing and Refining Computational Artifacts (6.2)
Standard:
Systematically apply troubleshooting strategies to identify and resolve hardware and software problems in computing systems.
Descriptive Statement:
When problems occur within computing systems, it is important to take a structured, step-by-step approach to effectively solve the problem and ensure that potential solutions are not overlooked. Examples of troubleshooting strategies include following a troubleshooting flow diagram, making changes to software to see if hardware will work, checking connections and settings, and swapping in working components. Since a computing device may interact with interconnected devices within a system, problems may not be due to the specific computing device itself but to devices connected to it. For example, students could work through a checklist of solutions for connectivity problems in a lab of computers connected wirelessly or through physical cables. They could also search for technical information online and engage in technical reading to create troubleshooting documents that they then apply. (CA CCSS for ELA/Literacy RST.6-8.10) Alternatively, students could explore and utilize operating system tools to reset a computer's default language to English. Additionally, students could swap out an externally-controlled sensor giving fluctuating readings with a new sensor to check whether there is a hardware problem.
Systematically apply troubleshooting strategies to identify and resolve hardware and software problems in computing systems.
Descriptive Statement:
When problems occur within computing systems, it is important to take a structured, step-by-step approach to effectively solve the problem and ensure that potential solutions are not overlooked. Examples of troubleshooting strategies include following a troubleshooting flow diagram, making changes to software to see if hardware will work, checking connections and settings, and swapping in working components. Since a computing device may interact with interconnected devices within a system, problems may not be due to the specific computing device itself but to devices connected to it. For example, students could work through a checklist of solutions for connectivity problems in a lab of computers connected wirelessly or through physical cables. They could also search for technical information online and engage in technical reading to create troubleshooting documents that they then apply. (CA CCSS for ELA/Literacy RST.6-8.10) Alternatively, students could explore and utilize operating system tools to reset a computer's default language to English. Additionally, students could swap out an externally-controlled sensor giving fluctuating readings with a new sensor to check whether there is a hardware problem.
Standard Identifier: 9-12.CS.3
Grade Range:
9–12
Concept:
Computing Systems
Subconcept:
Troubleshooting
Practice(s):
Testing and Refining Computational Artifacts (6.2)
Standard:
Develop guidelines that convey systematic troubleshooting strategies that others can use to identify and fix errors.
Descriptive Statement:
Troubleshooting complex problems involves the use of multiple sources when researching, evaluating, and implementing potential solutions. Troubleshooting also relies on experience, such as when people recognize that a problem is similar to one they have seen before and adapt solutions that have worked in the past. For example, students could create a list of troubleshooting strategies to debug network connectivity problems such as checking hardware and software status and settings, rebooting devices, and checking security settings. Alternatively, students could create troubleshooting guidelines for help desk employees based on commonly observed problems (e.g., problems connecting a new device to the computer, problems printing from a computer to a network printer).
Develop guidelines that convey systematic troubleshooting strategies that others can use to identify and fix errors.
Descriptive Statement:
Troubleshooting complex problems involves the use of multiple sources when researching, evaluating, and implementing potential solutions. Troubleshooting also relies on experience, such as when people recognize that a problem is similar to one they have seen before and adapt solutions that have worked in the past. For example, students could create a list of troubleshooting strategies to debug network connectivity problems such as checking hardware and software status and settings, rebooting devices, and checking security settings. Alternatively, students could create troubleshooting guidelines for help desk employees based on commonly observed problems (e.g., problems connecting a new device to the computer, problems printing from a computer to a network printer).
Standard Identifier: 9-12.NI.6
Grade Range:
9–12
Concept:
Networks & the Internet
Subconcept:
Cybersecurity
Practice(s):
Communicating About Computing (7.2)
Standard:
Compare and contrast security measures to address various security threats.
Descriptive Statement:
Network security depends on a combination of hardware, software, and practices that control access to data and systems. The needs of users and the sensitivity of data determine the level of security implemented. Potential security problems, such as denial-of-service attacks, ransomware, viruses, worms, spyware, and phishing, present threats to sensitive data. Students compare and contrast different types of security measures based on factors such as efficiency, feasibility, ethical impacts, usability, and security. At this level, students are not expected to develop or implement the security measures that they discuss. For example, students could review case studies or current events in which governments or organizations experienced data leaks or data loss as a result of these types of attacks. Students could provide an analysis of actual security measures taken comparing to other security measure which may have led to different outcomes. Alternatively, students might discuss computer security policies in place at the local level that present a tradeoff between usability and security, such as a web filter that prevents access to many educational sites but keeps the campus network safe.
Compare and contrast security measures to address various security threats.
Descriptive Statement:
Network security depends on a combination of hardware, software, and practices that control access to data and systems. The needs of users and the sensitivity of data determine the level of security implemented. Potential security problems, such as denial-of-service attacks, ransomware, viruses, worms, spyware, and phishing, present threats to sensitive data. Students compare and contrast different types of security measures based on factors such as efficiency, feasibility, ethical impacts, usability, and security. At this level, students are not expected to develop or implement the security measures that they discuss. For example, students could review case studies or current events in which governments or organizations experienced data leaks or data loss as a result of these types of attacks. Students could provide an analysis of actual security measures taken comparing to other security measure which may have led to different outcomes. Alternatively, students might discuss computer security policies in place at the local level that present a tradeoff between usability and security, such as a web filter that prevents access to many educational sites but keeps the campus network safe.
Questions: Curriculum Frameworks and Instructional Resources Division |
CFIRD@cde.ca.gov | 916-319-0881