SOA filling the Gaps

Agile Methodologies are used frequently in modern systems development. Readers of this blog, as well as many people who do not read it, know that the rate of Business changes was accelerated and Information Technology systems should be flexible in order to adapt  quickly  to the Business changes. Agile Methodologies focus on high priority requirements. If you would use classic Waterfall methodologies, probably the requirements will change before you complete the Analysis. According to an old Aberdeen Group's survey, published a decade ago, the time for implementing BPM is more important than the implementation's costs. The results of the Aberdeen Group's survey implies that  Agility was required in implementing BPM. Those days, it is required more than it was required ten years ago. Forrester's analysts  Clay Richardson and John R. Rymer wrote in 2013: "The Mantra for BPM has always been "start small, think big, move fast!" However, most teams ...

I am not happy to Revisit a Vendor Survival post saying that my prediction that a vendor will not survive was correct (for example, SUN ). If a vendor is not a monopoly , I am not happy to find that the probability that it will survive is lower than it was ( Apple , HP  etc.). Even if it is a monopoly in specific markets and not a monopoly in others, I am not happy to find that its Survival probability is lower than it was ( Microsoft ).  The reason that I am not happy is that competition is good for my customers: They can buy better products and pay less. This post is out of the ordinary. The probability that Software AG will Survive is now higher than it was when I wrote the post: Will Software AG Survive until 2019?      Software AG's Business Lines In my previous Vendors Survival post on Software AG, I analyzed its two major Business Lines: 1. Mainframe DataBase , Development and Integration products 2. BPM and SOA products I will repea...

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