实例介绍
【实例简介】
Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development an
Simply put, this book is both a must-read and a great reference for anyone working to define and manage software development projects. In today s modern software development world, too often sound requirements practices are set aside for the lure of"unencumbered"agile. Karl and Joy have detailed a progressive approach to managing requirements, and detailed how to accommodate the ever-changing approaches to delivering software -Mark Kulak, Software Development Director, Borland, a Micro Focus company am so pleased to see the updated book on software requirements from Karl Wiegers and Joy Beatty. I especially like the latest topic on how to apply effective requirements practices to agile projects, because it is a service that our consultants are engaged in more and more these days. The practical guide and real examples of the many different requirement practices are invaluable Doreen Evans, Managing Director of the Requirements and Business Analysis Practice for Robbins Gioia Inc. As an early adopter of Karl's classic book, Software Requirements, I have been eagerly awaiting his new edition -and it doesn't disappoint Over the years, IT development has undergone a change of focus from large, new, 'green-field projects towards adoption of ready-made off-the-shelf solutions nd quick-release agile practices. In this latest edition, Karl and Joy explore the implications of these new developments on the requirements process with invaluable recommendations based not on dogma but on what works, honed from their broad and deep experience in the field Howard Podeswa, CEO, Noble InC, and author of The Business Analyst's Handbook If you are looking for a practical guide into what software requirements are, how to craft them, and what to do with them, then look no further than Software Requirements, Third Edition. This usable and readable text walks you through exactly how to approach common requirements-related scenarios The incorporation of multiple stories, case studies, anecdotes, and examples keeps it engaging to read Laura brandenburg, CBAP, Host at Bridging the Gap How do you make a good requirements read better? You add content like Karl and Joy did to address incorporating product vision, tackling agility issues, covering requirements reuse, tackling packaged and outsourced software, and addressing specific user classes. You could take an outside look inside of requirements to address process and risk issues and go beyond just capturing functionality -Donald Reifer, President, Reifer Consultants LLC This new edition keeps pace with the speed of business, both in deepening the foundation of the second edition and in bringing analysts down -to-earth how to' s for addressing the surge in agile development, using features to control scope, improving elicitation techniques, and expanding modeling Wiegers and Beatty have put together a must-read for anyone in the profession Keith Ellis, President and CEO, Enfocus Solutions Inc. and author of business analysis Benchmark +Microsoft Software Requirements Third edition Karl Wiegers and Joy Beatty PUBLISHED BY Microsoft press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright@ 2013 Karl Wiegers and Sealevel All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of congress Control Number: 2013942928 SBN:978-0-7356-7966-5 Microsoft Press books are available through booksellers and distributors worldwide. If you need support related to this book,emailMicrosoftPressBookSupportatmspinput@microsoft.com.Pleasetelluswhatyouthinkofthisbookat http.//www.microsoft.com/earning/booksurvey Microsoftandthetrademarkslistedathttp://www.microsoft.com/aboutlegal/en/us/intellectualproperty/ Trademarks/EN-US. aspx are trademarks of the Microsoft group of companies. All other marks are property of their respective owners The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred This book expresses the authors views and opinions the information contained in this book is provided without any express, statutory, or implied warranties. Neither the authors, Microsoft Corporation, nor its resellers, or distributors will be held liable for any damages caused or alleged to be caused either directly or indirectly by this book Acquisitions Editor: Devon Musgrave Developmental Editors: Devon Musgrave and Carol Dillingham Project Editor: Carol Dillingham Editorial Production: Christian Holdener, S4Carlisle Publishing Services Copyeditor: Kathy Krause Indexer: Maureen Johnson Cover: Twist creative. Seattle [LSI [2013-09-06] For Chris, yet again. Eighth time's the charm KW For my parents, Bob and Joanne, for a lifetime of encouragement -人.B Contents at a glance Introduction XXV Acknowledgments XXⅩ PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO CHAPTER 1 The essential software requirement CHAPTER 2 Requirements from the customer s perspective 25 CHAPTER 3 Good practices for requirements engineering 43 CHAPTER 4 The business analyst 61 PART I REQUIREMENTS DEVELOPMENT CHAPTER 5 Establishing the business requirements 77 ChAPTER 6 Finding the voice of the user 101 CHAPTER 7 Requirements elicitation 119 CHAPTER8 Understanding user requirements 143 CHAPTER 9 Playing by the rules 167 CHAPTER 10 Documenting the requirements 181 CHAPTER 11 Writing excellent requirements 203 CHAPTER 12 A picture is worth 1024 words 221 CHAPTER 13 Specifying data requirements 245 CHAPTER 14 Beyond functionality 261 CHAPTER 15 Risk reduction through prototyping 295 CHAPTER 16 First things first: Setting requirement priorities 313 CHAPTER 17 Validating the requirements 329 CHAPTER 18 Requirements reuse 351 CHAPTER 19 Beyond requirements development 365 PART I REQUIREMENTS FOR SPECIFIC PROJECT CLASSES CHAPTER 20 Agile projects 383 CHAPTER 21 Enhancement and replacement projects 393 CHAPTER 22 Packaged solution projects 405 CHAPTER 23 Outsourced projects 415 CHAPTER 24 Business process automation projects 421 CHAPTER 25 Business analytics projects 427 CHAPTER 26 Embedded and other real - time systems projects 439 PART IV REQUIREMENTS MANAGEMENT CHAPTER 27 Requirements management practices 457 CHAPTER 28 Change happens 471 CHAPTER 29 Links in the requirements chain 491 CHAPTER 30 Tools for requirements engineering 503 PART V IMPLEMENTING REQUIREMENTS ENGINEERING CHAPTER 31 Improving your requirements processes 517 CHAPTER 32 Software requirements and risk management 537 epic 549 Appendix A 551 Appendix B 559 AppendⅸC 575 Glossary 597 Referen 605 Index 619 Contents at a glance Contents Introduction XXV Acknowledgments XXⅩ PART SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO Chapter 1 The essential software requirement 3 Software requirements defined Some interpretations of "requirement Levels and types of requirements Working with the three levels 12 Product vs project requirements 14 Requirements development and management 15 Requirements development 15 Requirements management .17 Every project has requirements 18 When bad requirements happen to good people Insufficient user involvement 0 accurate planning 20 Creeping user requirements .20 Ambiguous requirements Gold plating 21 Overlooked stakeholders 22 Benefits from a high-quality requirements process .22 Chapter 2 Requirements from the customer's perspective 25 The expectation gap 26 Who is the customer? The customer-development partnership Requirements Bill of Rights for Software Customers Requirements bill of Responsibilities for Software Customers... 33 【实例截图】
【核心代码】
Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development an
Simply put, this book is both a must-read and a great reference for anyone working to define and manage software development projects. In today s modern software development world, too often sound requirements practices are set aside for the lure of"unencumbered"agile. Karl and Joy have detailed a progressive approach to managing requirements, and detailed how to accommodate the ever-changing approaches to delivering software -Mark Kulak, Software Development Director, Borland, a Micro Focus company am so pleased to see the updated book on software requirements from Karl Wiegers and Joy Beatty. I especially like the latest topic on how to apply effective requirements practices to agile projects, because it is a service that our consultants are engaged in more and more these days. The practical guide and real examples of the many different requirement practices are invaluable Doreen Evans, Managing Director of the Requirements and Business Analysis Practice for Robbins Gioia Inc. As an early adopter of Karl's classic book, Software Requirements, I have been eagerly awaiting his new edition -and it doesn't disappoint Over the years, IT development has undergone a change of focus from large, new, 'green-field projects towards adoption of ready-made off-the-shelf solutions nd quick-release agile practices. In this latest edition, Karl and Joy explore the implications of these new developments on the requirements process with invaluable recommendations based not on dogma but on what works, honed from their broad and deep experience in the field Howard Podeswa, CEO, Noble InC, and author of The Business Analyst's Handbook If you are looking for a practical guide into what software requirements are, how to craft them, and what to do with them, then look no further than Software Requirements, Third Edition. This usable and readable text walks you through exactly how to approach common requirements-related scenarios The incorporation of multiple stories, case studies, anecdotes, and examples keeps it engaging to read Laura brandenburg, CBAP, Host at Bridging the Gap How do you make a good requirements read better? You add content like Karl and Joy did to address incorporating product vision, tackling agility issues, covering requirements reuse, tackling packaged and outsourced software, and addressing specific user classes. You could take an outside look inside of requirements to address process and risk issues and go beyond just capturing functionality -Donald Reifer, President, Reifer Consultants LLC This new edition keeps pace with the speed of business, both in deepening the foundation of the second edition and in bringing analysts down -to-earth how to' s for addressing the surge in agile development, using features to control scope, improving elicitation techniques, and expanding modeling Wiegers and Beatty have put together a must-read for anyone in the profession Keith Ellis, President and CEO, Enfocus Solutions Inc. and author of business analysis Benchmark +Microsoft Software Requirements Third edition Karl Wiegers and Joy Beatty PUBLISHED BY Microsoft press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright@ 2013 Karl Wiegers and Sealevel All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of congress Control Number: 2013942928 SBN:978-0-7356-7966-5 Microsoft Press books are available through booksellers and distributors worldwide. If you need support related to this book,emailMicrosoftPressBookSupportatmspinput@microsoft.com.Pleasetelluswhatyouthinkofthisbookat http.//www.microsoft.com/earning/booksurvey Microsoftandthetrademarkslistedathttp://www.microsoft.com/aboutlegal/en/us/intellectualproperty/ Trademarks/EN-US. aspx are trademarks of the Microsoft group of companies. All other marks are property of their respective owners The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred This book expresses the authors views and opinions the information contained in this book is provided without any express, statutory, or implied warranties. Neither the authors, Microsoft Corporation, nor its resellers, or distributors will be held liable for any damages caused or alleged to be caused either directly or indirectly by this book Acquisitions Editor: Devon Musgrave Developmental Editors: Devon Musgrave and Carol Dillingham Project Editor: Carol Dillingham Editorial Production: Christian Holdener, S4Carlisle Publishing Services Copyeditor: Kathy Krause Indexer: Maureen Johnson Cover: Twist creative. Seattle [LSI [2013-09-06] For Chris, yet again. Eighth time's the charm KW For my parents, Bob and Joanne, for a lifetime of encouragement -人.B Contents at a glance Introduction XXV Acknowledgments XXⅩ PART I SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO CHAPTER 1 The essential software requirement CHAPTER 2 Requirements from the customer s perspective 25 CHAPTER 3 Good practices for requirements engineering 43 CHAPTER 4 The business analyst 61 PART I REQUIREMENTS DEVELOPMENT CHAPTER 5 Establishing the business requirements 77 ChAPTER 6 Finding the voice of the user 101 CHAPTER 7 Requirements elicitation 119 CHAPTER8 Understanding user requirements 143 CHAPTER 9 Playing by the rules 167 CHAPTER 10 Documenting the requirements 181 CHAPTER 11 Writing excellent requirements 203 CHAPTER 12 A picture is worth 1024 words 221 CHAPTER 13 Specifying data requirements 245 CHAPTER 14 Beyond functionality 261 CHAPTER 15 Risk reduction through prototyping 295 CHAPTER 16 First things first: Setting requirement priorities 313 CHAPTER 17 Validating the requirements 329 CHAPTER 18 Requirements reuse 351 CHAPTER 19 Beyond requirements development 365 PART I REQUIREMENTS FOR SPECIFIC PROJECT CLASSES CHAPTER 20 Agile projects 383 CHAPTER 21 Enhancement and replacement projects 393 CHAPTER 22 Packaged solution projects 405 CHAPTER 23 Outsourced projects 415 CHAPTER 24 Business process automation projects 421 CHAPTER 25 Business analytics projects 427 CHAPTER 26 Embedded and other real - time systems projects 439 PART IV REQUIREMENTS MANAGEMENT CHAPTER 27 Requirements management practices 457 CHAPTER 28 Change happens 471 CHAPTER 29 Links in the requirements chain 491 CHAPTER 30 Tools for requirements engineering 503 PART V IMPLEMENTING REQUIREMENTS ENGINEERING CHAPTER 31 Improving your requirements processes 517 CHAPTER 32 Software requirements and risk management 537 epic 549 Appendix A 551 Appendix B 559 AppendⅸC 575 Glossary 597 Referen 605 Index 619 Contents at a glance Contents Introduction XXV Acknowledgments XXⅩ PART SOFTWARE REQUIREMENTS: WHAT, WHY, AND WHO Chapter 1 The essential software requirement 3 Software requirements defined Some interpretations of "requirement Levels and types of requirements Working with the three levels 12 Product vs project requirements 14 Requirements development and management 15 Requirements development 15 Requirements management .17 Every project has requirements 18 When bad requirements happen to good people Insufficient user involvement 0 accurate planning 20 Creeping user requirements .20 Ambiguous requirements Gold plating 21 Overlooked stakeholders 22 Benefits from a high-quality requirements process .22 Chapter 2 Requirements from the customer's perspective 25 The expectation gap 26 Who is the customer? The customer-development partnership Requirements Bill of Rights for Software Customers Requirements bill of Responsibilities for Software Customers... 33 【实例截图】
【核心代码】
标签：
好例子网口号：伸出你的我的手 — 分享！
小贴士
感谢您为本站写下的评论，您的评论对其它用户来说具有重要的参考价值，所以请认真填写。
- 类似“顶”、“沙发”之类没有营养的文字，对勤劳贡献的楼主来说是令人沮丧的反馈信息。
- 相信您也不想看到一排文字/表情墙，所以请不要反馈意义不大的重复字符，也请尽量不要纯表情的回复。
- 提问之前请再仔细看一遍楼主的说明，或许是您遗漏了。
- 请勿到处挖坑绊人、招贴广告。既占空间让人厌烦，又没人会搭理，于人于己都无利。
关于好例子网
本站旨在为广大IT学习爱好者提供一个非营利性互相学习交流分享平台。本站所有资源都可以被免费获取学习研究。本站资源来自网友分享，对搜索内容的合法性不具有预见性、识别性、控制性，仅供学习研究，请务必在下载后24小时内给予删除，不得用于其他任何用途，否则后果自负。基于互联网的特殊性，平台无法对用户传输的作品、信息、内容的权属或合法性、安全性、合规性、真实性、科学性、完整权、有效性等进行实质审查；无论平台是否已进行审查，用户均应自行承担因其传输的作品、信息、内容而可能或已经产生的侵权或权属纠纷等法律责任。本站所有资源不代表本站的观点或立场，基于网友分享，根据中国法律《信息网络传播权保护条例》第二十二与二十三条之规定，若资源存在侵权或相关问题请联系本站客服人员，点此联系我们。关于更多版权及免责申明参见 版权及免责申明
网友评论
我要评论