6.1 Benefits
It’s an umbrella term that refers to many different methods and processes for testing software and ensuring quality. QA is your best friend when it comes to delivering great software.
- Save You Money
- Prevents catastrophic corporate emergencies
- Inspires client confidence
- Maintains great user experience
- Brings in more profit
- Boosts customer satisfaction
- Promotes organization, productivity, and efficiency
6.2 Roles
An SQA acts as an advisory and monitoring group to aid Project Teams, Acceptance Test Teams, and SQA Teams in providing proper SQU at weDevs.
- The Project Team consists of the person or persons responsible for the project activities. It is responsible for delivering the final system and keeping track of all the associated documentation which was created during the project’s life cycle.
- The Acceptance Test Team deals with the Acceptance Test Plan. They are responsible for its creation, its execution, and the resulting documentation.
- The SQA Team is concerned with the activities which deal with software quality, assurance and the associated documentation which is created.
Software gets tested for ease of use, how it handles bad data, what happens when the power goes down and how well it performs when thousands or millions use it at the same time. Throughout this phase of development, test engineers try to break the programs in any way possible then report their findings back to the development team.
6.3 Strategy
An SQA strategy consists of a basic set of procedures and activities designed to emphasize the quality of software at weDevs.
Figure 1 shows the minimum set of eight elements necessary to define the project and SQA activities and to provide for defect analysis as a means of continuous quality improvements.
Figure 1: Software Quality Strategy
6.4 Management Support
Management plays an important part in the level of success that an SQA Team can achieve on a project. Effective SQA requires effective management. Management supports SQA by
- Supporting the consistent use of SQA principles by all involved
- Understanding software engineering and SQA methods
- Communicating well-defined requirements to SQA Team members in order to achieve quality
- Realizing the level of Commitment required for SQA to work
6.5 Software Metrics
Software metrics is the process of measuring software quality. The intent is to show the correlation between software engineering methods and improved software quality. The long-term goal is to see how different SQA procedures and structured development methods affect the overall quality that can be achieved. By collecting metrics data, improvements in quality can be measured. Such quality metrics are important because it is difficult to manage and improve what is not measured.