Automatically generating code and related artifacts such as application programming interfaces (APIs) and related documentation from an abstract model of a database. The abstract model is derived from a physical model which may be a source such as a legacy database, an entity relationship diagram, or other schema defining the data tables, objects, entities, or relationships etc. of the source. The generated code may be exposed (that is, made visible to the developer in its pre-compiled state) and further configurable and extendable. Any such extended code is maintained separately from generated code. An API and related documentation are also generated from the same abstract model.

Automatically generating code and related artifacts such as application programming interfaces (APIs) and related documentation from an abstract model of a database. The abstract model is derived from a physical model which may be a source such as a legacy database, an entity relationship diagram, or other schema defining the data tables, objects, entities, or relationships etc. of the source. The generated code may be exposed (that is, made visible to the developer in its pre-compiled state) and further configurable and extendable. Any such extended code is maintained separately from generated code. An API and related documentation are also generated from the same abstract model.

In some implementations, a system may receive, from a software repository, a difference file indicating changes, to software code, that was submitted to the software repository. The system may parse the difference file to determine files, associated with the software code, affected by the changes and to determine content associated with the changes. The system may apply rules, from a rule dictionary, based on comparing identifiers, associated with the files, with identifiers included in the rules and based on comparing the content, associated with the changes, with content included in the rules. The system may generate software review checklist items based on applying the rules and output the software review checklist items for display. The system may receive, based on input from a user, confirmation of the changes and commit the changes to the software repository based on the confirmation.

In some implementations, a system may receive, from a software repository, a difference file indicating changes, to software code, that was submitted to the software repository. The system may parse the difference file to determine files, associated with the software code, affected by the changes and to determine content associated with the changes. The system may apply rules, from a rule dictionary, based on comparing identifiers, associated with the files, with identifiers included in the rules and based on comparing the content, associated with the changes, with content included in the rules. The system may generate software review checklist items based on applying the rules and output the software review checklist items for display. The system may receive, based on input from a user, confirmation of the changes and commit the changes to the software repository based on the confirmation.

Techniques are described herein that are capable of automatically generating, revising, and/or executing troubleshooting guide(s). In a first example, an operation is selected based at least in part on a schema and information indicating that the operation is capable of mitigating a category of issues. In a second example, information is analyzed to identify operations performed with regard to service(s) to mitigate issues, and an operation is selected based at least in part on the information indicating that the operation is capable of mitigating a category of issues that includes an identified issue. In these examples, an executable troubleshooting guide is automatically generated to perform the selected operation. In a third example, weights are assigned to features that are extracted from data associated with troubleshooting guide(s), and a subset of the troubleshooting guide(s) is automatically revised based at least in part on the weights corresponding to the subset.

Techniques are described herein that are capable of automatically generating, revising, and/or executing troubleshooting guide(s). In a first example, an operation is selected based at least in part on a schema and information indicating that the operation is capable of mitigating a category of issues. In a second example, information is analyzed to identify operations performed with regard to service(s) to mitigate issues, and an operation is selected based at least in part on the information indicating that the operation is capable of mitigating a category of issues that includes an identified issue. In these examples, an executable troubleshooting guide is automatically generated to perform the selected operation. In a third example, weights are assigned to features that are extracted from data associated with troubleshooting guide(s), and a subset of the troubleshooting guide(s) is automatically revised based at least in part on the weights corresponding to the subset.

An apparatus is provided. The apparatus including a plurality of network interfaces, including a first network interface and a second network interface. The apparatus also includes a processor with two or more independent processing units, including a first independent processing unit and a second independent processing unit. The apparatus further includes a memory having first instructions and second instructions stored thereon. Execution of the first instructions, cause the first independent processing unit to execute operations associated with a first operating system and communicate, via the first network interface, over a bi-direction communication, with one or more platform computing devices. Execution of the second instructions, cause the second independent processing unit to execute real-time operations associated with a second operating system and communicate, via the second network interface, with one or more computing devices each having one or more sensors thereon.

An apparatus is provided. The apparatus including a plurality of network interfaces, including a first network interface and a second network interface. The apparatus also includes a processor with two or more independent processing units, including a first independent processing unit and a second independent processing unit. The apparatus further includes a memory having first instructions and second instructions stored thereon. Execution of the first instructions, cause the first independent processing unit to execute operations associated with a first operating system and communicate, via the first network interface, over a bi-direction communication, with one or more platform computing devices. Execution of the second instructions, cause the second independent processing unit to execute real-time operations associated with a second operating system and communicate, via the second network interface, with one or more computing devices each having one or more sensors thereon.

Techniques are provided for provenance-based software script reuse. One method comprises extracting provenance data from source code including, for example, source code fragments, wherein the extracted provenance data indicates a control flow and a data flow of the source code; encapsulating source code fragments from the source code that satisfy one or more similarity criteria as a reusable source code fragment; and providing a repository of encapsulated reusable source code fragments for reuse during a development of new software scripts. The repository of encapsulated reusable source code fragments optionally comprises a searchable database further including, for example, the provenance data, data annotations, input parameters and generated results for the corresponding source code fragment.

Techniques are provided for provenance-based software script reuse. One method comprises extracting provenance data from source code including, for example, source code fragments, wherein the extracted provenance data indicates a control flow and a data flow of the source code; encapsulating source code fragments from the source code that satisfy one or more similarity criteria as a reusable source code fragment; and providing a repository of encapsulated reusable source code fragments for reuse during a development of new software scripts. The repository of encapsulated reusable source code fragments optionally comprises a searchable database further including, for example, the provenance data, data annotations, input parameters and generated results for the corresponding source code fragment.