# Fitness Friend Lesson 2

This lesson focussed on the key concepts of decomposition and algorithms (pseudocode and flowcharts) as students begin to build their ‘Fitness Friend’ example.

## Curriculum links

**Computing**: Algorithms (pseudocode & flowcharts), input and output devices, iteration, loops, decomposition, logical thinking, debugging**Science**: The heart**P.E.**: The importance of regular exercise**PSHE**: Healthy mind and body

**Skills:** Designing, analysing, problem solving, team working, time management.

## Background

It is assumed that you have first completed Lesson 1 of the Fitness Friend activity.

## Introduction

This lesson focussed on the key concepts of decomposition and algorithms (pseudocode and flowcharts) as students begin to build their ‘Fitness Friend’ example - a wearable device to encourage regular exercise by giving an audio and visual reminder after 25 minutes to move their body.

## Teacher Guide

## Activities

**Algorithm design**

- Show students the problem again (slide 7) and depending on students’ experience either as a class or in pairs write a basic, broad algorithm to solve the problem (slide 8). Ask questions to test understanding and encourage discussion such as:
- will this be detailed enough for someone to code?
- what would we need to do to make it detailed enough?
- Which parts are ambiguous and how would we address that?
- Highlight they have just decomposed the problem into smaller parts and explain they will now design more detailed, accurate algorithms for each part using pseudocode (slide 9).

**Team algorithms**

- Split the class into their teams and give out the algorithm worksheets (ideally on A3 paper).
- Explain you want them to write a detailed algorithm using pseudocode that someone could follow accurately to write the code for the Fitness Friend. They may wish to split the team down to write different sections on rough paper before putting it all together. An example more detailed algorithm is given on slide 10 (with the ‘stop’ command missing) and more detailed on slide 11 including a start and stop button press.

**Testing and refining algorithms**

- Pair up teams and ask them to swop algorithms, test them and give feedback to the other team, comparing and debugging as necessary.
- Come up with a final algorithm as a class, ensuring an appropriate level of detail and accuracy according to your class’ experience and ability and addressing any misconceptions.
- Highlight they are using inputs and outputs (slide 12) and iteration and loops (slide 13).

**Flowcharts **

- Invite students to share why creating a flowchart algorithm can also be helpful alongside or instead of pseudocode (graphical representation of algorithm, can be easier for a person to follow and to see decision points).
- Remind students if needed of the standard flowchart symbols (slide 14) and give each team a large sheet of paper and coloured pens. Ask them to create a flowchart for the algorithm and then share, test and debug as necessary as a class (example on slide 15).

**Lesson wrap up**

- Explain next lesson they will use their algorithms to code the fitness friend next lesson.
- Ask students a variety of questions to test their understanding (suggestions on slide 16).
- If you wish, use the learning objectives to check progress and understanding (slide 17).

**Extension / homework**

- Students can add to their learning log and/or working wall if using.
- They could use the pomodoro technique and report back on if it helped their concentration/and or amount of exercise they did.
- Students could write pseudocode or flowchart algorithms to solve other everyday problems they encounter (e.g. getting out of bed, doing homework, deciding what film to watch, feeding a pet).

### Differentiation

**Support:**

- Consider groupings carefully to ensure all students are able to participate.
- Encourage students to focus on writing a clear, simple algorithm and supply them with a print and cut out version of the basic algorithm to sequence into place.

**Stretch & challenge:**

Students can be challenged to include additional detail and elements in their algorithms. For example, can they include a countdown timer to show how long is left before the next exercise session?

**Opportunities for assessment:**

Informal assessment of team algorithms (pseudocode and flowcharts) and use questioning to assess understanding and progress throughout and in lesson wrap up.