Phase 1: Analysis Problem definition and analysis is the critical first phase in an integration project. Because the TIBCO ActiveMatrix BusinessWorks graphical user interface is so easy to use, it is tempting to start development right away. However, detailed problem analysis results in a faster over-all development process. By clearly identifying and analyzing the problem, you avoid pursuing dead-end design paths and the steps to solve the problem become apparent. As a rule, it makes sense to start with a business analysis that includes a problem definition, which states your project’s goals clearly. An engineering analysis goes a step further and identifies the components of the integration project, the process flow, error handling, etc. The analysis should include consideration of expansion possibilities. In the example scenario, one could consider expansion to include direct communication with a business partner. Because of the TIBCO ActiveMatrix BusinessWorks distributed architecture, most expansions are straightforward. TIBCO ActiveMatrix BusinessWorks implicitly supports analysis and design by offering a set of objects representing services and activities as the basis for the project flow. The design team can use these objects during project design. See Phase 1: Analysis (Chapter 3). Here are some questions that are commonly asked during analysis: • What are the services my business process will access? In the example, the process is accessing two adapter services (PeopleSoft and Siebel), the web service that supplies shipping information, and an application server. • What are the transports being used? In the example, the adapter services are accessed using TIBCO Rendezvous. The web service is accessed via SOAP. The application service is accessed via JMS.
