CLIAMS:We claim:

1. A data validation system, for data validation, over a communication network, of data transformed from a source repository to a target repository, the data validation system comprising:
a processor;
a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
receive a data transformation specification from a user;
analyze the data transformation specification to determine data transformation rules, wherein the data transformation rules are indicative of a relationship between corresponding fields of the source repository and the target repository;
generate test cases and test scripts based on the data transformation rules;
execute the test cases and the test scripts on the source repository and the target repository to validate the relationship between the corresponding fields of the source repository and the target repository; and
generate a log file indicative of the outcome of the execution of the test cases and the test scripts.

2. The data validation system as claimed in claim 1, wherein the instructions, on execution, further cause the processor to:
determine the number of records on which the test cases and the test scripts are to be executed;
initiate parallel execution of the test cases and the test scripts on determining the number of records to have exceeded a critical threshold; and
initiate serial execution of the test cases and the test scripts on determining the number of records to be less than the critical threshold.

3. The data validation system as claimed in claim 1, wherein the instructions, on execution, further cause the processor to generate, by the data validation system, a report, based on the log file, wherein the report is indicative of whether values sored in the corresponding fields of the source repository and the target repository are in accordance with the data transformation rules.

4. The data validation system as claimed in claim 1, wherein the instructions, on execution, further cause the processor to:
determine a schema of the source repository and the target repository;
identify attributes of the corresponding fields of the source repository and the target repository; and
determine the data transformation rules based on the identified attributes.

5. The data validation system as claimed in claim 1, wherein the instructions, on execution, further cause the processor to ascertain at least one of inconsistent standards between corresponding fields of the source repository and the target repository, discrepancies in data format between the corresponding fields of the source repository and the target repository, difference in structure of data between the corresponding fields of the source repository and the target repository, missing values between the corresponding fields of the source repository and the target repository, data fields filled with default values or nulls in the corresponding fields of the source repository and the target repository, and data anomalies.

6. The data validation system as claimed in claim 1, wherein the instructions, on execution, further cause the processor to::
receive an identifier from a user, wherein the identifier is indicative of an application whose associated data repositories are to be validated;
identify the source repository and the target repository based on the identifier;
receive configuration parameters of the source repository and the target repository, wherein the configuration parameters are indicative of at least one of data formats, structure, and schema of the source repository and the target repository;
receive connection parameters of the source repository and the target repository, wherein the connection parameters are indicative of the authentication details associated with accessing source repository and the target repository;
establish connection with the source repository and the target repository, based on the connection parameters;
identify the corresponding tables and fields of the source repository and the target repository; and
prompt the user to confirm the identified corresponding tables and fields of the source repository and the target repository.
7. A computer implemented method of data validation, over a communication network, of data transformed from a source repository to a target repository, the method comprising:
receiving, by a data validation system, a data transformation specification from a user;
analyzing, by the data validation system, the data transformation specification to determine data transformation rules, wherein the data transformation rules are indicative of a relationship between corresponding fields of the source repository and the target repository;
generating, by the data validation system, test cases and test scripts based on the data transformation rules;
executing, by the data validation system, the test cases and the test scripts on the source repository and the target repository to validate the relationship between the corresponding fields of the source repository and the target repository; and
generating, by the data validation system, a log file indicative of the outcome of the execution of the test cases and the test scripts.
8. The method as claimed in claim 7, wherein the method further comprises:
determining, by the data validation system, the number of records on which the test cases and the test scripts are to be executed;
initiating, by the data validation system, parallel execution of the test cases and the test scripts on determining the number of records to have exceeded a critical threshold; and
initiating, by the data validation system, serial execution of the test cases and the test scripts on determining the number of records to be less than the critical threshold.

9. The method as claimed in claim 7, wherein the method further comprises generating, by the data validation system, a report, based on the log file, wherein the report is indicative of whether values sored in the corresponding fields of the source repository and the target repository are in accordance with the data transformation rules.

10. The method as claimed in claim 7, wherein the analyzing the data transformation specification further comprises:
determining, by the data validation system, a schema of the source repository and the target repository;
identifying, by the data validation system, attributes of the corresponding fields of the source repository and the target repository; and
determining, by the data validation system, the data transformation rules based on the identified attributes.
11. The method as claimed in claim 7, wherein the execution of the test cases and the test scripts further comprise ascertaining, by the data validation system, at least one of inconsistent standards between corresponding fields of the source repository and the target repository, discrepancies in data format between the corresponding fields of the source repository and the target repository, difference in structure of data between the corresponding fields of the source repository and the target repository, missing values between the corresponding fields of the source repository and the target repository, data fields filled with default values or nulls in the corresponding fields of the source repository and the target repository, and data anomalies.

12. The method as claimed in claim 7, wherein the method further comprises:
receiving, by the data validation system, an identifier from a user, wherein the identifier is indicative of an application whose associated data repositories are to be validated;
identifying, by the data validation system, the source repository and the target repository based on the identifier;
receiving from the user, by the data validation system, configuration parameters of the source repository and the target repository, wherein the configuration parameters are indicative of at least one of data formats, structure, and schema of the source repository and the target repository;
receiving from the user, by the data validation system, connection parameters of the source repository and the target repository, wherein the connection parameters are indicative of the authentication details associated with accessing source repository and the target repository;
establishing, by the data validation system, connection with the source repository and the target repository, based on the connection parameters;
identifying, by the data validation system, the corresponding tables and fields of the source repository and the target repository; and
prompting, by the data validation system, the user to confirm the identified corresponding tables and fields of the source repository and the target repository.

Dated this 11th day of March, 2014
SRAVAN KUMAR GAMPA
K&S PARTNERS
AGENT FOR THE APPLICANT
,TagSPECI:TECHNICAL FIELD
The present subject matter is related, in general to data validation and, in particular, but not exclusively to a method and system for validating data in a communication network environment.