Muutke küpsiste eelistusi

Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management, and Research [Kõva köide]

  • Formaat: Hardback, 832 pages, kõrgus x laius x paksus: 260x186x44 mm, kaal: 1551 g, Drawings: 0 B&W, 0 Color
  • Sari: Practitioners
  • Ilmumisaeg: 19-Jun-2007
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 047014873X
  • ISBN-13: 9780470148730
Teised raamatud teemal:
  • Formaat: Hardback, 832 pages, kõrgus x laius x paksus: 260x186x44 mm, kaal: 1551 g, Drawings: 0 B&W, 0 Color
  • Sari: Practitioners
  • Ilmumisaeg: 19-Jun-2007
  • Kirjastus: John Wiley & Sons Inc
  • ISBN-10: 047014873X
  • ISBN-13: 9780470148730
Teised raamatud teemal:
Boehm's career stretches from a brilliant practice in private industry to high-end government work and finally academia (software engineering, U. of Southern California). His projects now include studies of value-based software engineering, product models, property models and success models called "model-based system engineering and software engineering" (MBASE), and his publications, dozens of which appear here, date from the early 1970s onward. Sorted into chronological order by topic, Boehm's articles reflect the wide range of his research across his diverse career and include software architecture and quality, software economics, software tools, the early spiral model of software process, software risk management, emerging extensions in software process, software and systems management, the state of the art and practice of software engineering. He closes with comments on being a software engineer in the software century. Annotation ©2007 Book News, Inc., Portland, OR (booknews.com)

This is the most authoritative archive of Barry Boehm's contributions to software engineering. Featuring 42 reprinted articles, along with an introduction and chapter summaries to provide context, it serves as a "how-to" reference manual for software engineering best practices. It provides convenient access to Boehm's landmark work on product development and management processes. The book concludes with an insightful look to the future by Dr. Boehm.

Arvustused

"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 xi
Richard W. Selby
Acknowledgements xiii
Software Architecture and Quality
1(86)
Introduction
1(4)
Lawrence Bernstein
Article 1--1. Software Design and Structuring (1975)
5(16)
Barry W. Boehm
Article 1--2. Quantitative Evaluation of Software Quality (1976)
21(26)
Barry W. Boehm
J. R. Brown
M. Lipow
Article 1--3. An Early Application Generator and Other Recollections (1997)
47(22)
Barry W. Boehm
Article 1--4. COTS Integration: Plug and Pray? (1999)
69(6)
Barry W. Boehm
Chris Abts
Article 1--5. Software Defect Reduction Top 10 List (2001)
75(6)
Barry W. Boehm
Victor R. Basili
Article 1--6. COTS-Based Systems Top 10 List (2001)
81(6)
Victor R. Basili
Barry W. Boehm
Software Economics
87(140)
Introduction
87(4)
Richard W. Selby
Article 2--1. Software and Its Impact: A Quantitative Assessment (1973)
91(26)
Barry W. Boehm
Article 2--2. Software Engineering Economics (1984)
117(34)
Barry W. Boehm
Article 2--3. Improving Software Productivity (1987)
151(28)
Barry W. Boehm
Article 2--4. Managing Software Productivity and Reuse (1999)
179(6)
Barry W. Boehm
Article 2--5. Software Economics: A Roadmap (2000)
185(34)
Barry W. Boehm
Kevin J. Sullivan
Article 2--6. Early Experiences in Software Economics (2002)
219(8)
Barry W. Boehm
Software Tools
227(88)
Introduction
227(4)
Arthur B. Pyster
Article 3--1. Some Experience with Automated Aids to the Design of Large-Scale Reliable Software (1975)
231(14)
Barry W. Boehm
Robert K. McClean
D. B. Urfrig
Article 3--2. A Software Development Environment for Improving Productivity (1984)
245(24)
Barry W. Boehm
Maria H. Penedo
E. Don Stuckle
Robert D. Williams
Arthur B. Pyster
Article 3--3. Cost Models for Future Software Life Cycle Processes: COCOMO 2.0 (1995)
269(32)
Barry W. Boehm
Bradford Clark
Ellis Horowitz
Chris Westland
Ray Madachy
Richard W. Selby
Article 3--4. Developing Groupware for Requirements Negotiation: Lessons Learned (2001)
301(14)
Barry W. Boehm
Paul Grunbacher
Robert O. Briggs
Software Process: Early Spiral Model
315(68)
Introduction
315(4)
Walker Royce
Article 4--1. Prototyping Versus Specifying: A Multiproject Experiment (1984)
319(26)
Barry W. Boehm
Terence E. Gray
Thomas Seewaldt
Article 4--2. A Spiral Model of Software Development and Enhancement (1988)
345(22)
Barry W. Boehm
Article 4--3. Anchoring the Software Process (1996)
367(16)
Barry W. Boehm
Software Risk Management
383(116)
Introduction
383(4)
Tom DeMarco
Article 5--1. Software Risk Management: Principles and Practices (1991)
387(16)
Barry W. Boehm
Article 5--2. Section
1. Software Risk Management: Introduction and Overview (1989)
403(24)
Barry W. Boehm
Article 5--3. Section
2. Risk-Management Practices: The Six Basic Steps (1989)
427(44)
Barry W. Boehm
Article 5--4. Section
3. Risk-Resolution Techniques (1989)
471(10)
Barry W. Boehm
Article 5--5. Section
4. Implementing Risk Management (1989)
481(18)
Barry W. Boehm
Software Process: Emerging Extensions
499(74)
Introduction
499(4)
Leon J. Osterweil
Article 6--1. Using the WinWin Spiral Model: A Case Study (1998)
503(20)
Barry W. Boehm
Alexander Egyed
Julie Kwan
Daniel N. Port
Archita Shah
Ray Madachy
Article 6--2. Making RAD Work for Your Project (1999)
523(6)
Barry W. Boehm
Article 6--3. Requirements that Handle IKIWISI, COTS, and Rapid Change (2000)
529(6)
Barry W. Boehm
Article 6--4. Get Ready for Agile Methods, with Care (2002)
535(10)
Barry W. Boehm
Article 6--5. Some Future Trends and Implications for Systems and Software Engineering Processes (2006)
545(28)
Barry W. Boehm
Software and Systems Management
573(54)
Introduction
573(6)
Frederick P. Brooks, Jr.
Article 7--1. Theory-W Software Project Management: Principles and Examples (1989)
579(28)
Barry W. Boehm
Rony Ross
Article 7--2. The Art of Expectations Management (2000)
607(4)
Barry W. Boehm
Article 7--3. Unifying Software Engineering and Systems Engineering (2000)
611(4)
Barry W. Boehm
Article 7--4. Spiral Acquisition of Software-Intensive Systems of Systems (2004)
615(12)
Barry W. Boehm
A. Winsor Brown
Victor R. Basili
Richard Turner
Software Engineering State of the Art and Practice
627(104)
Introduction
627(6)
Victor R. Basili
Article 8--1. Software Engineering (1976)
633(30)
Barry W. Boehm
Article 8--2. Software Engineering---As It Is (1979)
663(24)
Barry W. Boehm
Article 8--3. Gaining Intellectual Control of Software Development (2000)
687(10)
Barry W. Boehm
Victor R. Basili
Article 8--4. A View of 20th and 21st Century Software Engineering (2006)
697(34)
Barry W. Boehm
Value-Based Software Engineering
731(76)
Introduction
731(6)
Kevin J. Sullivan
Article 9--1. Project Termination Doesn't Equal Project Failure (2000)
737(6)
Barry W. Boehm
Article 9--2. Avoiding the Software-Model-Clash Spiderweb (2000)
743
Barry W. Boehm
Daniel N. Port
Mohammed Al-Said
Article 9--3. Value-Based Software Engineering: A Case Study (2003)
479(284)
Barry W. Boehm
Li Guo Huang
Article 9--4. Value-Based Processes for COTS-Based Applications (2005)
763(14)
Ye Yang
Jesal Bhuta
Barry W. Boehm
Daniel N. Port
Article 9--5. An Initial Theory of Value-Based Software Engineering (2005)
777(20)
Barry W. Boehm
Apurva Jain
Being a Software Engineer in the Software Century
797(10)
Barry W. Boehm
Index 807(10)
About the Editor 817


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.