Abstract: The present disclosure relates to medical delivery devices that include a barrel having an inner surface, and in at least one embodiment, the inner surface is hydrophilic. The medical delivery device may further include a stopper may having an elastomeric body, one or more fluoropolymer layers, and two or more ribs laminated to the one or more fluoropolymer layers. In some embodiments, the contact angle of the inner surface of the barrel is less than about 58°. Additionally, the stopper includes a sliding surface that is less than about 2.0 mm. The barrel provides inner surface that in combination with the fluoropolymer laminate or fluoropolymer film achieve high levels of air and liquid impermeability while also maintaining an acceptably low break loose force, low average glide force, and low glide force variation. In some embodiments, the compressibility stopper against the barrel is greater than about 7.9%.

Abstract: Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and a second deployment engine corresponding to the second deployment engine grouping to

Abstract: Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and a second deployment engine corresponding to the second deployment engine grouping to

Abstract: Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and a second deployment engine corresponding to the second deployment engine grouping to

Abstract: Provided are techniques for modeling operational units, each operational unit corresponding to an operational workflow and to one or more deployment engines of a plurality of deployment engines; selecting, for each of the plurality of operational units, one of the corresponding deployment engines; ordering the operational units with respect to the operational workflow; grouping the ordered operation units according to the selected deployment engines into deployment engine groupings; mapping output parameters corresponding to a first operational unit that concludes a first deployment engine grouping to input parameters corresponding to a second operational unit that initiates a second deployment engine grouping, inserting between the first operational unit and the second operational unit a transitional operational unit for transitioning between a first deployment engine corresponding to the first deployment engine grouping and as second deployment engine corresponding to the second deployment engine grouping t

Abstract: A method, computer program product, and computer system for receiving, at a computing device, logs and traces from one or more sources. The logs and traces are analyzed for problem imprints associated with an error. A set of one or more candidate lists is generated from the logs and traces. A change set from the set of one or more candidate lists that caused the error is identified.

Abstract: Various embodiments create a cross-configuration software module for cross-configuring software entities. In one embodiment, a first set of requirements and at least a second set of requirements are obtained. Each of the first and second set of requirements identify at least one of a set of software entities and a set of hardware components required to be present on at least one system including software entities to be cross-configured. At least one set of operations is obtained. The set of operations includes at least one executable instruction that configures a first software entity with a second software entity. A first configuration definition is generated including at least the first set of requirements and the at least one set of operations. A second configuration definition is generated including at least the second set of requirements. The first and second configuration definitions are stored within a cross-configuration software module.

Abstract: A method, computer program product, and computer system for receiving, at a computing device, logs and traces from one or more sources. The logs and traces are analyzed for problem imprints associated with an error. A set of one or more candidate lists is generated from the logs and traces. A change set from the set of one or more candidate lists that caused the error is identified.

Abstract: A composable software bundle is created by retrieving a semantic representation of a set of software modules. A functional representation of a set of operations is retrieved. Each operation in the set of operations is to be performed on the set of software modules during at least one virtual image life-cycle phase in a set of virtual image life-cycle phases. A set of artifacts including a set of executable instructions associated with the set of operations is identified. The semantic representation, the functional representation, and the set of artifacts, are stored in a composable software bundle.

Abstract: Various embodiments create a cross-configuration software module for cross-configuring software entities. In one embodiment, a first set of requirements and at least a second set of requirements are obtained. Each of the first and second set of requirements identify at least one of a set of software entities and a set of hardware components required to be present on at least one system including software entities to be cross-configured. At least one set of operations is obtained. The set of operations includes at least one executable instruction that configures a first software entity with a second software entity. A first configuration definition is generated including at least the first set of requirements and the at least one set of operations. A second configuration definition is generated including at least the second set of requirements. The first and second configuration definitions are stored within a cross-configuration software module.

Abstract: Three methods for converting sketch shapes into semantic elements by way of a semantic editor are disclosed. First, a method for conversion of a sketch shape that is part of a nested shape combination, which includes a sketch shape either hosting or nested within a semantic element. Second, a method for conversion of sketch shapes to semantic elements by storing sketch shape names and sketch shape descriptions in correlation with specific semantic elements and properties. The stored correlation is referenced for subsequent sketch shapes names or descriptions that are the same or a subset of the stored sketch shape name or description. Third, a method of conversion of one or more sketch shapes into a semantic template containing a plurality of semantic elements. Each of the one or more sketch shapes is mapped to a specific semantic element within the semantic template.

Abstract: A model simplification tool can receive a command to simplify the presentation of a visually complex semantic model from a graphical modeling application. The visually complex semantic model can be comprised of a multitude of object representations and their associations, such that the usability of the model is impaired. An association status can be determined for each object representation, which can designate the object representation as autonomous, containment, or subordinate. The presentation of the visually complex semantic model can be consolidated based on the association status of object representations. Subordinate objects can be nested within containment objects to produce a simplified semantic model. The simplified semantic model can be rendered within the graphical modeling application.

Abstract: Various embodiments create a cross-configuration software module for cross-configuring software entities. In one embodiment, a first set of requirements and at least a second set of requirements are obtained. Each of the first and second set of requirements identify at least one of a set of software entities and a set of hardware components required to be present on at least one system including software entities to be cross-configured. At least one set of operations is obtained. The set of operations includes at least one executable instruction that configures a first software entity with a second software entity. A first configuration definition is generated including at least the first set of requirements and the at least one set of operations. A second configuration definition is generated including at least the second set of requirements. The first and second configuration definitions are stored within a cross-configuration software module.

Abstract: A method, computer program product, and computer system for receiving, at a computing device, logs and traces from one or more sources. The logs and traces are analyzed for problem imprints associated with an error. A set of one or more candidate lists is generated from the logs and traces. A change set from the set of one or more candidate lists that caused the error is identified.

Abstract: A method, computer program product, and computer system for receiving, at a computing device, logs and traces from one or more sources. The logs and traces are analyzed for problem imprints associated with an error. A set of one or more candidate lists is generated from the logs and traces. A change set from the set of one or more candidate lists that caused the error is identified.

Abstract: A virtual image is created by receiving a selection of at least one composable software bundle. The at least one composable software bundle includes a first set of metadata and a first set of artifacts comprising a first set of executable instructions associated with a first set of operations. A virtual image asset is selected and received. The virtual image asset includes one or more virtual image disks, a second set of metadata, and a second set of artifacts including a second set of executable instructions associated with a second set of operations. A new virtual image asset is created based on the at least one composable software bundle and the virtual image asset. The new virtual image asset includes a third set of metadata that is based on the first set of metadata and the second set of metadata.

Abstract: A system for managing advisories for complex model nodes that can include a complex model, a graphical modeling application, and an advisory manager. The complex model can be configured to graphically represent a user-defined system as multiple nodes and relationships. The graphical modeling application can be configured to execute operations upon the complex model. The graphical modeling application can store data defining the graphical characteristics of the complex model as a notation model and data defining the semantic characteristics of the complex model as a semantic model. The notation model and the semantic model can be stored as separate data entities. The advisory manager can be configured to aggregate notifications and potential resolutions for the nodes of the complex model. The notifications and potential resolutions can be visually presented within the graphical modeling application.

Abstract: Embodiments of the present invention provide a flexible approach to construct/create instances of cloud computing environments. Specifically, under embodiments of the present invention, an image of a virtual machine instance is created from the following components: image bits; content such as the liner notes, manual, metadata, etc.; end user information (so that the image can be customized for one or more specific end users); values provided to an installer; and cloud based values (e.g., IP address, hostname, etc.). By constructing the virtual machine using this approach, dynamic aspects of the image are managed external to the static binary representation of the image. This would include artifacts such as documentation, install scripts, binary files, etc. Additionally, user supplied data can be captured dynamically and copied to customize the image at the time of instance creation. Still yet, embodiments of the present invention provides system level configuration to construct the virtual machine.

Abstract: Various embodiments create a cross-configuration software module for cross-configuring software entities. In one embodiment, a first set of requirements and at least a second set of requirements are obtained. Each of the first and second set of requirements identify at least one of a set of software entities and a set of hardware components required to be present on at least one system including software entities to be cross-configured. At least one set of operations is obtained. The set of operations includes at least one executable instruction that configures a first software entity with a second software entity. A first configuration definition is generated including at least the first set of requirements and the at least one set of operations. A second configuration definition is generated including at least the second set of requirements. The first and second configuration definitions are stored within a cross-configuration software module.

Abstract: Lifecycles of virtual image assets are managed as follows. A set of assets including a set virtual image assets and a set of software bundle assets are analyzed. At least a portion of relationship data between one or more of the virtual image assets and one or more of the software bundle assets is determined. The at least a portion of relationship data is stored in a memory. At least one of one or more virtual image assets and one or more software bundle assets are determined to be associated with a set of changes. At least one virtual image asset that is related to the one or more virtual image assets and/or one or more software bundle assets associated with the set of changes is identified. The at least one virtual image asset that has been identified is updated based on the set of changes.