Access the full text.
Sign up today, get DeepDyve free for 14 days.
L. Wills (1987)
Automated Program Recognition: A Feasibility DemonstrationArtif. Intell., 45
W. Kozaczynski, S. Letovsky, J. Ning (1991)
A Knowledge-based Approach To Software System UnderstandingProceedings., 6th Annual Knowledge-Based Software Engineering Conference
A. Aho, Ravi Sethi, J. Ullman (1986)
Compilers: Principles, Techniques, and Tools
E. Soloway, Kate Ehrlich (1984)
Empirical Studies of Programming KnowledgeIEEE Transactions on Software Engineering, SE-10
M. Weiser (1981)
Program SlicingIEEE Transactions on Software Engineering, SE-10
W. Kozaczynski, J. Ning, Thomas Sarver (1992)
Program concept recognitionProceedings of the Seventh Knowledge-Based Software Engineering Conference
E. Soloway, W. Lewis, Elliot Solowy (1984)
PROUST: Knowledge-Based Program UnderstandingIEEE Transactions on Software Engineering, SE-11
J. Hartman (1991)
Automatic Control Understanding for Natural Programs
C. Rich (1981)
A Formal Representation For Plans In The Programmer's Apprentice
B. Curtis, S. Sheppard, Elizabeth Kruesi-Bailey, J. Bailey, D. Boehm-Davis (1989)
Experimental evaluation of software documentation formatsJ. Syst. Softw., 9
J. Ferrante, K. Ottenstein, J. Warren (1984)
The program dependence graph and its use in optimizationACM Trans. Program. Lang. Syst., 9
L. Wills (1992)
Automated program recognition by graph parsing
W. Johnson (1986)
Intention-based diagnosis of errors in novice programs (program understanding, debugging, intelligent computer-aided instruction)
J. Ning (1989)
A knowledge-based approach to automatic program analysis
Automated Supportfor Legacy Code Understand3ng any large companies inhibiting a legacy can be approached system, requirements. are facing growth in a number replacing a problem: and capacity their legacy systems This are their business to chans. problem new rules in else of ways. One way is to simply get rid of to meet business anywhere for many reasons. critical For exam- it with a new one developed systep contains This option is rarely exercised assets to the company. very difficult ple, more often than not, alegacy ,that are valuable and are therefore Another the code may not be accurately alternative The business rules embedded and explicitly to capture documented and redevelop. is to encapsulate a legacy system so it can be used or within a new system. is the use of terminal machine and feaarc is a mainframe as a whole under a new execution A very simple example emulators terminal intelligent preserved. to translate workstations. data streams environment between of such system âwrappingâ screens so that dumb terminals This approach can be replaced with LAN-based has a number of attractive function&ties tures: 1) &f&y. Since there is no software change,original is necessary limitations: 2) Low cost. Since
Communications of the ACM – Association for Computing Machinery
Published: May 1, 1994
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.