Intro

Question 1

What are two quality definitions?

Answer 1

Conformance to requirements.
Fitness for use.

They are the same if requirements are correct!
Fitness for use is better imo, cause that is the real measurement of how useful the product is. But following requirements may be more secure legally.
If requirements are sensible they are easier to achieve imo.

Question 2

Deming cycle parts?

Answer 2

Plan, Do, Check, Act.

Question 3

“Quality is free but not a gift”? What means it?

Answer 3

That putting more efforts and cost into bug prevention and bug fixing will save more money in the long run.

Question 4

What are the four costs of quality?

Answer 4

Prevention: process improvement and infrastructure.
Appraisal: Finding defects (review, testing).
Internal failure: fixing defects discovered prior to delivery).
External failure: responding to problems discovered after release.

Question 5

What is Brook’s law?

Answer 5

That adding people to a late software project makes it later.
Reasons:
1. takes time for people to get productive. Time from people already working on the project.
2. Communications overhead.
3. Limited divisibility of tasks.

Question 6

Explain the bathtub curve of costs vs quality.

Is it bathtub for non-critical or critical software?

Answer 6

Bathtub curve shows improving quality up to a sweet spot pays off, up to a point where further efforts cause costs to increase again.
That is for non-critical systems.
For critical systems the curve is more like a line high up for a while and moves down at a very high quality.

Question 7

“No quality management without quantifiable and measurable requirements”… Good and bad quality measurements for software?
“Still things that cannot be measured and still must be managed”… Examples?

Answer 7

???

Question 8

What are the three pillars of SQM?

For each pillar describe concrete examples of what might influence quality and associated costs.

Answer 8

(mynd glæra 1-43)
Organizational Activities (organize control):
- Infrastructure.
- Management.
- configuration and defect management.
- (CMMI and SPICE)
- process models and process improvement 
  models...???
Constructive Activities (avoid errors):
- Training.
- Best Practices.
- Languages.
- requirements engineering, modelling, high-level 
  programming languages, training tools.
Analytical Activities (detect errors):
- Testing.
- Metrics.
- Reviews.
- dynamic software testing, software metrics, manual reviews and static code analysis.

Question 9

What is:
Failure?
Fault?
Error?

Does every fault lead to a failure?

Answer 9

Failure: problem encountered in execution.
Fault: the cause of a failure.
Error: the cause of a fault. - human coding error.

Not every fault necessarily leads to a failure. For example if the code is never executed.

Question 10

Difference between Validation and Verification?

Answer 10

Validation is checking that the result of development fulfills user requirements. (built the right system?)
Verification is checking if the input was correctly transformed into the output. (built the system right?)

Question 11

What is risk in our context?

Answer 11

severity of damage * probability of damage.
Project risk.
Product risk.