Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including methods for generating visualizations. On a client side, a user request is received for an inter-entity call visualization. Code analysis data is accessed. A visualization model is built. The visualization is shown. User inputs are received for interacting with the visualization. The visualization is updated based on the received user inputs. On a server side, a request is received for code analysis data. The requested data collected, including running analyzers for any available data. The requested data is sent. The code analysis data can be used for other purposes than visualizations.

Abstract: The disclosure generally describes methods, software, and systems, including a method for defining and using models. A model definition language is provided for defining models. The model definition language includes elements of a meta-model. The elements define, for a model, a root element of the model and plural participant instances of the model. Each participant instance is linked with the root element. Each participant instance defines at least one of plural participants of the model. Each participant instance is an instance of a participant class. A relation port for the model defines plural relations and flows among the plural participants. Each relation is defined by a relation instance being of a relation class and defining a relationship between participants.

Abstract: The disclosure generally describes methods, software, and systems, including a method for defining and using models. A model definition language is provided for defining models. The model definition language includes elements of a meta-model. The elements define, for a model, a root element of the model and plural participant instances of the model. Each participant instance is linked with the root element. Each participant instance defines at least one of plural participants of the model. Each participant instance is an instance of a participant class. A relation port for the model defines plural relations and flows among the plural participants. Each relation is defined by a relation instance being of a relation class and defining a relationship between participants.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for providing in-place extensions to an application, including receiving one or more artifacts associated with the application; graphically depicting a representation of at least one artifact of the one or more artifacts on a display, the at least one artifact comprising extension points defined by a developer of the application; receiving first user input indicating a first extension to the at least one artifact, the first extension being associated with an extension point of the one or more extension points and being applied to the representation, the at least one artifact remaining unchanged in view of the first extension being applied to the representation; determining a delta based on the first extension and the at least one artifact; and storing the delta in an extension repository, the delta being usable to extend one or more other artifacts.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including methods for generating visualizations. On a client side, a user request is received for an inter-entity call visualization. Code analysis data is accessed. A visualization model is built. The visualization is shown. User inputs are received for interacting with the visualization. The visualization is updated based on the received user inputs. On a server side, a request is received for code analysis data. The requested data collected, including running analyzers for any available data. The requested data is sent. The code analysis data can be used for other purposes than visualizations.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including methods for generating visualizations. On a client side, a user request is received for an inter-entity call visualization. Code analysis data is accessed. A visualization model is built. The visualization is shown. User inputs are received for interacting with the visualization. The visualization is updated based on the received user inputs. On a server side, a request is received for code analysis data. The requested data collected, including running analyzers for any available data. The requested data is sent. The code analysis data can be used for other purposes than visualizations.

Abstract: The disclosure generally describes computer-implemented methods, software, and systems, including methods for generating visualizations. On a client side, a user request is received for an inter-entity call visualization. Code analysis data is accessed. A visualization model is built. The visualization is shown. User inputs are received for interacting with the visualization. The visualization is updated based on the received user inputs. On a server side, a request is received for code analysis data. The requested data collected, including running analyzers for any available data. The requested data is sent. The code analysis data can be used for other purposes than visualizations.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for generating a repository comprising receiving a language meta-model; receiving annotations, each annotation including meta-data; annotating the language meta-model based on the annotations to provide an annotated language meta-model; and generating one or more repository modules based on the annotated language meta-model, the repository being defined based on the one or more repository modules.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for providing in-place extensions to an application, including receiving one or more artifacts associated with the application; graphically depicting a representation of at least one artifact of the one or more artifacts on a display, the at least one artifact comprising extension points defined by a developer of the application; receiving first user input indicating a first extension to the at least one artifact, the first extension being associated with an extension point of the one or more extension points and being applied to the representation, the at least one artifact remaining unchanged in view of the first extension being applied to the representation; determining a delta based on the first extension and the at least one artifact; and storing the delta in an extension repository, the delta being usable to extend one or more other artifacts.

Abstract: Implementations include methods, systems, and computer-readable storage media for receiving a lifecycle model, the lifecycle model including a representation of a lifecycle of an entity, the lifecycle including a plurality of states and transitions between states, receiving one or more artifacts, the entity including the one or more artifacts, each artifact of the one or more artifacts being associated with at least one state of the plurality of states, receiving a generic lifecycle management toolset, processing the lifecycle model and the one or more artifacts to configure the generic lifecycle management toolset and to define an adapted lifecycle management toolset that is specific to the entity, the adapted lifecycle management toolset including a lifecycle management interface, and providing the lifecycle management interface for display on a display device, the lifecycle management interface displaying representations of states of the plurality of states and a status of each state.

Abstract: Methods, computer-readable media, and computer systems for visualizing reporting data using system models. Reporting data from multiple data sources is extracted and mapped to a common language reporting. The mapped reporting data is correlated to elements of system models. Visualization options to present the mapped reporting data correlated to the system models are identified. The mapped reporting data is presented according to the visualization options in response to receiving a request for reporting data.

Abstract: Implementations include methods, systems, and computer-readable storage media for receiving a lifecycle model, the lifecycle model including a representation of a lifecycle of an entity, the lifecycle including a plurality of states and transitions between states, receiving one or more artifacts, the entity including the one or more artifacts, each artifact of the one or more artifacts being associated with at least one state of the plurality of states, receiving a generic lifecycle management toolset, processing the lifecycle model and the one or more artifacts to configure the generic lifecycle management toolset and to define an adapted lifecycle management toolset that is specific to the entity, the adapted lifecycle management toolset including a lifecycle management interface, and providing the lifecycle management interface for display on a display device, the lifecycle management interface displaying representations of states of the plurality of states and a status of each state.

Abstract: Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for generating a repository comprising receiving a language meta-model; receiving annotations, each annotation including meta-data; annotating the language meta-model based on the annotations to provide an annotated language meta-model; and generating one or more repository modules based on the annotated language meta-model, the repository being defined based on the one or more repository modules.

Abstract: Implementations of the present disclosure include methods for lifecycle management of services provisioned in a business network that include actions of defining a service package associated with a service, the service package being a logical representation of the service and including a plurality of artifacts, storing the service package in computer-readable memory, defining a service lifecycle model associated with the service, the service lifecycle model including a plurality of states, storing the service lifecycle model in the computer-readable memory, determining that the service is in a first state, determining that a first set of provisioning activities has occurred, in response to determining that the first set of provisioning activities has occurred, transitioning the service lifecycle model from the first state to a second state, and updating the service lifecycle model in the computer readable memory.