This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Dependence Directed Reasoning and Learning in Systems Maintenance Support
February 1988 (vol. 14 no. 2)
pp. 211-227

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, it is shown that the system 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 he consequences of changing conditions or requirements, A formalism called REMAP (representation and maintenance of process knowledge) that accumulates design process knowledge to manage systems evolution is described. 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 cannot only be applied to prototype refinement and systems maintenance, but can also support the reuse of existing design or software fragments to construct similar ones using analogical reasoning techniques.

[1] D. S. Appleton,System 2000 Database Management System, Guide 37, Cambridge, MA, in Nov. 1973.
[2] R. Balzer, D. Dyer, Fehling, and Saunders, "Specification based computing environments," inProc. 8th Int. VLDB Conf., 1982, pp. 273-279.
[3] B. I. Blum, "A workstation for information systems development," inProc. 7th IEEE COMPSAC Conf., 1983, pp. 116-120.
[4] B. W. Boehm, J. F. Elwell, A. B. Pryster, B. D. Stuckle, and R. D. Williams, "The TRW software productivity system," inProc. 6th Int. Conf. Software Engineering, 1982, pp. 148-156.
[5] A. Borgida, S. Greenspan, and J. Mylopolous, "Using knowledge representation for requirements modeling,"Computer, vol. 18, pp. 82-91, 1985.
[6] A. Borgida, J. Mylopoulas, and H. Wong, "Generalization/specialization as a basis for software specification," inOn Conceptual Modelling. New York: Springer-Verlag, 1984.
[7] A. Borgida and K. Williamson, "Accomodating exceptions in databases and refining the schema by learning from them," inProc. 11th VLDB Conf., 1985, pp. 72-81.
[8] R. Davis, "Interactive transfer of expertise,"Artificial Intell., vol. 12, pp. 121-158, 1979.
[9] T. deMarco,Structured Analysis and System Specification. New York: Yourdon, 1978.
[10] V. Dhar and M. Jarke, "Learning from prototypes," inProc. 6th Int. Conf. Inform. Syst., Dec. 1985, pp. 114-133.
[11] V. Dhar, P. Ranganathan, and M. Jarke, "Taxonomic concept formation and refinement from examples," Dep. of Inform. Syst., New York Univ., Working Paper 170, Dec. 1987.
[12] J. Doyle, "A truth maintenance system," Massachusetts Inst. Technol., Cambridge, AI Lab. Memo. 521, 1978.
[13] H. Eckhardt, "Draft report on the database programming language DBPL," Univ. Frankfurt, 1985.
[14] C. Gane and T. Sarson,Structured Systems Analysis: Tools and Techniques. Englewood Cliffs, NJ: Prentice-Hall, 1979.
[15] C. Groner, M. D. Hopwood, N. D. Palley, and W. Sibley, "Requirements analysis in clinical research information processing--A case study,"Computer, vol. 12, pp. 100-108, 1979.
[16] C. Hewitt, "Implications of open systems," inManagers, Micros, and Mainframes, Integrating Systems for End Users, M. Jarke, Ed. New York: Wiley, 1986.
[17] M. Jarke, J. Mylopoulos, J. W. Schmidt, and Y. Vassiliou, "KBMS for software development," inProc. Xania Workshop Large-Scale Knowledge Base Management and Reasoning Systems. New York: Springer-Verlag, 1987.
[18] M. Jarke and J. Shalev, "A database architecture for supporting business transactions,"J. Management Inform., vol. 1, pp. 63-80, 1984.
[19] B. Konsynski, J. Kotteman, J. Nunamaker, and J. Stott, "PLEXSYS- 84: An integrated development environment for systems development,"J. Management Inform. Syst., vol. 1, 1984.
[20] J. E. Kotteman and B. R. Konsynski, "Dynamic metasystems for information systems development," inProc. 5th Int. Conf. Inform. Syst., Tucson, AZ, 1984, pp. 187-204.
[21] D. McAllester, "Reasoning utility package," Massachusetts Inst. Technol., Cambridge, AI Lab. Memo 667, 1982.
[22] R. Michalski,Machine Learning. Palo Alto, CA: Tioga, 1983.
[23] N. Minsky and A. Borgida, "The Darwin software evolution environment," inProc. SIGSOFT/SIGPLAN Software Engineering Symp. Practical Software Development, Pittsburgh, PA, 1984.
[24] T. Mitchell, "Learning and problem solving," inProc. Eighth Int. Joint Conf. Artificial Intelligence, 1983, pp. 1139-1151.
[25] T. Mitchell, S. Mahadevan, and L. Steinberg, "LEAP: A learning apprentice for VLSI design," inProc. 9th Int. Joint Conf. Artificial Intell., Los. Angeles, CA, 1985, pp. 573-580.
[26] D. Moon and D. Weinreb,Lisp Machine Manual, Massachusetts Inst. Technol., Cabridge, AL Lab., 1981.
[27] M. Morgenstern, "Active databases as a paradigm for enhanced computing environments," inProc. VLDB, Florence, 1983, pp. 34-42.
[28] J. Mostow, "Towards better models of the design process,"AI Mag., vol. 6, pp. 44-66, Spring 1985.
[29] J. Mylopoulos,et al., "A language facility for designing database intensive applications,"ACM Trans. Database Syst., vol. 5, no. 2, June 1980.
[30] K. Narayanaswamy, W. Scacchi, and D. McLeod, "Management support for evolving software systems," Dep. Comput. Sci., Univ. Southern California, Los Angeles, 1985.
[31] J. D. Naumann, and A. M. Jenkins, "Prototyping: The new paradigm for systems development,"MIS Quart., vol. 10, pp. 24-40, 1982.
[32] H. Shrobe, "Dependency directed reasoning for complex program understanding," Ph.D. dissertation, Massachusetts Inst. Technol., Cambridge, 1979.
[33] C. Rich, " A formal representation for plans in the programmers apprentice," inOn Conceptual Modeling, M. L. Brodie, J. Mylopolous, and J. W. Schmidt, Eds. New York: Springer-Verlag, 1984.
[34] E. H. Shortliffe,Computer-Based Medical Consultations: MYCIN. New York: American Elsevier, 1976.
[35] H. A. Simon,The Sciences of the Artificial, 2nd ed. Cambridge, MA: MIT Press, 1981.
[36] R. Waters, "The programmer's apprentice: Knowledge based program editing,"IEEE Trans. Software Eng., vol. SE-8, pp. 1-20, 1982.
[37] P. H. Winston, "Learning and reasoning by analogy,"Commun. ACM, vol. 23, pp. 869-703, 1979.

Index Terms:
software tools; expert systems; dependency directed reasoning; systems maintenance support; information systems; user requirements; teleology; REMAP; process knowledge; prototyping; domain-specific design rules; software fragments; expert systems; software reliability; software tools
Citation:
V. Dhar, M. Jarke, "Dependence Directed Reasoning and Learning in Systems Maintenance Support," IEEE Transactions on Software Engineering, vol. 14, no. 2, pp. 211-227, Feb. 1988, doi:10.1109/32.4639
Usage of this product signifies your acceptance of the Terms of Use.