The role of Otto the Robot will now be played by...
Let's watch an introductory video about organizing your thoughts around a problem:
- Show your brand new HTML skills
- Play nicely with other humans
- See how dang picky computers are in one big overworked metaphor
- Program with great style
- Transform all students into mindless robots! MWAAAAAH HAAAA HAAAAAA!
- ___/10 — HTML: Quality of code
- ___/10 — PROCESS: Completion and quality of answers to questions
- ___/10 — STYLE: Indentation, filenames, lower-case HTML tags
Working in groups of 2-4 students, complete the problem solving process to solve the following problem: getting a student from our classroom (sitting in a chair) to the library in the most efficient way. The student must be sitting in a chair in the library for the solution to be complete.
- You will be required to gather other information such as hall distances, number of steps, and location of rooms
- You may want to break down the entire solution into smaller parts (object oriented analysis)
Problem solving process
- Understand the problem (collect info to gather a knowledge base)
- Identify alternative solutions
- Select the best solution
- List the instructions to get to the cafeteria
- Evaluate your solution (test your steps)
OttoCode® — instructing Otto the Robot
The person in your group playing Otto the Robot can only understand these instructions:
FWD— Take a step forward (must be standing)
DWN— Take step down a stair (must be standing)
UP— Take a step up a stair (must be standing)
RT— Turn right
RPT(X)— Repeat instructions x times (x can be any number) — example:
- Otto always begins in a seated position
For example: if you wanted Otto to stand up, turn right, walk four steps forward, then sit down, the OttoCode® would be:
Saving your work
You will discuss your solution through an HTML report that each of you will create individually.
Save the empty template as "
1.04H-OttoTheRobot-LastName.html" in your Computer Programming 12 directory.
- Create the empty framework of your HTML report
- Gather together a team of 2-4 students and start answering questions
- Together, consider three different solutions
- Choose the best solution
- Break your solution down into 5-9 chunks, and then write out the OttoCode® for each chunk
- Do a trial run of your solution with a student volunteering to be Otto
- Complete your HTML report individually and then hand it in
Code an HTML document that looks like this:
Extend & expand
- Can you organize your list of commands into an HTML table?
- Please find a gorgeous picture of Otto to add to your report