Software Engineering

Richard W. Selby, PhD, is the Head of Software Products at Northrop Grumman Space Technology and an Adjunct Professor of Computer Science at the University of Southern California. He cowrote the international bestselling book Microsoft Secrets: How the World's Most Powerful Software Company Creates Technology, Shapes Markets, and Manages People.

"The fact that we still face basically the same problems in the areas of software architecture, reuse, and development with modern approaches (such as reliability and performance, as well as the software development process in service-oriented architectures) makes this book continue to be highly relevant.  This, and the sheer pleasure of reading it, makes the book a remarkable and extraordinary contribution to an otherwise buzzword-driven book market." (Computing Reviews, March 25, 2008)

• Introduction xiRichard W. SelbyAcknowledgements xiiiChapter 1. Software Architecture and Quality 1Introduction 1Lawrence BernsteinArticle 1–1. Software Design and Structuring (1975) 5Barry W. BoehmArticle 1–2. Quantitative Evaluation of Software Quality (1976) 21Barry W. Boehm, J. R. Brown, and M. LipowArticle 1–3. An Early Application Generator and Other Recollections (1997) 47Barry W. BoehmArticle 1–4. COTS Integration: Plug and Pray? (1999) 69Barry W. Boehm and Chris AbtsArticle 1–5. Software Defect Reduction Top 10 List (2001) 75Barry W. Boehm and Victor R. BasiliArticle 1–6. COTS-Based Systems Top 10 List (2001) 81Victor R. Basili and Barry W. BoehmChapter 2. Software Economics 87Introduction 87Richard W. SelbyArticle 2–1. Software and Its Impact: A Quantitative Assessment (1973) 91Barry W. BoehmArticle 2–2. Software Engineering Economics (1984) 117Barry W. BoehmArticle 2–3. Improving Software Productivity (1987) 151Barry W. BoehmArticle 2–4. Managing Software Productivity and Reuse (1999) 179Barry W. BoehmArticle 2–5. Software Economics: A Roadmap (2000) 185Barry W. Boehm and Kevin J. SullivanArticle 2–6. Early Experiences in Software Economics (2002) 219Barry W. BoehmChapter 3. Software Tools 227Introduction 227Arthur B. PysterArticle 3–1. Some Experience with Automated Aids to the Design of Large-Scale Reliable Software (1975) 231Barry W. Boehm, Robert K. McClean, and D. B. UrfrigArticle 3–2. A Software Development Environment for Improving Productivity (1984) 245Barry W. Boehm, Maria H. Penedo, E. Don Stuckle, Robert D. Williams, and Arthur B. PysterArticle 3–3. Cost Models for Future Software Life Cycle Processes: Cocomo 2.0 (1995) 269Barry W. Boehm, Bradford Clark, Ellis Horowitz, Chris Westland, Ray Madachy, and Richard W. SelbyArticle 3–4. Developing Groupware for Requirements Negotiation: Lessons Learned (2001) 301Barry W. Boehm, Paul Grünbacher, and Robert O. BriggsChapter 4. Software Process: Early Spiral Model 315Introduction 315Walker RoyceArticle 4–1. Prototyping Versus Specifying: A Multiproject Experiment (1984) 319Barry W. Boehm, Terence E. Gray, and Thomas SeewaldtArticle 4–2. A Spiral Model of Software Development and Enhancement (1988) 345Barry W. BoehmArticle 4–3. Anchoring the Software Process (1996) 367Barry W. BoehmChapter 5. Software Risk Management 383Introduction 383Tom DeMarcoArticle 5–1. Software Risk Management: Principles and Practices (1991) 387Barry W. BoehmArticle 5–2. Section 1. Software Risk Management: Introduction and Overview (1989) 403Barry W. BoehmArticle 5–3. Section 2. Risk-Management Practices: The Six Basic Steps (1989) 427Barry W. BoehmArticle 5–4. Section 3. Risk-Resolution Techniques (1989) 471Barry W. BoehmArticle 5–5. Section 4. Implementing Risk Management (1989) 481Barry W. BoehmChapter 6. Software Process: Emerging Extensions 499Introduction 499Leon J. OsterweilArticle 6–1. Using the WinWin Spiral Model: A Case Study (1998) 503Barry W. Boehm, Alexander Egyed, Julie Kwan, Daniel N. Port, Archita Shah, and Ray MadachyArticle 6–2. Making RAD Work for Your Project (1999) 523Barry W. BoehmArticle 6–3. Requirements that Handle IKIWISI, COTS, and Rapid Change (2000) 529Barry W. BoehmArticle 6–4. Get Ready for Agile Methods, with Care (2002) 535Barry W. BoehmArticle 6–5. Some Future Trends and Implications for Systems and Software Engineering Processes (2006) 545Barry W. BoehmChapter 7. Software and Systems Management 573Introduction 573Frederick P. Brooks, Jr.Article 7–1. Theory-W Software Project Management: Principles and Examples (1989) 579Barry W. Boehm and Rony RossArticle 7–2. The Art of Expectations Management (2000) 607Barry W. BoehmArticle 7–3. Unifying Software Engineering and Systems Engineering (2000) 611Barry W. BoehmArticle 7–4. Spiral Acquisition of Software-Intensive Systems of Systems (2004) 615Barry W. Boehm, A. Winsor Brown, Victor R. Basili, and Richard TurnerChapter 8. Software Engineering State of the Art and Practice 627Introduction 627Victor R. BasiliArticle 8–1. Software Engineering (1976) 633Barry W. BoehmArticle 8–2. Software Engineering—As It Is (1979) 663Barry W. BoehmArticle 8–3. Gaining Intellectual Control of Software Development (2000) 687Barry W. Boehm and Victor R. BasiliArticle 8–4. A View of 20th and 21st Century Software Engineering (2006) 697Barry W. BoehmChapter 9. Value-Based Software Engineering 731Introduction 731Kevin J. SullivanArticle 9–1. Project Termination Doesn’t Equal Project Failure (2000) 737Barry W. BoehmArticle 9–2. Avoiding the Software-Model-Clash Spiderweb (2000) 743Barry W. Boehm, Daniel N. Port, and Mohammed Al-SaidArticle 9–3. Value-Based Software Engineering: A Case Study (2003) 749Barry W. Boehm and Li Guo HuangArticle 9–4. Value-Based Processes for COTS-Based Applications (2005) 763Ye Yang, Jesal Bhuta, Barry W. Boehm, and Daniel N. PortArticle 9–5. An Initial Theory of Value-Based Software Engineering (2005) 777Barry W. Boehm and Apurva JainChapter 10. Being a Software Engineer in the Software Century 797Barry W. BoehmIndex 807About the Editor 817