Scribd
Upload
159 views

Eight Consideration of Testing Methodologies

The document discusses the key components of software quality assurance. It describes 6 classes of SQA system components: 1) pre-project components, 2) software project life cycle components, 3) infrastructure components for error prevention and improvements, 4) management SQA components, 5) SQA standards, system certification and assessment components, and 6) organizing for SQA – the human components. The document outlines the objectives and considerations for each component class in developing a comprehensive SQA system.

Uploaded by

Aswini M
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
159 views

Eight Consideration of Testing Methodologies

The document discusses the key components of software quality assurance. It describes 6 classes of SQA system components: 1) pre-project components, 2) software project life cycle components, 3) infrastructure components for error prevention and improvements, 4) management SQA components, 5) SQA standards, system certification and assessment components, and 6) organizing for SQA – the human components. The document outlines the objectives and considerations for each component class in developing a comprehensive SQA system.

Uploaded by

Aswini M
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Components of

Software Quality
Assurance
 SQA system components can be classified into 6 classes
1) Pre-project components
2) Software project life cycle components
3) Infrastructure components for error prevention and improvements
4) Management SQA components
5) SQA standards, system certification and assessment components
6) Organizing for SQA – the human components

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
3

 To assure that :
1. The project commitments have been adequately defined
considering the resources required, the schedule and budget.
2. The development and quality plans have been correctly
determined.
Contract reviews
 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 fulfill his obligations
 Evaluation of development risks.

Development and quality plans


 Reviews
 Expert opinions
 Software testing
 Software maintenance components
 Assurance of the quality of
external participants’ work

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
4

 The project life cycle composed of two stages:


1. The development Life cycle stage:
 Detect design and programming errors
 Its components divided into:
 Reviews
 Expert opinions
 Software testing
 Assurance of the quality of the subcontractors’work and
customer-supplied parts.
2. The operation-maintenance stage
 Include specialize maintenance components as well as development
life cycle components, which are applied mainly for functionality
improving maintenance tasks.
 Procedures and work instruction
 Templates and checklists
 Staff training, retraining and
certification
 Preventive and corrective actions
 Configuration management
 Documentation control

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
5

Main objectives of these components, which are applied throughout the


entire organization, are :
To eliminate or at least reduce the rate of errors, based on the
organization’s accumlated SQA experience.
 Project progress control
 Software quality metrics
 Software quality costs

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
6

 This class of components is geared toward several goal:


 The major ones being the control of development and maintenance activities and
introduction of early managerial support actions that mainly prevent or minimize
schedule and budget failures and their outcomes.
 Project process standards
 Quality management standards

Objectives:
 Utilization of international professional knowledge
 Improvement of coordination with other organizations’
quality systems
 Objective professional evaluation and measurement of the
organization’s SQA achievement
Galin, SQA from Theory to Implementation
@Pearson Education Limited 2004
7

The main objective of this class are:


1. Utilization of international professional knowledge
2. Improvement of coordination of the organizational
quality system with other organizations
3. Assessment of the achievements of quality systems
according to a common scale.
 The various standards classified into 2 groupes:
 Quality management standards
 Project process standards.
 Management’s role in SQA

 The SQA unit


 SQA trusties
 SQA committees

 SQA forums

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
8

The SQA organizational base includes :


 Managers
 Testing personnel
 The SQA unit and practitioners interested in SQ.
 The main objectives are :
 to initiate and support the implementation of SQA components
 Detect deviation from SQA procedures and methodology
 Suggest improvements
The Software Quality Shrine

Project
Contract review Development plan
and Quality Plan
Ch.5 Ch.6

Project Life Cycle SQA components

SQA of External Participants


Formal Design Reviews
Sec. 8.2

Ch 12
Quality Infrastructure components Quality Management Standards
Supporting Training Document- Project Software Software Quality Project
Preventive Configuration
Process
Management
ation Progress Quality Quality Management
Procedures Devices Instruction Actions Control Control Metrics Costs Standards Standards
Ch. 14 Ch. 15 Ch. 16 Ch.17 Ch. 18 Ch. 19 Ch. 20 Ch. 21 Ch. 22 Ch. 23 Ch.24

Organizational Base – Human components


Management - Ch. 25 SQA Unit - Sec. 26.1 SQA Trustees – Sec. 26.2 SQA Committees – Sec. 26.2 SQA Forums – Sec 26.4

Galin, SQA from Theory to Implementation


@Pearson Education Limited 2004
1. Organizational considerations
a. Type of software development clientele
b. Type of software maintenance clientele
c. Range of software products
d. Size of the organization
e. Degree and nature of cooperation with other organizations carrying out related projects
f. Optimization objectives
2. Project and maintenance service considerations
a. Level of complexity and difficulty
b. Degrees of experience with the project technology
c. Extent of software reuse in the new projects

3. Professional staff considerations


a. Professional qualifications
b. Level of acquaintance with team members

You might also like