Advertisement

Experiences in Object-Oriented Re-Engineering

  • Stéphane Ducasse
  • Joachim Weisbrod
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1543)

Abstract

The ability to reengineer object-oriented systems has become a vital matter in today’s software industry. Early adopters of the object-oriented programming paradigm are now facing the problem of transforming their object-oriented ‘legacy’ systems into full-fledged frameworks. Dealing with programs exceeding 10,000 lines of badly documented code definitely requires support from methodologies as well as tools.

Keywords

Core Model Early Adopter Development Cost Software Industry Programming Paradigm 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. DW98.
    Ducasse Stéphane and Joachim Weisbrod, Proceedings of the ECOOP’98 Workshop on Experiences in Object-Oriented Re-Engineering, FZI Report Number 6/7/98, Frschungszentrum Informatik, Hid-und-Neu-Straße 10-14, 76131 Karlsruhe, Germany, June 1998.Google Scholar

Other References

  1. Bär98.
    Holger Bär, Automatische Suche von Designproblemen in objektorientierten Systemen, Diplomarbeit, Universität Karlsruhe, März 1998.Google Scholar
  2. BC98.
    Holger Bär and Oliver Ciupke, Exploiting design heuristics for automatic problem detection, In Stéphane Ducasse and Joachim Weisbrod, editors, Proceedings of the ECOOP Workshop on Experiences in Object-Oriented Re-Engineering, number 6/7/98 in FZI Report, June 1998.Google Scholar
  3. JF88.
    Ralph E. Johnson and Brian Foote, Designing reuseable classes, Journal of Object-Oriented Programming, 1(2):22–35, June 1988Google Scholar
  4. Lak96.
    John Lakos, Large-Scale C++ Software Design, Addison-Wesley, 1996.Google Scholar
  5. Rie96.
    Arthur J. Riel, Object-Oriented Design Heuristics, Addison-Wesley, 1996.Google Scholar

Other References

  1. 1.
    F. Brito e Abreu, M. Goulao, and R. Esteves. Toward the design quality evaluation of OO software systems. In 5th Int Conf on Software Quality, 1995.Google Scholar
  2. 2.
    M. Cartwright and M. Shepperd. An empirical analysis of object-oriented software in industry. In Bournemouth Metrics Workshop, Bournemouth, UK, April 1996.Google Scholar
  3. 3.
    S. R. Chidamber and C.F. Kemerer. MOOSE: Metrics for object oriented software engineering. In Workshop on Processes and Metrics for Object Oriented Software Development, OOPSLA’ 93, Washington, 1993.Google Scholar
  4. 4.
    M. Lorenz and J. Kidd. Object-oriented Software Metrics. Prentice Hall Object-Oriented Series, 1994.Google Scholar

Other References

  1. Age96.
    Ole Agesen. Concrete Type Inference: Delivering Object-Oriented Applications. PhD thesis, Sun Microsystems Laboratories, 1996.Google Scholar
  2. BI82.
    Alan Borning and Dan Ingalls. A type declaration and inference system for Smalltalk. In A CM Symposium on Principles of Programming Languages, 1982.Google Scholar
  3. Joh86.
    R.E. Johnson. Type-checking Smalltalk. In Proceedings OOPSLA’ 86, pages 315–321. ACM, sep 1986.Google Scholar
  4. PC94.
    J. Plevyak and A. Chien. A precise concrete type inference for object-oriented languages. In Proceedings of OOSPLA’ 94, pages 324–340, 1994.Google Scholar
  5. Rapi98.
    Pascal Rapicault, D: A Language Framework for Distriubted Programming, Université de Nice, Rapport de DEA, 1998Google Scholar

Other References

  1. BJRF98.
    John Brant, Ralph E. Johnson, Donald Roberts, and Brian Foote. Wrappers to the rescue. In To appear in Proceedings of ECOOP’98, LNCS 1445, Springer-Verlag, 1998.Google Scholar
  2. MN97.
    Gail Murphy and David Notkin. Reengineering with reflexion models: A case study. IEEE Computer, 17(2):29–36, aug 1997.Google Scholar
  3. Wuy98.
    Roel Wuyts. Declarative reasoning about the structure of object-oriented systems. In To appear in Proceedings of TOOLS USA’ 98, 1998.Google Scholar
  4. YHC97.
    A.S. Yeh, D.R. Harris, and M.P. Chase. Manipulating recovered software architecture views. In Proceedings of ICSE’97, 97.Google Scholar

Other References

  1. Gam95.
    Gamma, E. et al, Design Patterns: Elements of Reusable Object-Oriented Software, Addison-Wesley, 1995.Google Scholar
  2. OCi97.
    Ó Cinnéide, M., Towards Automating the Introduction of the Decorator Pattern to Avoid Subclass Explosion, Technical Report TR-97-7, Department of Computer Science, University College Dublin, Ireland.Google Scholar
  3. OCi98.
    Ó Cinnéide, M. and Nixon, P., Program Restructuring to Introduce Design Patterns, Technical Report TR-98-2, Department of Computer Science, University College Dublin, Ireland.Google Scholar
  4. Opd92.
    Opdyke, W. F., Refactoring Object-Oriented Frameworks, PhD thesis, University of Illinois, 1992.Google Scholar

Other References

  1. SGMZ98.
    Benedikt Schulz and Thomas Genßler and Berthold Mohr and Walter Zimmer, On the Computer Aided Introduction of Design Patterns into Object-Oriented Systems, Proceedings of the 27th TOOLS conference, 1998, IEEE CS PressGoogle Scholar
  2. Mohr98.
    Berthold Mohr, Reorganisation objektorientierter Systeme, Forschungszentrum Informatik (FZI) an der Universität Karlsruhe (TH), 1998, FZI; Haid-und-Neu-Str. 10-14; 76137 Karlsruhe, DiplomarbeitGoogle Scholar
  3. Zimm97.
    Walter Zimmer, Frameworks und Entwurfsmuster, 1997, University of KarlsruheGoogle Scholar
  4. RoBJ97.
    Don Roberts and John Brant and Ralph Johnson, A Refactoring Tool for Smalltalk, http://st-www.cs.uiuc.edu/users/brant/Refactory/RefactoringBrowser.html, 1997
  5. Opd92.
    William F. Opdyke, Refactoring Object-Oriented Frameworks, 1992, University of Illinois at Urbana-ChampaignGoogle Scholar

Other References

  1. CDIF94.
    “CDIF Framework for Modeling and Extensibility”, Electronic Industries Association, EIA/IS-107, January 1994, online available at http://www.cdif.org/.
  2. Deme98.
    Serge Demeyer and Sander Tichelaar, “Definition of the FAMOOS Information Exchange Model-Version 1.1”, Technical Report, 1998. http://www.iam.unibe.ch/famoos/InfoExchFormat/

Other References

  1. 1.
  2. 2.
    Juhani I., Why CASE Tools are not Used?, Communication of the ACM, October 1996, Vol. 39, No 10, p.94–103CrossRefGoogle Scholar
  3. 3.
    Kusters, R.J. ja Wijers, G.M., On the practical use of CASE-tools: results of a survey, IEEE Proceedings of the 6th International Workshop on CASE, Singapore 1993, pp. 2–10Google Scholar
  4. 4.
    Rumbaugh J., Blaha M., Premerlani W., Eddy F. and Lorensen W., Object-Oriented Modeling and Design, Prentice-Hall International, 1991Google Scholar
  5. 5.
    Rational Rose CASE tool. See http://www.rational.com/

Copyright information

© Springer-Verlag Berlin Heidelberg 1998

Authors and Affiliations

  • Stéphane Ducasse
    • 1
  • Joachim Weisbrod
    • 2
  1. 1.University of Bern, IAM-SCGBernSwitzerland
  2. 2.Forschungszentrum Informatik (FZI)KarlsruheGermany

Personalised recommendations