1 / 13

Standardize Software Quality and Productivity Measurement

Standardize Software Quality and Productivity Measurement. Dr. Bill Curtis Director, Consortium for IT Software Quality. Mayans  Apocalypse Will Occur This Dec. 21. Interrupt controller. User interface. Network bus. Graphics card. ALU. Data Cache. Memory. Memory.

perdy
Download Presentation

Standardize Software Quality and Productivity Measurement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standardize Software Quality and Productivity Measurement Dr. Bill Curtis Director, Consortium for IT Software Quality

  2. Mayans  Apocalypse Will Occur This Dec. 21 Interrupt controller User interface Network bus Graphics card ALU Data Cache Memory Memory Register bank 2

  3. The IT Apocalypse Has Already Started 3

  4. Measuring Software Quality Is Imperative For software measurement to become common practice,two capabilities must be achieved: Automation Vendors Vendors Standards CISQ 4

  5. Levels of Measuring Software Quality Unit Level • Basic coding standards • Code style & layout • Code documentation • Cyclomatic complexity Component Level • In-technology architecture • Intra-layer dependencies • Inter-program invocation • Security vulnerabilities System Level • Architectural compliance • Application security • Resiliency checks • Transaction integrity 5

  6. System Level Measurement Is Critical Architecturally Complex Defect A structural flaw involving interactions among multiple components that reside in different application layers % of total repair effort % of total app defects Component-level violations 92% 48% 20x as many fixes to correct Architecturally Complex Defects 52% Architectural hotspots provide a roadmap for remediating the worst risk, rework, and cost drivers 80% of architecturally complex defects touch an Architectural Hotspot—a badly designed component causing problems 8% 6

  7. Consortium for IT Software Quality Co-sponsorship CISQ Technical experts IT Executives www.it-cisq.org 7

  8. CISQ Standards 8

  9. CISQ Measures Relate to Business Value Business Measure Operational problems CISQ Measure Availability Reliability Outages Work efficiency Performance Degraded response Data loss Security Breaches, Theft Agility Changeability Excessive effort 9

  10. IT Execs  Establish Policy & Priorities Quality Policy Corporate purpose Training Expected behavior Reporting Audit Reliability Performance Security Maintainability Quality Priorities Customer-facing Internal business Reliability Performance Security Maintainability 10

  11. App Managers  Set Quality Thresholds Reliability 3.8 Performance 3.9 Security 2.5 Maintainability 3.0 Product information Retail Website Reliability 3.5 Performance 3.5 Security 3.9 Maintainability 2.5 Online purchase Reliability 3.5 Performance 3.0 Security 3.9 Maintainability 2.5 Delivery scheduling 11

  12. App Teams Plan Quality Goals & Take Action Quality Score Target by Release Score 12

  13. Join the CISQ Community 13

More Related