| Impact Analysis in Testing |
|
|
|
| Thursday, 13 October 2011 13:11 |
|
In this article, we will tell you our own way of Impact Analysis introduction and work with it. Why did we decide to introduce Impact Analysis into our work? What practical benefit from this innovation have we got and are getting today? You will get answers to these and many other questions concerning this topic while reading this material.
Written by: Specialists of Network QA Team Contents Introduction 1. Impact Analysis: what is it? 1.1 Basic principles 1.2 Impact Analysis for developer 1.3 Impact Analysis for tester 2. Our experience with Impact Analysis 2.1 Life before Impact Analysis 2.2 Impact analysis in our projects 2.3 Features of the innovation introduction Impact Analysis: our benefit Conclusion
IntroductionWe devise and implement different features, additional means that can be useful for a user. We work with the constantly changing acceptance criteria: we develop something, then change it, add something, remake something, etc. In such continuous process of development, it is possible to face an unpleasant situation when it is difficult to track consequences of changes and modifications being introduced: to estimate what parts of the program may be affected and how significantly they may be affected. As a result, testing is performed accordingly to the best practices, but some part of the product, some module or feature are looked over or checked not deeply enough, just because of the Impact Analysis information absence. Information presented in this article will be useful for those specialists who need to analyze, what product items made changes can influence on; i.e. for everyone who is related to IT product development. We will touch upon such questions:
It is safe to say that after reading this article you can figure out how to make your product better easily. 1. Impact Analysis: what is it?1.1 Basic principlesFirst of all, let’s clarify what Impact Analysis is, who, when and why uses it. Briefly, the Impact Analysis is used to define all the risks associated with any kind of changes in a product being tested. There exist several Impact Analysis definitions that accent different aspects. I think we should consider each of these definitions because this will help you to make a decision and define to which of these definitions your personal Impact Analysis will be closer. The first definition says that Impact Analysis means detection of potential consequences of changes or things that must be remade together with the introduced changes. Here, Impact Analysis is considered in terms of changes in the product. According to the second definition, Impact Analysis is an estimation of the number of risks associated with the product changes, including the estimation of influence on resources, work and timetable. This definition takes into consideration changes consequences in terms of the whole development process. If we consult with ISTQB glossary, Impact Analysis is an estimation of changes on different levels of development documentation, testing documentation and components for introduction of these changes and registration them in corresponding requests. Here, our attention is drawn to the fact that changes should be taken into consideration on all documentation levels: from the code to requests. Knowing what Impact Analysis is, let’s clarify when Impact Analysis is used. It may be useful in such cases:
Now, let’s answer the question: -Why? The complete article text is available only for the registered users. Please Log In or Register. |






