What drove me into EAI (Enterprise Application Integration) was the opportunity to continuously learn new technologies. Little I knew at the time that, behind each of those technologies was a team with all of its predicaments.
The EAI team is the glue that connects all the edges of the Enterprise Architecture within an Organization. Because of that, projects that spread amongst several applications are paced up or down accordingly to the speed of Integration.
Typical Projects in this context set their milestones aligned with Integration, assembling the calendar accordingly.
However for the Integration Team there are always complications:
#1 - Integration depend on all of the applications
The main requirement is to interconnect applications; one can only start developing when applications crystallize their interface.
#2 - Delays on Integration often fall within the critical path
The need for integration testing is always on the critical path for assurance concerns. Also few applications develop simulators or mock services, and depend heavily on functional integration services for development.
#3 - Workarounds are expected to overcome specification inconsistencies
A great deal of requirements/specification gaps are overcome by workarounds implemented on the integration layer. With less impact for the applications, and using a more agile approach.
But the most relevant fact is that the Integration team acts as the communication channel between Teams. Starting on the analysis and ending as the first line of contact to the Quality Assurance Team during the Test phase.
A great deal of success for integration comes from the relations established between teams. Diplomacy and soft-skills are in demand for managing such an array of stakeholders.
Share your thoughts on this subject!
Typical Projects in this context set their milestones aligned with Integration, assembling the calendar accordingly.
However for the Integration Team there are always complications:
#1 - Integration depend on all of the applications
The main requirement is to interconnect applications; one can only start developing when applications crystallize their interface.
#2 - Delays on Integration often fall within the critical path
The need for integration testing is always on the critical path for assurance concerns. Also few applications develop simulators or mock services, and depend heavily on functional integration services for development.
#3 - Workarounds are expected to overcome specification inconsistencies
A great deal of requirements/specification gaps are overcome by workarounds implemented on the integration layer. With less impact for the applications, and using a more agile approach.
But the most relevant fact is that the Integration team acts as the communication channel between Teams. Starting on the analysis and ending as the first line of contact to the Quality Assurance Team during the Test phase.
A great deal of success for integration comes from the relations established between teams. Diplomacy and soft-skills are in demand for managing such an array of stakeholders.
Share your thoughts on this subject!