Forrester Application Development & Program Management March First Look

This is my response to Forrester’s Jeffrey Hammonds March First Look:

Dear Jeffrey,

I have read your March 20th First Look several times now. For some reason I kept it in my inbox.

Now when I was about to clean it I found what was bothering me. Everyone at Forrester is talking about what the NEXT FIVE years will bring in terms of application development technology to enable change. You say that developers need to develop means to enable change, because of the fourth paradigm of SOA, rules and CEP will enable that.

What I disagree with: First, programming in the sense of coding for applications is too complex and there is nothing anyone can do to make change easier. Second, agile processes will never be delivered by coded applications and best-practice release management. It requries a life-cycle repository but that can’t be used with coded applications, because there is no 100% roundtrip from model to code and back. Third, why should anyone need to wait for five years?

You also mention that RIA will be the next big thing and here I am not in disgagreement. It should however not be a programming model like Adobe Flex which will once again resist the change you are asking for. What I see missing in most process applications is however not a cutsy web-GUI but the core information carrier – content! Business documents are not BLOBs, because they typically contain data that has to be mapped to the data models of the business process. Why does NO ONE talk about that? There is a huge amount of coding going on to integrate MS-Word and PDF and OCR-images and all that code will resist change! XML, XSL and other acronyms do not solve that problem as promised. It all requires a lot of code to work.

The future that you are talking about is here and has 200 corporate users with up to 3000 seats!
a) The ISIS Papyrus Platform has a model&rule-to-production paradigm via its WebRepository to deploy powerful versioned application models time-synchronized to any number of production servers.
b) Papyrus uses a state/event model for processes rather than an limited flowcharts.
c) Business rules can be created to control processes in terms of compliance.
d) Processes are created by teaching the complex event patterns (CEP) that define the process progression to our User-Trained Agent.
e) The metadata model of the platform is populated via the Adapters (DB, MQ, SOA) with federated business data and thus directly available to the users, content, rules, and the CEP functionality. This enables real-time business data to be used for process decision making without the need for a data warehouse.
f) Inbound and Outbound content is handled by our ECM and DOM modules and imbedded into the context of the process/case.
g) User frontend is either the configurable Papyrus Desktop our the new Papyrus EYE web presentation that uses Flash and is deployed also through the repository. In difference to Adobe Flex there is not a single iine of Java or .NET code needed to trigger a process from a business application data set, create the related content and present it to a Web front end.

There is more on our Website and we have our OpenHouse in Dallas and Vienna coming up and you are invited to see this for yourself. We may be at the Forrester IT-Forum if things work out, so please drop by.

Sorry for budging in on you and thanks for reading this!

Freundliche Grüße,
With my best regards,
Max J. Pucher
Chief Architect ISIS Papyrus


Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s