The article discusses how software requirements often change during development, leading to mistakes. The researchers suggest a method called feature-oriented requirements change management with value analysis to handle these changes effectively. They introduce a requirements change tree to organize user requests by feature and outline a process for managing changes, including normalization, impact analysis, and evaluation. The researchers also present results from a case study on an asset management portal system, demonstrating the effectiveness of their approach.