-
Notifications
You must be signed in to change notification settings - Fork 0
Understanding the SDLC
This repository uses a simple development sequence:
Analyze → Design → Construct → Test
The Module Four assignment grades the Design artifact, but the later phases show what the pseudocode is preparing you to do.
Analyze means determining what the program must do before deciding how to express the solution.
For the higher/lower game, analysis includes identifying:
- Inputs
- Validation rules
- The randomly selected value
- Decision outcomes
- Repeated behavior
- Output
- Stopping conditions
The assignment Guidelines and Rubric is the official source. The Sample Output demonstrates expected behavior, and the SRS reorganizes the requirements for easier reference.
Design means deciding how the solution will work before writing executable code.
In Module Four, the graded design artifact is:
- Pseudocode
Your pseudocode must be detailed enough to represent the complete required program flow, including validation, decision branching, and loops.
Construct means translating the design into executable Python code.
Construction is optional practice for this assignment. If you choose to complete it, use your pseudocode as the plan rather than redesigning the program while you code.
Test means checking whether the constructed program behaves as the requirements and design say it should.
Testing is also optional practice in Module Four. Because the game contains branching, validation, and loops, one successful run cannot exercise every path.
The graded assignment focuses on pseudocode, but seeing the later phases helps show why design matters. A useful design should be clear enough to guide construction and specific enough that its behavior can be checked with test scenarios.
Loops make this connection especially important. A loop that does not clearly move toward a stopping condition can become an infinite loop when implemented.