This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Maintenance Support for Object-Oriented Programs
December 1992 (vol. 18 no. 12)
pp. 1038-1044

[1] G. Booch, "Object-oriented development,"IEEE Trans. Software Eng., vol. SE-12, pp. 211-221, Feb. 1986.
[2] S.C. Choi and W. Scacchi, "Extracting and restructuring the design of large systems,"IEEE Software, vol. 7. pp. 66-71, Jan. 1990.
[3] L. Clevland, "A program understanding support environment,"IBM Systems J., vol. 28, pp. 324-344, 1989.
[4] B.J. Cox,Object-Oriented Programming: An Evolutionary Approach. Reading, MA: Addison Wesley, 1986.
[5] Digitalk, Inc., Smalltalk/V Mac Tutorial and Programming Handbook, Digitalk Corp., Los Angeles, CA, 1989.
[6] J. Foster and M. Munro, "A documentation method based on crossreferencing," inProc. IEEE Conf. Software Maintenance, pp. 181-185, Sept. 1987.
[7] A. Goldberg and D. Robson,Smalltalk80: The Language and Its Implementation. Reading, MA: Addison-Wesley, May 1983.
[8] J. Graver and R. Johnson, "A type system for Smalltalk," inProc. 17th Annual ACM Symp. Principles of Programming Languages, pp. 136-150, 1990.
[9] R. Helmet al., "Contracts: Specifying behavioral compositions in object-oriented systems," inProc. ECOOP/OOPSLA 90-SIGPLAN Notices, vol. 25, pp. 169-180, Oct. 1990.
[10] D. Hutchens and V.R. Basili, "System Structure Analysis: Clustering with Data Bindings,"IEEE Trans. Software Eng., Vol. SE-11, No. 8, Aug. 1985, pp. 749-757.
[11] R.E. Johnson and B. Foote, "Designing reusable classes,"J. Object-Oriented Programming, vol. 1, pp. 25-35, June/July 1988.
[12] D.R. Kuhn, "A source code analyzer for maintenance," inProc. IEEE Conf. Software Maintenance, pp. 176-180, Sept. 1987.
[13] M. Lejteret al., "Support for maintaining object-oriented programs," inProc. IEEE Conf. Software Maintenance, pp. 171-178, Oct. 1991.
[14] K.L. Lieberherr and I.M. Holland, "Assuring good style for object-oriented programs,"IEEE Software, vol. 6, pp. 38-48, Sept. 1989.
[15] K. Lieberherret al., "Graph-based software engineering: Concise specifications of cooperative behavior,"Tech. Rep. NU-CCS-91-14, College of Computer Science, Northeastern University, Sept. 1991.
[16] B. P. Lientz and E. B. Swanson,Software Maintenance Management. Reading, MA: Addison-Wesley, 1980.
[17] S.-S. Liu and N. Wilde, "Identifying objects in a conventional procedural language: An example of data design recovery," inProc. IEEE Conf. Software Maintenance, pp. 266-271, Nov. 1990.
[18] D. Manel and W. Havanas, "A study of the impact of C++ on software maintenance," inProc. IEEE Conf. Software Maintenance, pp. 63-69, Nov. 1990.
[19] B. Meyers,Object Oriented Software Construction. Englewood Cliffs, NJ: Prentice-Hall, 1988.
[20] J. Nielsen and J. Richards, "Experience of Learning and Using Smalltalk",IEEE Software, pp. 73-77, May 1989.
[21] D.E. Perry and G.E. Kaiser, "Adequate testing and object oriented programming,"J. Object-Oriented Programming, vol. 2, pp. 13-19, Jan. 1990.
[22] V. Rajlichet al., "Visual support for programming-in-the-large," inProc., IEEE Conf. Software Maintenance, pp. 92-99, Oct. 1988.
[23] J. Sametinger, "A tool for the maintenance of C++ programs," inProc. IEEE Conf. Software Maintenance, pp. 54-59, Nov. 1990.
[24] R.W. Schwanke and M.A. Platoff, "Cross references are features," inProc. 2nd Int. Workshop on Software Con Fig. Management, pp. 86-95, Oct. 1989.
[25] R.W. Selby and V. Basili, "Error localization during software maintenance: Generating hierarchical system descriptions from the source code alone," inProc. IEEE Conf. Software Maintenance, pp. 192-197, Oct. 1988.
[26] I. Silva-Lepe, "Abstracting graphed-based specifications of object-oriented programs,"Tech. Rep. NU-CCS-92-4, College of Computer Science, Northeastern University, Mar. 1992.
[27] M. Weiser, "Program slicing," inProc. 5th Int. Conf. Software Eng., May 1981, pp. 439-449.
[28] N. Wilde and B. Nejmeh, "Dependency analysis: An aid for software maintenance,"SERC-TR-13-F, Software Engineering Research Center, Univ. Florida, Gainesville, FL, Sept. 1987.
[29] N. Wilde, R. Huitt, and S. Huitt, "Dependency analysis tools: Reusable components for software maintenance," inProc. IEEE Conf. Software Maintenance, pp. 126-131, Oct. 1989.
[30] N. Wilde and R. Huitt, "A reusable toolset for software dependency analysis,"J. Systems and Software, vol. 14, pp. 97-102, Feb. 1991.
[31] N. Wildeet al., "Describing object oriented software: What maintainers need to know,"SERC-TR-54-F, Software Engineering Research Center, Univ. Florida, Gainesville, FL, Dec. 1991.
[32] S.S. Yau, "Ripple effect analysis of software maintenance," inProc. COMPSAC-78, IEEE Computer Society, pp. 60-65, 1978.

Citation:
N. Wilde, R. Huitt, "Maintenance Support for Object-Oriented Programs," IEEE Transactions on Software Engineering, vol. 18, no. 12, pp. 1038-1044, Dec. 1992, doi:10.1109/TSE.1992.1263033
Usage of this product signifies your acceptance of the Terms of Use.