The key to developing an Enterprise Application Integration (EAI) architecture is recognizing that there are different levels of integration, each with its own requirements and considerations. Successful implementation of consistent, scalable, reliable, incremental, cost-effective solutions depends on the standards and methodologies that are defined for these levels.
The question arises: How is information shared?
- Within an application?
- Between applications within an enterprise?
- Between departments?
- Between enterprises?
- Directly with customers?
In answering these questions, we use our EAI Methodology – iROAD – covering the spectrum of integration requirements.
The iROAD Methodology was created by adapting Online’s proven Application Development, Testing, and Project Management methodologies to an Integration project. Sample and template deliverables are included in the methodology to provide the team a blueprint for success.
Online created the iROAD Methodology to document our field experiences and techniques in order to accelerate integration implementations for clients. This methodology covers most stages of the development cycle from requirements to deployment.
Each phase of the project contains Assumptions, Roles, Guiding Principles, Best Practices, Risks, Information Expected, and Deliverables. Most of the deliverables identified in iROAD are UML-based, providing technology professionals the ability to quickly grasp and utilize the capabilities of the Integration product.