Averting of Software Bugs and Testing Process Improvement

Averting of Software Bugs and Testing Process Improvement
March 27 10:00 2012 Print This Article

Generally, software testing and other works connected with quality assurance refer to system errors and defects that have been penetrated into the system during a two-stage process:

  1. Observation, testing or monitoring which are used to determine the presence of the defects in the system or their consequences;
  2. Taking activities in order to find and destroy most of the defects, or to accept their presence if it is impossible to remove these errors or because of the impractical for some definite cases.

Averting of Software Bugs and Testing Process Improvement

These activities take up a significant proportion of the budget spent on the development and maintenance of software product and these costs can range from one-fourth to the half. Moreover, the longer a defect exists in the system in a latent state, the more problems it generates.

Thus, software bugs in the software applications associated with the design, specifications and requirements are very expensive and destructive because of their chain reaction. Unfortunately, most existing strategies and techniques of software testing are not efficient for such defects due to lack of information about the realization of program at the early stages of development. Other quality assurance activities can also be used to solve these problems, but they will also have the limitations.

There are two main problems with existing approaches to quality assurance:

  • Limitations and lack of the effectiveness of existing quality assurance techniques for the project references at the early stages of development.
  • The fact that a significant portion of the budget for the correction of defects is already embedded in the system.

Related Posts:

  • No Related Posts

About Article Author

view more articles
Nataliia Vasylyna

View More Articles