| Introduction |
|
xi | |
|
|
| Acknowledgements |
|
xiii | |
|
Software Architecture and Quality |
|
|
1 | (86) |
|
|
|
1 | (4) |
|
|
|
Article 1--1. Software Design and Structuring (1975) |
|
|
5 | (16) |
|
|
|
Article 1--2. Quantitative Evaluation of Software Quality (1976) |
|
|
21 | (26) |
|
|
|
|
|
|
|
Article 1--3. An Early Application Generator and Other Recollections (1997) |
|
|
47 | (22) |
|
|
|
Article 1--4. COTS Integration: Plug and Pray? (1999) |
|
|
69 | (6) |
|
|
|
|
|
Article 1--5. Software Defect Reduction Top 10 List (2001) |
|
|
75 | (6) |
|
|
|
|
|
Article 1--6. COTS-Based Systems Top 10 List (2001) |
|
|
81 | (6) |
|
|
|
|
|
|
|
87 | (140) |
|
|
|
87 | (4) |
|
|
|
Article 2--1. Software and Its Impact: A Quantitative Assessment (1973) |
|
|
91 | (26) |
|
|
|
Article 2--2. Software Engineering Economics (1984) |
|
|
117 | (34) |
|
|
|
Article 2--3. Improving Software Productivity (1987) |
|
|
151 | (28) |
|
|
|
Article 2--4. Managing Software Productivity and Reuse (1999) |
|
|
179 | (6) |
|
|
|
Article 2--5. Software Economics: A Roadmap (2000) |
|
|
185 | (34) |
|
|
|
|
|
Article 2--6. Early Experiences in Software Economics (2002) |
|
|
219 | (8) |
|
|
|
|
|
227 | (88) |
|
|
|
227 | (4) |
|
|
|
Article 3--1. Some Experience with Automated Aids to the Design of Large-Scale Reliable Software (1975) |
|
|
231 | (14) |
|
|
|
|
|
|
|
Article 3--2. A Software Development Environment for Improving Productivity (1984) |
|
|
245 | (24) |
|
|
|
|
|
|
|
|
|
|
|
Article 3--3. Cost Models for Future Software Life Cycle Processes: COCOMO 2.0 (1995) |
|
|
269 | (32) |
|
|
|
|
|
|
|
|
|
|
|
|
|
Article 3--4. Developing Groupware for Requirements Negotiation: Lessons Learned (2001) |
|
|
301 | (14) |
|
|
|
|
|
|
|
Software Process: Early Spiral Model |
|
|
315 | (68) |
|
|
|
315 | (4) |
|
|
|
Article 4--1. Prototyping Versus Specifying: A Multiproject Experiment (1984) |
|
|
319 | (26) |
|
|
|
|
|
|
|
Article 4--2. A Spiral Model of Software Development and Enhancement (1988) |
|
|
345 | (22) |
|
|
|
Article 4--3. Anchoring the Software Process (1996) |
|
|
367 | (16) |
|
|
|
|
|
383 | (116) |
|
|
|
383 | (4) |
|
|
|
Article 5--1. Software Risk Management: Principles and Practices (1991) |
|
|
387 | (16) |
|
|
|
Article 5--2. Section 1. Software Risk Management: Introduction and Overview (1989) |
|
|
403 | (24) |
|
|
|
Article 5--3. Section 2. Risk-Management Practices: The Six Basic Steps (1989) |
|
|
427 | (44) |
|
|
|
Article 5--4. Section 3. Risk-Resolution Techniques (1989) |
|
|
471 | (10) |
|
|
|
Article 5--5. Section 4. Implementing Risk Management (1989) |
|
|
481 | (18) |
|
|
|
Software Process: Emerging Extensions |
|
|
499 | (74) |
|
|
|
499 | (4) |
|
|
|
Article 6--1. Using the WinWin Spiral Model: A Case Study (1998) |
|
|
503 | (20) |
|
|
|
|
|
|
|
|
|
|
|
|
|
Article 6--2. Making RAD Work for Your Project (1999) |
|
|
523 | (6) |
|
|
|
Article 6--3. Requirements that Handle IKIWISI, COTS, and Rapid Change (2000) |
|
|
529 | (6) |
|
|
|
Article 6--4. Get Ready for Agile Methods, with Care (2002) |
|
|
535 | (10) |
|
|
|
Article 6--5. Some Future Trends and Implications for Systems and Software Engineering Processes (2006) |
|
|
545 | (28) |
|
|
|
Software and Systems Management |
|
|
573 | (54) |
|
|
|
573 | (6) |
|
|
|
Article 7--1. Theory-W Software Project Management: Principles and Examples (1989) |
|
|
579 | (28) |
|
|
|
|
|
Article 7--2. The Art of Expectations Management (2000) |
|
|
607 | (4) |
|
|
|
Article 7--3. Unifying Software Engineering and Systems Engineering (2000) |
|
|
611 | (4) |
|
|
|
Article 7--4. Spiral Acquisition of Software-Intensive Systems of Systems (2004) |
|
|
615 | (12) |
|
|
|
|
|
|
|
|
|
Software Engineering State of the Art and Practice |
|
|
627 | (104) |
|
|
|
627 | (6) |
|
|
|
Article 8--1. Software Engineering (1976) |
|
|
633 | (30) |
|
|
|
Article 8--2. Software Engineering---As It Is (1979) |
|
|
663 | (24) |
|
|
|
Article 8--3. Gaining Intellectual Control of Software Development (2000) |
|
|
687 | (10) |
|
|
|
|
|
Article 8--4. A View of 20th and 21st Century Software Engineering (2006) |
|
|
697 | (34) |
|
|
|
Value-Based Software Engineering |
|
|
731 | (76) |
|
|
|
731 | (6) |
|
|
|
Article 9--1. Project Termination Doesn't Equal Project Failure (2000) |
|
|
737 | (6) |
|
|
|
Article 9--2. Avoiding the Software-Model-Clash Spiderweb (2000) |
|
|
743 | |
|
|
|
|
|
|
|
Article 9--3. Value-Based Software Engineering: A Case Study (2003) |
|
|
479 | (284) |
|
|
|
|
|
Article 9--4. Value-Based Processes for COTS-Based Applications (2005) |
|
|
763 | (14) |
|
|
|
|
|
|
|
|
|
Article 9--5. An Initial Theory of Value-Based Software Engineering (2005) |
|
|
777 | (20) |
|
|
|
|
|
Being a Software Engineer in the Software Century |
|
|
797 | (10) |
|
|
| Index |
|
807 | (10) |
| About the Editor |
|
817 | |