Successful Software Development

by Donaldson, Scott E.; Siegel, Stanley G.

• ISBN13: 9780130868268
• ISBN10: 0130868264
• Edition: 2nd
• Format: Hardcover
• Copyright: 2001-01-01
• Publisher: Prentice Hall

Summary

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.

Table of Contents

Preface	xi
Authors' Biographies	xxviii
Science Applications International Corporation	xxxii
Acknowledgments	xxxiv
Business Case	1	(62)
Introduction	1	(7)
Business Case Key Ideas	8	(4)
What Makes Good Business Sense?	12	(14)
Software Systems Development Concepts	26	(6)
Product ``Goodness'' and Process ``Goodness''	32	(4)
Requisite Software Systems Development Disciplines	36	(5)
Generic Four-Stage Software Systems Development Life Cycle	41	(3)
User, Buyer, and Seller Organizations Involved in Software Systems Development	44	(2)
Obstacles to Improving Software Systems Development Cultures	46	(6)
Alternative Approaches to Software Process Improvement	52	(6)
Preview of the Rest of Book	58	(5)
Project Planning Process	63	(56)
Introduction	63	(2)
Project Planning Key Ideas	65	(2)
Life Cycle Role in Project Planning	67	(11)
Ideal, Real, and Realistic Project Planning	78	(17)
Risk Assessment and Project Planning	95	(5)
Project Planning Process	100	(10)
Project Plan Contents	110	(6)
Project Planning Summary	116	(3)
Software Systems Development Process	119	(54)
Introduction	119	(5)
Software Systems Development Process Key Ideas	124	(2)
Software Systems Development Process Overview	126	(6)
Customer	132	(4)
Seller Process Engineering Group	136	(3)
Customer/Seller Development Team and Change Control Board (CCB)	139	(23)
Seller Senior Management	162	(2)
Software Systems Development Process Summary	164	(9)
Change Control Process	173	(90)
Introduction	173	(5)
Change Control Process Key Ideas	178	(3)
Planned and Unplanned Change	181	(6)
The Processing of Changes	187	(20)
Examination of the Change Control Board	207	(17)
Paperwork Support of the Change Control Board	224	(34)
Change Control Process Summary	258	(5)
Product and Process Reviews	263	(118)
Introduction	263	(4)
Product and Process Reviews Key Ideas	267	(2)
A Taxonomy of Product and Process Reviews	269	(27)
Combining Reviews for Software Audits	296	(75)
Product and Process Reviews Summary	371	(10)
Measurement	381	(96)
Introduction	381	(12)
Measurement Key Ideas	393	(3)
Product Integrity	396	(23)
Process Integrity	419	(17)
Capability Maturity Model (CMM) for Software	436	(11)
Other Process-Related Measurements	447	(15)
Measurement Summary	462	(15)
Cultural Change	477	(68)
Introduction	477	(14)
Cultural Change Key Ideas	491	(2)
Process Engineering Group (PEG)	493	(36)
Seller Project Participants and Project Managers	529	(6)
Buyer/User Project Management	535	(3)
Buyer/User Senior Management	538	(2)
Seller Senior Management	540	(2)
Cultural Change Summary	542	(3)
Process Improvement Planning	545	(126)
Introduction	545	(10)
SEE Implementation Planning Key Ideas	555	(4)
Key SEE Implementation Planning Issues	559	(109)
Making Successful Software Development Happen	668	(3)
Appendix A How to Measure Strategic Information Management (SIM)	671	(20)
A.1 Strategic Information Management	671	(5)
A.2 Quantifying Strategic Information Management	676	(2)
A.3 Diagnostic Areas and Diagnostic Criteria	678	(5)
A.4 OM Measurement Map and Measurement Trends	683	(5)
A.5 Summary	688	(3)
Appendix B List of Figures	691	(12)
Appendix C List of Tables	703	(2)
Bibliography	705	(24)
Index	729

Excerpts

Preface We must not promise what we ought not, lest we be called on to perform what we cannot. --Attributed to Abraham Lincoln, speech delivered before the first Republican convention of Illinois, May 29, 1856,The Writings of Abraham Lincoln, ed. Arthur B. Lapsley, vol. 2, p. 249 (1905).Successful Software Developmentmeans "the ability to produce 'good' software systems 'consistently'"Customers want software systems to do what they are supposed to do, to be delivered on time, to be delivered for the agreed-upon cost, and to satisfy any other criteria they may specify. Sellers want the systems they develop to do what the customer wants, to be delivered ahead of schedule or on time, to earn them a reasonable profit, and to satisfy any other criteria that may govern the way they do business. Software systems satisfying both customer and seller criteria are "good." Customers and sellers also want their criteria satisfied "consistently." The software development business should not be a lottery.This book is a practitioner's guide for achieving successful software development.Making It Happenmeans "implementing a 'way' of successful software development"There is no one "way" to develop software systems. If there were, software systems development would have been reduced to an assembly-line process long ago. People with diverse experiences and educational disciplines contribute to advances in software development methodologies, processes, techniques, practices, and tools. This rich diversity brings about different "ways" to develop "good" software systems "consistently."This book is a practitioner's guide for making successful software development happen in a way that makes sense for your environment. Who Should Read This Book?The software development business is centered on a relationship between a customer and a seller of software products and services. So, this book is for both software customers and software sellers. More specifically, the intended audience is anyone who performs one or more of the following activities: Develops software products and software-related products Directly manages people who do the above Manages the above managers Buys/uses products from the above Educates the people aboveIndividuals have used the first edition of this book to complement their particular expertise. Customers have used this book to refine their business dealings with sellers. Sellers have used this book to establish or refine their "way" of developing software systems for their customers. Sellers have also used the book to provide in-house training to their marketing personnel so the marketers better understand what their businesses are selling. Customers and sellers have used the book to train their human resource personnel so they better understand what skill sets are needed for the software development business. Universities have used the book in graduate schools to teach how to be successful in the software development business.For thesoftware customer, we explain and illustrate mechanisms to effectively communicate to the software seller (1) what you want, (2) when you want it, and (3) how much you want to pay for it.For thesoftware seller, we explain and illustrate the mechanisms to effectively communicate (1) to your customer your understanding of what the customer wants and (2) among your project team members how you are going to give the customer what the customer wants.For theeducator, we provide supplemental training materials for the classroom. This material is packaged in a separately available study guide that consists of the following items: Over 500 pages that recast the book's contents as presentation material. This material is organized by chapt