Per Group Code Verification for Complex Projects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional code verification methods are unreliable due to resource overloading and lack of granularity, often resulting in non-useful results when verifying large and complex code projects, as they treat the entire code as a single unit rather than identifying specific non-compliant portions.
Innovation Solution
Implementing per group verification techniques that divide code projects into related groups based on defined relationships between code portions, allowing for separate verification of each group against specific rules, thereby reducing non-useful results and providing more granular feedback.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If static analysis is performed on the complete code project, then verification coverage is improved, but resource consumption increases and reliability decreases
Solution Approach 1:
The patent divides the complete code project into multiple groups based on relationships between code portions. Each group is verified separately through static analysis, which reduces resource consumption and improves reliability by avoiding analysis of the entire complex codebase at once. The segmentation allows verification to focus on specific portions while maintaining overall coverage.
2Reliability
If static analysis is performed on the complete code project, then verification coverage is improved, but resource consumption increases
Solution Approach 1:
The code project is segmented into multiple groups that can be verified independently. This segmentation reduces resource consumption by analyzing smaller portions separately rather than processing the entire codebase simultaneously, while still achieving comprehensive verification coverage across all groups.
Solution Approach 2:
Instead of performing verification on the complete code project at once (excessive action), the patent applies verification to individual groups or portions of code (partial action). This approach reduces resource consumption while maintaining adequate verification coverage for each segment.
3Reliability
If verification is performed on the complete code project, then overall compliance is assessed, but granularity of results decreases
Solution Approach 1:
By dividing the code project into multiple groups and verifying each group separately, the patent achieves both overall compliance assessment and granular results. Each group's verification provides precise information about specific code portions, while aggregation of group results delivers comprehensive compliance evaluation.
Solution Approach 2:
The patent introduces a new dimension of analysis by organizing code into hierarchical groups. This allows verification results to be viewed at multiple levels: individual group granularity and overall project compliance, effectively adding a dimensional layer that simultaneously provides both detailed and aggregate information.
4Reliability
If static analysis is performed on large code projects, then comprehensive verification is achieved, but timing out occurs
Solution Approach 1:
The patent segments the large code project into smaller groups that can be verified independently and in parallel. This segmentation reduces verification time by avoiding the sequential processing of the entire codebase, while maintaining comprehensive verification coverage across all segments.
Solution Approach 2:
Verification is performed periodically on individual groups rather than continuously on the entire codebase. This periodic action on segmented portions reduces total verification time while achieving complete coverage through repeated analysis of each group.
Data Source
AI summary
Various embodiments provide per group verification techniques in which code may be verified against one or more rules on a group by group basis. In one or more embodiments relationships between portions of a module to be verified can be defined. By being aware of relationships between various code portions, various embodiments can divide a module into related groups and perform verification on the basis of the groups. Multiple groups can be derived based at least in part upon the relationships. Each group can then be verified separately for compliance with one or more rules. Verification results can be output for each of the groups.