Skip to main content

Modernization with SOA – The EDS way



    Arie Amit and Eyal Kot presented EDS Modernization with SOA approach and practices in the 21st meeting of the SOA Forum of the Israeli Association of Information Processing on May 14th.
Arie is Business Development and Management Consulting of EDS Israel.
This post describes Arye's presentation about Business aspects and EDS approach to Modernization.

   The following bullets summarizes Arie's presentation.
 

Business Value of Modernization


  • Current Legacy systems include valuable assets; however the architecture is too rigid. Modernization is a key for transforming these assets to Agile solutions enabling the enterprise to respond to business changes and needs.
  • System Maintenance is about 80% of the IT Budget. Maintenance of old Legacy systems is expansive. After Modernization Maintenance costs will be reduced so higher percent could be allocated to Development and Innovation.
  • Omitting redundant systems developed by different departments.
  • Reducing Risk level due to diminished legacy skills.
  • High cost ineffective integration mechanisms are a barrier for fulfilling Business needs.
  • The goal is transforming the organization to a Responsive Organization

The Journey

  • Transition to SOA is part of The Journey towards Agile Platforms.
  • It includes Agile Enterprise (e.g. SOA), Agile Infrastructure (e.g. Virtualization) and Agile Applications (Standard, Open, Modular etc.).
  • Organizational factors such as Maturity should be considered
Modernization stages
  • · Definitions & planning: Mapping current assets, Roadmap etc.
  • · Managing the Journey: Business Architecture, Applications Architecture, performing the Modernization endeavor.
  • · Agile Enterprise (SOA, Business Processes, Vertical models etc.)

EDS's Approach


  •  Top Down
  •  Changing infrastructure to partners' infrastructure products (Microsoft, EMC, Oracle, SAP, Sun, Dell, Borland, CA, Cisco, Tibco etc.)
  •  Focus on Large Enterprises and on Outsourcing
  •  Gradual transition according to Roadmap and not Big Bang
  • The 7 Res: Re-learn (analyzing and understanding components, thinking of Reuse candidates), Re-host (migration to new platforms), Re-Factor (current code optimization), Re-interface (web based interface), Re-architect (SOA), Replace (replace Legacy applications by packages or new applications), Retire (applications retirement).

  • Critical Success Factors: Business Management commitment, Pragmatic approach (Best Practices, Methodologies), continuous plan adaptation, Budgeting next Modernization steps by savings from previous steps of the modernization endeavor.

Q & A


The following issues were raised by forum participants:
  • Organizational maturity.
EDS assess the maturity as part of the first steps based on a Maturity Model.
  • Organizational Culture changes and other organizational changes as part of the Modernization endeavor.
These changes are usually required during the transition process. The organization is maturing
gradually as described by the Maturity Model.

  • Partial Modernization
It is possible to implement part of the Modernization process as cited above. EDS defined and
is deploying autonomous services for partial implementations.


My Take


  • Modernization Value Proposition as presented by EDS is commonly presented by most SOA experts as SOA initiative Value Proposition.
  • Modernization as defined by EDS is not SOA only. Transition to SOA is a significant part of the Modernization endeavor in order to build a Responsive Organization and to get benefits of Agility.
  • A full implementation of EDS's methodology and practices is not a Panacea. It is a multi-years endeavor and high resources consuming. For some Enterprises it is a good choice but for others it is not.
  • It is not easy to justify this kind of endeavor. Some organizations should begin with addressing Pain Points by SOA project, which could be afterwards extended to a SOA initiative. Recently I read an Oracle SOA Case Study titled as: SOA by Accident: A successful point deployment of BPEL led to a SOA initiative.
  • Replace: is it necessary to replace platforms?
  • Replace: On which stage do you replace platforms: during transition to SOA or after completing the transition. The preferred approach is to postpone replacement after advanced SOA implementation stages. Afterwards a gradual transparent is a possible method. Sometimes maintaining current platforms could be inefficient, expensive or impossible.
  • EDS Modernization best fit could be large enterprises implementing the complete model and using previously EDS's services.
Labels:

Comments

Post a Comment

Popular posts from this blog

The mainframe: still alive and kicking

Recently, I was interviewed by  Pcon   (unfortunately the link points to an Hebrew only site) as part of debriefing on Legacy Systems.  Pcon is an Israeli company investigating IT topics by quoting professional articles and interviewing experts. They publish the results of the investigations including practical recommendations. This post is mainly about topics raised by me during the interview, but not included in the debriefing, which will be published.    What are Legacy Systems? The term Legacy Systems refers to old application systems and/or veteran technologies still in use.  Usually, the term Legacy Systems is associated with: 1. Mainframe Hardware e.g. IBM System z and its Operating Systems or Proprietary Servers and Operating Systems such as HP Alpha and OpenVMS Operating System, IBM AS/400 and OS/400   Operating System. 2. Development and Production Environments, e.g. COBOL , Natural and DBMS systems such as Adabas  ...
16 comments
Read more

Will Business and IT Aligned?

For decades we are talking about closing the gap between business and IT , but the gap is still as wide as it was. In the beginning of the ERP era, we focused on aligning Business Processes and Core Systems, but in most enterprises we failed. SOA was the next alignment promise: defining the SOA Services in Business boundaries instead of Technical boundaries, should narrow the gap. However, despite of SOA Business Value ( Agility and Reuse )  in most enterprises,  the large Business-IT Gap remained as large as it was.  The IT Community aimed at the next alignment attempt: SOA is technical and BPM is its Business related complement.  Will the current BPM based alignment attempt succeed? I do not know, but Nick Heath's article  titled: Stop doing what the vendors tell you, CIOs told , published in  Tech Republic , suggests that the root of the problem is not Technological .   Stop Doing What the vendors Tell You Nick Heath's article is based ...
11 comments
Read more

Vendors Survival: Will Software AG Survive until 2019?

This post is another post in the Vendors Survival series following posts on Microsoft , Google , HP , Sun and EMC . On July 14 th Software AG and IDS Scheer announced that Software AG is going to take over IDS Scheer . The intended acquisition is an opportunity to add another post in my Vendors Survival posts series. A brief history of Software AG Mainframe products Software AG is larger than any German software company except SAP . It was established in the Mainframe age (in 1969). I worked with many customers, who used and some of them are still using, its two flagship products Adabas and Natural . Although these products support many platforms, their main platform is IBM Mainframe. Adabas is a database and Natural is a development environment. Like other pairs of Database and Development Environment in the mainframe environment (e.g. Ideal and Datacom , Mantis and Supra) build by the same vendor, they are tied together. As a result, although it is possible t...
8 comments
Read more