Understanding and Organizing the Business Requirements of Our Project
Before writing a single line of code, we first need to understand the goals of a project and what problems we are trying to solve. We build software to solve problems, and if we do not adequately understand what the client or the business is trying to achieve, we will have problems coming up with the ideal solution—or, worse, we can end up spending months building software that doesn’t even address the business requirements.
As software developers, it is great to have a clear list of what needs to be built. It’s just like having a simple grocery list. This list will help us determine which features we need to develop or release first. So, before we start building solutions to a problem by writing software, we will try to come up with a simple example where we will try to interpret business problems and goals into a list of software features that we will need to write code for.
In this chapter...
