![]() |
service-oriented processveryard projects > process > service orientation |
process characteristics
(old economy) |
process characteristics
(new economy) |
material | ||||||||||||||||||||
|
|
Service Oriented Economy | ||||||||||||||||||||
![]() |
![]() |
Business Processes in the Old Economyveryard projects > process > service oriented > old |
In theory, manufacturing could go all the way from raw materials to finished goods in a single production line. However, in most manufacturing contexts, this production line is subdivided, with some production lines designed to produce components, which are then input to other production lines. This is usually true even in so-called vertically integrated companies, where all the production lines belong to the same company and are fairly tightly coordinated.
Until recently, most software development was organized in a single production line – with a complete application produced, as it were, from nothing. Within the CBD world, however, we have long been aware of the advantages of so-called twin-track development, where the software process is divided into at least two production lines – one to produce software components, and another to assemble software components into applications.
Even service industries, such as finance, are often based on business processes constructed on the same principles and assumptions: linear, chronological, cumulative and synchronous. This is the normal basis for defining workflow and controlling work, so that an increasing proportion of the workforce may be working within some kind of virtual or abstract production line – converting blank application forms into mortgages, say.
But the business process is not just the workflow. A bank doesn’t make money by converting blank forms into mortgages; it makes money by providing a range of savings and loan services to its customers.
![]() |
Business Processes in the Service-Oriented Economyveryard projects > process > service oriented > new |
The same considerations apply to IT systems and their requirements. An IT application provides a set of services – either to human users or to other IT systems – and uses a series of other services in order to achieve this. Although for many purposes it is good enough to have a model that simply shows the IT services used by the application, a complete model of the services used by an IT application should also show the use of such human services as system administration.
Showing how an IT application is dependent upon human as well as IT services is particularly important for requirements like security, where the functionality of the authorization and authentication subsystems may be critically dependent upon human administrators to issue passwords and so on. It is also relevant for the design of On-Demand systems, where the system’s ability to respond to changes in demand may call for some defined level of human intervention.
In the traditional economy, the enterprise is dependent upon the supply
of raw materials and components. Companies pay considerable attention to
the supply chain, not merely to drive down costs but also to deal with
various risks such as interruption or contamination to supply that would
threaten business efficiency and continuity. In the service-based economy,
we need to pay similar attention to the service supply chain – making sure
that dependencies on service providers are properly managed.
![]() |
SOA Modelling Workshop |
![]() |
veryard projects > process > service oriented |
Copyright © 2003 Veryard Projects Ltd http://www.veryard.com/process/serviceoriented.htm |