Object-oriented system for configuration history management with a project workspace and project history database for draft identification

• US 5,752,245 A
• Filed: 12/09/1994
• Issued: 05/12/1998
• Est. Priority Date: 12/09/1994
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Object Technology Licensing Corporation
• Inventors: Maghoul, Farzin, Parrish, Jeff W.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US08/353,027
• Time in Patent Office: 1,250 Days
• Field of Search: 395/600, 395/700, 395/182.18, 395/800, 395/156, 395/650, 395/221, 395/601, 395/610, 395/200.1
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A distributed program configuration database system is designed for use on a client-server network. The system consists of a plurality of program servers which maintain version information for various program components. A program developer, upon logging into a client terminal on the network, establishes a workspace or project and connects with one of the servers. After connection to the server has been made, a draft of the program configuration is retrieved from the server. The configuration draft may include information for constructing some of the program components and "bridge" information identifying other program servers where additional program components are located. The workspace uses the component information to assemble components and the bridge information to connect to other servers and retrieve the remaining components in order to assemble the complete source code for a program in the workspace.

Claims

1. A method for assembling in a project workspace, a version of a program configuration comprising a plurality of software program components, each of said software components being stored in a tree structure and containing member properties including at least one draft identifier identifying a draft of said component as belonging to said program configuration version, comprising the steps of:

A. creating a program component database and storing in the program component database a plurality of program component drafts, each of said program component drafts including a draft identifier identifying said program component draft as being associated with a program configuration version;

B. using information in the project workspace to locate said program component database and send a program component request including a component draft identifier for each component belonging to said program configuration version to said program component database; and

C. retrieving program component drafts from the program component database in response to said program component request using said draft identifier to identify said program component drafts belonging to said program configuration version.

2. A method according to claim 1 wherein step A comprises the step of:

A1. storing a plurality of component drafts for each component belonging to said program configuration version in the program component database; and

step C comprises the step of;

C1. selecting one of the plurality of component drafts for program component retrieval.

3. A method according to claim 1 wherein step A comprises the steps of:

A2. creating a first program component database containing at least some of the components;

A3. storing some of the program component drafts associated with the program configuration version in the first component database;

A4. creating a second program component database; and

A5. storing some of the program component drafts associated with the program configuration version in the second program component database.

4. A method according to claim 3 wherein step A comprises the further step of:

A6. adding to the components located in the first program component database information for locating the second program component database.

5. A method according to claim 4 further comprising the steps of:

D. retrieving the information for locating the second program component database from the components in the first program component database; and

E. retrieving program component drafts from the second program component database.

6. A method according to claim 1 wherein the software program components are comprised of a plurality of component kinds and property kinds and wherein the method further comprises the step of:

F. storing the plurality of component kinds and property kinds in the project workspace.

7. A method according to claim 6 further comprising the step of:

G. sending the plurality of component kinds and property kinds from the project workspace to the program component database.

8. A method for assembling in a project workspace, a plurality of software program component drafts comprising a program configuration version over a client server network, the method comprising the steps of:

A. creating a history server;

B. connecting the history server to the network;

C. creating in the history server a program component database for storing a plurality of program component drafts each of the program component drafts including a component ID and a draft ID identifying the program component draft as being associated with a program configuration version;

D. creating a client terminal containing the project workspace, a draft ID associated with the program configuration version and means for locating the history server on the network;

E. connecting the client terminal to the network;

F. sending a program component request from the project workspace to the history server; and

G. retrieving program component drafts from the program component database in response to the program component request using the draft ID to identify program component drafts belonging to the program configuration version.

9. A method according to claim 8 wherein step A comprises the step of:

A1. creating a plurality of history servers;

step B comprises the step of;

B1. connecting each history server to the network; and

step C comprises the steps of;

C1. storing some of the program component drafts belonging to the program configuration version on a first history server;

C2. storing some of the program component drafts belonging to the program configuration on a second history server; and

C3. storing in the component drafts belonging to the program configuration version on the first history server information for locating the second history server on the network.

10. A method according to claim 9 wherein step C1 comprises the steps of:

C1A. storing in the first history server a component containing a list of program component drafts for the component belonging to the program configuration version which are located on the first history server; and

C1B. storing information in the component for locating the second history server on the network.

11. A method according to claim 8 further comprising the step of:

H. displaying a graph of program component drafts.

12. A method according to claim 11 wherein the component comprises a list of program component drafts belonging to the program configuration version and wherein step G comprises the step of:

G1. iterating through the program component draft list in response to the program component request.

13. A method according to claim 8 wherein step D comprises the steps of:

D1. creating in the client terminal a tree structure with branches; and

D2. adding program component drafts retrieved from the history server to the branches.

14. A method according to claim 8 wherein the program component drafts have component properties and component kinds and wherein step D further comprises the step of:

D3. storing the component properties and the component kinds in the client terminal.

15. Apparatus for use on a computer system with a memory, the apparatus assembling in a project workspace, a version of a program configuration comprising a plurality of software program components, each of the software components being stored in a tree structure and containing member properties including at least one draft identifier identifying a draft of the component as belonging to the program configuration version, the apparatus comprising:

a program component database in the memory including a plurality of program component drafts, each of the program component drafts including a draft identifier identifying the program component draft as being associated with a program configuration version;

means responsive to information in the project workspace for locating the program component database and for sending a program component request including a component draft identifier for each component belonging to the program configuration version to the program component database; and

means responsive to the program component request for retrieving program component drafts from the program component database using the draft identifier to identify the program component drafts belonging to the program configuration version.

16. Apparatus according to claim 15 wherein the program component database includes a plurality of component drafts for each component belonging to the program configuration version in the program component database;

and retrieving means comprises means for selecting one of the plurality of component drafts for program component retrieval.

17. Apparatus according to claim 15 wherein the program component database comprises:

first program component database containing at least some of the components and some of the program component drafts associated with the program configuration version; and

a second program component database containing some of the program component drafts associated with the program configuration version.

18. Apparatus according to claim 17 wherein the first program component database includes information for locating the second program component database.

19. Apparatus according to claim 18 further comprising:

means for retrieving the information for locating the second program component database from the components in the first program component database; and

means for retrieving program component drafts from the second program component database.

20. A computer program product for use in a computer system having a memory, the computer program product assembling in a project workspace, a version of a program configuration comprising a plurality of software program components, each of the software components being stored in a tree structure and containing member properties including a at least one draft identifier identifying a draft of the component as belonging to the program configuration version, the computer program comprising a computer usable medium having computer readable program code thereon including:

program code for creating a program component database in the memory and program code storing in the program component database a plurality of program component drafts, each of the program component drafts including a draft identifier identifying the program component draft as being associated with a program configuration version;

program code for using information in the project workspace to locate the program component database and send a program component request including a component draft identifier for each component belonging to the program configuration version to the program component database; and

program code for retrieving program component drafts from the program component database in response to the program component request using the draft identifier to identify the program component drafts belonging to the program configuration version.

21. A computer program product according to claim 20 wherein the program code for creating a program component database comprises program code for storing a plurality of component drafts for each component belonging to the program configuration version in the program component database;

and wherein the program code for retrieving program component drafts comprises program code for selecting one of the plurality of component drafts for program component retrieval.

22. A computer program product according to claim 20 wherein the program code for creating a program component database comprises:

program code for creating a first program component database containing at least some of the components;

program code for storing some of the program component drafts associated with the program configuration version in the first component database;

program code for creating a second program component database; and

program code for storing some of the program component drafts associated with the program configuration version in the second program component database.

23. A computer program product according to claim 22 wherein the program code for creating a program component database comprises program code for adding to the components located in the first program component database information for locating the second program component database.

24. A computer program product according to claim 23 further comprising:

program code for retrieving the information for locating the second program component database from the components in the first program component database; and

program code for retrieving program component drafts from the second program component database.