Skip to main content

Thomas Mercer-Hursh's blog

Types of Transformation

There are as many different kinds of transformation projects as there are companies considering them – every project has its own special issues based on the state of the application at the start, the business drivers, and the desired goal. But, we can make some broad categorizations in order to understand something about some broad categories of approach.

Two approaches are characterized by modest, short term investment and focused goals.

More About Business Drivers

Business drivers for Transformation come in many different flavors and the perception of them often changes during the needs assessment process. At the start of the assessment process, a need may be obvious and well-recognized by much of the company or it may be an obscure problem, perhaps recognized by only one person and it may not have occurred to that person better software could fix anything. Drivers may be common to many companies or very idiosyncratic to a specific company and its own business processes.

Business Drivers for Transformation

Because of the atmosphere of comfortable inertia around legacy ABL applications, they often experience a sort of benign neglect – small, short-term, immediate projects get attention and larger scope issues never quite make it onto the table. A developer might bring up one of these more general issues in response to something in an on-line forum or conference. Or an astute manager might be aware of the issue from prior experience or reading.

Exchange 2008 Presentation

"Modeling Existing ABL Systems with UML" was given at the Exchange 2008 meeting in Paris. It discusses the current state of development of out ABL2UML tool.

Modernizing Legacy Code - Getting Started

"Transformation" has become a popular term in the ABL for various kinds of application modernization -- moving to a new User Interface (UI), implementing a Service-Oriented Architecture (SOA), evolving toward the OpenEdge Reference Architecture (OERA), and other projects directed toward upgrading old versions of legacy ABL applictions. Today's ABL is just not the same language it was back 15-20 years ago when many ABL applications were first written and our ideas about good architecture have, if anything, evolved more than the language.

Syndicate content