jump to navigation

EAI project strategies-3. EAI Implementation Process July 27, 2009

Posted by Terry.Cho in Architecture, EAI.
Tags: , , ,
trackback
Second is delivery process of EAI project.
In persepctive of tranditional water-fall model, to do item is like below.
Analysis Phase
In this phase we define “What to do EAI system ?”
1) Define interface type
It is about, what business systems are integrated? What is techical interface type of the system (EJB,IIOP,MQ,Web Service etc)
In this phase, decide to what interface use XA.
2) Define MEP (Message Exchange Pattern)
Gather requirement of MEP. Sync,Async,Real time, Near real time and multiplicities (1:1,1:N etc)
3) Define Message structure
Define message format. What header fields are required? What format will be used? (MFL?Text?XML? etc)
After finishing Anlaysis phase, we understand the EAI system what will do.
Design Phase
1) Designe architecture
Based on requirement from analysis phase. Design architecture and system.
2) Implement prototype
With the design, priotize most critical functionalities and design and implement prototype.
3) Test with prototype
Valdating prototype and enhance architecture
4) Gather interface list
Gather interface list what business system and functional will be integrated.
EAI project has a dependency to schedule of other business systems. Based on interface list and integration schedule, EAI system arrange their interface implementation schedule.
Important thing in design phase is validate architecture. After validating the architecture, EAI team implement interface with validated architecture by factory job.
Removing risk in design phase is important because architecture related changes are requires a lot of resource and time. So removing risk in beginning phase enables reduce cost.
Implementation Phase
1) Implement interface
Implement interface based on schedule. EAI interface implementation impacts business team implementation. Because business system communicates by using EAI system.
2) Step by step transition
Transition (Deployment) plan in EAI is very important. As i mentioned lot of time EAI system has dependencies to other system and it also has dedicated network line (X.25 etc)/
So during implementation interfaces deployed in development system. After validating the interface, it is deployed to staging system. Other business system connected the staging system.
Finally all of implementation has been finished and ready to move production, EAI system is deployed into production environment.
I will describe more about deployment environment later.
3) Monitoring and fix
After starting deploying interface to staging system. (Open interface to business team). EAI project team monitors the interfaces. The interfaces always has errors like “Table comlumn mismatch”,”Message type missmatch” etc.
The error let the interface down and it brings complain from business development team.
In implementation phase, support business team to follow up their schedule by matching EAI interface implementation schedule. If delay is occurred, business team try to responsibilities to EAI team for the schedule delay.
And there are many requirement change like number of interfaces, type etc. So in the implementation phase, interface schedule management is very important.

Second is delivery process of EAI project.

In perspective of traditional water-fall model, to do item is like below.

eaiprocess

Analysis Phase

In this phase we define “What to do EAI system ?”

1) Define interface type

It is about, what business systems are integrated? What is techical interface type of the system (EJB,IIOP,MQ,Web Service etc).  In this phase, decide to what interface use XA.

2) Define MEP (Message Exchange Pattern)

Gather requirement of MEP. Sync,Async,Real time, Near real time and multiplicities (1:1,1:N etc)

3) Define Message structure

Define message format. What header fields are required? What format will be used? (MFL?Text?XML? etc)

After finishing Analysis phase, we understand the EAI system what will do.

Design Phase

1) Design architecture

Based on requirement from analysis phase. Design architecture and system.

2) Implement prototype

With the design, prioritize most critical functionalities and design and implement prototype.

3) Test with prototype

Valdating prototype and enhance architecture

4) Gather interface list

Gather interface list what business system and functional will be integrated.

EAI project has a dependency to schedule of other business systems. Based on interface list and integration schedule, EAI system arrange their interface implementation schedule.

Important thing in design phase is validate architecture. After validating the architecture, EAI team implement interface with validated architecture by factory job.

Removing risk in design phase is important because architecture related changes are requires a lot of resource and time. So removing risk in beginning phase enables reduce cost.

Implementation Phase

1) Implement interface

Implement interface based on schedule. EAI interface implementation impacts business team implementation. Because business system communicates by using EAI system.

2) Step by step transition

Transition (Deployment) plan in EAI is very important. As i mentioned lot of time EAI system has dependencies to other system and it also has dedicated network line (X.25 etc)/

So during implementation interfaces deployed in development system. After validating the interface, it is deployed to staging system. Other business system connected the staging system.

Finally all of implementation has been finished and ready to move production, EAI system is deployed into production environment.

I will describe more about deployment environment later.

3) Monitoring and fix

After starting deploying interface to staging system. (Open interface to business team). EAI project team monitors the interfaces. The interfaces always has errors like “Table comlumn mismatch”,”Message type missmatch” etc.

The error let the interface down and it brings complain from business development team.

In implementation phase, support business team to follow up their schedule by matching EAI interface implementation schedule. If delay is occurred, business team try to responsibilities to EAI team for the schedule delay.

And there are many requirement change like number of interfaces, type etc. So in the implementation phase, interface schedule management is very important.

Conclusion.

As i mentioned EAI project has a lot of dependencies to other system or project and their are many requirement changes about interfaces. In EAI project how to manage schedule and environment is very important to success EAI project

Advertisements

Comments»

No comments yet — be the first.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: