Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 3 : FAGAN'S INSPECTIONS - Coggle Diagram
CHAPTER 3 : FAGAN'S INSPECTIONS
Fagan's Inspection
Definition
A highly structured,
clearly defined process by which software documents are reviewed
in detail by a team including the author and, ideally, the customer.
Goal
To
identify defects as closely as possible
to the point of occurrence in order to facilitate corrective action.
Objective of Inspection
To find every deviation from the exit criteria
Exit criteria are the work requirements of the process that the work product must meet
Each deviation from requirements is a defect
Purpose of Inspection
Measure product quality (Exit Criteria)
Determine whether a process has been completed
Reduce the schedule impact of defect rework on subsequent life cycle processes
Give real measurements against project management check points
Reduce total defect rework to a minimum
Find defects immediately after they are caused
Provide early data for improvement of the software process
Provide the software author with the quickest feedback on defects, how to recognize and avoid them in the future
What is a defect
Can exist in the accuracy/completeness of requirements, standards, and associated interface/reference documents
Identified by team consensus during inspection meeting based on requirements/standards
An instance of non-conformance with the initiating requirements, standards, or exit criteria
Defect Categories
Class
Wrong
: Information that is specified in the requirements or standards and is present in the document, but the information is incorrect
Extra
: Information that is not specified in the requirements or standards but is present in the document
Missing
: Information that is specified in the requirements or standard, but is not present in the document
Type
Describes what kind of areas the inspection document has defects in (often an “-illity”; e.g. grammar, syntax)
Inspection teams should define and tailor the classes to the work product
Severity
Major
Information that would lead to an incorrect response or misinterpretation of the information by the user
An instance of non-conformance that would lead to a discrepancy report if implemented as is
A Condition that causes an operational failure, malfunction, or prevents attainment of an expected or specified result
Minor
Information that is undesirable but would not cause a malfunction or unexpected results (bad workmanship)
Information that, if left uncorrected, may decrease maintainability
A violation of standards, guidelines, or rules, but would not lead to a discrepancy report
Inspection Team Roles
Author
: Originates/reworks the document
Reader (also an analyst, designer ,coder)
: Paraphrases/interprets the document
Moderator
: Leads the inspection team
Tester
: Consider testability, traceability, requirement, standards and external interactions
The Seven Step Inspection Process
Inspection
Identify, classify and record defects
No solutions or improvements
Preparation
Prepare to fulfill role
Completely understand document from role's perspective
Inspection Analysis
Identify defect causes
Recommend process improvements
Review/analyze inspection steps 1 - 5 for improvement
Rework
Correct ALL defects
Overview
Educate inspection team. Provide work product background, context, rationale, etc
Follow-up
Ensure all defects identified are corrected
Ensure no new defects are introduced
Planning
Assign Inspector roles
Schedule meeting time/place for steps 2, 4 & 5
Materials meet inspection entry criteria
Inspection Team
Author
Provides inspection team with overview of work product
Actively participates in Inspection Meeting
Confirms reader and tester understanding
Has vested interest in ensuring that all defects are found
Originator of work product being inspected
Reader
Obtains complete understanding of the document
Determines the path to be followed through the document
Recipient of work product being inspected
Paraphrases and interprets the document
Moderator
Stimulates participation of all team members
Consensus driver (defect, and where, or ...)
Is technically competent - Could have developed work product being inspected
Manages the inspection meeting
Ensures that team follows inspection process
Tester
Ensures that document complies with requirements and standards
Describes test approaches
Considers testability
Addresses all external interactions - control and data
Completely understand the inspection document
Seven Step Inspection Process
Inspection
Roles
Involved: Inspection Team
Responsibilities:
Moderator records inspection start time
Moderator ensures adequacy of preparation time
If inadequate preparation by team, moderator cancels and reschedules inspection meeting
Moderator records team members preparation times
Objective
Identify, classify, and record document defects
Analysis
Was team synergy adequate?
What would you do to improve your next inspection?
Planning
Overview
Preparation
Inspection
Inspection Analysis
Were preparation and inspection rates within limits of recommended rates?
Preparation
Roles Involved
: Entire Inspection Team
Responsibilities
:
:
Team members become completely familiar with requirements, standards, exit criteria, and other relevant documentation
Team members individually review, study, and understand document
Note possible defects on the document and prepare for discussion at the inspection meeting (prepare to fulfill role)
Objective
: Enable effective participation in inspection meeting
Overview
Roles Involved
: Inspection Team
Objective
Obtain shared understanding, enable efficient preparation
Responsibilities:
Author gives presentation, briefing team on document background, purpose, design rationale, etc. (i.e. a fast walkthrough)
Inspection team should understand their role and ask questions from the role's perspective to clarify and enhance understanding of the document
Moderator chairs the meeting and assigns roles
Moderator distributes inspection materials and records overview hours
Rework
Objective
: Remove defects
Role Involved
: Author
Responsibilities:
Author utilizes the defect list and any notes he recorded during the meeting
Author corrects ALL defects documented in the inspection meeting
Author determines if scope of rework increased sufficiently to justify reinspection
Author records actual rework time
Planning
Objective
Ensure document meets inspection entry criteria :
Roles Involved:
Author, Moderator
Responsibilities
:
Depending on the size of the document, the moderator may need to schedule several inspection meetings (chunking)
Author and moderator select inspection team and determine roles
Moderator ensures that document meets the inspection entry criteria and that all supporting documentation is available
Moderator schedules overview and inspection meetings and sends out meeting notices
Follow-up
Roles Involved:
Author/Moderator
Responsibilities
::
Moderator reviews corrected defects with author, ensures all defects identified are corrected, conform to standards, meet exit criteria and product requirements
Moderator ensures that no new defects were introduced as the result of the rework
Moderator determines if scope of rework increased sufficiently to justify reinspection
Moderator signs off on reworked document
Moderator publishes inspection summary report
Objective
: Verify defect removal; Ensure no new defects introduced