IT 140 Module Four Assignment | Pseudocode Revisited

---

Important

GitHub repository options

Do not select Fork or Use this template. These options will interfere with the repository setup commands later in this README.

• 🚫 Fork — Do not use
• 🚫 Use this template — Do not use
• ⭐ Star — The setup commands later in this README will bookmark this repository for you.
• 👁️ Watch
  • Students: Not recommended. Watching is not needed and may generate unnecessary notifications.
  • Faculty: Consider selecting Watch → Custom → Releases + Issues to receive major repository updates and follow reported issues.

---

Note

🆕 New for 2026 C-5: IT 140 now uses GitHub repositories to provide assignment starter files, development resources, and supporting documentation.

If you find a problem with this GitHub repository or its instructions, or have a suggestion for improvement, please open GitHub Issues to review existing issues or create a new issue.

---

• Course: IT 140 - Introduction to Scripting
• Task Title: 4-3: Pseudocode Revisited
• Task Type: Required, graded, one submission required
• Repository Version: 1.0.2
• Repository Version DTG: 2026-08-30-12-56
• Design Problem: Higher/Lower Game
• Graded Deliverable:
  • design/hilow_game.pseudo

Required assignment progress: 0 Start Here → 1 Analyze → 2 Design → 3 Submit

Optional SDLC practice: Construct → Test

Important

The Module Four Assignment Guidelines and Rubric in D2L Brightspace is the official source for assignment requirements, grading criteria, and submission requirements. This repository provides starter files, reference documents, and step-by-step guidance to help you complete those requirements.

What You Are Doing in Module Four

Module Four continues the design-before-code work from Module Three and adds loops to the input/output and decision-branching concepts you have already practiced.

You will design pseudocode for a Higher/Lower Game. The game must:

• obtain and validate lower and upper bounds;
• generate a random number between those bounds;
• obtain and validate guesses;
• distinguish guesses that are too low, too high, or correct; and
• repeat until the correct number is guessed.

The repository also includes optional Python construction and testing practice so you can continue through the complete simplified Software Development Life Cycle (SDLC):

Analyze → Design → Construct → Test

For the graded Module Four assignment, however, your required path is:

Analyze → Design → Submit

Construct and Test are optional practice and do not add graded deliverables.

What You May Edit

Graded and submitted

Edit and submit:

• design/hilow_game.pseudo — graded pseudocode

Working notes; not submitted

You may also edit:

• hilow_game_sdw.md — Software Development Worksheet (SDW) working notes

The SDW is a learning aid. It is not a graded deliverable unless your instructor specifically tells you otherwise.

Optional practice; not submitted

After your graded pseudocode is complete, you may edit:

• src/hilow_game.py — optional Python construction practice

The provided test file is a practice tool. Do not edit it to make a test pass.

Course-provided reference and support files

Do not edit the SRS, SDD, Draw.io file, README files, tests, .github files, repository configuration, or other course-managed files. They provide requirements, guidance, examples, checks, or configuration.

Note

design/hilow_game.drawio is a course-provided reference file. The Module Four assignment does not require a flowchart submission.

0. Meet the Prerequisites

Before starting this assignment:

• Complete the GitHub and Course IDE portions of the Module One Setup Tasks.
• Complete the assigned Module Four zyBooks activities before relying on the assignment to teach loops from the beginning.
• Open the Module Four Assignment Guidelines and Rubric and the Higher/Lower Game Sample Output in D2L Brightspace before editing the starter file.

Relevant Module Four zyBooks topics include:

• 4.1 Loops (general)
• 4.2 While loops
• 4.3 More while examples
• 4.7 While vs. for loops
• 4.9 Developing programs incrementally

Earlier topics on input/output, if/elif/else, relational operators, Boolean expressions, and indentation also apply.

1. Set Up or Open Your Assignment Repository

You create your personal it140-m4-assignment repository only once.

If You Have Not Created It Yet

Use the VS Code integrated terminal. On Windows, use PowerShell or Git Bash, not Command Prompt (cmd.exe).

First confirm the GitHub account you use for IT 140:

gh auth status

If the correct account is not active, use the GitHub CLI sign-in or account-switching instructions from the Module One Setup Tasks before continuing.

Then run:

cd ~/Repos
gh auth setup-git
gh api --method PUT /user/starred/GC-STEM/it140-m4-assignment
gh repo create it140-m4-assignment --template GC-STEM/it140-m4-assignment --private --clone
cd it140-m4-assignment
git remote -v

Confirm that the final remote belongs to your GitHub account.

Note

These creation commands are for the first successful setup only. If a personal repository or local folder already exists, open that existing work instead of creating another repository.

If You Already Created It

Open VS Code and select File > Open Folder, then open:

~/Repos/it140-m4-assignment

If you are on another computer and your personal repository exists on GitHub but not locally, clone your existing repository:

cd ~/Repos
gh repo clone "$(gh api user --jq .login)/it140-m4-assignment"
cd it140-m4-assignment
git status

2. Complete the Assignment

2.1 Analyze the Requirements

Open Analyze Phase.

During Analyze, focus on what the Higher/Lower Game must do. Use:

• the official Guidelines and Rubric in D2L Brightspace;
• the official Higher/Lower Game Sample Output;
• the provided Software Requirements Specification (SRS); and
• the optional Software Development Worksheet (SDW).

Pay particular attention to what repeats and what stops each repetition. The assignment requires validation for both the selected bounds and the player's guesses.

2.2 Create the Graded Pseudocode

Open Design Phase.

Complete:

• design/hilow_game.pseudo

Your pseudocode should logically outline the required game, identify inputs and outputs, and use decision branching and loops to control program flow.

The rubric weights are:

• Logical Steps — 35%
• Input/Output — 30%
• Program Flow — 35%

Review the completed pseudocode against the current Guidelines and Rubric before submission.

2.3 Save Your Work to GitHub

Save your files normally while you work in VS Code. Periodically commit and push your assignment work so your personal GitHub repository contains a current backup.

You can use the Source Control tools in VS Code or run the following from the repository root:

cd ~/Repos/it140-m4-assignment
git status
git add hilow_game_sdw.md design/hilow_game.pseudo src/hilow_game.py
git commit -m "Save Module Four assignment progress"
git push

These commands stage only the student working, graded design, and optional practice files.

If Git reports that there is nothing to commit, your local files do not contain new changes that need to be saved to GitHub.

Note

GitHub is used to develop and back up your work. Assignment submission, grading, and instructor feedback remain in D2L Brightspace.

2.4 Review the Assignment Checks

Each push runs the Assignment Checks workflow in your personal repository.

While you are still working, a red X can simply mean that the graded pseudocode is still in the starter state. As you complete your work, the checks can verify basic repository conditions such as:

• required course files are still present;
• committed changes are limited to student-editable files;
• the graded pseudocode changed from its starter state;
• the pseudocode retains its outer START / END structure;
• starter TODO: prompts are no longer present in the graded pseudocode; and
• course-provided Markdown and configuration remain internally consistent.

The checks also verify that the provided Draw.io reference remains readable, but the Draw.io file is not a graded Module Four deliverable.

The Assignment Checks do not grade the quality or correctness of your pseudocode. A green check is not a grade and does not submit your assignment.

To review a run:

1. Open your personal repository on GitHub.
2. Select Actions.
3. Open the most recent Assignment Checks run.
4. Open Check assignment repository to see the results.

3. Submit Your Assignment

In D2L Brightspace, open the Module Four Assignment and follow the current submission instructions.

Submit exactly the graded design file required by the assignment:

• design/hilow_game.pseudo

Do not submit the SDW, Draw.io reference, optional Python practice file, test file, GitHub Actions output, SRS, SDD, or repository README files unless your instructor specifically requests them.

Optional: Continue Through Construct and Test

After the graded pseudocode is complete and ready to submit, you may continue through the remaining SDLC phases for practice:

1. Construct — translate your own pseudocode into a small Python program.
2. Test — manually test the program and optionally run the provided practice tests.

Optional practice is intended to help you connect design to implementation before the larger course projects. It does not change the one-file Module Four submission.

Restore or Restart Your Assignment Repository

Choose the recovery method that matches the problem. Preserve existing work whenever possible.

Restore a Damaged Local Copy From GitHub

Use this when the copy you previously pushed to GitHub is good but the local folder is damaged or confusing.

CVD, Linux, macOS, or Git Bash on Windows

cd ~/Repos
mv it140-m4-assignment "it140-m4-assignment-local-backup-$(date +%Y%m%d-%H%M%S)"
gh repo clone "$(gh api user --jq .login)/it140-m4-assignment"
cd it140-m4-assignment
git status

Windows PowerShell

cd ~/Repos
Rename-Item it140-m4-assignment "it140-m4-assignment-local-backup-$(Get-Date -Format 'yyyyMMdd-HHmmss')"
gh repo clone "$(gh api user --jq .login)/it140-m4-assignment"
cd it140-m4-assignment
git status

Start Over From the Current Course Template

Use this only when you intentionally want a fresh assignment copy. Preserve the old local folder and GitHub repository first.

CVD, Linux, macOS, or Git Bash on Windows

cd ~/Repos
backup="it140-m4-assignment-backup-$(date +%Y%m%d-%H%M%S)"
mv it140-m4-assignment "$backup"
gh repo rename "$backup" --repo "$(gh api user --jq .login)/it140-m4-assignment" --yes
gh repo create it140-m4-assignment --template GC-STEM/it140-m4-assignment --private --clone
cd it140-m4-assignment
git remote -v

Windows PowerShell

cd ~/Repos
$backup = "it140-m4-assignment-backup-$(Get-Date -Format 'yyyyMMdd-HHmmss')"
Rename-Item it140-m4-assignment $backup
gh repo rename $backup --repo "$(gh api user --jq .login)/it140-m4-assignment" --yes
gh repo create it140-m4-assignment --template GC-STEM/it140-m4-assignment --private --clone
cd it140-m4-assignment
git remote -v

Important

Starting over does not automatically copy work from the preserved repository into the new one.

Help and Support

Use the Module Four Assignment Wiki for supplemental explanations of the SDLC, assignment documents, pseudocode, loops, course IDE tools, Git/GitHub, testing, sources, and AI use.

• Use GitHub Discussions for questions about using this repository that do not request a completed graded solution.
• Use GitHub Issues to report a technical problem with the provided repository, starter files, documentation, automated checks, or course tools.
• Contact your instructor through D2L Brightspace for assignment requirements, grading, feedback, or course-specific questions.

Do not post your completed graded pseudocode publicly when asking for help.