SLIDE 7 10/2/19 ¡ 5 ¡
TDM ARCHITECTURE
1 Capture & define data use case scenario 2 3 4 5 6 Build a Model of the data flow Coverage analysis of existing vs new data sources for all scenarios and models Existing: Clone, Subset, Mask, Purge New: Define & Parameterize model, Create Define data consumption and provisioning approach & methods Make data accessible to testing suites, applications, and environment 7 Automate the process as a set of API/CLI workflows via a self service portal
Test Data as a Service (DaaS)
Create the capability within your TDM practice to allow data consumers (users, processes, applications) to quickly & easily request test data and have it provisioned automatically upon demand. Goal is Speed of Service, Optimal Coverage, Repeatable Process, Automated
Process & Architecture
Request & Provision Test Data using Self-Service Portal
Process to Acquire, Subset, Mask, Archive Synthetic Data Process
TDM CatLog TDM Data Models Prod & Existing Data New Data Requirement Data Injection & Provisioning Data Consumers – Request & Fulfillment Test Data Management Practice Lower Environment s Data Formats API/CLI Driven Dev, Test & Automation DevOps TDM Tools and Process
Coverage Analysis Process Automated Provisioning
Test Data As a Service
WHY TDM?
PEOPLE ¡and ¡Process ¡FIRST ¡ Use the right tool for the job Assemble the Right Team Eliminate Process Friction Prioritize coverage and re-use Roadmap for synthetic data
IMPLEMENTATION KEYS