We claim:
1. A system (100) for integrating and implementing virtual service packages across different service virtualization tools, the system (100) comprising:
an input device (410);
an output device (412);
a memory (406);
a storage (414); and
a processor (404) for configuring:
a virtual isomorph engine (212) to host multiple virtual service package interfaces; and
a router search engine (206) to:
generate data for performing a search on multiple virtual service package interfaces based on a request received from a service virtualization tool, the multiple virtual service package interfaces corresponding to multiple external virtual service packages;
fetch one or more virtual service package interfaces based on the search performed on the multiple virtual service package interfaces using the generated data, wherein each of the fetched virtual service package interfaces is assigned a selection priority value and a weight value;
characterized by:
compute an execution criticality value for each of the fetched virtual service package interfaces based on the selection priority value and the weight value assigned to each of the fetched virtual service package interfaces;
select a virtual service package interface with highest execution criticality value;
invoke the selected virtual service package interface stored in the virtual isomorph engine (212) for executing the selected virtual service package interface; and

send a response generated based on execution of the selected virtual service package interface to the service virtualization tool, wherein the selected virtual service package interface is integratable and implementable across different service virtualization tools.
2. The system (100) as claimed in claim 1 further comprising a dictionary engine (208) configured by the processor (404) to maintain a list of virtual service package names, classification information for each of the virtual service packages, list of identification names of virtual service package interfaces corresponding to the virtual service packages and list of number of virtual service package interfaces available for each of the virtual service packages.
3. The system (100) as claimed in claim 2 comprising a dictionary validation engine (210) configured by the processor (404) to validate information related to the virtual service package interfaces stored in the dictionary engine (208) against the virtual service package interfaces stored in the virtual isomorph engine (212).
4. The system (100) as claimed in claim 1, wherein the router search engine (206) is configured to:
analyze the request to obtain details pertaining to an external web service and information related to a business requirement for implementing the virtual service package corresponding to the requested web service; and
generate, in communication with the dictionary engine (208), data associated with the virtual service package interfaces that correspond to the virtual service package.
5. The system (100) as claimed in claim 1 comprising an isomorph coverage engine (214)
configured by the processor (404) to:
maintain data structures corresponding to each of the virtual service package interfaces stored in the virtual isomorph engine (212); and
update the data structures corresponding to each of the virtual service package interfaces by communicating with real application services that correspond to each of the virtual service package interfaces.

6. The system (100) as claimed in claim 5, wherein the isomorph coverage engine (214) is configured to assign identification names to each of the virtual service package interfaces.
7. The system (100) as claimed in claim 1 comprising a router engine (204) configured by the processor (404) to route the request received from the service visualization tool to the router search engine (206).
8. The system (100) as claimed in claim 7, wherein the isomorph coverage engine (214) is configured to invoke the router engine (204) to route the request to the selected virtual service package interface if it is found that the invoked virtual service package interface does not correspond to the selected virtual service package interface.
9. The system (100) as claimed in claim 1, wherein the router search engine (206) is configured to:
generate a response message that includes details obtained based on execution of the invoked virtual service package interface; and
send the response message to the service virtualization tool for integration and implementation of the selected virtual service package interface.
10. A method for integrating and implementing virtual service packages across different service
virtualization tools, for a system (100) as claimed in claim 1, the method comprising:
generating, via the processor (404), data for performing a search on multiple virtual service package interfaces based on a request from a service virtualization tool, the multiple virtual service package interfaces corresponding to multiple virtual service packages;
fetching, via the processor (404), one or more virtual service package interfaces based on the search performed on the multiple virtual service package interfaces using the generated data, wherein each of the fetched virtual service package interface is assigned a selection priority value and a weight value;

computing, via the processor (404), an execution criticality value for each of the fetched virtual service package interfaces based on the selection priority value and the weight value assigned to each of the fetched virtual service package interfaces;
selecting, via the processor (404), a virtual service package interface with a highest execution criticality value;
invoking, via the processor (404), the selected virtual service package interface for executing the selected virtual service package interface; and
sending, via the processor (404), a response generated based on execution of the selected virtual service package interface to the service virtualization tool, wherein the selected virtual service package interface is integratable and implementable across different service virtualization tools.
11. The method as claimed in claim 10, wherein the virtual service packages emulate behavior of corresponding external application services during testing or an application development operation.
12. The method as claimed in claim 10, wherein the request is analyzed to obtain details pertaining to an external web service interface and information related to a business requirement for executing the virtual service package corresponding to the requested web service interface.
13. The method as claimed in claim 12, wherein the generated data comprises virtual service package names related to the requested web service interface, classification information for each of the virtual service packages, identification names of virtual service package interfaces corresponding to the virtual service packages and number of virtual service package interfaces available for each of the virtual service packages.
14. The method as claimed in claim 13, wherein fetching the one or more virtual service package interfaces based on the generated data further comprises:
fetching one or more virtual service package interfaces for each class of the virtual service packages that correspond to the requested web service.

15. The method as claimed in claim 14, wherein the selection priority value and the weight value is assigned against the identification names of each of the fetched virtual service package interfaces in each class of the virtual service package.
16. The method as claimed in claim 10, wherein the execution criticality value is a numeric value computed using the following formulae: EC(k)=wt(k)*sp(j), where EC represents execution criticality for each virtual service package interface, wt represents weight value, sp represents selection priority value, k represents virtual service package interface for each class j of the virtual service package.
17. The method as claimed in claim 10, wherein selecting the virtual service package interface with the highest execution criticality value comprises:
creating an isomorphic graph with one or more nodes representing each of the fetched virtual service package interfaces, wherein the computed execution criticality is represented against each of the node representations of each of the virtual service package interfaces;
searching the fetched virtual service package interfaces using the isomorphic graph based on identification names of the virtual service package interfaces obtained based on the generated data;
rendering details of all the nodes representing the virtual service package interfaces that correspond to the identification names; and
identifying the node with the highest execution criticality from the rendered nodes, wherein the node with the highest criticality is representative of the most prioritized virtual service package interface for responding to the request message.
18. The method as claimed in claim 10, wherein invoking the selected virtual service package
interface further comprises:
validating if the invoked virtual service package corresponds to the selected virtual service package interface; and
routing the request to the selected virtual service package interface if it is found that the selected virtual service package interface is not invoked.

19. The method as claimed in claim 10, wherein sending a response generated based on execution of the selected virtual service package interface to the service virtualization tool comprises:
generating a response message that includes details obtained based on execution of the invoked virtual service package interface; and
sending the response message to the service virtualization tool for integration and implementation of the selected virtual service package interface.