1 Quality Assurance Presentation


Published on

Published in: Technology, Business
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

1 Quality Assurance Presentation

  2. 2. AGENDA <ul><li>1.What is Quality? </li></ul><ul><li>2.What is Software Quality Assurance? </li></ul><ul><li>3.Components Of Quality Assurance. </li></ul><ul><li>4.Software Quality Assurance Plan. </li></ul><ul><li>5.Quality Standards. </li></ul>
  3. 3. What is Quality? <ul><li>1.Accroding to computer literature Quality means “Meeting Requirement”. </li></ul><ul><li>2.The product has something that other similar products do not that adds value. (Product based Definition). </li></ul>
  4. 4. Software Quality Assurace <ul><li>Systematic activities providing evidence of the fitness for use of the total software product. </li></ul><ul><li>It is achieved through the use of established guidelines for quality control to ensure integrity and prolonged life of software. </li></ul><ul><li>It is a planned effort to ensure that a software product fulfils criteria and has additional attributes specific to the product. </li></ul>
  5. 5. <ul><li>It is the collection of activities and functions used to monitor and control a software project so that specific objectives are achieved with the desired level of confidence. </li></ul><ul><li>It is not the sole responsibility of the software quality assurance group but is determined by the consenses of the project manager ,project leader, project personnel, and the users. </li></ul>Software Quality Assurace
  6. 6. Components of Quality Assurance
  7. 7. Software Testing <ul><li>Software testing is a popular risk management strategy.It is used to verify that functional requirements were met. </li></ul><ul><li>The major purpose of verification and validation activities is to ensure that software design, code, and documentation meet all the requirements imposed on them. </li></ul>
  8. 8. Quality Control <ul><li>Quality control is defined as the processes and methods used to monitor work and observe whether requirements are met.It focuses on reviews and removal of defects before shipment of products. </li></ul><ul><li>For small projects,the project personnel’s peer group or the department’s software quality coordinator can inspect the documents.on large projects a configuration control board may be responsible for quality control </li></ul>
  9. 9. Software Configuration Management. <ul><li>It is concerned with the labeling, tracking and controlling changes in the software elements of a system. </li></ul><ul><li>It consists of activities that ensure that design and code are defined and cannot be changed without a review of the effect of the change itself and its documentation. </li></ul>
  10. 10. Elements of software configuration management.
  11. 11. Component Identification <ul><li>A basic software configuration management activity is to identify the Software components that make up deliverable at each point of development. </li></ul><ul><li>In order to mange the development process one must establish methods and name the component standards. </li></ul>
  12. 12. Version control <ul><li>Software is frequently changed as it evolves through a succession of temporary states called versions. </li></ul><ul><li>A software configuration management </li></ul><ul><li>facility for controlling versions is a software configuration management repository or library. </li></ul>
  13. 13. Configuration Building <ul><li>To build a software configuration one needs to identify the correct components versions and execute the component build procedures.This is often called Configuration building. </li></ul><ul><li>Software configuration management uses different approaches for selecting versions.The simplest method is to maintain all the component verisons. </li></ul>
  14. 14. Change control <ul><li>Software Change control is the process by which a modification to a software component is proposed. </li></ul><ul><li>Modification of a configuration has four elements : a change request, an impact analysis of the change,a set of modifications and additions of new components and a method for reliably installing new componets. </li></ul>
  15. 15. Software Quality Assurance Plan <ul><li>Software quality assurance plan is an outline of quality measures to ensure quality levels within a software development effort. </li></ul><ul><li>The plan provides the framework and guidelines for development of understandable and maintainable code. </li></ul>
  16. 16. Step to develop and implement a Software quality Assurance Plan <ul><li>Step 1. Document the plan. </li></ul><ul><li>Step 2.Obtain Management Acceptance. </li></ul><ul><li>Step 3.Obtain development acceptance. </li></ul><ul><li>Step 4.Plan for implementation of the SQA Plan. </li></ul><ul><li>Step 5.Execute the SQA Plan. </li></ul>
  17. 17. Quality Standards. <ul><li>ISO9000 </li></ul><ul><li>CMM( Capability Maturity Model) </li></ul><ul><li>PCMM(People Capability Maturity Model) </li></ul><ul><li>CMMI </li></ul>