Determining use cases and requirements

Before building your CLI application, you’ll need to have an idea of the application’s purpose and responsibilities. The purpose of the application can be defined as an overarching description, but to start implementing, it’s necessary to break down the purpose into use cases and requirements. The goal of use cases and requirements is to drive effective discussion around what an application should do, with the result that everyone has a shared understanding of what is going to be built and continues these discussions as the application evolves.

Use cases

Use cases are a way of documenting the functional requirements of a project. This step, at least for CLIs, is typically handled by an engineer after gathering some high-level requirements from their internal, or external, business customers. It’s important to have a clear picture of the application’s purpose and document the use cases before any technical...