Quality management


Published on

Topics Covered:
1. Quality assurance and standards.
2. Quality planning.
3. Quality control.

Published in: Technology, Business
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Quality management

  1. 1. Managing the quality of software quality and products uday_saikia@ymail.com
  2. 2.  To introduce the quality management process and key quality management activities.  To explain the role of standards in quality management.  To explain the role of a software metrics , predictor metrics and control metrics.  To explain how measurement may be used in assessing software quality.
  3. 3.  Quality assurance and standards.  Quality planning.  Quality control.
  4. 4.  Concerned with ensuring that the required level of quality is achieved in a software product.  Involves defining appropriate quality standards and procedures and ensuring that these are followed.  Should aim to develop a ‘quality culture’ where quality is seen as everyone’s responsibility.
  5. 5.  Quality simplistically, means that a product should meet its specification.  This is problematical for software systems…. Tension between customer quality requirements (efficiency, reliability, etc.) and developer quality requirements(maintainability, reusability etc.). Some quality requirements are difficult to specify in an unambiguous way.  Software specification are usually incomplete and often inconsistent.
  6. 6.  We cannot wait for specification to improve before paying attention to quality management.  Must put procedures to place to improve quality in spite of imperfect specifications.  Quality management is therefore not just concerned with reducing defects but also with other product qualities.
  7. 7.  Quality assurance Establish organizational procedures and standards for quality.  Quality planning Select applicable procedures and standards for a particular project and modified these as required.  Quality control Ensure that procedures and standards are followed by the software development team  Quality management should be separate fro project management to ensure independence.
  8. 8.  International set of standards for quality management.  Applicable to a range of organization from manufacturing to service industries.  ISO 9001 is a generic model of the quality process must be intended for each organization
  9. 9. Management responsibility Quality system Control of non-conforming products Design control Handling, storage, packaging and delivery Purchasing Purchase-supplied products Product identification and traceability Process control Inspection and testing Inspection and test equipment `Inspection and test status Contract review Corrective action Document control Quality records Internal quality audits Training Servicing Statistical technique
  10. 10.  Quality standards and procedures should be documented in an organizational quality manual.  External body may certify that an organization’s quality manual conforms to ISO 9000 certified.
  11. 11.  Standards are the key to effective quality management.  They may be international, national , organizational or project standards.  Product standards define characteristics that all components should exhibit e.g. a common programming style.  Process standards define how the software process should be enacted.
  12. 12.  Encapsulation of best practice-avoid repetition of past mistakes.  Framework for quality assurance process – it involves checking standard compliance.  Provide continuity – new staff can understand the organization by understand the standards applied.
  13. 13. Product standards Process standards Design review from  Document naming standards  Procedure header format  Project plan format  Change request from Design review conduct Submission of document Version release process Change control process Test recording process
  14. 14.  A quality plan sets out the desired product qualities and how these are assessed and define the most significant quality attributes.  It should define the quality assessment process.  It should set out which organizational standards should be applied and if necessary, define new standards.
  15. 15.  Product introduction.  Product plans.  Process description.  Quality goals.  Risks and risk management.  Quality plans should be short, succinct documents.  if they are too long , no-one will read them.
  16. 16. REQUIREMENT ANALYSIS R DESIGN R CODING R UT IT/ST AT Development process Defect Injection Defect Removal R  Removal. UT Unit testing. IT Integration testing. ST  System testing. AT  AcceptanceTesting
  17. 17.  QC activities for defect removal includes  Requirement Reviews Design Reviews  Code Reviews  UnitTesting  IntegrationTesting  SystemTesting  AcceptanceTesting
  18. 18. Safety Understandability Portability Security Testability Usability Reliability Adaptability Reusability Resilience Modularity Efficiency Robustness Complexity Learn ability
  19. 19.  Checking the software development process to ensure that procedures and standards are being followed.  Two approaches to quality control Quality reviews Automated software assessment and measurement.
  20. 20.  The principle method of validating the quality of a process or a product.  Group examined part or all of a process or system and its documentation to find potential problems.  There are different types of review with different objectives  Inspection for defect removal(product) Reviews for progress assessment(product and process) Quality reviews(product and standards)
  21. 21.  Design or program inspections.  Progress reviews.  Quality reviews.
  22. 22.  Quality functions-They are part of the general quality management process.  Project management function-They provide information's for project managers.  Training and communication function – Product knowkwdge is passed between development team members.
  23. 23.  Comments made during the review should be classified. No action. No change to the software or documentation is required Refer for repair. Designer or programmer should correct an identified fault. Reconsider overall design.The problem identified in the review impacts other parts of the design. Some overall judgment must be made about the most cost effective way of solving problem.
  24. 24.  Software quality management is concerned with ensuring that software meets its required standards.  Software standards are an encapsulation of best practice.  Reviews are the most widely used approach for assessing software quality.  Quality plans revolves around testing and reviews.
  25. 25.  1.An integratedApproach to Software Engineering – Pankaj Jalote.  2. Software Engineering – Rajiv Mall.  3. wikipedia.org and various websites.