Skip to content

Understanding the Assignment Documents

mike-snhu edited this page Aug 16, 2026 · 2 revisions

Understanding the Assignment Documents

This repository and the course contain several documents because each serves a different purpose in the development process.

Assignment Guidelines and Rubric

The Module Four Assignment Guidelines and Rubric in D2L Brightspace is the official source for:

  • Assignment requirements
  • Grading criteria
  • Required file format
  • Submission requirements
  • Current AI-use guidance

Read it before the repository documents and return to it before submitting.

Higher/Lower Game Sample Output

The Higher/Lower Game Sample Output in D2L Brightspace shows example program behavior.

Use it to observe:

  • The order in which inputs are requested
  • How invalid bounds cause another attempt
  • How the program responds to guesses
  • How guessing repeats
  • What happens when the correct number is guessed

The sample document notes that the output messages in your pseudocode may differ slightly. Treat the examples as evidence of required behavior, not as a script that every output sentence must copy exactly.

Software Requirements Specification (SRS)

File:

analysis/hilow_game_srs.md

The SRS reorganizes the stated problem into requirements and acceptance conditions. It helps answer:

What must the solution do?

Do not edit the provided SRS.

Software Design Document (SDD)

File:

design/hilow_game_sdd.md

The SDD explains design goals, loops, branching, and review checks without supplying completed pseudocode. It helps answer:

What must my design make clear?

Do not edit the provided SDD.

Software Development Worksheet (SDW)

File:

hilow_game_sdw.md

The SDW is optional working space for brief notes while you move through the SDLC. It is not a graded deliverable.

You may edit it.

Pseudocode Template

File:

design/hilow_game.pseudo

This is the graded deliverable. Replace the TODO: prompts with your own pseudocode while keeping the required .pseudo file format.

Optional Python Starter

File:

src/hilow_game.py

This file supports optional Construct-phase practice. It is not a graded Module Four deliverable.

Optional Tests

File:

tests/test_hilow_game.py

The test script supports optional Test-phase practice. Leave the provided test file unchanged and use it only after completing the optional Python program.

Which Files Should I Change?

For the graded assignment, change only:

  • design/hilow_game.pseudo

You may also change:

  • hilow_game_sdw.md for working notes
  • src/hilow_game.py for optional practice

Leave the other provided files unchanged unless your instructor directs you otherwise.

Clone this wiki locally