Software Requirements Management: Use Case Method (2nd Edition)

Author: Dean Leffingwell
Publisher:
Publish Date: 2004-05-01
Features: Dean Leffingwell, former CEO of Rational, is recognized as an authority in the requirements field. He adopts a non-formal, easily acceptable style, sharing his practical experiences and citing numerous case studies, demonstrating to designers and developers how to effectively combine use case technology with traditional software expression forms to determine requirements. The book also introduces proven techniques for requirements determination, implementation, and validation. Building on the success of the previous edition, the author has significantly rewritten and condensed the content based on feedback from numerous readers, making it more practical and readable, and providing greater guidance for readers' actual work. Today, despite the continuous enrichment of knowledge and experience in development and the increasing availability of tools, a significant proportion of software projects still fail, often due to incorrect determination and definition of requirements at the outset or incorrect management of requirements as the project progresses. This book is the second edition of the bestseller "Software Requirements Management," focusing on this critical reason for project failure and proposing a proven practical method to help us deliver a system that meets customer needs within budget and on time. The author adopts a non-formal, easily acceptable style, sharing his practical experiences and, through numerous case studies, demonstrating to designers and developers how to effectively combine use case technology with traditional software expression forms to determine requirements. The book also introduces proven techniques for requirements determination, implementation, and validation. The book outlines six team skills for requirements management throughout the entire project lifecycle: analyzing problems, understanding user needs, defining the system, managing scope, refining system definitions, and building the correct system. The book particularly emphasizes the continuous management of changes, describing a process to ensure successful definition of project scope and achieve consensus among all stakeholders. The main issues discussed in the book include:
· Five steps of problem analysis
· Business modeling and systems engineering
· Techniques for eliciting requirements from customers and stakeholders
· Establishing and managing project scope
· Applying and refining use cases
· Product management
· Transition from requirements to design and implementation
· Transition from use cases to test cases
· Agile requirements methods