1 / 40

Software Quality Engineering

Software Quality Engineering. Testing: Fault Detection. BG # 1. Testing: Fault Detection Testing is core QA activity which aim to identify fault areas which are to be fixed. Testing is conducted at different levels in context of defect reduction. Software Quality Assurance. BG # 1.

bpatterson
Download Presentation

Software Quality Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Quality Engineering Testing: Fault Detection

  2. BG # 1 Testing: Fault Detection Testing is core QA activity which aim to identify fault areas which are to be fixed. Testing is conducted at different levels in context of defect reduction Software Quality Assurance

  3. BG # 1 Testing: Fault Detection Formally testing starts after code is handed over to QA Department. Different sub-testing activities are performed to ensure stability till post-release level Software Quality Assurance

  4. Software Quality Engineering Defect Containment

  5. BG # 1 Defect Containment Despite defect prevention and reduction strategies existence of defects are still risky in high impact applications. Real-time applications like medical, transportations, nuclear have high risk due to defects Software Quality Assurance

  6. BG # 1 Defect Containment Few faults are generated under rare conditions at real-time. Impossible to test exhaustively all the conditions. Strategy is to break fault-failure relation to contain the damage Software Quality Assurance

  7. Software Quality Engineering Software Fault Tolerance

  8. BG # 1 Software Fault Tolerance Traditional Hardware system require high level of reliability and availability. In case of these systems backups are used for reduced functionality in case of failure Software Quality Assurance

  9. BG # 1 Software Fault Tolerance N-Version Programming(NVP) is running multiple version of same specs in parallel. If there is fault in one version then dynamically fault-less version is switched. Software Quality Assurance

  10. BG # 1 Software Fault Tolerance N-Version ensure faults in limited versions does not compromise global versions. Faults are not identified hence not fixed which is contradiction to defect prevention. Software Quality Assurance

  11. Software Quality Engineering Safety Assurance and Fault Containment

  12. BG # 1 Safety Assurance and Fault Containment For Safety critical system fault in even low – priority areas with consequences to be avoided. Hazard Reduction technique include automatic locking of some portion of software Software Quality Assurance

  13. BG # 1 Safety Assurance and Fault Containment Damage control through escape routes is achieved to ensure minimal global damage Software Quality Assurance

  14. Software Quality Engineering Defect Resolution

  15. BG # 1 Defect Resolution Defect Resolution is a process that keep record of reported defect till Testing Department close it In case defect is not fixed then all the parties agree to it. Software Quality Assurance and Defect

  16. Software Quality Engineering Defect LifeCycle

  17. BG # 1 Defect LifeCycle It includes steps which are to be done from defect reported till defect resolution Reported defects should be fixed, re-verified and closed formally Software Quality Assurance and Defect

  18. BG # 1 Defect LifeCycle Defects are usually tracked by assigning different status in tools Status like Assigned, In-Progress, Fixed, NotAFix, Pending, Not Reproduceable, closed are usually used to track defect Software Quality Assurance and Defect

  19. Software Quality Engineering StakeHolders in Defect LifeCycle

  20. BG # 1 Stakeholders Defect LifeCycle Depending on defect resolution decision all the stakeholders must agree. If Defect is decided not to be fixed for current release then all stakeholder must agree Software Quality Assurance and Defect

  21. BG # 1 Stakeholders Defect LifeCycle Usually Minor or cosmetic defects are deferred to future releases At times reported defect is re-classified as not a bug , it has to be done with consensus Software Quality Assurance and Defect

  22. Software Quality Engineering Defect Logging

  23. BG # 1 Defect Logging It is first step to report the discovered defect. Defect Logging ensure that record with details is provided for the Developer to fix the defect. Software Quality Assurance and Defect

  24. Software Quality Engineering Defect Tracking

  25. BG # 1 Defect Tracking It ensure the monitoring of different stages of defect resolution Usually it maintained through templates or tools to ensure global status Software Quality Assurance and Defect

  26. Software Quality Engineering Example of Defect Logging

  27. BG # 1 Example of Defect Logging Defect Logging Software Quality Assurance and Defect

  28. BG # 1 Example of Defect Tracking Usually Defect Logging files are shared among Team members to collaborate Software Quality Assurance and Defect

  29. Software Quality Engineering Example of Defect Tracking

  30. BG # 1 Example of Defect Tracking Defect Logging Software Quality Assurance and Defect

  31. BG # 1 Example of Defect Tracking Usually defects are completed with consensus if there is conflict Software Quality Assurance and Defect

  32. Software Quality Engineering Project Based Defects

  33. BG # 1 Product Based Defects Product Based defects and fixing of defects is on-going activity till Product is deployed at even one-site. Support activities has to be there to ensure hot-fixes, to maintain defects backlogs Software Quality Assurance and Defect

  34. Software Quality Engineering Project Based Defects

  35. BG # 1 Project Based Defects Project Based defects are usually reported, analyse, fixed and closed once during Project life-cycle Service Level Agreement (SLA) is signed for support purposes Software Quality Assurance and Defect

  36. Software Quality Engineering Product Evaluation

  37. BG # 1 Product Evaluation Product evaluation include steps to evaluate the stability , reliability and market value of the Product. Defect backlog, features, reliability of features, compatibility, support of the features are key component Software Quality Assurance and Defect

  38. Software Quality Engineering Software Maintaince and Defect Handling

  39. BG # 1 Software Maintaince and Defect Handling Maintaince usually include scope of support to be provided with terms and condition. Product and Project based defect handling is different. Software Quality Assurance and Defect

  40. BG # 1 Software Maintaince and Defect Handling Level – I: Customer Support Team Level – II: QA Team Level – III: To include development team Software Quality Assurance and Defect

More Related