Thoughts on missing requirements during software development

 

In a relatively large software project, it is easy to discover problems in the later stage of the software life because of incomplete consideration, which increases the cost. For example, in the demand analysis and design phase, or even in the encoding phase, a function is not considered. Incomplete, it will not only affect the overall project plan, but also may affect the quality of the project. The reason for careful analysis is nothing more than two points: the understanding of the business is not deep enough; the consideration of the problem is not comprehensive, careful, and lack of risk awareness.

How can we avoid such problems? First, you should be more familiar with the business, and then be brave enough to challenge your own ideas, especially those that require experience to make decisions. We have been emphasizing the idea that allProgramAll of them are flawed. In the same way, this sentence is especially true for demand analysis. All the requirements are imperfect. Some of them even have serious problems such as incomplete functions and poor user experience.