A method includes identifying a plurality of consumption layer objects, at least two of the plurality of consumption layer objects being associated with a different framework and each of the plurality of consumption layer objects include a plurality of business objects, generating a plurality of interface objects each corresponding to a framework, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation, associating metadata with the plurality of interface objects, and associating a runtime interface with the plurality of interface objects.

A system includes a first non-transitory computer-readable storage medium and a second non-transitory computer-readable storage medium each having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform steps. The steps associated with the first non-transitory computer readable medium include generating a Service Adaptation Definition Language (SADL) definition for each of a plurality of business entity types, the SADL definition being based on an intermediate representation of each of the plurality of business entities, and publishing the SADL definition as a service of a SADL engine. The steps associated with the second non-transitory computer-readable storage include discovering the SADL definition and displaying, on a user interface, a representation of the SADL definition, the user interface configured to enable selection of two or more business entity types each associated with a different model layer framework.

A system validates code ownership of software components identified in a build process. The system receives a pull request identifying a set of software components. The system analyzes code ownership of each software component using machine learning. The system provides features describing the software components as input to a machine learning model. The system determines based on the output of the machine learning model, whether the code ownership of the software component can be determined accurately. If the system determines that a software component identified by the pull request cannot be determined with high accuracy, the system may block the pull request or send a message indicating that the code ownership of a software component cannot be determined accurately.

A system configuration derivation device calculates a first evaluation value indicating an evaluation of a similarity between a specific embodiment rule application and a candidate of the embodiment rule application, wherein the specific embodiment rule application is included in a design history, the design history indicates a history of in a case where an embodiment configuration is obtained by repeatedly applying an embodiment rule to an abstract configuration; selects, based on a second evaluation value, a specific abstract configuration among the abstract configurations obtained by applying the embodiment rule to the new configuration one or more times, wherein the second evaluation value indicates the evaluation of the similarity with the design history, of the entirety of one or more applications of the embodiment rule until the abstract configuration is obtained from the new configuration; and repeats the embodiment rule application to the selected specific abstract configuration.

The present technology adds code to a top level build configuration file of a configuration program that will gather metrics for each invocation of a build. These metrics are sent to a commonly accessible metric server for future analysis. The metrics are collected for a distributed engineering team over several machines. Compilation time metrics may then be collected for each compilation event and those metrics are analyzed by a common aggregator.

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generated aggregated dependencies between software elements in a code base. One of the methods includes receiving a request to generate implicit dependencies introduced by remote procedure calls in a project. A registration of a remote procedure call is identified, wherein the registration of the remote procedure call specifies a target function and a name for the remote procedure call. An invocation of the remote procedure call using the name for the remote procedure call is identified, wherein the invocation occurs in a source software element of the project. A definition of the target function of the remote procedure call is identified, wherein the target function is defined in a target software element of the project. A new dependency is generated, the new dependency being a dependency from the source software element to the target software element.

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for generated aggregated dependencies between software elements in a code base. One of the methods includes receiving a request to generate implicit dependencies introduced by remote procedure calls in a project. A registration of a remote procedure call is identified, wherein the registration of the remote procedure call specifies a target function and a name for the remote procedure call. An invocation of the remote procedure call using the name for the remote procedure call is identified, wherein the invocation occurs in a source software element of the project. A definition of the target function of the remote procedure call is identified, wherein the target function is defined in a target software element of the project. A new dependency is generated, the new dependency being a dependency from the source software element to the target software element.

A device may provide an interface for an interactive programming environment and may receive a command to display information about an object. The device may provide, based on the command, the information about the object, using: a first display interface that presents the information about the object in a first format that is applicable to users of the object. A second display interface, for the object, may present the information about the object in a second format, different from the first format, the second format including information about the object that is applicable to authors of the class or to authors of subclasses corresponding to the object. The first and second display interface may present the information, about the object, based on a state of the object and/or based on a display section of the information (e.g., certain information may be presented in a header section of the display).

A workflow development system is described herein that includes a graphical user interface (GUI) that is configured to selectively and dynamically allocate relatively more of a display area to a particular one of a plurality of different, simultaneously-displayed workflow step representations than is allocated to the other workflow step representation(s) to facilitate user interaction the particular workflow step representation. Such allocation may be carried out in response to user interaction with the particular workflow step representation or in response to a determination that a user is otherwise focused on the particular workflow step representation. In embodiments, the workflow step representations represent different workflow steps in a series of workflow steps. In further embodiments, the workflow step representations represent different workflow steps that may be performed depending upon the evaluation of a condition.

A workflow development system is described that provides a developer with a search utility for finding steps for inclusion in a workflow. The system also automatically generates a meaningful name and/or graphical representation for a workflow. The system also provides a graphical user interface that represents output parameters of a first workflow step as user-interactive objects. These objects can be interacted with to cause the objects to be inserted into a data entry element that is used to specify a value for an input parameter of a second workflow step. When executable logic representing the first and second workflow steps is generated, the insertion of the objects into the data entry element has the effect of causing the value of the input parameter of the second workflow step to be defined to include the values of the output parameters that correspond to the inserted objects.