www.aspnews.com/analysis/analyst_cols/article.php/582001
|
By Phil Wainewright February 7, 2001 The next phase in the evolution of packaged software rental takes the critical, revolutionary step that breaks with the past. It leads to an era when applications are set free from the software that binds them to specific vendors and providers. Where software ceases to be packaged into applications, and instead is packaged into services that are combined together on demand to create applications. Unlocking business logic Network computing was enabled by the emergence of the three-tier computing model, which made the breakthrough of separating application logic from data. But it left a fundamental shortcoming. While the data is portable, the application logic remains a hardwired jumble of function, procedure and identity. The data can be shared between applications, or transferred from one to another. But all of the business logic must be reprogrammed into every new application from scratch. This unnecessary binding of business logic into applications is at the root of the compulsion to own software. Businesses instinctively realise that when an application is customised to their requirements, what is happening is that their business processes are being hardwired into the implementation. The compulsion to own software is driven by the instinct to own the proprietary business logic hardwired into applications during implementation and customisation.But there is no reason for keeping logic bound up with individual software implementations in this way. The emerging network computing environment allows the separation of business logic from individual software packages, and the ASP model will encourage users to demand it. Process, policy and profile Three separate elements are intermingled in the code of present-day applications. The emerging component-based, messaging-enabled network computing architecture enables each to be separated out:
As a simple example, consider an expense management application. An employee who wishes to file an expense report calls up the application running on a server somewhere in the network. The employee is identified by reference to a profile stored on a directory server somewhere else. The directory server validates the application as the correct one to manage this process. The application server matches the employee's profile to the appropriate policy for approval of expenses reports. It then calls up software code from another server to execute the approval and filing process. Process on demand This revolution will not happen overnight. It depends on the creation and agreement of standardised definitions for business processes that allow each to be fulfilled by discrete software code components. Here is a likely sequence of events.
This is a verbatim extract from edition 1.2 of Packaged Software Rental: The Net's Killer App, published January 2000. The same themes are further developed in the latest ASPnews special report, Internet Application Engines. Both reports can be purchased together at a special bundle price. |