References of The_Pros_and_Cons_and_Risks_of_Reengineering

@Article{	  andrews:systems,
  author	= { D.C. Andrews },
  title		= { Systems Re-engineering: A Critical Perspective },
  journal	= { CASE Trends },
  year		= { July/August 1990 },
  pages		= { 15-16 },
  abstract	= { see Arnold's book },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@Article{	  arnold.frakes:software,
  author	= {Robert S. Arnold and V. B. Frakes},
  title		= {Software Reuse and Reengineering},
  journal	= {Case Trends},
  year		= {1992},
  volume	= {4},
  number	= {2},
  pages		= {44-48},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@Article{	  arnold:common,
  author	= {Robert S. Arnold},
  title		= {Common Risks of Reengineering},
  journal	= {Reverse Engineering Newsletter},
  year		= {1992},
  pages		= {Rev-1 -- Rev-2},
  month		= apr,
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@Article{	  arnold:common*1,
  author	= { R.S. Arnold },
  title		= { Common Risks of Reengineering },
  journal	= { Reverse Engineering Newsletter },
  year		= { April 1992 },
  pages		= { Rev.1-Rev.2 },
  abstract	= { },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@InProceedings{	  arnold:risks,
  author	= { R.S. Arnold },
  title		= { Risks of Reengineering },
  booktitle	= { Proceedings of the Reverse Engineering Forum, {\rm
		  (Washington University, St. Louis, Missouri)}},
  year		= { April 1991 },
  abstract	= { see Arnold's book },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@Article{	  bartholemew:charles,
  author	= { D. Bartholemew },
  title		= { Charles Schwab: Bullish on Reengineering },
  journal	= { Information Week },
  year		= { July 22, 1991 },
  pages		= { 12-13 },
  abstract	= { see Arnold's book },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@InProceedings{	  brice:existing,
  author	= { L. Brice },
  title		= { Existing Computer Applications. Maintain or Redesign: How
		  to Decide? },
  booktitle	= { Proceedings of the Computer Measurement Group },
  year		= { December 1981 },
  pages		= { 20-28 },
  abstract	= { see Arnold's book },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@Article{	  brooks-jr-:no,
  author	= {Frederick P. {Brooks Jr.}},
  title		= {No Silver Bullet: Essence and Accidents of Software
		  Engineering},
  journal	= {IEEE Computer},
  year		= {April 1987},
  volume	= {20(4)},
  pages		= {10-19},
  abstract	= {},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering }
}

@Article{	  bush:reverse,
  author	= { E. Bush },
  title		= { Reverse Engineering: What and Why },
  journal	= { American Programmer },
  volume	= { 3(10) },
  year		= { October 1990 },
  pages		= { 1-7 },
  abstract	= { see Arnold's book },
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@InProceedings{	  chikofsky:case,
  author	= {Elliot J. Chikofsky},
  title		= {{CASE} and Reengineering: From Archeology to Software
		  Perestroika},
  booktitle	= {Proceedings of the 12th  International Conference on
		  Software Engineering },
  pages		= {122},
  month		= mar,
  year		= {1990},
  abstract	= {CASE (computer-aided software engineering), reverse
		  engineering, and reengineering together form a coherent set
		  of strategies for software organizations to get a handle on
		  and reclaim their existing software assets. Each of the
		  three supports and depends upon the others for long-term
		  success. It is argued that they will be a permanent part of
		  the process of evolutionary development. Even in future
		  CASE systems with reliable automatic generation of
		  executable code, the resulting system will be (perhaps
		  automatically) reread by a reverse engineering process back
		  into the CASE dictionary. This will allow the discovery of
		  ramifications and side effects which are not foreseeable in
		  the forward engineering process.},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@InBook{	  hall:reverse,
  author	= {P. A. V. Hall},
  pages		= {209-243},
  title		= {Reverse Engineering - hype, hope or here?},
  series	= {Software Reuse and Reverse Engineering in Practice},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@InBook{	  hall:software,
  author	= {P. A. V. Hall},
  pages		= {3-31},
  title		= {Software Reuse, Reverse Engineering, and Re-engineering},
  series	= {Software Reuse and Reverse Engineering in Practice},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@InBook{	  holloway:re-engineering,
  author	= {S. Holloway},
  pages		= {271-282},
  title		= {Re-engineering business systems to use the next generation
		  of software},
  series	= {Software Reuse and Reverse Engineering in Practice},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@InBook{	  mcgill:reverse,
  author	= {R. McGill},
  pages		= {245-252},
  title		= {Reverse Engineering - not yet?},
  series	= {Software Reuse and Reverse Engineering in Practice},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}

@Article{	  miller:software,
  author	= {J. Cris Miller},
  title		= {Software Reengineering: Getting Done is Twice the Fun},
  year		= {1987},
  pages		= {171-178},
  class		= {Reengineering_in_General,
		  The_Pros_and_Cons_and_Risks_of_Reengineering}
}