VALIDATION SERVICE OPERATION

The services are structured in a service oriented architectural design, depicted on high level in the diagram below:

The driving principles of the design are as follows:

  1. eDamis remains to serve as the single point of contact for Data Providers both for data entry and retrieval of results. From a production user perspective, the services remain invisible and interaction is limited to input and output file handling.

  2. Services are loosely coupled, meaning the design excludes direct interaction between services. This helps to minimize dependencies and ensure prompt diagnosis and mitigation in case of the breakdown of service performance.

  3. As services do not directly interface, a separate component performs the orchestration of the workflow itself. This process manager calls the services and ensures data transfer between services. All business decisions driving the process are defined and executed on this level and no decisions are delegated to the services themselves (e.g. decisions based on severity levels). This will enhance the flexibility when configuring or optimizing the workflow as the services are not affected by changes.

  4. Services operate as discrete units with a selective scope. This means the services are called by the process manager as per business process logic, perform a single function (validation), and stay inactive after returning a result until called again.

  5. Validation rules to be executed on a dataset are also located externally and called by the process manager. As of Q4 2016, this principle is an ongoing priority: content validation rules remain part of the service until the availability of a rule repository based on the Validation Transformation Language (VTL).

  6. Validation reports (regardless of outcome) are transmitted by the process manager to Edamis.

  7. Validated datasets are transmitted by the process manager for processing beyond validation.