Inspection Course

1
Inspection Course

• Introduction
• Why do we inspect
• When do we inspect
• What is a good inspection process
• How do we inspect

2
Historical Roots

• Michael Fagan IBM - correction process
• Godfrey ATT
• Jones Mays IBM - prevention process
• Tom Gilb
• ANSI/IEEE Std 1029-1988

3
Reviews Inspection (RI) är de effektivaste
metoderna för kvalitetskontroll och
kvalitetssäkring!

• Chris Ebert Inspections are surely a key topic,
  and with the right instrumentation and training
  they are one of the most powerful techniques for
  defect detection.
• Terry Bollinger They work, they help foster
  broader understanding and learning, and for the
  most part they do lead to better code.
• Robert Cochran Reviews of all types are a major
  positive influence.

4
RI, the Best influence on Software Engineering!
IEEE Software Jan/Feb 2000
5
WHY
6
Informationsstruktur

• Allt hänger ihop!
• Fel sprider sig till flera dokument senare i
  kedjan
• Felen blir mycket dyrare att rätta ju senare de
  hittas!

7
Why do we inspect

• To save time money
• As quality Assurance (You can not test in
  quality It has to be built in to the system)
• To secure the releases downstream (To avoid that
  the fault is spread)
• To control the quality on the source documents
• To identify and correct defects
• To analyze causes for the defect and make
  improvements in our processes, to prevent it from
  happen again
• To spread knowledge
• To help the author

8
WHEN
9
When do we inspect

• Whenever we have written something !
• The process of writing
• 1/3, 2/3 and final reviews

10
The process of writing
1/3 Review
Inspection
2/3 Review
The process of approving
11
The purpose with 1/3, 2/3 and final reviews
Final Review or Inspection
Reviews
1/3 Review
2/3 Review
Document the collected info
Collect information
Inspection
Present the idea
Right solution?
Good enough to approve?
The process of approving
12
Granskningsmetoder, Strategi
Time(Weeks)
1
2
3
4
5
6
1/3 Presentation
Frequent Review
Inspection
13
Vad är en bra process
14
Inspektion - För att säkra TTM(Leveransåtaganden)

• För att bedöma rätt kvalitet krävs följande av
  Inspektionsprocessen
• Regelverk
• Effektivitet
• Felklassning
• Nettosidor
• Optimal hastighet

15
Inspektion - Regelverk

• Skrivna regler som beskriver hur dokumentet på
  bästa sätt ska skrivas

16
Inspektion - Effektivitet

• Dokumentroller
• Checklistor
• Processroller
• Inspektionsledare (Inspection Leader)
• Inspektör (Checker)
• Författare (Author)
• Sekreterare (Scribe)

17
Inspektion - Felklassning

• Ekonomisk bedömning
• Super Major
• Majors
• minors

18
Inspektion - Nettosidor

• Är en normaliserad sida
• Gör det möjligt att jämföra information oavsett
  hur den är representerad
• Planering av Inspektionen baseras på antalet
  Nettosidor

19
What is one page ?
20
How do we inspect

• The inspection process
• Process Brainstorm
• Roles, details
• The documents
• Rules - Standards
• Checklists
• Classification

21
(No Transcript)
22
Net Page or Logical page

• 300 Non-commentary words 1 Net Page

23
Inspection Rate

• How fast can a document be inspected ?
• How do you prevent people from going to fast ?

24
Optimal Rate
Source UM/EPL Inspection database. Inspections
1996-01-01 to 1999-12-30.
25
Estimated remaining Majors (ErM)

• The number of remaining Majors per net page. This
  can be calculated by the total estimated number
  of Majors (before Inspection)' minus Majors
  found and corrected' plus Majors that has been
  incorrectly fixed'.
• The following assumptions are made A mature
  organisation finds approximately 50 of the
  faults and during the correction 17 new faults
  are introduced (Gilb, Graham, 1996, Software
  Inspection).
• ErM Majors found 1,17.

26
References

• Literature
• Gilb, Tom Graham, Dorothy Software Inspection,
  Addison-Wesley, 1996. ISBN 0-201-63181-4.
• Fenton Pfleeger Software Metrics - A Rigorous
  Practical Approach, PWS, 1997, ISBN 053495425-1
• Wiegers, Karl E. Creating a software engineering
  culture, 1996, ISBN 0-932633-33-1
• McConnell , Steve The Best Influences on
  Software Engineering, IEEE SOFTWARE January /
  February 2000
• Links
• http//www.Result-Planning.com/Pages/2ndLevel/gilb
  download.html
• http//www.Result-Planning.com/Download/InspLea4.p
  df