0% found this document useful (0 votes)
8 views3 pages

Overview of Software Inspection Process

Software inspection is a process of reviewing software documents by a team. The process includes preparation, inspection meeting, and follow-up. The key roles are the author, moderator, reader, and inspectors. The goal is to identify defects to improve software quality.

Translated by

ScribdTranslations
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views3 pages

Overview of Software Inspection Process

Software inspection is a process of reviewing software documents by a team. The process includes preparation, inspection meeting, and follow-up. The key roles are the author, moderator, reader, and inspectors. The goal is to identify defects to improve software quality.

Translated by

ScribdTranslations
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Software inspection

Inspection in theSoftware EngineeringIt relates to meetings and repetitive work can be reiterated.
thePeer reviewof any work product
by trained individuals who seek defects through
a well-defined process. Software inspection is Planning: The inspection is planned for the mo-
gerund.
also known asFagan inspectionin tribute
to Michael Fagan, the creator of this popular method of
software inspection. •General meeting: The author describes the background
product test.

Preparation: Each inspector examines the product


1 Introduction to identify possible defects.

An inspection is one of the most common practices of Inspection Meeting: During this meeting, the
review that is found in software projects. reader reads part by part of the product and inspects
The goal of the inspection is, for all inspectors- stores mark the defects of each part.
to reach a consensus on a work product and
approve it for use in the project. Commonly the •Repetition of the work: The author makes changes in
inspected work products include the analysis the product according to the action plans of the
ofsoftware requirements specificationsytest plan inspection meeting.
basDuring an inspection, a work product is selected
a review and a team meets to organize Follow-up: The author's changes are reviewed
a work product inspection. A moderator is to ensure that everything is correct.
chosen to moderate the meeting. Each inspector prepares
for the meeting inspecting the product of the work
and taking note of each defect. 'The objective of the inspection- The process is finalized by the moderator when satisfied
The goal is to identify defects. In an inspection, a defect There are some predefined exit criteria.
from any part of the work product will be maintained
until the inspector of its approval. By
for example, if the team is inspecting a specific 3 Roles of the process
software requirements specification, each defect will be the text
of the document in which an inspector disagrees
with him. During an inspection, the following roles are utilized-
satisfy.

2 The process Author: The person who created the product that is...
pick it.
The inspection process was developed by Michael.
Fagan in the mid-1970s and subsequently has been am- Moderator: This is the leader of the inspection. The mo-
The supervisor plans the inspection and coordinates it.
folded and modified.
same.
The process must have admission criteria that determine
if the inspection process is ready to start. This Reader: The person who reads through the docu-
prevent unfinished work products from entering mentos, one element at a time. The inspectors then
the inspection process. The entry criteria could point out the defects.
being achecklistincluding items such
The document has been spell-checked.
•Documenter: The person who documents the de-
The stages in the inspection process are: defects found during the inspection.
Planning Meeting, General information, prepa-
ration, inspection meeting, repetition of the work and Inspector: The person who examines the product
tracking. Stages of preparation, the inspection of to identify possible defects.

1
2 6 EXTERNAL LINKS

4 Related types of inspection • Comparison of different inspection and review techniques


niques
4.1 Code Review

Acode reviewit can be done as a special type of


inspection in which the team examines a sample of
code and correct any defects in it. In a review
a defect is acode blockdo not apply
car adequately its requirements, which does not work as
should, or that is not incorrect but could be improved
(for example, it could be made more readable or the performance-
lie can be improved). In addition to helping the team-
after finding and correcting errors, code reviews
they are useful for cross-training and to help
to junior developers learning new techniques of
programming.

4.2 Peer Review

peer reviewsit is considered in the industry one of the


best practices for software defect detection
early ware and the learning of soft artifacts
Peer Reviews consist ofsoftware tutorial,
and software inspections are an integral part of the
software engineering activities of the product. A
collection of coordinated knowledge, the skills and
behaviors facilitate the practice in the best possible way
peer reviews. The elements of the reviews
by pairs include the structured review process, the
level of excellence product control checklists, the
defined functions of the participants, and the forms
and reports.
Software inspections are the most rigorous form.
from peer reviews and should be maximized
I use these elements to detect defects. Results of
the measurements reveal that peer reviews pro-
they lead to an attractive return on the investment obtained through
through accelerated learning and defect detection
early.

5 See also

• Portal:Software TestingRelated content


withSoftware Testing.

• Software engineering

• List of software engineering topics

6 External links
• Review and inspection practices

ArticleSoftware Inspectionsby Ron Radice


3

7 Origin of the text and the images, collaborators and licenses


7.1 Text
Software Inspection Source:Unable to access external [Link]:Ger-
manX, CEM-bot, Laura Fiorucci, Alvarogili, Waeswaes, EmausBot, ZéroBot, Grillitus, KLBot2, Beatrizaix and Anónimos: 1

7.2 Images
File:Commons-emblem-question_book_orange.svg Source: Invalid input, please provide text for translation.
Commons emblem question book [Link]: CC BY-SA 3.0 Contributors: <a href='//[Link]/wiki/File:
[Link]' class='image'><img alt='[Link]' src='[Link]
commons/thumb/b/bc/[Link]/[Link]' width='25' height='25' srcset='https:
//[Link]/wikipedia/commons/thumb/b/bc/[Link]/[Link] 1.5x
[Link] 2x
data-file-width='48' data-file-height='48' /></a> + <a href='//[Link]/wiki/File:Question_book.svg' class='image'><img
alt='Question [Link] src='[Link]
[Link]' width='25' height='20' srcset='[Link]
38px-Question_book.[Link] 1.5x, [Link]
Original artist:GNOME icon artists, Jorge 2701
File:[Link]:Unable to translate image links. Please provide text for [Link]: CC BY 2.5 Contributors:
•[Link]
Original artist: [Link]:Pepetps

7.3 Content License


• Creative Commons Attribution-Share Alike 3.0

You might also like