Impact analysis-Towards a framework for comparison

Arnold, Robert S.; Bohner, Shawn A.

doi:10.1109/icsm.1993.366933

Cited by 165 publications

(136 citation statements)

References 6 publications

Supporting

Mentioning

133

Contrasting

Unclassified

Order By: Relevance

“…Compare Figures 18 and 19 generated by CIV with Figures 23 and 24 generated by SoftBench for the same system. Figure 23 shows approximately 1 30 th of the entire call-graph, and Figure 24 shows approximately 1 5 th of the entire class-inheritance graph. Conversely, Figure 18 shows about 90 of the entire class-inheritance and high-level call-graph view, and Figure 19 shows 100 of the detailed internal view of a single class.…”

Section: Hp Softbenchmentioning

confidence: 99%

“…Programs written in C++, however, may apply dynamic binding. The speci c method that gets executed is determined at run time, and could be any of a hierarchy 1 In 16 this person is called the visualizer, and the user is de ned as the person using the resulting visualization to understand a software system. However, in a fully automated system, such as CIV, the visualizer and the user are one in the same.…”

Section: Software Understandingmentioning

confidence: 99%

See 1 more Smart Citation

3–D Visualization of Software Structure

Staples

Bieman

1999

Advances in Computers

View full text Add to dashboard Cite

A common and frustrating problem in software engineering is the introduction of new faults as a side-e ect of software maintenance. An understanding of all of the relationships that exist between modi ed software and the rest of a system can limit the introduction of new faults. For large systems, these relationships can be numerous and subtle. The relationships can be especially complex in object-oriented systems that include inheritance and dynamic binding. Software visualization can potentially ease both impact analysis and general program understanding. Software visualization can facilitate program understanding by graphically displaying important software features. However, despite recent success in developing useful and intuitive graphical representations for certain aspects of software, current software visualization systems are limited by their lack o f scalability | the ability to visualize both small and large-scale software entities. This paper demonstrates that three-dimensional 3-D graphics and a hierarchy o f o v erlapping views can increase the scalability of software visualization. The hierarchy provides detailed information without sacri cing the big picture". Overlapping is used to provide context between high and low-level views. A prototype system, Change Impact Viewer CIV , tests these visualization mechanisms. CIV highlights areas of a system that can potentially be a ected by a change to a selected function. The mechanisms, as implemented in CIV, show improvements in scalability o v er those provided by other systems, without decreasing usefulness or intuitiveness.

show abstract

Section: Hp Softbenchmentioning

confidence: 99%

Section: Software Understandingmentioning

confidence: 99%

3–D Visualization of Software Structure

Staples

Bieman

1999

Advances in Computers

View full text Add to dashboard Cite

show abstract

“…The presence of at least a difference between c ∈ S j−1 and c ∈ S j indicates that the class c -and thus the pattern -has been changed in correspondence of the snapshot S j . The analysis is automatically performed by using a fact extractor based on the JavaCC parser generator 1 and a Perl script that compares facts (e.g., for each class the list of methods, attributes, associations, parents, descendants) of the two versions of c to identify the above mentioned differences.…”

Section: 3mentioning

confidence: 99%

Relating the Evolution of Design Patterns and Crosscutting Concerns

Cerulo¹,

Penta²

2007

Seventh IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2007)

View full text Add to dashboard Cite

show abstract

“…Change impact analysis techniques [1] estimate the potential effects of software changes. The results of an impact analysis can be used by other program analysis techniques, e.g., regression testing, to determine which parts of a program to re-analyze and which parts can safely be ignored because they are not impacted by the changes.…”

Section: Introductionmentioning

confidence: 99%

A change impact analysis to characterize evolving program behaviors

Rungta

Person

Branchaud

2012

2012 28th IEEE International Conference on Software Maintenance (ICSM)

View full text Add to dashboard Cite

Abstract-Change impact analysis techniques estimate the potential effects of changes made to software. Directed Incremental Symbolic Execution (DiSE) is an intraprocedural technique for characterizing the impact of software changes on program behaviors. DiSE first estimates the impact of the changes on the source code using program slicing techniques, and then uses the impact sets to guide symbolic execution to generate path conditions that characterize impacted program behaviors. DiSE, however, cannot reason about the flow of impact between methods and will fail to generate path conditions for certain impacted program behaviors. In this work, we present iDiSE, an extension to DiSE that performs an interprocedural analysis. iDiSE combines static and dynamic calling context information to efficiently generate impacted program behaviors across calling contexts. Information about impacted program behaviors is useful for testing, verification, and debugging of evolving programs. We present a case-study of our implementation of the iDiSE algorithm to demonstrate its efficiency at computing impacted program behaviors.Traditional notions of coverage are insufficient for characterizing the testing efforts used to validate evolving program behaviors because they do not take into account the impact of changes to the code. In this work we present novel definitions of impacted coverage metrics that are useful for evaluating the testing effort required to test evolving programs. We then describe how the notions of impacted coverage can be used to configure techniques such as DiSE and iDiSE in order to support regression testing related tasks. We also discuss how DiSE and iDiSE can be configured for debugging; finding the root cause of errors introduced by changes made to the code. In our empirical evaluation we demonstrate that the configurations of DiSE and iDiSE can be used to support various software maintenance tasks.

show abstract

Impact analysis-Towards a framework for comparison

Cited by 165 publications

References 6 publications

3–D Visualization of Software Structure

3–D Visualization of Software Structure

Relating the Evolution of Design Patterns and Crosscutting Concerns

A change impact analysis to characterize evolving program behaviors

Contact Info

Product

Resources

About