Software Requirements Essentials: Core Practices for Successful Business Analysis - Candase Hokanson

. .

Résumé :
Karl Wiegers is Principal Consultant with Process Impact, a software development consulting and training company in Happy Valley, Oregon. Previously, he spent eighteen years at Kodak, where he held positions as a photographic research scientist, software developer, software manager, and software process and quality improvement leader. Karl received a PhD in organic chemistry from the University of Illinois. Karl is the author of thirteen previous books and has written many articles on software development, management, design, consulting, chemistry, and military history. Karl has served on the editorial board for IEEE Software magazine and as a contributing editor for Software Development magazine. He is the author of Software Development Pearls (Addison-Wesley, 2022).Candase Hokanson is a Business Architect and PMI-Agile Certified Practitioner at ArgonDigital, a software development, professional services, and training company based in Austin, Texas. Candase graduated from Rice University with a BS and MS in civil engineering and a BA in religious studies. She is an active member of the product and business analysis communities, previously serving as a co-chair for the Keep Austin Agile conference in 2019 and president of the Austin IIBA. She has authored multiple articles on using visual models in agile, requirements in agile, and agile in the large enterprise....

Biographie:
Joy Beatty, a leader in the software requirements community, has trained thousands of business analysts and helped major organizations build business-analysis centers of excellence. She is coauthor of Visual Models for Software Requirements....

Sommaire:

Foreword xvii
Acknowledgments xix
About the Authors xxi

Chapter 1: Essentials of Software Requirements 1
Requirements Defined 2
Good Practices for Requirements Engineering 5
Who Does All This Stuff? 8
Some Recurrent Themes 9
The Life and Times of Requirements 11
Getting Started 11

Chapter 2: Laying the Foundation 13
Practice #1: Understand the problem before converging on a solution 14
Practice #2: Define business objectives 19
Practice #3: Define the solution's boundaries 26
Practice #4: Identify and characterize stakeholders 33
Practice #5: Identify empowered decision makers 39

Chapter 3: Requirements Elicitation 45
Practice #6: Understand what users need to do with the solution 47
Practice #7: Identify events and responses 53
Practice #8: Assess data concepts and relationships 59
Practice #9: Elicit and evaluate quality attributes 67

Chapter 4: Requirements Analysis 75
Practice #10: Analyze requirements and requirement sets 76
Practice #11: Create requirements models 84
Practice #12: Create and evaluate prototypes 91
Practice #13: Prioritize the requirements 97

Chapter 5: Requirements Specification 107
Practice #14: Write requirements in consistent ways 109
Practice #15: Organize requirements in a structured fashion 115
Practice #16: Identify and document business rules 121
Practice #17: Create a glossary 127

Chapter 6: Requirements Validation 131
Practice #18: Review and test the requirements 132

Chapter 7: Requirements Management 141
Practice #19: Establish and manage requirements baselines 142
Practice #20: Manage changes to requirements effectively 149

Appendix: Summary of Practices 157

References 159
Index 165