Skip navigation
Please use this identifier to cite or link to this item:
Authors: Dhar, Vasant
Jarke, Matthias
Issue Date: Aug-1985
Publisher: Stern School of Business, New York University
Series/Report no.: IS-85-66
Abstract: The maintenance of large information systems involves continuous design modifications to designs in response to evolving business conditions or changing user requirements. Because of the complexity barrier associated with engineering such systems, changes can be ad hoc and prone to errors. Based on our observations of such a process in the oil industry, we believe that the systems maintenance activity would benefit greatly if the process knowledge reflecting the teleology of a design could be captured and used in order to reason about changing requirements, and to design parts of systems that might be “similar” to existing ones. In this paper, we describe a partially implemented formalism called REMAP (REpresentation and MAintenance of Process knowledge) that accumulates design process knowledge to manage systems evolution. To accomplish this, REMAP acquires and maintains dependencies among the design decisions made during a prototyping process as well as the general domain-specific design rules on which such dependencies are based. This knowledge can then be applied to prototype refinement, systems maintenance, and the re-use of existing designs to construct “similar” design fragments.
Appears in Collections:IOMS: Information Systems Working Papers

Files in This Item:
File Description SizeFormat 
IS-85-66.pdf4.89 MBAdobe PDFView/Open

Items in FDA are protected by copyright, with all rights reserved, unless otherwise indicated.