Information Systems Transformation: Architecture-Driven Modernization Case Studies (The MK/OMG Press) [Paperback]

William M. Ulrich (Author), Philip Newcomb (Author)

Book Description

Publication Date: March 8, 2010 | ISBN-10: 0123749131 | ISBN-13: 978-0123749130 | Edition: 1

Every major enterprise has a significant installed base of existing software systems that reflect the tangled IT architectures that result from decades of patches and failed replacements. Most of these systems were designed to support business architectures that have changed dramatically. At best, these systems hinder agility and competitiveness and, at worst, can bring critical business functions to a halt.

Architecture-Driven Modernization (ADM) restores the value of entrenched systems by capturing and retooling various aspects of existing application environments, allowing old infrastructures to deliver renewed value and align effectively with enterprise strategies and business architectures.

This book provides a practical guide to organizations seeking ways to understand and leverage existing systems as part of their information management strategies. It includes an introduction to ADM disciplines, tools, and standards as well as a series of scenarios outlining how ADM is applied to various initiatives. Drawing upon lessons learned from real modernization projects, it distills the theory and explains principles, processes, and best practices for every industry.

* Acts as a one-stop shopping reference and complete guide for implementing various modernization models in myriad industries and departments.

* Every concept is illustrated with real-life examples from various modernization projects, allowing you to immediately apply tested solutions and see results.

* Authored by the Co-chair of the Object Management Group (OMG) Architecture-Driven Modernization (ADM) Task Force, which sets definitive systems modernization standards for the entire IT industry.

* A web site supports the book with up to date coverage of evolving ADM Specifications, Tutorials, and Whitepapers, allowing you to remain up to date on modernization topics as they develop.

Editorial Reviews

Review

"Ulrich and Newcomb's book offers a comprehensive examination of the challenges of growing software-intensive systems. Every system has an architecture, but as the authors explain, it is only by continuous, intentional architectural transformation that one can attend to costs while simultaneously creating a mechanism wherein innovation may flourish.

I enjoyed the many case studies. Every circumstance is unique, but the authors have offered up best practices for systems modernization from their experience. Their focus on architecture as an artifact for governance is sound, but they go far beyond the technical issues and address many of the social and economic practices that help one evolve a good technical architecture.

From the moment one writes a line of code, it becomes legacy, and that legacy accumulates. Whether it becomes a cause of innovation inertia or a source of future value is a factor of how it is continuously modernized."

Grady Booch IBM Fellow & Chief Scientist, Software Engineering in IBM Research

"Estimates by internationally-known researchers of the worldwide legacy code base is now approaching a half-trillion lines.  That only counts so-called "legacy languages" like COBOL--which drive the world.  Add in database schemas, configuration files, and legacy data and the amount of hidden data adds up.  This "dark information," like the dark matter of the universe, is critical to our understanding of our world, we can't simply ignore it.  Our best hope is to update it, bring it into modern systems, and keep it alive and vital.  Fortunately, nobody knows the modernization landscape better than Ulrich and Newcomb, and this in-depth, practical guide is indispensable to planners & practitioners faced with the legacy modernization challenge.  Architecture-driven modernization is the best hope for "bringing back" legacy applications & information so it can be successfully applied & reused, and this book explains how to plan, develop & manage modernization from every angle." Richard Mark Soley, Ph.D. Chairman and CEO, OMG

From the Back Cover

Every major enterprise has a significant installed base of existing software systems that reflect the tangled IT architectures that result from decades of patches and failed replacements. Most of these systems were designed to support business architectures that have changed dramatically. At best, these systems hinder agility and competitiveness and, at worst, can bring critical business functions to a halt.

Architecture-Driven Modernization (ADM) restores the value of entrenched systems by capturing and retooling various aspects of existing application environments, allowing old infrastructures to deliver renewed value and align effectively with enterprise strategies and business architectures.

This book provides a practical guide to organizations seeking ways to understand and leverage existing systems as part of their information management strategies. It includes an introduction to ADM disciplines, tools, and standards as well as a series of scenarios outlining how ADM is applied to various initiatives. Drawing upon lessons learned from real modernization projects, it distills the theory and explains principles, processes, and best practices for every industry.

See all Editorial Reviews

Product Details

• Paperback: 456 pages
• Publisher: Morgan Kaufmann; 1 edition (March 8, 2010)
• Language: English
• ISBN-10: 0123749131
• ISBN-13: 978-0123749130
• Product Dimensions: 1 x 7.3 x 8.9 inches
• Shipping Weight: 1.7 pounds (View shipping rates and policies)
• Average Customer Review: 4.3 out of 5 stars  See all reviews (15 customer reviews)
• Amazon Best Sellers Rank: #1,356,596 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Most Helpful Customer Reviews

3 of 4 people found the following review helpful

4.0 out of 5 stars Systems modernization scenarios, tasks, and case studies November 20, 2010

By Erik Gfesser VINE™ VOICE

Format:Paperback|Amazon Vine™ Review (What's this?)

Since the marketplace is largely absent of texts discussing the modernization of software systems architecture, this reviewer did not know what to expect from authors William M. Ulrich and Philip H. Newcomb. In addition, the space of this topic can be very large depending on how it is defined. In the opinion of this reviewer, the best part of what the authors present are the ten case studies, which comprise the bulk of the content, but the initial chapters and concluding chapter provide some initial high-level guidance for managers looking to pursue modernization projects for the first time.

While the case studies presented here offer a variety of scenarios, the potential reader should note that there are some commonalities across these scenarios as well. The tooling and processes utilized across these case studies are shared to a large extent, although there is definitely variation depending on the systems and firms involved. Newcomb is CEO of The Software Revolution, Incorporated (TSRI), and so some of the commonality is due to the tooling and services provided by his firm, for example. The variation provided is largely due to type of system, associated technologies, and modernization approach.

During their initial discussion of challenges facing most enterprises today, the authors note that there is "a lack of understanding by executive teams regarding the impact of these issues and the actions that can be taken to address them for the betterment of the business environment" and that "it is of great concern that software and data assets are largely a mystery to management and planning teams". In following up this discussion with salvaging or rehabilitating legacy systems to provide business value, the authors offer "architecture-driven modernization"....

Architecture-driven modernization is defined by the authors as "a collective set of tool-enabled disciplines that facilitate the analysis, refactoring and transformation of existing software assets to support a wide variety of business and IT-driven scenarios". Ulrich later discusses "the four corners of modernization", which consist of modernization scenarios, modernization tasks and disciplines, modernization technologies, and modernization standards, and argues that scenarios form the basis for modernization roadmaps.

Common modernization scenarios include IT portfolio management, replacement/rewrite, COTS package deployment, architecture consolidation, Model-Driven Architecture (MDA) migration, SOA transformation, data architecture migration, user interface refactoring, application improvement, language/source artifact transliteration and platform migration, and data conversion. Ulrich argues that management should be creative and look at a mix-and-match approach that addresses their requirements, and as a consultant who has been a participant in several such endeavors, this review wholeheartedly agrees with this assessment.

As an architect, this reviewer especially enjoyed the following case studies: "Modernization of the Eurocat Air Traffic Management System (EATMS)", "PowerBuilder/4GL Generator Modernization Pilot", and "Veterans Health Administration's VistA MUMPS Modernization Pilot". Note that each of the ten case studies was written by a different set of authors, so the subject concentration and writing style differ greatly between each. Diagram and table effectiveness also varies considerably, and it is no accident that apart from the subject matter of the three case studies sited, these case studies also excel in these areas.

The first of these three spends considerable time discussing all of the steps performed during transformation of Ada 83 code into C++ and Java (the Java solution won). concentrating on performance and duplication of the exact functionality provided in the original system. In contrast to low-level detail, the second of these three concentrates at the high-level, providing a high number of relevant architecture diagrams (to which this reviewer is partial). This reviewer enjoyed the third of these case studies from a business domain perspective, since it concentrates on health care system modernization.

While no book can offer detailed advice specific to the challenges a given potential reader might face in this space, in the opinion of this reviewer the authors offer solid introductory advice on how to start tackling a modernization project, and provide a wide enough variety of case studies that readers can get a feel for what they might encounter in pursuit of such a project. The discussions that the authors provide here definitely delve into the technical, but it is perhaps managers that will benefit the most from a reading of this book, especially the sections that discuss assessments and scenarios and issues underlying traditional approaches such as greenfield replacement and use of COTS software. Read more ›

2 of 3 people found the following review helpful

4.0 out of 5 stars Alternate Approach for Massive, Aging, Business Critical Software September 25, 2010

By E. Griffin VINE™ VOICE

Format:Paperback|Amazon Vine™ Review (What's this?)

Information Systems Transformation: Architecture-Driven Modernization Case Studies addresses the challenge of monolithic and aging, yet business critical software systems. The book focuses on modernizing the application and data architectures of these massive and fragile systems as an alternative to the common approaches of re-writing, replacing with packaged software, or wrapping in middleware.

Part one explains architecture-driven modernization, its potential value over other approaches, creating a strategy, standards, and roadmap, along with the use of scenario creation. The second portion of book consists of ten in-depth case studies, spanning a range of technologies and organization types. The final chapter is a brief synopsis of initiating and sustaining modernization initiatives.

The audience for Information Systems Transformation: Architecture-Driven Modernization Case Studies is technology architects, application developers, system engineers and others with a strong interest in addressing the challenge of legacy systems. The first two parts of the book, especially the case studies, are very good, providing comprehensive information illustrated with charts and tables. The final chapter is very brief, containing superficial information about the reality of implementing modernization.

This book is recommended for anyone deeply interested in the topic, and system architects, while practitioners will want to supplement with additional reading about successful technology initiatives and centers of excellence.

4.0 out of 5 stars Great case studies walk you through the author's model of modernization April 6, 2013

By D. Brennan TOP 1000 REVIEWERVINE™ VOICE

Format:Paperback|Amazon Vine™ Review (What's this?)

I am fortunate enough to work in a mid-sized organization where we have a lot less legacy software than those described in this book. That being said, I read this book so that I could get a sense of where we might be headed and to see if I could figure out a way to avoid the bloated, inefficient, IT architecture that plagues most companies today. For years it has struck me how much of a company's IT budget can be spent on simply maintaining existing systems. In some cases maintenance can account for 85% or more of your IT budget. That doesn't eave much for new initiatives.

In my case, agility is a key requirement for every function within our business. Our markets, products and customers change often, and we need to be able to respond. Being responsible for a legacy IT system that does not respond at the speed required is one way to find yourself looking for a new job.

The authors tackle technical details, but also spend time discussing social and business realities that can cause problems, as well as techniques for getting through them. The case studies in particular help you see how others have gone through the same issues you are facing. I like the case study approach and wish that more IT books incorporated this approach.

5.0 out of 5 stars Critical assistance in modernizing legacy systems April 5, 2013

By Charles Ashbacher HALL OF FAMETOP 500 REVIEWERVINE™ VOICE

Format:Paperback|Amazon Vine™ Review (What's this?)

In the early 1990's, I worked for the University of Iowa in the Department of Physics. The great James Van Allen was a pioneer in the exploration of space and the department was also a leader in using computers in analyzing the data. The language used was FORTRAN and a great deal of the code that I worked with had been originally written in the 1960's, a time when there were few best practices for code development. Variables were generally called X1 and Y1 and the routines were written by experts in the physics of magnetic fields, so they needed no explanation of the expressions. I. e. there was often little documentation.
A companion program that I worked on was the transferring of legacy data on 7-track tapes to 9-track tapes and optical platters. Some of the equipment was relatively ancient and occasionally did not perform as well as desired (much cursing).
This experience made me appreciate two things:
1) How difficult it can be to make sense of legacy code and structures that were constructed generations ago in terms of software development.
2) How much legacy data there is that still can be mined for value yet how difficult it can be to convert it into a modern format. I was told that the U. of I. had the second largest stockpile of data on magnetic tape in the world and after walking in the warehouse, I did not doubt it.
This experience helped me appreciate all aspects of the case studies presented in this book. When first presented with the monumental task of modernizing a legacy system, it is easy to shudder, utter a few curse words and consider entering another line of work. With this book as a backdrop, the size of the task may not be reduced, but the complexity is somewhat unraveled....
The case studies here do not involve the replacement of systems, but on modernizing them. By examining the case studies it will be easier for the worker to recognize and work within the fundamental architecture of the legacy system and develop a plan to build on what is right about it That is a very effective way to start with a fragile system with virtual gray hairs and wrinkles and turn it into a robust system capable of growing and surviving changes in hardware and software platforms.
When I was working with the legacy code, I learned to recognize the formulas for magnetic fields, which of course made up the underlying architecture of the system. Based on this recognition, I was better able to convert the code into modern versions of FORTRAN and occasionally translate it into C. This book will show you how to do something similar in much larger and more complex systems. Read more ›