Scribd
Upload
235 views

SQA System Architecture

This document outlines the components of an SQA (Software Quality Assurance) system architecture. It describes six classes of SQA components: 1) Pre-project components like contract reviews and development/quality plans, 2) Software project life cycle components like reviews, testing, and maintenance, 3) Infrastructure components for error prevention and improvements like procedures and training, 4) Management SQA components, 5) SQA standards and assessment, and 6) Organizing the human components of SQA. Each component class is then described in more detail.

Uploaded by

Euclid Jay Corpuz
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
235 views

SQA System Architecture

This document outlines the components of an SQA (Software Quality Assurance) system architecture. It describes six classes of SQA components: 1) Pre-project components like contract reviews and development/quality plans, 2) Software project life cycle components like reviews, testing, and maintenance, 3) Infrastructure components for error prevention and improvements like procedures and training, 4) Management SQA components, 5) SQA standards and assessment, and 6) Organizing the human components of SQA. Each component class is then described in more detail.

Uploaded by

Euclid Jay Corpuz
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

SQA SYSTEM ARCHITECTURE

Prepared by: Euclid Jay Corpuz


SQA System Components can be
classified into six 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
Pre-project components

Contract reviews: includes a detailed


examination of the project proposal draft and
the contract drafts.

Development and quality plans: Once the


contract is signed, a plan is prepared of the
project and its integrated quality activities.
Pre-project components

Development Plan
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
Pre-project components

Quality Plan
The main issues treated in the projects quality
plan are:
Quality goals, expressed in the appropriate
measurable terms
Criteria for starting and ending each project stage
List of reviews, tests, and other scheduled
verification and validation activities.
Software project life cycle
components:
Reviews
Expert opinions
Software testing
Software maintenance components
Assurance of the quality of external
participants work
Project Life Cycle
Components
Reviews: The design phase of the development
process produces a variety of documents. Reviews
can be categorized as follows:
Formal design reviews (DRs): These documents
require formal professional approval of their quality
before moving to next step. Committees are
composed of senior professionals including project
leader.

Peer reviews (Inspections and Walkthrough): Directed


at reviewing short documents. Reviewers are all
peers. The main objective is to detect as many design
and programming faults as possible.
Project Life Cycle
Components
Expert opinions: Introduce additional external
capabilities into the organization:
Outside experts may join a DR committee.
Their opinions may replace a DR.
In case of disagreement of senior professionals,
an outside expert may support a decision.
Project Life Cycle
Components
Software testing: This includes formal SQA components that
are targeted toward review of the actual running of the
software. All tests have to be designed, planned and
approved.

Software maintenance components: Software maintenance


services fall into three categories:

Corrective maintenance
Adaptive maintenance
Functionality improvement maintenance

Assurance of the quality of external participants work:


Special efforts are needed to assure the quality of the
hardware, software, staff and training supplied by the
customer.
Infrastructure components
for error prevention and
improvements
Procedures and work instruction
Templates and checklists
Staff training, retraining and certification
Preventive and corrective actions
Configuration management
Documentation control
Infrastructure components
for error prevention and
improvements
Documentation control functions: Refer mainly
to customer requirement documents, contract
documents, design reports, project plans,

Documentation control activities: Entail


definition of the needed documents,
specification of the format, definition of review
and approval processes, definition of the
archive storage methods

You might also like