Tips

For attempting Answers

Questions – Unit-1: (5 OR 10 Marks)

1. Explain McCall’s Quality model for quality assessment with examples.

2. Differentiate between McCall’s Quality Model and Boehm’s Quality
Model.
3. Define Defect Prevention and mention the reason why Defect Prevention Is
Important?
4. Describe the activities coming under Defect Prevention?
5. Explain the steps under Defect Prevention with its advantages.
6. Differentiate between Defect Reduction and Defect Containment.
7. Differentiate between ISO/IEC 9126 and ISO 25010:2011 Quality.
8. What do you mean by the software reviews ? How is software review
carried out ? Discuss any two software review methods.
Questions – Unit 1: (2 Marks)

1. Define Software Quality with the help of an example.

2. What do you mean by inspection process? Discuss.
3. Explain the terms: Defect, Fault, Failure
4. Why do we need documents and metrics in software quality engineering?
5. Discuss various quality attributes.
6. Define Software Reliability in brief.
7. What is cost of software quality.
8. What do you understand by software measurement?
9. Write a short note on origins of defects
 Write a short note on origins of defects.

The term defect and its relationship to the

terms error and failure in the context of the
software development domain. Defects have
detrimental affects on software users, and
software engineers work very hard to
produce high-quality software with a low
number of defects. But even under the best
of development circumstances errors are
made, resulting in defects being injected in
the software during the phases of the
software life cycle. Defects as shown in fig
3.1 RHS.
Differentiate between ISO/IEC 9126 and ISO 25010:2011 Quality?

ISO 25010, which was published in 2011,

superseded ISO 9126 published in 2001.
The main difference between the two
lies in how they categorize and define
non-functional software quality
requirements.
ISO 25010 added two additional product
quality characteristics to the six specified
in ISO 9126 — adding security and
compatibility.
Explain McCall’s Quality model for quality assessment with examples.

McCall’s Factor Model: This model

classifies all software requirements into 11
software quality factors. The 11 factors are
grouped into three categories – product
operation, product revision, and product
transition factors.
• Product operation factors − Correctness,
Reliability, Efficiency, Integrity,
Usability.
• Product revision factors −
Maintainability, Flexibility, Testability.
• Product transition factors − Portability,
Reusability, Interoperability.
Differentiate between McCall’s Quality Model and Boehm’s Quality Model.

Boehm’s software quality model offers more attributes and

characteristics of product than McCall’s quality model. It was
presented by Barry W. Boehm in 1978. Boehm’s model is
almost similar to the McCall Quality Model because it also
presents a hierarchical quality model designed about high-level,
intermediate level and primitive characteristics, each of them
plays an important role in the overall quality level. All above
stated levels represent the questions of buyer, the quality factor
which can affect or represent the quality of product and offers
the basis for describing qualities metrics. The difference in
these two models is that McCall’s model mainly centers on the
accurate measurement of the high-level characteristics “As-is
utility”. On other hand Boehm’s quality model is dependent on
a broader range of characteristics with a stretched and detailed
emphasis on primarily maintainability.
Difference among Defect Prevention, Defect Reduction and Defect
Containment.

Defect containment measures focus on the failures by either containing them

to local areas so that there are no global failures observable to users, or limiting
the damage caused by software system failures.
• Defect Containment Effectiveness(DCE)
• Phase Containment Effectiveness (PCE)
• Total Defect Containment Effectiveness (TDCE)
• Defect Removal Effectiveness (DRE)
What is Defect Prevention. Why Defect Prevention Is Important?

Defect Prevention (DP) is a strategy applied to the software development life

cycle that identifies root causes of defects and prevents them from recurring
Why it is important?:
• Once QA engineers invested time on Defect Prevention in the early stages of
the development process, they do not have to put more time and effort into
detecting defects and tracking them in the testing stage. This directly saves
time and leads to an on-time delivery of the product.
• It is very cost effective, and time saving to identify the defects and fix them in
the early stages of the development process. As the code base grows, it is
more difficult to fix a defect without having a negative impact that leads to
rework.
What are the activities coming
under Defect Prevention?

Software Requirement Analysis: The main cause of defects in

software products is due to error in software requirements and
designs. Software requirements and design both are important
and should be analyzed in an efficient way with more focus.
Software requirement is basically considered an integral part
of Software Development Life Cycle (SDLC). These are the
requirements that basically describes features and
functionalities of target product and also conveys expectations
or requirement of users from software product. Therefore, it is
very much needed to understand about software requirements
more carefully, If requirements are not understood well by
tester and developers, then there might be chance of occurring
of issue or defect in further process. Therefore, it is essential to
analyze and evaluate requirements in more appropriate and
proper manner.
Review and Inspection: Review and Defect Logging and Documentation:
inspection, both are essential and After successful analysis and review, there
integral part of software should be records maintained about defects to
development. They are considered as simply complete description of defect. This
powerful tools that can be used to record can be further used to have better
identify and remove defects if understanding of defects. After getting
present before there occurrence and knowledge and understanding of defect, then
impact on production. Review and only one can take some effective and required
inspection come in different levels or measures and actions to resolve particular defects
stages of defect prevention to meet so that defect cannot be carried further to next
different needs. They are used in all phase.
software development and Root Cause Analysis: Root cause analysis is
maintenance methods. There are two basically analysis of main cause of defect. It
types of review i.e., self-review and simply analysis what triggered defect to occur.
peer-review. After analyzing main cause of defect, one can
What are the activities coming find best way to simply avoid occurrence of such
under Defect Prevention? types of defects next time.
 What are the steps under Defect
Prevention with its advantages?

Identifying Critical Defect: Identification of defect

is one of major part of defect prevention. During
SDLC, different types of defects are encountered.
Each defect has different impact on system. Some of
them have severe impact i.e. largely affects system,
some of them are less severe i.e. have less impact on
system, and some of them have very less impact on
system that can be considered as negligible.
Therefore, it is very important to identify critical
and more severe defects in system at soon as
possible. Critical defects are very severe and have
more impact on system as on their occurrence, they
might stop the functioning of overall system or can
cause some other problems on greater level. So, it is
very much essential to identify critical defects.
Estimate Expected Impact: Estimating expected impact of defect on cost is
also important part of defect prevention. Whenever defect is encountered in
system, main questions arises is what are measures that are needed to be taken
to resolve it and amount required to resolve it. More critical defect is, more
will be amount required to resolve it as more effort and resources will be
required to resolve it. Therefore, it’s better to estimate expected impact of
defect on cost if defect somehow encounters or occurs. After that, some
measures should be taken to minimize their occurrence.
Minimize Expected Impact: After identifying and estimating impact of
critical defects, one should take some measures actions to minimize or
eliminate defects permanently before its occurrence. Minimizing expected
impact is also important part of defect prevention. If one could not eliminate
defect, then he/she should try to reduce possibility of its occurrence and its
impact.
Advantages of DP
• Number of defects in a system is reduced or minimized by taking some
measures required.
• Checklist that is being developed for review is improved.
• Amount of work required to fix defect is reduced as number of defects is
minimized.
• Overall cost of production is reduced as cost required to resolve defect is
minimized by taking some measures to prevent defect from re-occurrence.
• Helps in making software defect-free as much as possible.
• Increase overall quality of software products.
• Improves software process by backing up testing process and minimizing cost
required of resolving errors.
What do you mean by the software
reviews ? How is software review
carried out ? Discuss any two
software review methods.

Software Review is systematic inspection

of a software to find and resolve errors
and defects in the software during the
early stages of Software Development Life
Cycle (SDLC). It helps in validating the
quality, functionality and other vital
features and components of the software.
It is a whole process that includes testing
the software product and it makes sure
that it meets the requirements stated by
the client.
Software Review is carried out with the
following steps in testing process as in RHS
There are mainly 3 types of software reviews:
• Software Peer Review
• Software Management Review
• Software Audit Review
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.
Peer Review has following types:
• Code Review
• Pair Programming
• Walkthrough
• Technical Review
• Inspection
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.

What do you mean by the software

reviews ? How is software review
carried out ? Discuss any two
software review methods.
Questions – Unit-2: (5 OR 10 Marks)

1. Illustrate the meaning of Function Points in relation to ISO/IEC Standards with its
functional units & advantages of FPA.
2. What is FP? Write down its importance?
3. What is phase-based removal pattern? Discuss
4. What are the requirements of customer problem metrics? Discuss
5. Explain backlog management index for software quality metrics
6. Discuss various software quality indicators
7. How to measure customer satisfaction metrics? Explain with an example.
8. Describe the defect arrival pattern during machine testing and phase-based
removal pattern.
9. Explain various software maintenance metrics with example
10. Describe the following term with respect in SQE :
a) Mean time to failure (MTTF)
b) Defect density
Questions – Unit-2: (5 OR 10 Marks)

11. Is it possible to assess the quality of software if the customer keeps changing?
What is it supposed to do?
12. Demonstrate the significance of In-Process Quality Metrics for dealing with defect.
13. What do you mean by function points (FPs) ? Why are FPs becoming acceptable in
industry ? Also compute the function point value for a project with the following
information domain characteristics :
Number of user inputs=30
Number of user outputs=42
Number of user enquiries=08
Number of files=07
Number of external interfaces=06
Assume that all complexity adjustments values are moderate.
Questions – Unit 2: (2 Marks)

1. What is Net Satisfaction Index (NSI). Describe with example?

2. Explain function points
3. What are the requirements of customer problem metrics
4. What is Phase-based Defect Removal Pattern.
5. Differentiate between Fix quality and software quality
6. Explain backlog, management index for software quality matrices