It clearly states the project's objectives and what problem is to be solved. The problem statement should be free of technical acronyms. State the problem in terms of the business objective, not the technical objective. Gathering requirements When the problem statement is written, you are ready to create a list of functional requirements. The list of requirements enables you to attain the next level of detail in the design.
Functional requirements are always a group process.
In this process, assemble everyone who has an interest in the project for group meetings. When the problem statement is written, you are ready to create a list of functional requirements. The list of requirements enables you to attain the next level of detail in the design. Functional requirements are always a group process. In this process, assemble everyone who has an interest in the project for group meetings.