Nandish V. Patel
15
model is contrasted with a ‘passive model’ which is static rather than dynamic, representing the
position at the point of observation and lacking an updating mechanism (Beeson I, Green S et al. 2002).
Integral to the active model of business process is the process ‘coordination layer’.(Warboys B, 2000).
The coordination layer enables the co-evolution of business process and IT systems.
In terms of cybernetics, ProcessWeb can be categorised as a non-trivial machine conceptualization
of business processes with one critical qualification. In ProcessWeb, the input-process-output
relationship is non-variant, whereas in non-trivial machines it is variant. Whilst the active model
provides a link with the actual business processes modelled, the system architecture of ProcessWeb
does not enable variable input-process-output.
ProcessWeb illustrates four of the five constructs, and their interrelationships, of the deferred
action theoretical model. The theoretical model directs modelling attention to emergent factors. In
ProcessWeb, specified design is based on the active model. As the active model keeps a synchronised
link with the business domain, it accounts for emergent factors. There is no direct enablement of
deferred action. However, the synchronisation link in the active model is the mechanism that enables
organizational actors to keep the IT system relevant to business needs. It indirectly caters for deferred
action. The conceptual model of the ProcessWeb is based on business process and so its system
architecture is process-oriented. As ProcessWeb is an experimental system it has no e-business model.
The three propositions deduced from the theoretical model are accounted for in ProcessWeb.
Concerning proposition 1, ProcessWeb is capable of supporting any process-based business model
since its architecture is process-oriented. It seeks to be effective by catering for business processes.
Proposition 2 is met because organizational change, an aspect of organizational emergence, is catered
for by the synchronisation link in the active model. Since ProcessWeb is predicated on software
evolution, it meets Proposition 3 of non-standardisable processes evolving with the same magnitude of
IT systems evolution.
Exemplar 2 service oriented architecture (SOA)
The underlying design principle of Service Oriented Architecture (SOA) is the provision of
software services to business on demand. The services are loosely coupled or configured to meet
specific business process needs (Jones S 2005). IT system architecture, including computer networks, is
accessed without constraints to deliver required services.
SOA illustrates five of the constructs and their interrelationships of the deferred action theoretical
model. Specified design is based on software (and hardware) components. A software component is a
system element offering a predefined service and able to communicate with other components. Since
software components are ‘non-context-specific’, they enable emergence through composition to be
represented in IT systems. Software componentry, indirectly, makes deferred action at the level of
systems designers possible (as opposed to organizational actors). Concerning the process architecture,
as components are non-context-specific, they can be mapped onto existing or newly designed business
processes. The technical system architecture is distributed computing based on application servers.
SOA, within which software componentry is embedded, is suited to support emergent e-business
models. Business processes and the needs of organizational actors underpin SOA. It recognises the
interconnectedness of organization, data and applications. The architecture is designed to deliver
computational resources on demand as required by business users, thereby serving any e-business
model.
The three propositions deduced from the theoretical model are accounted for in SOA. Concerning
proposition 1, since the concept of service underpins SOA, any underlying e-business model is
supported. IT systems are configured to support specific, and unique, business processes. Proposition 2
is met because organizational change (and emergence) is catered for by re-configuring services.
Similarly, Proposition 3 is met as non-standardisable processes are directly catered by re-configuring
services as required.
Generally, the exemplar systems are indicative of a trend towards a new conceptualization of IT
systems. In terms of cybernetics, the emerging conceptualisation is tending towards IT systems as non-
trivial machines whose input-process-output structure is variant. This conceptualisation mirrors the
deferred action theoretical model developed above and the derived propositions. It is evident in systems
like ProcessWeb and emerging technologies like software componentry, SOA, and the Semantic Web.
The theoretical model has wider implications for process management. Process management
involves approaches to process improvement. It encompasses interest in business process modelling
languages and theory of process management change. Process management encompasses
methodologies, techniques and tools to support the re(design) of business processes. Business process
design is informed by business process modelling languages. Practitioners particularly are interested in
modelling languages. Kettinger et al (1997) surveyed 25 methodologies, 72 techniques and 102 tools.