Dr. Bill Curtis Director, Consortium for IT Software Quality

Standardize Software Quality and Productivity Measurement

Mayans Apocalypse Will Occur This Dec. 21

2

ALU

Memory

Register bank

Graphicscard

User interface

Network bus

Data Cache

Interrupt controller

Memory

The IT Apocalypse Has Already Started

3

Measuring Software Quality Is Imperative

4

For software measurement to become common practice, two capabilities must be achieved:

Automation

Standards

Vendors

CISQ

Vendors

Levels of Measuring Software Quality

5

Unit Level Basic coding standards Code style & layout Code documentation Cyclomatic complexity

Component Level

System Level

In-technology architecture Intra-layer dependencies Inter-program invocation Security vulnerabilities

Architectural compliance Application security Resiliency checks Transaction integrity

20x as many

fixes to correct

80% of architecturally complex defects touch an Architectural Hotspot—a badly designed component causing problems

System Level Measurement Is Critical

6

48%

52%92%

8%Architecturally

Complex Defects

Component-level violations

% of total app defects

% of total repair effort

ArchitecturallyComplex Defect

A structural flaw involving interactions among multiple components that reside in different application layers

Architectural hotspots provide a roadmap for remediating the worst risk, rework, and cost drivers

Consortium for IT Software Quality

7

CISQ

Co-sponsorship

IT Executives

Technical experts

www.it-cisq.org

CISQ Standards

8

CISQ Measures Relate to Business Value

9

Reliability

Performance

Security

Changeability

CISQ Measure

Outages

Degraded response

Breaches, Theft

Excessive effort

Operational problems

Availability

Work efficiency

Data loss

Agility

BusinessMeasure

10

IT Execs Establish Policy & Priorities

Quality Policy

Corporate purpose

Expected behavior

Training

Reporting

Audit

Quality Priorities

Customer-facing

Internal business

ReliabilityPerformance

SecurityMaintainability

ReliabilityPerformance

SecurityMaintainability

11

App Managers Set Quality Thresholds

Retail Website

Product information

Online purchase

Delivery scheduling

Reliability 3.5Performance 3.5Security 3.9Maintainability 2.5

Reliability 3.8Performance 3.9Security 2.5Maintainability 3.0

Reliability 3.5Performance 3.0Security 3.9Maintainability 2.5

12

App Teams Plan Quality Goals & Take Action

Relea

se 5

Relea

se 6

Relea

se 7

Relea

se 8

Relea

se 9

Relea

s...

Relea

s...

Relea

s...

2.5

2.7

2.9

3.1

3.3

3.5

3.7

3.9

ReliabilityPerformanceSecurityMaintainabil-ity

Score

Quality Score Target by Release

Join the CISQ Community

13