Create a topic outline to guide the "Incremental Breakdown of Functionality in Pseudocode"

[daaimah123]

👉🏾 First time contributing to this repo? START HERE 👈🏾

To be added as a curriculum contributor and be assigned the related issue, please kindly complete our contributor steps in order to have your PR addressing this issue merged.

Over the course of weeks 2 - 8, participants should work on breaking down logic for prospective functionality of a given problem. This lesson has the use case of being provided a screen recording of an application's various features. The participant should work with their trios and/or their mentors to actively break down the various features, spending a 20-30 minute session on digging into the logic (in pseudocode) for the entire feature's functionality end-to-end as best they are able. Give an expectation that the participants should revisit this exercise each week, trying their hand at a new feature each week.

Breakdown the various stages identified in the following Hoopla Digital screen recording as follows:

• Search
• Results Tiles / Showing Books
• Play View
• Fast Forward
• Rewind
• Categories Options
• Favorites
• Settings

Provide an example walkthrough of pseudocode breakdown for one of the features and which questions arise as you pick apart the logic to guide participants in what they should be considering when breaking down their own attempt at a feature.

The participants will also be learning and building over the weeks concurrently. As such there should be mention of the following:

• revisit their time management slides,
• intentionally breaking down the work implementing and sharing it with their trio or mentor,
• checking in with their trio or their mentor for accountability about support and progress needs.

Page where issue should live

Add the lesson here.

Type of problem

This lesson aims to guide participants in building the skill to breakdown the logic that goes into each piece of functionality.

Suggested Solution

This lesson will enable them with the skill to swiftly breakdown their projects as they grow in complexity, aiding in their ability to implement their logic confidently.