An Avanade Blogging Community

Welcome to An Avanade Blogging Community Sign in | Join | Help
in Search

Nico Joos (Avanade)

Integration projects

 

Previous posts in my blog, for those who have read them, were about some general project management related topics. This post will cover some thoughts about integration projects in specific.

In IT we all know that the integration of 2 systems is often not more than 1 line between 2 objects on a canvas, but the line implies a lot more than it suggests. We all love to draw those objects, and to connect them using simple lines. In fact this is what we do when we want to convince people about an integration opportunity, in order to put things as easy as possible.

Nevertheless we should take a moment to consider the things that should be taken into account when we are planning to implement.

 

Integration is about communication. 2 systems are going to work together to exchange information from to the other. There will be senders and there will be receivers. There will be a medium and there will be a language. I already stated in previous posts the importance of communication in PM. Now we'll match this to integration projects.

 

Please review the following key tasks:

  • Define the actors: senders, receivers
  • Define the medium: LAN, WAN, Internet, ...
  • Define the language: XML, flat files, EDI, ...

 

Once you have considered these key elements of classic communication fundamentals, you will be coping with lots of other details. You find yourself defining the communication messages; the layout of these messages; the schema they should comply with.

 

It is not the intention of this post to explain from a to z each step in order to analyse an integration project. I just want to provide you with the fundamentals, and even a different approach on how to think about integration. Don't fall into the trap of getting too technical too soon in the project. Try to analyse things rather technology independant. Soon you will find yourself creating a blueprint of a complete architecture, ready to be translated into the best technological architecture, dealing with the overall requirements you stated in the blueprint.

 

I advise you to read more information about how to architect the integration of systems using the following resources:

 

 

Kind regards,

Nico

Published Tuesday, June 17, 2008 3:18 AM by Nico Joos

Comments

No Comments
Anonymous comments are disabled

This Blog

Post Calendar

<June 2008>
SuMoTuWeThFrSa
25262728293031
1234567
891011121314
15161718192021
22232425262728
293012345

Syndication