Declaration File Modification for Restricted Resource Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing object-oriented programming languages restrict access to resources such as variables and functions, limiting the functionality of test codes by denying them access to private or protected resources.

Innovation Solution

A method that modifies declaration files by removing restriction definitions, allowing test codes to access previously restricted resources by converting them to unrestricted resources, thereby enabling access to these resources during execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access restrictions are enforced on private or protected resources, then resource security and encapsulation are maintained, but test code functionality is limited and cannot access these resources

Engineering Contradiction:
Improveresource securityVSAvoidtest code functionality
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The solution segments the compilation process into two distinct phases: first compiling the original program with access restrictions intact, then separately compiling test code with modified declaration files that have restrictions removed. This allows different access control levels for different code components, resolving the contradiction between maintaining security and enabling test access.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention applies different access control properties to different parts of the system: the original program maintains strict access restrictions on private and protected resources, while the test code environment is configured with modified declaration files that remove these restrictions locally. This localized modification allows test code to access restricted resources without compromising the overall security architecture.

Inventive Principle:
Principle #3Local quality

2Stability of the object's composition

If test code is denied access to private or protected resources, then resource encapsulation is preserved, but testing completeness and functionality are decreased

Engineering Contradiction:
Improveencapsulation integrityVSAvoidtesting efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

The system dynamically adjusts access control based on the compilation phase. During normal program execution, access restrictions are enforced to maintain encapsulation integrity. During test code compilation, the system automatically uses modified declaration files that remove restrictions, enabling complete testing. This dynamic switching resolves the contradiction between maintaining encapsulation and achieving testing completeness.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The invention creates modified copies of declaration files with access restrictions removed, specifically for use during test code compilation. These copied files allow test code to access private and protected resources without modifying the original declaration files, thus preserving encapsulation integrity while enabling comprehensive testing.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If declaration files are modified to remove restrictions, then test code can access restricted resources, but original program integrity may be compromised

Engineering Contradiction:
Improvetest code access capabilityVSAvoidprogram integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary compilation of the original program with intact access restrictions before modifying declaration files for test code compilation. This ensures that the original program binary is created with full security measures in place, while subsequent test code compilation uses modified files. This preliminary action sequence prevents any compromise to the original program integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention extracts the access restriction definitions from the declaration files to create separate modified versions. The original declaration files with restrictions remain unchanged and are used for compiling the main program, while extracted and modified versions without restrictions are used solely for test code compilation. This separation ensures program integrity is maintained while enabling test access.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8671456B2Accessing restricted resources in computer programming
Publication Date: 2014.03.11 SAP PORTALS ISRAEL
  • US8671456B2 patent drawing
  • US8671456B2 patent drawing
  • US8671456B2 patent drawing

AI summary

A computerized method for providing a computer code an access to a restricted resource of a computer program, comprising modifying an at least one duplicate of an at least one declaration file of the computer program by removing a restriction definition of an at least one resource of the computer program that is referred to by the computer code, thereby generating an at least one modified declaration file, and building a computer application comprising the computer code and also the computer program as being dependent on the at least one modified declaration file, thereby providing access to the at least one resource originally defined as restricted, and an apparatus for performing the same.