|
|
App. Modernization Products - Legacy Rejuvenator® - Modernization Console
S2T® Technology - Overview - Whitepapers & Presentations Resources - Support - News - Case Studies - Webcast Login - Partners - Strategic Alliances - About EvolveWare - Contact Us |
Legacy applications have evolved over time with no guarantees that available documentation is current. Mainframe programmers and support personnel are reaching retirement age. Replacing these resources is becoming difficult and expensive as graduating engineers lack knowledge of “old” languages like COBOL, Natural, Assembler, PL/1, RPG, C++ etc., preferring to focus their school years on learning “new” languages like C#, VB.Net and Java. This lack of demand for learning “old” languages has, in turn, forced Universities to stop offering courses in these languages, further compounding the resource problem for organizations that run their operations on mainframe and mid-frame applications. Enterprises are running global operations. Interoperability and sharing of applications as services is the key to efficiencies, which is difficult to achieve with proprietary and legacy systems. So how does one address the Legacy Problem? For starters IT Departments “need to know” the processes and rules running these applications. Most such applications have been in use for long periods of time and there is no certainty that available documentation is current. Processes and rules become hidden or “lost” over time. Gathering all this data manually is tedious and impossible to rely on. Legacy Rejuvenator automates the discovery and extraction of program logic, business rules and data model from COBOL, Adabas/Natural and Assembler applications, making this information available in the following formats: Program Logic
As a first step, Legacy Rejuvenator extracts the data model from the source, thereby identifying the entities within the code. Then the data structures/variables are extracted with their contexts of use (data flow trace information). As a next step the entire source code is converted into an intermediate form of XML (iXML). This is a first level interpretation of the source in XML format and includes the business logic with references to entities and variables. Thereafter the iXML is transformed into a standardized form of XML (Generic XML), which includes the program logic, entities, data structures and their flow trace. At this point fuzzy-neural rules are applied to this Generic XML to interpret the logic and extract business rules from the same. All of this information is populated in a knowledgebase (repository) and made available to the user through the Modernization Console.
|
