SOFTWARE QUALITY IN 2012: A SURVEY OF THE STATE OF THE ART
|
|
|
- Joleen Mitchell
- 10 years ago
- Views:
Transcription
1 Namcook Analytics LLC SOFTWARE QUALITY IN 2012: A SURVEY OF THE STATE OF THE ART Capers Jones, CTO Web: Capers.Jones3@GMAILcom May 1, 2012 SOURCES OF QUALITY DATA Data collected from 1984 through 2012 About 675 companies (150 clients in Fortune 500 set) About 35 government/military groups About 13,500 total projects New data = about projects per month Data collected from 24 countries Observations during more than 15 lawsuits SWQUAL08\2 1
2 BASIC DEFINITIONS OF SOFTWARE QUALITY Functional Software Quality Software that combines low defect rates and high levels Of user satisfaction. The software should also meet all user requirements and adhere to international standards. Structural Software Quality Software that exhibits a robust architecture and can operate In a multi-tier environment without failures or degraded performance. Software has low cyclomatic complexity levels. Aesthetic Software Quality Software with elegant and easy to use commands and Interfaces, attractive screens, and well formatted outputs. SWQUAL08\3 ECONOMIC DEFINITIONS OF SOFTWARE QUALITY Technical debt The assertion (by Ward Cunningham in 1992) that quick and careless development with poor quality leads to many years of expensive maintenance and enhancements. Cost of Quality (COQ) The overall costs of prevention, appraisal, internal failures, and external failures. For software these mean defect prevention, pre-test defect removal, testing, and post-release defect repairs. (Consequential damages are usually not counted.) Total Cost of Ownership (TCO) The sum of development + enhancement + maintenance + support from day 1 until application is retired. (Recalculation at 5 year intervals is recommended.) SWQUAL08\4 2
3 FUNDAMENTAL SOFTWARE QUALITY METRICS Defect Potentials Sum of requirements errors, design errors, code errors, document errors, bad fix errors, test plan errors, and test case errors Defect Discovery Efficiency (DDE) Percent of defects discovered before release Defect Removal Efficiency (DRE) Percent of defects removed before release Defect Severity Levels (Valid unique defects) Severity 1 = Total stoppage Severity 2 = Major error Severity 3 = Minor error Severity 4 = Cosmetic error SWQUAL08\5 FUNDAMENTAL SOFTWARE QUALITY METRICS (cont.) Standard Cost of Quality Prevention Appraisal Internal failures External failures Revised Software Cost of Quality Defect Prevention Pre-Test Defect Removal (inspections, static analysis) Testing Defect Removal Post-Release Defect Removal Error-Prone Module Effort Identification Removal or redevelopment repairs and rework SWQUAL08\6 3
4 QUALITY MEASUREMENT PROBLEMS Cost per defect penalizes quality! (Buggiest software has lowest cost per defect!) Lines of code penalize high-level languages! Lines of code ignore non-coding defects! Most companies don t measure all defects! Most common omissions are requirement bugs, design bugs, and bugs found by desk checks and unit testing. Real bugs can outnumber measured bugs by more than 5 to 1! SWQUAL08\7 COST PER DEFECT PENALIZES QUALITY Case A Case B High quality Low quality Defects found Test case creation $10,000 $10,000 Test case execution $10,000 $10,000 Defect repairs $10,000 $70,000 TOTAL $30,000 $90,000 Cost per Defect $600 $180 $ Cost savings $60,000 $0.00 SWQUAL08\8 4
5 LINES OF CODE HARM HIGH-LEVEL LANGUGES Case A JAVA Case B C KLOC Function points 1,000 1,000 Code defects found 500 1,250 Defects per KLOC Defects per FP Defect repairs $70,000 $175,000 $ per KLOC $1,400 $1,400 $ per Defect $140 $140 $ per Function Point $70 $175 $ cost savings $105,000 $0.00 SWQUAL08\9 U.S. AVERAGES FOR SOFTWARE QUALITY (Data expressed in terms of defects per function point) Defect Removal Delivered Defect Origins Potential Efficiency Defects Requirements % 0.23 Design % 0.19 Coding % 0.09 Documents % 0.12 Bad Fixes % 0.12 TOTAL % 0.75 (Function points show all defect sources - not just coding defects) (Code defects = 35% of total defects) SWQUAL08\10 5
6 BEST IN CLASS SOFTWARE QUALITY (Data expressed in terms of defects per function point) Defect Removal Delivered Defect Origins Potential Efficiency Defects OBSERVATIONS Requirements % 0.08 Design % 0.02 Coding % 0.01 Documents % 0.01 Bad Fixes % 0.01 TOTAL % 0.13 (Most often found in systems software > SEI CMM Level 3 or in TSP projects) SWQUAL08\11 POOR SOFTWARE QUALITY - MALPRACTICE (Data expressed in terms of defects per function point) Defect Removal Delivered Defect Origins Potential Efficiency Defects OBSERVATIONS Requirements % 0.75 Design % 1.10 Coding % 0.50 Documents % 0.30 Bad Fixes % 0.40 TOTAL % 3.05 (Most often found in large water fall projects > 10,000 Function Points). SWQUAL08\12 6
7 GOOD QUALITY RESULTS > 90% SUCCESS RATE Formal Inspections (Requirements, Design, and Code) Text static analysis Code static analysis (for about 25 languages out of 2,500 in all) Joint Application Design (JAD) Requirements modeling Functional quality metrics using function points Structural quality metrics such as cyclomatic complexity Defect Detection Efficiency (DDE) measurements Defect Removal Efficiency (DRE) measurements Automated defect tracking tools Active quality Assurance (> 3% SQA staff) Mathematical test case design based on design of experiments Quality estimation tools Testing specialists (certified) Root-Cause Analysis SWQUAL08\13 MIXED QUALITY RESULTS: < 50% SUCCESS RATE CMMI level 3 or higher (some overlap among CMMI levels: Best CMMI 1 groups better than worst CMMI 3 groups) ISO and IEEE quality standards (Prevent low quality; Little benefit for high-quality teams) Six-Sigma methods (unless tailored for software projects) Quality function deployment (QFD) Independent Verification & Validation (IV & V) Quality circles in the United States (more success in Japan) Clean-room methods for rapidly changing requirements Kaizan (moving from Japan to U.S. and elsewhere) Cost of quality without software modifications Pair programming SWQUAL08\14 7
8 POOR QUALITY RESULTS: < 25% SUCCESS RATE Testing as only form of defect removal Informal Testing and uncertified test personnel Testing only by developers; no test specialists Passive Quality Assurance (< 3% QA staff) Token Quality Assurance (< 1% QA staff) LOC Metrics for quality (omits non-code defects) Cost per defect metric (penalizes quality) Failure to estimate quality or risks early Quality measurement leakage such as unit test bugs SWQUAL08\15 SOFTWARE QUALITY OBSERVATIONS Quality Measurements Have Found: Individual programmers -- Less than 50% efficient in finding bugs in their own software Normal test steps -- often less than 75% efficient (1 of 4 bugs remain) Design Reviews and Code Inspections -- often more than 65% efficient; have topped 90% Static analysis often more than 65% efficient; has topped 95% Inspections, static analysis, and testing combined lower costs and schedules by > 20%; lower total cost of ownership (TCO) by > 45%. SWQUAL08\16 8
9 SOFTWARE DEFECT ORIGINS 1. Requirements Hardest to prevent and repair 2. Requirements creep Very troublesome source of bugs 3. Architecture Key to structural quality 4. Design Most severe and pervasive 5. Source code Most numerous; easiest to fix 6. Security flaws Hard to find and hard to fix 7. Documentation Can be serious if ignored 8. Bad fixes Very difficult to find 9. Bad test cases Numerous but seldom measured 10. Data errors Very common but not measured 11. Web content Very common but not measured 12. Structure Hard to find by testing; inspections and static analysis can identify multi-tier platform defects SWQUAL08\17 SOFTWARE DEFECT SEVERITY CATEGORIES Severity 1: TOTAL FAILURE S 1% at release Severity 2: MAJOR PROBLEMS 20% at release Severity 3: MINOR PROBLEMS 35% at release Severity 4: COSMETIC ERRORS 44% at release STRUCTURAL MULTI-TIER DEFECTS 15% of reports INVALID USER OR SYSTEM ERRORS 15% of reports DUPLICATE MULTIPLE REPORTS 30% of reports ABEYANT CAN T RECREATE ERROR 5% of reports SWQUAL08\18 9
10 HOW QUALITY AFFECTS SOFTWARE COSTS Pathological Technical debt COST Healthy Poor quality is cheaper until the end of the coding phase. After that, high quality is cheaper. Requirements Design Coding Testing Maintenance TIME SWQUAL08\19 U. S. SOFTWARE QUALITY AVERAGES CIRCA 2012 (Defects per Function Point) System Commercial Information Military Outsource Software Software Software Software Software Defect Potentials Defect Removal 94% 90% 73% 96% 92% Efficiency Delivered Defects First Year Discovery Rate 65% 70% 30% 75% 60% First Year Reported Defects SWQUAL08\20 10
11 U. S. SOFTWARE QUALITY AVERAGES CIRCA 2012 (Defects per Function Point) Web Embedded SEI-CMM 3 SEI-CMM 1 Overall Software Software Software Software Average Defect Potentials Defect Removal 72% 95% 95% 83% 86.7% Efficiency Delivered Defects First Year Discovery Rate 95% 90% 60% 35% 64.4% First Year Reported Defects SWQUAL08\21 SOFTWARE SIZE VS DEFECT REMOVAL EFFICIENCY (Data Expressed in terms of Defects per Function Point) Size Defect Potential Defect Removal Efficiency Delivered Defects 1st Year Discovery Rate 1st Year Reported Defects % % % % % % % % % % % % 0.72 AVERAGE % % 0.38 SWQUAL08\22 11
12 SOFTWARE DEFECT POTENTIALS AND DEFECT REMOVAL EFFICIENCY FOR EACH LEVEL OF SEI CMM (Data Expressed in Terms of Defects per Function Point For projects nominally 1000 function points in size) Defect Removal Delivered SEI CMM Levels Potentials Efficiency Defects SEI CMMI % 1.05 SEI CMMI % 0.75 SEI CMMI % 0.48 SEI CMMI % 0.32 SEI CMMI % 0.17 SWQUAL08\23 SOFTWARE DEFECT POTENTIALS AND DEFECT REMOVAL EFFICIENCY FOR EACH LEVEL OF SEI CMM (Data Expressed in Terms of Defects per Function Point For projects 10,000 function points in size) Defect Removal Delivered SEI CMM Levels Potentials Efficiency Defects SEI CMMI % 1.63 SEI CMMI % 1.13 SEI CMMI % 0.71 SEI CMMI % 0.53 SEI CMMI % 0.29 SWQUAL08\24 12
13 DEFECTS AND SOFTWARE METHODOLGOIES (Data Expressed in Terms of Defects per Function Point For projects nominally 1000 function points in size) Defect Removal Delivered Software methods Potential Efficiency Defects Waterfall % 1.10 Iterative % 0.62 Object-Oriented % 0.54 Agile with scrum % 0.40 Rational Unified Process (RUP) % 0.26 PSP and TSP % 0.14 Model-based % % Certified reuse % 0.02 SWQUAL08\25 DEFECTS AND SOFTWARE METHODOLGOIES (Data Expressed in Terms of Defects per Function Point For projects nominally 10,000 function points in size) Defect Removal Delivered Software methods Potential Efficiency Defects Waterfall % 1.75 Iterative % 1.13 Object-Oriented % 0.86 Agile with scrum % 0.72 Rational Unified Process (RUP) % 0.55 PSP and TSP % 0.30 Model-based % % Certified reuse % 0.09 SWQUAL08\26 13
14 GLOBAL SOFTWARE QUALITY SAMPLES Data Expressed in Terms of Defects per Function Point Top countries for software quality out of 66 Defect Removal Delivered Country Potential Efficiency Defects Japan % 0.29 India % 0.34 Denmark % 0.38 Canada % 0.39 South Korea % 0.39 Switzerland % 0.40 United Kingdom % 0.40 Israel % 0.41 SWQUAL08\27 GLOBAL SOFTWARE QUALITY SAMPLES Data Expressed in Terms of Defects per Function Point Selected Countries out of 66 compared Defect Removal Delivered Country Potential Efficiency Defects United States % 0.47 France % 0.49 Germany % 0.59 Italy % 0.62 Spain % 0.66 Russia % 0.70 China % 0.70 Ukraine % 0.74 SWQUAL08\28 14
15 MAJOR SOFTWARE QUALITY ZONES Defects per FP Malpractice. U.S. Average. Best in Class 50% 55% 60% 65% 70% 75% 80% 85% 90% 95% 100% Defect Removal Efficiency SWQUAL08\29 DEFECT REMOVAL EFFICIENCY CASE 1 Inspections + static analysis + testing DEVELOPMENT DEFECTS REMOVED Static analysis 350 Inspections 390 Testing 250 Subtotal 990 USER-REPORTED DEFECTS IN FIRST 90 DAYS Valid unique defects 10 TOTAL DEFECT VOLUME Defect totals 1,000 DEFECT REMOVAL EFFICIENCY Dev. (990) / Total (1,000) = 99.0% SWQUAL08\30 15
16 DEFECT REMOVAL EXPENSES CASE 1 Inspections + static analysis + testing Static analysis $12,772 Inspections $70,773 Testing $220,889 Subtotal $304,434 Maintenance $6,629 TOTAL $310,703 (lowest cost) SWQUAL08\31 DEFECT REMOVAL EFFICIENCY CASE 2 No static analysis. Inspections + testing DEVELOPMENT DEFECTS REMOVED Static analysis 0 Inspections 560 Testing 400 Subtotal 960 USER-REPORTED DEFECTS IN FIRST 90 DAYS Valid unique defects 40 TOTAL DEFECT VOLUME Defect totals 1,000 DEFECT REMOVAL EFFICIENCY Dev. (960) / Total (1,000) = 96.0% SWQUAL08\32 16
17 DEFECT REMOVAL EXPENSES CASE 2 No static analysis. inspections + testing Static analysis $0 Inspections $91,387 Testing $230,203 Subtotal $321,590 Maintenance $13,932 TOTAL $335,522 SWQUAL08\33 DEFECT REMOVAL EFFICIENCY CASE 3 No inspections. Static analysis + testing DEVELOPMENT DEFECTS REMOVED Static analysis 500 Inspections 0 Testing 425 Subtotal 925 USER-REPORTED DEFECTS IN FIRST 90 DAYS Valid unique defects 75 TOTAL DEFECT VOLUME Defect totals 1,000 DEFECT REMOVAL EFFICIENCY Dev. (925) / Total (1,000) = 92.5% SWQUAL08\34 17
18 DEFECT REMOVAL EXPENSES CASE 3 No inspections; static analysis + testing Static analysis $12,772 Inspections $0 Testing $264,045 Subtotal $276,817 Maintenance $41,796 TOTAL $318,613 SWQUAL08\35 DEFECT REMOVAL EFFICIENCY CASE 4 No inspections; no static analysis. Testing only. DEVELOPMENT DEFECTS REMOVED Inspections 0 Static analysis 0 Testing 850 Subtotal 850 USER-REPORTED DEFECTS IN FIRST 90 DAYS Valid unique defects 150 TOTAL DEFECT VOLUME Defect totals 1,000 DEFECT REMOVAL EFFICIENCY Dev. (850) / Total (1,000) = 85.0% SWQUAL08\36 18
19 DEFECT REMOVAL EXPENSES CASE 4 Inspections + static analysis + testing Static analysis $0 Inspections $0 Testing $326,089 Subtotal $326,089 Maintenance $92,879 TOTAL $418,968 (Highest cost) SWQUAL08\37 COSTS FOR CASES 1 THROUGH 4 Removal Repairs Total Case 1 $304,434 $6,289 $310,703 Best Case 2 $321,590 $13,932 $335,522 Case 3 $276,817 $41,796 $318,613 Case 4 $326,089 $92,879 $418,698 Worst Note: Defect removal costs predicted by Software Risk Master SWQUAL08\38 19
20 REMOVAL FOR FOR CASES 1 THROUGH 4 Efficiency Removed Delivered Case % Best Case % Case % Case % Worst Note: Defect removal efficiency predicted by Software Risk Master SWQUAL08\39 INDUSTRY DATA ON DEFECT ORIGINS Because defect removal is such a major cost element, studying defect origins is a valuable undertaking. IBM Corporation (MVS) SPR Corporation (client studies) 45% Design errors 20% Requirements errors 25% Coding errors 30% Design errors 20% Bad fixes 35% Coding errors 5% Documentation errors 10% Bad fixes 5% Administrative errors 5% Documentation errors 100% 100% TRW Corporation MITRE Corporation Nippon Electric Corp. 60% Design errors 64% Design errors 60% Design errors 40% Coding errors 36% Coding errors 40% Coding errors 100% 100% 100% SWQUAL08\40 20
21 SOFTWARE QUALITY AND PRODUCTIVITY The most effective way of improving software productivity and shortening project schedules is to reduce defect levels. Defect reduction can occur through: 1. Defect prevention technologies Structured design and JAD Structured code Use of inspections, static analysis Reuse of certified components 2. Defect removal technologies Design inspections Code inspections, static analysis Formal Testing using mathematical test case design SWQUAL08\41 RANGES OF DEFECT REMOVAL EFFICIENCY Lowest Median Highest 1 Requirements review (informal) 20% 30% 50% 2 Top-level design reviews (informal) 30% 40% 60% 3 Detailed functional design inspection 30% 65% 85% 4 Detailed logic design inspection 35% 65% 75% 5 Code inspection or static analysis 35% 60% 90% 6 Unit tests 10% 25% 50% 7 New Function tests 20% 35% 65% 8 Integration tests 25% 45% 60% 9 System test 25% 50% 65% 10 External Beta tests 15% 40% 75% CUMULATIVE EFFICIENCY 75% 98% 99.99% SWQUAL08\42 21
22 NORMAL DEFECT ORIGIN/DISCOVERY GAPS Defect Origins Requirements Design Coding Documentation Testing Maintenance Defect Discovery Requirements Design Coding Documentation Testing Maintenance Zone of Chaos SWQUAL08\43 DEFECT ORIGINS/DISCOVERY WITH INSPECTIONS Defect Origins Requirements Design Coding Documentation Testing Maintenance Defect Discovery Requirements Design Coding Documentation Testing Maintenance SWQUAL08\44 22
23 DISTRIBUTION OF 1500 SOFTWARE PROJECTS BY DEFECT REMOVAL EFFICIENCY LEVEL Defect Removal Efficiency Level (Percent) Number of Projects Percent of Projects > % % % % % < % Total 1, % SWQUAL08\45 CONCLUSIONS ON SOFTWARE QUALITY No single quality method is adequate by itself. Formal inspections, static analysis, models are effective Inspections + static analysis + testing > 97% efficient. Defect prevention + removal best overall QFD, models, inspections, & six-sigma prevent defects Higher CMMI levels, TSP, RUP, Agile, XP are effective Quality excellence has ROI > $15 for each $1 spent High quality benefits schedules, productivity, users SWQUAL08\46 23
24 REFERENCES ON SOFTWARE QUALITY Black, Rex; Managing the Testing Process; Microsoft Press, Crosby, Phiip B.; Quality is Free; New American Library, Mentor Books, Gack Gary, Managing the Black Hole; Business Expert Publishing, 2009 Gilb, Tom & Graham, Dorothy; Software Inspections; Addison Wesley, Jones, Capers & Bonsignour, Olivier; The Economics of Software Quality; Addison Wesley, 2011 Jones, Capers; Software Engineering Best Practices; McGraw Hill, 2010 Jones, Capers; Applied Software Measurement; McGraw Hill, Jones, Capers; Estimating Software Costs, McGraw Hill, Jones, Capers; Assessments, Benchmarks, and Best Practices, Addison Wesley, SWQUAL08\47 REFERENCES ON SOFTWARE QUALITY Kan, Steve; Metrics and Models in Software Quality Engineering, Addison Wesley, McConnell; Steve; Code Complete 2; Microsoft Press, 2004 Pirsig, Robert; Zen and the Art of Motorcycle Maintenance; Bantam; 1984 Radice, Ron; High-quality, Low-cost Software Inspections, Paradoxican Publishing, Wiegers, Karl; Peer Reviews in Software, Addison Wesley, SWQUAL08\48 24
25 REFERENCES ON SOFTWARE QUALITY (American Society for Quality) (CAST Software Inc.) (Int. Func. Pt. Users Group) (Int. Software Bench. Standards Group) (International Organization for Standards) (Infor. Tech. Metrics and Productivity Institute) (Project Management Institute) (Process Fusion) (Software Engineering Institute) (Software Productivity Research LLC) SWQUAL08\49 REFERENCES ON SOFTWARE QUALITY (Society for Software Quality) (Software Engineering Methods and Theory) (Consortium for IT software quality) Sans Institute listing of software defects European Institute for Software Qualiy www,galorath.com Galorath Associates Namcook Analytics LLC Association for Software Testing Quality Assurance Institute (QAI) SWQUAL08\50 25
SOFTWARE QUALITY IN 2002: A SURVEY OF THE STATE OF THE ART
Software Productivity Research an Artemis company SOFTWARE QUALITY IN 2002: A SURVEY OF THE STATE OF THE ART Capers Jones, Chief Scientist Emeritus Six Lincoln Knoll Lane Burlington, Massachusetts 01803
Function Points as a Universal Software Metric. Draft 10.0 July 13, 2013. Blog: http://namcookanalytics.com; Web: WWW.Namcook.com
Function Points as a Universal Software Metric Capers Jones, VP and CTO Namcook Analytics LLC Draft 10.0 July 13, 2013 Blog: http://namcookanalytics.com; Web: WWW.Namcook.com Keywords Capers Jones data,
Software Quality Metrics: Three Harmful Metrics and Two Helpful Metrics. June 6, 2012
Software Quality Metrics: Three Harmful Metrics and Two Helpful Metrics June 6, 2012 Capers Jones, VP and Chief Technology Officer Namcook Analytics LLC Abstract The cost of finding and fixing bugs or
EVALUATING SOFTWARE METRICS AND SOFTWARE MEASURMENT PRACTICES. Version 4.0 March 14, 2014. Capers Jones, VP and CTO; Namcook Analytics LLC
EVALUATING SOFTWARE METRICS AND SOFTWARE MEASURMENT PRACTICES Version 4.0 March 14, 2014 Capers Jones, VP and CTO; Namcook Analytics LLC Web: www.namcook.com Blog: http://namcookanalytics.com Email: [email protected]
Building Security into the Software Life Cycle
Building Security into the Software Life Cycle A Business Case Marco M. Morana Senior Consultant Foundstone Professional Services, a Division of McAfee Outline» Glossary» What is at risk, what we do about
Laws of Software Engineering Circa 2014. Version 7.0 February 17, 2014. Capers Jones, VP and CTO, Namcook Analytics LLC.
Laws of Software Engineering Circa 2014 Version 7.0 February 17, 2014 Capers Jones, VP and CTO, Namcook Analytics LLC. Copyright 2014 by Capers Jones. All rights reserved. Introduction Software development
Optimizing Software Development: Pattern matching, Dynamic visualization, and Reusable components to exceed 100 Function Points per Month
Optimizing Software Development: Pattern matching, Dynamic visualization, and Reusable components to exceed 100 Function Points per Month Version 2.0 April 2, 2013 Abstract Capers Jones, VP and CTO Namcook
Three Things I Wish I Learned in School
Three Things I Wish I Learned in School www.construx.com 2008 Construx Software Builders, Inc. All Rights Reserved. #1 Motion = Progress The Cost of Defects 50 100X Phase in which a Defect Is Introduced
Praise for The Economics of Software Quality
Praise for The Economics of Software Quality This book provides the best treatment on the subject of economics of software quality that I ve seen. Peppered with valuable industry data, in-depth analysis,
A SHORT HISTORY OF SOFTWARE ESTIMATION TOOLS. Version 12.0 August 26, 2013
A SHORT HISTORY OF SOFTWARE ESTIMATION TOOLS Version 12.0 August 26, 2013 Keywords Activity-based costs, Capers Jones data, function points, Namcook Analytics data, software costs, software development,
the state of the practice Variations in Software Development Practices
focus the state of the practice invited article Variations in Software Development Practices Capers Jones, Software Productivity Research My colleagues and I at Software Productivity Research gathered
Software Project Management Practices: Failure Versus Success
This article is derived from analysis of about 250 large software projects at or above 10,000 function points in size that were examined by the author s company between 1995 and 2004. (Note that 10,000
LUXOFT ADVANTAGES. International Quality Standards
CMMI LUXOFT ADVANTAGES International Quality Standards CMMI CIS s first SEI CMM/CMMI level 5 assessment in 2003, Europe s first SEI CMMI v1.2 Level 5 assessment in 2007 ISO annual confirmation of ISO 9001:2008
SOFTWARE ESTIMATING RULES OF THUMB. Version 1 - April 6, 1997 Version 2 June 13, 2003 Version 3 March 20, 2007
SOFTWARE ESTIMATING RULES OF THUMB Version 1 - April 6, 1997 Version 2 June 13, 2003 Version 3 March 20, 2007 Abstract Accurate software estimating is too difficult for simple rules of thumb. Yet in spite
Enterprise Services for Defense Transformation
Enterprise Services for Defense Transformation Prof. Paul A. Strassmann George Mason University, February 19, 2007 1 Case Study Hewlett-Packard Cost Reduction 2 Example of Application Simplification Domain
Software Test Costs and Return on
Software Test Costs and Return on Investment (ROI) Issues Bob Hunt, Galorath Tony Abolfotouh, John Carpenter; Robbins Gioia March 2014 1 Introduction The recent Affordable Health Care Web Site issues have
Challenges in adopting Agile
ImproValue Consulting in adopting Copyright: ImproValue 2011 www.improvalue.com About Us ImproValue Consulting specialize in business process consulting focus on IT and ITES organizations. provide a wide
Personal Software Process (PSP)
Personal Software Process (PSP) Application of CMM principles to individuals Developed by Watts Humphrey of the Software Engineering Institute (SEI) in the early 1990s Extensive supporting materials: books,
Measuring Software Process Efficiency. By Gary Gack, Process-Fusion.net
Measuring Software Process Efficiency By Gary Gack, Process-Fusion.net This article is the second in a series of three. The first article, Measuring Software Process Effectiveness describes use of the
Certified Software Quality Assurance Professional VS-1085
Certified Software Quality Assurance Professional VS-1085 Certified Software Quality Assurance Professional Certified Software Quality Assurance Professional Certification Code VS-1085 Vskills certification
What do you think? Definitions of Quality
What do you think? What is your definition of Quality? Would you recognise good quality bad quality Does quality simple apply to a products or does it apply to services as well? Does any company epitomise
Software Code Quality Checking (SCQC) No Clearance for This Secret: Information Assurance is MORE Than Security
Software Code Quality Checking (SCQC) No Clearance for This Secret: Information Assurance is MORE Than Security Nominee International Security Executives (ISE ) Information Security Project of the Year
Abstract. Heavy vs Light Methodologies: Bulimic or Anorexic? Fernando Brito e Abreu FCT/UNL
Heavy vs Light Methodologies: Bulimic or Anorexic? Fernando Brito e Abreu FCT/UNL ISCTE, 15 April 2005 Abstract 2 From anorexic to bulimic Overview of heavy-weight methodologies Origins of light-weight
Testing in Agile methodologies easier or more difficult?
Testing in Agile methodologies easier or more difficult? Lucjan Stapp Warsaw University of Technology Stowarzyszenie Jakości Systemów Informatycznych [email protected] [email protected] Professor in
Future of CMM and Quality Improvement. Roy Ko Hong Kong Productivity Council
Future of CMM and Quality Improvement Roy Ko Hong Kong Productivity Council 1 Agenda Future Development of CMMI CMMI and Small Organizations CMMI and Agile Development Good Enough Quality CMMI and Other
CS 1632 SOFTWARE QUALITY ASSURANCE. 2 Marks. Sample Questions and Answers
CS 1632 SOFTWARE QUALITY ASSURANCE 2 Marks Sample Questions and Answers 1. Define quality. Quality is the degree of goodness of a product or service or perceived by the customer. Quality concept is the
Benchmarking Software Quality With Applied Cost of Quality
Benchmarking Software Quality With Applied Cost of Quality Cost of Quality has remained theoretical in many treatments despite its powerful relevance in software quality. A survey-based approach makes
Software Development Life Cycle (SDLC)
Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process
Software Development s Low Hanging Fruit. www.construx.com
Software Development s Low Hanging Fruit www.construx.com Copyright Notice These class materials are 2007-2008 Construx Software Builders, Inc. All Rights Reserved. No part of the contents of this seminar
Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.
INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing
Software Quality and Assurance in Waterfall model and XP - A Comparative Study
Software Quality and Assurance in Waterfall model and XP - A Comparative Study Dr. Sana a Jawdat Khalaf [email protected] Dr. Mohamed Noor Al-Jedaiah [email protected] Abstract: -Dealing with
Integrating Security into the Application Development Process. Jerod Brennen, CISSP CTO & Principal Security Consultant, Jacadis
Integrating Security into the Application Development Process Jerod Brennen, CISSP CTO & Principal Security Consultant, Jacadis Agenda Seek First to Understand Source Code Security AppSec and SQA Analyzing
Software Project Management Matrics. Complied by Heng Sovannarith [email protected]
Software Project Management Matrics Complied by Heng Sovannarith [email protected] Introduction Hardware is declining while software is increasing. Software Crisis: Schedule and cost estimates
Body of Knowledge General Knowledge (16 questions) Quality principles Benefits of software quality Organizational and process benchmarking
Body of Knowledge The following is an outline of topics that constitute the Body of Knowledge for Software Quality Engineer. This new BOK started with the exams on December 6, 2008. The topics in this
Software Process and Models
Agenda Software Process Models Plan-driven Process Models Software Process and Models A software process model simplified, abstracted description of a software development process. A model is good for
Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects
Transdyne Corporation CMMI Implementations in Small & Medium Organizations Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Dana Roberson Quality Software Engineer NNSA Service
Management. Project. Software. Ashfaque Ahmed. A Process-Driven Approach. CRC Press. Taylor Si Francis Group Boca Raton London New York
Software Project Management A Process-Driven Approach Ashfaque Ahmed CRC Press Taylor Si Francis Group Boca Raton London New York CRC Press is an imprint of the Taylor St Francis Croup, an Informa business
How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY
How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve
Certified Software Quality Engineer (CSQE) Body of Knowledge
Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions
I. General Knowledge, Conduct, and Ethics (16 Questions)
Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions
Sustainable Software Development in Agile and CMMI: Apply Lessons Learned today
Sustainable Software Development in Agile and CMMI: Apply Lessons Learned today 2009 What is the CMMI Level 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed 1 Initial Focus Continuous Process
CHAPTER. Software Process Models
CHAPTER Software Process Models 4 Chapter Objectives Introduce the generic concept of software engineering process models. Discuss the three traditional process models. Waterfall Incremental Spiral Discuss
What you can find in the ISBSG Development & Enhancement Repository Release 13
What you can find in the ISBSG Development & Enhancement Repository Release 13 This document provides details of the various project data types that are included in the ISBSG project repository Release
USING DEFECT ANALYSIS FEEDBACK FOR IMPROVING QUALITY AND PRODUCTIVITY IN ITERATIVE SOFTWARE DEVELOPMENT
USING DEFECT ANALYSIS FEEDBACK FOR IMPROVING QUALITY AND PRODUCTIVITY IN ITERATIVE SOFTWARE DEVELOPMENT Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur
Certified Software Quality Engineer (CSQE) Body of Knowledge
Certified Software Quality Engineer (CSQE) Body of Knowledge The topics in this Body of Knowledge include additional detail in the form of subtext explanations and the cognitive level at which the questions
Chapter 24 - Quality Management. Lecture 1. Chapter 24 Quality management
Chapter 24 - Quality Management Lecture 1 1 Topics covered Software quality Software standards Reviews and inspections Software measurement and metrics 2 Software quality management Concerned with ensuring
An Introduction to. Metrics. used during. Software Development
An Introduction to Metrics used during Software Development Life Cycle www.softwaretestinggenius.com Page 1 of 10 Define the Metric Objectives You can t control what you can t measure. This is a quote
UNIT-II Part-A Questions
UNIT-I 1. What is quality? 2. Define software quality? 3. What are the views of quality? 4. Give the definitions of quality? 5. What is quality as per ISO? 6. What are the reasons for software becomes
TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
A Capability Maturity Model (CMM)
Software Development Life Cycle (SDLC) and Development Methods There are some enterprises in which a careful disorderliness is the true method. Herman Melville Capability Maturity Model (CMM) A Capability
Software Engineering: Analysis and Design - CSE3308
CSE3308/DMS/2004/25 Monash University - School of Computer Science and Software Engineering Software Engineering: Analysis and Design - CSE3308 Software Quality CSE3308 - Software Engineering: Analysis
Software Engineering Introduction & Background. Complaints. General Problems. Department of Computer Science Kent State University
Software Engineering Introduction & Background Department of Computer Science Kent State University Complaints Software production is often done by amateurs Software development is done by tinkering or
Software Development Life Cycle Models - Process Models. Week 2, Session 1
Software Development Life Cycle Models - Process Models Week 2, Session 1 PROCESS MODELS Many life cycle models have been proposed } Traditional Models (plan-driven) } Classical waterfall model } Iterative
SOFTWARE PROCESS IMPROVEMENT AT SYSGENIC
STUDIA UNIV. BABEŞ BOLYAI, INFORMATICA, Volume LIII, Number 1, 2008 SOFTWARE PROCESS IMPROVEMENT AT SYSGENIC DUMITRU RĂDOIU AND MILITON FRENŢIU Abstract. The Capability Maturity Model (CMM) was defined
CALCULATING THE COSTS OF MANUAL REWRITES
CALCULATING THE COSTS OF MANUAL REWRITES Know before you go. 2 You ve got an old legacy application and you re faced with the dilemma.. Should I rewrite from scratch? Should I keep trying to maintain it?
Driving Quality Improvement and Reducing Technical Debt with the Definition of Done
Driving Quality Improvement and Reducing Technical Debt with the Definition of Done Noopur Davis Principal, Davis Systems Pittsburgh, PA [email protected] Abstract This paper describes our experiences
Lecture 1: Introduction to Software Quality Assurance
Lecture 1: Introduction to Software Quality Assurance Software Quality Assurance (INSE 6260/4-UU) Winter 2009 Thanks to Rachida Dssouli for some slides Course Outline Software Quality Overview Software
The role of Software Metrics on Software Development Life Cycle
The Role of Software Metrics on Software Development Life Cycle 39 The role of Software Metrics on Software Development Life Cycle N. Rajasekhar Reddy 1 and R. J. Ramasree 2 1 Assistant Professor, Department
Agile Software Development Methodologies and Its Quality Assurance
Agile Software Development Methodologies and Its Quality Assurance Aslin Jenila.P.S Assistant Professor, Hindustan University, Chennai Abstract: Agility, with regard to software development, can be expressed
Introduction to Agile Software Development
Introduction to Agile Software Development Word Association Write down the first word or phrase that pops in your head when you hear: Extreme Programming (XP) Team (or Personal) Software Process (TSP/PSP)
Plan-Driven Methodologies
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
V. Phani Krishna et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (6), 2011, 2915-2919
Software Quality Assurance in CMM and XP- A Comparative Study CH.V. Phani Krishna and Dr. K.Rajasekhara Rao CSE Department, KL University, Guntur dt., India. Abstract Software Quality Assurance is a planned
Verification and Validation of Software Components and Component Based Software Systems
Chapter 5 29 Verification and Validation of Software Components and Component Based Christina Wallin Industrial Information Technology Software Engineering Processes ABB Corporate Research [email protected]
Software Process Improvement. Overview
Software Process Improvement Overview Marcello Visconti Departamento de Informática Universidad Técnica Federico Santa María Valparaíso, Chile Motivation Immaturity of software engineering - state of the
Software Development Process
Software Development Process A software development process, also known as software development lifecycle, is a structure imposed on the development of a software product. Similar terms include software
The Compelling Case For CMMI-SVC: CMMI-SVC, ITIL & ISO20000 demystified
The Compelling Case For CMMI-SVC: CMMI-SVC, ITIL & ISO20000 demystified T: 01748 821824 E: [email protected] Agenda What is CMMI-SVC? How Does CMMI-SVC Relate to Existing Models? CMMI-SVC and ISO 20000
The «SQALE» Analysis Model An analysis model compliant with the representation condition for assessing the Quality of Software Source Code
The «SQALE» Analysis Model An analysis model compliant with the representation condition for assessing the Quality of Software Source Code Jean-Louis Letouzey DNV IT Global Services Arcueil, France [email protected]
Agile-Enabled High Maturity
Agile-Enabled High Maturity SEPG NORTH AMERICA 2013 Richard Swensen Process Improvement Director Sean Cohan Technical Director CMMI Level 5 ISO 9001 ISO/IEC 20000-1 ISO/IEC 27001 Serving Our Customers
Frank Tsui. Orlando Karam. Barbara Bernal. State. University. Polytechnic. Ail of Southern JONES & BARTLETT LEARNING
Frank Tsui Orlando Karam Barbara Bernal Ail of Southern Polytechnic State JONES & BARTLETT LEARNING University Preface Hi Chapter 1 Writing a Program 1 1.1 A Simple Problem 2 1.2 Decisions, Decisions 2
Defect Management in Agile Software Development
I.J. Modern Education and Computer Science, 2014, 3, 55-60 Published Online March 2014 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijmecs.2014.03.07 Defect Management in Agile Software Development
Minimizing code defects to improve software quality and lower development costs.
Development solutions White paper October 2008 Minimizing code defects to improve software quality and lower development costs. IBM Rational Software Analyzer and IBM Rational PurifyPlus software Kari
Software Quality Development and Assurance in RUP, MSF and XP - A Comparative Study
Software Quality Development and Assurance in RUP, MSF and XP - A Comparative Study Wolfgang Zuser Vienna University of Technology [email protected] Stefan Heil Capgemini Consulting Austria
How To Understand Software Engineering
PESIT Bangalore South Campus Department of MCA SOFTWARE ENGINEERING 1. GENERAL INFORMATION Academic Year: JULY-NOV 2015 Semester(s):III Title Code Duration (hrs) SOFTWARE ENGINEERING 13MCA33 Lectures 52Hrs
Software Engineering for Software-Intensive Systems: III The Development Life Cycle
Software Engineering for Software-Intensive Systems: III The Development Life Cycle Assistant Professor Dr. Room E 3.165 Tel. 60-3321 Email: [email protected] Outline I Introduction II Foundations III The Development
Introduction to Function Points www.davidconsultinggroup.com
By Sheila P. Dennis and David Garmus, David Consulting Group IBM first introduced the Function Point (FP) metric in 1978 [1]. Function Point counting has evolved into the most flexible standard of software
Software Quality Assurance in Agile, XP, Waterfall and Spiral A Comparative Study
Software Quality Assurance in Agile, XP, Waterfall and Spiral A Comparative Study S. Vijayakumar [email protected] School of Computer and Information Science University of South Australia,
What CMMI Cannot Give You: Good Software
What CMMI Cannot Give You: Good Software Ivar Jacobson [email protected] [email protected] Objective To understand what CMM/CMMI is and what it is not To demonstrate how the unified process helps you
Outline. III The Development Life Cycle. Characteristics of Software Development Methodologies. The Prototyping Process
Software Engineering for Software-tensive Systems: Assistant Professor Dr. Room E 3.165 Tel. 60-3321 Email: [email protected] line I troduction II Foundations IV Requirements V Analysis & Design VI Implementation
Useful Automated Software Testing Metrics
Useful Automated Software Testing Metrics By Thom Garrett IDT, LLC Adapted from the book Implementing Automated Software Testing, by Elfriede Dustin, Thom Garrett, Bernie Gauf Author Bio: Thom Garrett
Web Applications Development and Software Process Improvement in Small Software Firms: a Review
Web Applications Development and Software Process Improvement in Small Software Firms: a Review Haroon Tarawneh Al-balqa Applied University [email protected] Sattam Allahawiah Al-balqa Applied University
CMMi and Application Outsourcing
White Paper CMMi and Application Outsourcing Abstract A lot of applications outsourcing providers in the market today are claiming for being assessed in different maturity levels of CMMi. But it is important
TOGAF usage in outsourcing of software development
Acta Informatica Pragensia 2(2), 2013, 68 76, DOI: 10.18267/j.aip.25 Section: Online: aip.vse.cz Peer-reviewed papers TOGAF usage in outsourcing of software development Aziz Ahmad Rais 1, Rudolf Pecinovsky
