Within the growing complexity if IT-infrastructure due to the number of integrated IT-systems – there is naturally increased demand on software testing service. The increased number & complexity of tests, and this, in turn, slows down the release of products into exploitation.
On the other hand, almost all top software testing companies seek to shorten the time of software products release. The elongation of SDLC due to increasing volumes of testing is perceived negatively. Sometimes it turns into a partial or even complete abandonment of testing and translated into a marked deterioration in the quality of IT testing services.
Disrespect Towards Testing Can Cause:
- quality deviation of the product under development (the source of all other ensuring consequences);
- the constant growth of indirect costs on quality assurance services because of the emergence of software defects in industrial exploitation;
- the loss of customers who don’t wish to use a poor-quality product.
Now one can see the importance of early testing introduction, at least on the phase of requirements analysis. It is also worth noting that there are two types of costs: indirect and direct.
Direct costs – means that company spends to support the product in good condition, i.e., essentially, on the remuneration of everyone involved in the project, including QA.
Indirect costs – are the costs related to product quality, users’ habituation to a new product.
If the process of product testing started from the beginning of the project development, the direct costs on support of the product quality would be approximately at the same level and only grow along with the growth of the project, and indirect costs are minimized. In the case when testing is not conducted at all, the price of direct cost for testing is absent and indirect costs from poor software grow infinitely.
In order to reduce the growth of indirect costs, it is necessary to introduce testing as early as possible, at least until the release, preferably at the beginning of product requirements analysis and before preparation of design documentation.
Based on the above reasons, it can be concluded that the most painless and least expensive way to release a product in the case of early introduction of testing namely at the stage of forming requirements or during project development.
NB! It’s not worth saving on testing, the absence of which leads to the users being not satisfied with a product, uncontrolled spendings and may result in loss of significant funds.
Comments are closed.
