| Patent application number | Description | Published |
|---|
| 20080235664 | METHOD, SYSTEM AND COMPUTER PROGRAM FOR DISCOVERING MULTI-COMPONENT SOFTWARE PRODUCTS - A solution ( | 09-25-2008 |
| 20080313599 | METHOD, SYSTEM AND COMPUTER PROGRAM FOR DEVELOPING SOFTWARE APPLICATIONS WITH INCREASED MODULARITY - A solution is proposed for developing software applications on a data processing system. A corresponding method (A | 12-18-2008 |
| 20090077419 | Monitoring System with Trusted Corrective Actions - A system and computer program product for monitoring a data processing system is proposed. The system and computer program product involve the measuring of state parameters of the system. Indicators of the performance of the system are then inferred from the state parameters by applying fuzzy-logic rules. The proposed solution is based on the idea of estimating a trust value, based on the effectiveness of the corrective actions. If the previous corrective actions prove to be effective than the trust value is enhanced and the system is allowed a higher level of autonomy. Otherwise the intervention of an operator might be invoked. | 03-19-2009 |
| 20090094183 | Predictive Monitoring Method and System | 04-09-2009 |
| 20090157806 | Method and System for Delivering Information with Caching Based on Interest and Significance | 06-18-2009 |
| 20090198543 | License Compliance Management - Methods, computer program products and systems for determining the level of use of a program associated with a license, by one or more agents, for comparison with a predetermined licensed level of use. In one embodiment of the invention, the method comprises the steps of collecting initial data from the one or more agents associated with a metric indicative of use of the program during a first predetermined time period, calculating the metric to determine a level use of the program for the first predetermined time period, receiving new data from one or more agents associated with the metric of usage of the program, where the new data arrives after the first predetermined time period, estimating a new value of the metric to determine a approximate level of use for a second predetermined time period from the original data, the metric and the new data and in response to a trigger event, recalculating the metric to produce a final value of the metric based on the original data and the new data to provide an indication of the level of use of the program. | 08-06-2009 |
| 20090241105 | Detecting Applications in a Virtualization Environment - A method, computer program product and system for allowing licence tools to detect the installation of applications that are not physically installed on a machine when an Application Virtualization Environments is used. In one embodiment of the invention, the licence tools may further detect application usage. In one embodiment of the invention, a virtual installation signature may be defined. Agents in a target computer may be used to compare the virtual installation signature of an application with a localized list of potential applications to detect whether the software is installed on the target computer. | 09-24-2009 |
| 20090320020 | Method and System for Optimising A Virtualisation Environment - A mechanism for advising users on how to optimize their virtualisation infrastructure to minimise their software costs. There are two aspects to solution. The first aspect considers the distribution of software in the virtualised environment. The second aspect determines the proper licence types (e.g., sub-capacity or full capacity) for the virtualised environment, based on the usage of the software products therein. | 12-24-2009 |
| 20110113402 | REPRESENTING NON-FUNCTIONAL REQUIREMENTS (NFRS) IN UNIFIED MODELING LANGUAGE (UML) - Modeling non-functional requirements (NFRs) in a computer programming environment. In one aspect, this further comprises: identifying use case (UC) artifacts having one or more NFRs; retrieving the one or more NFRs and any data associated therewith; analysing the associated data to define a test case therefor; retrieving a UC realisation from a model to determine one or more possible program flows; and testing each possible program flow to select the test case which verifies the use case required, thereby modeling the NFR. | 05-12-2011 |
