1. Software Quality Engineering
Testing: Fault Detection

2. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

3. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

4. Software Quality Engineering
Defect Containment

5. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

6. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

7. Software Quality Engineering
Software Fault Tolerance

8. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

9. Software Quality Assurance
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.
Defect Prevention: Clarifying human misconceptions or ambiguities

10. Software Quality Assurance
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.
Defect Prevention: Clarifying human misconceptions or ambiguities

11. Software Quality Engineering
Safety Assurance and Fault Containment

12. Software Quality Assurance
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
Defect Prevention: Clarifying human misconceptions or ambiguities

13. Software Quality Assurance
BG # 1
Safety Assurance and Fault Containment
Damage control through escape routes is achieved to ensure minimal global damage
Defect Prevention: Clarifying human misconceptions or ambiguities

14. Software Quality Engineering
Defect Resolution

15. Software Quality Assurance and Defect
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.
Pg. 111 The Unschooled Mind

16. Software Quality Engineering
Defect LifeCycle

17. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

18. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

19. Software Quality Engineering
StakeHolders in Defect LifeCycle

20. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

21. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

22. Software Quality Engineering
Defect Logging

23. Software Quality Assurance and Defect
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.
Pg. 111 The Unschooled Mind

24. Software Quality Engineering
Defect Tracking

25. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

26. Software Quality Engineering
Example of Defect Logging

27. Software Quality Assurance and Defect
BG # 1
Example of Defect Logging
Defect Logging
Pg. 111 The Unschooled Mind

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

29. Software Quality Engineering
Example of Defect Tracking

30. Software Quality Assurance and Defect
BG # 1
Example of Defect Tracking
Defect Logging
Pg. 111 The Unschooled Mind

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

32. Software Quality Engineering
Project Based Defects

33. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

34. Software Quality Engineering
Project Based Defects

35. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

36. Software Quality Engineering
Product Evaluation

37. Software Quality Assurance and Defect
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
Pg. 111 The Unschooled Mind

38. Software Quality Engineering
Software Maintaince and Defect Handling

39. Software Quality Assurance and Defect
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.
Pg. 111 The Unschooled Mind

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