• Me gusta
1 Quality Assurance Presentation
Próxima SlideShare
Cargando en...5
×
  • Full Name Full Name Comment goes here.
    ¿Está seguro?
    Tu mensaje aparecerá aquí
  • Thanks a lot
    ¿Está seguro?
    Tu mensaje aparecerá aquí
Sin descargas

reproducciones

reproducciones totales
25,034
En SlideShare
0
De insertados
0
Número de insertados
0

Acciones

Compartido
Descargas
654
Comentarios
1
Me gusta
1

Insertados 0

No embeds

Denunciar contenido

Marcada como inapropiada Marcar como inapropiada
Marcar como inapropiada

Seleccione la razón para marcar esta presentación como inapropiada.

Cancelar
    No notes for slide

Transcript

  • 1. QUALITY ASSURANCE FRAMEWORK
  • 2. AGENDA
    • 1.What is Quality?
    • 2.What is Software Quality Assurance?
    • 3.Components Of Quality Assurance.
    • 4.Software Quality Assurance Plan.
    • 5.Quality Standards.
  • 3. What is Quality?
    • 1.Accroding to computer literature Quality means “Meeting Requirement”.
    • 2.The product has something that other similar products do not that adds value. (Product based Definition).
  • 4. Software Quality Assurace
    • Systematic activities providing evidence of the fitness for use of the total software product.
    • It is achieved through the use of established guidelines for quality control to ensure integrity and prolonged life of software.
    • It is a planned effort to ensure that a software product fulfils criteria and has additional attributes specific to the product.
  • 5.
    • 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.
    • 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.
    Software Quality Assurace
  • 6. Components of Quality Assurance
  • 7. Software Testing
    • Software testing is a popular risk management strategy.It is used to verify that functional requirements were met.
    • The major purpose of verification and validation activities is to ensure that software design, code, and documentation meet all the requirements imposed on them.
  • 8. Quality Control
    • 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.
    • 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
  • 9. Software Configuration Management.
    • It is concerned with the labeling, tracking and controlling changes in the software elements of a system.
    • 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.
  • 10. Elements of software configuration management.
  • 11. Component Identification
    • A basic software configuration management activity is to identify the Software components that make up deliverable at each point of development.
    • In order to mange the development process one must establish methods and name the component standards.
  • 12. Version control
    • Software is frequently changed as it evolves through a succession of temporary states called versions.
    • A software configuration management
    • facility for controlling versions is a software configuration management repository or library.
  • 13. Configuration Building
    • 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.
    • Software configuration management uses different approaches for selecting versions.The simplest method is to maintain all the component verisons.
  • 14. Change control
    • Software Change control is the process by which a modification to a software component is proposed.
    • 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.
  • 15. Software Quality Assurance Plan
    • Software quality assurance plan is an outline of quality measures to ensure quality levels within a software development effort.
    • The plan provides the framework and guidelines for development of understandable and maintainable code.
  • 16. Step to develop and implement a Software quality Assurance Plan
    • Step 1. Document the plan.
    • Step 2.Obtain Management Acceptance.
    • Step 3.Obtain development acceptance.
    • Step 4.Plan for implementation of the SQA Plan.
    • Step 5.Execute the SQA Plan.
  • 17. Quality Standards.
    • ISO9000
    • CMM( Capability Maturity Model)
    • PCMM(People Capability Maturity Model)
    • CMMI