Abstract: An upgrade campaign is generated for entities of a system described by a source configuration. According to the upgrade campaign, the system is upgraded to a target configuration using available software. A change model describes changes from the source configuration to the target configuration. According to the change model, an upgrade campaign specification model is generated, which contains at least one upgrade campaign element for each change in the change model. A subset of upgrade campaign elements are matched based on a first set of rules, and the matched upgrade campaign elements are merged into an upgrade procedure in the upgrade campaign specification model. The upgrade procedures are ordered based on a second set of rules and dependencies among the entities of the system, where the dependencies are extracted from the source configuration, the target configuration and the description of available software.

Abstract: An upgrade campaign is generated for entities of a system described by a source configuration. According to the upgrade campaign, the system is upgraded to a target configuration using available software. A change model describes changes from the source configuration to the target configuration. According to the change model, an upgrade campaign specification model is generated, which contains at least one upgrade campaign element for each change in the change model. A subset of upgrade campaign elements are matched based on a first set of rules, and the matched upgrade campaign elements are merged into an upgrade procedure in the upgrade campaign specification model. The upgrade procedures are ordered based on a second set of rules and dependencies among the entities of the system, where the dependencies are extracted from the source configuration, the target configuration and the description of available software.

Abstract: Configuration requirements that specify the provision of services using a system-level description are automatically generated from user requirements. The user requirements are decomposed into one or more levels of decomposed functionalities using an ontology as input. The ontology stores known decompositions of functionalities and relations between the known decompositions. The lowest level of the decomposed functionalities is mapped into a set of components provided by vendors, and additional components on which the set of components depend are identified. Based on the set of components and the additional components, a required number of instances of service workload is calculated to generate the configuration requirements of the system that satisfy the user requirements.

Abstract: Configuration requirements that specify the provision of services using a system-level description are automatically generated from user requirements. The user requirements are decomposed into one or more levels of decomposed functionalities using an ontology as input. The ontology stores known decompositions of functionalities and relations between the known decompositions. The lowest level of the decomposed functionalities is mapped into a set of components provided by vendors, and additional components on which the set of components depend are identified. Based on the set of components and the additional components, a required number of instances of service workload is calculated to generate the configuration requirements of the system that satisfy the user requirements.