62 results about "Software assets" patented technology

The disclosed invention is a software license management system (SLMS) utilizing a web-based interactive database to automate a software management process (SWMP) for managing software assets, measuring compliance requirements, and tracking/reporting status as necessary to assure proficiency and adherence to implementation requirements of the software management process. The SWMP is a process consisting of five different phases. The five steps of the SWMP involve identification of various solution alternatives, acquisition, deployment, maintenance and software retirement. The SWMP establishes high-level software management process to avoid litigation and penalties, maximize software asset utilization through tighter inventory control, and capitalize on the software procurement process.

Provided is a process that includes: determining whether to execute a software asset based on trust records documenting provenance of the software asset published to a blockchain, wherein determining whether to trust the software asset comprises: accessing the trust record, verifying the trust record has not been tampered with subsequent to publishing, verify that a hash digest based on the software asset matches a hash digest associated with the trust record and published to the blockchain; verifying that trust assertions of the trust record are cryptographically signed by trusted entities specified by entity criteria, and verifying that the trust assertions satisfy execution criteria.

Provided is a smart contract that specifies a routine to be executed by a plurality of the computing nodes of a blockchain-based, decentralized computing platform, wherein the promotion smart contract is configured to determine whether a pre-release software asset satisfies software quality criteria required to advance the pre-release software asset to a next stage, and the promotion smart contract is configured to cause an assertion indicating whether software quality criteria are satisfied to be published to a blockchain storing trust records in response to determining whether the software quality criteria are satisfied.

Provided is a process that includes: traversing, with one or more processors, a constituency graph of a software asset and accessing corresponding trust records of a plurality of the software assets of the constituency graph visited by traversing the constituency graph, the trust records being published to a tamper-evident, immutable, decentralized data store; and for each respective constituent software asset among the plurality of constituent software assets visited by traversing, assessing, with one or more processors, trustworthiness of the respective software asset based on the corresponding trust record of the respective software asset.

Provided is a process that includes: calling an alert program configured to execute on a decentralized computing platform and access records on a blockchain, wherein: the decentralized computing platform is configured to execute multiple instances of the program to produce multiple instances of candidate results, the decentralized computing platform is configured to determine an output of the alert program in response to the call with a first consensus algorithm, the alert program is configured to verify a cryptographic signature of the call and determine whether an alerting entity is authorized to issue the alert, and the alert program is configured to publish the information about the software asset to alert recipients or to the blockchain upon verifying the cryptographic signature and determining that the alerting entity is authorized to issue the alert.

A development system with improved methodology for creation and reuse of software assets is shown and described. In one embodiment, for example, in a development system, a method is described for facilitating creation of a reusable application, the method comprises steps of: during development of the application, capturing knowledge and intent of the application's original developer alongside source code created for the application; producing an archival module storing the source code for the application together with metadata capturing the knowledge and intent of the original developer, the metadata including at least one script guiding subsequent developers in use and modification of the source code for the application; and consuming the archival module by a follow-on developer, including executing the at least one script for facilitating creation of a reusable version of the application.

Provided is a process that includes: calling a program executed on a decentralized computing platform configured to persist state to a blockchain, the call requesting the program to release the software asset to the production environment, wherein: respective instances of the program are configured to publish release documentation by which provenance of the software asset is verifiable to the blockchain, respective instances of the program are configured to verify a cryptographic signature associated with the software asset, the cryptographic signature establishes that the software asset being released has not been tampered with subsequent to signing, the cryptographic signature establishes that the releasing entity or a proxy of the releasing entity has access to a cryptographic key by which the cryptographic signature was formed, and the decentralized computing platform is configured to reach a consensus verification determination among verification results from the replicated instances of the program.

A system and method for converting a target computing device to a virtual machine are provided. An assessment of the physical and software assets of a target computing device are obtained. A data image of the target computing device is deployed on an instance of a virtual machine. The virtual machine adjusted to correspond to the physical and software assets of the target computing device.

A method for providing software/license and physical/virtual machine management is disclosed for a specialized asset management system. The specialized asset management system aggregates physical and online software assets and their corresponding license(s), as well as physical and virtual machines into a unified library system wherein assets can be managed, used, reserved, tracked, reconciled, and reported on using a library check-out and check-in paradigm.

The present invention provides a virtual Reusable Asset Specification (RAS) repository. A method in accordance with an embodiment of the present invention includes: providing RAS assets for each different lifecycle phase of a software asset; and linking the RAS assets together using RAS related-assets.

The invention discloses a software risk assessment method based on defect analysis. The risk assessment method comprises the following steps of obtaining input data and an input relationship required by risk calculation through software asset identification, the defect analysis and consequence attribute evaluation, calculating consequence attribute factors of consequence attributes in functional modules, calculating risk degrees sumRtk of consequences of whole software, calculating weighted means of the risk degrees of the consequence attributes according to weights (pwti) of the functional modules of the software, obtaining the risk degrees sumRtk of the consequence attributes of the whole software, calculating a whole risk value of the software, calculating weighted means of the risk degrees of the consequence attributes of the whole software according to weights (rwtk) of the consequence attributes, obtaining a final risk value Risk of the software, evaluating a risk level, and obtaining the risk level of the software as an assessment result according to the risk value Risk of the software. The method solves the problems that risk element assignments in most risk assessment models relate to more expert opinions at present, and some assignments are unquantifiable. The method avoids repeated risk calculation to the greatest extent.

A method and system are provided for performing an extract-transform-load (ETL) process. The method includes collecting load information about a volume and a complexity of raw data to be processed during the ETL process. The method further includes receiving an expected completion time of the ETL process and execution information about (i) hardware resources and (ii) an influence of the hardware resource on an execution time of the ETL process. The method also includes calculating resources for a distributed processing software infrastructure to be used to perform the ETL process, by applying a statistical method to the load information, expected completion time, and execution information. The method additionally includes dynamically assigning cloud resources corresponding to and based on the calculated resources, in accordance with the expected completion time. The method further includes performing the ETL process on the raw data using the assigned cloud resources and storing ETL process results.

The invention discloses a software asset management system and a software and hardware information automatic grabbing method, and relates to the management device or system technology field. The asset management system comprises a fundament archive management sub-system, a software inventory management sub-system, a software utilization management sub-system, a software lease management sub-system, a computer device monitoring system, a statistical analysis sub-system, and a system management sub-system. The asset management system is used for effective management, control, and protection of software and hardware devices of users, is used to facilitate the control of the users over the purchasing costs and the utilization costs of the software, is used to improve the utilization rate and the integral benefit of the IT asset, and is used to guarantee the legality of the software utilization, and therefore the legal risks and the financial risks caused by the utilization of the software asset are prevented.

An asset catalog is disclosed which includes a plurality of software assets and at least one hardware asset configured to be selectively functionally interconnected with at least one of the plurality of software assets. The plurality of software assets and the at least one hardware asset are organized in accordance with reusable asset specifications.

A method of managing links can include inserting a universal resource identifier for a software asset within a link resolution file, wherein a symbolic link within a document that is independent of the link resolution file references the link resolution file. The method also can include publishing the document and the link resolution file and, responsive to a selection of the symbolic link within the document, resolving the symbolic link to the universal resource identifier using the link resolution file.