It is 360T’s goal to enable true straight-through-processing (STP), further integrating robust and proven infrastructures already existing at customer’s sites. To achieve this goal, 360T solutions are built in an open, modular architecture and with ready-developed integration adaptors (standard interfaces) to the most frequently used front office systems. These integration adaptors provide integration and mapping services from the 360T network data model to the third-party systems.		This way, 360T solutions fit harmoniously into almost any constellation and environment in order to bridge the gap to full-scale STP, with very modests costs and operative disruptions involved. 360T has developed a very detailed project management methodology for the implementation and integration phase at customer’s sites, providing a maximum level of efficiency and smoothness in the collaboration of designated project stakeholders:
	The requirement definition phase initiates the integration project. The aim of this phase is to translate the customer’s individual preferences into a detailed requirement specification. Organizational and staff requirement definitions are also an important part of this phase. The purpose of the requirement analysis phase is to produce a clear and detailed definition of the technical requirements of the integration, thus they have to be categorized, analysed, controlled and approved at every stage. Risk management and configuration management are also introduced in this phase. The implementation phase covers the physical connection of 360T components to the customers existing infrastructure according to the detailed requirement specification. Depending on the level of customization required, there will also be a phase of designing, coding and testing individual interfaces. At the same time, the implementation team prepares and conducts unit and module testing. Module integration takes place after that, simoultaneously with the user manual drafted and the system test plan prepared. Controlling requirement changes, quality assurance and reassessment measures are inevitable for a scheduled implementation and a smooth transition to system testing. The purpose of the system testing phase is to verify the end-to-end functionality of the system in satisfying all requirements and specifications. During this phase, the implementation team executes the tests specified, and documents the results, providing an audit trail for quality assurance. The acceptance test phase verifies that the system meets its requirements in the operational environment. The acceptance test team and the implementation team have to work closely together. The first round of testing is usually executed by the implementation team, which also provides training for the acceptance test team, who then assumes responsibility for test execution during the subsequent rounds. Acceptance testing is complete when each test item specified in the acceptance test plan has been succesfully completed and the system is accepted by the customer.