Pre-SOA Models

7/29/2019 Pre-SOA Models

http://slidepdf.com/reader/full/pre-soa-models 1/4

(IJCSIS) International Journal of Computer Science and Information Security,

Vol. 11 , No. 8 , 2013

Pre-SOA Models First step to SOA

Safa Talal Hasan Al-RamadaniSoftware engineering. Mosul University

Mosul University, uomosul

Mosul, Iraq

.

Abstract — In this paper I propose a number of steps as a starting

point to any SOA project. First we talk about SOA and its

importance in nowadays, then listing other researches opinions in

the first step to SOA. After that I'll lists my proposed practical

approach to start the way toward any SOA system, and enforce

that by a practical case study for a technical institution system.

Keywords-component; formatting; SOA : Service OrientedArchitecture, Pre-SOA Model.

I. I NTRODUCTION

rganizations tend to use SOA to achieve their strategic

goals such as agility, productivity, and interoperability.

SOA is a way or architectures used to build systems, these

systems were build as a set of independent, loose coupled, and

interoperable services. Each service is as simple as a distinct

function, (or can be obtain multiple capabilities) which can

works independent from others. These services can be reused

to building new enterprise by using a correct recomposing

architecture. The use of SOA might increase the alignment

between organization's business and IT, resulting in more

agility, well organization performance, and increased Return

On Investment (ROI) [6][10].

II. FIRST STEP TO SOA

Many papers and books talk about first step to SOA.

Many of them have the same opinion, others have a different

look with different proposing way. Such as listing a service set

[2], determine the scope and direction of SOA project*, view

business as a collection of independent services, identifying

critical business problems and challenges, start as a small

project then increase toward business and technology metrics

[3], messaging backbone or ESB [5][7], and other opinions as

proposed by many of researchers.

Any person new to SOA see any of these suggested starting

point is not enforced by a practical and explanation approach.

We can consider these point of views just as a theoretical

opinions. The question coming into account is how to put

correct step in the SOA road with any of them?In this paper I try to produce a practical point to start with

any SOA weather legacy or new system, and enforce my

proposed perspective with a practical case study, to produce aworkable opinion.

III. PRE-SOA MODELS

When we tend to start a new enterprise by using SOA, the first

question came into mind is how and when will we start? Is the

start point from classical software engineering? Or from business patterns? Or any other ways? In this paper I'll give

answer about this question.

I'll suggest to start from enterprise-Business side toward

technology side.

1- Dimensions : As an organization, we first take into

account the importance organization's dimensions.

These dimensions are: Business ( which can be

considered as the basic of an organization), Tier, and

department dimension. Then analyze each dimension

to its major components ( the tier is known that it

contribute data, process, and front-end tier) those the

organization and the system to be developed were

interested in.We can add another dimension called Entity, which

can be used to build additional tables by contribute

with the main dimensions metioned above. This new

dimension can give us a different perspective, we can

see the degree of relationship of dimensions those

related to the same entity. (in this paper we use only

the three main listed dimensions).

2- Build Tables : Second step is to build a number of

two dimension tables, each of which take two of the

earlier dimensions mentioned in the above step. First

dimension components represent the column's

address of the table, and the other represents the

rows. ( a detailed case study listed in the next

section). After building tables schema we can start

analyzing the intended system.

3- Services Analysis: The analysis phase can take place

either after or as a parallel with requirements

gathering process. In this phase we decompose the

intended system ( according to each table's column-

row relation) into a small parts called services , each

service is capable of doing a distinct function. And

put the resulted services in the corresponding

O

* http://msdn.microsoft.com/en-us/library/bb833022.aspx

97 http://sites.google.com/site/ijcsis/ISSN 1947-5500




Vol. 11 , No. 8 , 2013

column-row intersection. This analysis is done for

each tabular according to its dimensions relation, and

can be done incrementally as system requirement

changed.

4- Service Filtering : the next step after models filling

completed, we start an assessment process.

Assessment process can be considered as service

filtering process. We examined every model for new

service(s) (which is not exists in an organizationinventories), and reused services.

When we have complete a filtering of services we get

a two lists of services, one for reusable (exist within

one of inventories) and the other for new services (

need to be developed ).

After these steps we can work with new service list and

implement it as it is an agnostic or non-agnostic services and

according to service oriented architectures and patterns .

IV. CASE STUDY : BUILDING A SYSTEM FOR TECHNICAL

I NSTITUTION:

We work to build a SOA system for the Mosul technicalinstitution which provide deferent systems and services as thenext requirement list explained:

System name function Output

Salary Money

transaction,

compute salary

reports

Absence Compute absence Hunt, report

Technical

development

Learning,

training

Reports,

certified

Library Borrowing Report, bill,

alarm

Store Inbound,

outbound, computeexisting items

Report, alarm

Student Student

information

Report,

Employee Employee

information

Report

Exam committee Degree, subjects,

certified

Report, degree

bill

First step we begin with analysis of dimensions to their major

components.

- Tier dimension components are kwon : Data, Process,

and Front-End.

- The business major components those resulted from

the analyzing phase are : Finance, Technical

Development, and Security.- Departments contain : Salary , Absence, Store, Exam

committee, Technical Development.

Now we can building the following tables :

1- Business – Tier table.

2- Business – Department table.

3- Department - Tier table.The next step is the analysis of system and fitting it to

tables dimensions. By applying this step we get the followingtables :

1- Business – Tier mapping Model :

Data Process Front End

Technical

Development

Finance

Security

Update

Data

Subjectmaterial

Learn

Train

Data

hardwar

e store

Dataanalyst &Modeler

cost

Access rights

Processing

environmen

t cost

Executer

Cost

Compute

Salary

Reports

Certification

Course

Accounts

98 http://sites.google.com/site/ijcsis/

ISSN 1947-5500




Vol. 11 , No. 8 , 2013 2- Department- Tier Model

Data Process Front End

Salary

Absence

Store

Technical

development

Exam

Committee

3- Business – Department Model :

Finance Technical

Development

Security

Salary

Absence

Technical

development

Exam

Committee

Store

From above tables we can recognize some services were

repeated in many tables, these repetitions giving us a wider insight of a service capabilities, which can be a useful thing

when we deals with SOA patterns and when IT

implementation taken place.

ACKNOWLEDGMENT

I would to thanks Dr. Abdul Sattar M. Khidir for hissupport.

Checkeddeliveringfield

Getemployee

information

Computeservice

duration

Transform

money

Compute

salaryC

/S

re

p

or t

Create

clearancefor

training or

learning

ComputeAbsence

Sendstart

datealarm

Send

alarm

De

let

e

Mo

dif y

In

ser

tCheck

available

book

Books

restoration

BooksBorrow

system

Computeitems

quantity

Create/delete

borrowed bill

Compute

average

Sort

students

Computesum of

degree

C/S&Archiving

students

report

C/S studentsdegree

report

Transfer money

Discountratio per hour/day

Training

cost

Awardscost

additionexperience

salary

Huntingsystem

Training

courses

Safetymoney

transfer

Authorize

access

Work hours

Fellowship

learning

Buyingof

items

Books borrow

system

Thesisclassifying

system

Itemavailability

Secureinbound

andoutbound

system

Class,

course,student,

and degree

system


ISSN 1947-5500




Vol. 11 , No. 8 , 2013

R EFERENCES

[1] A. Rotem-Gal-Oz, SOA patterns, 1st ed. Shelter Island, NY 11964,2012.

[2] BEA, VMware, SOA and Virtualization: How Do They Fit Together?,white paper, 2007, pp. 3.

[3] C. Abrams, R. W. Schulte , Service-Oriented Architecture Overview andGuide to SOA Research, Gartner, ID Number: G00154463, 2008, pp.5.

[4] G. Lewis, Getting Started with Service- Oriented Architecture (SOA)Terminology, Software engineering institute, white paper, 2010.

[5] IBM Corporation, Providing a messaging backbone for SOAconnectivity, White paper, 2007, pp. 4.

[6] J. Hurwitz, R. Bloor, M. Kaufman, and F. Halper, Service Oriented Architecture for Dummies, 2nd ed. USA, 2009.

[7] L.I. Terlouw, A. Albani, Identifying Services in SOA, ICRIS WhitePaper , 2009, pp. 3.

[8] S. M. Glen, J. Andexer, A practical application of SOA Combine thetechnology and business perspectives of SOA implementation, IBM,2007.

[9] T. Erl, SOA Design Patterns,1st ed. USA, 2009.

[10] T. Erl, SOA : Principles of Service design, USA, 2008.

AUTHORS PROFILE

Safa T. Al-Ramadani : received the B.S. degree in software

egineering from Mosul University, Mosul, Iraq, She is

currently pursuing the M.S. degree in software engineering at

Mosul University.


ISSN 1947-5500

http://www.ibm.com/developerworks/webservices/library/ws-soa-practical/#author1




Pre-SOA Models

Documents

Transcript of Pre-SOA Models