Problem
Requirements errors may be viewed by customers as errors that need to be repaired by the software producer before the application is formally accepted. They may be viewed by software engineers as incorrectly stated requirements that were accepted by the customer when the requirements specification document was issued and reviewed. Since the customer did not object to the specification at that point, the software engineers reject the arguments of the customer, holding that if the customer wants the application changed, he or she should pay for it. What is your opinion? How can the conflict be solved or alleviated?