Scribd
Upload
6 views

Lecture 2 For Computer Science engineering students

CSE class NOTES

Uploaded by

dhruvtiwari360
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views

Lecture 2 For Computer Science engineering students

CSE class NOTES

Uploaded by

dhruvtiwari360
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 20

University Institute of Engineering

DEPARTMENT OF COMPUTER SCIENCE


& ENGINEERING
Bachelor of Engineering (Computer Science & Engineering)
Subject Name: Software Engineering
Subject Code: 22CST-313
Prepared by:
Er. Puneet Kaur(E6913)

Quality Management DISCOVER . LEARN . EMPOWER


1
Chapter-8
Quality Management
• Software Review

• Formal technical Review

2
Software Review
• Software Review is systematic inspection of a software by one or
more individuals who work together to find and resolve errors and
defects in the software during the early stages of Software
Development Life Cycle (SDLC).
• Software review is an essential part of Software Development Life
Cycle (SDLC) that helps software engineers in validating the quality,
functionality and other vital features and components of the
software.

3
Software Review
• It is a whole process that includes testing the software product and it
makes sure that it meets the requirements stated by the client.
• Usually performed manually, software review is used to verify various
documents like requirements, system designs, codes, test plans and
test cases.

4
Objectives of Software Review
• The objective of software review is:
• To improve the productivity of the development team.
• To make the testing process time and cost effective.
• To make the final software with fewer defects.
• To eliminate the inadequacies.

5
Process of Software Review

6
Types of Software Reviews

There are mainly 3 types of software reviews:


• Software Peer Review:
Peer review is the process of assessing the technical content and
quality of the product and it is usually conducted by the author of the
work product along with some other developers.
Peer review is performed in order to examine or resolve the defects in
the software, whose quality is also checked by other members of the
team.

7
Types of Software Reviews
• Peer Review has following types:
(i) Code Review:
Computer source code is examined in a systematic way.
(ii) Pair Programming:
It is a code review where two developers develop code together at the same platform.
(iii) Walkthrough:
Members of the development team is guided bu author and other interested parties
and the participants ask questions and make comments about defects.
(iv) Technical Review:
A team of highly qualified individuals examines the software product for its client’s use
and identifies technical defects from specifications and standards.
(v) Inspection:
In inspection the reviewers follow a well-defined process to find defects.
8
Types of Software Reviews
• Software Management Review:
Software Management Review evaluates the work status. In this
section decisions regarding downstream activities are taken.
• Software Audit Review:
Software Audit Review is a type of external review in which one or
more critics, who are not a part of the development team, organize
an independent inspection of the software product and its processes
to assess their compliance with stated specifications and standards.
This is done by managerial level people.

9
Advantages of Software Review
• Defects can be identified earlier stage of development (especially in
formal review).
• Earlier inspection also reduces the maintenance cost of software.
• It can be used to train technical authors.
• It can be used to remove process inadequacies that encourage
defects.

10
Formal Technical Review

• Formal Technical Review (FTR) is a software quality control activity performed by


software engineers.
• Objectives of formal technical review (FTR):
Some of these are:
• Useful to uncover error in logic, function and implementation for any
representation of the software.
• The purpose of FTR is to verify that the software meets specified requirements.
• To ensure that software is represented according to predefined standards.
• It helps to review the uniformity in software that is development in a uniform
manner.
• To makes the project more manageable.
11
Formal Technical Review

• In addition, the purpose of FTR is to enable junior engineer to


observer the analysis, design, coding and testing approach more
closely.
• FTR also works to promote back up and continuity become familiar
with parts of software they might not have seen otherwise.
• Actually, FTR is a class of reviews that include walkthroughs,
inspections, round robin reviews and other small group technical
assessments of software.
• Each FTR is conducted as meeting and is considered successfully only
if it is properly planned, controlled and attended.
12
Formal Technical Review

• The review meeting:

Each review meeting should be held considering the following constraints-


Involvement of people:
• Between 3, 4 and 5 people should be involve in the review.
• Advance preparation should occur but it should be very short that is at
the most 2 hours of work for every person.
• The short duration of the review meeting should be less than two hour.
Gives these constraints, it should be clear that an FTR focuses on specific
(and small) part of the overall software.
13
Formal Technical Review

• At the end of the review, all attendees of FTR must decide what to do.
• Accept the product without any modification.
• Reject the project due to serious error (Once corrected, another app
need to be reviewed), or
• Accept the product provisional (minor errors are encountered and are
should be corrected, but no additional review will be required).
• The decision was made, with all FTR attendees completing a sign-of
indicating their participation in the review and their agreement with
the findings of the review team.

14
Formal Technical Review

• Review reporting and record keeping :-


• During the FTR, the reviewer actively records all issues that have been
raised.
• At the end of the meeting all these issues raised are consolidated and
a review list is prepared.
• Finally, a formal technical review summary report is prepared.

15
Formal Technical Review

• It answers three questions :-


• What was reviewed ?
• Who reviewed it ?
• What were the findings and conclusions ?

16
Formal Technical Review

• Review guidelines
Guidelines for the conducting of formal technical reviews should be
established in advance.
• These guidelines must be distributed to all reviewers, agreed upon,
and then followed.
• A review that is unregistered can often be worse than a review that
does not minimum set of guidelines for FTR.

17
Formal Technical Review

• Review the product, not the manufacture (producer).


• Take written notes (record purpose)
• Limit the number of participants and insists upon advance preparation.
• Develop a checklist for each product that is likely to be reviewed.
• Allocate resources and time schedule for FTRs in order to maintain time schedule.
• Conduct meaningful training for all reviewers in order to make reviews effective.
• Reviews earlier reviews which serve as the base for the current review being
conducted.
• Set an agenda and maintain it.
• Separate the problem areas, but do not attempt to solve every problem notes.

18
References

• https://www.geeksforgeeks.org/software-engineering-software-revie
w/
• https://professionalqa.com/software-review
• https://www.geeksforgeeks.org/formal-technical-review-ftr-in-
software-engineering/#:~:text=Formal%20Technical%20Review
%20(FTR)%20is,formal%20technical%20review%20(FTR)
%3A&text=The%20purpose%20of%20FTR%20is,represented
%20according%20to%20predefined%20standards.

19
THANK YOU

20

You might also like