See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/237776180

Service-Oriented Architecture: Concepts and Implementation

Article · January 2006

CITATIONS READS
8 2,538

3 authors, including:

Jaymeen R. Shah
Texas State University
27 PUBLICATIONS   295 CITATIONS   

SEE PROFILE

All content following this page was uploaded by Jaymeen R. Shah on 25 March 2016.

The user has requested enhancement of the downloaded file.

Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

Service-Oriented Architecture:
Concepts and Implementation

Mayur R. Mehta
[email protected]

Sam Lee
[email protected]

Jaymeen R. Shah
[email protected]
Department of CIS & QMST
Texas State University–San Marcos
San Marcos, Texas 78666, USA

Abstract

In today’s increasingly competitive and technology-driven business environment, ability to

quickly adapt its business processes in response to both internal and external changes is a
must for any organization. Service-Oriented Architecture (SOA), along with its programming
models, is one strategic option to accomplish this. SOA enables an organization’s business to
drive its information systems design by enabling the organization to align its business proc-
esses with information technology (IT). SOA is an architectural style that supports integration
of business processes as linked services that may be accessed when needed over a network.
From the perspective of application developers, SOA is a set of programming models and tools
for building, accessing, and assembling services that implement business design. This paper
examines the role and benefits of an application development framework built on SOA founda-
tion. In addition, it presents a programming model to build Web services, which is the most
common approach used to implement SOA.
Keywords: Service-oriented architecture, Web services, J2EE

such standalone applications created islands

1. Introduction
of automation within an organization, which
Applications developed in the past were usu- usually led to duplication of business logic
ally standalone applications that performed a and data redundancy. In most organizations
specific task(s) such as accounts receiv- today, both intra- and inter-organizational
ables/payables. Such applications were not business processes are enabled by informa-
integrated with other applications. Use of tion technology (IT). As business processes

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 1
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

usually require the use of functionalities that plication. Finally, Section 7 contains con-
are embedded within standalone applications cluding comments as part of the Discussion
that may have been developed during differ- section.
ent time periods using different technolo-
gies, it has become necessary to integrate 2. Application Development Models
these existing standalone applications. In-
tegration of these applications must be such Application development models have
that, if necessary, it should allow the organi- evolved over the last few decades. Most of
zation to quickly adapt business processes in these changes in the application develop-
response to regulatory and/or environmental ment models are a result of the technologi-
changes, and also create new business proc- cal evolutions that preceded them. For ex-
esses by assembling existing business logic ample, emergence of the personal com-
that may exist in different applications. The puters made it possible to develop cli-
need of these capabilities precludes the use ent/server applications. The major applica-
of point-to-point tight integration between tion development models include the mono-
applications that are usually difficult and lithic host-centric model, client/server
time consuming to manage and adapt. Fur- model, n-tiered model, and service-oriented
ther, the complexity and cost of managing model.
point-to-point tight integrations tend to in- Monolithic host-centric model was dominant
crease significantly as the number of appli- during the 1960s and 1970s. In this ap-
cations that are integrated increase. The proach, monolithic applications were devel-
use of service-oriented architecture (SOA) oped using programming languages such as
will enable an organization to use standards- COBOL and FORTRAN. These applications
based, vendor agnostic approach to easily were developed mainly to run on mini- and
and cost-effectively integrate existing dispa- mainframe computing platforms. All of the
rate standalone applications (Sanchez, application processing was performed on the
2006). It will make it easier to integrate host computer. Mainframe-based monolithic
existing applications with new business func- applications are still being used in banking,
tionalities that are implemented as services, airline, insurance, telecomm, and other in-
and also enhance the ability to integrate in- dustries as these applications support critical
ternal applications with business partners’ business processes. Although overall cost of
applications. Successful integration of inter- mainframe applications is usually high,
nal business applications and their integra- mainframe based applications’ strengths in-
tion with business partners’ application will clude high availability and scalability. Thus,
enable organizations to use collaborative they are used in high-volume transaction
business models. Technology integration processing environments.
and use of collaborative business models are
considered to be important strategic busi- Availability of PCs and networks led to the
ness technology investments in today’s development of the client/server or 2-tiered
global and competitive business environment application development model. One of the
(Andriole, 2006). major driving forces for the popularity of this
model was the enhanced graphical user in-
In the following Section we present an over- terface that was made possible by the use of
view of application development models. PCs as clients. In an application designed
Then in Section 3, we discuss SOA and the using this model, the database is usually
importance of SOA in the current business deployed on an organizational server and
environment. In Section 4, an overview of the presentation is performed on client PCs.
Web services is presented along with discus- The rest of the application consisting mainly
sion regarding its role in SOA. An example of of the application logic can be split between
successful SOA implementation is briefly dis- the server and client PC in many different
cussed in Section 5. In Section 6 we discuss configurations. In a ‘fat’ client environment
the use of IBM WebSphere Studio Applica- a large portion of the application logic is
tion Developer (the new version of this soft- executed on the client PC, while in a ‘thin’
ware is offered under the Rational badge as client environment most or all of the applica-
Rational Application Developer) for imple- tion logic resides on the server (Watt et al.,
mentation of web-services which is an im- 2002).
portant component of a service-oriented ap-

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 2

2
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

The client/server (2-tiered) model was ex- plex, and collaborative business processes
tended to three-tiered model consisting of that may span within and/or across organ-
three distinct application components, izational boundaries using existing hetero-
namely, presentation, business logic, and geneous application assets and new applica-
data. These three components could reside tions. It provides a cost-effective and effi-
on three different platforms. With the emer- cient alternative to tight integration of het-
gence of the Internet in the 1990s, the erogeneous applications to support organiza-
three-tiered model evolved into the n-tiered tional business processes (Janssen, et al.,
architecture used in distributed Web-enabled 2006). SOA has been effectively used by
applications. Applications developed using organizations to transform complicated het-
this approach provide more-agile software erogeneous information system infrastruc-
architecture, and are easier and cost- ture into seamless, streamlined, easy to
effective to maintain compared to main- maintain infrastructure, thus helping organi-
frame based applications (Mitchell, 2006). zations in controlling their integration costs
Many of the software development projects (Sanchez, 2006).
today use this software development model
An SOA is an enterprise architecture that
to develop Web-enabled distributed applica-
supports organizational business processes
tions.
via the use of solutions conceived from the
composition of distributed services, where a
3. Service-oriented architecture (SOA)
service is a well-defined, repeatable busi-
In today’s competitive business environ- ness task that can be performed by an appli-
ment, ability to quickly adapt automated cation (Uleman, 2006). A service is usually
business processes in response to external implemented as a coarse-grained software
and/or internal changes is a must. Many unit that exists as a single instance, and in-
business applications that exist today in teracts with other services and/or applica-
large organizations were developed within tions by using a loosely coupled, message
departmental boundaries and had functional based communication model (Brown et al.,
instead of business-process focus. Such 2005).
functional focus based application develop-
SOA paradigm presents an approach in
ment resulted in existence of heterogeneous
which modular, accessible, self-describing,
stovepipe applications that have interopera-
implementation-independent, interoperable,
bility issues. To automate business proc-
and reusable components are published as
esses, functionalities embedded within these
services which can be remotely invoked and
heterogeneous stovepipe departmental ap-
consumed by other applications or combined
plications have to be weaved together. In
with other services (Fremantle et al., 2002;
the past, this was usually achieved by tightly
Stencil, 2002). Thus at the heart of SOA is a
integrating these applications using point-to-
collection of services that communicate with
point solutions. Such integration is accept-
each other, and these services are used as
able as long as the business processes are
building blocks of applications. SOA pro-
stable and integration of additional applica-
vides an approach for how to describe and
tions is required rarely.
organize services to support their discovery
In today’s business environment, business and use. Each component in a SOA may per-
processes are more likely to be dynamic and form one or more of the following three roles
collaborative, making it necessary to adapt that are essential for services to be discov-
business processes more often, and inte- ered and used: (1) service provider – pub-
grate processes across organizational lish the availability of services, (2) service
boundaries with business partners. Further, broker – register and categorize published
organizations also need to expose the busi- services and provide search capabilities, and
ness-critical functionalities embedded within (3) service requester – use service broker to
the millions of lines of mainframe code de- find a service and use it to build an applica-
veloped over the past four decades (Mitchell, tion (IBM, 2004).
2006), and integrate these functionalities
Few of the characteristics that are associ-
with new business applications being devel-
ated with SOA include the following: (1) use
oped using current technologies. Service-
of open standards based technologies, (2)
oriented architecture can enable organiza-
the basic building blocks are coarse-grained
tions to develop and support dynamic, com-

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 3

3
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

services that can be published and are dis- The Web services framework at the mini-
coverable, (3) services are loosely coupled mum consists of a collection of three stan-
with other services to implement solutions to dards - standard to support communication
satisfy business needs, (4) reuse of existing between interacting services, standard to
software assets, and (5) higher level of ab- describe services, and standard to publish
straction in design (Uleman, 2006). Loose and discover services. The three main stan-
coupling between services make solutions dards that enable implementation of Web
developed using this approach to be more services are the Simple Object Access Proto-
flexible and scalable compared to those de- col (SOAP), Web Services Description Lan-
veloped using tight coupling between soft- guage (WSDL), and Universal Description,
ware components. This allows IT to react Discovery, and Integration (UDDI). These
quickly to the changes in business require- three standards are briefly discussed below:
ments, which enhances an organization’s
• SOAP is an XML-based protocol to sup-
ability to compete effectively and efficiently.
port communication between a Web service,
Also, the higher level of abstraction used in
its clients, and UDDI registry. It facilitates
this approach ensures that the focus is on
communication between Web services and
the business tasks that constitute various
interacting application components across
business processes.
heterogeneous platforms without requiring
Finally, one of the distinctive features of SOA the use of custom binaries or other platform-
is the concept of top-down policy based ap- specific information (Fremantle et al., 2002;
proach of governance throughout the lifecy- Joshi et al., 2004). It provides a mechanism
cle of services at the enterprise level. This is to invoke a Web service.
necessary to effectively manage services
• WSDL is an XML-based standardized
within the enterprise in terms of functional-
interface definition language used to de-
ity, interoperability, quality (service levels),
scribe what a Web service can do, where it
security, regulatory compliance, reusability,
resides, and how it can be invoked. A WSDL
maintainability, retirement, etc. Use of such
file associated with a Web service contains
governance structure allows IT to enforce
important details about the Web-service in-
uniform standards across the organization to
terface for client-service interaction. WSDL
introduce new services, and maintain and
is used to provide definition of a Web service
retire existing services. This governance
and interface specification for it.
structure permits creation of a library that
lists available services, and will prevent • UDDI standard is used to publish, dis-
creation of redundant services and improve cover, and manage Web services in an UDDI
reuse of services. registry. UDDI registry is like Yellow Pages
that list available Web services that can be
4. Web Services discovered by an application. Creation of a
registry that contains available services al-
W3C Web Services Architecture Group de-
lows service consumers to discover and in-
fines a Web service as a software system
voke Web services that are published within
identified by a universal resource identifier
the UDDI registry.
(URI), whose public interfaces and bindings
are defined and described using XML. Its As shown in Figure 1, a service provider can
definition can be discovered by other soft- publish a Web service and register it in a
ware systems. These systems may then service registry. A Web services requestor,
interact with the Web service in a manner which can be an application running on any
prescribed by its definition, using XML based type of computing platform, can discover a
messages conveyed by Internet protocols Web service that has been published in the
(W3C Web Services Architecture Group, service registry. After discovering the Web
2004). Although it is possible to implement service, the client interacts with it by send-
SOA without the use of Web services, Web ing and receiving SOAP messages. Each
services have been suggested to be the pre- Web service entry published in the service
ferred approach to implementing SOA as its registry points to a WSDL file that contains
use significantly simplifies loose coupling information for invoking and binding a Web
between business components (Bloomberg, service.
2005; IBM, 2004).

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 4

4
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

6. Implementation of service-oriented
application using IBM WebSphere
Service
registry Studio Application Developer
Find Publish To demonstrate the process of building a
Service description

Service description
service-oriented application, we will demon-
strate development of a simple inventory
Service Service search application. The application will be
requestor provider
Bind designed and implemented using the Model-
View-Controller (MVC) solution framework
(see Figure 2). The MVC enforces the sepa-
Figure 1 - Web Services Framework ration of presentation logic and business
logic, and has been suggested as the blue-
print that application developers should use
to design and implement Web solutions (Ta-
5. Example of successful SOA imple- kagiwa et al., 2002). The entire application
mentation will be developed using IBM WebSphere Ap-
plication developer Studio (WSAD) version
While many companies have benefited from
5.1.2. For the database environment, we
the use of SOA, Wachovia’s implementation
will use an Oracle 9i database server.
is perhaps one of the best illustrations of a
successful SOA implementation. SOA has
Client
been deployed by many financial institutions Web Application Server Database

to transform their complicated technology Java Interaction

Java Script
Controller
infrastructures into streamlined and easy to Reques Servlet
maintain technology infrastructure (Sanchez, s

Forward
2006). Wachovia Bank’s Corporate and In- HTML Web Java
JVM DB
vestment Banking division spent multi- Service
(Facade)
Bean
s
hundred million dollars to revamp its exist-
Applets

Java
Java

ing software architecture to transform it into Response

Server (JDBC)
a service-oriented architecture (Margulius, Java Enabled
Pages View
Model SQL
Processing
2006). They moved to software develop- Web Browser HTTP Server

ment strategy that revolved around a core of

reusable frameworks, components, and ser-
vices that can be leveraged by each of its Figure 2 – Model-View-Controller Solution
business unit. The final outcome of this Framework
transformation process was an end-to-end,
service-oriented development and delivery
platform that was supported by a business-
focused, product management culture within
6.1 Model-View-Controller
the information technology department.
Some of the resulting benefits included, in- Models are meant to serve as a computa-
creased IT productivity due to reduction in tional abstraction of real entities. For exam-
development of similar software components ple, a model of a product in an e-commerce
by different groups within the bank, faster application contains the identity and quantity
development of applications that end-users of the inventories that are available for the
need due to the reuse of existing compo- product and offers functions to add and re-
nents, and above all, a standards-based ap- move inventories. In J2EE (Java 2 Platform
plication development framework. It has Enterprise Edition) space, the model compo-
also allowed Wachovia Bank to win several nents are typically written as Java Beans
multimillion dollar contracts, where the key and represented by a Unified Modeling Lan-
selling point to the customer was the bank’s guage (UML) class diagram. In a service-
superior technology architecture that permit- oriented architecture, a Web service is cre-
ted easy integration with customers’ dispa- ated to transports the model components to
rate systems (Margulius, 2006). the Web service clients.
Views present (render) the information that
is contained in a model. For example, a

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 5

5
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

graphical view may render a product with a Web service client project using the
list that shows the quantity and location of facade.
inventories, with a “remove” button next to
• Develop the JSP page and Servlet in
each inventory. Views are rendered by a
the Web service client project.
Web browser using HTML, which in J2EE
Inventory Search JSP
space is typically produced by Java Server
pages (JSPs).
A controller component controls the applica-
tion flow. It accepts input from the user,
interprets the input, and invokes the appro-
priate operation in the model in response to
the input. For example, when the controller
receives a request from the “remove” button
of an item, it invokes the remove operation
for that item to remove it from inventory.
The controller then forwards the JSP view
that displays the updated product without
the item removed from inventory. In J2EE
space, the controller is normally imple- Figure 3 – Inventory Search Application
mented as a Java Servlet.

6.2 An example of a service-oriented

application
6.3 UML class diagram for represent-
The inventory search application is a simple ing model components
application that runs on the Web. The appli-
The class diagram illustrated in Figure 4 is
cation is illustrated in Figure 3. The user
created in a Web project using the IBM
enters search parameters for product iden-
WSAD UML (Unified Modeling Language)
tity and quantity fields, and then clicks the
visualization feature. The diagram consists
search button. The application responds by
of a few classes and associations. These are
displaying a message to inform the user
described as below:
whether there is adequate inventory.
• Product: a product of the system.
This application may be designed as a ser-
There are many products.
vice-oriented application by implementing
two Web projects: Web Service and Web • Inventory: a product inventory
Service client using WSAD; and it is devel- available in a warehouse location. A
oped using the following steps: product may be inventoried at multi-
ple warehouse locations.
• The Web service project is first cre-
ated in WSAD. • ProductAccess: a facade bean pro-
vides the service interfaces for find-
• Develop model components (Java
ing all products or a product by a
Beans) to represent data returned
product identity number. This ac-
by the Web service in the Web ser-
cess bean executes queries against
vice project.
the database tables, populates prod-
• Develop a facade bean that is a part uct beans using the query results,
of the model to define operations and returns the product beans to the
provided by the Web service. The clients.
facade is a J2EE design pattern to
encapsulate business logic and busi-
ness data and expose their inter-
faces, and thus the complexity the
distributed services, to the clients
(Alur et al., 2001).
• In WSAD, a wizard is provided to
generate the Web service and the

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 6

6
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

This Java package

includes the Web
service proxy bean.

Figure 4 – Class Diagram

Test JSP file

6.4 Generating Web service using a WSDL document
WebSphere wizard
IBM WSAD provides a wizard to generate a Figure 5 – Web Services Generation in Web-
Web service from a Java Bean. We create a Sphere
Web service using the facade bean (e.g. Pro-
ductAccess) that defines the Web service
interface. After the wizard guides us 6.5 Developing a Web service client
through the Web service generation steps, A Web service client project contains views
the Web service is produced and a client and controllers. Using the Inventory Search
project is created. The following files are JSP in Figure 3, this example demonstrates
included in the client project (see the Figure the views’ common features of providing a
5): user input form and displaying property val-
• WSDL document: this standard ues of Java Beans. The InventorySearchAc-
document uses XML to describe the tion controller receives the input data, per-
Web service (what it does, interface forms a Web service operation, and passes
it supports, etc.). The WSDL docu- result Java Beans to the view. The details of
ment also specifies the data (e.g. the JSP and Servlet controller are described
Product and Inventory) returned below.
from the Web service and operations After opening the JSP page, the user enters
(e.g. findAllProducts and findPro- a product ID and a quantity to check the
ductByID) to access the Web ser- availability of the product. The page shows
vice. an out-of-stock message if no Product Java
• Proxy bean: this bean runs in the Bean is returned; otherwise, it receives a
client, and provides Java methods to Product Java Bean and its Inventory Java
call the remote operations on the Bean for which available quantity is greater
Web service as if the methods were than the input quantity. For the successful
local. search, the page displays the product name
and the warehouse location that maintains
• Test JSP: this JSP page runs in a the adequate inventory.
Web browser and enables us to test
the designed Web service. We se- The InventorySearchAction controller that is
lect a method, enter the parameter, implemented by a Servlet is activated when
click the Invoke button, and inspect the user submits the JSP form. First the
the result. controller receives the product ID and quan-
tity. Second, it instantiates the Web service
proxy bean, obtains a remote ProductAccess

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 7

7
Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

facade bean using the proxy, and calls the it from a vendor, and you can’t build it with
findProductByID method of the facade by programming code. Architecture is a set of
the product ID (see the Figure 6). Third, if a best practices that guide your implementa-
product Java Bean were found to contain a tions, regardless of the technologies you
list of Inventory Java Beans, the controller choose to implement them” (Bloomberg,
2005).
//get parameters
int productID = new Integer( Many organizations have begun implementa-
req.getParameter("productID")).intValue(); tion of SOA and have reaped significant
int qty = new Inte-
ger(req.getParameter("qty")).intValue(); benefits. Implementation of SOA may re-
quire organizations to invest significant dol-
//instantiate a web service proxy
ProductAccessProxy proxy = new ProductAccessProxy(); lar amount, as indicated in Wachovia Bank’s
ProductAccess access = proxy.getProductAccess(); example (Margulius, 2006), and most likely
//find a product will also necessitate a change in the organ-
Product product = access.findProductByID(productID); izational IT culture and practices (Brown et
... al., 2005).

Figure 6 – Servlet Implementation 8. References

Alur, D., Crupi, J., and Malks, D. (2001).
“Core J2EE Patterns: Best Practices and De-
checks all of the list elements to see if there
sign Strategies.” Palo Alto, California: Sun
is an Inventory Java Bean with quantity
Microsystems Press.
greater than the input quantity. Finally, if
both the Product and Inventory Java Beans
Andriole, S.J. (2006). “The Collabo-
were found, they are passed back to the JSP
rate/Integrate Business Technology Strat-
page.
egy.” Communications of the ACM, Vol. 49,
No. 5, pp. 85-90.
7. Discussion
Use of SOA provides organizations with Bloomberg, J. (2005). “The SOA Pilot Pitfall.”
greater flexibility and control of the solutions www.zapthink.com, available at:
they deploy (Brown et al., 2005). The foun- http://www.zapthink.com/report.html?id=ZAPFL
dation of SOA is the use of standards based ASH-2005711
approach for description, publication, dis-
covery, selection, and binding of basic ser- Brown, A.W., Delbaere, M., Eeles, P., Johns-
vices (Papazoglou and Georgakopoulos, ton, S., and Weaver, R. (2005). “Realizing
2003). SOA promotes the idea of using Service-oriented Solutions with the IBM Ra-
loosely coupled services, each of which rep- tional Software Development Platform.”
resent a block of business functionality, that IBM Systems Journal, Vol. 44, No. 4, pp.
can be assembled together to support a 727-752.
business process. Thus, SOA can be used by
organizations to support business process Fremantle, P., Weerawarana, S., and Khalaf,
driven application integration within and R. (2002). “Enterprise Services.” Communi-
across organizational boundaries. This will cations of the ACM, Vol. 45, No. 10, pp. 77-
enable organizations to quickly adapt their 82.
business processes in response to changes
in business requirements, and also allow IBM (2004). “Service-oriented Architectures
them to integrate their applications relatively and Web Services.” IBM Developerworks
easily with their business partners’ applica- Technical Presentation, Texas State Univer-
tions. sity, Fall 2004.
When adopted at an enterprise level, SOA Janssen, M., Gortmaker, J., and Wagenaar,
can provide an organization with a compre- R.W. (2006). “Web Service Orchestration in
hensive plan regarding how IT can support
Public Administration: Challenges, Roles,
business. However, it is important to note and Growth Stages.” Information Systems
that SOA is an architecture, which is well Management, Spring, Vol. 23, No. 2, pp.
reflected in the following note – “Never for- 44–55.
get that SOA is architecture – you can’t buy

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 8

8
 Mehta, Lee, and Shah Fri, Nov 3, 12:00 - 12:25, Normandy A

Joshi, P., Singh, H., and Phippen, A.D.

(2004). “Web Services: Measuring Practi-
tioner Attitude.” Internet Research, Vol. 14,
No. 5, pp. 366-371.

Margulius, D.L. (2006). “Banking on SOA.”

InfoWorld, July 13, Available at:
http://www.infoworld.com/article/06/07/13/29FE
wachovia_1.html

Mitchell, R.L. (2006). “Morphing the Main-

frame.” Computerworld, Vol. 30, No. 5, pp.
29-31.

Papazoglou, M.P. and Georgakopoulos

(2003). “Services-oriented Computing.”
Communications of the ACM, Vol. 46, No.
10, pp. 25-28.

Sanchez, F. (2006). “The SOA Approach to

Integration and Transformation.” U. S.
Banker, Vol. 116, July 2006, pp. 12-13.

Stencil (2002). “The Laws of Evolution: A

Pragmatic Analysis of the Emerging Web
Services Market.” The Stencil Group:
http://www.stencilgroup.com.

Takagiwa, O., Korchmar, J., Lindquist, A.,

and Vojtko, M. (2002). “WebSphere Studio
Application Developer Programming Guide
(1st ed.).” San Jose, California: IBM Corpo-
ration, International Technical Support Or-
ganization.

Uleman, R. (2006). “Service Oriented Archi-

tecture Unveiled.” Geospatial Solutions, Vol.
16, No. 6, pp. 30-33.

Watt, E.R., Denoncourt, D., Lee, S., Ste-

vens, R., and Cancilla, B. (2002). “Under-
standing e-Business Application Integra-
tion.” Double Oak, Texas: MC Press, LLC.

W3C Web Services Architecture Group

(2004). “Web Services Architecture Re-
quirements.” Editors: Austin, D., Barbir, A.,
Ferris, C. and Garg, S., Available at:
http://www.w3.org/TR/2004/NOTE-wsa-
reqs-20040211/

Proc ISECON 2006, v23 (Dallas): §2335 (refereed)

c 2006 EDSIG, page 9

9
View publication stats