Why do requirements analysis in a software project?

Customer engagement is the only way to avoid the desired difference (expectation gap), which is reflected in the expectations of the customer The product is not compatible with the product that the developer has designed. However, at the beginning of the project, simply ask one or two Customer needs, and then start coding, this is not enough. If the developer only opens up for the customer's initial needs Software, then they may want to re-develop, because, customers often don't know what they really need while developing People do not know. The user's "need" feature does not always have to do with the work required by the user to process their task (t a S k) with a new product can equal the price. Therefore, once you have collected your users ' opinions, you must analyze and collate these needs until you understand it , and write your understanding into a document, and then discuss it with the user, which is a recurring process and takes Time. If you do not take the time in this regard, there is no consensus on the expected product consensus-the eventual consequences may is rework, and the product is unsatisfactory.