Successful Software Development (2nd Edition)

This book introduces an amazingly effective approach in getting starting in planning software processes and leading teams to be consistent in software development. I was actually quite suprised at how useful and straightforward alot of the concepts are in this book, that even if applyed to a CMMi 1 organization, one with little to no defined process, can they begin to see positive results on a project. It's a good reference for a SEPG (Software Engineering Process Group), or PEG as they call it in this book, in your organization to really begin applying concepts of software process initiatives and improvements. I especially liked the chapters on Project Planning, CCB, Measurements, and Process Improvement which have alot of ready to apply concepts. I also really enjoyed the concept of ADPE (Application Development Process Enviornments) as a way to structure your own organizations practices, which fits into the bigger idea of the SEE (Software Engineering Enviornment). Software development processes, which are a concept that alot of organizations that rely on software today seem to discount, yet continue to manage in an ad-hoc manner and are constently wondering how they can ensure product quality; which can be quite frustrating to developers who do value consistency. Home Page ......Page 2 Contents......Page 6 Preface......Page 10 Authors’ Biographies......Page 27 Science Applications International Corporation......Page 31 Acknowledgments......Page 33 1.1 Introduction......Page 36 1.2 Business Case Key Ideas......Page 43 1.3 What Makes Good Business Sense?......Page 47 1.4 Software Systems Development Concepts......Page 61 1.5 Product “Goodness” and Process “Goodness”......Page 67 1.6 Requisite Software Systems Development Disciplines......Page 71 1.7 Generic Four-Stage Software Systems Development Life Cycle......Page 76 1.8 User, Buyer, and Seller Organizations Involved in Software Systems Development......Page 79 1.9 Obstacles to Improving Software Systems Development Cultures......Page 81 1.10 Alternative Approaches to Software Process Improvement......Page 87 1.11 Preview of the Rest of Book......Page 93 2.1 Introduction......Page 98 2.2 Project Planning Key Ideas......Page 100 2.3 Life Cycle Role in Project Planning......Page 102 2.4 Ideal, Real, and Realistic Project Planning......Page 113 2.5 Risk Assessment and Project Planning......Page 130 2.6 Project Planning Process......Page 135 2.7 Project Plan Contents......Page 145 2.8 Project Planning Summary......Page 151 3.1 Introduction......Page 154 3.2 Software Systems Development Process Key Ideas......Page 159 3.3 Software Systems Development Process Overview......Page 161 3.4 Customer......Page 167 3.5 Seller Process Engineering Group......Page 171 3.6 Customer/Seller Development Team and Change Control Board (CCB)......Page 174 3.7 Seller Senior Management......Page 197 3.8 Software Systems Development Process Summary......Page 200 4.1 Introduction......Page 208 4.2 Change Control Process Key Ideas......Page 213 4.3 Planned and Unplanned Change......Page 216 4.4 The Processing of Changes......Page 222 4.5 Examination of the Change Control Board......Page 242 4.6 Paperwork Support of the Change Control Board......Page 259 4.7 Change Control Process Summary......Page 293 5.1 Introduction......Page 298 5.2 Product and Process Reviews Key Ideas......Page 302 5.3 A Taxonomy of Product and Process Reviews......Page 304 5.4 Combining Reviews for Software Audits......Page 331 5.5 Product and Process Reviews Summary......Page 406 6.1 Introduction......Page 416 6.2 Measurement Key Ideas......Page 428 6.3 Product Integrity......Page 431 6.4 Process Integrity......Page 454 6.5 Capability Maturity Model (CMM) for Software......Page 471 6.6 Other Process-Related Measurements......Page 482 6.7 Measurement Summary......Page 497 7.1 Introduction......Page 512 7.2 Cultural Change Key Ideas......Page 526 7.3 Process Engineering Group (PEG)......Page 528 7.4 Seller Project Participants and Project Managers......Page 564 7.5 Buyer/User Project Management......Page 570 7.6 Buyer/User Senior Management......Page 573 7.7 Seller Senior Management......Page 575 7.8 Cultural Change Summary......Page 577 8.1 Introduction......Page 580 8.2 SEE Implementation Planning Key Ideas......Page 590 8.3 Key SEE Implementation Planning Issues......Page 594 8.4 Making Successful Software Development Happen......Page 703 A.1 Strategic Information Management......Page 706 A.2 Quantifying Strategic Information Management......Page 711 A.3 Diagnostic Areas and Diagnostic Criteria......Page 713 A.4 OM Measurement Map and Measurement Trends......Page 718 A.5 Summary......Page 723 Appendix B: List of Figures......Page 726 Appendix C: List of Tables......Page 738 Bibliography......Page 740 A......Page 764 C......Page 765 D......Page 768 I......Page 769 M......Page 770 O......Page 771 P......Page 772 R......Page 775 S......Page 776 T......Page 779 W......Page 780 Home Page 2 Contents 6 Preface 10 Authors’ Biographies 27 Science Applications International Corporation 31 Acknowledgments 33 Chapter 1 Business Case 36 1.1 Introduction 36 1.2 Business Case Key Ideas 43 1.3 What Makes Good Business Sense? 47 1.4 Software Systems Development Concepts 61 1.5 Product “Goodness” and Process “Goodness” 67 1.6 Requisite Software Systems Development Disciplines 71 1.7 Generic Four-Stage Software Systems Development Life Cycle 76 1.8 User, Buyer, and Seller Organizations Involved in Software Systems Development 79 1.9 Obstacles to Improving Software Systems Development Cultures 81 1.10 Alternative Approaches to Software Process Improvement 87 1.11 Preview of the Rest of Book 93 Chapter 2 Project Planning Process 98 2.1 Introduction 98 2.2 Project Planning Key Ideas 100 2.3 Life Cycle Role in Project Planning 102 2.4 Ideal, Real, and Realistic Project Planning 113 2.5 Risk Assessment and Project Planning 130 2.6 Project Planning Process 135 2.7 Project Plan Contents 145 2.8 Project Planning Summary 151 Chapter 3 Software Systems Development Process 154 3.1 Introduction 154 3.2 Software Systems Development Process Key Ideas 159 3.3 Software Systems Development Process Overview 161 3.4 Customer 167 3.5 Seller Process Engineering Group 171 3.6 Customer/Seller Development Team and Change Control Board (CCB) 174 3.7 Seller Senior Management 197 3.8 Software Systems Development Process Summary 200 Chapter 4 Change Control Process 208 4.1 Introduction 208 4.2 Change Control Process Key Ideas 213 4.3 Planned and Unplanned Change 216 4.4 The Processing of Changes 222 4.5 Examination of the Change Control Board 242 4.6 Paperwork Support of the Change Control Board 259 4.7 Change Control Process Summary 293 Chapter 5 Product and Process Reviews 298 5.1 Introduction 298 5.2 Product and Process Reviews Key Ideas 302 5.3 A Taxonomy of Product and Process Reviews 304 5.4 Combining Reviews for Software Audits 331 5.5 Product and Process Reviews Summary 406 Chapter 6 Measurement 416 6.1 Introduction 416 6.2 Measurement Key Ideas 428 6.3 Product Integrity 431 6.4 Process Integrity 454 6.5 Capability Maturity Model (CMM) for Software 471 6.6 Other Process-Related Measurements 482 6.7 Measurement Summary 497 Chapter 7 Cultural Change 512 7.1 Introduction 512 7.2 Cultural Change Key Ideas 526 7.3 Process Engineering Group (PEG) 528 7.4 Seller Project Participants and Project Managers 564 7.5 Buyer/User Project Management 570 7.6 Buyer/User Senior Management 573 7.7 Seller Senior Management 575 7.8 Cultural Change Summary 577 Chapter 8 Process Improvement Planning 580 8.1 Introduction 580 8.2 SEE Implementation Planning Key Ideas 590 8.3 Key SEE Implementation Planning Issues 594 8.4 Making Successful Software Development Happen 703 Appendix A: How to Measure Strategic Information Management (SIM) 706 A.1 Strategic Information Management 706 A.2 Quantifying Strategic Information Management 711 A.3 Diagnostic Areas and Diagnostic Criteria 713 A.4 OM Measurement Map and Measurement Trends 718 A.5 Summary 723 Appendix B: List of Figures 726 Appendix C: List of Tables 738 Bibliography 740 Index 764 A 764 B 765 C 765 D 768 E 769 F 769 G 769 H 769 I 769 J 770 K 770 L 770 M 770 N 771 O 771 P 772 Q 775 R 775 S 776 T 779 U 780 V 780 W 780

a Systematic Approach To Consistently Successful Software Development.

in The Age Of The Internet, Where Software Is More Mission-critical Than Ever, It's No Longer Enough For Your Development Projects To Succeed Some Of The Time. You Need To Deliver Excellence, Consistently–and You Must Do It Faster Than Ever.

successful Software Development Proceeds From The Fact That There Is No One Way To Develop Software Systems And Introduces A Model For A Mature Software Development Process That Accommodates Flexibility, The Systems Engineering Environment (see). This Model Comprises Two Fundamental, Interlocked Elements: The Policies And Procedures That Define How Software Development Is Performed And The Technologies Available To Get The Job Done. Using The See Framework, Learn How To:

• understand And Sell The Business Case For Software Improvement
• establish And Nourish An Ongoing, Productive Dialogue Between Developers And Customers
• manage The Multiple Constituencies, Personalities, Issues, And Egos That Complicate Software Development
• create Plans That Reflect The Need For Change–and Take Into Account Real-world Risks
• write Clearer, More Useful Contracts And Statements Of Work

successful Software Development Includes Over 200 Figures, Process Diagrams, And Annotated Outlines–all Designed To Help You Understand And Implement Better Processes Quickly And With Less Resistance.

this Book's Techniques Will Work With Any Software Quality Methodology You Choose, As Well As Sei's Capability Maturity Models And Iso 9000. They Will Work With Any Development Technology, From Case To Object-oriented Design To Rapid Prototyping. And They Will Work For You Whether You're A Programmer, Manager, Or Customer. When It Comes To Delivering Better Software, If You Need To Get Results, You Need This Book.

booknews

introduces A Model For A Mature Software Development Process That Accommodates Flexibility, Focusing On Policies And Procedures That Define How Software Development Is Performed, And Technologies Available. Tells How To Sell The Business Case For Software Process Improvement, How To Establish Dialogue Between Developers And Customers, And How To Manage Multiple Constituencies, Personalities, And Issues. Shows How To Create Plans That Reflect The Need For Change, And How To Write Clear Contracts And Statements Of Work. Donaldson Has 25 Years Of Software Engineering Experience. Siegel Has Been In The Software Industry Since 1970. Annotation C. Book News, Inc., Portland, Or (booknews.com)

A systematic approach to consistently successful software development. In the age of the Internet, where software is more mission-critical than ever, it's no longer enough for your development projects to succeed some of the time. You need to deliver excellence, consistently--and you must do it faster than ever. Successful Software Development proceeds from the fact that there is no one way to develop software systems and introduces a model for a mature software development process that accommodates flexibility, the Systems Engineering Environment (SEE). This model comprises two fundamental, interlocked elements: the policies and procedures that define how software development is performed and the technologies available to get the job done. Using the SEE framework, learn how to: Understand and "sell" the business case for software improvement Establish and nourish an ongoing, productive dialogue between developers and customers Manage the multiple constituencies, personalities, issues, and egos that complicate software development Create plans that reflect the need for change--and take into account real-world risks Write clearer, more useful contracts and statements of work "Successful Software Development" includes over 200 figures, process diagrams, and annotated outlines--all designed to help you understand and implement better processes quickly and with less resistance. This book's techniques will work with any software quality methodology you choose, as well as SEI's capability maturity models and ISO 9000. They will work with any development technology, from CASE to object-oriented design to rapidprototyping. And they will work for you whether you're a programmer, manager, or customer. When it comes to delivering better software, if you need to get results, you need this book A systematic approach to consistently successful software development. In the age of the Internet, where software is more mission-critical than ever, it's no longer enough for your development projects to succeed some of the time. You need to deliver excellence, consistently—and you must do it faster than ever. Successful Software Development proceeds from the fact that there is no one way to develop software systems and introduces a model for a mature software development process that accommodates flexibility, the Systems Engineering Environment (SEE). This model comprises two fundamental, interlocked elements: the policies and procedures that define how software development is performed and the technologies available to get the job done. Using the SEE framework, learn how to: Understand and'sell'the business case for software improvement Establish and nourish an ongoing, productive dialogue between developers and customers Manage the multiple constituencies, personalities, issues, and egos that complicate software development Create plans that reflect the need for change–and take into account real-world risks Write clearer, more useful contracts and statements of work Successful Software Development includes over 200 figures, process diagrams, and annotated outlines–all designed to help you understand and implement better processes quickly and with less resistance. This book's techniques will work with any software quality methodology you choose, as well as SEI's capability maturity models and ISO 9000. They will work with any development technology, from CASE to object-oriented design to rapid prototyping. And they will work for you whether you're a programmer, manager, or customer. When it comes to delivering better software, if you need to get results, you need this book. For courses in Software Engineering and Software Reliability. Successful Software Development takes a systematic approach to consistently successful software development. It proceeds from the fact that there is no one way to develop software systems and introduces a model for a mature software development process that accommodates flexibility, the Systems Engineering Environment (SEE). This model comprises two fundamental, interlocked elements: the policies and procedures that define how software development is performed and the technologies available to get the job done.