US5659735A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Object-oriented system for program version and history database management system for various program components
Assignee: Apple Inc
•
Filing: 1994-12-09
•
Granted: 1997-08-19
•
Expires: 2014-12-09
Abstract
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.
Inventors
- 👤 Jeff W. Parrish
- 👤 Farzin Maghoul
- 👤 P. Thyagarajan
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-25 09:50
CPC Classifications
G; G06; G06F; G06F8/00; G06F8/70; G06F8/71
Claims Analysis
Total Claims: 25
Claim 1
Independent Claim
105 words
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.
Claim 2
Dependent Claim
105 words
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.
Claim 3
Dependent Claim
46 words
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.
Claim 4
Dependent Claim
51 words
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.
Claim 5
Dependent Claim
35 words
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.
Claim 6
Dependent Claim
45 words
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.
Claim 7
Dependent Claim
48 words
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.
Claim 8
Dependent Claim
31 words
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.
Claim 9
Dependent Claim
135 words
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.
Claim 10
Dependent Claim
135 words
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.
Claim 11
Dependent Claim
80 words
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.
Claim 12
Dependent Claim
44 words
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.
Claim 13
Dependent Claim
24 words
A program development management system according to claim 8 wherein the history server comprises means for displaying a time sequence of program component drafts.
Claim 14
Dependent Claim
47 words
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.
Claim 15
Dependent Claim
29 words
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.
Claim 16
Dependent Claim
34 words
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.
Claim 17
Dependent Claim
37 words
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.
Claim 18
Dependent Claim
39 words
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.
Claim 19
Dependent Claim
24 words
A program development management system according to claim 16 further comprising means for sending the metadata from the client terminal to the history server.
Claim 20
Independent Claim
112 words
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.
Claim 21
Independent Claim
112 words
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.
Claim 22
Dependent Claim
47 words
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.
Claim 23
Dependent Claim
70 words
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.
Claim 24
Dependent Claim
41 words
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.
Claim 25
Dependent Claim
38 words
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.
References Cited (Backward Citations)
US4558413A
Cited
US4821220A
Cited
US4885717A
Cited
US5325522A
Cited
US4809170A
Cited
US5421012A
Cited
US4891630A
Cited
US4953080A
Cited
US5136705A
Cited
US5041992A
Cited
US5133075A
Cited
US5050090A
Cited
US5325524A
Cited
US5060276A
Cited
US5125091A
Cited
US5321841A
Cited
US5181162A
Cited
US5093914A
Cited
US5075848A
Cited
US5276876A
Cited
US5313636A
Cited
US5151987A
Cited
US5315709A
Cited
US5379426A
Cited
US5119475A
Cited
US5325481A
Cited
US5317741A
Cited
US5392432A
Cited
US5305461A
Cited
US5418945A
Cited
US5315703A
Cited
US5574898A
Cited
US5499357A
Cited
US5325533A
Cited
US5519866A
Cited
US5553282A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-08-18 | 2001-02-17 | 2001-08-19 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-08-18 | 2005-02-17 | 2005-08-19 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-08-18 | 2009-02-17 | 2009-08-19 | $7700.00 | Window Closed / Lapsed |