businessstrategies.pdf

Business Strategies

Primary Strategies

 Maximize customer satisfaction

 Minimize engineering effort and

schedule

 Minimize defects

The Goal/Question/Metric

Paradigm

 Developed by Victor Basili and associates at the

University of Maryland.

 Organizations have goals.

 For each goal there questions you would ask to

determine whether you are meeting your goal or

not.

 For each question there are likely metrics you

could use to help answer the question.

Template for Software Quality

Goal Definition

 Purpose: To (characterize, evaluate,

predict, monitor, etc.) the (process,

product, model, metric, etc.) in order to

(understand, plan, assess, manage,

control, engineer, learn, improve, etc.) it.

 Example: To evaluate the maintenance

process in order to improve it.

Template for Software Quality

Goal Definition (cont’d)

 Perspective: Examine the (cost,

effectiveness, correctness, defects,

changes, product measures, etc.) from

the viewpoint of the (developer,

manager, customer, etc.)

 Example: Examine the effectiveness from

the viewpoint of the customer.

Template for Software Quality

Goal Definition (cont’d)  Environment: The environment consists of

the following: process factors, people

factors, methods, tools, constraints, etc.

 Example: The maintenance staff are poorly

motivated programmers who have limited

access to tools.

Determining Metrics

Goal Questions Metrics

Evaluate How fast are fixes to

customer reported

problems made?

What is the quality of

fixes delivered?

Average effort to

fix a problem

Percentage of

incorrect fixes