46 results about "Software artifacts" patented technology

The use of extension types as a mechanism for an essentially horizontal extension of types for modeling multiple extensions and variations of a software artifact. In that an extension type is a tuple of unrelated classes, each element class in the tuple corresponds to an extension of the extension type. Using extension types, one can bring two unrelated classes or types together to perform computations. Shown herein are manners via which extension types may elegantly model multiple and dynamic extensions of an artifact. Also shown is how extension types simplify aspect-oriented software development and several design patterns.

A pattern implementation technique in which a pattern is defined as a software artifact that comprises a pattern signature representing one or more parameters of the pattern and a pattern implementation model representing one or more methods for expanding the pattern in a selected software context by assigning one or more arguments to the one or more parameters. The pattern implementation model can be based on one or more framework code sets, each of which supports the creation of plural patterns by providing a pattern implementation model for a particular software context. The framework code sets can be rendered extensible by a pattern author by virtue of providing methods whose code is adapted to be modified by a pattern author when defining a pattern. The pattern can be applied by creating an instance of the pattern in a software context and presenting a graphical representation of the pattern instance that can be manipulated by the pattern user in order to apply arguments to the pattern parameters.

An artifact update notification system that includes a server computer and client computer is discussed and described. The server computer stores artifact preferences, determined according to objective and subjective criteria, of artifact characteristics. The client computer executes a software development environment that makes use of a software artifact. The server computer and client computer interact to perform an update cycle. The update cycle includes the server computer communicating to the client computer whether there is an actionable change to the software artifact with respect to the artifact preferences. If there has been an actionable change to the software artifact, the client computer performs an update action in the software development environment in response to the actionable change. A related artifact update notification method is also described, as is a computer-readable storage medium that includes instructions for operation of a computer to execute a related artifact update notification method.

A method (which can be computer implemented) for inferring whether at least a first relationship exists between at least first and second entities includes the steps of applying a first assessor to obtain a first confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, applying a second assessor to obtain a second confidence level pertaining to putative existence of said at least first relationship between said at least first and second entities, and combining said first and second confidence levels to obtain an overall inference whether said at least first relationship exists between said at least first and second entities.

A software diagram is created based on software artifacts for a software program, where the software diagram comprises shapes corresponding to software artifacts. The diagram shapes may be customized to illustrate certain properties of the software artifacts or relationships between the software artifacts. Later, one or more changes are made to one or more of the software artifacts such that the diagram no longer accurately reflects the program code. A diagramming tool attempts to automatically update the software diagram to reflect the changed program code, but may be unable to account for at least one diagram shape because its associated software artifact has changed such that the diagramming tool no longer recognizes it as the same software artifact. The unaccounted for shape is known as an orphaned shape. A user may instruct the diagramming tool to associate the orphan shape with one of the changed software artifacts. The diagramming tool automatically reapplies the customizations previously associated with the orphan shape using the properties of the changed software artifact where applicable.

Controlling usage of virtual disks in a data-processing center hosting a set of virtual machines is described where each virtual disk comprises a set of software artifacts. A corresponding method comprises detecting a request of adding a new virtual disk comprising a set of new software artifacts to a selected one of the virtual machines, determining composition information of the new virtual disk, which includes an indication of the new software artifacts, retrieving an indication of usage entitlements of the new software artifacts in the data-processing center, enabling or preventing the attachment of the new virtual disk to the selected virtual machine according to a comparison between the composition information and the usage entitlements, attaching the new virtual disk to the selected virtual machine in response to the enabling thereof, and updating the usage entitlements in response to the attachment of the new virtual disk.

Computing systems, for example, multi-tenant systems deploy software artifacts in data centers created in a cloud platform using a cloud platform infrastructure language that is cloud platform independent. The system receives an artifact version map that identifies versions of software artifacts for datacenter entities. The system generates a master pipeline for deploying services on a target cloud platform. The master pipeline includes a change management stage comprising instructions for interacting with a change management system. The execution of the change management stage of a pipeline provides a status of deployment of one or more services to the change management system. The details recorded can be used for auditing, for example, to determine why certain change in the configuration of services of the datacenter was made.

The invention discloses a software workpiece relationship mining method based on integrated development platform. The method comprises the following steps: firstly, extracting all explicit referencesfrom a GitHub page; filtering noise out, identifying a solution relationship among a defect report, a submission request and a submission record from an explicit reference, recovering a missing link of the solution relationship among workpieces, analyzing other relationships in residual references by using a text mining and machine learning technology, and finally constructing a connection graph based on the identified solution relationship and non-solution relationship. According to the method, the mining accuracy and efficiency can be improved.

Computing systems, for example, multi-tenant systems deploy software artifacts in data centers created in a cloud platform using a cloud platform infrastructure language that is cloud platform independent. The system receives pipeline templates including templating expressions that can be substituted with values for generating pipelines. A pipeline can be executed to perform a set of actions associated with continuous delivery of a software artifact. The system stores sets of partially hydrated pipeline templates. The partially hydrated pipeline templates can be compiled into executable pipelines associated with services configured on a datacenter of a cloud platform. The system stores different versions of pipeline templates as deployment packages. The system stores version pointers that identify specific deployment packages that are selected when a software release is deployed. The version pointers allow the deployment package to be updated in case of roll back or for deploying more recent changes.

Computing systems, for example, multi-tenant systems deploy software artifacts in data centers created in a cloud platform using a cloud platform infrastructure language that is cloud platform independent. The system uses a control datacenter with a set of service groups used for configuring other datacenters, for example, for performing continuous delivery of software artifacts for other datacenters. The system uses a primary control datacenter and a secondary control datacenter. The primary control datacenter configures infrastructure of the tenant datacenter, for example, by configuring computing resources in the cloud platform for the tenant datacenter according to a declarative specification of the tenant datacenter. The secondary control datacenter efficiently takes control of the process of configuring the tenant datacenter, for example, if there is a failure of the primary control datacenter.

This document discusses, among other things, a system and a method for using a meta-model to manage relationships between software artifacts, the method comprising determining a meta-model; identifying one or more available artifacts in one or more software applications; using the meta-model to define one or more relationships between the one or more available artifacts, wherein each relationship is a specific instance of a possible association defined in the meta-model; and providing the one or more relationships as one or more configurations to the one or more software applications.

Computing systems, for example, multi-tenant systems deploy software artifacts in data centers created in a cloud platform using a cloud platform infrastructure language that is cloud platform independent. The system generates pipelines for deploying software artifacts in data center entities configured in a cloud platform. The system allows partial execution of pipelines such that the pipeline can be executed again to complete execution of the remaining stages. The system maintains state of the pipeline execution and checks the state to determine whether a stage should be executed during subsequent executions. The system allows a failed stage to be retried multiple times based on a retry strategy. A retry strategy may depend on the data center entity in a hierarchy of data venter entities of a data center.