» » Software Change Impact Analysis
Download Software Change Impact Analysis epub book
ISBN:0818673842
Author: Robert Arnold,Shawn Bohner
ISBN13: 978-0818673849
Title: Software Change Impact Analysis
Format: docx mobi doc rtf
ePUB size: 1308 kb
FB2 size: 1462 kb
DJVU size: 1163 kb
Language: English
Category: Programming
Publisher: Wiley-IEEE Computer Society Pr; 1 edition (June 30, 1996)
Pages: 392

Software Change Impact Analysis by Robert Arnold,Shawn Bohner



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"

As software systems become increasingly large and complex, the needincreases to predict and control the effects of software changes.This book captures the latest information on the science and art ofdetermining what software parts affect each other. It is a handyone-volume source of useful information about software changeimpact analysis techniques and technical results. The book framesthe field, focuses attention, and tempers expectations.The book provides a battery of ideas for doing impact analysisbetter. The reader will gain a healthy respect for the strengthsand limitations of impact analysis technology and a solidbackground that will provide valuable for years to come. The bookidentifies key impact analysis definitions and themes andillustrates those themes through a collection of representativepapers. It includes reports on software source code dependencyanalysis and software traceability analysis and proposes howresults from both areas can more effectively support impactanalysis in software engineering repositories. It also describeswhy impact representation and determination techniques are at theheart of both source dependency analysis and traceability analysis.The papers provide fundamental information of enduring value andwere selected by how well they illustrate the important themes andhow well they equip the reader with a solid understanding fortackling impact analysis problems.
Reviews: 3
post_name
It's a good start point. Don't expect to have a very well organized body of knowledge. It is just a selection of some important piece of work. Most of the papers are available in IEEE and ACM digital libraries.
Anararius
This collection of papers on software change impact analysis covers both practice and theory. The book starts with an introduction to change impact analysis. This intro covers terms, theories and practices that have emerged and are accepted among most researchers and practitioners, and provides a basic discussion of traceability and impact analysis.
Chapter 1 is titled Nature of Impact Analysis and contains A Process Model for Software Maintenance, Impact Analysis-Towards A Framework for Comparison, and The Year 2000 Problem: Impact, Strategies, and Tools. Although the last paper is obviously out of date, some of the techniques are worth examining, especially since a good amount of the Y2K problem required impact and risk analysis.
State of the Practice is the topic of chapter 2, and contains the following papers: An Analysis of the Requirements Traceability Problem, Software Change Impact Analysis for Design Evolution and Configuration Management Survey. These three papers are a combination of practice and theory.
The material in Chapter 3, Automated Support for Impact Analysis, is spotty. Some is out of date in my opinion, while other papers are as fresh today as when the book was published. Papers in this chapter are: The Integrated CASE Manifesto, A Practical Software Maintenance Environment, Intelligent Assistance for Software Development and Maintenance and Maintenance Support for Object-Oriented Programs (the last is excellent!). Chapter 4 contains the most practical material in the collection. The topic title is Dependency-Analysis Approaches, and the papers are: Using Dependence Analysis to Support the Software Maintenance Process, Interprocedural Slicing Using Dependence Graphs, Data Dependency Graphs for Ada Programs, Data Flow Analysis and its Application to Software Maintenance and Change Impact Identification in Object Oriented Software Maintenance.
Papers in Chapter 5 (Traceability Approaches) are also mostly practical, but many are out of date or contain information that was a good idea at the time, but seem quaint by today's standards. Paper topics are: A Hypertext System to Manage Software Life-Cycle Documents (very much ahead of its time, but woefully out of date now), A Software Documentation Support Environment-Its Definition, Traceability Based on Design Decisions (this is *must reading* in my opinion) and A Process for Consolidating and Reusing Design Knowledge. Chapter 6's papers address Impact Representation. While many were written a decade ago all of them are interesting and include ideas that are as valid today. Topics are: The Prism Model of Changes, A Unified Interprocedural Program Representation for a Maintenance Environment, A Formal Model of Program Dependencies and Its Implications for Software Testing, Debugging, and Maintenance and A Graph Model for Software Evolution.
Chapter 7 is devoted to Impact-Determination Techniques and contains interesting papers that are more theoretical than practical in my opinion. Topics are: An Early Impact Analysis Technique for Software Maintenance, Using Program Slicing in Software Maintenance, Efficient Algorithms for the Instantiated Transitive Closure Queries, and Approximate Reasoning About the Semantic Effects of Program Changes. Chapter 8 is a synopsis of material in the preceding chapters, with and commentary and observations about impact analysis as a discipline.
Overall, this book represents a substantial cross section of the body of knowledge devoted to software change impact analysis. Some strengths include the fact that this collection of papers makes the body of knowledge available in one book, and the focus of the papers on software engineering aspects of change and maintenance, and how to manage impact to complex applications. A key weakness is that some of the papers are over 10 years old. However, despite the age of some of the papers many are surprisingly applicable to maintenance challenges faced by practitioners today.
Na
The book had arrived very quickly and in a great condition. I must say that i am very pleased with this puirchase.

Thanks,
EladSoftware Change Impact Analysis (Practitioners)