Skip navigation
Please use this identifier to cite or link to this item:
Authors: Dhar, Vasant
Jarke, Matthias
Issue Date: Mar-1987
Publisher: Stern School of Business, New York University
Series/Report no.: IS-87-20
Abstract: The maintenance of large information systems involves continuous modifications in response to evolving business conditions or changing user requirements. Based on evidence from a case study, we show 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 the consequences of changing conditions or requirements. We describe a 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, and is able to learn general domain-specific design rules on which such dependencies are based. This knowledge can not only be applied to prototype refinement and systems maintenance, but can also support the re-use of existing design or software fragments to construct similar ones using analogical reasoning techniques.
Appears in Collections:IOMS: Information Systems Working Papers

Files in This Item:
File Description SizeFormat 
IS-87-20.pdf4.36 MBAdobe PDFView/Open

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