Apparatus and method for generating a software dependency map
First Claim
1. A method for altering an existing configuration of a first software functionality on a client device to install a second software functionality comprising:
- receiving a request to install a second software functionality on a client device;
receiving a software manifest describing a plurality of software files residing on the client device, the plurality of software files residing on the client device comprising at least one existing software file associated with the first software functionality to be altered for installation of the second software functionality;
accessing a software installation map comprising a plurality of software elements representing at least the plurality of software files described in the software manifest, a plurality of software files for installing the second software functionality, a plurality of dependency pointers representing dependencies between the software elements representing at least the plurality of software files described in the software manifest and the plurality of software files for installing the second software functionality, a plurality of dependency confidence factors associated with the plurality of dependency pointers, the plurality of dependency confidence factors indicating at least a number of a plurality of successful prior installations involving the plurality of dependency pointers, and an installation route confidence factor comprising an average of the plurality of dependency confidence factors;
analyzing the software installation map to determine a first software installation route for installing the second software functionality, the first software installation route comprising;
the plurality of software files for installing the second software functionality, the plurality of software files including the at least one existing software file associated with the first software functionality to be altered for installation of the second software functionality; and
an installation order for installing the plurality of software files; and
providing the first software installation route to the client device to alter the first software functionality and install the second software functionality.
2 Assignments
0 Petitions
Accused Products
Abstract
A virtual installation map, and method involving installing a software functionality using the same, the virtual installation map including a first software installation map including a plurality of software elements representative of a related software file, the software elements also including at least one dependency to another software element. The virtual installation map further including a second software installation map also including a second plurality of software elements representative of related software file along with related dependencies. The first and second software installation maps may be hosted in separate databases and may relate to software products provided by different vendors. One or both software installation maps may include a pointer or other reference to the other installation map thereby providing a virtual installation map, in one example.
-
Citations
19 Claims
-
1. A method for altering an existing configuration of a first software functionality on a client device to install a second software functionality comprising:
-
receiving a request to install a second software functionality on a client device; receiving a software manifest describing a plurality of software files residing on the client device, the plurality of software files residing on the client device comprising at least one existing software file associated with the first software functionality to be altered for installation of the second software functionality; accessing a software installation map comprising a plurality of software elements representing at least the plurality of software files described in the software manifest, a plurality of software files for installing the second software functionality, a plurality of dependency pointers representing dependencies between the software elements representing at least the plurality of software files described in the software manifest and the plurality of software files for installing the second software functionality, a plurality of dependency confidence factors associated with the plurality of dependency pointers, the plurality of dependency confidence factors indicating at least a number of a plurality of successful prior installations involving the plurality of dependency pointers, and an installation route confidence factor comprising an average of the plurality of dependency confidence factors; analyzing the software installation map to determine a first software installation route for installing the second software functionality, the first software installation route comprising; the plurality of software files for installing the second software functionality, the plurality of software files including the at least one existing software file associated with the first software functionality to be altered for installation of the second software functionality; and an installation order for installing the plurality of software files; and providing the first software installation route to the client device to alter the first software functionality and install the second software functionality. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A method for receiving instructions for installing a second software functionality on a client device with an existing first software functionality comprising:
-
providing an installation request for a second software functionality, wherein a first software functionality currently resides on a client device; providing a software manifest describing a plurality of software files residing on the client device and associated with at least the first software functionality; accessing a software installation map comprising; a plurality of software files for installing the second software functionality, the plurality of software files including at least one software file associated with the first software functionality to be altered for installation of the second software functionality; a plurality of dependency pointers representing dependencies between the software elements representing at least the plurality of software files described in the software manifest and the plurality of software files for installing the second software functionality; a plurality of dependency confidence factors associated with the dependency pointers, the plurality of dependency confidence factors indicating at least a number of a plurality of successful prior installations involving the dependency pointers; an installation route confidence factor comprising an average of the plurality of dependency confidence factors; and an installation order for installing the plurality of software files; and receiving a software installation route from the installation map comprising the plurality of software files for installing the second software functionality and the installation order for installing the plurality of software files. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A non-transitory computer readable medium having computer-executable instructions stored thereon that, when executed by a computer, causes the computer to perform the operations of:
-
providing an installation request for a second software functionality wherein a first software functionality Currently resides on a client device; providing a software manifest describing a plurality of software files residing on the client device and associated with at least the first software functionality; and accessing a software installation map comprising; a plurality of software files for installing the second software functionality, the plurality of software files including at least one software file associated with the first software functionality to be altered for installation of the second software functionality; a plurality of dependency pointers representing dependencies between the software elements representing at least the plurality of software files described in the software manifest and the plurality of software files for installing the second software functionality; a plurality of dependency confidence factors associated with the dependency pointers, the plurality of dependency confidence factors indicating at least a number of a plurality of successful prior installations involving the dependency pointers; an installation route confidence factor comprising an average of the plurality of dependency confidence factors; and an installation order for installing the plurality of software files; and receiving a software installation route from the installation map comprising plurality of software files for installing the second software functionality and the installation order for installing the plurality of software files.
-
Specification