decisions, and, therefore, if has a close relationship
to the subject of real-time BI processing.
3 ABOUT SERVICE-ORIENTED
ARCHITECTURES
3.1 The Service-Oriented Architecture
Basics
The service-oriented architecture (SOA) has been
held out for nearly two decades as a substantially
more cost-effective and flexible strategy for
constructing enterprise software systems than
historical approaches including monolithic system
design and tightly coupled client server models
(Newcomer, 2002). Many IT professionals and
industry observers believe Web services technology,
and the unprecedented universal vendor support of
the underlying standards, will finally make practical
the widespread adoption of the SOA approach.
In the past, enterprise software systems were
complex, monolithic behemoths. The complexity of
these systems made them difficult to fully
understand and therefore leverage. There were
limited integration points allowing reuse of the
embodied business information and processes. This
resulted in islands of automation with costly
duplication of information across systems.
Information flows between applications were
limited, preventing the delivery of information to the
people and systems that could best utilize it.
Even more damaging to the organization, these
systems were difficult to change. Modifications,
upgrades and enhancements were time consuming,
costly and risky. Since these systems embodied the
business processes of the organization, IT frequently
became the bottleneck in attempts to adapt the
business to changing market conditions.
The very systems that were built to bring
automation and efficiency to the processes of the
organization now prevent the organization from
maintaining efficiency as business conditions
change.
The service-oriented approach to enterprise
software architecture replaces large, complex,
monolithic applications with applications composed
of loosely coupled collections of modular software
components linked through well-defined Web
service interfaces (Clabby, 2003). In other words,
SOA is an architectural style that promotes loosely
coupled interactions between software agents.
One of the best ways of enabling application
developers to understand concepts and put them to
use is by providing an application framework that
provides the infrastructure needed while designing
and developing applications based on those
concepts. Unfortunately, there is not enough
literature that can help application architects and
developers in the design and implementation phases
to build on the SOA concepts, apart from those from
product vendors, which mostly explain in terms of
their products/technologies.
In its simplest form, the basic SOA is
schematized in Figure 1.
It should be noted that there is no contradiction
between the fact that interacting software agents are
loosely coupled and the requirement for business
intelligence itself to be tightly coupled with business
processes. These issues simply do not have mutual
influence.
Service
Consumer
Service
Provider
Service Request
Service Response
The SOA Framework
Figure 1: The basic Service-oriented Architecture (Kay,
2004).
3.2 Benefits to Businesses Achieved
through SOA Implementation
For the business, the result of the Service-oriented
Architecture implementation is movement toward
what is often referred to as the ‘real-time enterprise.’
(Flint, 2003) Because applications have well defined
service-based integration points, and because these
services are built on standards embraced by every
major enterprise software vendor, connecting
software systems together will be orders of
magnitude easier than in the past.
The ability to move the right information, to the
right people and systems, at the right time,
maximizes the ability of the enterprise to identify
and interpret changes in its markets and to respond
by adjusting its processes, operating models or
structure.
ICEIS 2008 - International Conference on Enterprise Information Systems
192