Lists, Loops, and Traversals - Lesson 16: Project - Hackathon Part 4

Overview

This is the fourth day of a five-day unit project. Students continue to build their apps.

Goals

Students will be able to:

• Translate a paper prototype to screens
• Continue programming an app which uses a database

Purpose

Students will demonstrate their app design and programming skills throughout this five day project. In addition, students work with a dataset as this ensures students will be using the types of programming constructs required for the Create Performance Task, which this project is designed as a practice for. Students complete the project by individually filling out a Written Response, modeled after the Create PT.

This project can be used as a unit project, or as an end cap to the first semester of the course.

Resources

• CSP-Widgets repository
• CSP Unit 5 Hackathon Project - Planning Guide

Getting Started (0 minutes)

Do This: Move quickly to the activity portion of the lesson.

Activity (40 minutes)

Hackathon Project

Step 6 (continued): Students work on building their apps, guided by their roles.

• Programmers: Use the table to guide you in adding programming statements to your project.
• Designers: Use the chart to guide you in adding screen elements to your program. You can work on a separate computer from your partner.

Do This: When the designer is ready to share their screens with the programmer, there are specific steps that must be followed after the designer clicks share and copies the link to their app. The programmer:

1. Programmer: Add a blank screen
2. Programmer: Delete the old project screens.
3. Programmer: Click the screen dropdown, then click "Import screen"
4. Designer: Click to share your project. Copy the link and send to the Programmer
5. Programmer: Paste in the link from the designer.
6. Programmer: Select to import all of the screens.
7. Delete the blank screen.
8. Set the home screen to be the default screen (Hint: Go to design mode and click on the screen)

Do This: Take some time around the midpoint of the activity for students to check the Overall Project section of the Scoring Guidelines (final page of the Planning Guide). Update your code as needed to meet the requirements in the Overall Project section.

Wrap Up (5 minutes)

Do This:Remind students that they will be completing the Written Response portion of the project individually during the next lesson. Both students need to fully understand how the program works and have access to the final project.

Planning Guide: As an optional completion assessment, you can look at the table in Step 4 of the Planning Guide.

Assessment: Optional

Standards Alignment

• CSTA K-12 Computer Science Standards (2017): 3A-AP-14, 3A-AP-22, 3A-AP-23

Next Tutorial

In the next tutorial, we will discuss Code.Org Unit 5 Lesson 17, which describes Project Day 5.