There will continue to be two basic models: workflow as just another application and workflow as the backbone of the information system. I think these two models will continue to exist. If agent technology really starts to take off, there may be a third model with process-aware agents. |
An infrastructure layer, as the networking one, and as the EAI one.
A descriptive one as the schema for databases.
|
Process orientation, rather than just process automation will be central to information system architectures. It will provide a prespective to information system architectures than can be comprehended by business people and key decision makers. |
It would be much easier to answer the question of Should. However, I truly believe that workflow's time has come, and it will begin to play a more predominant role in IS strategy. Particularly for progressive organizations, or those organizations that must compete in very volatile or dynamic market places. Specifically, there are several instances in which workflow has been leveraged to extend the life and capability of financial systems beyond their intended capacities. There are several instances in which workflow has been used as the focal point for processing in organizations that, through acquisition or poor planning, have multiple ERP systems. In these cases workflow provides a single unified interface and coordination of activity. I expect organizations will begin to leverage the flexibility of workflow to solve the complexities of merging ERP systems or controlling processes that must cross-functional and systematic boundaries. |
It will facilitate an increased use of components |
It will drive them |
Process specification and execution technology will become a standard part of all major information systems(e.g. windows) |
an increasingly important role, as the trend towards rapid application development moves to the next level and includes not only GUIs, but also mission critical, back-end enterprise applications, and as the need for monitoring and reporting increases. |
High. Application software must be constructed in such a way that the underlying processes retain flexibility, in order to keep in step with organizational changes/mergers/new partner relationships.
|
Ideally, every application of a certain minimal complexity that has scaling and flexibility requirements will be constructed as a business process running on a workflow engine.
Realistically, the pressure of applications to become 'workflow enabled' will continue to rise. As a first step, applications will expose services of varying granularity to become process enabled. |
It might be very important in increasing the flexibility and shorten time-to-market of a given system by having its own layer in the architecture. |
The role will increase, as integrated e-end-to-end automation in complex environments will require automated process support. |
It should be an intergral part of the system architectures |
I suspect that BPM will form the backbone of all future systems architectures - but if you think about it it always has - business logic has until now always been embedded in tha application code - all we are doing here is implementing that logic outside of the application. |
it is simply a programming paradigm. People want it. People are using it for appropriate and inappropriate things now. It clearly will always be an option to those who want to think about the problem in that way. |
Process automation will be a central part of IS architectures. Just as a database is an important part of an IS/IT architecture, similarly, the process component will also be central. |
again, one component among others, e.g., security, transactions. |
A huge role. Automation of processes is going to be big business. Understanding an organizations current state of affairs and then recommending an automated way to do business will be an amazing field to be in. |
As companies continue to strive toward efficiency and customer service, workflow management / process automation will become inbedded with the information systems architecture. |
A more and more important role since process automation will become part of the standard architectures. |