TDM Glossary

Item

Description

TDM (Test Data Management)

TDM offers an automated solution for copying subsets of Business Entities (Digital Entities) like Customer, Order, Patient, Product or Household from source systems into selected testing environments to provide real, high-quality data to testing teams.

Fabric

K2view Fabric is a data management platform that provides access to data where and when you need it. Acting as a new data layer above existing data sources, Fabric controls data using a patented Digital Entity centric approach offering multiple and diverse built-in integrated data management capabilities for end-to-end management of the data lifecycle. For more details see Fabric Overview.

Broadway

Broadway is a Fabric module that is used to design data movement, its transformation and the orchestration of business flows. Featuring a powerful user interface for creating and debugging business and data flows, Broadway also provides a high-performance execution engine that can be activated by Fabric. For more details see Broadway Overview.

TDM GUI

The self-service web application of the TDM product. Used for TDM setup and for creating, executing and monitoring TDM tasks.

Digital Entity

A digital version of a person, place, or a thing which is usually correlated to a Business Entity.

LU / LUT

Logical Unit (LU) or Logical Unit Type (LUT) is a blueprint holding a set of definitions/instructions used to create and maintain the data of a Digital Entity.

LUI

A Logical Unit Instance (LUI) is a specific instance of a Logical Unit. For example, the data for a specific Customer ID.

MDB / MicroDB

Micro-database, a small SQL database used to store Digital Entity Instance (LUI) data. An MDB is stored as an SQLite file and as a Blob field in the Cassandra Entity table, depending on the saved property's definition in the LU Schema.

Fabric Role

Fabric provides a role-based access control management. Fabric permissions are granted to each given role. Each Fabric user can be assign to one or multiple roles.

For more information see Fabric Credentials Overview.

TDM Permission Group

There are three main types of TDM users, each with different permissions for different activities. Each type is called a Permission Group. The following Permission Groups are supported by TDM: Admin, Owner, and Tester. 

For more information see TDM GUI - Permission Groups.

Business Entity / BE

A Business Entity (BE) represents the main entity of the selected data for provisioning by TDM. A Business Entity can have multiple LUs in a hierarchical structure. For example, a Customer Business Entity consists of Customer Care, Billing, Ordering and Usage LUs.

Environment

A logical definition of a source or target environment. For example, Production, UAT1, UAT2, etc. An environment can contain multiple systems and multiple data sources. The list of source and target environments available for TDM must be defined in the TDM GUI and in Fabric.

Product

A system or application installed in the source or target environment. For example, the UAT1 environment contains CRM and Billing products. Each product can have multiple data sources.

Task

Data provisioning is implemented by creating and executing TDM tasks. TDM tasks are created via the TDM GUI. The following task types are supported by the TDM:

  • Extract task, extracts the selected entities or Reference tables from the selected source environment and saves this data in Fabric for later use.
  • Load task, extracts the selected entities or Reference tables from the selected source environment and copies (provisions) them to the selected target environment.

Data Flux

Data Flux mode enables users to keep versions (backups) of data during functional tests and return to the latest saved version of the data when needed. Users can create an Extract task to create a version of the data and save it in Fabric. To get the extracted version in the testing environment, the tester can create a load task, select the required version and re-load the selected version of the data to the environment instead of the corrupted data.

Previous

TDM Glossary

Item

Description

TDM (Test Data Management)

TDM offers an automated solution for copying subsets of Business Entities (Digital Entities) like Customer, Order, Patient, Product or Household from source systems into selected testing environments to provide real, high-quality data to testing teams.

Fabric

K2view Fabric is a data management platform that provides access to data where and when you need it. Acting as a new data layer above existing data sources, Fabric controls data using a patented Digital Entity centric approach offering multiple and diverse built-in integrated data management capabilities for end-to-end management of the data lifecycle. For more details see Fabric Overview.

Broadway

Broadway is a Fabric module that is used to design data movement, its transformation and the orchestration of business flows. Featuring a powerful user interface for creating and debugging business and data flows, Broadway also provides a high-performance execution engine that can be activated by Fabric. For more details see Broadway Overview.

TDM GUI

The self-service web application of the TDM product. Used for TDM setup and for creating, executing and monitoring TDM tasks.

Digital Entity

A digital version of a person, place, or a thing which is usually correlated to a Business Entity.

LU / LUT

Logical Unit (LU) or Logical Unit Type (LUT) is a blueprint holding a set of definitions/instructions used to create and maintain the data of a Digital Entity.

LUI

A Logical Unit Instance (LUI) is a specific instance of a Logical Unit. For example, the data for a specific Customer ID.

MDB / MicroDB

Micro-database, a small SQL database used to store Digital Entity Instance (LUI) data. An MDB is stored as an SQLite file and as a Blob field in the Cassandra Entity table, depending on the saved property's definition in the LU Schema.

Fabric Role

Fabric provides a role-based access control management. Fabric permissions are granted to each given role. Each Fabric user can be assign to one or multiple roles.

For more information see Fabric Credentials Overview.

TDM Permission Group

There are three main types of TDM users, each with different permissions for different activities. Each type is called a Permission Group. The following Permission Groups are supported by TDM: Admin, Owner, and Tester. 

For more information see TDM GUI - Permission Groups.

Business Entity / BE

A Business Entity (BE) represents the main entity of the selected data for provisioning by TDM. A Business Entity can have multiple LUs in a hierarchical structure. For example, a Customer Business Entity consists of Customer Care, Billing, Ordering and Usage LUs.

Environment

A logical definition of a source or target environment. For example, Production, UAT1, UAT2, etc. An environment can contain multiple systems and multiple data sources. The list of source and target environments available for TDM must be defined in the TDM GUI and in Fabric.

Product

A system or application installed in the source or target environment. For example, the UAT1 environment contains CRM and Billing products. Each product can have multiple data sources.

Task

Data provisioning is implemented by creating and executing TDM tasks. TDM tasks are created via the TDM GUI. The following task types are supported by the TDM:

  • Extract task, extracts the selected entities or Reference tables from the selected source environment and saves this data in Fabric for later use.
  • Load task, extracts the selected entities or Reference tables from the selected source environment and copies (provisions) them to the selected target environment.

Data Flux

Data Flux mode enables users to keep versions (backups) of data during functional tests and return to the latest saved version of the data when needed. Users can create an Extract task to create a version of the data and save it in Fabric. To get the extracted version in the testing environment, the tester can create a load task, select the required version and re-load the selected version of the data to the environment instead of the corrupted data.

Previous