File-Based Table Content Transport in Software Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software development systems are inadequate in managing tabular data, leading to an inability to establish a unified lifecycle for code and tabular data within software applications.
Innovation Solution
The system exposes files as database tables and builds application-specific data management applications, integrating tabular data into the application lifecycle through configuration set definition files and configuration data files, using a two-table structure for translatable text management and supporting extension files to overwrite original data, ensuring conflict-free storage and simplified access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing software development systems are used to manage tabular data, then code management is supported, but tabular data management capability is lacking
Solution Approach 1:
The patent merges tabular data management with existing code management systems by treating configuration data files as source files. The system integrates tabular data into the software development lifecycle by using a unified file-based approach where configuration data is stored in .cdt files alongside code files, managed by the same version control and build systems, thereby extending the versatility of existing systems without adding separate complex infrastructure.
Solution Approach 2:
The system achieves universality by creating a multi-functional platform that handles both code and tabular data through a single unified interface. The software development system is enhanced to simultaneously manage source code files and configuration data files, providing version control, validation, and deployment capabilities for both types of artifacts through the same toolset, eliminating the need for separate specialized systems.
2Stability of the object's composition
If tabular data is managed separately from code, then data management is possible, but unified lifecycle management is not achieved
Solution Approach 1:
The patent combines tabular data and code into a unified lifecycle by treating configuration data files as first-class citizens in the software development process. Both code and configuration data undergo the same lifecycle stages: development in the same environment, version control through the same system, validation through integrated checks, compilation into runtime artifacts, and deployment together. This merging ensures stability of the unified lifecycle composition.
Solution Approach 2:
The system performs preliminary actions by validating configuration data files during the build process before deployment. The build system automatically validates the syntax and semantics of configuration data files, ensuring they meet required standards before the application is deployed. This preliminary validation prevents runtime errors and simplifies maintenance by catching issues early in the development cycle.
3Adaptability or versatility
If configuration data is activated during runtime, then flexibility is improved, but activation time increases
Solution Approach 1:
The system performs configuration data activation as a preliminary action during the build process rather than at runtime. Configuration data files are validated, processed, and activated before the application is deployed. This preliminary activation ensures that configuration data is ready and validated before runtime, providing flexibility for different configuration scenarios while avoiding time-consuming activation operations during runtime execution.
Solution Approach 2:
The system creates runtime artifacts by copying and processing configuration data files during the build process. Configuration data is transformed into the appropriate runtime format and stored alongside compiled code. This copying approach allows configuration data to be prepared in advance and efficiently loaded at runtime without requiring complex activation operations, reducing activation time while maintaining flexibility.
Data Source
AI summary
A system includes reception of a configuration set definition file defining the structure of one or more customizing tables of a software application, reception of a configuration data file including data for the one or more customizing tables, and, during activation of the software application in a run-time system, generation of the one or more customizing tables based on the configuration set definition file, generation of a service to access the configuration data file, and population of the one or more customizing tables with data of the configuration data file.