Lesson 10: Maximizing System Reliability

Throughout this year, you've used your software engineer skills to debug your code. Let's think about some examples of bugs in the real world.

Discuss: Use the Retrieve-Pair-Share strategy to discuss the prompt.

• When have you experienced a bug in an application or program that you use that affected system reliability - a system's ability to function without failure?

Discussion Goal: Students share examples of bugs they have experienced, such as a website being down or apps that they use crashing.

It's impossible to completely prevent all bugs in a program. However, as software engineers, there are actions we can take to quickly identify and resolve bugs before they cause significant issues for users.

Do This: Review the lesson objectives.

Group: Place students in pairs.

Distribute: Give each pair two copies of the same version of the Open Source Bugs handout.

Do This: Review the instructions for the Open Source activity.

Now that you are an expert on your Open Source Bug, let's learn about the other bugs.

Discuss: Click through the animated slide to display the prompts.

• What was the bug?
• How widespread was it?
• What is being done to maximize system reliability in the future?

Discussion Goal: Students share the bug they reviewed and the impacts resulting from the bug. Students identify the actions that are being taken to prevent these issues in the future and may also suggest additional actions that can be taken to prevent these issues.

Display: Show the video – The Rise of Open Source Software.

Software engineers often use existing open source software to develop their own programs. They also may choose to develop new programs and make them open source for other people and software engineers to use in their programs.

Discuss: What can you do as software engineers to maximize the reliability of open source software?

Discussion Goal: Students suggest ways to maximize the reliability of open source software, such as contributing code to existing projects or identifying and submitting bugs found in existing projects.

The next five lessons are an opportunity to Show What You Know! We complete our unit project, then spend a day practicing answering AP-style free-response questions and wrapping up the unit with a multiple-choice assessment. You've learned so much in this unit, and now you're ready to show what you know!

Distribute: Give each student a copy of the Unit 7 Study Guide.

Do This: Introduce the Show What You Know week.

Do This: Explain the goals of the project workdays.

Do This: Have students update their Project Planning Board and Project Backlog with any tasks they completed, changed, or added.

Do This: Review the concepts covered in this lesson.

Display: Key Vocabulary

Check For Understanding Question(s) and solutions can be found in each lesson on Code Studio. These questions can be used for an exit ticket.