Scribd
Upload
52 views3 pages

Software Quality Assurance Principles

Uploaded by

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

Software Quality Assurance Principles

Uploaded by

balasubramanian MS
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

software quality assurance principles

HYPERLINK
"https://www.tutorialspoint.com/software_quality_management/software_quality_management_tutorial
.pdf"https://www.tutorialspoint.com/software_quality_management/
software_quality_management_tutorial.pdf

SOFTWARE QUALITY Management is a process that ensures the required level of


software quality is achieved when it reaches the users, so that they are satisfied by its
performance. The process involves quality assurance, quality planning, and quality
control. This tutorial provides a complete overview of Software Quality Management and
describes the various steps involved in the process. The entire content is divided into
sections for easy understanding.

It is especially beneficial for software quality managers, software testing professionals, and software
developers.

Software Quality Assurance

Software Quality Control

The Software Quality Challenge

The Software Quality Challenge In the software industry, the developers will never declare that the
software is free of defects, unlike other industrial product manufacturers usually do. s

Product Complexity
It is the number of operational modes the product permits. Normally, an industrial product
allows only less than a few thousand modes of operation with different combinations of its machine
settings. However
software packages allow millions of operational possibilities. Hence, assuring of all these operational
possibilities correctly is a major challenge to the software industry.

Product Visibility
Since the industrial products are visible, most of its defects can be detected during the
manufacturing process. Also the absence of a part in an industrial product can be easily detected in the
product. However, the defects in software products which are stored on diskettes or CDs are invisible.

in the case of software, the only phase where defects can be detected is the development phase.

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.
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: CREIU

Correctness - OUTPUT GOODNESS -How far the output is correct


• The required accuracy of output that can be negatively affected by inaccurate data or inaccurate
calculations.
• The completeness of the output information, which can be affected by incomplete data.
• The up-to-dateness of the information defined as the time between the event and the response by
the software system.,

Reliability,
Reliability requirements deal with service failure. They determine the maximum allowed
failure rate of the software system, and can refer to the entire system or to one or more of its separate
functions.

Efficiency- HARDWARE portion of the SOFTWARE


It deals with the hardware resources needed to perform the different functions of the software
system. It includes processing capabilities (given in MHz), its storage capacity (given in MB or
GB) and the data communication capability (given in MBPS or GBPS).

Integrity, SECURITY -AUTHORITY ACESSABILITY - This factor deals with the software
system security, that is, to prevent access to unauthorized persons, also to distinguish between the
group of people to be given read as well as write permit.

Usability. Usability requirements deal with the staff resources needed to train a new employee
and to operate the software system.

• Product revision factors: MFT


Maintainability - If problem, the software should be modified, testable, verified to the correctness

Flexibility, Flexibility to the new requirements without changes to existing software

Testability. While testing, it should able to give intermediate results,LOG files should be there,
to find out whether all components of the system are in working order and to obtain a report

• Product transition factors: PRI


Portability, SOFTWATE SHOULD BE REUSABLE on OtherHARDWARE, platform, other OS
Portability Portability requirements tend to the adaptation of a software system to other
environments consisting of different hardware, different operating systems, and so forth. The software
should be possible to continue using the same basic software in diverse situations. Reusability This
factor deals with the use of software modules originally designed for one project in a new software
project currently being developed. They may also enable future projects to make use of a given module
or a group of modules of the currently developed software. The reuse of software is expected to save
development resources, shorten the development period, and provide higher quality modules.
Reusability -Creating SUBROUTINES commonly usable with many systems
This factor deals with the use of software modules originally designed for one project in a new
software project currently being developed. They may also enable future projects to make use of a
given module or a group of modules of the currently developed software.
Inter operability. INTERFACES
Interoperability requirements focus on creating interfaces with other software systems

You might also like