Database Validation and Repair Tool for Agile Project Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Agile project management tools lack effective mechanisms for validating and repairing large, complex databases with evolving data structures, leading to inconsistencies and difficulties in managing or troubleshooting issues over time.

Innovation Solution

A software tool that takes snapshots of database data at different time periods, maps hierarchical relationships, and uses an analytics engine to identify and repair anomalies by creating user-selectable controls for modifying data structures, leveraging high-performance caching and predefined rules for validation checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If database data is continuously updated and revised by users, then the database remains dynamic and adaptable to changing project requirements, but data inconsistencies and anomalies accumulate over time

Engineering Contradiction:
Improvedata adaptabilityVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary validation actions by establishing predefined rules and constraints before data is entered or modified. The analytics engine proactively identifies potential anomalies by comparing incoming data against these预先 established rules, preventing inconsistencies before they propagate through the database.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements continuous feedback mechanisms by repeatedly validating data against predefined rules and generating anomaly reports. This feedback loop allows the system to detect, report, and facilitate correction of data inconsistencies, maintaining reliability while allowing continuous updates.

Inventive Principle:
Principle #23Feedback

2Reliability

If comprehensive validation rules are applied to all data in the database, then data quality and integrity are improved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidvalidation processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system applies validation selectively rather than uniformly across all data. The analytics engine identifies and focuses validation efforts on specific areas where anomalies are detected or where predefined rules indicate potential issues, rather than validating every data point equally, thus reducing unnecessary processing time.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system performs partial validation by applying predefined rules to subsets of data that are most critical or likely to contain anomalies. This partial action approach maintains data integrity for key areas while avoiding the time cost of comprehensive validation across the entire database.

Inventive Principle:
Principle #16Partial or excessive action

3Adaptability or versatility

If the database structure becomes more complex to accommodate evolving project management needs, then functionality and versatility improve, but difficulty in managing and troubleshooting increases

Engineering Contradiction:
ImprovefunctionalityVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the complex database into manageable components by organizing data around work task entities with hierarchical relationships. This segmentation allows the analytics engine to validate and analyze specific portions of the database independently, making troubleshooting easier despite overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The analytics engine acts as an intermediary layer between the complex database structure and the user. It handles the complexity of validation rules and anomaly detection internally, presenting simplified reports and repair options to users without requiring them to understand the underlying data structure complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Ease of operation

If manual validation and repair processes are used, then flexibility and user control are maintained, but productivity and efficiency decrease

Engineering Contradiction:
Improveuser controlVSAvoidvalidation efficiency
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system implements self-service capabilities by automatically detecting anomalies, generating repair suggestions, and allowing users to apply repairs with a single action. This automated self-service approach maintains user control while dramatically improving validation efficiency compared to purely manual processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary analysis and generates repair options before user intervention is needed. By pre-processing the data, identifying anomalies, and preparing repair suggestions in advance, the system reduces the time and effort required for manual validation while preserving user oversight and control.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12045214B2Database validation and repair tool
Publication Date: 2024.07.23 AGILE COMPANION TECH LTD
  • US12045214B2 patent drawing
  • US12045214B2 patent drawing
  • US12045214B2 patent drawing

AI summary

A system and method for improving and/or repairing data structures in databases or other structured data such as in project management computer software. Such project management software includes complicated data structures, which are prone to developing inconsistencies and errors over time. The system or method takes snapshots of datasets from the project management software at periodic points in time, ingests the data and maps it to internal data objects. This allows an analytics engine to efficiently perform a range of validation checks for anomalies and other issues that contravene Agile rules by identifying dependencies between individual work task entities and creating links in the data objects to other data objects representing those dependencies. Thus, the system may indicate to the user issues with the data, automate repair of the data structures and provide tools for the user to quickly and efficiently fix the source data.