References of Change_Impact

@InProceedings{	  abbattista.lanubile.ea:experiment,
  author	= { F. Abbattista and F. Lanubile and G. Mastelloni and G.
		  Visaggio },
  title		= { An Experiment on the Effect of Design Recording on Impact
		  Analysis },
  booktitle	= { Proceedings of the International Conference on Software
		  Maintenance (ICSM~'94), {\rm (Victoria, B.C.; Sept. 19-23,
		  1994)}},
  year		= { September 1994 },
  editor	= { Hausi A. M\"{u}ller and Mari Georges },
  pages		= { 253-259 },
  abstract	= { },
  class		= {Alteration, Change_Impact }
}

@TechReport{	  al-zoubi.prakash:software,
  author	= {Al-Zoubi, R. and Prakash, A.},
  title		= {Software Change Analysis via Attributed Dependency
		  Graphs},
  year		= {1991},
  month		= {May},
  number	= {CSE-TR-95-91},
  institution	= {Department of EECS, University of Michigan},
  class		= {Alteration, Change_Impact,Software_Reverse_Engineering,
		  Reverse_Design, Fundamental_Methods_in_Reverse_Design,
		  Static_Analysis }
}

@PhDThesis{	  al-zoubi:attributed,
  author	= {Ratib H. Al-Zoubi},
  title		= {Attributed Graph-Based Representations for Software View
		  Generation and Impact-of-Change Analysis},
  school	= {The University of Michigan},
  year		= {1992},
  abstract	= {Great ref. on change analysis; mostly PITS. Good related
		  work info. Tool is called SCAN.},
  class		= {Alteration, Change_Impact,Software_Reverse_Engineering,
		  Reverse_Design, Fundamental_Methods_in_Reverse_Design,
		  Software_Reverse_Engineering,
		  Intermediate_Representations_of_Source_Code, Using_graphs}
}

@InProceedings{	  arnold.bohner:impact,
  author	= {Robert S. Arnold and Shawn A. Bohner},
  title		= {Impact Analysis - Towards a Framework for Comparison},
  booktitle	= {Proceedings of the  International Conference on Software
		  Maintenance ~1993},
  year		= {1993},
  publisher	= {IEEE Computer Society Press},
  month		= sep,
  pages		= {292-301},
  abstract	= {The term ``impact analysis'' is used with many meanings.
		  We define a three-part framework for characterizing and
		  comparing diverse impact analysis approaches. The parts
		  correspond to how an appraoch is used to accomplish impact
		  analysis, how an approach does impact analysis internally,
		  and the effectiveness of the impact analysis approach. To
		  illustrate the frameworks's application, we classify five
		  impact analysis approaches according to it.},
  class		= {Alteration, Change_Impact}
}

@InProceedings{	  avellis:case,
  author	= {Giovanna Avellis},
  title		= {{CASE} Support for Software Evolution: A Dependency
		  Approach to Control the Change Process},
  booktitle	= {{CASE'92}: Proceedings of the fifth international workshop
		  on computer-aided software engineering, {\rm (Montr\'{e}al,
		  Qu\'ebec; July 6-10, 1992)}},
  year		= {July 1992},
  pages		= {62-73},
  publisher	= {IEEE Computer Society Press (Order Number 2960)},
  abstract	= {},
  class		= {Alteration, Change_Impact }
}

@InProceedings{	  kung.gao.ea:change,
  key		= {Kung et. al, 1994},
  author	= {D. Kung and J. Gao and P. Hsia and F. Wen and Y. Toyoshima
		  and C. Chen},
  title		= {Change Impact Identification in Object Oriented Software
		  Maintenance},
  pages		= {202-211},
  booktitle	= {Proceedings of the  International Conference on Software
		  Maintenance ~1994},
  year		= {1994},
  publisher	= {IEEE Computer Society Press},
  month		= sep,
  abstract	= {In the object-oriented (OO) paradigm, new features (such
		  as encapsulation, aggregation, inheritance, polymorphism
		  and dynamic binding) introduce new problems in software
		  testing and maintenance. One of them is the difficulty of
		  identifying the affected components (such as classes) when
		  changes are made in object-oriented class libraries or
		  programs. This paper discusses the types of code changes in
		  an object-oriented class library, and provides an automated
		  solution to identify different kinds of code changes and
		  their impact. In addition, an OO software maintenance
		  environment that implements the research result is
		  described. Our experience with the environment prototype
		  shows promising results.},
  class		= {Alteration, Change_Impact}
}

@InProceedings{	  loyall.mathisen:using,
  author	= {Joseph P. Loyall and Susan A. Mathisen},
  title		= {Using Dependence Analysis to Support the Software
		  Maintenance Process},
  pages		= {282-291},
  booktitle	= {Proceedings of the  International Conference on Software
		  Maintenance ~1993},
  year		= {1993},
  publisher	= {IEEE Computer Society Press},
  month		= sep,
  abstract	= {Dependence analysis is useful for software maintenance
		  because it indicates the possible effects of a software
		  modification on the rest of a program. This helps the
		  software maintainer evaluate the appropirateness of a
		  software modification, drive regression testing, and
		  determine the vulnerabiltiy of critical sections of code.
		  This paper presents a definition of interprocedural
		  dependence analysis and its implementation in a prototype
		  tool that supports software maintenance.},
  class		= {Alteration, Change_Impact}
}