An Integration bus technology allows a multi-tool integration in bus architecture. It also offers a significant savings in integration effort and cost over ad-hoc point-to-point integrations since the number of distinct integration code pieces for integration bus is ‘n’ which is substantially less than n*(n-1)/2 for point-to-point integration for ‘n’ number of tools.
- Integration Bus allows for a two way total synchronization between two tools for a particular Entity. This two way synchronization is necessary to keep all the information current in both tools.
- Integration Bus enables integration between multiple tools managing the same type of items. For example a transparent synchronization among multiple Requirements Management tools will keep the particular users of each tool aware of what is happening in the other tools.
- Integration Bus synchronizes not just the data but also relations between items Synchronization of data is just the starting point of any meaningful integration. A bigger value is gained by synchronization of the relations among these data.
- Integration Bus allows business rule to decide when and what to replicate across different tools. For example not all Requirements need to be replicated from the Requirements management tool to the Test management tools but only those which are approved.
- Integration Bus enables federation of data in terms of getting the data from other repositories on-demand. It is not necessary or even desirable to have all data from all tools to be replicated in the other tools.
An on-demand access of data allows minimization of the data replication and network traffic.