Configuring Business Objects from Legacy Systems

  • Willem-Jan van den Heuvel
  • Mike Papazoglou
  • Manfred A. Jeusfeld
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1626)


In this paper we present a methodology, called binding Business Applications to LEgacy systems (BALES), that allows to blend modern business objects and processes with objectified legacy data and functionality in order to construct flexible, configurable applications, that are able to respond to business changes in a pro-active way.


Business Process Legacy System Legacy Process Business Object Enterprise Model 
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.


  1. [1]
    D.A. Taylor. Business Engineering with Object Technology. John Wiley and Sons, Inc., New York, 1995.Google Scholar
  2. [2]
    M. Hammer and J. Champy. Re-engineering the Corporation: A Manifesto for Business Revolution. Harper Collins, New York, 1993.Google Scholar
  3. [3]
    M.L. Brodie. “The Emperor’s Clothes are Object-Oriented and Distributed” in M.P. Papazoglou and G. Schlageter, editors, Cooperative Information Systems: Trends and Directions, Academic Press, 1998.Google Scholar
  4. [4]
    S. Abinavam and et al. San Francisco Concepts & Facilities. International Technical Support Organization, IBM, February 1998. SG24-2157-00.Google Scholar
  5. [5]
    M. L. Brodie and M. Stonebraker. Migrating Legacy Systems: Gateways, Interfaces and the Incremental Approach. Morgan Kaufman Publishing Company, 1995.Google Scholar
  6. [6]
    A. Umar. Application (Re)Engineering: Building Web-based Applications and Dealing with Legacies. Prentice Hall, New Jersey, 1997.Google Scholar
  7. [7]
    R.C. Aronica and D.E. Rimel Jr. “Wrapping your Legacy System”, Datamation, 42(12):83–88, June 1996.Google Scholar
  8. [8]
    P. Robertson. “Integrating Legacy Systems with Modern Corporate Applications”, Communications of the ACM, 50(5):39–46, 1997.CrossRefGoogle Scholar
  9. [9]
    I. Jacobson, M. Griss, and P. Jonsson. Software Reuse: Architecture, Process and Organization for Business Success. Addison Wesley, 1997.Google Scholar
  10. [10]
    T. Curran, G. Keller, and A. Ladd. SAP R/3 Business Blueprint: Understanding the Business Process Reference Model. Prentice-Hall, New-Jersey, 1998.Google Scholar
  11. [11]
    A.W. Scheer. Business Process Engineering: Reference Models for Industrial Enterprises. Springer-Verlag, 1994.Google Scholar
  12. [12]
    M.P. Papazoglou and W.J. van den Heuvel. “From Business Processes to Cooperative Information Systems: An Information Agents Perspective”, in M. Klusch, editor, Intelligent Information Agents, Springer-Verlag, Feb. 1999.Google Scholar
  13. [13]
    P. Eeles and O. Sims. Building Business Objects. John Wiley & Sons, New York, 1998.Google Scholar
  14. [14]
    I. Graham. Migrating to Object Technology. Addison-Wesley Publishing Company, Workingham, England, 1994.Google Scholar
  15. [15]
    I. Jacobson and M. Ericsson. The Object Advantage: Business Process Re-engineering with Object Technology. ACM Press, Addison-Wesley Publishing Company, Workingham, England, 1995.Google Scholar
  16. [16]
    E. Yu. Modeling Strategic Relationships for Process Engineering. PhD thesis, University of Toronto, 1994.Google Scholar
  17. [17]
    Department of Defense Netherlands. “Methodiek voor het inrichten van de informatievoorziening op basis van bouwstenen ten behoeve van het ministerie van defensie”, Technical Report, Defense Telematics Organization, 1997.Google Scholar
  18. [18]
    M.P. Papazoglou and S. Milliner. Content-based Organization of the Information Space in Multi-database Networks”, in B. Pernici and C. Thanos, editors, Procs. CAISE’98 Conf., Pisa, Italy, Springer-Verlag, 1998.Google Scholar
  19. [19]
    Data Access Technologies. Business object architecture (BOA) proposal. BOM/97-11-09, OMG Business Object Domain Task Force, 1997.Google Scholar
  20. [20]
    W. Hordijk, S. Molterer, B. Peach, and Ch. Salzmann. “Working with Business Objects: A Case Study”, OOPSLA’98 Business Object Workshop,, October 1998.
  21. [21]
    J. Mylopoulos, A. Borgida, M. Jarke, and M. Koubarakis. “Telos: Representing Knowledge about Information Systems”, ACM Transactions on Information Systems, 8(4):325–362, 1990.CrossRefGoogle Scholar
  22. [22]
    M.A. Jeusfeld, M. Jarke, H.W. Nissen, and M. Staudt. “ConceptBase: Managing Conceptual Models about Information Systems”, in P. Bermus, K. Mertins, and G. Schmidt, editors, Handbook on Architectures of Information Systems. Springer-Verlag, 1998.Google Scholar
  23. [23]
    M.P. Papazoglou and N. Russell. “A Semantic Meta-modeling Approach to Schema Transformation”, In CIKM-95: Int’l. Conf. on Information and Knowledge Management, Baltimore, Maryland, 1995.Google Scholar
  24. [24]
    M.P. Papazoglou and W.J. van den Heuvel. “Leveraging Legacy Assets”, to appear in M. Papazoglou, S. Spaccapietra, Z. Tari, editors, Advances in Object-Oriented Modeling, MIT-Press, 1999.Google Scholar
  25. [25]
    S. Chen. Retrieval of Reusable Components in a Deductive, Object-Oriented Environment. PhD thesis, RWTH Aachen, Information Systems Institute, 1993.Google Scholar
  26. [26]
    B. Meyer. Object-Oriented Software Construction. Prentice-Hall, Englewood Cliffs, 1994.Google Scholar
  27. [27]
    J. Mylopoulos. “Conceptual modeling and Telos”, in P. Loucopoulos and R. Zicari, editors, Conceptual Modeling, Databases and Case: an Integrated View on Information Systems Development, J. Wiley, New York, 1992.Google Scholar
  28. [28]
    P. Kardasis and P. Loucopoulos. “Aligning Legacy Information Systems to Business Processes”, in B. Pernici and C. Thanos, editors, Procs. CAISE’98 Conf., Pisa, Italy, Springer-Verlag, 1998.Google Scholar
  29. [29]
    M. Jarke, M.A. Jeusfeld, A. Miethsam, and M. Gocek. “Towards a Logic-based Reconstruction of Software Configuration Management”, 7th Knowledge-Based Software Engineering Conference. IEEE Computer Society Press, Los Alamitos, California, 1992.Google Scholar
  30. [30]
    Leonid Kalinichenko. “Workflow Reuse and Semantic Interoperation Issues”, in: Workflow Management Systems and Interoperability (A. Doğaç, L. Kalichenko, M.T. Özsu and A. Sheth eds.), NATO ASI Series, Springer, 1998Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1999

Authors and Affiliations

  • Willem-Jan van den Heuvel
    • 1
  • Mike Papazoglou
    • 1
  • Manfred A. Jeusfeld
    • 1
  1. 1.INFOLABTilburg UniversityTilburgThe Netherlands

Personalised recommendations