Creating a high-level and low-level design

When a team has gathered enough requirements from the planning phase, they can then conceptualize how it all works together with a design that is used to help build the finished product. Having a good design makes it easier for teams to get started with coding in the implementation phase. Most complex problems are approached by breaking them down into smaller parts to solve them, and the same can be applied to software. When it comes to design, this process is typically split into two phases: high-level, which involves converting requirements into large functional parts of the software, and low-level, which involves breaking the larger parts into smaller pieces until they are manageable enough to describe how they work and will be solved.

After some back and forth, the Coder Bank team project managers and lead software engineers agree there is enough information to get started on the design phase. The project managers have decided to give...