While I am not a typical Enterprise Architect as I am responsible for our products at ISIS Papyrus Software, I face the same problems as someone being in charge of Enterprise IT. I am in fact linked to EA architects problems with our solutions. Let me point out a few things that I see as problematic with current EA thinking and analyst stance related to the subjects of application life-cycle management. These are essential architectural issues that are not enough covered and therefore I will also cover them in my upcoming book.
• Re: Effective planning to optimize shrinking IT budgets
Lets face it, IT projects have neither become simpler nor more successful. Rather the opposite. More than half of IT budgets are maintenance cost. More than half of projects still get canceled. More than half of project budget is manpower. And more than half of software cost is ‘cost of sales’ at the vendor. That leaves around five percent of IT budgets actually going into software development at vendors. With current technology being sold in current market conditions that is hard to change. No amount of EA planning will improve that situation. There is a huge amount of money going up in smoke. Why is anyone surprised? Things have to become way simpler!
• Re: Agility with SOA and BPM (Arrrrggh!)
Very soon this will make me want to scream. The reason business process management (BPM) implementations and service-oriented architecture (SOA) are white hot is that there is huge amount of money spent on marketing! Neither BPM nor SOA make a business more agile. SOA makes IT just a lot more complex (and thus rigid) and BPM is about long and expensive process analysis that is dated the day it is finished and outdated once implemented. Large scale BPM deployment is a failure where ever you look because no one has a handle on metadata, versioned deployment, and process interdependencies. The huge effort of putting SOA in could only make sense with large scale BPM and therefore these two are doomed together. The reason that everything is being outsourced is the immense cost of complexity. Obviously SOA life-cycle management is important, just like life-cycle management of eveything else. It makes however no sense to manage SOA and not manage BPM as an integrated element of the overall application. In all cases that I have seen putting in SOA and BPm meant substantial Java coding, that again is managed some place else. Forget agility …
• Re: The bottom line depends on new capabilities.
I could not agree more! IT is stuck in mud, soggy with programmer’s and user’s tears. True innovation is the name of the game. Not product buying and renaming as most vendors do. We at ISiS Papyrus do actually deliver game-changing technology. Do enterprise architects care much? Most of them are in CYA mode and if at all they take some vendor from the ‘Magic Quadrant’ that is chosen from past market share analysis … not really the new stuff. Please, don’t use Microsoft and innovation in the same sentence. They have long forgotten how to be innovative. They only know how to spend marketing billions.
How do we address thise issues at ISIS. What is so innovative about our Papyrus Platform?
Papyrus WebRepository promotes ‘Experience Sharing’ in the enterprise rather than rigid planning, and combined with the consolidated BPM, CRM and ECM capabilites in its own transaction and OR-DB engine it is a unique, innovative solution. We are only a medium size, privately held company, but have around 200 implementations in major organizations worldwide since its availability in 2001. The largest are 3000+ workflow users.
The ISIS Papyrus WebRepository has full life-cycle (DEV-TEST-PROD) project management with alerts and reports. It (project) manages all aspects (analysis, design and implementation) of the business process as well as the service registry, regardless of its implementation … SOA or not. While we can easily manage UDDI and WSDL files and their parameters and use in projects, but we get chosen in most cases because SOA is not mandatory. I yet have to see a company that has a readily available SOA interface that we can simply latch onto. A change in (SOA) interface metadata is propagated automatically to all processes and process elements, such as rules, user interfaces and created content! The user interface for the BPM implementation is much more powerful and extensive than Adobe Flex and runs in either Flash or the Papyrus Desktop with the same definition. The integrated UML capabilities of the WebRepository give it enough power for enterprise architecture planning. No Java, no .NET, no SOA, just process oriented applications that are simple and manageable!