Method and apparatus for versioning and configuration management of object models

• US 7,322,025 B2
• Filed: 07/17/2003
• Issued: 01/22/2008
• Est. Priority Date: 07/17/2001
• Status: Active Grant

• Current Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Original Assignee: TATA Consultancy Services Limited (Tata Sons Pvt Ltd.)
• Inventors: Bahulkar, Arun Gajanan, Reddy, Sreedhar Sannareddy
• Primary Examiner(s): Zhen; Wei
• Assistant Examiner(s): Nahar; Qamrun
• Application Number:
  US10/622,324
• Publication Number:
  US 20040103393A1
• Time in Patent Office: 1,650 Days
• Field of Search: 717/120, 717/121, 717/122, 717/107, 717/108, 717/104, 717/105, 717/162, 717/167, 707/203
• US Class Current: 717/121
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A tool for versioning and configuration management of object models in a computing system including a component container for grouping objects to form a component containing the objects, the objects having properties and associations and a configuration container for grouping the assembled components to form a configuration. Each component is assigned a version number upon creation whereupon subsequent versions, if any, of the component are derived directly or indirectly from an earlier version, the objects accessibly isolated within the assigned component versions except for inter-component associations established between compatible ones of the objects in separate but compatible components of the configuration, the associations forming the basis for assembling, managing and function of the configuration.

Claims

1. A software tool installed on and operating from a computer appliance for versioning and Configuration Management of data models in a computing system comprising:

a modeling means in which associations are augmented with a notion of ownership;

a component means for grouping model elements including at least objects, associations and properties;

said component means having a mechanism for versioning;

the component further having means to create a tree of component versions;

with further means to support change isolation; and

a configuration as a unit for assembling component versions providing a binding context for associations between objects contained in the assembled component versions;

the configuration having means to interpret semantics of association of the ownership to determine completeness and compatibility of the assembled component versions;

wherein interpreting the semantics at least determine if any of the associations of the ownership of any of the component versions of said configuration are unbound in the configuration.

2. The software tool of claim 1, wherein the version mechanism of the component is flexible to permit a user to include a plurality of objects as determined by the user.

3. The software tool of claim 1, wherein configuration includes means to track configuration evolution history.

4. The software tool of claim 1, in which a facility is provided to track component version evolution history.

5. The software tool of claim 1, having means to support a plurality of models and meta models.

6. A method for versioning and Configuration Management of models in a computing system comprising the steps of:

(a) providing modeling means for augmenting associations with a notion of ownership;

(b) providing a component means for grouping model elements including at least objects, associations and properties;

said component means having a mechanism for versioning;

(c) creating a tree of component versions further having means to support change isolation;

(d) providing a configuration as a unit for assembling component versions and providing a binding context for associations between objects contained in the assembled component versions; and

(e) interpreting semantics of association ownership to determine completeness and compatibility of the assembled component versions, the interpretation of the semantics at least determining if any of the associations of the ownership of any of the component versions of said configuration are unbound in the configuration.

7. The method of claim 6, wherein the version mechanism of the component is flexible to permit a user to include a plurality of objects as determined by the user.

8. The method of claim 6, wherein the configuration includes means to track configuration evolution history.

9. The method of claim 6, in which a step is provided to track component version evolution history.

10. The method of claim 6, having means in step (a) to support a plurality of models and meta models.