The SOAmods system uses the architecture concept called separation of concerns to organize the functional tiers of the platform. There are two driving factors Service Oriented Architecture (SOA) and Component based Architecture in this project.

Service orientated architecture (SOA) is an architecture pattern that exposes system functionality as XML services .The main features of a service are XML interfaces which in-cap the input and output data structures, Business Rules for processing any request through system and different types of services (Asynchronous and synchronous). Whereas the SOA Modules are organized in three functional tiers FOS (Front-office Services providing integration with customer facing applications), SPP (Service Processing Platform to provide the automation and workflow) and BOS (Back-office Service providing corporate business applications).

Technically this project has 5 modules, (Apache Tools, Registration, ERP, CRM, and Sales Portal), so we performed testing accordingly.

First of all we created test conditions for each of the 5 modules according to the technical specification then learn the Functionality of applications and mapped them in a testing metrics, in XML schemas reviewing we understand the GUI and the fields/data elements that are required and optional and mapped then in a data mapping sheets .Understand XSDs and WSDLs messaging by using the application GUI. Understand the data fields required in the SOAP messages by entering data manually. After mapping the data in data mapping sheets we created the SOAP messages (XML) for each of the web services, execute the created SOAP messages using the Test Harness and Comparison the results of SOAP message with manual data entering-interface (entering data via the application GUI).

We also have performed the system integration testing and validated the flow of data through out the applications by end-to-end testing. We used Bugzilla for bug logging and tracking.

During the whole project timing is one of the major challenges we have faced. Another big challenge for us is to create the right Soap messages for right services, to overcome this issue we intensely studied the architecture of the WDSL which are the backbone of the whole system and develop the soap request very meticulously because these are the key element on which whole system is reliant.