Trustworthy Systems Through Quantitative Software Engineering

A benchmark text on software development and quantitative software engineering
"We all trust software. All too frequently, this trust is misplaced. Larry Bernstein has created and applied quantitative techniques to develop trustworthy software systems. He and C. M. Yuhas have organized this quantitative experience into a book of great value to make software trustworthy for all of us."
—Barry Boehm
Trustworthy Systems Through Quantitative Software Engineering proposes a novel, reliability–driven software engineering approach, and discusses human factors in software engineering and how these affect team dynamics. This practical approach gives software engineering students and professionals a solid foundation in problem analysis, allowing them to meet customers′ changing needs by tailoring their projects to meet specific challenges, and complete projects on schedule and within budget.
Specifically, it helps developers identify customer requirements, develop software designs, manage a software development team, and evaluate software products to customer specifications. Students learn "magic numbers of software engineering," rules of thumb that show how to simplify architecture, design, and implementation.
Case histories and exercises clearly present successful software engineers′ experiences and illustrate potential problems, results, and trade–offs. Also featuring an accompanying Web site with additional and related material, Trustworthy Systems Through Quantitative Software Engineering is a hands–on, project–oriented resource for upper–level software and computer science students, engineers, professional developers, managers, and professionals involved in software engineering projects.

Spis treści:
Preface.
Acknowledgment.
PART 1: GETTING STARTED.
1. Think Like an Engineer—Especially for Software.
1.1 Making a Judgment.
1.2 The Software Engineer& #8242;s Responsibilities.
1.3 Ethics.
1.4 Software Development Processes.
1.5 Choosing a Process.
1.5.1 No–Method "Code and Fix" Approach.
1.5.2 Waterfall Method.
1.5.3 Spiral Method: Planned Risk Assessment–Driven Process.
1.5.4 Development Plan Approach.
1.5.5 Planned Incremental Development Process.
1.5.6 Agile Process, a Apparent Oxymoron.
1.6 Re–emergence of Model–Based Software Development.
1.7 Process Evolution.
1.8 Organization Structure.
1.9 Principles of Sound Organizations.
1.10 Short Projects–4 to 6 Weeks.
1.10.1 Project 1: Automating Library Overdue Book Notices.
1.10.2 Project 2: Ajax Transporters, Inc. Maintenance Project.
1.11 Problems.
2. People, Process, Product, Project–The Big Four.
2.1 People: Cultivate the Guru and Support the Majority.
2.1.1   How to Recognize a Guru.
2.1.2 How to Attract a Guru to Your Project.
2.1.3 How to Keep Your Gurus Working.
2.1.4 How to Support the Majority.
2.2 Product: "Buy Me!".
2.2.1 Reliable Software Products.
2.2.2 Useful Software Products.
2.2.3 Good User Experience.
2.3.Process: "OK, How Will We Build This?".
2.3.1 Agile Processes.
2.3.2 Object Oriented Opportunities.
2.3.3 Meaningful Metrics.
2.4 Project: Making It Work.
2.5 Problems.
2.6 Case Studies.
PART 2: ETHICS AND PROFESSIONALISM.
3. Software Requirements.
3.1 What Can Go Wrong With Requirements.
3.2 The Formal Processes.
3.3 Robust Requirements.
3.4 Requirements Synthesis.
3.5 Requirements Specification.
3.6 Quantitative Software Engineering Gates.
3.7 SQFD Technology.
3.8 ICED–T Metrics.
3.8.1 ICED–T Insights.
3.8.2 Using the ICED–T Model.
3.9 Development Sizing and Scheduling with Function Points.
3.9.1 Function Point Analysis Experience.
3.9.2 NCSLOC vs Function Points.
3.9.3 Computing Simplified Functi on Points (sFP).
3.10 Case Study: The Case of the No–Show Service.
3.11 Problems.
4. Prototyping.
4.1 Make It Work; Then Make It Work Right.
4.1.1 How to Get at the Governing Requirements.
4.1.2 Rapid Application Prototype.
4.1.3 What′s Soft is Hard.
4.2 So What Happens Monday Morning?.
4.2.1 What Needs to Be Prototyped?.
4.2.2 How Do You Build a Prototype?.
4.2.3 How Is the Prototype Used?.
4.2.4 What Happens to the Prototype?.
4.3 It Works, But Will It Continue to Work?.
4.4 Case Study: The Case of the Driven Development.
4.4.1 Significant Results.
4.4.2 Lessons Learned.
4.4.3 Additional Business Histories.
4.5 Why is Prototyping So Important?.
4.6 Prototyping Deficiencies.
4.7 Iterative Prototyping.
4.8 Case Study: The Case of the Famished Fish.
4.9 Problems.
5. Architecture.
5.1 Architecture Is a System′s DNA.
5.2 Pity the Poor System Administrator.
5.3 Software Architecture Experience.
5.4 Process and Model.
5.5 Components.
5.5.1 Components as COTS.
5.5.2 Encapsulation and Abstraction.
5.5.3 Ready or Not, Objects Are Here.
5.6 UNIX.
5.7 TL1.
5.7.1 Mission.
5.7.2 Comparative Analysis.
5.7.3 Message Formatting.
5.7.4 TL1 Message Formulation.
5.7.5 Industry Support of TL1.
5.8 Documenting the Architecture.
5.8.1 Diary or Log Document.
5.8.2 Debriefing Document.
5.8.3 Users of Architecture Documentation.
5.9 Architecture Reviews.
5.10 Middleware.
5.11 How Many Times Before We Learn?.
5.11.1 Comair Cancels 1,100 Flights on Christmas 2004.
5.11.2 Air Traffic Shutdown in September 2004.
5.11.3 NASA Misses Mars, 2004.
5.11.4 Case Study: The Case of the Preempted Priorities.
5.12 Financial Systems Architecture.
5.12.1 Typical Business Processes.
5.12.2 Product–Related Layer in the Architecture.
5.12.3 Finding Simple Components.
5.13 Design and Architectural Process.
5.1 4 Problems.
6. Estimation, Planning and Investment.
6.1 Software Size Estimation.
6.1.1 Pitfalls and Pratfalls.
6.1.2 Software Size Metrics.
6.2 Function Points.
6.2.1 Fundamentals of Function Point Analysis.
6.2.2 Brief History.
6.2.3 Objectives of Function Point Analysis.
6.2.4 Characteristics of Quality Function Point Analysis.
6.3 Five Major Elements of Function Point Counting.
6.3.1 External Input (EI).
6.3.2 External Output (EO).
6.3.3 External Inquiry EQ).
6.3.4 Internal Logical File (ILF).
6.3.5 External Interface Files (EIF).
6.4 Each Element Can Be Simple, Average or Complex.
6.5 Sizing an Automation Project with FPA.
6.5.1 Advantages of Function Point Measurement.
6.5.2 Disadvantages of Function Point Measurement.
6.5.3 Results Common to FPA.
6.5.4 FPA Accuracy.
6.6 SLOC Metric.
6.6.1 Company Statistics.
6.6.2 Reuse.
6.6.3 Wide Band Delphi.
6.6.4 Disadvantages of SLOC.
6.7 Production Planning.
6.7.1 Productivity.
6.7.2 Mediating Culture.
6.7.3 Customer Relations.
6.7.4 Centralized Support Functions.
6.8 Investment.
6.8.1 Cost Estimation Models.
6.8.2 COCOMO.
6.8.3 Scheduling Tools–PERT, Gantt.
6.8.4 Project Manager′s Job.
6.9 Problems.
7. Design for Trustworthiness.
7.1 Built–in Trustworthiness.
7.2 Software Reliability Overview.
7.3 Design Reviews.
7.3.1 Topics for the Design Review.
7.3.2 Case Study.
7.3.3 Interfaces.
7.3.4 Software Structure Influences Reliability.
7.3.5 Components.
7.3.6 Open & Closed Principle.
7.3.7 The Liskov Substitution Principle.
7.3.8 Comparing Object Oriented Programming with Componentry.
7.3.9 Politics of Reuse.
7.3.9.1 Qualified Successes.
7.3.9.2 Conditions Fostering Reuse.
7.3.9.3 Reuse "As Is".
7.4 Design Principles.
7.4.1 Strong Cohesion.
7.4.2 Weak Coupling.
7.4.3 Information Hiding.
7.4.4 Inheritance.
7.4