Transforming from Legacy to Packaged/Standard S/W Solutions: For Big Enterprises
DOI:
https://doi.org/10.37591/josettt.v3i1.662Abstract
Today with the technological developments in the field of computers and software, the automation through computerization has entered widely and deeply in almost every field. It has become very common to run an enterprise through sophisticated computer software. As it is well accepted fact that technology is changing rapidly hence the need to keep upgraded with latest trends is key to success; especially for the big enterprises where the challenge is not only to keep the enterprise running but also to collaborate with other enterprises doing similar business. The difficulty is not only in the information exchanges but also in sharing the concepts across the organizations. In today’s business context mergers and acquisitions, is another common move and integrating two organizations running on legacy is a marathon effort. The enterprises which are running on the legacy systems build long back and are being maintained internally or externally need to be adopted with standard solutions after a limit. In a sense it becomes mandatory for their survival. It is must if ICT has to be really a value adder and enabler to business. This paper reveals the approach how the transformation can be done smoothly from legacy to standard solutions.
Keywords: Legacy transformation, business IT alignment, management commitment, IT as business enabler, indispensability syndrome, partner collaboration, mergers and acquisitions, migrations
Cite this Article
Amit Mishra, Pradeep Tomar, Anurag Singh Baghel. Transforming from Legacy to Packaged/Standard S/W Solutions: For Big Enterprises. Journal of Software Engineering Tools & Technology Trends. 2016; 3(1): 5–11p.
References
Chad Vawter, Ed Roman. J2EE vs Microsoft.NET: A Comparison Of Building XML-Based Web Services. The Middleware Company; 2002.
http://www.middleware-company.com.
Bainbridge A, Colgrave J, Colyer A, et al. CICS and Enterprise Java Beans. IBM Systems Journal. 2001; 40(1).
Amey. Stone Keeping Legacy Software Alive. Business Week; 2001.
Anon Application Mining, (2001).
http://www.it-analysis.com/article_pf.php?id=1575.
Anthony Lauder, Stuart Kent. Legacy System Anti-Patterns and a Pattern-Oriented Migration Response. Computing Laboratory, University of Kent at Canterbury. 2000.
http://www.ukc.ac.uk/research/publications/2000/compsci.pdf.
Arie van Deursen, Paul Klint, Chris Verhoef. Research Issues in the Renovation of Legacy Systems. ETAPS Conference, Jim Duggan Graceful Retirement: Your Applications, Not You AV-15-4789. Gartner Group, 1999. February 2002-08-15. http://www.gartner.com.
Jerry Loza. Is a Switch to Java a Good Move for You? 2001.
http://www.techrepublic.com/article.jhtml?id=r00820010627ggp01.htm&src=bc.
John Bergey, Liam O’Brien, Dennis Smith. DoD Software Migration Planning. Technical Note CMU/SEI-2001-TN-012, Carnegie Mellon University. 2000.
Len Erlikh. Unlock the Power of Your Legacy Systems. Relativity Technologies Inc.; 2000. http://www.relativity.com.
Brodie Michael L, Michael Stonebraker. DARWIN: On the Incremental Migration of Legacy Information Systems. Technical Memorandum TR-0222-10-92-165, Electronics Research Laboratory, College of Engineering, University of California, and Berkeley. 1993.
Scott Tilley. The Net Effects of Product Lines SEI Interactive. Sep 1999.
http://interactive.sei.cmu.edu.
Simone Kaplan. Despite the Sluggish Economy and Uncertain Business Climate, Right Now is the Perfect Time to Tear down Your Legacy Applications and Start Over. CIO Magazine. 2002.
http://www.cio.com/archive/031502/infrastructure_content.html?printversion=yes.
Downloads
Published
Issue
Section
License
Declaration and Copyright Transfer Form
(to be completed by authors)
I/ We, the undersigned author(s) of the submitted manuscript, hereby declare, that the above manuscript which is submitted for publication in the STM Journals(s), is not published already in part or whole (except in the form of abstract) in any journal or magazine for private or public circulation, and, is not under consideration of publication elsewhere.
- I/We will not withdraw the manuscript after 1 week of submission as I have read the Author Guidelines and will adhere to the guidelines.
- I/We Author(s ) have niether given nor will give this manuscript elsewhere for publishing after submitting in STM Journal(s).
- I/ We have read the original version of the manuscript and am/ are responsible for the thought contents embodied in it. The work dealt in the manuscript is my/ our own, and my/ our individual contribution to this work is significant enough to qualify for authorship.
- I/We also agree to the authorship of the article in the following order:
Author’s name
1. ________________
2. ________________
3. ________________
4. ________________
| We Author(s) tick this box and would request you to consider it as our signature as we agree to the terms of this Copyright Notice, which will apply to this submission if and when it is published by this journal. |