IT 511 SNHU How to Write Pseudocode Project Your work on the final project for this course is supported by a series of stepping stone labs. This is the first.
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.
To learn more about writing pseudocode, review the How To Write Pseudocode document.
Stepping Stone One is an opportunity to consider how to incorporate object-oriented principles to solve a problem in a manner that users can readily engage.
To complete this assignment, review the Stepping Stone Lab One Guidelines and Rubric document. IT 511 How to Write Pseudocode
Pseudocode is an intermediary step between reading a problem statement and writing the code to solve
the problem. It serves as a blueprint for your program in order to guide you through it, in much the
same way that contractors start with a blueprint before building a house. Use it as a tool to begin
thinking about your program, but keep in mind it might not be the final solution to the problem.
Pseudocode is written in a natural language using some programming keywords. Consider this example:
INCREMENT the number of apples in the basket by one
Notice how the example fully describes, in natural language, what needs to be done in the program.
When writing pseudocode, start at the beginning of what you need the program to do and then work
through step by step until reaching the end of what is required by the program in the problem
statement. This is putting the problem in sequence. For example, making a peanut butter sandwich
could be written as follows:
OBTAIN a plate
OBTAIN two slices of bread
OBTAIN a jar of peanut butter
OBTAIN a knife
Place the slices of bread on the plate
Open the jar of peanut butter
Spread peanut butter on one bread slice with the knife
Place the empty slice of bread on top of the slice with peanut butter
There are several common keywords that get capitalized because they refer to actions taken in the
program. Those words include READ, WRITE, PRINT, DISPLAY, CALCULATE, SET, and INCREMENT. Choices
and loops can be shown in pseudocode. When an item is nested inside another item, indent that line of
pseudocode, just like coding. Below are three generic examples:
IF condition THEN
Include the first sequence
Include the second sequence
Include the sequence
FOR loop parameters
Include the sequence
You can also use the keyword CALL to reference another algorithm written separately. Now look at a
more complete example of both good and bad pseudocode to get a general feel of how to write it:
Bad Example—Vague and Incomplete
Get things for homework
Write the code correctly
Finish the homework
Bad Example—Too Technical, Does Not Follow Natural Language Usage
for (var count = 0; count < problems.length(); count++) solve(); while (!compile) debug(); submit() shutDownComputer(); Good Example–Follows Steps One at a Time Through the End of the Algorithm function doProgrammingHomework(): GET a computer OPEN the learning environment module FOR each of the problems in the module Complete problem WHILE the problem does not compile Debug ENDWHILE Submit the assignment ENDFOR Shut down the computer Remember not to make your pseudocode too technical. You are not trying to write the code itself, just a plan to be used as a stepping stone after the initial problem to get your creative juices flowing. IT 511 Stepping Stone Lab One Guidelines and Rubric 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: Address the following in your submission: A. B. C. D. Analyze the problem your program will solve. This analysis will inform your code logic as you consider how to solve the problem. Break the problem down into distinct steps of pseudocode that will solve the problem. Create variables to track the various elements in the pseudocode; use control structures such as branching or looping. Use natural language to work through the problems. Refer to the How to Write Pseudocode document for guidance. Rubric Guidelines for Submission: This assignment should be submitted as a Microsoft Word document with 12-point Times New Roman font and one-inch margins. Critical Element Assignments Code Logic Decisions or Flow Control Using Branches Proficient (100%) All variables are assigned with logical names and represent relevant values Pseudocode clearly illustrates all of the program’s primary functionality and logic and is self-explanatory Proper decision functionality is clearly defined and correctly applied using a branching structure Need Improvement (70%) Variables are present but do not clearly represent the relevant values Pseudocode illustrates all or most of the program’s primary functionality and logic, but pseudocode is not self-explanatory, has inconsistencies with the program’s functionality, or contains significant errors or gaps in detail Decision functionality is present but is not clearly defined or is applied incorrectly Not Evident (0%) Variables are not assigned Value 10 Pseudocode does not illustrate the program’s primary functionality and logic 30 Decision functionality is not present 20 Iteration or Processing Using Loops Readability and Convertibility Appropriate processing steps and iterations are clearly represented using a loop structure More than one processing step or iteration is incomplete, lacks clarity, or is absent Pseudocode is clear and understandable and the code is organized Pseudocode contains portions that are unclear, difficult to understand, or unorganized Processing steps or iterations are absent or do not represent the proper steps to solve the problem Pseudocode is difficult to understand and is unorganized Total 20 20 100% Purchase answer to see full attachment