|Author:||Robert Arnold,Shawn Bohner|
|Title:||Software Change Impact Analysis|
|Format:||docx mobi doc rtf|
|ePUB size:||1308 kb|
|FB2 size:||1462 kb|
|DJVU size:||1163 kb|
|Publisher:||Wiley-IEEE Computer Society Pr; 1 edition (June 30, 1996)|
Software Change Impact Analysis captures the latest information on the science and art of determining what software parts affect each other. It provides a battery of ideas for doing impact analysis better, presents a framework for the field, and focuses attention on important results. You will gain a healthy respect for the strengths and limitations of impact analysis technology and a solid background that will prove valuable for years to come. This collection of papers on software change impact analysis covers both practice and theory. The book starts with an introduction to change impact analysis.
Software Change Impact Analysis. by Robert Arnold, Shawn Bohner. ISBN 9780818673849 (978-0-8186-7384-9) Softcover, Wiley-IEEE Computer Society Pr, 1996. Find signed collectible books: 'Software Change Impact Analysis'. Founded in 1997, BookFinder
Software Change Impact Analysis. Robert Arnold, Shawn Bohner. ISBN: 978-0-818-67384-9 July 1996 Wiley-IEEE Computer Society Pr 392 Pages. The book identifies key impact analysis definitions and themes and illustrates those themes through a collection of representative papers. It includes reports on software source code dependency analysis and software traceability analysis and proposes how results from both areas can more effectively support impact analysis in software engineering repositories. It also describes why impact representation and determination techniques are at the heart of both source dependency analysis and traceability analysis. An Analysis of the Requirements Traceability Problem. Software Change Impact Analysis for Design Evolution. Configuration Management Survey. Chapter 3. Automated Support for Impact Analysis.
Authors: Arnold Robert Arnold Shawn Bohner. The book provides a battery of ideas for doing impact analysis better. The reader will gain a healthy respect for the strengths and limitations of impact analysis technology and a solid background that will provide valuable for years to come.
In 1996, American software engineers Robert S. Arnold and Shawn A. Bohner were the first to write about Impact Analysis (IA) in their book ‘Software Maintenance’. It is about identifying the potential consequences of a change within complex product development. As a result, predefined requirements can be improved.
Shawn A. Bohner and Robert S. Arnold. An introduction to software change impact analysis. IEEE Computer Society Press, 1996. James Law and Gregg Rothermel. Published 1996 by IEEE Computer Society Press in Los Alamitos, Calif. Evaluation, Computer software. Includes bibliographical references (p. 361-374).
Change impact analysis (IA) is defined by Bohner and Arnold as "identifying the potential consequences of a change, or estimating what needs to be modified to accomplish a change", and they focus on IA in terms of scoping changes within the details of a design. In contrast, Pfleeger and Atlee focus on the risks associated with changes and state that IA is: "the evaluation of the many risks associated with the change, including estimates of the effects on resources, effort, and schedule"