THE LITTLE FLOWER’S COLLEGE

Academic Year : 2021-2021

Sub: STQA
Std : SYBCA

Topic
Ch2: Quality concept
• Quality of software means makes your software bug or
defect free, delivered on time and within budget, meets
requirements and/or expectations, and is maintainable.
• Key aspects of quality for the customer include:
• Good design – looks and style
• Good functionality – it does the job well
• Reliable – acceptable level of breakdowns or failure
• Consistency
• Durable – lasts as long as it should
• Good after sales service
• Value for money
• Good design – looks and style:
• It is very important to have a good design. The application or product should
meet all the requirement specifications and at the same time it should be user
friendly. The customers are basically attracted by the good looks and style of the
application. The right color combinations, font size and the styling of the texts
and buttons are very important.

• Good functionality – it does the job well:

• Along with the good looks of the application or the product it’s very important
that the functionality should be intact. All the features and their functionality
should work as expected. There should not be any deviation in the actual result
and the expected result.

• Reliable – acceptable level of breakdowns or failure:

• After we have tested for all the features and their functionalities it also very
important that the application or product should be reliable. For example: There
is an application of saving the students records. This application should save all
the students records and should not fail after entering 100 records. This is called
reliability.
• Consistency:
• The software should have consistency across the application or
product. Single software can be multi dimensional. It is very important
that all the different dimensions should behave in a consistent manner.
• Durable – lasts as long as it should:
• The software should be durable. For example if software is being used
for a year and the number of data has exceed 5000 records then it
should not fail if number of records increases. The software product or
application should continue to behave in the same way without any
functional breaks.
• Good after sales service:
• Once the product is shipped to the customers then maintenance
comes into the picture. It is very important to provide good sales
services to keep the customers happy and satisfied. For example if after
using the product for six months the customer realizes to make some
changes to the application then those changes should be done as fast
as possible and should be delivered to the customers on time with
quality.
 Value for money:
 It’s always important to deliver the product to the customers which
have value for money. The product should meet the requirement
specifications. It should work as expected, should be user friendly.
We should provide good services to the customers. Other than the
features mentioned in the requirement specifications some
additional functionality could be given to the customers which they
might not have thought of. These additional functionalities should
make their product more user friendly and easy to use. This also
adds value for money.
 Quality Assurance
• What Is Assurance?
• Assurance is provided by organization management, it means
giving a positive declaration on a product which obtains
confidence for the outcome. It gives a security that the
product will work without any glitches as per the expectations
or requests.
• What Is Quality Assurance?

• Quality Assurance is known as QA and focuses on preventing

defect. Quality Assurance ensures that the approaches,
techniques, methods and processes are designed for the
projects are implemented correctly.
• Quality assurance activities monitor and verify that the
processes used to manage and create the deliverables have
been followed and are operative.
• Quality Assurance is a proactive process and is Prevention in
nature. It recognizes flaws in the process. Quality Assurance
has to complete before Quality Control.
 What is Control?

 Control is to test or verify actual results by comparing it with the

defined standards.
• What Is Quality Control?
• Quality Control is known as QC and focuses on identifying a
defect. QC ensures that the approaches, techniques, methods
and processes are designed in the project are following
correctly. QC activities monitor and verify that the project
deliverables meet the defined quality standards.
• Quality Control is a reactive process and is detection in nature. It
recognizes the defects. Quality Control has to complete after
Quality Assurance.
 Quality Factor

• The need for comprehensive software quality requirements .

• Classifications of software requirements into software quality
factors  McCall’s factor model
• The various attributes of software and its use and
maintenance, as defined in software requirements documents
,can be classified into content groups called quality factors.
 McCall’s factor model include:

• Product operation factors: Correctness, Reliability, Efficiency,

Integrity,Usability.
• Product revision factors: Maintainability, Flexibility, Testability.
• Product transition factors: Portability, Reusability,
Interoperability
1) Product operation factors: Correctness, Reliability, Efficiency,
Integrity,Usability.
• Reliability :
• Reliability requirements deal with failures to provide service. They
determine the maximum allowed software system failure rate, and can
refer to the entire system or to one or more of its separate functions.
• Correctness :Correctness requirements are defined in a list of the software
system’s required outputs.
a. The output mission
b. Accuracy of output
c. Completeness of the output information
d. Up-to-date of the information
e. Availability of the information.The
f. standard for coding and documenting of software system
• Integrity :
• Integrity requirements deal with the software system security, that
is, requirements to prevent access to unauthorized persons, to
distinguish between the majority of personnel allowed to see the
information (“read permit”) and a limited group who will be allowed
to add and change data (“write permit”).
• Efficiency :
• Efficiency requirements deal with the hardware resources needed to
perform all the functions of the software system in conformance to
all other requirements.
• Usability:
• Usability requirements deal with the scope of staff resources needed
to train a new employee and to operate the software system.
2) Product revision factors: Maintainability, Flexibility,
Testability.
• Maintainability :
• Maintainability requirements determine the efforts
that will be needed by users and maintenance personnel to
identify the reasons for software failures, to correct the
failures, and to verify the success of the corrections. This
factor’s requirements refer to the modular structure of
software, the internal program documentation, and the
programmer’s manual, among other items.
• Flexibility :
• The capabilities and efforts required to support adaptive
maintenance activities are covered by the flexibility
requirements. These include the resources(i.e. in man-days)
required to adapt a software package to a variety of customers
of the same trade, of various extents of activities, of different
ranges of products and so on. This factor’s requirements also
support perfective maintenance activities.
• Testability :
• Testability requirements deal with the testing of an information
system as well as with its operation. Testability requirements for
the ease of testing are related to special features in the
programs that help the tester, for instance by providing
predefined intermediate results and log
3) Product transition factors: Portability, Reusability,
Interoperability.
• Portability :
• Portability requirements tend to the adaptation of a software
system to other environments consisting of different
hardware, different operating systems.
• Reusability :
• Reusability requirements deal with the use of software
modules originally designed for one project in a new software
project currently being developed.
• Interoperability :
• Interoperability requirements focus on creating interfaces
with other software systems or with other equipment
firmware (for example, the firmware of the production
machinery and testing equipment interfaces with the
production control software).  Interoperability requirements
can specify the name(s) of the software or firmware for which
interface is required. They can also specify the output
structure accepted as standard in a specific industry or
applications area.
 Quality Metrics

• It is not possible to manage anything until you can't measure it. Software
quality metric provides an effective way to manage the quality of the larger
processes of Software Development Life Cycle (SDLC) along with task of
managing the software quality throughout the development cycle.
• What is Software Quality Metrics?
• The word 'metrics' refer to standards for measurements. Software Quality
Metrics means measurement of attributes, pertaining to software quality
along with its process of development.
• The term "software quality metrics“ illustrate the picture of measuring the
software qualities by recording the number of defects or security loopholes
present in the software. However, quality measurement is not restricted to
counting of defects or vulnerabilities but also covers other aspects of the
qualities such as maintainability, reliability, integrity, usability, customer
satisfaction, etc.
 Why Software Quality Metrics?

• To define and categorize elements in order to have better

understanding of each and every process and attribute.
• To evaluate and assess each of these process and attribute
against the given requirements and specifications.
• Predicting and planning the next move w.r.t software and
business requirements.
• Improving the Overall quality of the process and product, and
subsequently of project.
• Software Quality Metrics: sub-category of Software Metrics
• It is basically, a subclass of software metrics that mainly
emphasizes on quality assets of the software product,
process and project. Software metric is a broader concept
that incorporates software quality metrics in it, and mainly
consists of three types of metrics:
• Product Metrics: It includes size, design, complexity,
performance and other parameters that are associated with
the product's quality.
• Process Metrics: It involves parameters like, time-duration in
locating and removing defects, response time for resolving
issues, etc.
• Project Metrics: It may include number of teams, developers
involved, cost and duration for the project, etc.
 Methodology Of Software Quality Metrics

• The methodology behind software quality metric is as under:

• Identify and prepare the list of possible requirements of
quality, and subsequently, assigning direct metric, such as
understanding, learning and operation time, to each of these
requirements.
• Apply metrics framework, along with the cost-benefit analysis.
• Implementing metrics via collecting and defining data to
compute metric values.
• Interpret and analyse the results, to ensure the fulfilment of
requirements.
• Validate the metrics through validation methodology and
thereafter proper documentation of the results.