Solid Software
Published on 11. July 2001
Book
Paperback/Softback
304 pages
978-0-13-091298-5 (ISBN)
Description
No large software system will ever be perfect, but decision-makers need better ways to evaluate software quality -- especially in software that is business-critical, mission-critical, or utilized in life-or-death environments. In this book, three leading software quality consultants present practical techniques for projecting software quality and robustness in any software system or software-intensive product. Unlike other books, this one provides a business context, helping decision-makers make intelligent, responsible tradeoffs. KEY TOPICS: The authors help decision-makers understand what levels of quality and robustness are reasonable to expect at every stage of the software lifecycle, including development, deployment, and maintenance. They present best-practices techniques for projecting software quality, and assessing systems in production. Solid Software presents many real-world examples based on the authors' extensive experience as software quality consultants, and shares the insights of key software decision-makers throughout the U.S. in Europe.MARKET: For all software designers, system engineers, regulators, project/program managers, and chief technology officers who must judge quality and make tradeoffs in critical software and software-intensive products.
More details
Persons
SHARI LAWRENCE PFLEEGER is President of Systems/Software, Inc., a leading software engineering consultancy. She has been founder/director of Howard University's Center for Research in Evaluating Software Technology, visiting scientist at the City University (London) Centre for Software Reliability, principal scientist at MITRE Corporation's Software Engineering Center, and manager of the measurement program at Contel Technology Center.
LES HATTON is managing partner at Oakwood Consulting, advising clients such as Ford and Philips on software system safety.
CHARLES C. HOWELL, Chief Engineer at MITRE Corporation, has served as Director of Consulting Services at Reliable Software Technologies and as Java Technologist at Sun Microsystems.
LES HATTON is managing partner at Oakwood Consulting, advising clients such as Ford and Philips on software system safety.
CHARLES C. HOWELL, Chief Engineer at MITRE Corporation, has served as Director of Consulting Services at Reliable Software Technologies and as Java Technologist at Sun Microsystems.
Content
(Note: Each chapter concludes with section on References.)
1. Why Is This Book Needed?
Software: The Universal Weak Link? Why Is This So Hard? Solid, Survivable Software. Surviving a Software Project. The Road Ahead.
2. Defining Quality: What Do You Want?
Five Views of Quality. Risky Business. Risk and Quality. Consequences of Failure. Rules of the Road.
3. Hazard Analysis.
The Rewards of Caution. What is Hazard Analysis? HAZOP. Fault-Tree Analysis. Failure Modes and Effects Analysis. How to Describe Problems. Planning for Hazard Analysis. For Additional Information.
4. Testing.
Types of Faults. Testing Strategies. Test Cases and Results. Who Should Test? Automated Testing Tools. Testing: Good and Bad. How Much Testing Is Enough? Assessing Testing Risk and Trade-offs.
5. Software Design.
The Audience for Design. The Meaning of Good Design. Issues to Consider in Good Design. Design Leverage Points.
6.Prediction.
Predicting Software Characteristics. Predicting Effort. Evaluating Mode Accuracy. Predicting and Evaluating Return on Investment. Predicting and Managing Risk.
7. Peer Reviews.
What Is a Review? Review Effectiveness. Product Inspection. Process Improvement. How to Improve Review Results: The Psychological Basis. Automating the Review Process. Pitfalls of the Review Process. The Role of Checklists.
8. Static Analysis.
Static Fault versus Dynamic Failure. When Faults Cause Failures. Early versus Late Detection. Measurements for Static Analysis. Coverage: How Much is Enough? Approaches to Static Analysis. Static Noise.
9. Configuration Management.
Constant Change. Worth the Effort? Getting Control. Versions, Releases, and the Challenge of Commercial Components. The Fur Facets of SCM. Applying the Principles: Regression Testing. Change Control Boards. Impact Analysis. One Size Does Not Fit All. Tool Support. Begin with the End, but Start Where You Are.
10. Using Appropriate Tools.
How Tools Develop. The Evolution of Software Tools. Tool Properties. The Anatomy of a Valuable Tool. Tool Quality. Tooling and Process. Tooling and the Organization.
11. Trust but Verify.
Where We Are. Learning from Mistakes. The Importance of Being Human. Best Practices. Making Decisions. What's Next?
Index.
1. Why Is This Book Needed?
Software: The Universal Weak Link? Why Is This So Hard? Solid, Survivable Software. Surviving a Software Project. The Road Ahead.
2. Defining Quality: What Do You Want?
Five Views of Quality. Risky Business. Risk and Quality. Consequences of Failure. Rules of the Road.
3. Hazard Analysis.
The Rewards of Caution. What is Hazard Analysis? HAZOP. Fault-Tree Analysis. Failure Modes and Effects Analysis. How to Describe Problems. Planning for Hazard Analysis. For Additional Information.
4. Testing.
Types of Faults. Testing Strategies. Test Cases and Results. Who Should Test? Automated Testing Tools. Testing: Good and Bad. How Much Testing Is Enough? Assessing Testing Risk and Trade-offs.
5. Software Design.
The Audience for Design. The Meaning of Good Design. Issues to Consider in Good Design. Design Leverage Points.
6.Prediction.
Predicting Software Characteristics. Predicting Effort. Evaluating Mode Accuracy. Predicting and Evaluating Return on Investment. Predicting and Managing Risk.
7. Peer Reviews.
What Is a Review? Review Effectiveness. Product Inspection. Process Improvement. How to Improve Review Results: The Psychological Basis. Automating the Review Process. Pitfalls of the Review Process. The Role of Checklists.
8. Static Analysis.
Static Fault versus Dynamic Failure. When Faults Cause Failures. Early versus Late Detection. Measurements for Static Analysis. Coverage: How Much is Enough? Approaches to Static Analysis. Static Noise.
9. Configuration Management.
Constant Change. Worth the Effort? Getting Control. Versions, Releases, and the Challenge of Commercial Components. The Fur Facets of SCM. Applying the Principles: Regression Testing. Change Control Boards. Impact Analysis. One Size Does Not Fit All. Tool Support. Begin with the End, but Start Where You Are.
10. Using Appropriate Tools.
How Tools Develop. The Evolution of Software Tools. Tool Properties. The Anatomy of a Valuable Tool. Tool Quality. Tooling and Process. Tooling and the Organization.
11. Trust but Verify.
Where We Are. Learning from Mistakes. The Importance of Being Human. Best Practices. Making Decisions. What's Next?
Index.