Integration projects are a lot like development projects. We start by determining the precise requirements and understand the integration needs, from a business process perspective, and then determine the data and messages that must flow between each system and/or module. It is especially useful to identify functional domains and boundaries that match the current and future business needs. Some artifacts that are  in this process include: 

• Functional Model using Yourdon Notation, describing Functional Domains, Boundaries and Messages
• Identification of Business Archetype Patterns, Universal Models and Best Practices
  
• Several UML2 artifacts illustrating static and dynamic properties and components of the integrated systems
• Logical data model identifying the master and slave data relationships, of replicated data

Once the Functional and Conceptual Integration Model is defined, this stage specifies the actual components and technologies to be deployed in the integrated solution. UML2 models are used to clearly define the different aspects such as:

• Classes, Objects and Collaboration Diagrams
  
• Sequence, Timing Diagrams and State Machines
  
• Deployment Model

This phase is the actual implementation and coding of the integration components. We try at best to use ready-made Open Source Solutions and Integrations Frameworks. We usually recommend the use of purely decentralized and loosely coupled interfaces, but some clients may prefer a bus-like integration scenario such as the implementation of an Enterprise Service Bus (ESB) that are usually nothing more that a conglomerate of other EAI technologies. There is quite a debate on the best patterns for EAI and we usually support Endpoint-based approach rather than the ESB fashion, although we have worked with both.

Testing, Documentation and Training 

In all our processes, testing is very important. Whenever possible we use Test Driven Development (TDD) techniques for unit and functional tests at the factory (FAT: Factory Acceptance Testing), and always carry out Site Acceptance Tests (SAT) with the client to make sure the new solution will perform as required. As customary, our documentation is extensive and we almost always include a technology transfer stage for our client's personnel.