Managing Software Component Version Identifications in a Componentised Software System

• US 20080082974A1
• Filed: 09/20/2007
• Published: 04/03/2008
• Est. Priority Date: 09/28/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Ellison, Timothy Peter
• Application Number:
  US11/858,245
• Publication Number:
  US 20080082974A1
• Time in Patent Office: Days
• US Class Current: 717/170
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A method, apparatus and software for managing software component version identifications in a componentised software system in which one or more software components are arranged to export one or more application program interfaces (APIs). The system is arranged to derive meta data defining data structures for APIs exported by a software component and to identify any differences between the meta data and previously derived meta data for the same component so as to enable notification of any identified differences.

Claims

1. A method for managing software component version identifications in a componentised software system in which one or more software components are arranged to export one or more application program interfaces (APIs), said method comprising:

a) deriving a first set of meta data defining one or more data structures for one or more

APIs exported by a software component;

b) storing said first set of meta data in relation to said software component;

c) deriving a second set of meta data for said software component; and

d) identifying any differences between said second set of meta data and said first set of meta data so as to enable notification of any identified differences.

2. A method according to claim 1 further comprising:

e) applying a set of compatibility rules to said identified differences, said compatibility rules defining acceptable differences between said sets of meta data so as to enable notification of any contravened rules.

3. A method according to claim 2 in which at least one of said exported APIs has an associated version identification and said method comprises:

f) if any of said compatibility rules are contravened, applying a set of version identification rules, said version identification rules determining any necessary updates to said version identification of said software component API; and

g) updating said version identification in response to the results of said version identification rules.

4. A method according to claim 2 or claim 3 in which said meta data is derived from a syntax tree created by a compiler for said software component.

5. A method according to claim 3 in which said meta data comprises descriptions of the methods, fields and constructors for a given API.

6. A method according to claim 3 in which step d) is performed for a set of interdependent components being assembled.

7. A method according to claim 3 in which step d) is performed at runtime.

8. A method according to claim 3 in which said version identification comprises major and minor revision numbers.

9. A method according to claim 3 in which said component is written in Java™

and said compatibility rules embody Java™

binary compatibility rules.

10. Apparatus for managing software component version identifications in a componentised software system in which one or more software components are arranged to export one or more application program interfaces (APIs), said apparatus comprising:

means for deriving a set of meta data defining one or more data structures for one or more APIs exported by a software component;

means for storing the set of meta data in relation to said software component;

means for comparing the stored set of metadata with a second set of meta data generated by the deriving means for a different version of said software component; and

means for identifying any differences between said second set of meta data and said first set of meta data so as to enable notification of any identified differences.

11. Apparatus according to claim 10 further comprising:

means for applying a set of compatibility rules to said identified differences, said compatibility rules defining acceptable differences between said sets of meta data so as to enable notification of any contravened rules.

12. Apparatus according to claims 11 in which at least one of said exported APIs has an associated version identification and said apparatus further comprises means responsive to the contravention of any of said compatibility rules for applying a set of version identification rules, said version identification rules determining any necessary updates to said version identification of said software component API;

and

means for updating said version identification in response to the results of said version identification rules.

13. Apparatus according to claim 12 in which the means for deriving the meta data operates on a syntax tree created by a compiler for said software component.

14. Apparatus according to claims 12 in which said meta data comprises descriptions of the methods, fields and constructors for a given API.

15. A storage medium containing computer-readable program code for controlling a computer to manage software component version identifications in a componentised software system in which one or more software components are arranged to export one or more application program interfaces (APIs), said storage medium comprising:

code for deriving a set of meta data defining one or more data structures for one or more APIs exported by a software component;

code for storing the set of meta data in relation to said software component;

code for comparing the stored set of meta data with a second set of meta data generated by the deriving code for a different version of said software component; and

code for identifying any differences between said second set of meta data and said first set of meta data so as to enable notification of any identified differences.

16. The storage medium of claim 15 further comprising:

code for applying a set of compatibility rules to said identified differences, said compatibility rules defining acceptable differences between said sets of meta data so as to enable notification of any contravened rules.

17. Apparatus according to claim 16 in which at least one of said exported APIs has an associated version identification and said storage medium further comprises code responsive to the contravention of any of said compatibility rules for applying a set of version identification rules, said version identification rules determining any necessary updates to said version identification of said software component API;

and

code for updating said version identification in response to the results of said version identification rules.

18. The storage medium of claim 16 in which the code for deriving the meta data operates on a syntax tree created by a compiler for said software component.

19. The storage means of claim 16 in which said meta data comprises descriptions of the methods, fields and constructors for a given API.