Legacy ForensicS€¦ · · 2014-03-25technologies and methods used in legacy systems development, ... it is difficult to understand why businesses continue to use such old technology

Legacy ForensicSTHE BUSINESS CASE, CHALLENGES AND

SOLUTION FOR REDUCING RISK IN LEGACY ENVIRONMENTS

Legacy systems have passed through many hands over many years, often without proper documentation of features or functional relationships. A detailed analysis of legacy applications and databases is essential for risk mitigation and proper decision-making in any modernization project. This paper breaks down the business case for legacy forensics, best practices, and how BluePhoenix’s solution can help.

page - 02 | LEGACY FORENSICS

Overview

Many find it astounding that 80% of the world’s corporate data resides in or originates from technology that is more than half of a century old. Given the prev-alence of legacy systems and the changing environment within which they exist, conversion to modern applications can be expensive, risky, and time- consuming.

This whitepaper:

• Uses data culled from analyst relationships, partners and over 20 years of modernization projects with customers like Walmart, NY Life, Citi and more

• Breaks down market, business and technology factors contributing to legacy system risk

• Spells out most frequent and impactful risk factors for modernization projects

• Offers detailed, proven solution for reducing risk factors for modernization

• Offers examples of solution impact in real-world projects and engagements

Legacy Forensics: Why It’s Important Understanding the liability created by aging critical systems

Common Risk Factors of Modernization The relationship between project failure and the lack of detailed data on the legacy environment

Best Practices In Successful Modernization Using forensic data to overcome challenges and scenarios that contribute to project overrun and failure

Technical Overview: BluePhoenix Solutions Breakdown of our Legacy Forensics service and technology

Practical Application, Real World Scenarios Examples of how Legacy Forensics fits into real-world scenarios and the story of a successful project with banking giant Merrill Lynch

Conclusion Closing statement, About BluePhoenix

ContentsKnow the Details, Reduce The Risk


Overview: Legacy Forensics

Drivers for ModernizationThe internet, the evolution of e-commerce, and new hardware and communications systems have forced organizations to adopt new ways to maintain competitive edge. Companies have been forced to expand the ways in which business rules and information housed in legacy environments are used. Unfortunately, because of their architecture, these legacy systems do not integrate well with modern-day IT environments, making the expansion of functionality very costly. To make matters worse, the evolution of software development from a procedural landscape to object-oriented design has opened a rift between the skills required to maintain legacy systems and the skills being utilized by today’s developers in the design and implementation of modern software. In other words, the workforce available to understand old technologies is aging alongside the systems themselves.

Consider this from a 2013 Computerworld Survey:

Between an evolving marketplace and an aging resource pool, retaining legacy systems is becoming very risky, driving the need for modernization and renovation. However, modernization of legacy systems presents some unique challenges:

• Although the legacy technology introduces risk, the rules and methods imbedded in the functionality of the code continue to be relevant to the business, therefore retaining the business knowledge and concepts around transactional procedures housed in the legacy systems is of the utmost importance.

• Due to the age of the systems, their cluttered architecture, and the nature of employee turnover, the likelihood of obtaining useful documentation of business rules and code functionality is infinitely small.

• The present generation of application designers and programmers are often unfamiliar with the technologies and methods used in legacy systems development, thus rendering the systems almost impossible to understand, maintain, modify, and adapt to changing needs.

Legacy systems play an enormous role in business today. Many find it astounding that 80% of the world’s corporate data resides in or originates from mainframes running technology that is more than half of a century old. To some, it is difficult to understand why businesses continue to use such old technology for such critical applications. The reason is quite simple. The legacy systems are robust. They perform satisfactorily and continue to meet the functional requirements around which they were originally built. Banks loan money to their customers and calculate interest rates in the same way they have for decades. Insurance companies gather, calculate, and store policy information in basically the same way they have since long before IT technology was around. The fact is they’ll probably continue these methods in similar ways going forward no matter what technology evolves next. The business rules at work in the legacy system rarely change, so why mess with it?

ComputerWorld’s IT Survey identified a massive resource gap facing the mainframe world. Moving to a distributed system mitigates risk around increasingly rare legacy system resources.

46%

50%

22%

64%

nearly 75%

said age of average COBOL staffer is over 45

said the age is 55 or older

said COBOL represents more than half of all internal business application code

said their organizations still use COBOL- more than any modern language except for Java/JavaScript and Visual Basic

are noticing a COBOL programmer shortage

Given the prevalence of legacy systems and the changing environment within which they exist, their conversion to modern applications is an expensive, risky, and time-consuming undertaking.

In order to develop well-designed applications from legacy environments, powerful tools and expertise are required to analyze the legacy system and aid in generating new programs that are architecturally sound and utilize modern design methods.

Furthermore, they must capitalize on the fact that, for the most part, the business processing functions of the legacy system (i.e. the business rules) will retain their validity in the new application.

Understanding these business rules and their relationship to the legacy environment is a foremost requirement in the reduction of risk associated with their effective transition into a maintainable and agile target application.


Overview: Legacy Forensics (continued)The Importance of Legacy Forensics

“

”

BluePhoenix worked closely with our teams from the inception of the project through the scope and planning to the delivery. The project has been completed with-in timescale and budget and this enables us to move onto the next stage of our IT strategy.

David Loughenbury, CIOPolice Mutual Assurance Society, UK

Tactical Challenges of Legacy Systems, CIO Magazine 2013

Consider the following data from a 2013 Gartner survey of CIOs and other IT leaders in the U.S. insurance industry:

These findings show that the risks of legacy modernization are much greater than commonly anticipated, and pose a significant problem for IT organizations. Through reviewing the results and feedback from respondents’ migration projects, Gartner identified a number of common risks associated with modernization, including:


Common Risk Factors Associated With Modernization

42% 34% 18%

Of respondents’ modernization projects were completed within the originally planned budget Covered the originally planned scope Completed within the originally planned

time frame

Gartner: Modernization Risk FactorsCost overrun The hardware, software, and service costs of a legacy modernization approachExcessive effort/time The human resources, skills, or time needed for a legacy modernization project is

either underestimated or greater than expected due to unforeseen issuesLack of innovation The degree of innovation and business value that is delivered by a legacy modern-

ization initiative doesn’t meet the initial expectationsUnrealistic timelines The timeline for a legacy modernization initiative is set by some external dynamics,

rather than the effort needed for the project — for example, a mainframe outsourcing contract ends

Complex manageability The controllability or maturity of a legacy modernization initiative is not sufficient, leading to underperformance of the new system, higher maintenance costs or other issues

Lack of reuse There is no investment protection or possible reuse of formerly existing legacy system functions, which has a negative business impact

High change impact The required process or organizational changes, and the potential resistance before, during, or after the legacy modernization project, are very high

Low efficiency The cost, efficiency, or productivity and gains after the legacy modernization initiative are insufficient

High complexity The costs, required skills, and dependencies of the new IT system on legacy artifacts, vendor resources or other factors decrease system stability and business performance.

Insufficient sustainability There is a low likelihood that a certain technology or vendor solution that is selected for legacy modernization will remain relevant for the expected lifetime of the investment

For many organizations, the legacy system is a “black box” - a vast entanglement of intertwined code written by developers who retired or left the firm long ago, leaving behind little documentation or applied standards of any kind. These unknowns make planning a migration extremely difficult.

Most of the common risks associated with migrations revolve around understanding the breadth of influence of the business rules housed within the legacy system, and planning based on the accuracy of the assessed complexity of the system itself. The depth of understanding the source environment is directly related to an organization’s ability to plan for and implement a successful modernization strategy.

With an accurate, detailed understanding of the source environment, organizations reduce the potential of cost overrun by understanding the scope of the project earlier, are able to set more realistic timelines, and understand the impact of scope and time on the level of effort required to be successful.

Furthermore, understanding the source environment in detail provides an avenue for the definition and analysis of business rules, allowing cross-functional stakeholders to make strategic decisions and adjustments to reduce change impact, introduce innovative change, and mitigate against inefficiency or unnecessary complexity.


Common Risk Factors Associated With Modernization

No Easy Way To Modernize, But You Can Reduce The Risk

“

”

We’re seeing a shift away COBOL and Natural applications as skilled resources retire. BPHX helps customers convert to maintainable code, utilizing SQL Server and Win-dows Server. Now they can address the skills shortage and more importantly, enable the deployment of mobile, social and always connected experiences their customers demand.Bob Ellsworth, WW Director of Platform Modernization, Microsoft

Strategic Challenges of Legacy Systems, CIO Magazine 2013


Best Practices In Successful Modernization

Document and Map the Source System

Never Underestimate the Impact of Change

Develop a Comprehensive Project and Testing Plan

It is difficult to overemphasize the importance of developing test cases/scenarios for integration and system testing. Some organizations fail to involve end users in such testing at an early stage of the legacy modernization project, or they test in organizational silos and fail to ensure appropriate cross-functional representation when testing processes that cut across the enterprise. This is an essential element in collecting input on the usability of new systems or communicating the impact of redesigned business processes. Develop a comprehensive test strategy and involve end users in creating test cases. Start early with your test plan to minimize risks and costs.

While documentation and mapping of the legacy environment significantly reduces risk, going a step further by including time during the modernization planning process to consider feedback from important constituents to ensure that the destination and route to modernize are correct for the business, will pay enormous dividends.

Project and test planning should recognize the timeframes necessary to modernize the application portfolio and the cost of engaging in the effort in realistic terms.

Manage change by dividing the project into clusters. Early steps can identify applications related by data stores or interfaces. These applications may be modernized in phases. The project plan can then treat these related applications in isolation from other systems and build an evolution plan based on their own needs. It may also reduce the number of bridges that may need to be built between platforms as the migration evolves.

Create a dedicated and focused team to lead the modernization effort through its life span. This team should address risks exposed in the assessment of the legacy systems head-on by identifying them and planning for contingencies. They should actively reassess risk factors through each phase of the migration process to determine whether the plan of attack or project scope needs refinement.

Before migrating workloads away from legacy environments, organizations should carefully consider the implications of upending decades-old architecture that reflects significant historical business functions.

With proper planning, understanding, and testing, the migration process can be successful and timely. During the initial planning and business rules discovery phases, it is important to keep a few best practices at top of mind.

Understanding the details of an application and its interrelationships with other systems is absolutely necessary for successful modernization.

A challenge for many companies is that little documentation exists, or is current, for many applications. The core business functionality that is built into these legacy systems is highly complex and extremely difficult to understand without the use of specially designed tools.

Because of this, the tendency is to move forward without it. Obtaining good code understanding and creating documentation will help organizations make smart modernization decisions.

Most legacy applications in need of modernization are deeply embedded in the culture of the companies that they serve. The transactions they process and the records they keep impact every aspect of the business in ways that are impossible to quantify. As a result, introducing change into these foundational systems in the process of modernization can have far-reaching and unintended consequences.

Develop a business case that includes time and effort for training and change management. Involve the application stakeholders early in the cycle. Explain the approach to modernization in a way that is relevant to their roles and responsibilities.


Our Solution: Legacy Forensics

Legacy System Inventory and Analysis Syntactic Analysis

The purpose of syntactic analysis is to build a parse tree of the source code file based on the selected tokens provided by the lexical analyzer.

The parsing uses a special strategy to reduce and simplify the semantic analysis. This enables the analysis of a wide range of COBOL versions and dialects, and embedded statements from other supplementary packages, such as CICS, VSAM, DL/I, and SQL.

The result is maintained by BluePhoenix in the form of schema-based XML and any program can be analyzed in both its input source form as well as its XML form. The XML can also be exported to allow for further specific, external transformations such as XSLT transformations.

This service is designed to give organizations abstract and granular detail on the critical aspects of legacy systems. This goes far beyond a standard assessment- this service delivers valuable data for developers, architects and testers. It plays a key role in providing inventory for the legacy environment, presenting an inventory that can be understood cross-functionally, and providing comprehensive modernization planning strategy and tactics.

Detailed data and reports reduce risk by ensuring all technical use cases are documented and accounted for. This work is automated and precise, saving customers months of time and thousands of dollars in man hours- and ensuring no critical requirements or functionality are left out of the target state design. This data also impacts regression testing, making it more accurate and efficient- reducing time from source to target state.

This service involves four phases:

• Legacy System Inventory and Analysis

• Collaborative Discovery

• Delivery of sample converted code

• Modernization project plan and cost analysis

This compiler-centric approach gives BluePhoenix an automated capability to analyze and understand in detail, an entire system along with all of its components and even reanalyze it in the event of ongoing changes.

In the inventory and analysis phase, the legacy environ-ment is analyzed both syntactically and semantically.

This phase documents the customer environment’s current state and any important dependencies or conditions.

BluePhoenix harnesses proprietary tools to perform detailed control flow and data flow analyses on legacy COBOL applications.

It analyzes COBOL applications, stores the results in an open database repository, and presents the information in a user-friendly way by means of graphs, reports, and external representation formats such as XML.

BluePhoenix’s ability to collect and extract detailed information about an application, to examine it carefully, and to present it in a coherent manner, is based on an engine which is essentially a “smart compiler.”

Screenshot: Program Interaction Diagram


Legacy Forensics (cont’d)

Collecting and Analyzing Information

Semantic Analysis

Analysis Presentation

Once BluePhoenix collects and analyzes the legacy system, the customer is presented with an overview of the operational flow of the applications and their ‘inter’ and intra-program relationships in a collection of visual program interaction diagrams.

These diagrams can be manipulated to represent high-level system views as well as procedural detail.

For example, displayed objects and their relationships can be filtered by type, and the depth of the relationships displayed can be controlled. In addition, when the mouse cursor is placed on a link or entity, a pop-up window appears showing the location of the corresponding code line or the name of the program, respectively.

When links or entities are clicked, the source file is opened in an edit window, allowing for immediate access to the underlying source.

Semantic analysis captures the meaning of the different code components within the source code file and the way they relate to each other. The purpose is to understand the design, rules, and logic that is hidden behind the code.

Understanding the programming techniques that were used by the original programmers and implemented in the code can help in later stages of modernization.

BluePhoenix parses the application’s components, verifies that the inventory is complete, and that they are syntactically and semantically correct.

Each of the entities is compiled, and code fragments that are rejected in this process are highlighted in reports presented to the customer. These code fragments may originate, for example, from source code that doesn’t match the production application. When parsing and analysis are completed, BluePhoenix prepares a final information repository for the application.

After all components are examined and verified, an XML information repository is generated containing all of the information extracted from the application.

The repository contains information about the application’s components, the relationships between these components, abstracted semantic information about each program’s behavior, the usage of data items inside programs, control flow, and more.

The information in the repository can be accessed from any reporting tool that can access XML.

For Java, we also have EMF models (serialized as XMI which is a special type of xml) that are compatible with Object Management Group ASTM: http://www.omg.org/spec/ASTM/1.0/

Screenshot: Repository Information Explorer



Reporting Collaborative DiscoveryIn addition to viewing the analysis information graphically, BluePhoenix offers numerous reports that can be used to understand and document the application. These analysis reports are divided into four categories:

Usage reports These reports specify usage details for each item. For example, a report listing all statements in which a specific variable is used, or all programs (including specific lines inside the program) in which a screen or a file is used.

Resource reports Similar to the resource diagram, these reports list all of the resources of a program, a group of programs, or even specific paragraphs.

Statistics reports These reports provide statistical information such as line counts, how many times a specific screen is used, which file is used most frequently, which program has the most I/O statements, and the ratio between I/O and logic in a specific program.

Complexity reports These reports assist in determining program complexity, a major factor when deciding how to approach modernization with a given program. These reports support both standard complexity analysis such as Halstead/ Cyclomatic/McCabe complexity analyses, as well as heuristic complexity analysis that pro-duces complexity analysis based on simple statement type counts where the customer can determine their own weighting based on the type of statement.

There are hundreds of standard reports available depending on legacy system needs. Customized reports are also available upon request or obvious need.

BluePhoenix holds discussions with the customer and key stakeholders to clarify additional system details, understand and apply project roadmap milestones, or to enrich business rule definitions. These discussions focus on four key contributing elements of the modernization plan:

Business Requirements Includes understanding project timescales, documenting future application plans, reviewing the backlog of errors and enhancements, user interface changes and considerations, and the data warehouse and business intelligence ecosystem.

Application Architecture and Delivery Review the application architecture, external interfaces, file usage and structure, schema structure, batch handling, print and sched-uling management, security management, as well as preferences surrounding the delivery of any proposed risk mitigation solutions.

Testing Plan and Approach BluePhoenix’s extensive modernization experience helps shape a comprehensive testing plan. From guiding the testing process, to enabling an automated test recorder, to providing guidelines and best practices for performance comparison.

Test Recorder enables automated test recording of the source in a UAT environment for performance tuning and comparative testing of the potential target environment. User activity is recorded over time and automated tests are developed by the system based on the observed activity. Test Recorder works by:

- Recording input, output and program flows, with database or in app-only decoupled mode.

- Cataloging code and test coverage, code usage trends, and pinpoints failing code.

- Starting with decoupled code, running without data input / dependencies from the original system to validate code level. Second pass covers database, functions, files and other inputs. Compares outputs and pinpoints errors in code for remediation and retesting.

- Reporting confirmed functionality and use case matches between legacy and target applications if conversion is the preferred risk mitigation solution.

Target Platform, Language and Database A major factor in the design of a modernization project is the pre-ferred target platform, languages, and database. BluePhoenix con-siders preferences from HW, SW, batch, print, security, integrations, DB software & management, to performance and sizing identification.


Legacy Forensics (cont’d)Business Rule Extraction

Modernization efforts present many difficult challenges, but few are as daunting as making key business and systems decisions with very little information about the functionality of the legacy system. After all, part of the reason the modernization process is so important is to evolve systems to a point where the code and logic is maintainable and expandable. BluePhoenix’s toolset provides a window into underlying business rules by locating and extracting them from the COBOL code. This logic mining process is especially important to any necessary redevelopment.

Redevelopment is the process whereby an existing system is mined for its business logic and design information; this information is then used to construct a new replacement system. This is particularly useful when:

Existing legacy code is poorly structured

Uses GOTOs extensively or has been patched so often that quality is a severe problem

Need to cross an “architectural” boundary

Examples could include:

- Transforming procedural COBOL systems to Object Oriented environments such as Java and .NET

- Transforming 3270 driven COBOL applications to Service Oriented Architectures (SOAs), which requires the COBOL application to be restructured into more reusable components

- Transforming applications from “work-flow hard coded” to process driven architectures where the workflow is extracted and becomes external to the application services

Poorly Documented There is no documentation of the current system and the only “specification” available is what is currently running.

In general, a business rule can be defined as specific functionality that is related to a specific data element.

From a technical viewpoint, the main purpose of business rule extraction is to isolate related code that performs a well-defined business function.

These collections of code blocks, called slices, can then be analyzed for conversion into new components. There a number of tactics for determining the code collection that constitutes a well-defined process for inclusion in the slice:

• Data Driven—Backward Starts with a calculated result or its output, and works backward to determine the program flow that handles data assignments and calculations that lead to the result.

• Data Driven—Forward Starts with an input and works forward, finding the data flow that handles the input and other data variables that are influenced by it.



Assessment Report, Converted Code Samples, Project Plan and Roadmap

After thoroughly analyzing the legacy systems and presenting their underpinnings to the customer, collaborating to gain understanding and apply best practices around planning for modernization, and considering business rules extracted by code slicing and flow diagrams, BluePhoenix will present an assessment report, which includes a detailed inventory, analysis presentation, and converted code samples.

Based upon the desired modernization approach, BluePhoenix will develop a comprehensive project plan including:

• Fixed priced proposal

• Description of Project Phases

• Phase level Project Plan

• High-level Target Technical Architecture

• Project Technical Challenges or Risk Factors

• Roles and Responsibilities of each party

By combining logic mining technology, test recording capability, modernization best practices and over 20 years of experience, this service provides organizations that are considering modernization with the information they’ll need to succeed.

No other automated solution on the market today delivers this much background, resources, and environmental intelligence for reducing risk and planning a successful legacy system conversion.



Practical Application: Mergers and Acquisitions

Real Life Benefits of Legacy Forensics: Merrill Lynch

Mergers and consolidations, even though primarily business-driven activities, raise many issues of technology. In many cases, factors preventing the combined companies from going to market faster are directly related to disparate systems.

If one (or both) of the merging companies have legacy systems, our Forensics service can help identify the most efficient strategy for managing, consolidating or migrating systems. Specifically, we can assist with:

Standardization: overcoming issues of consistency between systems, including:

• Different naming conventions • Different versions of languages—for example, COBOL VS and COBOL 370

Operations: issues of mismatched IT systems and methods for accessing them:

• Incompatibility of systems—Operating systems and platforms may be incompatible, such as VAX/VMX

• Different security systems and access methods— for example, CA/ACF2 and RACF

Data Handling: overcoming issues of data compatibility, including:

• Different data locations—Data may not be stored in the same logical location.

• Unacceptable data—Data acceptable in one system may not be acceptable in another.

• Inaccessible data—One system may not be able to access data available to the other.

• Incompatible databases—Each system may use a different data tier for example: ADABAS and DB2

Merrill Lynch (ML) is one of the world’s leading financial management and advisory companies, with offices in 36 countries and total client assets of approximately $1.4 trillion.

ML had all the information they needed about their highly complex mission-critical IT environment, but it was scattered across numerous different applications and configuration files.

With more than 3.3 million lines of JCL code, 79,000 programs, 9 million rows of SMF records, and 130,000+ jobs, they needed a focal point of control for IT management, application groups, and data center staff.

ML wanted to gain a comprehensive, consistent, and easily accessible view of the entire IT system that enabled fast identification of potential inefficiencies and trouble areas. They required comprehensive information on the various software components, their daily use, and the interrelations among them. ML also required full integration of the information within their existing Intranet-based organizational portal.

ML’s goal was achieved in a relatively short time and provided an immediate ROI through cost savings and expedited resolution of production problems and maintenance issues.

Specific benefits achieved include:

• Savings of several million dollars through streamlined operations, including reducing the number of DB2 DASD and DB2 image copy datasets, identifying low usage of vendor utilities and converting to less resource intensive programs, and vendor product elimination resulting in contract adjustments

• Increased productivity by making all information available through a dynamically updated repository that dramatically reduced the time it takes to find data and increased the number of people who can access it

• Improved decision-making through an increased level of automation for real-time analysis based on accurate and up to date information, expedited problem-solving, and facilitated planning

BPHX help translate raw data intrinsic to our business applications into strategic information key to our operations. We are continually finding new applications for this metadata.Howard Goldberg, VP Global Data Management, Merrill Lynch

“”

Companies of all sizes are grappling with aging, complex systems that are costly to maintain and too inflexible to support new business initiatives.

Most vendors are more concerned with selling new systems than helping to retire old ones. It can take a lot of effort to move data off the old system, archive the application’s data and decommission the supporting applications and infrastructure. It can be a challenging project because of lack of documentation or data — or both — but the more legacy applications that are retired, the greater the cost savings in ongoing maintenance. This helps companies meaningfully shift their IT spending to more business-focused initiatives. Further, companies can manage operations more effectively with common technologies and processes. The benefits are tangible, real and achievable- as long as the right steps are taken. In conclusion, consider the benefits this company achieved in moving off a legacy IDMS data tier with COBOL applications.

Conclusion


COST REDUCTION IN SEARCH/DOCUMENT TRACKING

COST REDUCTION IN DEPLOYING B2B/EDI INTERFACES

COST REDUCTION IN SOFTWARE MAINTENANCE FEES

REDUCTION IN HIDDEN OPERATIONAL COST

REDUCTION IN TRANSFER FEES

96%

65%

60%

50%

30%

SOURCE: COMPUTERWORLD 2012 FINANCE FORUM


Ideal Solution Scenarios

Migration of legacy applications and databases from mainframe to distributed systems, need to maintain business logic of legacy systems

Integrate legacy data with modern platform to support BI and/or Analytics efforts

Proper documentation of legacy systems, dependencies and risk factors

Cost reduction for existing mainframe apps

Translates application code and database while keeping existing logic and function-ality. Reduce risk/cost without ground-up redesign, keep flexibility of target platform. Intelligent testing validates full application functionality upon delivery.

Flexibility to choose target language and database solution.

Software powers secure, audited integration between source and target. No technology lock-in: full flexibility of target platform and BI/analytics solution of your choice.

Automated Indexing of legacy code and da-tabases. Reduces risk of modernization by cataloguing Technical Inventory, Use Cases and Business Rules.

Empowers customer to choose what work-loads to run off the mainframe. Reduces MIPS immediately, does so in a low-risk manner controlled by customer.

Application Modernization, Database Modernizaion

Database Modernization

Legacy Forensics

Application Modernization

COBOL, NATURAL, CA GEN, ADSO, PL/1, VSAM, ADABAS, IMS, ICL

Java, C#, SQL Server, DB2, Oracle

VSAM, ADABAS, IDMS sources; SQL Server, DB2, Oracle targets

COBOL, VSAM, ADSO, NATURAL, ADABAS

COBOL appli-cations, VSAM databases

BluePhoenix: Company Overview

BluePhoenix ATLAS PlatformBluePhoenix’s ATLAS (Automated Translation and Legacy Advancement System) Platform reduces risk and solves business problems specific to the legacy application lifecycle. ATLAS:

• Is applicable COBOL applications, CA GEN, Natural, PL/1 and more • Is applicable to legacy databases such as IDMS, ADABAS, VSAM and more • Generates fully maintainable Java and/or C# code • Enables data migration and/or integration with SQL Server, Oracle and/or DB2 • Doesn’t restrict choices for target infrastructure- works in public or private cloud • Is a proven solution being used by the world’s biggest and most transaction- intensive brands, including:

Business Challenge BPHX Service How It Works Applicable To

BluePhoenix Solutions Ltd. (NASDAQ: BPHX) is the leading provider of legacy language and database translation. The BluePhoenix portfolio includes a comprehensive suite of tools and services for automated database and application migra-tion. Leveraging over 20 years of best-practice domain expertise, BluePhoenix works closely with its customers to minimize risk and provide a clear path from legacy platforms like VSAM, IDMS, IMS, ADABAS and others to modern solutions like SQL, DB2 and Oracle Database. BluePhoenix customers come from diverse industries and vertical markets such as auto-motive, banking and financial services, insurance, manufacturing, and retail. BluePhoenix maintains global presence in the USA, UK, Italy, Romania, and Israel.

TARGET STATEAGNOSTIC INTEGRATION

FRIENDLY

AUTOMATED TRANSLATION

AUTOMATED FUNCTIONALITYTESTINGIMPROVE

PERFORMANCE

KEEP LEGACYLOGIC

Documents

Legacy ForensicS€¦ · · 2014-03-25technologies and methods used in legacy systems development, ... it is difficult to understand why businesses continue to use such old technology