Test Data Management via Reservation Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Shared databases used for testing often experience collisions when multiple users access the same data, leading to over-provisioning and lost productivity, and isolated database management systems are complex and inflexible.

Innovation Solution

A computer-implemented method that reserves test data by determining its availability in a source database and transferring a copy to a test database, using a reservation database to manage user access and prevent collisions, allowing multiple users to test without interfering with each other.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple users access the same shared database for testing, then data sharing efficiency is improved, but collisions occur between users leading to lost productivity

Engineering Contradiction:
Improvedata sharing efficiencyVSAvoidlost productivity due to collisions
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by checking the reserved status of test data before allowing user access. The reservation database pre-allocates test data to specific users or testing applications, preventing collisions before they occur. This advance reservation mechanism ensures that multiple users can access the shared database simultaneously without interfering with each other's testing operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If isolated databases are created for each user, then collisions are prevented, but system complexity and infrastructure cost increase

Engineering Contradiction:
Improvecollision preventionVSAvoiddatabase management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Instead of creating multiple isolated databases, the system creates a copy of the test data in a reservation database. This copy contains reservation status information that tracks which test data is allocated to which user or testing application. The reservation database acts as a lightweight proxy that prevents collisions without requiring multiple full database instances, thus reducing infrastructure complexity while maintaining collision prevention.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If isolated databases are frequently created or modified for new users, then user-specific testing requirements are met, but maintenance complexity increases

Engineering Contradiction:
Improveuser-specific testing flexibilityVSAvoiddatabase setup and maintenance ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The reservation database uses dynamic record structures that can be easily modified to accommodate new users or testing applications. When a new user needs test data, the system simply creates or updates reservation records in the existing reservation database rather than creating new database instances. This dynamic approach allows flexible allocation and reallocation of test data to meet changing user requirements while maintaining a single, manageable database infrastructure.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9513997B2Test data management
Publication Date: 2016.12.06 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US9513997B2 patent drawing
  • US9513997B2 patent drawing
  • US9513997B2 patent drawing

AI summary

A method for managing test data includes receiving a request indicative of a testing application from a requesting user and identifying a plurality of test data in a source database matching the request. Further, the method includes determining a reserved status of the plurality of test data, and, when the reserved status indicates that the plurality of test data is not reserved by the user other than the requesting user, reserving the plurality of test data for the requesting user. Still further, the method includes transferring a copy of the plurality of test data to a test database, wherein a testing application executes based on the copy of the plurality of test data stored in the test database.