Object-oriented system for program version and history database management system for various program components

• US 5,659,735 A
• Filed: 12/09/1994
• Issued: 08/19/1997
• Est. Priority Date: 12/09/1994
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Object Technology Licensing Corporation
• Inventors: Parrish, Jeff W., Thyagarajan, P., Maghoul, Farzin
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Rones, Charles
• Application Number:
  US08/353,021
• Time in Patent Office: 984 Days
• Field of Search: 395/600, 395/700, 395/775, 395/156, 395/610, 395/683, 395/601, 395/608, 395/674, 395/703, 395/619, 395/500, 364/200, 364/650, 364/300
• US Class Current: 1/1
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A distributed program history database system is designed for use on a client-server network. The system consists of a plurality of program history 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 history servers. After connection to the history 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 history 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 program development management system for assembling in a project workspace, a program configuration comprising a plurality of software program components, the system comprising:

a program component database for storing a plurality of program component drafts and a root component identifying program component drafts associated with the program configuration;

means contained in the project workspace for locating the program component database and for sending a program component request 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 root component to identify program component drafts belonging to the program configuration.

2. A program development management system according to claim 1 wherein the program component database stores a plurality of root component drafts and the means for sending a program component request comprises means for selecting one of the plurality of root component drafts for program component retrieval.

3. A program development management system according to claim 1 further comprising a first program component database containing the root component draft and some of the program component drafts associated with the program configuration and a second program component database containing some of the program component drafts associated with the program configuration.

4. A program development management system according to claim 3 wherein the root component comprises information identifying program component drafts located in the first program component database and information for locating the second program component database.

5. A program development management system according to claim 4 further comprising means located in the project workspace for retrieving the information for locating the second program component database from the root component and means for retrieving program component drafts from the second program component database.

6. A program development management system according to claim 1 wherein the software program components are comprised of a plurality of component kinds and property kinds and wherein the program development management system comprises means for storing the plurality of component kinds and property kinds in the project workspace.

7. A program development management system according to claim 6 further comprising means for sending the plurality of component kinds and property kinds from the project workspace to the program component database.

8. A program development management system for assembling in a project workspace, a plurality of software program components comprising a program configuration, the system operating on a client-server network and comprising:

a history server connected to the network and comprising a program component database for storing a plurality of program component drafts and a root component identifying program components associated with the program configuration;

a client terminal connected to the network and containing means for creating the project workspace and means for locating the history server on the network;

means in the project workspace for sending a program component request to the history server; and

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

9. A program development management system according to claim 8 further comprising a plurality of history servers, each connected to the network and wherein some of the program component drafts belonging to the program configuration are located on a first history server containing the root component and some of the program component drafts belonging to the program configuration are located on a second history server and wherein the root component comprises information for locating the second history server on the network.

10. A program development management system according to claim 9 wherein the root component comprises a list of program component drafts belonging to the program configuration which are located on the first history server and information for locating the second history server on the network.

11. A program development management system according to claim 8 wherein the history server comprises means for displaying a time sequence of program component drafts.

12. A program development management system according to claim 8 wherein the root component comprises a list of program component drafts belonging to the program configuration and wherein the program component retrieval means comprises means responsive to the program component request for iterating through the program component list.

13. A program development management system according to claim 8 further comprising means located in the client terminal for connecting the client terminal to the history server over the network.

14. A program development management system according to claim 8 wherein the client terminal comprises a tree structure with branches and means for adding program component drafts retrieved from the history server to the branches.

15. A program development management system according to claim 8 wherein the program component drafts have component properties and component kinds and wherein the client terminal further comprises means for storing the component properties and the component kinds.

16. A program development management system according to claim 15 wherein the client terminal further comprises metadata for associating the component kinds and the component properties and the storing means comprises means for storing the metadata in the client terminal.

17. A program development management system according to claim 16 further comprising means for sending the metadata from the client terminal to the history server.

18. A method for assembling in a project workspace, a program configuration comprising a plurality of software program components, the method comprising the steps of:

A. creating a program component database and storing in the program component database a plurality of program component drafts and a root component identifying program component drafts associated with the program configuration;

B. using information in the project workspace to locate the program component database and send a program component request to the program component database; and

C. retrieving program component drafts from the program component database in response to the program component request using the root component to identify program component drafts belonging to the program configuration.

19. A method according to claim 18 wherein step A comprises the step of:

A1. storing a plurality of root component drafts in the program component database; and

step C comprises the step of;

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

20. A method according to claim 18 wherein step A comprises the steps of:

A2. creating a first program component database containing the root component draft;

A3. storing some of the program component drafts associated with the program configuration 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 in the second program component database.

21. A method according to claim 20 wherein step A comprises the further step of:

A6. adding to the root component information identifying program component drafts located in the first program component database and information for locating the second program component database.

22. A method according to claim 21 further comprising the steps of:

D. retrieving the information for locating the second program component database from the root component; and

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