Action Log Schema for Context-Rich Software Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software logging techniques are inefficient in capturing context and workflow information, leading to increased memory and energy usage, as they often include all data fields of context objects in action logs rather than linking them efficiently.
Innovation Solution
The proposed solution involves generating an action log type that includes object properties, action parameters, and an action context associated with editing a target object, where the action context comprises information from a second object type, state changes, metadata, and action rules, allowing for efficient logging by linking relevant objects rather than including all context data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If all data fields of context objects are included in action logs, then comprehensive logging information is achieved, but memory and energy usage increase
Solution Approach 1:
The patent extracts only the essential elements needed for logging (action identifiers, target object identifiers, and contextual relationships) while leaving out the complete context object data. This is achieved through generating action logs that reference context objects by identifier rather than embedding full context object data, thereby reducing memory storage requirements and energy consumption while preserving the ability to retrieve comprehensive information when needed.
Solution Approach 2:
The patent creates simplified copies of context information in the form of action logs that contain only essential referencing data (identifiers and relationships) rather than complete data copies. These action log entries serve as lightweight references that can be expanded when full context is required, balancing information completeness with efficient resource usage.
2Loss of information
If action logs include extensive context data, then detailed workflow information is captured, but logging efficiency decreases
Solution Approach 1:
The patent extracts only the critical workflow information elements (action type, target object, and contextual relationships) while omitting redundant or derivable data. This extraction approach enables rapid log generation and processing while maintaining sufficient detail for workflow analysis, thereby improving logging efficiency without sacrificing essential information.
Solution Approach 2:
The patent performs preliminary structuring of logging data by establishing action log types with predefined schemas that include only essential fields. This preliminary organization allows for efficient log generation and processing, as the system doesn't need to process or filter extensive context data during the logging action itself, thereby improving logging efficiency.
3Reliability
If all context object fields are stored in action logs, then complete audit trail is maintained, but storage requirements increase
Solution Approach 1:
The patent extracts and stores only the essential audit trail elements (action identifiers, timestamps, user identifiers, target object identifiers, and contextual relationships) while excluding redundant or derivable information. This extraction maintains the完整性 of the audit trail for compliance and analysis purposes while significantly reducing the volume of data that needs to be stored.
Solution Approach 2:
The patent introduces action log types as intermediary structures that reference context objects by identifier rather than embedding complete context object data. These intermediary action logs serve as efficient storage vehicles that maintain audit trail completeness through relational references, allowing the system to store minimal data while preserving the ability to reconstruct complete audit information when needed.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed are systems and methods for validations related to software. In some embodiments, a method for building software with software action logging, the method comprises: accessing a target object type, the target object type comprising one or more object properties; accessing an action type, the action type comprising one or more action parameters and associated with one or more action rules, the action type associated with editing a target object of the target object type; generating an action log type comprising at least one of the one or more object properties and at least one of the one or more action parameters, the action log type further comprising an action context associated with an action of the action type.