1. Software QualityInfrastructureProcedures and Work instruction LUTHFIYA ULINNUHA - 5209100115
2. 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.
3. 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
5. 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.
6. AdvantageFacilitates the process of preparing documentsFacilitates review of documentsEnsures that documents prepared by the developer are morecompleteProvides for easier integration of new team membersEnables easier location of the information
7. List activitiesPreparation of new templates Application of templates Updates templates
8. 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).
9. Example of Checklist
10. Advantage of Using ChecklistHelps developers carrying out self-checks of documents orsoftware codeAssists developers in their preparations for tasksAssures completeness of document reviews by review teammembersProvides for easier integration of new team membersFacilitates improves efficiency of review sessions
11. List activitiesPreparation of new checklist Promotion of Checklist Use Updating Cheklist
12. Software QualityInfrastructureStaff Training and Certification
13. 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
14. Determining training and updatingneeds• 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.
15. Software QualityInfrastructureCorrective and Preventive Actions
16. 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.
17. 5 main approachesfor introductionof CAPA.■ Updating relevant procedures.■ Changing software developmentor maintenance practices and updating workinstructions.■ Changing current to more effective software development tools that are less prone tofaults.■ Improving reporting methods by revising task content and reporting frequencies. Thisapproach is meant to achieve earlier detection of faults and thus reduce damages.■ Initiating training, retraining and updating ofstaff.
18. Activities of CAPAInformation collectionAnalysis of informationDevelopment of solutions and improved methodsImplementation of improved methodsFollow-up.
19. 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.
20. B. Analysis of collectedInformation Screening the information and identifying potential improvements. Analysis of potential improvements. Generating feedback
21. • Follow-up of the flow of development andC. Follow- maintenance CAPA up recordsofactivities • Follow-up of implementation. • Follow-up of outcomes.
24. 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.
25. SCIs are generally placed into 4 class Design documents Software code Data files, including files of test cases and test scripts Software development tools.
26. Configuration ManagementVersion• 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.
27. Task of software configurationmanagement Controlofsoftware change Release of SCI and software configuration versions Provision ofSCM information services Verification ofcompliance to SCM procedures.
28. Main task of software changecontrol 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.
29. 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.
30. • 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.
31. Objective software configurationmanagement plan Plan ahead the required resources to carry out all the activitiesrequired for the software configuration releases
32. Software QualityInfrastructureDocumentation Control
33. 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.
34. ObjectiveTo assure To assure the future the availability ofquality of documents that the maybe required fordocumen software system t maintenance, To assure its To support technical investigation completeness of software and compliance failure causes
35. 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.
36. Procedures Definition of the listofthe Document preparation document typesand requirements updates to be controlled Document storage and retrieval requirements, Document approval including controlled storage requirements Of document versions, revisions and disposal
37. Component of procedures
38. • Taken from Software Quality Assurance , Daniel Galin