Pseudocode

Scenario

You will create a program that will help you manage a collection of recipes.

You will implement three classes: one for the main recipe items, one for the ingredients that are part of the recipe, and one for the entire collection of recipes.

The collection should use a list data structure to store the individual items. Your collection class should include methods like addItem(), printItem(), and deleteItem() that allow you to add, print, or delete items from your collection of items.

Your Ingredient class will model the items that will be stored in each recipe in your collection. You will give it some basic attributes (of numeric or string types) and some basic methods (accessors/mutators, printItemDetails(), etc.).

Your Recipe class will start off similar to your Ingredient class, but you will increase its functionality by modifying it to accept the Ingredient objects, containing all the details stored in an Ingredient class object. You will also expand the Recipe class by adding recipe-specific methods to your Recipe class.

The basic, foundational elements are shown in the following Unified Modeling Language (UML) diagram for the required classes:

Pseudocode for a Collection Manager Program

Overview

Your work on the final project for this course is supported by a series of stepping stone labs. This is the first. Stepping Stone Lab One is an opportunity to consider how to incorporate object-oriented principles to solve a problem in a manner that users can readily engage.

In this lab, you will write pseudocode for the final project scenario program. Pseudocode is a description of how a program will be structured and will operate. It allows a programmer to “think in words” about the design of a program before composing code, and it is also useful for project teams in deciding on basic structures and design.

Prompt

You have been tasked with developing a complete, modular, object-oriented program that will allow for the management of a collection. The scenario provided to you outlines all of the program’s requirements. Refer to the provided scenario to make the determinations for all data types, algorithms and control structures, methods, and classes used in your program.