SOA filling the Gaps

Why SOA is implemented by more enterprises than BPM ?  SOA is an Architecture, so an enterprise may use an Architecture or not.  Many Enterprises without any architecture, begin their SOA initiative, when SOA was only Hype and buzzword. Other Enterprises followed when it matured. Some realized measurable SOA benefits.  Unfortunately, many of them executed it wrongly, and therefore their SOA benefits were limited or even non-existent.  Managing Business Processes is not an option it is a must . Therefore Enterprises managed their Processes manually or by usage of  code  embedded in Systems' Business Logic Layer. It is difficult to convince them to change their Process Management practices by implementing BPM. The company's management team may use the slogan: If it is not broken do not fix it.   The significant value of BPM is not Business Process Automation. It is Business Process Change or Improvement or Flexibility. In order to change a Bus...

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  ...