+ All Categories
Home > Technology > Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Date post: 16-Apr-2017
Category:
Upload: ow2-consortium
View: 88 times
Download: 0 times
Share this document with a friend
27
Measure It ! Daniele Gagliardi @dangagliar
Transcript
Page 1: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Measure It !

Daniele Gagliardi@dangagliar

Page 2: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

28 For which of you, desiring to build a tower, does not first sit down and count the cost, whether he has enough to complete it?

Luke 14:28

Page 3: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Gilb’s Law

Anything you need to quantify can be measured in some way that is superior to not measuring it at all

Page 4: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Source: SEI CMU/SEI-2010

How would you measure it ?(concretely)

Page 5: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

GQM Approach

● Define a goal● Ask a question on how to reach that

goal● Answer with an indicator● Refine and derive the metric

Page 6: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

GOAL / BENEFIT

Question Indicator Algorithm Definition

Measuring bugs distribution within project lifecycle, within the effort to solve them

It helps on measuring test effectivenss and bus resolution effort

In which project phases bugs are originated?

In which project phases bugs are solved?

Bugs source distribution within project lifecycle

Bugs detection distributionwithin project lifecycle

BO = # bugs in project phase X/# total bugs

BS = # bugs solvedin project phase X/# total bugs

Currently Total number of bugs originated within project phase X

Currently Total number of bugs solved within project phase Y

GQM examples

Page 7: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Eng corporate framework

Page 8: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Bugs resolution ratioBugs detection ratioAverage bug resolution timeBugs resolution effectivenessBugs distribution by severityBugs distribution by project phasesBugs resolution effort distribution by people

Eng corporate metrics (sample)

Page 9: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Comments density IQ10 – Dead codeIQ11 – Essential ComplexityIQ12 – Encupsulation violationsIQ13 – Class dependencies on its subclasses IQ14 – Cyclomatic complexity IQ16 – Cohesion

Eng Customers metrics (sample)

Page 10: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

SLA definitionthe point of view of the

customer

Measures, Metrics, KPI are the building blocks

Page 11: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Nicola Bertazzo, Spago4Q Team Leader at Engineering Group

Need for an expert in measures and quality & productivity intelligence

Page 12: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

✔Infras – boosts production, sources for measures(don’t assemble an infra without Measures in mind)

✔Plan it (processes, measures, etc) - ✔Most of measures should be automated

✔Set it up✔Configure it (default configuration couldn’t serve you in the best way)✔Manage it✔Train people✔Support people✔Ask and collect feedbacks (survey, trouble ticketing) : infra evolves

with its users

The importance of an infrastructure

Page 13: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Roles of an infrastructure

Tools to produce software (sources for measures)Tools to collect measuresTools to visualize

Page 14: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Plan and Setup the infra

Luca Andreatta, Solution Architect at Engineering Group

Need for an expert in software development processes and tools

Page 15: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Measures come automatically from professionals’ work

Matteo Massarotto, Senior Developer at Engineering Group

Need for trained professionals using right tools in the best way

Page 16: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Extract data

Alessio De Rossi, ETL & DWH Specialist at Engineering Group

Need for an expert in ETL and DWH design

Page 17: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Build your dashbords

Giorgia Fineschi, BI Specialist & Spago4Q Consultant at Engineering Group

Need for an expert in Business Intelligence and quality data visualisation

Page 18: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

00 – Feasibility and Contract01 – Project Management02 – Project setup03 – Configuration04 – Environment setup05 – Requirements06 – Design07 – Implementation08 – Test09 – Release10 – UAT11 – Sstartup12 – Production13 – Peer Reviews14 – Bugs Management

- Coding error- Design error- Missing requirements- Requirement error- Management error- Estimation and planning error- User training error- Infrastructure error- Startup error- Configuration error- Inconsistent Data- Interface error- Documentation error- Contract error

Bug type

Project phase bug was detected

Project phase bug was originated

Example :Bug tracking Configuration

Page 19: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Bugs statistics

Distribution of bugs by originating project phase

Distribution of bugs by resolution project phase

Distribution of bugs resolution effort by originating prj phase

Page 20: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Impact values:– Very Low: 1– Low: 2– Moderate: 3– High: 4– Very High: 5

Cost impact

Time impact

Risk exposure = Impact x probability

Example:- Impact High (4), Probability 80%→ Exposure = 4 x 0.8 = 3.2

Red zone risks: Impact >= Moderate and Probability >= 80%

Example :Risk Management Configuration

Probability

Page 21: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Risks dashboard(thanks, Spago4Q ☺)

Page 22: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Company production(thanks again, Spago4Q ☺)

Page 23: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Usage of infra(many thanks, Spago4Q ☺)

Page 24: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Corporate infra support dashboard(many many thanks, really, Spago4Q ☺)

Page 25: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Oscar connection(work in progress... ☺)

Leveraging experiences coming from OW2 projects, individual members and company members

Page 26: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Contacts : @dangagliar

http://www.spago4q.org

Merci de votreattention!

Dankon pro via atento!

Grazie per la vostraattenzione !

Thanks forYour attention !

Page 27: Measure It! How to measure quality in (not only) large software projects, OW2con'16, Paris.

Bibliography

● Spago4Q - www.spago4q.org● "Peopleware, 2nd edition" Tom Demarco & Timothy Lister – Dorset House

Publishing, 1999● Gospel of Luke● Agile Metrics in Action - Christopher W. H. Davis – Manning Publications

- 2015● https://oscar.ow2.org/● Il Processo di Test – Gabriele Ruffatti & Sergio Oltolina, Engineering

Group● Lesson Learned in Software Testing, Cem Kaner, James Bach, Bret

Pettichord, John Wiley and Sons, 2002● Pragmatic Software Testing, Rex Black, Wiley Publishing, 2007


Recommended