Is it possible to manage a legacy system in a modern way?
"Legacy applications are a goldmine of valuable business rules and design intelligence."
"Modern developers want nothing to do with RPG or the AS/400 other than get rid of them."
You've probably heard these seemingly conflicting statements.
My theory is this:
So is it possible to manage a legacy system in a modern way?
Business Processes, Business Rules, Business Data
Gee, you would think it's all about the business!
Well, it is, of course, and new tools and methodologies reflect that. IBM's own leading tools focus first on Business Process Management (BPM) and then WebSphere Lombardi for implementation; they also use iLog as a Business Rule Management System (BRMS).
There are big benefits to defining systems in a language closer to business terms, rather than in programming terms. Less translation means faster development, fewer errors, truer modeling, better comprehension, and improved communication.
That's great for new development, but what about legacy applications?
Advanced Paradigms for Legacy Systems?
While most legacy IT people think of their systems in terms of objects and lines of code, there's the opportunity to automatically translate much of the system back to being closer to business terms.
Here's the important point:
(For a deeper look at using business rules in legacy systems, see the Visual Guide to Business Rule Reuse.)
Most of the business rules and data model rules in your current system will also be found someday in the successor system. Here's the concept illustrated:
Figure 1: Business and data rules stay with the system. (Click image to enlarge.)
The IT Trustee
As managers of software applications, IT managers are trustees of these business rules and data model rules. These are the things that businesses truly care about. How many IT managers of legacy applications can list their business rules? Or confirm that they're accurate? And consistent?
Because of the way programming has evolved, legacy applications are managed in a programming-centric manner, rather than business-centric.
But that's not the future. Nor should it be the present if there is any hope of realizing the gains available from BPM and BRMSes.
It's the business-centric view that leads to a logical, informed strategy about future system directions.
Prepare for Tomorrow's System by Improving Today's System
That heading sounds like a noble thought that never quite goes anywhere. You have to make it go somewhere.
If you've understood the essence of this discussion, then you've understood that:
The business rules you're managing today are the business rules you'll be managing tomorrow, whether they're in your current application or its successor. They will evolve, to be sure, but mostly they are the same.
"What gets managed gets improved."
—Bill Hewlett, founder Hewlett-Packard
Here's the question for managers of legacy applications in RPG, COBOL, or CA:2E:
Manage a Legacy System in a Modern Way
This may sound wonderful but impossible. But it can in fact be done by using an advanced paradigm product that enables recovery and reuse of application design elements, such as business rules, data model rules, and business processes: static analysis and design recovery tools.
For 25 years, Databorough has been building and deploying increasingly advanced versions of the X-Analysis tool suite to extract, analyze, and reuse information from legacy RPG and COBOL applications. In recent years, the product has evolved to where it specifically extracts business rules, data model rules, and business process information, thereby enabling a move to a modern business-centric approach and even assisting in automatically rebuilding these designs with modern technologies and methods.
Time to Rethink
By adopting a more business-centric system perspective, you begin to chart a more productive path to the future, whether it's to improve your current IT processes or lead the way to new systems.
Leading legacy organizations are leaving the old programming-centric view of objects and lines of code and moving to a business-centric view of business rules, data model rules, and business processes, and charting a logical, informed course to the future.
as/400, os/400, iseries, system i, i5/os, ibm i, power systems, 6.1, 7.1, V7, V6R1
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online