Item

Description

TDM (Test Data Management)

TDM offers an automated solution for copying subsets of Business Entities (like customer, order, patient, product and household) from source systems into selected testing environments. This solution provides real, high-quality data for 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 business driven entity approach offering multiple and diverse built-in integrated data management capabilities for an end-to-end management of the data life cycle. For more details, read Fabric Overview.

Broadway

Broadway is a Fabric module that is used for designing 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, read Broadway Overview.

TDM Portal

TDM self-service web application. It is used in TDM setup and in TDM tasks’ creation, execution and monitoring.

LU / Data Product

A Logical Unit (LU, or Logical Unit Type - LUT), also known as Data Product, is a blueprint holding a set of definitions and instructions used for creating and maintaining the required dataset.

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

A micro-database, a small SQL database, is used for storing Data Product / LU Instance (LUI) data. It is stored as an SQLite file, depending on the saved property's definition in the LU Schema.

Fabric Role

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

For more information, read Fabric Credentials Overview.

TDM Permission Group

There are 3 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, read TDM Portal - 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

An Environment is a logical definition of either a source or a target environment, e.g., Production, UAT1, UAT2, etc. An environment can contain multiple systems and data sources. The list of source and target environments available for TDM must be defined in both the TDM Portal and Fabric.

System

A system (product) or application that is installed on 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 Portal. The task can run on selected business entities (with or without related referential tables) or on tables only. The business entities can be either extracted from a source environment or synthetically generated.

Click here for more information about the TDM tasks.

Data Versioning

Data Versioning enables users to keep versions (backups) of data during functional tests and restore 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.

Entity Reservation

The Entity Reservation feature is made to enable a user to reserve (lock) entities in the testing environment and prevent other users from re-provisioning these entities into the testing environment until the user completes the functional tests and can release these entities.

For more information, read Entity Reservation.