Page 1 of 10

Journal for Studies in Management and Planning

Available at http://internationaljournalofresearch.org/index.php/JSMaP

e-ISSN: 2395-0463

Volume 01 Issue 05

June 2015

Available online: http://internationaljournalofresearch.org/ P a g e | 38

Service Oriented Archtecture: Technology, Application

and Future Directions

1Nweke F. Henry,

2

Ugwu .E. Gabriel,

3Ezekwe C. G,

1, 2 Computer Science Department, Ebonyi State University, P.M.B 053 Abakaliki Nigeria

3.Electronics Development Institute, Awka

National agency for Science and Engineering Infrastructure (NASENI)

Federal ministry of Science and Technology, Nigeria

1

ufoo2010@yahoo.com,

2

norakingchi@yahoo.com,

3

ugwugabrielevo@yahoo.co.uk

Abstract

The development and introduction of service

oriented architecture into organization and

business process has helped to deal with rapid

changes in the business environment. This enable

organizations to access the quality of its products

before implementation. Service oriented

architecture as a technology provide flexibility

and allow enterprise to change business

infrastructures in response to changes in the

business environment with basic web services

process. To ensure appropriate understanding

and implementation by organizations, this

research paper explore the different services

oriented architecture architectural models,

design principles and service orientation

composition. The paper also provides a

knowledge on independent services with defined

interface that can be called upon to perform

different task in a standard way without the

knowledge of the calling application.

Keywords: Service oriented architecture, service

orientation, architectural principles, and web

service

1. Introduction

Service oriented architecture is an architectural

paradigm and discipline that may be used to build

infrastructure to enable interaction of service

consumer and service irrespective of domain and

technology. The service helps to facilitate

electronic data interchange that require additional

mechanism to functions (Dion, 2007). Service

oriented architecture is also a software design and

architectural pattern based on discrete pieces of

software to provide application functionality to

other application. The service provided are

independent of vendor, products or technology.

Basically, the service is self-contained unit, and

can be as a simple as retrieving online bank

statements, checking of account balance and

online transaction details (Zednet, 2009).

There are number of features of services oriented

architecture paradigm that has been implemented

in many industries (Zednet, 2009). These include

application to provide complete functionality of a

large software applications. Moreover, it enable

computer connected over a network to cooperate

and can run a number of services built in a way

that ensure exchange of information with other

networks without human interaction or change to

the underlying program itself. Service oriented

architecture is a natural evolution of other

software development models such as object

oriented model of 1980s, component based

development of the 1990s and now the service

orientation models. The service orientation model

has retained the benefits and features of

component based development model which

include self-description, encapsulation, dynamic

discovery and dynamic service loading

(Zdnet.com, 2009). To enhance more service

features, service orientation has incorporated

other features and techniques for calling objects,

instead of remotely invoking methods, messages

Page 2 of 10

Journal for Studies in Management and Planning

Available at http://internationaljournalofresearch.org/index.php/JSMaP

e-ISSN: 2395-0463

Volume 01 Issue 05

June 2015

Available online: http://internationaljournalofresearch.org/ P a g e | 39

are passed between services. Also, to promote

service interoperability and provide adaptability,

service schema can be used to describe the

message structure, behavioral contracts and

message exchange patterns and policies which

also defines the meaning of each service. The

organization further noted that services in

services oriented architecture are unassociated,

loosely coupled and self-contained. So, services

use defined protocols to explain how services

pass and parse message using description

metadata. The metadata describe the

characteristics and data that drive these services.

Other service components employed by

programmers are extensible markup languages

(XML), which is used to structure data that they

wrap in nearly exhaustive description-container

called the web service description language

(WSDL). The language describe the SOAP

protocols which describe the communication

protocols. The service describe by the metadata

are required to fulfil number of criteria such as, it

should be provided inform the system designer

can understand and manage with reasonable

expenditure cost and effort. Another important

criteria is that, the metadata must provide means

to ensure dynamic software system configuration

and maintain coherence and data integrity.

There are number of benefits outlined by Waldo

(2002), which have made SOA technology to be

adopted by organizations. Firstly, service oriented

architecture services are reusable, thereby

reducing the deployment and maintenance cost.

Secondly, the service provide more value when it

is developed and tested. Service reusability also

provide quicker services to the users. While a

well planned and executed service oriented

architecture can help organization realize greater

responsiveness in a changing market place and

technology, it is still faced by number of

problems. Hoyer et al (2008) noted the project

may experience limited success when developer

take bottom up approach that is not tailored to the

strategic need of the organization. They further

submitted that when service oriented architecture

are built without reference to the business

context, it will result to unorganized principles

and guidance. The above critical issues may

create chaotic implementation with no relevance

to organization’s business plan. However, taking

the top-down approach to service oriented

architecture is time consuming and result to

organizational project not meeting the business

need. Service oriented architecture has not

provided industrial standard, but individual

organization provide principle that guide their

implementation of service oriented architecture.

These principles according to Waldo (2002) are:

 Standardize Service Contract: This

describe the communication agreement which is

defined by service description documents.

 Service Loose Coupling: The principle

help to maintain relationship and service

awareness to reduce service dependencies.

 Service Abstraction: Services hide

detailed logic and functionalities to outside

organization or entities.

 Service reusability: The service are

divided into bits to enhance service reuse.

 Service Autonomy: Services are self- contained within organization and can control

underlying business logic.

 Statelessness: Service reduce the

consumption by deferring the management of

state information.

 Service Discoverability: Service

oriented architecture provide a principle for

added communication metadata which can be

discovered and interpreted.

Other principles that guide service

implementation include:

 Service Composition: Services are made

up other participatory service regardless of the

size and complexity of such composition.

Page 3 of 10

Journal for Studies in Management and Planning

Available at http://internationaljournalofresearch.org/index.php/JSMaP

e-ISSN: 2395-0463

Volume 01 Issue 05

June 2015

Available online: http://internationaljournalofresearch.org/ P a g e | 40

 Service Granularity: The principle

provide design consideration for optimal

scope and functionality in service

operation.

 Service Normalization: To reduce

redundancy, service are normalized of

decomposed to a normal level. Service

normalization help to increase

performance access to service and

aggregation.

 Service Optimization: There is increase

of service optimization and high quality

of service.

 Service Relevance: Functionality is

presented at a granularity recognized by

the user as a meaningful service.

 Service Encapsulation: many Services

are consolidated for use under SOA.

Sometimes, such services were not

planned to be under service oriented

architecture.

 Service Location Transparency: The

last but not the least of service oriented

architecture is location transparency.

Service in many location can be called by

consumer irrespective of such location in

the network. Services discoverability

allow consumer to discover services and

have the right to use such service.

Another technology in service location

transparency is virtualization where

logical services can be called by users

and suitable service oriented architecture

can enable the service to be mapped with

a physical service.

2. Service Composition

Architecture

One of the core characteristics of services

developed using service orientation

design paradigm is that they are

composition centric. As described by

Schroth et al (2007), such services can

help to provide new requirement by

recomposing the same service in different

configurations. The service compose of

different individual architecture of the

participating services. With service

abstraction principle, this type of

architecture only documents the service

contract and any published Service Level

Agreement (SLA) and representation of

only internal detail of each service.

Service composition architecture has a lot

of other service architecture as child

service composition. These service

composition architecture are:

2.1.Service Inventory Architecture

Service inventory architecture helps to automate

business process, and account for the combined

process requirement of all the services within the

services architecture. Service inventory

architecture enable the documentation of service

requirement as a different entity from the

business process that they automate, thereby

helps to identify problems in the process. Service

inventory architecture is made possible by service

inventory blueprint, so that service candidate can

be redesigned before their implementation.

2.2.Service-Oriented Enterprise Architecture.

This is made up of service composition,

inventory architecture and any enterprise wide

technological resources to be accessed by these

architecture. This can be assisted by enterprise- wide architectural standard that apply the

resources to architecture type. Other types of the

enterprise architecture are also documented in

order to consider transformation requirement if

the service needs to communicate with the

business process automated by the part of the

enterprise, thereby delivering agility to the

business process.

2.3.Web Service Approach