Abstract: A method of evaluating a cost associated with a test scenario, which test scenario comprises one or more branches making up a use case, the method comprising the steps of: determining a first parameter based on the complexity of the use case; determining a second parameter which indicates the criticality of the use case; determining a third parameter which indicates an execution cost of each action and decision point of the use case; determining a fourth parameter which indicates the priority of each branch of the use case; determining a fifth parameter which indicates the classification of each test parameter for each branch of the use case; determining a cost associated with the test scenario, based on a predetermined calculation using two or more of the first, second, third, fourth and fifth parameters.

Abstract: A method is presented for installing a software application on a data processing system that may include multiple data processing entities. The software application may include multiple components for installation on one or more of the entities. The method may include providing input information for each of the components designated for installation. Each component may then be installed according to its corresponding input information, and output information corresponding to each component may be generated. This output information may be provided to one or more data processing entities identified for installation of a subsequent component. The input information corresponding to the subsequent component may be at least partially determined from this output information.

Abstract: Method, computer program products and systems for testing a software application by providing one or more test units. Each test unit is adapted to verity a feature of the software application. A weight is assigned to each test unit. A theoretical sequence of execution of the test units is determined for the assigned weights and the test units are executed for the theoretical sequence.

Abstract: A method (300) and system for controlling use of software programs on multiple workstations of a network. An agent running on each workstation detects (306) any new process (using a kernel hooking technique), which is started in response to the request of execution of a program (397). The process is suspended (308) and an authorisation to run the program is requested (334) to an associated metering server. The metering server compares (380) the current usage of the product with the respective authorised conditions of use, and answers (382) the agent granting or denying the authorisation to run. The process is accordingly resumed (312), in order to enable the program to start, or aborted (315), so as to prevent execution of the program. In any case, the program is not stopped (but it is prevented from starting); this avoids killing the program while it is performing potentially risky operations.

Abstract: A technique for monitoring computers connected to a hardware switch. The switch is used to selectively connect a single set of peripheral units to the central unit of a selected one of the computers. In the proposed solution, status information of each non-selected computer is transmitted from the corresponding central unit to the switch. For this purpose, it is preferably exploited a corresponding bi-directional input port—such as of the USE type. The switch routes the status information of the different non-selected computers to the central unit of the selected computer. The central unit of the selected computer aggregates the status information with its output information, and then transmits this aggregated information to the switch for its display on a monitor. For example, the output information is shown in a main area of the screen, while the status information is shown in a reserved strip on top of it.

Abstract: A method (300) and system for controlling use of software programs on multiple workstations of a network. An agent running on each workstation detects (306) any new process (using a kernel hooking technique), which is started in response to the request of execution of a program (397). The process is suspended (308) and an authorisation to run the program is requested (334) to an associated metering server. The metering server compares (380) the current usage of the product with the respective authorised conditions of use, and answers (382) the agent granting or denying the authorisation to run. The process is accordingly resumed (312), in order to enable the program to start, or aborted (315), so as to prevent execution of the program. In any case, the program is not stopped (but it is prevented from starting); this avoids killing the program while it is performing potentially risky operations.

Abstract: A solution for metering usage of at least one software product on a data processing system, the at least one software product having a plurality of available associated licenses, each license having a set of attributes. An event indicative of the use of the at least one product on the system is detected. Responsive to the detection, the best available license among said plurality of licenses is determined according to predetermined preference rules of the attributes. Metering conditions to the at least one software product are applied according to the identified best available license. A change of the best available license is detected. New metering conditions are applied to the at least one software product accordingly.

Abstract: A display case for watches is described comprising an armoured outer case and at least one transparent portion for enabling the vision of the watches from outside. The display case further comprises supports for the watches and movement means of the supports so as to provide a preset movement to the watches in order to maintain a charge state so as to prevent stoppage.

Abstract: A solution (200) for facilitating the test of a command line interface (CLI) of a software product is proposed. For this purpose, the process is divided into two phases. The first phase relates to the generation of a scenarios matrix (235). This result is achieved by defining each command of the CLI (205-215), and more specifically its arguments and the corresponding properties (such as their acceptable ranges, patterns and/or option choices); the test activity is defined by specifying a desired accuracy level (230) of the test process. It is then possible to generate (220) the scenarios matrix automatically, by selecting (according to the desired accuracy level) predefined rules specifying happy paths and errors cases for each property. A second phase relates to the generation of corresponding test cases (255). For this purpose, an expected result (i.e., an output message with optional verification actions) is associated (240-250) with each test scenario in the respective matrix.

Abstract: A method and a corresponding apparatus for controlling and metering usage of software products on a computer are proposed. In a license manager software product, when several licenses are available for the same product a method for determining the best license is proposed in order to maximize the exploitation of the licenses. The solution of the invention is based on the idea that, if a choice is possible, it is preferable to use a license with a narrower scope, leaving a license with a wider applicability for future needs. According to the present invention the licenses are stored on a catalogue with an associated list of attributes indicative of usage constraints of the product. The licenses are ordered according to predetermined attributes optimization criteria, so that when a request is received, the license manager can easily find the best license, i.e. that license, suitable for the requested use, having the highest usage constraint, saving the more flexible licenses for future needs.

Abstract: A method (300) and system for controlling use of software programs on multiple workstations of a network. An agent running on each workstation detects (306) any new process (using a kernel hooking technique), which is started in response to the request of execution of a program (397). The process is suspended (308) and an authorisation to run the program is requested (334) to an associated metering server. The metering server compares (380) the current usage of the product with the respective authorised conditions of use, and answers (382) the agent granting or denying the authorisation to run. The process is accordingly resumed (312), in order to enable the program to start, or aborted (315), so as to prevent execution of the program. In any case, the program is not stopped (but it is prevented from starting); this avoids killing the program while it is performing potentially risky operations.