- Ivar Jacobson "Many projects fail for the simple reason that the developer failed to build the right thing: They also provide a system that does not meet the expectations of the intended users, or they provide a system that focuses on secondary functions at the expense of primary use - Grady Booch. Despite the wealth of development knowledge, experience, and tools generally available today, most software projects continue to fail, often because requirements are not determined and defined at the beginning, or is not managed correctly as the project unfolds. By using force, was approached informally, their own war stories, and a comprehensive case study they show how designers and developers can effectively identify requirements by using the power of use cases and more traditional forms of requirements expression. It describes six vital Team Skills for managing requirements throughout the project life cycle: Analyze the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining System Definition, and Building The Right System. Managing Software Requirements specifically addresses the ongoing challenge of managing change and explain the process to ensure that the project scope of work defined and agreed upon by all stakeholders. Topics covered include: * The five steps in problem analysis * Business modeling and system engineering * Techniques to bring the needs of clients, users, developers, and stakeholders * Applying and refining use cases * Prototyping * Organizing and managing requirements information * Define project scope and manage customer * Using both informal and technical methods to determine requirements * How to measure and improve the quality of your product requirements * Moving from requirements to implementation * Verifying and validating * Manage system change The book concludes with a step-by-step to combine powerful techniques into future projects.