Legacy Platform Analysis

1334 Words6 Pages
“A legacy platform, also called a legacy operating system, is an operating system (OS) no longer in widespread use, or that has been supplanted by an updated version of earlier technology. Many enterprises that use computers have legacy platforms, as well as legacy applications, that serve critical business needs” (Rouse, 2017). For example, a large amount of banks and government entities still utilize legacy systems. Why would organizations want to use outdated operating systems when there are likely new, better alternatives? In short, legacy systems have been altered so much over the years to handle the organization’s operations that the organization has created a situation of extreme dependence on the legacy system. The revisions and…show more content…
This would allow an organization the ability to pin-point critical domains associated with the transition in an accurate and organized fashion to reduce any disruptions within the organization.

Rouse, M. (2017). Legacy Platform (Legacy Operating System). Retrieved on December 8, 2017 from http://whatis.techtarget.com/definition/legacy-platform-legacy-operating-system.
Schneider, A. (2013). When Companies Become Prisoners of Legacy Systems. Retrieved from http://deloitte.wsj.com/cio/2013/10/01/when-companies-become-prisoners-of-legacy-systems/.

As stated previously, the adoption of service-oriented architecture can bring forth various complexities due to the nature of its design. For this reason, it is necessary for organizations to make a considerable initial investment into adopting a service-oriented architecture design. In order to make service-oriented architecture work well for an organization, there must first be a substantial analysis of every facet of the initiative. “The construction of services can be expensive and time-consuming, introducing a more burdensome project delivery lifecycle, further compounded by some of the top-down analysis requirements that may need to be in place before services can be built” (Erl, 2008, p. 88). The complexities of analyzing, developing, and implementing a service-oriented architecture initiative coupled with the monetary expenses, time-constraints, and potentially vexatious project lifecycle
Open Document