METHOD AND SYSTEM FOR VERSION INDEPENDENT SOFTWARE RELEASE MANAGEMENT
First Claim
1. A method for assembling an update for a software release, comprising steps of:
- (a) defining classes of software components, each class comprising one or more instances of the class, each instance having a unique identifier (UID), each instance of the class representing a software component, which has one or more versions;
(b) for each version of a software component, assigning one or more time stamps, and an indicator identifying a status of the version of the software component;
(c) introducing a flexible coupling between versions of components and instances of classes by providing a pointer between a version of a component and a UID of an instance of a class;
(d) selecting versions of software components from which pointers originate;
(e) for each instance of the class, to which the pointer points at, selecting one version of the software component based on the assigned indicators;
(f) assembling the selected versions of software components into the update of the software release.
6 Assignments
0 Petitions
Accused Products
Abstract
A method for assembling an update for a software release is described, comprising defining classes of software components, each class comprising one or more instances of the class, each instance having a unique identifier, each instance representing a software component, which has one or more version; for each version of a software component, assigning time stamps and indicators identifying status of the version; introducing a flexible coupling between versions of components and instances of classes by providing a pointer between a version of a component and a unique identifier of an instance of a class; selecting versions of software components from which pointers originate; for each instance of the class, to which the pointer points at, selecting one version of the software component based on the assigned indicators; and assembling the selected versions of software components into the update of the software release. A corresponding system is also provided.
-
Citations
26 Claims
-
1. A method for assembling an update for a software release, comprising steps of:
-
(a) defining classes of software components, each class comprising one or more instances of the class, each instance having a unique identifier (UID), each instance of the class representing a software component, which has one or more versions; (b) for each version of a software component, assigning one or more time stamps, and an indicator identifying a status of the version of the software component; (c) introducing a flexible coupling between versions of components and instances of classes by providing a pointer between a version of a component and a UID of an instance of a class; (d) selecting versions of software components from which pointers originate; (e) for each instance of the class, to which the pointer points at, selecting one version of the software component based on the assigned indicators; (f) assembling the selected versions of software components into the update of the software release. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 26)
-
-
21. A system for assembling an update for software release, comprising:
-
(a) a repository of classes of software components, each class comprising one or more instances of the class, each instance having a unique identifier (UID), each instance of the class representing a software component, which has one or more versions; (b) a software release management module, comprising; (b1) a rule repository, comprising rules for flexible coupling between versions of software components and instances of classes by providing a pointer between a version of a software component and a UID of an instance of a class; (b2) means for assigning, for each software component, one or more time stamps and indicators identifying status of the software component in accordance with the rules; (b3) means for selecting versions of software components from which the pointers originate; and
for selecting, for each instance of the class, to which the pointer points at, one version of the software component based on the assigned indicators; and(c) means for assembling the selected versions of the software components into the update of the software release. - View Dependent Claims (22, 23, 24, 25)
-
Specification