Method and system for version independent software release management

• US 8,117,596 B2
• Filed: 07/10/2008
• Issued: 02/14/2012
• Est. Priority Date: 07/11/2007
• Status: Active Grant

• Current Assignee: Trend Micro Kabushiki Kaisha
• Original Assignee: Trend Micro Inc.
• Inventors: Foster, Justin Alexander, Thorley, Jeb Stuart
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Wu, Daxin
• Application Number:
  US12/170,931
• Publication Number:
  US 20110099543A1
• Time in Patent Office: 1,314 Days
• Field of Search: 717/120, 717/122, 717/123, 717/168, 717/170
• US Class Current: 717/122
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

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.

Claims

1. A method for assembling an update for a software release, comprising employing a processor for performing:

defining classes of software components, each class comprising a plurality of instances, each instance having a unique identifier (UID), said each instance of said each of class representing a software component, which has a plurality of versions;

for each version of the software component, assigning one or more time stamps, and an indicator identifying a release status of the each version of the software component;

introducing a flexible coupling between versions of the software components and instances of classes including introducing a pointer between a version of the software component and a UID of an instance of a class associated with the version;

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 indicator, and;

assembling the selected versions of software components into the update of the software release.

2. The method as described in claim 1, wherein the step of assigning the indicator comprises assigning one or more of the following indicators:

a deleted indicator when a version of the software component is no longer needed;

an issued indicator when a version of the software component is included in a current software release;

or

an un-issued indicator when a new version of the software component has been submitted to a repository of software components, or when the version of the software component does not have the issued or deleted indicator.

3. The method as described in claim 2, wherein the step assigning further comprises:

assigning a checked-in date set and an issued date set to each version of the software components.

4. The method as described in claim 3, wherein the step of assigning the checked-in —

date set further comprises assigning the checked-in date set, including a checked-in date time stamp when the version of the software component has become the latest version of the software component, and a checked-in retired date time stamp when a new version of the software component is submitted to the repository of software components.

5. The method as described in claim 3, wherein the step of assigning the issued date set comprises assigning the issued date set including an issued date time stamp when the version of the software component is assigned the issued indicator, and an issued retired date time stamp when the version of the software component is assigned the un-issued or deleted indicator.

6. The method as described in claim 2, wherein the steps of selecting further comprise selecting versions of software components, which have the issued indicator to form an issued view of the software components.

7. The method as described in claim 4, wherein the steps of selecting comprise selecting versions of software components having the most recent checked-in date time stamps and no checked-in retired date time stamps to form a latest view of the software components.

8. The method as described in claim 2, wherein the step of defining comprises defining one or more of the following classes:

(i) an Application Type class representing software applications to be protected;

(ii) a Filter class representing software filters to provide protection against computer intrusion attacks;

(iii) a Port List class representing computer ports.

9. The method as described in claim 4, further comprising preventing the version of the software component, from which the pointer originates, to be set as the issued version of the software component unless at least one version of a software component in the instance of the class, to which the pointer points at, has the issued indicator, preventing being performed before the assembling.

10. The method as described in claim 4, further comprising preventing the version of the software component, to which the pointer points, to have a deleted indicator applied as long as the version of the software component is pointed to by a pointer originating from a version of another software component, which has an issued indicator, the preventing being performed before the assembling.

11. The method as described in claim 1, further comprising preventing the version of the software component to have un-issued indicator once the version of the software component is included in the update of the software release.

12. The method as described in claim 8, wherein the introducing comprises providing a pointer between the version of the software component in the Filter class and the UID of the instance of the Application Type class.

13. The method as described in claim 2, wherein the assigning further comprises:

provided the version of the software component has a valid name, determining whether the version of the software component does not have a deleted indicator;

performing validation for the version of the software component based on the class;

if there is no a previous version of the software component, assigning a checked-in date time stamp to the version of the software component;

otherwise,

if there is a previous version of the software component, setting a checked-in retired time stamp to the previous version of the software component;

otherwise terminating the step of assigning the indicator.

14. The method as described in claim 13, wherein the performing validation comprises:

checking-in a version of a Filter component from which the pointer originates, the Filter component representing a software filter to provide protection against computer intrusion attacks, comprising;

ensuring that an Application Type component, to which the pointer points at, exists, the Application Type component representing a software application to be protected; and

provided there is a pointer to another Filter component, ensuring that said another Filter component exists.

15. The method as described in claim 2, wherein the assigning comprises:

assigning the issued indicator to the version of the software component, comprising;

performing validation of the version of the software component based on the class;

if the version of the software component has a deleted indicator, assigning an un-issued indicator to the version of the software component;

if the version of the software component does not have a deleted indicator;

determining that the version of the software component does not have any version with the issued indicator, followed by assigning the issued indicator to the version of the software component and setting an issued retired date time stamp to a previous version of the software component.

16. The method as described in claim 15, wherein the performing validation comprises:

(t) assigning the issued indicator to the version of the Filter component from which the pointer originates, comprising;

ensuring that an Application Type component, to which the pointer points at, exists and has an issued indicator, the Application Type component representing a software application to be protected; and

provided there is a pointer to another Filter component, ensuring that said another Filter component exists and has an issued indicator, the Filter component representing a software filter to provide protection against computer intrusion attacks;

otherwise terminating the assigning the issued indicator.

17. The method as described in claim 6, wherein the assigning comprises:

un-issuing the version of the software component, comprising assigning the un-issued indicator, comprising;

performing validation of the version of the software component based on the class;

determining whether the version of the software component was not previously included in the update of the software release and then deleted from the update;

if the version of the software component has a deleted indicator, assigning an un-issued indicator to the version of the software component;

if the version of the software component does not have a deleted indicator, assigning an issued indicator to the version of the software component, and assigning an issued retired date time stamp to the previous version of the software component;

otherwise, terminating the un-issuing.

18. The method as described in claim 17, wherein the un-issuing comprises:

(v) un-issuing a version of a Port List component specifying a computer port, including assigning the un-issued indicator, comprising;

searching for versions of Application Type software components in a latest view or an issued view, which point to the version of the Port List component;

the Application Type component representing a software application to be protected, and the latest view comprising versions of the software components having the most recent checked-in date time stamps when the versions of the software components have become the latest versions of the software components, and having no checked-in retired date time stamps when new versions of the software components are submitted to the repository of the software components; and

terminating the un-issuing the version of the Port List component if the Applicant Type software components, which point to the Port List software component, have issued indicators.

19. The method as described in claim 7, wherein the assigning comprises:

assigning the deleted indicator to the version of the software component, comprising;

performing validation of the version of the software component based on the class;

provided the version of the software component has not been withdrawn from the repository of software components for further development;

if the version of the software component has an issued indicator, assigning an un-issued indicator and an issued retired time stamp to the previous version of the software component;

if the version of the software component does not have an issued indicator, assigning the deleted indicator to the version of the software component and setting its checked-in retired date stamp to the current date.

20. The method as described in claim 19, wherein the performing validation comprises:

assigning the deleted indicator to the version of the Port List component specifying a computer port, comprising ensuring that no version of the Application Type component in the latest view or an Issued view points at the instance of the Port List class.

26. A non-transitory computer readable storage medium, comprising computer readable instructions stored thereon, for execution by a processor, to perform the steps of the method as described in claim 1.

21. A system for assembling an update for software release, comprising:

a processor, and a memory having computer readable instructions stored thereon for execution by the processor, causing the processor to form;

a repository of classes of software components, each class comprising a plurality of instances, each instance having a unique identifier (UID), said each instance of said class representing a software component, which has plurality of versions;

a software release management module, comprising;

a rule repository, comprising rules for flexible coupling between versions of the software components and instances of classes, configured to provide a pointer between a version of the software component and a UID of an instance of a class associated with the version;

means for assigning, for each version of said each software component, one or more time stamps and indicators identifying release status of said each software component in accordance with the rules;

means for selecting versions of the 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

means for assembling the selected versions of the software components into the update of the software release.

22. The system as described in claim 21, wherein the indicators comprise one or more of the following:

a deleted indicator when a version of the software component is no longer needed;

an issued indicator when a version of the software component is included in a current software release; and

an un-issued indicator when a new version of the software component has been submitted to the repository of the software components, or when the version of the software component does not have the issued or deleted indicator.

23. The system as described in claim 22, wherein the means for assigning comprises means for assigning date sets, comprising a checked-in date set and an issued date set, to each version of the software components;

wherein the checked-in date set includes a checked-in date time stamp when the version of the software component has become the latest version of the software component, and a checked-in retired date time stamp when a new version of the software component is submitted to the repository of the software components; and

wherein the issued date set includes an issued date time stamp when the version of the software component is assigned the issued indicator, and an issued retired sate time stamp when the version of the software component is assigned the un-issued or deleted indicator.

24. The system as described in claim 22, wherein the means for selecting comprises means for generating views of versions of the software components, including generating an issued view by selecting the versions of the software components, which have the issued indicator, and a latest view by selecting the versions of the software components, which have the most recent checked-in date time stamp.

25. The system as described in claim 21, wherein the repository of classes comprises one or more of the following classes:

(i) an Application Type class representing software applications to be protected;

(ii) a Filter class representing software filters to provide protection against computer intrusion attacks;

(iii) a Port List class representing computer ports.