References of From_Procedural_to_Object-Oriented

@InProceedings{	  bosma.fielt.ea:scenarios,
  author	= {H. Bosma and E. Fielt and T. Wiggerts},
  title		= {Scenarios for the Identification of Objects in Legacy
		  Systems},
  booktitle	= {Fourth Working Conference on Reverse Engineering},
  publisher	= {IEEE Computer Society},
  year		= {1997},
  editor	= {I. Baxter and A. Quilici and C. Verhoef},
  pages		= {24-32},
  month		= {October},
  abstract	= {In this article we propose an incremental approach to the
		  identification of (business) objects in legacy
		  applications. In this approach different object
		  identification scenarios can be applied alternately. Three
		  different strategies are presented: function driven, data
		  driven and object driven objectification. We discuss these
		  scenarions and report on experiences gained from applying
		  them to a subsystem of a real-life mortgage system. We also
		  discuss related work.},
  keywords	= {legacy, objects, identification, extraction, scenarios,
		  experiences},
  class		= {From_Procedural_to_Object-Oriented Re-Design Alteration }
}

@InProceedings{	  pidaparthi.cysewski:case,
  author	= {Sagar Pidaparthi and Grzegorz Cysewski},
  title		= {Case study in Migration to Object-Oriented System
		  structure Using Design Transformation Methods},
  booktitle	= {1st  European Conference on Software Maintenance and
		  Reengineering 97},
  month		= mar,
  year		= {1997},
  publisher	= {IEEE Computer Society Press},
  abstract	= {Procedural programming languages are currently being used
		  extensively in the software industry for a wide range of
		  applications. Most of the old procedural programs, used
		  today may not have any documentation which can be used in
		  maintenance processes. In the recent time there has been a
		  paradigm shift towards object oriented design and
		  programming, from algorithmic decomposition, structured
		  design and procedural implementation. Hence, there is a
		  growing need to restructure old programs which have a poor
		  architecture during evolutionary processes. It is more
		  economic to restructure existing software into object
		  oriented topology by identifying objects within the subject
		  system than to redesign software starting from scratch.
		  Object identification relies upon program analysis and a
		  study of inter component relationships and dependencies.
		  Researchers in re-engineering have proposed some guidelines
		  to identify objects from within the subject systems. Design
		  Transformation is the first step in reengineering existing
		  programs, which can be followed by program translation
		  methods to transform a procedural program into the newly
		  identified structure. This paper reports the results of the
		  application of three object identification methods on a
		  sample procedural program. Secondly it provides a design of
		  a system for program component storage and object
		  identification },
  class		= {Alteration, Re-Design,
		  From_Procedural_to_Object-Oriented}
}

@InProceedings{	  sneed:migration,
  title		= {Migration of procedurally oriented {COBOL} programs in an
		  object-oriented architecture},
  author	= {H. Sneed},
  booktitle	= {\cite{SM92}},
  pages		= {105--116},
  year		= {1992},
  note		= { The subject of this paper is to describe the migration of
		  procedurally structured COBOL into functionally equivalent
		  object-oriented programs. Their major differences are
		  described together with an approach to bridge the gap
		  between the two},
  class		= {Alteration, Re-Design,
		  From_Procedural_to_Object-Oriented}
}