Abstract: A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components, integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Abstract: A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components, integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Abstract: A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Abstract: The different illustrative embodiments provide a method, computer program product, and apparatus for managing a number of surgical tools. A determination is made whether a number of surgical tools is to be used in performing a procedure based on information. Responsive to a determination that the number of surgical tools is to be used in performing the procedure, a determination is made whether a signal received by the number of surgical tools indicates that the number of surgical tools is present within a predetermined distance of a location on the patient where the procedure is to be performed. Responsive to a determination that the signal received by the number of surgical tools indicates that the number of surgical tools is within the predetermined distance of the location on the patient where the procedure is to be performed, the number of surgical tools is enabled for use in performing the procedure.

Abstract: A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Abstract: A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises a plurality of software components and data associated with said plurality of software components integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution, wherein the at least one migration strategy comprises at least one of a product level strategy specified for a particular software component of the plurality of software components and at least one solution level strategy specified for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component.