Department of Computer Science

University Institute of Engineering

DEPARTMENT OF COMPUTER SCIENCE
& ENGINEERING
Bachelor of Engineering
Subject Name: Software Engineering
Subject Code: CST-220

Quality Management DISCOVER . LEARN . EMPOWER

1
 Introduction to Software Engineering
Department of computer Science

Course Outcome
CO Title Level
Number

C01 Students will be able to learn how to apply  Understand

the software engineering lifecycle by
demonstrating competence in
communication, planning, analysis, design,
construction, and deployment.

C02 Students will be able to gain knowledge of Understand

software design and UI design.  

CO3 Students will be able to apply testing Understand

guidelines.

2
 Department of computer Science

Chapter-8
Quality Management
• SQA

3
SQA

• Software quality assurance is a planned and systematic plan of all

actions necessary to provide adequate confidence that an item or
product conforms to establish technical requirements.

• A set of activities designed to calculate the process by which the

products are developed or manufactured.

4
SQA Encompasses

• A quality management approach

• Effective Software engineering technology (methods and tools)
• Formal technical reviews that are tested throughout the software
process
• A multitier testing strategy
• Control of software documentation and the changes made to it.
• A procedure to ensure compliances with software development
standards
• Measuring and reporting mechanisms.
5
SQA Activities

• Software quality assurance is composed of a variety of functions

associated with two different constituencies ?

• The software engineers who do technical work and an SQA group that
has responsibility for quality assurance planning, record keeping,
analysis, and reporting.

6
Activities of SQA
• Following activities are performed by an independent SQA group:
• Prepares an SQA plan for a project: The program is developed during
project planning and is reviewed by all stakeholders.
• The plan governs quality assurance activities performed by the
software engineering team and the SQA group.
• The plan identifies calculation to be performed, audits and reviews to
be performed, standards that apply to the project, techniques for
error reporting and tracking, documents to be produced by the SQA
team, and amount of feedback provided to the software project team.

7
Activities of SQA
• Participates in the development of the project's software process
description: The software team selects a process for the work to be
performed.
• The SQA group reviews the process description for compliance with
organizational policy, internal software standards, externally imposed
standards (e.g. ISO-9001), and other parts of the software project
plan.

8
Activities of SQA
• Reviews software engineering activities to verify compliance with
the defined software process: The SQA group identifies, reports, and
tracks deviations from the process and verifies that corrections have
been made.
• Audits designated software work products to verify compliance with
those defined as a part of the software process: The SQA group
reviews selected work products, identifies, documents and tracks
deviations, verify that corrections have been made, and periodically
reports the results of its work to the project manager.

9
Activities of SQA
• Ensures that deviations in software work and work products are
documented and handled according to a documented
procedure: Deviations may be encountered in the project method,
process description, applicable standards, or technical work products.

• Records any noncompliance and reports to senior

management: Non- compliance items are tracked until they are
resolved.

10
Components of SQA System

• An SQA system always combines a wide range of SQA components.

These components can be classified into the following six classes −
• Pre-project components
• This assures that the project commitments have been clearly defined
considering the resources required, the schedule and budget; and the
development and quality plans have been correctly determined.

11
Components of SQA System

• Components of project life cycle activities assessment

• The project life cycle is composed of two stages: the development life
cycle stage and the operation–maintenance stage.
• The development life cycle stage components detect design and
programming errors. Its components are divided into the following
sub-classes: Reviews, Expert opinions, and Software testing.
• The SQA components used during the operation–maintenance phase
include specialized maintenance components as well as development
life cycle components, which are applied mainly for functionality to
improve the maintenance tasks.
12
Components of SQA System

• Components of infrastructure error prevention and improvement

• The main objective of these components, which is applied throughout
the entire organization, is to eliminate or at least reduce the rate of
errors, based on the organization’s accumulated SQA experience.
• Components of software quality management
• This class of components deal with several goals, such as the control
of development and maintenance activities, and the introduction of
early managerial support actions that mainly prevent or minimize
schedule and budget failures and their outcomes.

13
Components of SQA System

• Components of standardization, certification, and SQA system

assessment
• These components implement international professional and
managerial standards within the organization. The main objectives of
this class are utilization of international professional knowledge,
improvement of coordination of the organizational quality systems
with other organizations, and assessment of the achievements of
quality systems according to a common scale. The various standards
may be classified into two main groups: quality management
standards and project process standards.

14
Components of SQA System

• Organizing for SQA – the human components

• The SQA organizational base includes managers, testing personnel,
the SQA unit and the persons interested in software quality such as
SQA trustees, SQA committee members, and SQA forum members.
Their main objectives are to initiate and support the implementation
of SQA components, detect deviations from SQA procedures and
methodology, and suggest improvements.

15
Pre-project Software Quality Components

• These components help to improve the preliminary steps taken

before starting a project. It includes −
• Contract Review
• Development and Quality Plans

16
Pre-project Software Quality Components

• Contract Review
• Normally, a software is developed for a contract negotiated with a
customer or for an internal order to develop a firmware to be
embedded within a hardware product.
• In all these cases, the development unit is committed to an agreed-
upon functional specification, budget and schedule.
• Hence, contract review activities must include a detailed examination
of the project proposal draft and the contract drafts.

17
Pre-project Software Quality Components

• Specifically, contract review activities include −

• Clarification of the customer’s requirements
• Review of the project’s schedule and resource requirement estimates
• Evaluation of the professional staff’s capacity to carry out the
proposed project
• Evaluation of the customer’s capacity to fulfil his obligations
• Evaluation of development risks

18
Pre-project Software Quality Components

• Development and Quality Plans

After signing the software development contract with an organization
or an internal department of the same organization, a development
plan of the project and its integrated quality assurance activities are
prepared.
• These plans include additional details and needed revisions based on
prior plans that provided the basis for the current proposal and
contract.

19
Pre-project Software Quality Components

• Most of the time, it takes several months between the tender

submission and the signing of the contract.
• During these period, resources such as staff availability, professional
capabilities may get changed.
• The plans are then revised to reflect the changes that occurred in the
interim.

20
Issues of Project Development
• The main issues treated in the project development plan are −
• Schedules
• Required manpower and hardware resources
• Risk evaluations
• Organizational issues: team members, subcontractors and
partnerships
• Project methodology, development tools, etc.
• Software reuse plans

21
Issues of Project Quality
• The main issues treated in the project’s quality plan are −
• Quality goals, expressed in the appropriate measurable terms
• Criteria for starting and ending each project stage
• Lists of reviews, tests, and other scheduled verification and validation
activities

22
 Department of computer Science

References

• https://
www.tutorialspoint.com/software_quality_management/software_qu
ality_management_sqa_components.htm

• https://www.javatpoint.com/software-quality-assurance

• https://
www.guru99.com/software-quality-assurance-test-audit-review-make
s-your-life-easy.html

23
THANK YOU

24