How would companies modernize enterprise applications today
{"Image DocumentName": "How would companies modernize enterprise applications today?", "Image ImageDescription": "Search existing application documentation. Manually search libraries. Business request. Customer libraries. Study/analyze changes. Find impact of code changes. record findings manually. Manually test and debug applications, review dumps, and deploy applications. we need to understand how modernization would be done today in a customer shop and some of the problems associated with today s methods. first a developer or project leader receives a request from a business function to either enhance, move or enable an application for web access. Early in the process, a decision has to be made to rewrite or reuse the existing application, as well as how to integrate it into the existing system applications. COBOL and Java do not speak the same language and do not understand the same thing. In this example, we will assume that a decision has been made to reuse some part of the existing application. In order to understand the application, the developer has to search for existing application documentation, which is often nonexistent or out of date. Experts are not always located in same location. The developer must then search all libraries for all application artifacts. There is always the chance that some artifacts have been missed. Now the developer must estimate impact of any potential changes. He must find out how many programs interact with this application, as well applications that are affected by any data changes that are required for this e-business application. This research is all manual and thus, time consuming and error prone. Now the developer is ready to start the coding effort. He manually extracts the reusable code for the existing application. He must make sure that all necessary data elements are included. This creates our reusable component. Now he writes a program to call his new component. Now the developer, or, more likely, a developer with Java or other web based skills will create the web side of the application (connectors, JSPs, etc.). The original mainframe developer must communicate his requirements to the Java developer. Sometimes there are miscommunications. Once all the development is completed, the application has to be tested across all necessary platforms. all along, our developer has communicated with his team mates as needed. His phone calls or messages are not recorded. Memos/post-its can t be shared and can be lost. And  messages aren t saved. way are - outsourcing, buy package. Writing code - Java, COBOL,... Use findings to manually change or extract code.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}