-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the supplemental wiki for the IT 140 Module Three Assignment.
Start with the repository README:
https://github.com/GC-STEM/it140-m3-assignment
The repository 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 Three Assignment Guidelines and Rubric in D2L Brightspace.
The graded Module Three path is:
Analyze → Design → Submit
The two graded design files are:
-
design/paycheck_calculator.drawio— flowchart -
design/paycheck_calculator.pseudo— pseudocode
After your graded designs are complete and ready to submit, the repository also lets you continue through the rest of the simplified SDLC for practice:
Optional: Construct → Test
The optional Python program, automated tests, SDW, SRS, SDD, and repository documentation are not additional Module Three submissions.
| Phase | Main question | What you do | Graded? |
|---|---|---|---|
| Analyze | What must the program do? | Understand the paycheck requirements and boundary cases. | No |
| Design | How should the solution work? | Create the flowchart and pseudocode. | Yes |
| Construct | How can the design become Python? | Optionally implement your own design. | No |
| Test | Does the implementation behave as designed? | Optionally test and debug the Python program. | No |
This assignment intentionally emphasizes design before code.
- Understanding the SDLC — See how Analyze, Design, Construct, and Test fit together and why the graded path stops after Design.
- Understanding the Assignment Documents — Learn the role of the Guidelines and Rubric, SRS, SDD, SDW, starter files, and tests.
- Flowcharts and Pseudocode — Review the two graded design tools without receiving a completed paycheck solution.
- Working in Your Course IDE — Work with Markdown, Draw.io, pseudocode, Source Control, and optional Python in VS Code.
- Testing and Debugging — Trace designs and, if you construct the optional program, use manual and automated tests.
- Git and GitHub During the Assignment — Save and back up your work safely without confusing GitHub with assignment submission.
- Assignment Problems and Support — Choose the right place to ask a question or report a technical problem.
- Sources, Citations, and AI Use — Track outside assistance and follow the current assignment AI guidance.
The Codio Virtual Desktop (CVD) is the IT 140 reference environment. A supported local computer configured through the Module One Setup Tasks can also be used.
Inside VS Code, this assignment uses several file types:
-
.md— Markdown instructions and optional working notes -
.drawio— graded flowchart -
.pseudo— graded pseudocode -
.py— optional Python practice and provided test tools
See Working in Your Course IDE if you are unsure how to open or work with one of these files.
Use the support path that matches the question:
- Assignment requirements, grading, or instructor feedback: D2L Brightspace / your instructor
- How to use the repository: GitHub Discussions
- Technical problem with a provided repository file, tool, documentation, or check: GitHub Issues
- Course IDE setup problem: Module One Setup Tasks and support guidance
See Assignment Problems and Support for details.
When instructions differ, use this order:
- Current Module Three Assignment Guidelines and Rubric in D2L Brightspace
- Current instructions from your instructor
- 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.
The design habits practiced here carry forward into later IT 140 work. Project One asks you to design parts of a larger text-based game before Project Two asks you to implement it. The optional Construct and Test phases in this repository let you practice that same design-to-code transition on a much smaller problem.