Method for managing a hierarchical design transaction

• US 5,678,040 A
• Filed: 12/02/1996
• Issued: 10/14/1997
• Est. Priority Date: 10/29/1993
• Status: Expired due to Term

• Current Assignee: Freescale Semiconductor, Inc. (NXP Semiconductors NV)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Vasudevan, Venu, Womack, Tron Kyle, Gibson, Don Michael, Gossain, Dhiraj Kumar, Rigg, Dana Mark
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/759,339
• Time in Patent Office: 316 Days
• Field of Search: 395/608, 395/615, 395/610, 395/617, 395/619, 395/614
• US Class Current: 1/1
• CPC Class Codes: G06F 2111/02 CAD in a network environment, e.g. collaborative CAD or distributed simulation
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A hierarchical design transaction method which provides a shared project workspace and an individual user workspace. A desired portion of a hierarchical design is checked out from the shared project workspace and is edited in the individual user workspace. A new version of the desired portion of the hierarchical design is checked into the shared project workspace. Concurrently, another individual user workspace is provided, and another desired portion of the hierarchical design is checked out, edited and checked in. These steps are repeated for each of a plurality of desired portions of the hierarchical design, to continuously guarantee consistency between the shared project workspace and each individual user workspace.

Claims

1. A hierarchical design transaction method, comprising the steps of:

providing a first region of a computer memory which is identified as a shared project workspace and which contains a first version of a hierarchical design stored therein;

providing a second region of computer memory which is designated as an individual user workspace;

providing a second version of the hierarchical design in the shared project workspace;

checking out a desired portion of the hierarchical design from the shared project workspace by copying the desired portion of the hierarchical design into the individual user workspace;

editing the desired portion of the hierarchical design in the individual user workspace;

checking in a new version of the desired portion of the hierarchical design into the shared project workspace to continuously guarantee consistency between the shared project workspace and each individual user workspace, while maintaining both the second version of the hierarchical design and the relationships between the new version and the second version of desired portion of the hierarchical design in the shared project workspace; and

guaranteeing the internal consistency of the shared project workspace at all times.

2. The hierarchical design transaction method of claim 1 wherein guaranteeing the internal consistency of the shared project workspace comprises disallowing changes to previously checked in items such that the shared project workspace must grow as changes are made.

3. A hierarchical design transaction method, comprising the steps of:

providing a first region of a computer memory which is identified as a shared project workspace and which contains a hierarchical design stored therein;

providing a second region of computer memory which is designated as an individual user workspace;

providing a first version of a hierarchical design in the individual user workspace;

providing a second version of the hierarchical design in the shared project workspace;

checking out a desired portion of the hierarchical design from the shared project workspace by copying the desired portion of the hierarchical design into the individual user workspace;

editing the desired portion of the hierarchical design in the individual user workspace;

checking in a new version of the desired portion of the hierarchical design into the shared project workspace to continuously guarantee consistency between the shared project workspace and each individual user workspace, while maintaining both the second version of the hierarchical design and the relationships between the new version and the second version of desired portion of the hierarchical design in the shared project workspace; and

completely deleting the first version of the hierarchical design from the individual user workspace before the step of checking out the second version of the hierarchical design.

4. A hierarchical design transaction method, comprising the steps of:

providing a first region of a computer memory which is identified as a shared project workspace and which contains a hierarchical design stored therein;

providing a second region of computer memory which is designated as an individual user workspace;

checking out a desired portion of the hierarchical design from the shared project workspace by copying the desired portion of the hierarchical design into the individual user workspace;

editing the desired portion of the hierarchical design in the individual user workspace; and

checking in a new version of the desired portion of the hierarchical design into the shared project workspace to continuously guarantee consistency between the shared project workspace and each individual user workspace, while maintaining both the hierarchical design stored in the shared project workspace and the relationships between the new version of the desired portion of the hierarchical design and the hierarchical design stored in the shared project workspace, wherein the new version of the desired portion of the hierarchical design comprises a sub-hierarchy comprising a root item and at least one leaf item and further wherein the step of checking in the root item requires that all items that are descendent from the root item are checked in before the root item itself is checked in.

5. The hierarchical design transaction method of claim 4, wherein the root item is itself a descendent of a higher level item and the step of checking in the root item creates a new version of the subtree in the shared project workspace.

6. The hierarchical design transaction method of claim 5, further comprising:

providing an item which is only read by an individual user workspace;

subsequently checking out the item into the individual user workspace; and

promoting the item from a read only mode to an edit mode in such a way as to allow editing of the item in the individual user workspace.

7. The hierarchical design transaction method of claim 6, wherein promoting of an item requires that all references between the item and the sub-tree already present in the individual user workspace are also promoted to the edit mode.

8. A hierarchical design transaction method, comprising:

providing a first region of computer memory which is identified as shared project workspace and which contains a hierarchical design stored therein;

providing a second region of computer memory which is designated as an individual user workspace;

identifying a plurality of individual items within the shared project workspace which can be manipulated individually;

providing a first version of the hierarchical design in the individual user workspace;

providing a second version of the hierarchical design in the shared project workspace;

checking out individual items from the shared project workspace by copying a desired portion of the hierarchical design into the individual user workspace;

locking individual items within the shared project workspace so as to guarantee that only one edit is performed on an item at any time, while still allowing concurrent read only access to the item;

editing the desired portion of the hierarchical design in the individual user workspace;

checking in a new version of the desired portion of the hierarchical design into the shared project workspace; and

concurrently repeating the steps of providing a second region of computer memory, checking out a desired portion of the hierarchical design, editing the desired portion of the hierarchical design, and checking in a new version of one desired portion of the hierarchical design for each of a plurality of desired portions of the hierarchical design, in such a way as to continuously guarantee consistency between the shared project workspace and each individual user workspace, including completely deleting the first version of the hierarchical design from the individual user workspace before the step of checking out the second version of the hierarchical design, and in addition guarantee the internal consistency of the shared project workspace at all times.

9. A hierarchical design transaction method, comprising:

providing a first region of computer memory which is identified as shared project workspace and which contains an hierarchical design stored therein;

providing a second region of computer memory which is designated as an individual user workspace;

identifying a plurality of individual items within the shared project workspace which can be manipulated individually;

checking out individual items from the shared project workspace by copying the desired portion of the hierarchical design into the individual user workspace;

restricting the individual items which may be checked out to items which form a single sub-tree hierarchy within the design;

locking individual items within the shared project workspace so as to guarantee that only one edit is performed on an item at any time, while still allowing concurrent read only access to the item;

editing the desired portion of the hierarchical design in the individual user workspace while restricting changes in the relationships between items to those items which are checked out for edit;

checking in a new version of the desired portion of the hierarchical design into the shared project workspace wherein the new version of the desired portion of the hierarchical design comprises a sub-hierarchy comprising a root item and at least one leaf item and further wherein the step of checking in the root item requires that all items are descendent from the root item are checked in before the root item itself is checked in; and

concurrently repeating the steps of providing a second region of computer memory, checking out a desired portion of the hierarchical design, editing the desired portion of the hierarchical design, and checking in a new version of one desired portion of the hierarchical design for each of a plurality of desired portions of the hierarchical design, in such a way as to continuously guarantee consistency between the shared project workspace and each individual user workspace, and in addition guarantee the internal consistency of the shared project workspace at all times.