Lecture 1

Ms Rubab wafa
“ In its most general sense, is a set of instructions or
programs instructing a computer to do specific
tasks”
 “Software quality is defined as a field of study and practice that
describes the desirable attributes of software products.”
“The degree to which a system, component, or process meets
customer or user needs or expectations.”
“Software Quality assurance is simply a way
to assure quality in the software.”
“Software quality assurance is a process which works
parallel to development of software.”
 They think it is time Consuming Process.

 They think it increase the cost of the project.

 SQA Produce High Quality Software and those
are beneficial.
 High quality application saves time and cost.
 Better reliability and no maintenance for long
time.
 High quality commercial software increase
market share.
Presently there are two important approaches
that are used to determine the quality of the
software:

1) Defect Management Approach

2) Quality Attributes approach
 Many times the development team fails to
fully understand the requirement of the client
which eventually leads to design error.
 Besides that, the error can be caused due to,
wrong coding or improper data handling. In
order to keep a track of defect a defect
management approach can be applied.
 In defect management, categories of defects
are defined based on severity. The number of
defects is counted and actions are taken as
per the severity defined.
 Quality Attribute Approach on the other hand
focuses on characteristics that are listed below
1. Functionality
2. Reliability
3. Usability
4. Efficiency
5. Maintainability
6. Portability
7. Correctness
8. Integrity
9. Flexibility
10. Reusability
 Functionality:
◦ It is the ability of the system to do the work
for which it was intended
 Reliability
◦ Minimum failure rate
 Efficiency
◦ resources needed to perform software
function
 Usability
◦ ability to learn, perform required task
 Maintainability
◦ effort to identify and fix software failures (modularity,
documentation, etc)
 Portability
◦ adaptation to other environments (hardware, software)
 Correctness
◦ accuracy, completeness of required output
◦ upto-date, availability of the information
 Integrity
◦ software system security, access rights
 Flexibility
◦ degree of adaptability (to new customers, tasks, etc)
 Reusability
◦ use of software components for other projects
 The measures for quality differ from project to project and
organization to organization
◦ Quality measures used for small systems may not be
appropriate for the large ones.
 Criteria for quality vary as a function of the specific
characteristics of the project, the needs of the users and
stakeholders, and the application requirements of the system
and software.
Verification: Are we building the system right?
Validation: Are we building the right system?
Verification: Is the process of evaluating
products of a development phase to find out
whether they meet the specified
requirements.
Validation: Is the process of evaluating
software at the end of the development
process to determine whether software meets
the customer expectations and requirements.
 Introduction to software quality assurance
 Quality Control v/s Quality Assurance
 Quality Assurance in Software Projects (Phases)
 Verification and Validation
 Inspections and reviews Walkthroughs
 Principles of software validation and Software
verification,
 Software Quality Assurance (SQA) Plans, SQA-
Organizational Level Initiatives to quality
assurance, Product Quality and Process Quality,
Standards for process quality and standards for
product quality, Structure, Checklist, Audits,
Roles