A design assistance tool, which assists a design of at least one process, defines a metamodel using at least one metaclass, performs a design of the at least one process using the metamodel, stores a content of the design in a database as a design content, displays the design content as a view on a display, and performs creation, modification, or deletion of at least one of the metamodel or a design result based on the metamodel using the view on the display. The view on the display includes multiple view types described in different formats. When the creation, modification, or deletion of at least one of the metamodel or the design result based on the metamodel is made using one view type, corresponding design information is stored in the database, and the creation, modification, or deletion is reflected in another view type based on the stored design information.

A design assistance tool, which assists a design of at least two processes includes a database and a display, and is configured to: define a metamodel using one or more metaclass in each of the at least two processes; and perform a design of each process using the corresponding metamodel. The metamodel in one process has a derivation relationship and a different relationship with the metamodel in another process, the database stores the metamodel in one process and the metamodel in another process in associated manner according to the derivation relationship and the different relationship. In the derivation relationship, which is used as trace information, the one or more metaclass in one process is defined based on content of the one or more metaclass in another process. A design result of the process and the derivation relationship used as trace information are displayed in a view of the display.

A processor may identify an occurrence of a code change for a microservice hosted in a container. The processor may generate a representation of the code change. The processor may identify, utilizing an AI model, a set of microservice containers having microservices affected by the code change. The processor may determine recommended changes to system environments for one or more microservice containers of the set of microservice containers.

Disclosed are techniques for two-way synchronization of infrastructure-as-code templates and instances, including a method comprising detecting changes to a run-time state of a system and, in response to detecting a change, triggering an update of a current run-time state model. The method may further comprise, in response to updating the run-time state model, comparing the updated model to a current model using a template in a local repository instantiated as the current model. The method may further comprise, in response to the comparison determining a structural difference between the updated model and the current model, merging the updated model and the current model into a new model; and updating a local clone of a repository of the template with the new model. The method may further comprise, in response to the comparison determining no structural difference between the updated model and the current model, pushing changes to a remote repository.

An open compiler system for the construction of safe and correct computational systems. This system allows a user to define multiple computational resources, each of which containing multiple computations, which, together, provide some desired functionality. This system generates the artifacts required to create such computational resources, may verify logical properties of such a system, may integrate user-defined programs in the process of compiling such artifacts, and may allow for the deployment, debugging, and monitoring of such computational resources.

Systems and methods may generate code, for a model, with one or more service access points generated and at locations in the code based on an analysis of model constraints and deployment specifications (e.g., RTE specifications or OS specifications). The systems and methods may analyze the model and identify a functionality that needs an RTE service. The system and methods may receive deployment specifications. The systems and methods may generate code for the model, where an analysis of model constraints and the deployment specifications determine which service access points are generated and where in the code the service access points are located. In an embodiment, the code may be executed by different RTEs. In an embodiment, the systems and methods may determine, based on the analysis of the model constraints and the deployment specification, one or more admissible implementations for an RTE service that may be implemented in different ways.

Systems and methods may generate code, for a model, with one or more service access points generated and at locations in the code based on an analysis of model constraints and deployment specifications (e.g., RTE specifications or OS specifications). The systems and methods may analyze the model and identify a functionality that needs an RTE service. The system and methods may receive deployment specifications. The systems and methods may generate code for the model, where an analysis of model constraints and the deployment specifications determine which service access points are generated and where in the code the service access points are located. In an embodiment, the code may be executed by different RTEs. In an embodiment, the systems and methods may determine, based on the analysis of the model constraints and the deployment specification, one or more admissible implementations for an RTE service that may be implemented in different ways.

A design assistance tool: defines a metamodel using one or more metaclass in each of at least two processes and performs a design of each process using the corresponding metamodel; defines a relationship between one metaclass included in one process and one metaclass included in another process as a possession relationship or a reference relationship; displays a design result based on the metamodels as a view on a display; and, in response to an occurrence of an inconsistency in the possession relationship or the reference relationship between the one metaclass included in one process and the one metaclass included in another process due to creation, modification, or deletion of one metaclass in any one of the at least two processes, allows the inconsistency and displays the inconsistency on the view of the display.

Embodiments described herein provide a round-trip engineering system. During operation, the system can maintain an intermediate system representation (ISR) for a set of artifacts of a piece of software. The set of artifacts can include a piece of code and a development model. The ISR can remain persistent upon synchronization of the set of artifacts. The system can incorporate, in a respective component of the ISR, a reference to a code block in the piece of code and a corresponding element in the development model. If the system determines a first update in a first segment of a first artifact of the set of artifacts, the system can identify a second segment in a second artifact from the set of artifacts based on a corresponding component in the ISR. The system can then propagate a second update to the second segment to reflect the first update in the first segment.

A method of facilitating bidirectional programming of a user may include receiving an original program source code and evaluating the original program source code in the forward direction to generate a program output. The evaluation may occur in a programming environment. The program output may be displayed, and an indication of the user corresponding to modifying the program output may be received. The modified program output may be evaluated to generate an updated program source code, wherein the updated program source code, when evaluated, may generate the modified program output. The modified program output may be displayed in a display device of the user. A computing system including a bidirectional programming environment may also be included.