The tendency to software development cycle reduction makes developers look for alternative ways to deliver successful projects promptly. Introduction of quality assurance (QA) analysis into the set of QA activities performed throughout the development process allows to find the balance between quality requirements and time pressure.
We live in a greatly computerized society and our wide opportunities constantly cause new needs and requirements that in their turn give rise to new software which provides us with opportunities of the next level. It is an exclusive circle and its name is progress. We can’t stop it or slow it down, we can only adapt to it and try to foresee the next turn. Thinking of some software today I naturally expect it to surpass my expectation of tomorrow.
As a result of this process software development engineers all over the world observe certain changes in the development environment. These changes include software development lifecycle shortening, extreme changeability of requirements, appearance of ready-made components and many others.
We live in a greatly computerized society and our wide opportunities constantly cause new needs and requirements that in their turn give rise to new software which provides us with opportunities of the next level. It is an exclusive circle and its name is progress. We can’t stop it or slow it down, we can only adapt to it and try to foresee the next turn. Thinking of some software today I naturally expect it to surpass my expectation of tomorrow.
As a result of this process software development engineers all over the world observe certain changes in the development environment. These changes include software development lifecycle shortening, extreme changeability of requirements, appearance of ready-made components and many others.
What QA Analysis gives us?
Time-saving and quality considerations force us to look for ways of software development process optimization and efficiency increase. It can be achieved by introduction of QA analysis in addition to other quality assurance measures included into the software development lifecycle, e.g. testing and code review. The main advantage of QA analysis introduction is the differentiated approach to project bugs and mistakes. Testing reveals only those imperfections that occur in the project after the development stage.
The scope of work a tester carries out consists in system efficiency check on the basis of analysis of separate use cases described in the software requirements specification (SRS). It often ignores sequences of use cases and therefore leaves behind undiscovered bugs and failures. Besides, agile software development gives no way for detailed SRS and therefore deprives the testing stage of minuteness and efficiency. Testing also turns out to be insufficient when it comes to complex system development that requires differentiated approach to behaviour variants checking. So, it seems obvious that testing alone doesn’t satisfy the quality requirements for agile software development projects and very complex systems, neglecting comprehensive system behaviour though ensuring its conformity to the SRS.
The scope of work a tester carries out consists in system efficiency check on the basis of analysis of separate use cases described in the software requirements specification (SRS). It often ignores sequences of use cases and therefore leaves behind undiscovered bugs and failures. Besides, agile software development gives no way for detailed SRS and therefore deprives the testing stage of minuteness and efficiency. Testing also turns out to be insufficient when it comes to complex system development that requires differentiated approach to behaviour variants checking. So, it seems obvious that testing alone doesn’t satisfy the quality requirements for agile software development projects and very complex systems, neglecting comprehensive system behaviour though ensuring its conformity to the SRS.
The first fiddle in QA
This is the perfect time for a Quality Assurance (QA) analyst to appear on the stage. QA analysis implies more creative work, if you allow me to say so. Good understanding of user’s implicit expectations, project planning, budgeting and other project aspects is required for comprehensive quality assurance. It is a QA analyst who can make sure that the project fits the customer’s business needs to a ‘T’. To me it is evident that effective software can be developed successfully only if the project passes through QA analysis.
We at Gersis Software pay great attention to Quality Assurance analysis in all the projects we undertake in order to ensure their ultimate efficiency and functionality provided the customer accepts the proposal. I hope that the knowledge we share here with you will help someone avoid the mistakes that allowed us to gain this experience.
PS: Learn wisdom by the follies of others!
We at Gersis Software pay great attention to Quality Assurance analysis in all the projects we undertake in order to ensure their ultimate efficiency and functionality provided the customer accepts the proposal. I hope that the knowledge we share here with you will help someone avoid the mistakes that allowed us to gain this experience.
PS: Learn wisdom by the follies of others!
.jpg) |
Posted by Valeri Kireitchik, CEO |
| Bookmark or share: |          |
