17938174. INVISIBLE TROJAN SOURCE CODE DETECTION simplified abstract (International Business Machines Corporation)
Contents
- 1 INVISIBLE TROJAN SOURCE CODE DETECTION
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 INVISIBLE TROJAN SOURCE CODE DETECTION - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
INVISIBLE TROJAN SOURCE CODE DETECTION
Organization Name
International Business Machines Corporation
Inventor(s)
Luis Osvaldo Pizana of Austin TX (US)
INVISIBLE TROJAN SOURCE CODE DETECTION - A simplified explanation of the abstract
This abstract first appeared for US patent application 17938174 titled 'INVISIBLE TROJAN SOURCE CODE DETECTION
Simplified Explanation
The abstract describes a computer implemented method for detecting problematic source code by comparing the source code with a rendered version of the code and taking actions based on the differences found.
- Detects problematic source code by comparing source code with rendered version
- Determines difference between source code and rendered source code
- Identifies problematic source code based on the difference
- Performs actions in response to detecting problematic source code
Potential Applications
This technology could be applied in software development and quality assurance processes to identify and address problematic source code efficiently.
Problems Solved
1. Efficient detection of problematic source code 2. Improved software quality and reliability
Benefits
1. Increased efficiency in identifying and addressing issues in source code 2. Enhanced software quality and reliability 3. Streamlined software development processes
Potential Commercial Applications
Optimizing software development processes, improving software quality assurance, and enhancing overall product reliability in various industries such as technology, finance, healthcare, and more.
Possible Prior Art
One possible prior art could be static code analysis tools that help identify potential issues in source code before execution.
What are the potential limitations of this technology?
How does this technology compare to existing solutions in the market?
Original Abstract Submitted
A computer implemented method, apparatus, system, and computer program product detects a problematic source code. A computer system loads a source code into a first memory. The computer system loads a rendered source code into a second memory. The rendered source code is a rendered version of the source code. The computer system determines a difference between the source code in the first memory and the rendered source code in the second memory. The computer system determines whether a problematic source code is present within the source code using the difference. The computer system performs a set of actions with respect to the problematic source code in response to determining that the problematic source code is present in the source code. According to other illustrative embodiments, a computer system and a computer program product for detecting a problematic source code are provided.
