Abstract: A graphical user interface described herein can allow a user to easily explore and interact with a complex software application in a distributed computing environment. In one example, a system can generate a graphical user interface (GUI) for display on a display device. The GUI can depict a topological view of a group of software components of a distributed software application in a distributed computing environment. The topological view can include a group of nodes representing the group of software components. Each node in the group of nodes can represent a software component and have a status indicator for at least one container pod including the software component. The topological view can also include at least one link between the group of nodes, where the at least one link represents at least one relationship among the group of software components.

Abstract: A model based traceability framework is provided in an integrated development environment. The model based framework is embeddable, or deployable, in any application or plugin within the integrated development environment. A database provides scalable persistence of the model and traceability links created using the model. The framework comprises an underlying model that is created by an administrator through a table schema. Tools using the framework allow the creation and management of traceability links, which may be created during code generation or manually through a user interface. An administrator manages the model by creating and maintaining artifact information, traceability link types, and traceability link information in tables. A traceability tool, which may a standalone application or a plugin to an existing tool, allows users to create, update, and delete traceability links. The traceability tool may also allow users to query traceability links.

Abstract: A system and method for automatic instance data mapping generation is presented. A developer uses edit commands, such as mouse commands and keyboard commands, to update a model. For example, a software developer may upgrade “Application XYZ” from version 1.0 to version 2.0 in order to include a simpler approach to import images, as well as the ability to import newer image format types. As a developer updates a model using edit commands, the edit commands are stored in a migration mapping definition. In turn, the migration mapping definition is deployed, along with the updated model, to an end user. The end user then uses the migration mapping definition to migrate instance data generated by the original model to instance data that is usable by the updated model.

Abstract: A system and method for using a transformation engine to dynamically transform source instance document changes to target instance document changes is presented. A mapping developer creates and stores “model mapping definitions” that map source model elements to target model elements. In turn, the transformation engine receives source instance document changes from a user, and identifies the model mapping definition that corresponds to the changes. The transformation engine analyzes the model mapping definition, and locates a transformer that is defined in the model mapping definition. As a result, the transformation engine uses the transformer to generate a target object based upon the changes to the source instance document. The target object is inserted into a target instance document, which the user views.

Abstract: A system and method for developing software using dynamic dual-mode model and data entry is presented. During development, a model developer uses a model window and an editor window to create a model-driven editor. The model window displays model data, and the editor window displays instances of the model data, which results in the model-driven editor. When the developer is ready to deploy the model-driven editor, the model developer simply inhibits the model window. Therefore, the models are not compiled during deployment and, in turn, the model developer does not need to test compiled code. Since the model-driven editor relies upon self-contained models, the models may be updated, added, or removed locally or remotely on an individual basis. In one embodiment, the end user is able to re-enable the model window in order to view model data.