Organizations that introduce test data management into their daily operations typically assign resources to three distinct groups of activities. One group of activities is required to define business and regulatory requirements when working with test data, i.e. data protection strategies when working with scrambled production data. Another group of activities is related to implementation, the process of defining rules and composing packages of rules that can be executed when test data is needed. The third group is closely related to execution of packages that produce test data on a regular basis or on demand. BizDataX provides support for all three groups of activities.
BizDataX Portal aims at business stakeholders who are responsible for requirements management and sensitive data protection. It enables managing requirements, finding sensitive data within production databases and reporting about activities and results on various levels of the test data provisioning process.
BizDataX Designer enables Test Data Producer role to create and edit BizDataX workflows that consist of rules for data masking, data subsetting synthetic data generation and other data transformation rules. The tool integrates with Microsoft Visual Studio environment to allow designing of data transformation rules visually, using powerful Workflow Editor. Designer comes with an environment to host workflow test runs.
BizDataX Runtime is a robust and scalable hosting environment designed for management and execution of BizDataX packages (i.e. compiled BizDataX workflows). BizDataX Runtime includes a comprehensive set of tools such as tools to organize and configure BizDataX packages, monitor package execution progress or track history of executions and changes made on packages and configurations.
Figure 1: Typical BizDataX usage scenario showing different stakeholder groups and execution environments.
- Business stakeholders including test managers, security officers, audit or legal department can use BizDataX Portal to define data handling, data protection policies and test data requirements.
- Some requirements can be acquired from external tools such as Jira, HP ALM or TFS.
- Business analyst could also add more technical information to policies and requirements by importing information about DB structures and executing sensitive data discovery rules.
- All this information can be accessed by the implementation team that implements the rules and workflows.
- Team (Test Data Producers) implement workflows and rules for data masking, data subsetting, synthetic data generation and other required functionalities using BizDataX Designer and Microsoft Visual Studio Workflow Editor.
- During the implementation workflows and rules, BizDataX Designer can be used to establish links to portal artefacts such as data handling and protection policies or requirements. The links are an integral part of the workflow and help track implementation details and support reporting.
- BizDataX Designer enables workflow testing by using test databases and files with structures similar to production databases. This important feature eliminates the need for accessing the production data at implementation stage.
- When implementation is done, workflows are published to BizDataX Runtime as packages providing configuration options needed for execution in production environment.
- Administrators, or others responsible for execution and production systems, organize packages, setup security and other configuration parameters, enable and disable execution of packages and manage package execution schedules and sequences.
- Rules defined in packages and configured using configuration parameters and credentials are executed in a safe environment by the BizDataX Rule Execution Engine.
- Rule Execution Engine manages access to target databases and files and intermediate data as requested by the rules.
- During rules execution, database clones and other artefacts needed for testing, e.g. files with anonymized data, are produced and prepared for testing.
- Information such as test data labels, e.g. names, IDs or account numbers of candidate customer and account records for specific test cases, are provided (exported) for both manual and automated testing.