Muutke küpsiste eelistusi

E-raamat: Economics of Software Quality, Portable Documents, The

  • Formaat: PDF+DRM
  • Ilmumisaeg: 14-Jul-2011
  • Kirjastus: Addison-Wesley Educational Publishers Inc
  • Keel: eng
  • ISBN-13: 9780132564724
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 46,31 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Formaat: PDF+DRM
  • Ilmumisaeg: 14-Jul-2011
  • Kirjastus: Addison-Wesley Educational Publishers Inc
  • Keel: eng
  • ISBN-13: 9780132564724
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

Whether consulting, working on projects, or teaching, whenever I need credible, detailed, relevant metrics and insights into the current capabilities and performance of the software engineering profession, I always turn first to Capers Jones work. In this important new book, he and Olivier Bonsignour make the hard-headed, bottom-line, economic case, with facts and data, about why software quality is so important. I know Ill turn to this excellent reference again and again.





Rex Black, President, RBCS

 

Poor quality continues to bedevil large-scale development projects, but few software leaders and practitioners know how to measure quality, select quality best practices, or cost-justify their usage. In The Economics of Software Quality, leading software quality experts Capers Jones and Olivier Bonsignour show how to systematically measure the economic impact of quality and how to use this information to deliver far more business value.

 

Using empirical data from hundreds of software organizations, Jones and Bonsignour show how integrated inspection, structural quality measurement, static analysis, and testing can achieve defect removal rates exceeding 95 percent. They offer innovative guidance for predicting and measuring defects and quality; choosing defect prevention, pre-test defect removal, and testing methods; and optimizing post-release defect reporting and repair.

 

This book will help you





Move beyond functional quality to quantify non-functional and structural quality Prove that improved software quality translates into strongly positive ROI and greatly reduced TCO Drive better results from current investments in Quality Assurance and Testing Use quality improvement techniques to stay on schedule and on budget Avoid hazardous metrics that lead to poor decisions

Arvustused

This book provides the best treatment on the subject of economics of software quality that Ive seen. Peppered with valuable industry data, in-depth analysis, empirical methods for quality improvement, and economic analysis of quality, this book is a must-read for anyone who is interested in this subject. With the many real-life and up-to-date examples and stories linking software quality to daily-life activities, readers will find this book an enjoyable read.

Stephen H. Kan, Senior Technical Staff Member and Program Manager, Software QualityIBM Systems and Technology Group, and author of Metrics and Models in Software Quality Engineering

 

Finally, a book that defines the cost and economics of software quality and their relationship to business value. Facts such as the inability of testing alone to produce quality software, the value of engineering-in quality, and the positive ROI are illustrated in compelling ways. Additionally, this book is a mustread for understanding, managing, and eliminating technical debt from software systems.

Dan Galorath, CEO, Galorath Incorporated & SEER by Galorath

 

Congrats to Capers and Olivier as they release their relevant, extensive, and timely research on the costs of defects in todays software industry. The authors dont stop with the causes of defects; they explore injection points, removal, and prevention approaches to avoid the technical mortgage associated with defective software products. In todays quick-to-market world, an emphasis on strengthening the engineering in software engineering is refreshing. If youre a software developer, manager, student, or user, this book will challenge your perspective on software quality. Many thanks!

Joe Schofield, Sandia National Laboratories; Vice President, IFPUG; CQA, CFPS, CSMS, LSS BB, SEI-certified instructor

 

This masterpiece of a book will empower those who invest in softwareand the businesses and products that depend on itto do so wisely. It is a groundbreaking work that rigorously applies principles of finance, economics, management, quality, and productivity to scrutinize holistically the value propositions and myths underlying the vast sums invested in software. A mustread if you want to get your moneys worth from your software investments.

Leon A. Kappelman, Professor of Information Systems, College of Business, University of North Texas

 

Capers Jones is the foremost leader in the software industry today for software metrics. The Economics of Software Quality is a comprehensive, data-rich study of challenges of quality software across the many application domains. It is an essential read for software quality professionals who wish to better understand the challenges they face and the cost and effectiveness of potential solutions. It is clear that much research and thought has been put into this.

Maysa-Maria Peterson Lach, Senior Principal Software Engineer, Raytheon Missile Systems

 

In no other walk of life do we resist the necessity and validity of precise, rigorous measurement, as software practitioners have so vigorously resisted for more than fifty years. Capers Jones took up the challenge of bringing sanity and predictability to software production more than three decades ago, and now with Olivier Bonsignour, he brings forth his latest invaluable expression of confidence in applying standard engineering and economic discipline to what too often remains the Wild, Wild West of software development.

Douglas Brindley, President & CEO, Software Productivity Research, LLC

Foreword xix
Preface xxi
Acknowledgments xxvii
About the Authors xxxi
Chapter 1 Defining Software Quality and Economic Value
1(34)
Introduction
1(7)
Why Is Software Quality Important?
1(7)
Defining Software Quality
8(9)
Defining Economic Value and Defining the Value of Software Quality
17(16)
The Economic Value of Software and Quality to Enterprises that Build Internal Software for Their Own Use
19(3)
The Economic Value of Software and Quality to Internal Software Users
22(2)
The Economic Value of Software and Quality to Commercial Software Vendors
24(2)
The Economic Value of Software and Quality to COTS Users and Customers
26(2)
The Economic Value of Software and Quality to Embedded Software Companies
28(2)
The Economic Value of Software and Quality to Embedded Equipment Users
30(2)
The Economic Value of Software and Software Quality to Other Business Sectors
32(1)
Multiple Roles Occurring Simultaneously
33(1)
Summary and Conclusions
33(2)
Chapter 2 Estimating and Measuring Software Quality
35(84)
Introduction
35(4)
Using Function Point Metrics for Defect Potentials
39(1)
Software Defect Potentials
39(32)
The Special Case of Software Requirements
45(5)
The Origins of Software Requirements
50(2)
The Size, Structure, and Completeness of Software Requirements
52(3)
Minimizing Software Requirements Defects
55(9)
Conclusions about Software Requirements Defects
64(1)
The Special Case of Coding Defects
65(6)
Estimating Software Defect Prevention
71(3)
Estimating Software Defect Detection and Defect Removal
74(3)
Measuring Application Structural Quality
77(11)
Measuring Reliability
78(1)
Measuring Performance Efficiency
79(1)
Measuring Security
80(1)
Measuring Maintainability
81(2)
Measuring Size
83(1)
Summary of Application Structural Quality Measurement Attributes
83(5)
Examples of Structural Quality Assessments
88(7)
Bypassing the Architecture
88(2)
Failure to Control Processing Volumes
90(1)
Application Resource Imbalances
91(1)
Security Weaknesses
92(1)
Lack of Defensive Mechanisms
93(1)
Desiderata for Systems Evaluating Structural Quality
94(1)
Three Problems That Distort Software Economic Analysis
95(22)
Leakage from Software Historical Data
97(8)
Economic Problems with Lines of Code (LOC) Metrics
105(5)
Economic Problems with Cost-per-Defect Metrics
110(1)
Case A Poor Quality
111(1)
Case B Good Quality
111(3)
Case C Zero Defects
114(1)
Useful Rules of Thumb for Predicting Software Defect Potentials
115(2)
Summary and Conclusions on Software Quality Estimation and Measurement
117(2)
Chapter 3 Software Defect Prevention
119(72)
Introduction
119(16)
The Early History of Defect Prevention Studies in the 1970s at IBM
120(5)
Synergistic Combinations of Defect Prevention Methods
125(2)
Defect Potentials and Defect Origins
127(5)
Defect Prevention, Patterns, and Certified Reusable Materials
132(1)
Software Defect Prevention and Application Size
133(2)
Analysis of Defect Prevention Results
135(53)
Agile Embedded Users
136(1)
Automated Quality Predictions
136(1)
Benchmarks of Software Quality Data
137(1)
Capability Maturity Model Integrated (CMMI)
138(2)
Certification Programs
140(2)
Cost-per-Defect Measures
142(4)
Cost of Quality (COQ)
146(3)
Cyclomatic Complexity Measures (and Related Complexity Measures)
149(7)
Defect Measurements and Defect Tracking
156(3)
Formal Inspections
159(5)
Function Point Quality Measures
164(7)
ISO Quality Standards, IEEE Quality Standards, and Other Industry Standards
171(3)
Quality Function Deployment (QFD)
174(3)
Risk Analysis
177(7)
Six Sigma
184(1)
Static Analysis
185(3)
Summary and Conclusions of Software Defect Prevention
188(3)
Chapter 4 Pretest Defect Removal
191(88)
Introduction
191(5)
Small Project Pretest Defect Removal
196(5)
Large System Pretest Defect Removal
201(7)
Analysis of Pretest Defect Removal Activities
208(69)
Personal Desk Checking
208(1)
Informal Peer Reviews
209(2)
Automated Text Checking for Documents
211(9)
Proofs of Correctness
220(2)
Scrum Sessions
222(2)
Poka Yoke
224(2)
Kaizen
226(5)
Pair Programming
231(4)
Client Reviews of Specifications
235(2)
Independent Verification and Validation (IV&V)
237(2)
Software Quality Assurance (SQA) Reviews
239(7)
Phase Reviews
246(3)
Inspections (Requirements, Architecture, Design, Code, and Other Deliverables)
249(16)
User Documentation Editing and Proofreading
265(2)
Automated Static Analysis of Source Code
267(10)
Summary and Conclusions about Pretest Defect Removal
277(2)
Chapter 5 Software Testing
279(68)
Introduction
279(65)
Black Box and White Box Testing
291(2)
Functional and Nonfunctional Testing
293(1)
Automated and Manual Testing
293(1)
Discussion of the General Forms of Software Testing
294(1)
Subroutine Testing
294(1)
PSP/TSP Unit Testing
295(1)
Extreme Programming (XP) Unit Testing
296(1)
Unit Testing
296(1)
New Function Testing
297(2)
Regression Testing
299(1)
Integration Testing
300(1)
System Testing
301(2)
The Specialized Forms of Software Testing
303(1)
Stress or Capacity Testing
303(1)
Performance Testing
304(1)
Viral Protection Testing
304(4)
Penetration Testing
308(1)
Security Testing
309(1)
Platform Testing
310(1)
Supply Chain Testing
311(1)
Clean Room Testing
311(1)
Litigation Testing
312(1)
Cloud Testing
313(1)
Service Oriented Architecture (SOA) Testing
313(1)
Independent Testing
314(1)
Nationalization Testing
315(1)
Case Study Testing
316(1)
The Forms of Testing Involving Users or Clients
316(1)
Agile Testing
317(1)
Usability Testing
317(1)
Field Beta Testing
318(1)
Lab Testing
319(1)
Customer Acceptance Testing
320(1)
Test Planning
320(1)
Test Case Design Methods
321(2)
Errors or Bugs in Test Cases
323(1)
Numbers of Testing Stages for Software Projects
324(1)
Testing Pattern Variations by Industry and Type of Software
325(4)
Testing Pattern Variations by Size of Application
329(2)
Testing Stages Noted in Lawsuits Alleging Poor Quality
331(1)
Using Function Points to Estimate Test Case Volumes
332(3)
Using Function Points to Estimate the Numbers of Test Personnel
335(2)
Using Function Points to Estimate Testing Effort and Costs
337(5)
Testing by Developers or by Professional Test Personnel
342(2)
Summary and Conclusions on Software Testing
344(3)
Chapter 6 Post-Release Defect Removal
347(86)
Introduction
347(62)
Post-Release Defect Severity Levels
349(2)
Severity Levels from a Structural Quality Perspective
351(7)
Maintainability of Software
358(4)
Defect Discovery Rates by Software Application Users
362(1)
Invalid Defect Reports
363(2)
Abeyant Defects That Occur Under Unique Conditions
365(1)
Duplicate Defects Reported by Many Customers
366(1)
First-Year Defect Discovery Rates
367(1)
Measuring Defect Detection Efficiency (DDE) and Defect Removal Efficiency (DRE)
368(2)
Variations in Post-Release Defect Reports
370(4)
Variations in Methods of Reporting Software Defects
374(4)
Who Repairs Defects after They Are Reported?
378(1)
Case Study 1 Development Personnel Tasked with Maintenance Defect Repairs
379(1)
Case Study 2 Maintenance Specialists Handle Defect Repairs
380(1)
Comparing the Case Studies
381(1)
Litigation Due to Poor Quality
381(3)
Cost Patterns of Post-Release Defect Repairs
384(1)
Software Occupation Groups Involved with Defect Repairs
385(7)
Examining the Independent Variables of Post-Release Defect Repairs
392(1)
The Size of the Application in Function Points
393(11)
Error-Prone Modules in Software Applications
404(5)
User and Industry Costs from Post-Release Defects
409(22)
Impact of Security Flaws on Corporations and Government Agencies
414(2)
Customer Logistics for Defect Reports and Repair Installation
416(1)
Case Study 1 A Small Application by a Small Company
417(3)
Case Study 2 A Large Application by a Large Company
420(5)
Measurement Issues in Maintenance and Post-Release Defect Repairs
425(6)
Summary and Conclusions on Post-Release Defects
431(2)
Chapter 7 Analyzing the Economics of Software Quality
433(112)
Introduction
433(2)
The Economic Value of Software
435(25)
Methods of Measuring Value
435(8)
Funding Approval and Application Size
443(1)
The Impact of Software Construction Difficulties on Software Quality
444(5)
Revenue Generation from Software
449(4)
Difference Between Software and Other Industries
453(1)
Cost Reduction from Software
454(6)
Economic Impact of Low-Quality and High-Quality Software
460(81)
Software Development and Maintenance
461(1)
Software as a Marketed Commodity
462(1)
Software as a Method of Human Effort Reduction
463(1)
Software and Innovative New Kinds of Products
463(2)
Technical Debt---A Measure of the Effect of Software Quality on Software Costs
465(5)
A Framework for Quantifying Business Value
470(6)
Moving Beyond Functional Quality
476(1)
The Impact of Software Structure on Quality
476(1)
The Impact of Staff Training on Quality
477(1)
The Impact of Professional Certification on Quality
478(1)
The Impact of Technology Investment on Quality
479(1)
The Impact of Project Management on Quality
480(1)
The Impact of Quality-Control Methodologies and Tools on Quality
481(3)
The Impact of High and Low Quality on Software Schedules
484(1)
The Impact of High and Low Quality on Software Staffing
484(2)
The Impact of High and Low Quality on Software Development Effort
486(1)
The Impact of High and Low Quality on Development Productivity Rates
486(1)
The Impact of High and Low Quality on Software Development Costs
487(2)
The Impact of High and Low Quality on Development Cost per Function Point
489(1)
The Impact of High and Low Quality on Project Cancellation Rates
490(1)
The Impact of High and Low Quality on the Timing of Cancelled Projects
491(1)
The Impact of High and Low Quality on Cancelled Project Effort
492(1)
The Impact of High and Low Quality on Effort Compared to Average Projects
492(2)
The Impact of High and Low Quality on Software Test Stages
494(2)
The Impact of High and Low Quality on Testing as a Percent of Development
496(1)
The Impact of High and Low Quality on Test Cases per Function Point
497(1)
The Impact of High and Low Quality on Numbers of Test Cases Created
498(1)
The Impact of High and Low Quality on Test Coverage
498(2)
The Impact of Professional Testers on High and Low Quality
500(1)
The Impact of High and Low Quality on Software Defect Potentials
501(2)
The Impact of High and Low Quality on Total Software Defects
503(1)
The Impact of High and Low Quality on Defect Detection Efficiency (DDE)
504(1)
The Impact of High Quality and Low Quality on Defect Removal Efficiency (DRE)
504(1)
The Impact of High and Low Quality on Total Defect Removal
505(2)
The Impact of High and Low Quality on Defects Delivered to Customers
507(1)
The Impact of High and Low Quality on Delivered Defects per Function Point
507(1)
Impact of High and Low Quality on Delivered Defect Severity Levels
508(1)
The Impact of High and Low Quality on Severe Defects per Function Point
509(1)
The Impact of High and Low Quality on Software Reliability
510(1)
The Impact of High and Low Quality on Maintenance and Support
511(1)
The Impact of High and Low Quality on Maintenance and Support Costs
512(1)
The Impact of High and Low Quality on Maintenance Defect Volumes
513(1)
The Impact of High and Low Quality on Software Enhancements
514(1)
The Impact of High and Low Quality on Enhancement Costs
515(1)
The Impact of High and Low Software Quality on Maintenance and Enhancement Staffing
516(1)
The Impact of High and Low Quality on Total Effort for Five Years
517(3)
The Impact of High and Low Quality on Total Cost of Ownership (TCO)
520(3)
The Impact of High and Low Quality on Cost of Quality (COQ)
523(6)
The Impact of High and Low Quality on TCO and COQ per Function Point
529(1)
The Impact of High and Low Quality on the Useful Life of Applications
529(6)
The Impact of High and Low Quality on Software Application Tangible Value
535(1)
The Impact of High and Low Quality on Return on Investment (ROI)
536(1)
The Impact of High and Low Quality on the Costs of Cancelled Projects
537(1)
The Impact of High and Low Quality on Cancellation Cost Differentials
538(1)
The Distribution of High-, Average-, and Low-Quality Software Projects
538(3)
Summary and Conclusions on the Economics of Software Quality
541(4)
High-Quality Results for 10,000 Function Points
541(1)
Low-Quality Results for 10,000 Function Points
542(3)
References and Readings 545(16)
Index 561
Capers Jones, President/CEO of Capers Jones & Associates LLC, founded Software Productivity Research LLC (SPR), where he remains Chief Scientist Emeritus. One of the software engineering fields most influential thought leaders, his books include Patterns of Software Systems Failure and Success; Applied Software Measurement, Third Edition; and Software Assessments, Benchmarks, and Best Practices. Jones is a Distinguished Advisor to the Consortium for IT Software Quality (CISQ).

 

Olivier Bonsignour, Vice President of Product Development at CAST, is responsible for R&D and product management. Prior to CAST he was CIO at the Advanced Research Division of the French Defense Ministry. An early pioneer in distributed systems and object oriented development, Bonsignour holds advanced engineering and management degrees from top institutions in France.