Computerized design automation method using a single logical PFVL paradigm

• US 5,950,201 A
• Filed: 12/06/1996
• Issued: 09/07/1999
• Est. Priority Date: 12/06/1996
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Van Huben, Gary Alan, Mueller, Joseph Lawrence
• Primary Examiner(s): Kulik, Paul V.
• Assistant Examiner(s): HOMERE, JEAN RAYMOND
• Application Number:
  US08/759,692
• Time in Patent Office: 1,005 Days
• Field of Search: 707/10, 707/102, 707/8, 707/203, 707/4, 364/468.02, 395/200.31
• 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: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A design control system suitable for use in connection with the design of integrated circuits and other elements of manufacture having many parts which need to be developed in a concurrent engineering environment with inputs provided by users and or systems which may be located anywhere in the world providing a set of control information for coordinating movement of the design information through development and to release while providing dynamic tracking of the status of elements of the bills of materials in an integrated and coordinated activity control system utilizing a repository which can be implemented in the form of a database (relational, object oriented, etc.) or using a flat file system. Once a model is created and/or identified by control information design libraries hold the actual pieces of the design under control of the system without limit to the number of libraries, and providing for tracking and hierarchical designs which are allowed to traverse through multiple libraries. Data Managers become part of the design team, and libraries are programmable to meet the needs of the design group they service.

Claims

1. A method for computerized design automation comprising,

accessing a file and database management system for managing a plurality of projects as a design control system,

organizing data repository for each project for data records and a control repository comprising a common access interface and one or more databases,

said control repository communicating with users of said design control system for fulfilling requests of a user and the data repositories of said data management control system through a plurality of managers, each manager performing a unique function;

and

combining selected ones of said managers for supporting an computerized design automation application environment suitable for multiple users of a user community located at workstations anywhere in the world accessible via a network, an intranet, extranet or via the internet; and

defining for each project a control repository and one or more data repositories to store, manage and manipulate any data object, whereby said control repository communicates with users and the data repositories in numerous ways to support environments ranging from a small user community to a global enterprise; and

tracking all data and control information in an architecturally centralized location consisting of said data repository and said control repository using a single logical PFVL paradigm to identify all data in the DMS by Package, File Type, (Data Type), Version and Level, and wherein packages are arbitrary divisions of data, whereby all the data has some common association to a library.

2. A method for computerized design automation according to claim 1 wherein every piece of the design which is associated to a

Library--Variance--Quality Level--View--Cell--Version has all of the data associated so that the system ensures every piece of data has all its PFVL attributes associated with it, permitting every piece of data or attribute of a design element in the Data Management System (DMS), regardless of origin or importance, to be tracked by its PFVL single logical association of every piece of the design.

3. A method for computerized design automation according to claim 1 further comprising, providing that data management model structure capable of tracking a plurality of data objects governed under similar or disparate processes, wherein all objects are classified as part of a library, having one or more types, each type having one or more versions, and each version having one or more levels.

4. A method for computerized design automation according to claim 3 wherein said library is a grouping of objects which all have common characteristics causing them to belong to the same library grouping, and wherein within a library, data is organized by version, wherein versions allow parallel evolution of the same component data element to coexist in the same library enabling multiple versions of a component data element to be developed in tandem while using the same object name and residing in the same library and at the same level simultaneously.

5. A method for computerized design automation according to claim 4 wherein for each said version, there is a level structure denoting a degree of completeness, stability or quality control enabling said data manager a means to establish a level structure commensurate with the goals and objectives of the user community.

6. A method for computerized design automation according to claim 5 wherein at least some of the data objects are at a level chained to another level to allow data to migrate from one Level to the next, and wherein any or all of these Levels can be designated as Entry Levels allowing data to be entered into this Entry Level from a user'"'"'s Private Library;

and wherein there are also levels categorized as working levels and release levels wherein data in working levels is transitory, and must eventually migrate to a release level, while release levels provide permanent storage vaults for a coherent set of data.

7. A method for computerized design automation according to claim 1 further comprising, providing an architecturally centralized location which does not require that the location be physically in the same location but requires that the user must perceive the system in a manner by which all data appears to be tracked uniformly which enables the user to do things like find/view all the data associated with the design when multiple pieces of data are in physically disparate locations.

8. A method for computerized design automation according to claim 1 further comprising, the steps of mapping in order to use the system together with other systems the system attribute for conversion to provide the following mapping:

space="preserve" listing-type="tabular">__________________________________________________________________________Library Variance Quality Level View CellName Version / \ / \ / \ / \ / .backslash . / \ \ / \ / .backslash . / \ / \ / \ / Package Version Quality Level Type FileName Iteration. __________________________________________________________________________

9. A method for computerized design automation according to claim 1 further comprising, providing that the system provides working areas which serve as a private library for a user assigned to a team by a data manager, and to perform shared data management each team may have any number of Release or Integration Areas, while team members may have unlimited Working Areas and the system data manager can create release or integration areas, specify the physical location of the data, and rename or delete the Release or Integration Area at any time, and create virtual levels to define the type of structure required for concurrent engineering with multiple levels and variances, promote data between virtual levels and into Release Areas, and enable users to look at data in all Release or Integration Areas simultaneously.

10. A method for computerized design automation according to claim 1 further comprising, enabling with said PFVL single logical paradigm attributes of non-system originated data to be tracked and made accessible along with system originated data with a system command.

11. A method for computerized design automation according to claim 1 further comprising, enabling a user call for a system function, third party tool, shell script, perl script, C program, or any other type of application programming interface from within a user system may be invoked from a command line.

12. A method for computerized design automation according to claim 1 further comprising, enabling a locking mechanism which enables transfer of ownership permanently or temporarily of PFVL data, and allows for an override or rest of the check out locks, and provides notification to the original designer or administrator in the event of check out.

13. A method for computerized design automation according to claim 1 further comprising, providing that all data and control information is tracked in an architecturally centralized location consisting of a data and control repository for a project using a single logical PFVL paradigm, and wherein said system provides a dynamic Bill of Materials Tracker to identify all the desired pieces of a design at a particular Library, Level and Variance to be built into a "model".

14. A method for computerized design automation according to claim 1 further comprising, providing that all data and control information is tracked in an architecturally centralized location consisting of a data and control repository for a project using a single logical PFVL paradigm, and wherein said system provides Automated Library Processing whereby tools, checks and automated tasks can be launched either during movement of data between levels or while data is stable within a level and where results would be associated to the exact data objects used in the process and retained in the Control Repository.

15. A method for computerized design automation according to claim 1 further comprising, providing that all data and control information is tracked in an architecturally centralized location consisting of a data and control repository for a project using a single logical PFVL paradigm, and wherein said system provides Problem Fix Management and Engineering Change Tracking which would provide various utilities to ensure that fixes to problems are contained within the proper release or EC.

16. A method for computerized design automation according to claim 1 further comprising, enabling interaction with said Managers of the DMS to perform tasks such as Automated Library Processing, Problem Fix and EC management, BOM Tracking, Authority and Lock checking before, during and after the promotion of data in the DMS.

17. A method for computerized design automation according to claim 1 further comprising, enabling the use of Automated Library Machines in a client server environment for purposes of processing promotion requests, initiating and executing Automated Library Processes, installing newly created data into the DMS, performing any other functions provided by said Managers of the DMS, and permitting execution of non-DMS tasks through the use of an Auto-reader virtual queue.

18. A method for computerized design automation according to claim 1 further comprising, enabling accessible multiple working library levels, and means for extracting data from a public library.

19. A method for computerized design automation according to claim 5 all data objects are identified by name and type.

20. A method for computerized design automation according to claim 19 wherein at least some of the identified data objects are identified by a type of data object which depicts the objects as files.

21. A method for computerized design automation according to claim 19 wherein at least some of the identified data objects are identified by a type of data object which depicts the objects as files, while other data objects identified by the same file name exist, such that an entity of said data management system characterized by a single name may have multiple types of data objects, simultaneously residing in multiple Levels, of multiple versions and spanning multiple libraries.

22. A method for computerized design automation according to claim 6 wherein at least some of the data objects when the data is promoted into a release level, that Level is frozen and a new release level is opened such that data always migrates from the highest Working Level into the current, or open, Release Level.

23. A method for computerized design automation according to claim 6 wherein at least some of the data objects when the data is promoted into a release level, that Level is frozen and a new release level is opened such that any working level may be promoted to from another working level, or serve as an entry level for data coming from a Private Library while a current Release Level can be promoted to, but can'"'"'t be an entry point for outside data and frozen Release Levels are neither entry points nor are they promotable.

24. A method for computerized design automation according to claim 1 further comprising, providing that every piece of data or attribute of a design element in the Data Management System (DMS), regardless of origin or importance, is tracked by its PFVL single logical association of every piece of the design.

25. A method for computerized design automation according to claim 1 wherein a database for the control repository includes a multimedia database.

26. A method for computerized design automation according to claim 1 wherein a database for the data repository includes a multimedia database.