No matter how much instruction you've had on managing software requirements， there's no substitute for experience. Too often， lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book， Software Requirements， Second Edition， requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book.With straightforward， professional advice and practical solutions based on actual project experiences， this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements， this essential companion gives developers， analysts， and managers the cosmic truths that apply to virtually every software development project.
作者簡(jiǎn)介
Karl E. Wiegers is Principal Consultant with Process Impact， a software process consulting and education company in Portland， Oregon. His interests include requirements engineering， peer reviews， process improvement， project management， risk manage-ment， and software metrics. Previously， he spent 18 years at East-man Kodak Company， where he held positions as a photographic research scientist， software developer， software manager， and soft-ware process and quality improvement leader. Karl received a B.S. degree in chemistry from Boise State College， and M.S. and Ph.D. degrees in organic chemistry from the University of Illinois. He is a member of the IEEE， IEEE Computer Society， and ACM.
圖書目錄
Part Ⅰ On Essential Requirements Concepts 1 Requirements Engineering Overview 2 Cosmic Truths About Software Requirements Part Ⅱ On the Management View of Requirements 3 The Business Value of Better Requirements 4 How Long Do Requirements Take? 5 Estimating Based on Requirements Part Ⅲ On Customer Interactions 6 The Myth of the On-Site Customer 7 An Inquiry, Not an Inquisition 8 Two Eyes Aren't Enough Part Ⅳ On Use Cases 9 Use Cases and Scenarios and Stories, Oh My! 10 Actors and Users 11 When Use Cases Aren't Enough Part Ⅴ On Writing Requirements 12 Bridging Documents 13 How Much Detail Do You Need? 14 To Duplicate or Not to Duplicate 15 Elements of Requirements Style 16 The Fuzzy Line Between Requirements and Design Part Ⅵ On the Requirements Process 17 Defining ProJect Scope 18 The Line in the Sand 19 The Six Blind Men and the Requirements Part Ⅶ On Managing Requirements 20 Handling Requirements for Multiple Releases 21 Business Requirements and Business Rules 22 Measuring Requirements 23 Exploiting Requirements Management Tools
鄂公網(wǎng)安備 42010302001612號(hào) 