presentation quality management

Quality ManagementDaniel Vermaasen, Max Zuchowski

03

/31

/10

Quality design

Quality control

Software measuring/ metrics

Quality assurance/-standards

Process-/Product quality

Quality Management

Introduction

Quality design

Quality control




Quality Management

Introduction

maintainability

securityefficiency

prototype

Quality design

Quality control




Quality Management

Introduction

• Build a Quality Culture• Manage Quality Documents• Seperate Quality Assurance

Quality design

Quality control



Quality Management

Process-/Product quality Process-/Product quality

Quality design

Quality control



Quality Management

Process-/Product quality Concrete

Standardize

Quality design

Quality control




Quality Management

Quality assurance/

Standards

Document standards

Programming language standards

Modeling standards

Quality design

Quality control




Quality Management

What Is It Good For?

Prevent often happen mistakes

Measurable

Quality design

Quality control




Quality Management

How?

Incorporate with developers Check and revise regularly Provide tools

Quality control




Quality design

Quality Management

Quality designPlan!

1. Product description and quality expectations due to it

2. Product plans which include its responsible people and

all services around the product

3. Process descriptions

4. Quality goals and plans inclusive reasons for all quality

attributes

5. Risks and risk management

Quality control




Quality design

Quality Management

Consider

Comprehensibility

Quality design




Quality control

Quality Management

Why do we need quality

control?

• to ensure that the quality is what the customer expects

• to lower maintainability costs

• to lower extensibility costs

Quality design




Quality control

Quality Management

How can we control the

quality?

• set project standards at the beginning

• quality reviews

• automatic software evaluation

Quality design




Quality control

Quality Management

What is quality review?• technical analysis of product components and documentation

• quality review team of 5 people

• inspecting a part or the hole system and the documentation

• target: find differences between project standards and the system

• invite the authors of documents that are going to be reviewed

• record the results and hand it to the author/project leader

• all kind of documents can be reviewed

Quality design

Quality control




Quality Management

What is an automatic

software evaluation?• automated tests of your system

• derive a numeric value to the property of a software product

• allows you to compare your software to standards or to previous revisions

Quality design

Quality control




Quality Management

Why to use automatic

software evaluation?• to formulate common predictions:

the summary of the results can give an overview over the system attributes (system failures)

• to find abnormal components:

results that differ heavy from the expected value may be very complex or include errors

Quality design

Quality control




Quality Management

Sometimes it is impossible to measure the quality of the software therefore abstractions need to be done:

Quality design

Quality control




Quality Management

Measurement process

Quality design

Quality control




Quality Management

Product metrics• sub form of software metrics

• contains the properties of the software itself

• two groups:

• dynamic metrics

• static metrics

• relevant metrics are related to the project

Quality design

Quality control




Quality Management

Measurements analysis• problem of taking the right conclusions

• collected data can be interpreted in several directions

• when taking your conclusions, take every possible circumstance into account

• there are no universal software metrics, you must find the fitting ones yourself

thank you!