An industrial integrated development environment (IDE) supports collaborative tools that allow multiple designers and programmers to remotely submit design input to the same automation system project in parallel while maintaining project consistency. The industrial IDE also permits localized development of system projects, and provides an infrastructure for intelligently brokering between conflicting edits submitted to common portions of the system project. Project edits submitted to the IDE system, both applied and unapplied, are stored as edit records, allowing edits to be selectively undone or applied either manually or as part of a rollback to a milestone version.

Disclosed herein are techniques for analyzing software delta changes based on functional line-of-code behavior and relation models. Techniques include identifying a prompt to change a first version of code on a controller to a second version of code; constructing, based on the identified prompt, a line-of-code behavior and relation model representing execution of functions of the controller based on the second version of code; performing a signature operation on the generated line-of-code behavior and relation model to produce a signature value; and sending the signature value to the controller; wherein the controller is configured to compare the signature value to a computed signature value that the controller is configured to compute based on the second version of code and determine, based on the comparison, whether to validate the second version of code.

Embodiments herein disclose systems, methods, and computer-readable media for quality control of an object relational mapping (ORM) application and correction of problematic cast functions in the context of a relational database management systems. In embodiments, source code is parsed and portions of source code are identified when those portions of source code include a problematic casting between data types or a mapping between a field and a source table. In embodiments, the source code portions are marked or flagged and a report is generated. The report identifies the marked or flagged source code and further specifies the location of the marked or flagged source code, in embodiments.

Embodiments herein disclose systems, methods, and computer-readable media for quality control of an object relational mapping (ORM) application and correction of problematic cast functions in the context of a relational database management systems. In embodiments, source code is parsed and portions of source code are identified when those portions of source code include a problematic casting between data types or a mapping between a field and a source table. In embodiments, the source code portions are marked or flagged and a report is generated. The report identifies the marked or flagged source code and further specifies the location of the marked or flagged source code, in embodiments.

A system includes a source code repository which stores source code entries, which include instructions in a programming language for performing computing tasks. A code generator receives an input which includes a request to perform a first computing task. Keywords, including a variable-associated keyword and a function-related keyword, are identified in the input. Code-line entries are determined which, when executed in an ordered combination, achieve the first computing task. Based on the variable-associated keyword, variables appearing in the source code repository are determined to declare in order to perform the first computing task. Based on the function-related keyword, functions appearing in the source code repository are determined to define and call to perform the first computing task. A custom code is generated, in the programming language.

A system includes a source code repository which stores source code entries, which include instructions in a programming language for performing computing tasks. A code generator receives an input which includes a request to perform a first computing task. Keywords, including a variable-associated keyword and a function-related keyword, are identified in the input. Code-line entries are determined which, when executed in an ordered combination, achieve the first computing task. Based on the variable-associated keyword, variables appearing in the source code repository are determined to declare in order to perform the first computing task. Based on the function-related keyword, functions appearing in the source code repository are determined to define and call to perform the first computing task. A custom code is generated, in the programming language.

Disclosed are approaches for enforcing requirements that documentation be up to date. In response to initiation of a build process for an application, a source-code file associated with the application is evaluated to determine an identifier and a location for a corresponding documentation file. A determination can be made regarding whether the documentation file exists at the location. Another determination can be made regarding whether each function specified in the source-code file has a corresponding entry in the documentation file. The build process can be halted in response to determining that at least one function specified in the source-code file fails to have the corresponding entry in the documentation file. If the build process is halted, a message can be displayed on the computing device, the message identifying the at least one function specified in the source-code file that fails to have the corresponding entry in the documentation file.

Disclosed are approaches for enforcing requirements that documentation be up to date. In response to initiation of a build process for an application, a source-code file associated with the application is evaluated to determine an identifier and a location for a corresponding documentation file. A determination can be made regarding whether the documentation file exists at the location. Another determination can be made regarding whether each function specified in the source-code file has a corresponding entry in the documentation file. The build process can be halted in response to determining that at least one function specified in the source-code file fails to have the corresponding entry in the documentation file. If the build process is halted, a message can be displayed on the computing device, the message identifying the at least one function specified in the source-code file that fails to have the corresponding entry in the documentation file.

Disclosed herein are embodiments of systems, methods, and products that execute tools to identify non-malicious faults in source codes introduced by engineers and programmers. The tools may execute a machine learning model on the source codes to perform sentiment analysis and pattern analysis on information associated with the source codes to generate annotated source code files identifying anomalies based on the sentiment analysis and the pattern analysis. One or more threat levels are then identified and ranked based on the one or more anomalies and a ranked list of the one or more threat levels is displayed on a graphical user interface of a computer.

Disclosed herein are embodiments of systems, methods, and products that execute tools to identify non-malicious faults in source codes introduced by engineers and programmers. The tools may execute a machine learning model on the source codes to perform sentiment analysis and pattern analysis on information associated with the source codes to generate annotated source code files identifying anomalies based on the sentiment analysis and the pattern analysis. One or more threat levels are then identified and ranked based on the one or more anomalies and a ranked list of the one or more threat levels is displayed on a graphical user interface of a computer.