An Ontological Approach for Recovering Legacy Business Content

Legacy Information Systems (LIS) pose a challenge for many organizations. On one hand, LIS are viewed as aging systems needing replacement; on the other hand, years of accumulated business knowledge have made these systems mission-critical. Current approaches however are often criticized for being overtly dependent on technology and ignoring the business knowledge which resides within LIS. In this light, this paper proposes a means of capturing the business knowledge in a technology agnostic manner and transforming it in a way that reaps the benefits of clear semantic expression - this transformation is achieved via the careful use of ontology. The approach called Content Sophistication (CS) aims to provide a model of the business that more closely adheres to the semantics and relationships of objects existing in the real world. The approach is illustrated via an example taken from a case study concerning the renovation of a large financial system and the outcome of the approach results in technology agnostic models that show improvements along several dimensions.

[1]  Keith H. Bennett,et al.  Legacy Systems: Coping with Success , 1995, IEEE Softw..

[2]  Hans Eriksson,et al.  Business Modeling With UML: Business Patterns at Work , 2000 .

[3]  C. Brodsky The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .

[4]  Leon A. Kappelman Year 2000: A Reality Check , 1999, Commun. Assoc. Inf. Syst..

[5]  Michael Stonebraker,et al.  Migrating Legacy Systems: Gateways, Interfaces, and the Incremental Approach , 1995 .

[6]  Mark Lycett,et al.  Software Stability: Recovering General Patterns of Business , 2004, AMCIS.

[7]  Victoria Y. Yoon,et al.  Requirements-driven data engineering , 1999, Inf. Manag..

[8]  Young-Gul Kim Improving Legacy Systems Maintainability , 1997, Inf. Syst. Manag..

[9]  Michael Uschold,et al.  Ontologies: principles, methods and applications , 1996, The Knowledge Engineering Review.

[10]  Bing Wu,et al.  Legacy Information Systems: Issues and Directions , 1999, IEEE Softw..

[11]  Balakrishnan Chandrasekaran,et al.  What are ontologies, and why do we need them? , 1999, IEEE Intell. Syst..

[12]  Ben Light,et al.  A Business Perspective of Legacy Information Systems , 1999 .

[13]  Narsim Ganti,et al.  The Transition of Legacy Systems to a Distributed Architecture , 1995 .

[14]  Alan O'Callaghan,et al.  Focus Issue on Legacy Information Systems and Business Process Change: Migrating Large-Scale Legacy Systems to Component-Based and Object Technology: The Evolution of a Pattern Language , 1999, Commun. Assoc. Inf. Syst..

[15]  Mark J. Safferstone Leveraging the New Infrastructure: How Market Leaders Capitalize on Information Technology , 1998 .

[16]  Bing Wu,et al.  The Butterfly Methodology: a gateway-free approach for migrating legacy information systems , 1997, Proceedings. Third IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.97TB100168).

[17]  F. P. Goyla Legacy integration-changing perspectives [Cobol] , 2000 .

[18]  Shasha Wu,et al.  Merging multiple conventional models in one stable model , 2002, CACM.

[19]  Chris Partridge Business Objects: Re-engineering for Re-use , 1996 .

[20]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[21]  Paul Winsberg,et al.  Legacy code: don't bag it, wrap it , 1995 .

[22]  Richard Baskerville,et al.  Growing systems in emergent organizations , 1999, CACM.

[23]  J. L. Austin,et al.  The foundations of arithmetic : a logico-mathematical enquiry into the concept of number , 1951 .

[24]  Paul Robertson,et al.  Integrating legacy systems with modern corporate applications , 1997, CACM.

[25]  Barry Turner,et al.  THE USE OF GROUNDED THEORY FOR THE QUALITATIVE ANALYSIS OF ORGANIZATIONAL BEHAVIOUR , 1983 .

[26]  Frank P. Coyle,et al.  Legacy Integration: Changing Perspectives , 2000, IEEE Software.

[27]  Alessandro Bianchi,et al.  Iterative Reengineering of Legacy Systems , 2003, IEEE Trans. Software Eng..