-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the supplemental Wiki for the IT 140 Module Four Assignment.
Start with the repository README:
https://github.com/GC-STEM/it140-m4-assignment
The README contains the step-by-step assignment workflow. This Wiki explains concepts and tools that can help you follow those instructions. It does not replace the Module Four Assignment Guidelines and Rubric or the Higher/Lower Game Sample Output in D2L Brightspace.
For the graded Module Four assignment, follow this path:
Analyze → Design → Submit
After the graded pseudocode is complete, you may continue through optional practice:
Construct → Test
The optional phases help you connect design to Python implementation, but they do not create additional graded deliverables.
The assignment has one graded design deliverable:
-
design/hilow_game.pseudo— Higher/Lower Game pseudocode
The official rubric evaluates:
- Logical Steps — 35%
- Input/Output — 30%
- Program Flow — 35%
The course-provided design/hilow_game.drawio file is not a Module Four submission.
| Phase | Main question | Module Four result |
|---|---|---|
| Analyze | What must the game do? | Understand requirements and sample behavior |
| Design | How should the solution work? | Graded hilow_game.pseudo |
| Construct | Can the design become Python? | Optional hilow_game.py practice |
| Test | Does the optional program behave as intended? | Optional manual/automated testing |
| Submit | What goes to D2L? | Only the required .pseudo file |
- Understanding the SDLC — See how Analyze, Design, Construct, and Test fit together in this assignment.
- Understanding the Assignment Documents — Learn the purpose of the Guidelines and Rubric, Sample Output, SRS, SDD, SDW, starter files, and tests.
- Pseudocode, Loops, and Program Flow — Review sequence, validation, branching, repetition, and stopping conditions without receiving a completed assignment solution.
- Working in Your Course IDE — Work with Markdown, pseudocode, and optional Python files in VS Code.
- Testing and Debugging — Trace designs and test the optional Python implementation.
- Git and GitHub During the Assignment — Save and back up your work safely.
- Assignment Problems and Support — Choose the right place to ask a question or report a technical problem.
- Sources, Citations, and AI Use — Keep track of outside help and follow the current assignment AI guidance.
When instructions differ, use this order:
- Current Module Four Assignment Guidelines and Rubric in D2L Brightspace
- Current instructions from your instructor
- Official Higher/Lower Game Sample Output
- Repository README files
- Supplemental Wiki explanations
The repository and Wiki should help you understand and complete the assignment; they should not create additional graded requirements.