Method and system for change control management of shema definition objects

• US 20040123234A1
• Filed: 02/06/2003
• Published: 06/24/2004
• Est. Priority Date: 12/18/2002
• Status: Abandoned Application

• Current Assignee: SchemaLogic, Inc. (Progress Software Corporation)
• Original Assignee: SchemaLogic, Inc. (Progress Software Corporation)
• Inventors: Ovchinnikov, Andrei, Anderson, Breanna Daphne
• Application Number:
  US10/360,266
• Publication Number:
  US 20040123234A1
• Time in Patent Office: Days
• US Class Current: 715/513
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 9/454 Multi-language systems; Localisation; Internationalisation

Abstract

The present invention provides a method and system for change control management of schema definition objects across disparate systems. A determination is made when a proposed change associated with an object is made; an impact analysis is performed on the proposed change; the change is implemented when the impact analysis indicates that there is no impact on, other system stakeholders otherwise: a change object based on the proposed change is created, voting rights are allocated to users based on the impact analysis; and the proposed change is accepted or canceled in response to the voting. Change control contracts may be associated with the objects. The contracts may be customized to establish change management rules for and enterprise and to specialize rules for certain objects or branches of a Content Class tree corresponding to a department or a discipline. The access to changing the contracts may also be limited to help ensure that the contracts are not bypassed.

Claims

1. A method for change control management of schema definition objects across disparate systems, comprising:

determining when a proposed change associated with an object is made;

performing an impact analysis on the proposed change;

determining when the proposed change does not affect other objects, and when, implementing the change, otherwise;

creating a change object based on the proposed change;

allocating voting rights to users based on the impact analysis and an associated negotiated change contract;

determining when to accept the change based on a voting scheme; and

approving the change when accepted;

otherwise canceling the change.

2. The method of claim 1, wherein allocating the voting rights further comprises associating levels of permission to classes of the objects.

3. The method of claim 2, wherein the levels of permission are selected from a set comprising:

owner, stakeholder, and subscriber.

4. The method of claim 1, further comprising utilizing change control contracts that are associated with the objects.

5. The method of claim 4, further comprising customizing the contracts to establish change management rules for an enterprise and to specialize rules for certain objects or branches of a Content Class tree corresponding to a department or a discipline.

6. The method of claim 5, further comprising limiting access to customizing the contracts such that the contracts are not bypassed.

7. The method of claim 4, wherein a user may set at least one of the following parameters:

a number of timeout days;

an enforce timeout parameter;

an allow post-period votes parameter;

a voting rules matrix, and business rules.

8. The method of claim 2, wherein the voting rights further comprise an approval right, a veto right, and a no vote right.

9. The method of claim 7, wherein the contract inherits down a vocabulary tree.

10. The method of claim 4, wherein performing the impact analysis on the proposed change further comprises finding a contract that is the most relevant to the object with the proposed change.

11. The method of claim 10, wherein finding the contract that is the most relevant further comprises finding the contract with the closest proximity.

12. The method of claim 11, wherein finding the contract with the closest proximity further comprises using the creation time of the contract.

13. The method of claim 1, wherein performing the impact analysis on the proposed change further comprises determining users that are affected by the proposed object change.

14. The method of claim 13, further comprising assessing the proposed change up a tree to a root term of a vocabulary.

15. A system for change control management of schema definition objects across disparate systems, comprising:

a server, comprising;

a network connection configured to communicate with clients;

a memory configured to store resources;

a process configured to perform functions, comprising;

determining when a proposed change associated with an object is made by one of the clients;

performing an impact analysis on the proposed change;

determining when the proposed change does not affect other objects, and when the proposed change does not affect other objects implementing the change, otherwise;

creating a change object based on the proposed change;

allocating voting rights to users based on the impact analysis;

determining when to accept the change based on voting by the clients; and

approving the change when accepted;

otherwise canceling the change.

clients, comprising;

a network connection configured to communicate with the server;

a memory configured to store resources; and

a process arranged to receive and send information relating to objects with the server and configured to perform actions, comprising;

voting on the proposed change; and

proposing a change to an object.

16. The system of claim 15, wherein allocating the voting rights further comprises associating levels of permission to classes of the objects.

17. The system of claim 15, wherein the levels of permission are selected from a set comprising:

owner, stakeholder, and subscriber.

18. The system of claim 15, further comprising utilizing change control contracts that are associated with the objects.

19. The system of claim 18, further comprising customizing the contracts to establish change management rules for an enterprise and to specialize rules for certain objects or branches of a Content Class tree corresponding to a department or a discipline.

20. The system of claim 19, further comprising limiting access to customizing the contracts such that the contracts are not bypassed.

21. The system of claim 18, wherein a user may set at least one of the following parameters:

a number of timeout days;

an enforce timeout parameter;

an allow post-period votes parameter;

a voting rules matrix, and business rules.

22. The system of claim 16, wherein the voting rights further comprise an approval right, a veto right, and a no vote right.

23. The system of claim 21, wherein the contract inherits down a vocabulary tree.

24. The system of claim 18, wherein performing the impact analysis on the proposed change further comprises finding a contract that is the most relevant to the object with the proposed change.

25. The system of claim 24, wherein finding the contract that is the most relevant further comprises finding the contract with the closest proximity.

26. The system of claim 25, wherein finding the contract with the closest proximity further comprises using the creation time of the contract.

27. The system of claim 15, wherein performing the impact analysis on the proposed change further comprises determining users that are affected by the proposed object change.

28. The system of claim 27, further comprising assessing the proposed change up a tree to a root term of a vocabulary.

29. A system for change control management of schema definition objects across disparate systems, comprising:

means for determining when a proposed change associated with an object is made;

means for performing an impact analysis on the proposed change;

means for determining when the proposed change does not affect other objects, and when, implementing the change, otherwise;

means for creating a change object based on the proposed change;

means for allocating voting rights to users based on the impact analysis;

means for determining when to accept the change based on a voting scheme; and

means for approving the change when accepted;

otherwise canceling the change.