ISIS Papyrus Software

Adaptive Application Development with Papyrus

In key function, markets on November 29, 2010 at 9:37 am

It is actually not recent news that business application development as it has been practiced over the last two decades or so is unsatisfactory for both business users and IT departments as well as for the businesses as a whole that are supposed to be supported. What is new is that this general discomfort is voiced increasingly more often and more notably.

Typically those business applications are built on static models with heavily customized code and just cannot cope with the flexibility and the dynamic changes required by most businesses today. Information and meaning is hidden in forms and other design artifacts and completely isolated from users’ tasks and activities. Though the design problems in this sort of application development and the subsequent costs of maintenance and upkeep with changing requirements are obvious and well-known it appears as if there is still too much reluctance to get rid of such not-even-near-good practices for the perceived sake of “maturity” and other pretexts.

The Papyrus Platform from ISIS Papyrus by contrast is purely standard software that is not being customized for individual customers. It uses a model-preserving application technology to avoid programming projects. It is easily integrated into legacy systems by loosely coupled messaging interfaces to remain flexible, platform independent and upward compatible. Applications are defined and loaded into the platform as so called Framework Apps. Because the application is defined through object models and rules that are also fully documented in the central repository  it can be maintained by non-programmers and to some extent even by business users, thus providing substantial savings on cost and resources. The ease of maintenance is referred to as adaptive and means that business users can make a permanent changes (if authorized) to the process template during the execution of a process instance and thus create a new process variant. This again offsets IT and shifts collaboration between users and IT to a more strategic level in the business’ best overall interest.

%d bloggers like this: