Software Quality Management SQA Components
Software Quality Management SQA Components
Software Quality Management SQA Components
SQA COMPONENTS
https://www.tutorialspoint.com/software_quality_management/software_quality_management_sqa_components.htm Copyright © tutorialspoint.com
Advertisements
Software Quality Assurance S QA is a set of activities for ensuring quality in software engineering processes. It ensures that
developed software meets and complies with the defined or standardized quality specifications. SQA is an ongoing process within
the Software Development Life Cycle S DLC that routinely checks the developed software to ensure it meets the desired quality
measures.
SQA practices are implemented in most types of software development, regardless of the underlying software development model
being used. SQA incorporates and implements software testing methodologies to test the software. Rather than checking for
quality after completion, SQA processes test for quality in each phase of development, until the software is complete. With SQA,
the software development process moves into the next phase only once the current/previous phase complies with the required
quality standards. SQA generally works on one or more industry standards that help in building software quality guidelines and
implementation strategies.
Processes could be −
Once the processes have been defined and implemented, Quality Assurance has the following responsibilities −
Pre-project components
https://www.tutorialspoint.com/cgi-bin/printpage.cgi 1/3
4/15/2019 Software Quality Management SQA 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.
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.
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.
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.
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.
Contract Review
Development and Quality Plans
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
https://www.tutorialspoint.com/cgi-bin/printpage.cgi 2/3
draft and the contract drafts.
4/15/2019 Software Quality Management SQA Components
Evaluation of the professional staff’s capacity to carry out the proposed project
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.
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.
Schedules
Required manpower and hardware resources
Risk evaluations
Organizational issues: team members, subcontractors and partnerships
Project methodology, development tools, etc.
Software reuse plans
Lists of reviews, tests, and other scheduled verification and validation activities
https://www.tutorialspoint.com/cgi-bin/printpage.cgi 3/3