How can we reduce software requirement errors ? Solution If we want to reduce the error firstly we have to identify the error for improve the quality of software. Finding and fixing a software problem after delivery is often 100 times more expansive than finding and fixing it during requirement phase. Requirement errors can be categorized into two main types: specification generation errors and unwanted/unnecessary/incorrect user functionality. We are using two step methodology for reduce the requirement errors. Step 1: Operational demonstration for user requirement Involves user during early phases, as opposed to the later phases or after system delivery Eliminate unnecessary and incorrect functionalities Find how much risk on that phase and manage that risk (risk management) Step 2: Software inspection conducted on requirement specification Ensure user and developer requirements are accurately specified Detect errors associated with all phases regarding development Reduce software development cost by detecting errors early .