000			02752cam a22002294a 4500
020			_a032112247X _cTZS 99,840/=
040			_aMUL _beng _eAACR
082	0	0	_a005.1086
100	1		_aLeffingwell, Dean.
245	1	0	_aManaging software requirements : _ba use case approach / _cDean Leffingwell and Don Widrig.
250			_a2nd ed.
260			_aBoston : _bAddison-Wesley, _cc2003.
300			_axxxvii, 502 p. : _bill. ; _c25 cm.
440		4	_aThe Addison-Wesley object technology series
504			_aIncludes bibliographical references (p. 483-486) and index.
520			_a"Many projects fail because developers fail to build the right thing. Developers of any kind of application should read this book." -Grady Booch "A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." -Ivar Jacobson Despite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This second edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget. Using an accessible style, their own war stories, and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements, Second Edition , specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders. Topics covered include: The five steps in problem analysis Business modeling and system engineering Techniques for eliciting requirements from customers and stakeholders Establishing and managing project scope Applying and refining use cases Product management Transitioning from requirements to design and implementation Transitioning from use cases to test cases Agile requirements methods 032112247XB05082003
546			_aeng
650		0	_aComputer software
650		0	_aUse cases (Systems engineering)
700	1		_aWidrig, Don.
942			_cBK
999			_c6760 _d6760