software quality infrastructure

Software Quality Infrastructure Procedures and Work instruction

LUTHFIYA ULINNUHA - 5209100115

Definition

• procedures, as transmitted in documents, are the detailed activities or processes to be performed according to a given method for the purpose of accomplishing a task

• Work instructions are used mainly in cases where a uniform method of performing the task throughout the organization is either impossible or undesirable.

List activities

Preparation new procedures

• Shoul deal with conceptual and organizational framework

Implementation of new or revised procedures

• Distributed in a team with instruction

Update procedures

Software Quality Infrastructure Supporting Quality devices

Templates

• a format (especially tables of contents) created by units or organizations, to be applied when compiling a report or some other type of document.

Advantage

Facilitates the process of preparing documents

Facilitates review of documents

Ensures that documents prepared by the developer are more complete

Provides for easier integration of new team members

Enables easier location of the information

List activities

Preparation of new templates

Application of templates

Updates templates

Checklist

• the list of items specially constructed for each type of document, or a menu of preparations to be completed prior to performing an activity (e.g., installing a software package at the customer site).

Example of Checklist

Advantage of Using Checklist

Helps developers carrying out self-checks of documents or software code

Assists developers in their preparations for tasks

Assures completeness of document reviews by review team members

Provides for easier integration of new team members

Facilitates improves efficiency of review sessions

List activities

Preparation of new checklist

Promotion of Checklist Use

Updating Cheklist

Software Quality Infrastructure Staff Training and Certification

Objective

To develop the knowledge and skillsnew staff

To assure conformityto the organization’sstandardsfor software products(documentsand code)

To update the knowledge and skillsofveteran staffin response to developmentsin the organization

To transmit knowledge of SQA procedures.

To assure that candidates for key software development and maintenance positionsare adequately qualified

Determining training and updating needs • determined by comparison of the staff’s current knowledge

with the updated knowledge requirements.

Training: for new employees, according to their designated assignment

Retraining: for employees assigned to new positions or receiving new assignments

Updating: for staff members as demanded by their position.

Software Quality Infrastructure Corrective and Preventive Actions

Definition

• Defect correction is a limited activity directed toward immediate solution of defects detected in a projector a software system.

• Corrective and preventive actions are wider in scope; theyare meant to initiate and guide performance oforganization-wide actions that will eliminate the causes of known or potentialfaults.

5 main approachesfor introduction of CAPA.

■ Updating relevant procedures.

■ Changing software developmentor maintenance practices and updating work instructions.

■ Changing current to more effective software development tools that are less prone to faults.

■ Improving reporting methods by revising task content and reporting frequencies. This approach is meant to achieve earlier detection of faults and thus reduce damages.

■ Initiating training, retraining and updating ofstaff.

Activities of CAPA

Information collection

Analysis of information

Development of solutions and improved methods

Implementation of improved methods

Follow-up.

A. Information Collective

- Four main internal sources of information are the (1)Software development process

(2) Software maintenance

(3) SQA infrastructure and

(4) Software quality management procedures.

- External sources of information are mainly customers’ application statistics and cus-

tomer complaints.

B. Analysis of collected Information

Screening the information and identifying potential improvements.

Analysis of potential improvements.

Generating feedback

• Follow-up of the flow of development and maintenance CAPA records

• Follow-up of implementation.

• Follow-up of outcomes.

C. Follow-up

ofactivities

CAPA Process

Software Quality Infrastructure Configuration Management

Definition

• An approved unitofsoftware code, a documentor piece ofhardware that is designed for configuration management and treated asa distinct entity in the software configuration management process.

Design documents

Software code

Data files, including files of test cases and test scripts

Software development tools.

SCIs are generally placed into 4 class

Configuration Management Version • A software configuration version isan approved set of the SCI

versions that constitute a documented software system ata given point of time. The respective activities are controlled by software configuration management procedures.

Task of software configuration management

Controlofsoftware change

Release of SCI and software configuration versions

Provision ofSCM information services

Verification ofcompliance to SCM procedures.

Main task of software change control

Examining change requests and approving implementation those requests that qualify.

Controlling the changesand assuring the quality of approved changes.

Documenting the approved changes.

Applying mechanisms thatpreventmore than one team from simultaneously

introducing changesinto the same SCI.

Type software configuration

• Baseline version

Configuration versionsthatare planned ahead, during a system’sdevelopmentor operating stage. As part of the process, baseline versions are also reviewed and approved.

• Intermediate version

software configuration versions released, in most cases, to respond to immediate needs. These mayrange from correction of defects identified in an important SCI to swift introduction of adaptations to meet a new customer’s requirements.

Objective software configuration management plan

Plan ahead the required

resources to carry out all the

activitiesrequired for the software

configuration releases

Software Quality Infrastructure Documentation Control

Definitions

• A document that is currently vital or may become vitalfor the development and maintenance of software systems as well as for the management of current and future relationships with the customer.

Objective

To assure the

quality of the

document

To assure its technical

completeness and compliance

To assure the future availability of

documents that maybe required for

software system maintenance,

To support investigation of software

failure causes

Quality record

• a special type ofcontrolled document.

• It is a customer-targeted document that maybe required to demonstrate full compliance with customer requirements and effective operation of the software quality assurance system throughout the development and maintenance processes.

Procedures

Definition of the listofthe document typesand

updates to be controlled

Document preparation requirements

Document approval requirements

Document storage and retrieval requirements,

including controlled storage Of document versions, revisions and disposal

Component of procedures

• Taken from Software Quality Assurance , Daniel Galin

THANK YOU