Quality Models

Learn the shapes people use to talk about software quality.

Big Picture

One small picture can make this idea easier to hold.

Bug count only

• Looks at defects only.
• Misses user needs.
• Gives a narrow view.
• Can hide tradeoffs.

Quality model

• Looks at many traits.
• Includes user needs.
• Shows tradeoffs.
• Guides better talk.

VerdictQuality is bigger than bug count.

How It Moves

Short steps make the flow easier to see.

1

Pick a model

Choose the quality traits to care about.

2

Name the traits

List what good means for this app.

3

Measure

Look for evidence for each trait.

Discuss

Talk about tradeoffs with the team.

Step By Step

This is the same idea, stretched across time.

1. 1

   Need appears

   The team asks what good means.

2. 2

   Model chosen

   The team picks traits to track.

3. 3

   Evidence found

   The team checks the app against the traits.

4. 4

   Decision made

   The team improves the product or the plan.

One Small Model

Think of this like a tiny card you can keep in your pocket.

Quality model card

5 fields

Reliability:"Works as expected"

Usability:"Easy to use"

Performance:"Fast enough"

Security:"Hard to break"

Maintainability:"Easy to change"

Quick Check

Question 1 of 10 correct

What does a quality model help you do?

Pick one test caseDescribe good in a clear waySkip testingFix all bugs

HintSubmit

Map It

One more picture helps you see where this lesson matters most.

Traits vs evidence

Evidence

Strong

Only bug count

Very narrow view

Full model with data

Many traits and real evidence

Long list with no proof

Many words, little signal

Simple but measured

A few traits with solid checks

Weak

Few traitsMany traits

Model size

Final Quiz

Question 1 of 30 correct

What is true about quality?

It is only about bugsIt can include many traitsIt does not matter to usersIt is the same for every app

HintSubmit