Architect Simulator
Experience: 1st year, 4th quarter
Practice: Creating computational artifacts, Testing and refining computational artifacts, and Communicating about computing
Concept: Algorithms, Control, and Modularity
Length: 60+
Overview and Purpose
Coders combine their previous understandings of using pen blocks to create an app that allows users to create architecture with blocks. The purpose of this project is to reinforce understandings of modularity and user interaction by combining previous understandings within a new context.
Project Extensions
Suggested extensions
Add sounds for each user interaction (10+ minutes):
*3+ minute demonstration*
Demonstrate creating a message block for each interaction you want to add sound to and put them in the code for one of the block sprites. Select and add a sound for each interaction in the backdrops (we are using the backdrops so we don’t have to repeat this process for each sprite). Start the appropriate sound with each When I receive message block.
Ask the class how we could vary the sound so it's not the same every time. Create a new function (My Blocks) that will randomize the pitch of a sound. In the new function, place a pick random -10 to 10 block inside a set pitch effect block to randomly change the sound to a lower or higher pitch; this is a technique game designers use to make it so repeated sounds (e.g., footsteps) are not the same every time. Place this block above any of your start/play sound blocks and test the user interactions to make sure the new sounds work.
7+ minute coding time and 1-on-1 facilitating
Give time for coders to add their own sounds and audio effects for each of the user interactions they added to their projects.
Resources, suggestions, and connections
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
- Modularity
Video: Randomize a single sound (3:08)
Quick reference guide: Click here
Video: Customize sounds (3:21)
Quick Reference Guide: Click here
Suggested questions:
- How can you vary the sounds to make them more interesting?
- Why did we put the sounds in the backdrop instead of each sprite?
- It’s much easier to add/change the code when it’s in one location instead of several.
- In addition, although this is an advanced topic for elementary coders, this also means we are using less memory because we are not using duplicate sound files or code in the same project.
- How else could you randomize the sound?
- What else could you randomize in this project?
- What sound effects could you use in the Sounds tab to change the way your recording sounds?
- What do each of the tools in the Sounds tab do?
Create an erase button (10+ minutes):
*1+ minute demonstration*
Demonstrate the erase button in the example project. Point out that the costume switches when the mouse is touching it (or not touching it); however, it doesn’t erase until the sprite is clicked. Ask coders if they can figure out interesting ways to add an erase button in their project.
If needed, review one of the following examples:
- Video: Create custom buttons (2:03)
- Video: Code your buttons (2:41)
- Video: Indicate a button is pressed (2:55)
9+ minute coding time and 1-on-1 facilitating
Give time for coders to code their own erase button.
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
- Modularity
Video: Create an erase button (2:14)
Quick reference guide: Click here
Suggested questions:
- What other buttons could we add to this project?
- How could we add an erase function without using a button?
- For example, erase the screen when the user presses the ‘x’ key on the keyboard.
Prevent blocks from stamping on the menu (10+ minutes):
2+ minute demonstration
Select one of the block sprites and add an if block around the stamp block. Mention that for our condition, we want to check to see if the y position is greater than -140. This will allow us to stamp if the sprite is above -140, otherwise it won’t do anything (because it’s not an if/else block). Let the class know we could have used a sensing block to check to see if we were touching the color of the menu; however, this could have created a glitch if one of our stamped blocks was the same color as the menu. Another option is to demonstrate turning the menu bar into a sprite and moving the sprite behind the other sprites (see the video or quick reference guide for more details).
8+ minute coding time and 1-on-1 facilitating
Give time for coders to add their own sounds and audio effects for each of the user interactions they added to their projects.
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Control
Video: Prevent blocks from stamping on the menu (5:05)
Quick reference guide: Click here
Facilitation Suggestion: Some coders may not thrive in inquiry based approaches to learning, so we can encourage them to use the Tutorials to get more ideas for their projects; however, we may need to remind coders the suggestions provided by Scratch are not specific to our projects, so it may create some unwanted results unless the code is modified to match our own intentions.
Suggested questions:
- What would you need to change in the code if the menu was at the top of the screen?
- What about on one of the sides?
- What about if there were multiple menus?
Use the example project as a guide (as needed)
At some point, coders might get stuck or run out of ideas. Rather than explaining to them how to do something, ask them to open the example project, read the comments inside the various sprites and then look at the code to see if they can figure out how to solve their problem. Although this is a very open-ended approach, this models a common coding practice that helps coders become independent learners.
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
- 1B-AP-12 Modify, remix, or incorporate portions of an existing program into one's own work, to develop something new or add more advanced features
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
- Modularity
Resource: Example project
Facilitation Suggestion: Some coders may not thrive in inquiry based approaches to learning, so we can encourage them to use the Tutorials to get more ideas for their projects; however, we may need to remind coders the suggestions provided by Scratch are not specific to our projects, so it may create some unwanted results unless the code is modified to match our own intentions.
Snap blocks to a grid (Advanced) (10+ minutes):
*5+ minute demonstration*
Pull up the code in the example project that snaps the blocks to a grid. Explain that the sprites are 16 pixels high and 32 pixels wide, so the code in the example project snaps all of the blocks to a 16 pixel grid. We are able to snap to a grid by using the fancy equation instead of using a go to mouse-pointer block. If kids are really interested in how this works, feel free to share the video or quick reference guide, or provide your own walkthrough of the equation.
*Here’s the equation to snap to a 16 pixel grid: *
(round (mouse coordinate / 16)) * 16
5+ minute coding time and 1-on-1 facilitating
Give time for coders to copy the equation on the screen into each sprite. Encourage experimentation by using different paired numbers (e..g., trying using 32 and 32 instead of 16 and 16).
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
- Modularity
Video: Snap Blocks to a Grid (Advanced) (4:50)
Quick reference guide: Click here
Suggested questions:
- What happens when you change the numbers to 8/8, 32/32, 48/48, or 64/64?
Add even more (30+ minutes, or at least one class):
If time permits and coders are interested in this project, encourage coders to explore what else they can create in Scratch by trying out new blocks and reviewing previous projects to get ideas for this project. When changes are made, encourage them to alter their comments to reflect the changes (either in the moment or at the end of class).
While facilitating this process, monitor to make sure coders don’t stick with one feature for too long. In particular, coders like to edit their sprites/backgrounds by painting on them or taking photos, or listen to the built-in sounds in Scratch. It may help to set a timer for creation processes outside of using blocks so coders focus their efforts on coding.
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
Practices reinforced:
- Creating computational artifacts
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
Facilitation Suggestion: Some coders may not thrive in inquiry based approaches to learning, so we can encourage them to use the Tutorials to get more ideas for their projects; however, we may need to remind coders the suggestions provided by Scratch are not specific to our projects, so it may create some unwanted results unless the code is modified to match our own intentions.
Suggested questions:
- What else can you do with Scratch?
- What do you think the other blocks do?
- Can you make your project do ____?
- What other sprites can you add to your project?
- What have you learned in other projects that you could use in this project?
- Can you add user controls?
- Examples: change the size of the drawing, change the backdrop or sprite, change the speed of the cat, press a button to reset the screen, etc.
- How else might you use pen blocks in your project?
- How could you control the blocks using only your keyboard instead of your mouse?
- What about using your device’s camera?
Similar projects:
Have coders explore the code of other peers in their class, or on a project studio dedicated to this project. Encourage coders to ask questions about each other’s code. When changes are made, encourage coders to alter their comments to reflect the changes (either in the moment or at the end of class).
Watch this video (3:20) if you are unsure how to use a project studio.
Standards reinforced:
- 1B-AP-10 Create programs that include sequences, events, loops, and conditionals
- 1B-AP-12 Modify, remix, or incorporate portions of an existing program into one's own work, to develop something new or add more advanced features
Practices reinforced:
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
Note: Coders may need a gentle reminder we are looking at other projects to get ideas for our own project, not to simply play around. For example, “look for five minutes,” “look at no more than five other projects,” “find three projects that each do one thing you would like to add to your project,” or “find X number of projects that are similar to the project we are creating.”
Generic questions:
- What are some ways you can expand this project beyond what it can already do?
- How is this project similar (or different) to something you worked on today?
- What blocks did they use that you didn’t use?
- What do you think those blocks do?
- What’s something you like about their project that you could add to your project?
- How could you add pen blocks to this project?
- If they’re already using pen blocks, why do you think they used the blocks they have and not others?
micro:bit extensions:
Note: the micro:bit requires installation of Scratch Link and a HEX file before it will work with a computer. Watch this video (2:22) and use this guide to learn how to get started with a micro:bit before encouraging coders to use the micro:bit blocks.
Much like the generic Scratch Tips folder linked in each Coder Resources document, the micro:bit Tips folder contains video and visual walkthroughs for project extensions applicable to a wide range of projects. Although not required, the micro:bit Tips folder uses numbers to indicate a suggested order for learning about using a micro:bit in Scratch; however, coders who are comfortable with experimentation can skip around to topics relevant to their project.
Standards reinforced:
1B-AP-09 Create programs that use variables to store and modify data
1B-AP-10 Create programs that include sequences, events, loops, and conditionals
1B-AP-11 Decompose (break down) problems into smaller, manageable subproblems to facilitate the program development process
1B-AP-15 Test and debug (identify and fix errors) a program or algorithm to ensure it runs as intended
Practices reinforced:
- Recognizing and defining computational problems
- Creating computational artifacts
- Developing and using abstractions
- Fostering an inclusive computing culture
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
- Modularity
- Program Development
- Variables
Folder with all micro:bit quick reference guides: Click here
Additional Resources:
- Printable micro:bit cards
- Micro:bit’s Scratch account with example projects
Generic questions:
- How can you use a micro:bit to add news forms of user interaction?
- What do the different micro:bit event blocks do and how could you use them in a project?
- How could you use the LED display for your project?
- What do the tilt blocks do and how could you use them in your project?
- How could you use the buttons to add user/player controls?
- How might you use a micro:bit to make your project more accessible?
Differentiation
Less experienced coders
Demonstrate the example remix project or your own version, and walk through how to experiment changing various parameters or blocks to see what they do. Give some time for them to change the blocks around. When it appears a coder might need some guidance or has completed an idea, encourage them to add more to the project or begin following the steps for creating the project on their own (or with BootUp resources). Continue to facilitate one-on-one using questioning techniques to encourage tinkering and trying new combinations of code.
If you are working with other coders and want to get less experienced coders started with remixing, have those who are interested in remixing a project watch this video (2:42) to learn how to remix a project.
More experienced coders
Demonstrate the project without showing the code used to create the project. Challenge coders to figure out how to recreate a similar project without looking at the code of the original project. If coders get stuck reverse engineering, use guiding questions to encourage them to uncover various pieces of the project. Alternatively, if you are unable to work with someone one-on-one at a time of need, they can access the quick reference guides and video walkthroughs above to learn how each part of this project works.
If you are working with other coders and want to get more experienced coders started with reverse engineering, have those who are interested watch this video (2:30) to learn how to reverse engineer a project.
Debugging Exercises (1-5+ minutes each)
Debugging exercises
Resources and suggestions
Standards reinforced:
- 1B-AP-15 Test and debug (identify and fix errors) a program or algorithm to ensure it runs as intended
Practices reinforced:
- Testing and refining computational artifacts
Concepts reinforced:
- Algorithms
- Control
Suggested guiding questions:
- What should have happened but didn’t?
- Which sprite(s) do you think the problem is located in?
- What code is working and what code has the bug?
- Can you walk me through the algorithm (steps) and point out where it’s not working?
- Are there any blocks missing or out of place?
- How would you code this if you were coding this algorithm from Scratch?
- Another approach would be to read the question out loud and give hints as to what types of blocks (e.g., motion, looks, event, etc.) might be missing.
Reflective questions when solved:
- What was wrong with this code and how did you fix it?
- Is there another way to fix this bug using different code or tools?
- If this is not the first time they’ve coded: How was this exercise similar or different from other times you’ve debugged code in your own projects or in other exercises?
Unplugged Lessons and Resources
Although each project lesson includes suggestions for the amount of class time to spend on a project, BootUp encourages coding facilitators to supplement our project lessons with resources created by others. In particular, reinforcing a variety of standards, practices, and concepts through the use of unplugged lessons. Unplugged lessons are coding lessons that teach core computational concepts without computers or tablets. You could start a lesson with a short, unplugged lesson relevant to a project, or use unplugged lessons when coders appear to be struggling with a concept or practice.
List of 100+ unplugged lessons and resources
Incorporating unplugged lessons in the middle of a multi-day project situates understandings within an actual project; however, unplugged lessons can occur before or after projects with the same concepts. An example for incorporating unplugged lessons:
Lesson 1. Getting started sequence and beginning project work
Lesson 2. Continuing project work
Lesson 3. Debugging exercises and unplugged lesson that reinforces concepts from a project
Lesson 4. Project extensions and sharing
Reflection and Sharing
Reflection suggestions
Coders can either discuss some of the following prompts with a neighbor, in a small group, as a class, or respond in a physical or digital journal. If reflecting in smaller groups or individually, walk around and ask questions to encourage deeper responses and assess for understanding. Here is a sample of a digital journal designed for Scratch (source) and here is an example of a printable journal useful for younger coders.
Sample reflection questions or journal prompts:
- How did you use computational thinking when creating your project?
- What’s something we learned while working on this project today?
- What are you proud of in your project?
- How did you work through a bug or difficult challenge today?
- What other projects could we do using the same concepts/blocks we used today?
- What’s something you had to debug today, and what strategy did you use to debug the error?
- What mistakes did you make and how did you learn from those mistakes?
- How did you help other coders with their projects?
- What did you learn from other coders today?
- What questions do you have about coding?
- What was challenging today?
- Why are comments helpful in our projects?
- How is this project similar to other projects you’ve worked on?
- How is it different?
- How else could you use the stamp block?
- What other apps could you create in Scratch?
- What other user interaction could you add to this project?
- More sample prompts
Sharing suggestions
Standards reinforced:
- 1B-AP-17 Describe choices made during program development using code comments, presentations, and demonstrations
Practices reinforced:
- Communicating about computing
- Fostering an inclusive culture
Concepts reinforced:
- Algorithms
- Control
- Modularity
- Program development
Peer sharing and learning video: Click here (1:33)
At the end of class, coders can share with each other something they learned today. Encourage coders to ask questions about each other’s code or share their journals with each other. When sharing code, encourage coders to discuss something they like about their code as well as a suggestion for something else they might add.
Publicly sharing Scratch projects: If coders would like to publicly share their Scratch projects, they can follow these steps:
- Video: Share your project (2:22)
- Video (Advanced): Create a thumbnail (4:17)