{"product_id":"software-requirements-essentials-9780138190286","title":"Software Requirements Essentials","description":"\u003cb\u003eBook Synopsis\u003c\/b\u003e\u003cbr\u003e\u003cp\u003e\u003cstrong\u003eKarl Wiegers\u003c\/strong\u003e 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 \u003cem\u003eIEEE Software\u003c\/em\u003e magazine and as a contributing editor for \u003cem\u003eSoftware Development\u003c\/em\u003e magazine. He is the author of \u003cem\u003eSoftware Development Pearls\u003c\/em\u003e (Addison-Wesley, 2022).\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eCandase Hokanson\u003c\/strong\u003e is a Business Architect and PMI-Agile Certified Practitioner at ArgonDigital, a software development, professional services, and trai\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTrade Review\u003c\/b\u003e\u003cbr\u003e\u003c\/p\u003e\u003cp\u003e\"As research for a book, I once read the ten best-selling requirements engineering books of the prior ten years. This one book succinctly presents more useful information than those ten books combined. I wish I'd had it as a reference then.\"\u003cbr\u003e--\u003cstrong\u003eMike Cohn\u003c\/strong\u003e, author of \u003cem\u003eUser Stories Applied\u003c\/em\u003e and co-founder of the Scrum Alliance\u003c\/p\u003e \u003cp\u003e\"Diamonds come about when a huge amount of carbon atoms are compressed. The compression crystallizes to form diamonds. Karl and Candase have done something very similar: they have compressed their vast requirements knowledge into 20 gems they call 'core practices.'\u003c\/p\u003e \u003cp\u003e\"These 20 practices give you the essence of requirements discovery, and for extra convenience they are categorized to make your requirements journey more effective. These practices are potent stuff, and I recommend that they become part of everyone's requirements arsenal.\"\u003cbr\u003e--\u003cstrong\u003eJames Robertson\u003c\/strong\u003e, author of \u003cem\u003eMastering the Requirements Process\u003c\/em\u003e and \u003cem\u003eBusiness Analysis Agility\u003c\/em\u003e\u003c\/p\u003e \u003cp\u003e\"What a valuable resource for new and experienced business analysts alike, who want an accessible, clearly written, and well-organized introduction to key business analyst practices. Karl and Candase do a great job of breaking down a complex role into a straightforward set of practices that can be integrated into your business analysis process to make it more effective.\"\u003cbr\u003e--\u003cstrong\u003eLaura Brandenburg\u003c\/strong\u003e, author of \u003cem\u003eHow to Start a Business Analyst Career\u003c\/em\u003e\u003c\/p\u003e \u003cp\u003e\"Candase and Karl have drawn upon their deep knowledge and experience of what it takes to elicit, identify, represent, communicate, and validate requirements for software products effectively. They have produced a useful, accessible, and clear book, which is full of practical advice, great examples, and answers to the hard questions that people building software products face in the real world. If you're involved in building software in any role, this book will give you guidance on ways to make sure the product meets customer needs and delivers real value.\"\u003cbr\u003e--\u003cstrong\u003eShane Hastie\u003c\/strong\u003e, Global Delivery Lead at SoftEd and Lead Editor, Culture and Methods at InfoQ.com\u003c\/p\u003e \u003cp\u003e\"\u003cem\u003eSoftware Requirements Essentials\u003c\/em\u003e will be a high-value addition to your business analysis library. I give the book high marks, as it does an excellent job of selecting and comprehensively covering the most essential business analysis practices teams should be considering. I thoroughly appreciated that the content was not overdone. Lessons were succinct while remaining extremely usable. Care was taken to ensure the guidance was applicable whether you are using a waterfall, agile, or hybrid delivery approach. I believe anyone looking to improve their business analysis practices will find great practical advice they'll be able to apply immediately.\"\u003cbr\u003e--\u003cstrong\u003eLaura Paton\u003c\/strong\u003e, Principal Consultant, BA Academy, Inc.\u003c\/p\u003e \u003cp\u003e\"Here is a book that all business analysts should have on their shelves, a readable reference that pulls together all the best practices we've been applying in business analysis for 50 years or so. While the book is aimed at the experienced BA, Karl and Candase thoughtfully provide an opening chapter reviewing the basic precepts and principles of business analysis. The book is written in Karl's inimitable easy-to-read style, so even beginning BAs can understand and apply the practices. Karl and Candase have made the book 'agile' with lots of practices applicable both to the traditional BA approach and to the BA who's defining user stories for the agile software developers.\u003c\/p\u003e \u003cp\u003e\"\u003cem\u003eSoftware Requirements Essentials\u003c\/em\u003e encapsulates all of the excellent advice and counsel Karl has given us over the years into this one touchstone of a book. I wish that I had written it.\"\u003cbr\u003e--\u003cstrong\u003eSteve Blais\u003c\/strong\u003e, author of \u003cem\u003eBusiness Analysis: Best Practices for Success\u003c\/em\u003e and co-author of \u003cem\u003eBusiness Analysis for Practitioners\u003c\/em\u003e\u003c\/p\u003e \u003cp\u003e\"One of the many aspects of Karl Wiegers's latest book that we love is the universality of the requirements techniques he describes. Using real-life examples and easy-to-understand illustrations, Wiegers and Candase Hokanson describe practices that can be applied regardless of the project at hand or the methodology followed. They emphasize that there is no one right way to elicit and manage requirements; rather, they present many tried-and-true practices that lead to successful outcomes. Also helpful are the dozens of questions that business analysts can use to elicit various types of requirements.\u003c\/p\u003e \u003cp\u003e\"The authors emphasize concepts over methodology-specific terminology to ensure that the practices can be understood and applied as methodologies change. The recurrent themes they mention are spot-on and apply to any development effort. \u003cem\u003eSoftware Requirements Essentials\u003c\/em\u003e is a must-read for every business analyst who wants to avoid the pitfall of achieving 'project success but product failure.'\"\u003cbr\u003e--\u003cstrong\u003eElizabeth Larson\u003c\/strong\u003e and \u003cstrong\u003eRichard Larson\u003c\/strong\u003e, past co-owners of Watermark Learning and authors of \u003cem\u003eCBAP Certification Study Guide\u003c\/em\u003e\u003c\/p\u003e \u003cp\u003e\"So many product development projects face challenges because the stated requirements are ill-defined. This issue can be addressed by business analysts, or anyone conducting business analysis, if they possess the necessary toolkit of techniques and skills. \u003cem\u003eSoftware Requirements Essentials\u003c\/em\u003e offers an excellent introduction to the requirements engineering framework, and the techniques it encompasses, in an accessible and engaging way. The book offers invaluable guidance and insights via 20 best practices that are highly relevant, if not essential, for anyone working to define requirements. All business analysts need a mental map of the requirements definition service; this book provides it and more.\"\u003cbr\u003e--\u003cstrong\u003eDr. Debra Paul\u003c\/strong\u003e, Managing Director, Assist Knowledge Development\u003c\/p\u003e\u003cbr\u003e\u003cbr\u003e\u003cb\u003eTable of Contents\u003c\/b\u003e\u003cbr\u003e\u003cp\u003e\u003cem\u003eForeword xvii\u003c\/em\u003e\u003cbr\u003e\u003cem\u003eAcknowledgments xix\u003c\/em\u003e\u003cbr\u003e\u003cem\u003eAbout the Authors xxi\u003c\/em\u003e\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 1: Essentials of Software Requirements 1\u003c\/strong\u003e\u003cbr\u003eRequirements Defined 2\u003cbr\u003eGood Practices for Requirements Engineering 5\u003cbr\u003eWho Does All This Stuff? 8\u003cbr\u003eSome Recurrent Themes 9\u003cbr\u003eThe Life and Times of Requirements 11\u003cbr\u003eGetting Started 11\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 2: Laying the Foundation 13\u003c\/strong\u003e\u003cbr\u003ePractice #1: Understand the problem before converging on a solution 14\u003cbr\u003ePractice #2: Define business objectives 19\u003cbr\u003ePractice #3: Define the solution's boundaries 26\u003cbr\u003ePractice #4: Identify and characterize stakeholders 33\u003cbr\u003ePractice #5: Identify empowered decision makers 39\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 3: Requirements Elicitation 45\u003c\/strong\u003e\u003cbr\u003ePractice #6: Understand what users need to do with the solution 47\u003cbr\u003ePractice #7: Identify events and responses 53\u003cbr\u003ePractice #8: Assess data concepts and relationships 59\u003cbr\u003ePractice #9: Elicit and evaluate quality attributes 67\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 4: Requirements Analysis 75\u003c\/strong\u003e\u003cbr\u003ePractice #10: Analyze requirements and requirement sets 76\u003cbr\u003ePractice #11: Create requirements models 84\u003cbr\u003ePractice #12: Create and evaluate prototypes 91\u003cbr\u003ePractice #13: Prioritize the requirements 97\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 5: Requirements Specification 107\u003c\/strong\u003e\u003cbr\u003ePractice #14: Write requirements in consistent ways 109\u003cbr\u003ePractice #15: Organize requirements in a structured fashion 115\u003cbr\u003ePractice #16: Identify and document business rules 121\u003cbr\u003ePractice #17: Create a glossary 127\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 6: Requirements Validation 131\u003c\/strong\u003e\u003cbr\u003ePractice #18: Review and test the requirements 132\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eChapter 7: Requirements Management 141\u003c\/strong\u003e\u003cbr\u003ePractice #19: Establish and manage requirements baselines 142\u003cbr\u003ePractice #20: Manage changes to requirements effectively 149\u003c\/p\u003e \u003cp\u003e\u003cstrong\u003eAppendix: Summary of Practices 157\u003c\/strong\u003e\u003c\/p\u003e \u003cp\u003e\u003cem\u003eReferences 159\u003c\/em\u003e\u003cbr\u003e\u003cem\u003eIndex 165\u003c\/em\u003e\u003c\/p\u003e","brand":"Pearson Education (US)","offers":[{"title":"Default Title","offer_id":48864177619287,"sku":"9780138190286","price":23.39,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0817\/1739\/5799\/files\/9780138190286.jpg?v=1722270756","url":"https:\/\/bookcurl.com\/products\/software-requirements-essentials-9780138190286","provider":"Book Curl","version":"1.0","type":"link"}