About Us
Our Team
Our Impact
Contact Us
Corporate Programs

Get Creative with Coding

Page Views: 81

Email This Lesson Plan to Me
Email Address:
Subscribe to Newsletter?
Log in to rate this plan!
Overall Rating:
(5.0 stars, 1 ratings)

Keywords: Robotics, Coding,
Subject(s): Robotics
Grades 9 through 12
NETS-S Standard:
  • Creativity and Innovation
  • Critical Thinking, Problem Solving, and Decision Making
View Full Text of Standards
School: Greenup Co High School, Greenup, KY
Planned By: Kristina Brown
Original Author: Kristina Brown, Greenup
1. Students will be provided a background article "“Robots: Star Wars vs. the Real World” to read.

2. Students will be given the challenge: Write code using symbols that will direct a classmate to create a specific structure by stacking at least 10 plastic cups.

3. Students must use the criteria and constraints listed: a) the stack must have more than one level; b) your algorithm may include a maximum of 10 different types of actions, such as Pick up a cup or Move a cup forward; and c) your code must include one simple symbol for each action, such as an arrow.

4. Students will draw a diagram of what they want their finished stack of cups to look like. This will be done in their lab notebook.

5. Students will need to think about how they want someone to build their stack of cups. Which cups need to be placed first? What will need to happen after that? In their lab notebook, they will write out directions, in complete sentences, that someone could follow to create their design. Test it out and make any needed revisions.

6. Students will look over their algorithm and determine what symbols they will use for each action. Students will write a key that explains the action represented by each symbol. Students will translate their algorithm into code, using their symbols.

7. Students will test their code by using the Scratch program (scratch.mit.edu). They will code a sprite in the program to follow the algorithm they have written. If it doesn't work, students will determine what didn’t work and revise their code. Students will then test it again and determine if it worked. Students will explain what they did to fix the errors in, or debug, their code.
Links: Article Link
Materials: Mobile Labs, Web Page