Part 1 of 7 · 1 min read
Why this page comes fourth
In this module you will
- Apply the same five steps to any low-level design prompt.
- Keep to a time budget for each step.
- Turn the class sketch into compiling Java for the main flow.
- Find edge cases in a list instead of by luck.
- Answer a change request by pointing at the class that changes.
Modules 1 to 3 gave the parts: the goal, the requirements, the entities and the diagrams. This page joins them into one routine that works for every case study from Level 6 on. No book was supplied for this track, so the content is common practice, not from the books. The Java code was compiled and run before it was written here. Numbers marked "made up" only show the idea.