Makarand,

Given the problem scenario, I would recommend the following.

1. Perform Unit Testing, System Testing and Performance testing for the core application first.
2. Publish the Test Scenarios to other application testing team and cross-verify that you have covered all the scenarios for the core application.
3. If the applications using the Core system have more requirements or they are planning to use the Core app in a way (not covered in ur testing) then add that as a part of the core testing.

While this will ensure that core system meets all the requirement and will save time in testing as well.

Coming to number of instances for the application. IMHO you need only one instance of the core system as all the other apps will ensure that the test data they create is being deleted by them unless those data also have to be tested across applications.

Hope this helps

Cheers :)
Samir Kumar Mishra
Tel: +61-403-747-809
Email: [EMAIL PROTECTED]
Home: http://samirmishra.tripod.com/
My Attitude in life is best described by my Blood Group…  B +ve

On 3/11/06, catcher_scope <[EMAIL PROTECTED]> wrote:
Hi,
I need some help on this scenario

1) The core project has built a SOA solution that acts as the System of
Record for around 4 entities. The SOA solution would undergo a User
Acceptance test before integrating applications(around 30 at this point
of time) start using it.
2) Each integrating application would go through its SDLC(Unit testing,
System testing, Perf testing, User Acceptance testing etc). We are also
planning to have an integration test that tests the business process
across ALL applications.

In this scenario, How many distinct instances of the core SOA solution
(Web services plus the database) would be needed to ensure individual
applications can do their unit testing, System testing etc without
conflicts/dependencies ?

Thanks
Makarand



SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




Reply via email to