Independent Audit Module for Application Software
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data auditing systems are application-specific and require modification whenever new data fields or audit features are needed, leading to increased development and maintenance costs, as well as inflexibility in handling different transaction types and regulatory requirements.
Innovation Solution
An independent audit module that can be configured to audit transactions across various application software platforms, allowing for user-defined parameters and metadata management, enabling flexible data storage and reporting without the need for extensive code rewriting or re-validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If data auditing is integrated with application software functional requirements, then the auditing process can be implemented at the time of development, but modification is required whenever new data fields or audit features are needed, increasing development and maintenance costs
Solution Approach 1:
The patent separates the auditing functionality from the application software by implementing it as an independent audit module that can be configured separately. This segmentation allows the auditing component to be developed, deployed, and modified independently from the application software, resolving the contradiction between ease of implementation and adaptability.
Solution Approach 2:
The independent audit module is designed to be universal and configurable across multiple application software platforms and different transaction types. It provides a standardized auditing framework that can adapt to various regulatory requirements and data fields without requiring modifications to the core module, thus achieving both ease of manufacture and high adaptability.
2Adaptability or versatility
If application software is modified to incorporate new audit features, then new data fields can be audited, but extensive code rewriting and re-validation are required
Solution Approach 1:
The patent implements configuration mechanisms that allow audit features to be defined and configured in advance through metadata and parameter settings rather than through code modifications. This preliminary configuration approach enables new audit features to be activated without requiring code rewriting or re-validation, significantly reducing the time required to implement new auditing capabilities.
3Reliability
If application-specific auditing systems are used, then auditing can be implemented for specific transactions, but the system lacks flexibility in handling different transaction types and regulatory requirements
Solution Approach 1:
The independent audit module is designed as a universal auditing system that can handle multiple transaction types and regulatory requirements through configurable parameters and metadata. It maintains auditing accuracy for specific transactions while providing the flexibility to adapt to different transaction types and regulatory frameworks, resolving the contradiction between reliability and adaptability.
Solution Approach 2:
The patent utilizes parameter-based configuration and metadata to enable the audit module to adapt its behavior based on the specific transaction type and regulatory requirements. By changing parameters and configuration settings rather than the core auditing logic, the system maintains reliability for specific transactions while achieving versatility across different transaction types.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
System and methods of data auditing of transaction data of an application software (114) are described. In one implementation, the method includes data auditing of transaction data by an independent audit module (116) where metadata of the application software (114) is received, and an audit table based on at least one of the audit parameters, indicating the extent of audit data of one or more processes is created in an audit database (108) of the audit module (116). Further, triggers for capturing data changes from the application software (114) are generated based on at least one audit parameters. Captured changes data is optimized to reduce the storage requirements of audit data. In another implementation, the result of the analysis is displayed in form of a report in user desired format.