The document discusses the importance of requirements engineering in software development. It states that incomplete or changing requirements are major causes of cost overruns in projects. Proper requirements analysis can help reduce errors and save significant costs compared to later fixes. Challenges include insufficient time, review, and technical knowledge as well as political and communication issues. The key is to fully understand user needs, write clear specifications, and manage requirements throughout the project lifecycle.

1. Systems Requirements Engineering Prof M L Saikumar Institute of Public Enterprise

3. Why are Requirements so Important?

8. Typical Customer and Supplier Issues and Remedies Customer Supplier Remedies 1. Use domain experts 2. Consider technology change management Lacks subject matter expertise to address functional needs 5. Doesn’t update the statement of current user operating concepts or technology improvements 1. Emerge the high level real requirements 2. Strengthen commitment/gain a “shared vision” Doesn’t engage the client in a process to distill the real needs 4. Provides overly specific specifications 1. Take proactive steps to improve communications 2. Utilize a peer review process Doesn’t encourage and nurture more effective communication 3. Doesn’t communicate the need effectively 1. Utilize a joint team 2. Meet minimum requirements Is unwilling/unable to meet true needs within fiscal boundaries 2. Doesn’t understand what is achievable within fiscal boundaries 1. Invest more in the requirements process 2. Define the real customer needs Doesn’t understand the customer’s need 1. Doesn’t understand the real need

15. Hierarchical Decomposition of the Requirements Engineering Domain Requirements Engineering Requirements Development Requirements Management Elicitation Analysis Specification Verification