JP4532609B2 - Process management apparatus and method, and storage medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a process management apparatus and method for managing a plurality of processes, and a storage medium.
[0002]
[Prior art]
When designing a design, particularly a circuit on a substrate, using an interactive image processing apparatus such as CAD, there are roughly the following two design methods.
[0003]
First, in the first design method, a circuit element is input, a circuit diagram created by inputting the circuit element is verified, layout processing such as placement and routing is performed on the substrate, and a desired design is generated. Is.
[0004]
The second design method is to design the functional level of the circuit, verify the functional level, create a circuit diagram based on the verification result, verify the created circuit diagram, A layout process such as placement and routing is performed to generate a desired design. Recently, this second design technique is becoming more common.
[0005]
By the way, when designing a design object, it is necessary to proceed with processing in a plurality of processes. Conventionally, the designer has worked separately for each of the plurality of processes. Therefore, it is not easy to manage the entire design process including a plurality of processes.
[0006]
The “management” here is roughly divided into two types.
[0007]
First, “management” for each process is performed. The activation condition of the processing program activated at the time of executing each process is confirmed, the activation is controlled, and the design data to be used is managed.
[0008]
Further, it is “management” for a plurality of processes, and the process is transferred to the next process when the execution of the process is completed, and the design data is referred to between the processes.
[0009]
And now, or in the future, there are limits to the designer's own control over increasingly complex design processes. Therefore, recently, an apparatus for collecting and managing a plurality of processes has been required.
[0010]
In designing a design object, in order to collectively manage a plurality of processes, two elements such as a processing program that is activated at the time of executing each process and information on a design object that is the basis of the design object are in particular included. This is a very important factor in determining the design content.
[0011]
First, the processing program that is activated when each process is executed is a program that performs design processing on the computer screen and performs various data processing. In the field of electricity, an input tool for electrical components and various verifications are performed. There are tools, and recently, tools for expressing functions using block diagrams and state transition diagrams. For example, SUMMIT's “VisualHDL” is a functional level design tool, and Antares' “V-System / VHDL” is a functional level verification tool. In addition, since there are many processing programs that perform the same work as these, it is difficult to select which one should be used.
[0012]
In addition, there are ASIC (Application Specific Integrated Circuit) etc. in the design object that is the basis of the design object. In the design, the vendor name (manufacturer name), type, shape information, etc. Must be set. Therefore, when the design object to be used changes, it is necessary to change the execution order of the processes and the processing program activated in each process.
[0013]
In this way, in designing a design, the processing program that is activated when each process is executed and the information about the design object that is the basis of the design are extremely important elements. It seems that it will become extremely important to carry out process management focusing on one element.
[0014]
[Problems to be solved by the invention]
However, because the design, especially ASIC, is becoming increasingly dense and large-scale, the process for its design has become extremely complex. With conventional technology, it is necessary to manage these processes. , Putting a heavy burden on the designer.
[0015]
In addition, the design object that is the basis of the design object and the processing programs that are activated in each process have been diversified, and the conventional technology cannot cope with such a rapid change.
[0016]
In addition, in the prior art, when the design object that is the basis of the design object or the processing program that is started in each process is changed, the designer has to perform many setting operations related to it. .
[0017]
In addition, in the prior art, setting of information related to the design object that is the basis of the design object was performed from the design start stage, so the designer can change the information related to the design object during the design. However, in order to change the information, it was necessary to redesign from the design start stage.
[0018]
Further, in the conventional technique, a plurality of different patterns cannot be designed in parallel with respect to a design object that is the basis of a design object.
[0019]
The present invention consolidates complicated design processes of a design, and greatly simplifies the setting of a design object that is the basis of the design and the setting of a processing program that is activated when each process is executed. The purpose is to reduce the burden of design and to reduce design errors.
[0020]
Another object of the present invention is to make it possible to change information related to a design object that is the basis of a design object during design.
[0021]
It is another object of the present invention to allow a plurality of different design processes to be performed in parallel when designing a design object that is the basis of a design object.
[0022]
[Means for Solving the Problems]
In order to achieve the above object, the process management apparatus of the present invention is a process management apparatus that manages the execution order of a plurality of processes by displaying them on a display so as to be recognizable, and is generated in the plurality of processes. Each of the plurality of processes based on the state determined by the determination means, the storage means for storing the derivation relationship information of the data, the determination means for determining whether or not the plurality of processes are executable Display processing means for displaying on the display so as to be identifiable whether or not can be executed, wherein the discrimination means is a first for use during execution of the discrimination target process. Is generated in the first step, which is the previous step of the discrimination target step, The second data is the previous process of the discrimination target process There is a subsequent process of the first process. In the second process Raw From the derivation relationship information stored by the storage means. The second data is generated for the first data Derived relationship And the second data is generated by a program selected from a plurality of programs executed in the second step, The discrimination target process is executable When It is characterized by discriminating.
[0023]
Also, the processing method of the process management apparatus that manages the execution order of the plurality of processes by recognizing them on the display so as to be recognizable, the processing apparatus stores the derivation relationship information of the data generated in the plurality of processes in the storage device. Each of the plurality of steps can be executed based on a storage step for storing, a determination step for determining whether or not the plurality of steps can be performed, and a state determined by the determination unit. A display processing step that causes the processing device to display on the display so that it can be identified whether or not there is, and in the determination step, the processing device is a first for use when executing the determination target step. Is generated in the first step, which is the previous step of the discrimination target step, The second data is the previous process of the discrimination target process There is a subsequent process of the first process. In the second process Raw From the derivation relationship information stored in the storage device. The second data is generated for the first data There is a derivation relationship, and When the second data is generated by a program selected from a plurality of programs executed in the second step, It is determined that the determination target process is executable.
[0037]
DETAILED DESCRIPTION OF THE INVENTION
(Hardware configuration of design management device)
First, the hardware configuration of the design management apparatus according to the present invention will be described in detail.
[0038]
FIG. 1 is a hardware configuration diagram of the design management apparatus 101. Each component of the design management apparatus 101 will be described with reference to FIG.
[0039]
In FIG. 1, reference numeral 102 denotes a keyboard for converting various information such as character information, command information, and operation instruction information into electronic signals and inputting them. Reference numeral 103 denotes a CRT display for displaying various information input from an input device such as a keyboard 102 or a mouse 104 described later. The designer can confirm the operation of the design management program 112 and the CAD tool group 113 for carrying out the present invention by viewing the display on the CRT display 103. In particular, in the present invention, the CRT display 103 is very important as a configuration for determining what is being performed and what is to be performed next. Reference numeral 104 denotes a mouse, which is a pointing device for designating an arbitrary position on the CRT display 103.
[0040]
A program storage device 111 includes a memory such as a ROM, and stores programs such as a design management program 112 and a CAD tool group 113, and these programs are executed by the arithmetic processing device 106. A data storage device 110 includes a memory such as a RAM, and is generated by data used by the design management program 112 and the CAD tool group 113 stored in the program storage device 111 or by processing of the arithmetic processing device 106. Stored data and the like are stored. Reference numeral 105 denotes a hard disk device for storing not only various databases but also programs stored in the program storage device 111 and data stored in the data storage device 110. Of course, a program executed when the program is executed and data to be read and written may be stored in the hard disk device 105 in advance.
[0041]
An arithmetic processing unit 106 executes programs such as the design management program 112 and the CAD tool group 113 stored in the program storage device 111 based on electronic information received from the keyboard 102 and the mouse 104, and stores data in the data storage device 110. Read and write data.
[0042]
A conversion device 107 includes a graphics board, a video board, and the like, and converts electronic information transmitted from the arithmetic processing device 106 into information to be expressed on the CRT display 103.
[0043]
In this embodiment, a printer 108 is provided as an output device other than the CRT display 103, and information is printed out from the conversion device 107.
[0044]
Reference numeral 109 denotes a bus that electrically connects each component.
[0045]
Then, data is exchanged between the constituent elements by a desired operation of the designer, thereby realizing a desired design for the design object.
[0046]
(Concept of design management program)
FIG. 2 is a conceptual diagram of functions realized by the design management program 112 stored in the program storage device 111 of FIG.
[0047]
In the present embodiment, the design management program 112 is a program for managing a plurality of processes related to the design of a design, and is the basis of the operation of the design management apparatus 101. Hereinafter, the function of the design management program 112 will be described with reference to FIGS.
[0048]
The design management program 112 is roughly divided into two functions, a “data management function 201” and a “process management function 202”.
[0049]
First, the “data management function 201” is a function for managing a management database (hereinafter, management D / B 204) and a design database (hereinafter, design D / B 205) stored in the hard disk 105. Here, the management D / B 204 is a collection of unique data handled by the design management program 112. Specifically, the initial information data file 501, group information data file 502, CAD tool information data file 503, vendor data file 504, group management data 505, ASIC data 506, message log data file 507, lock information data file 508, etc. Is stored (see FIG. 5). The design D / B 205 stores general data generated by the CAD tool and a history management information data file 401.
[0050]
The data used or generated by the CAD tool is referred to as design data, which includes CAD tool environment data and log files.
[0051]
The “process management function 202” is a function for managing setting operations and design work processes (workflows) by the design management program 112.
[0052]
Further, the CAD tool group 113 is a program group stored in the program storage device 111 as in the case of the design management program 112 as described above.
[0053]
The processing performed by the “data management function 201” and the “process management function 202” for the CAD tool group 113, the management D / B 204, and the design D / B 205 will be described below.
[0054]
First, when an acquisition request for data stored in the management D / B 204 or the design D / B 205 is made from the “process management function 202” to the “data management function 201”, the “data management function 201” Is acquired from the management D / B 204 and the design D / B 205 and returned to the “process management function 202”. When the “process management function 202” designates a desired CAD tool and sets the design environment for the CAD tool group 113, the “process management function 202” displays an error code when executing the designated CAD tool. And an end code are acquired from the CAD tool group 113. Further, the “data management function 201” inquires each D / B about the stored data. If the data is in each D / B, the “data management function 201” Obtain from D / B. The CAD tool group 113 acquires design data stored in the design D / B 205, and the CAD tool group 113 outputs design data generated by executing an arbitrary CAD tool to the design D / B 205. To do.
[0055]
FIG. 3 is a diagram showing the main functions of the design management program.
[0056]
FIG. 3 is used to show the relationship between the “data management function 201” and the “process management function 202” in further detail.
[0057]
The “data management function 201” includes a “design data management function 300” and an “environmental data management function 310”, and the “process management function 202” includes a “project operation function 320” and a “setting change function”. 340 ”,“ flow control function 350 ”,“ startup control function 330 ”, and“ information confirmation function 360 ”.
[0058]
Each of the functions constituting the “data management function 201” and “process management function 202” further includes a plurality of functions.
[0059]
First, the “design data management function 300” is one of the functions of the “data management function 201”, and performs various processes on each data in the design D / B 205. Specific functions include a version management function 300-1, a derivative management function 300-2, a purge operation function 300-3, a history management function 300-4, and an environment restoration function 300-5.
[0060]
FIG. 4 is a diagram showing an outline of each function in the “design data management function 300”.
[0061]
The version management function 300-1 is a function for so-called versioning of design data in the design D / B 205, and stores a design environment including design data generated by a CAD tool and directory information. At this time, the design environment before activation is registered as an old version, and the design environment after activation is registered as a new version. As described above, the version management function 300-1 saves the design environment for each activation, and numbers the design data generated by the CAD tool in ascending order in the generation order. Of course, the numbering order is not limited to ascending order, and any order may be used.
[0062]
The derivation management function 300-2 is a function for linking design data in the design D / B 205. If the version management function 300-1 is a vertical management function, the derivation management function 300-2 is a horizontal management function. It can be said. The derivation management function 300-2 represents which design data is generated based on the design data generated by each CAD tool of the CAD tool group 113, and manages the derivation relationship between the design data. (The mechanism is such that the derivation relationship can be read from the history management information data file 401.) Derivation information for each design data is generated immediately after version management by the version management function 300-1. The generated derivative information is a key to the purge operation function 300-3 and the history management function 300-4.
[0063]
The purge operation function 300-3 is a function for organizing design data in the design D / B 205, and the number of management version data is set to a value determined by the initial information file 501 when the version management function 300-1 upgrades. If it exceeds, delete the oldest version of design data. The manageable version number can be set as a variable used in the design management program 112.
[0064]
The history management function 300-4 is a function for managing history information of design data using the history management information data file 401 stored in the design D / B 205. The version management function 300-1, the derivation management function 300-2 and the entire history of design data used by the purge operation function 300-3 are managed. Information between each design data is stored in the history management information data file 401, and the history management function 300-4 also performs input / output processing for the history management information data file 401. Also, design data history information is output to the “process management function 202”.
[0065]
The environment restoration function 300-5 is a function for restoring environment information including design data of the design D / B 205. More specifically, the environment restoration function 300-5 is more specifically one generation before the CAD tool is started (of course, two generations or three generations ago). This is a function for restoring the boot environment. Therefore, a file operation or the like is directly executed on the design D / B 205.
[0066]
Next, the “environmental data management function 310” is one of the functions of the “data management function 201” and manages unique data referred to by the “process management function 202”. Specific functions include an initial information management function 310-2, a design information management function 310-3, a backup management function 310-1, and a lock management function 310-4.
[0067]
FIG. 5 is a diagram showing the relationship between each function in the “environment data management function 310” and the environment data.
[0068]
The backup management function 310-1 is a function for managing the group management data 505, the ASIC data 506, and the message log data file 507 that are the backup (save the state before update) in the management D / B 204. When the environmental data is saved in the management D / B 204 by the setting process of the “process management function 202”, the data before saving is backed up (data is copied).
[0069]
The initial information management function 310-2 is a screen display on the CRT display 103 and data whose values can be set from the values stored in the initial information data file 501 in the management D / B 204 when the design management program 112 is started. This is a function for setting default information.
[0070]
The design information management function 310-3 is used when using the target setting function 340-1, the CAD tool change function 340-2 in the “setting change function 340” of the “process management function 202”, and the group-related functions. This function manages various information in the management D / B 204 such as a group information data file 502, a CAD tool information data file 503, a vendor data file 504, group management data 505, and ASIC data 506. The “group” in the present embodiment is a set of a plurality of designers when one project is executed.
[0071]
The lock management function 310-4 uses the lock information data file 508 in the management D / B 204, and designates that the “process management function 202” and the design information management function 310-3 are prohibited from changing the contents. It is a function to perform. The lock information data file 508 created by the lock management function 310-4 holds information regarding such prohibition of content change.
[0072]
Next, the “project operation function 320” is one of the functions of the “process management function 202”, and creates and selects a project. As actual processing, data necessary for processing is acquired from the “environmental data management function 310” by text input and selection from the designer, and processing is performed on design data and group information. Specific functions include a design data operation function 320-1 and a group management function 320-2. The “project” in the present embodiment is a design unit for designing a certain design.
[0073]
FIG. 6 is a diagram showing an outline of each function in the “project operation function 320”.
[0074]
The design data operation function 320-1 is a function for inputting / outputting data to / from selection information 601 stored in the hard disk 105 and used in a “flow control function 350” or “startup control function 330” described later. Specifically, a new project is created, copied, or deleted by inputting text or selecting it from the designer. The selected data is stored as selection information 601.
[0075]
The group management function 320-2 is a function corresponding to the network of the “project operation function 320”, and performs processing for responding to group design.
[0076]
Next, the “startup control function 330” is one of the functions of the “process management function 202” and performs a series of operations until the CAD tool is started up.
[0077]
FIG. 7 is a diagram showing an outline of each function in the “startup control function 330”.
[0078]
The activation condition confirmation function 330-1 is a function for confirming the CAD tool activation condition from the selection information 601 selected by the “project operation function 320”. There is.
[0079]
The CAD tool determination function 330-2 is a function for determining the type of CAD tool to be activated and the processing content from setting change information 701 and rule information 702 determined by a “setting change function 340” described later.
[0080]
The work shortening function 330-3 is a design process in which a plurality of work integrated in one process (the relationship between this process and work will be described in detail later. One process is constituted by a plurality of work. It is a function that executes up to necessary work. That is, this is a function that can reduce the number of operations in the process. Normally, all the work contents in the process are executed, but this work shortening function 330-3 can save useless time. Note that the work to be executed is determined by the designer's specification.
[0081]
The environment setting function 330-4 is a function for constructing an activation environment as pre-processing for CAD tool activation. In addition, processing for requesting restoration of environment data by the environment restoration function 300-5 of the “design data management function 300”, confirmation of design data, and the like are also performed here.
[0082]
Next, the “setting change function 340” is one of the functions of the “process management function 202”, and is a function for performing various setting operations (also referred to as a retarget function). Specific functions of the “setting change function 340” include a target setting function 340-1, a CAD tool change function 340-2, an input / output buffer change function 340-3, and a control rule determination function 340-4.
[0083]
Each function of the “setting change function 340” indicates that the design management program 112 has flexibility in changing information related to the ASIC. And by such a flexible function of the design management program 112, it is possible to realize many efficiencies such as shortening the design period and improving operability for the designer.
[0084]
Hereinafter, the target setting function 340-1, the CAD tool change function 340-2, the input / output buffer change function 340-3, and the control rule determination function 340-4 will be described in detail with reference to FIG.
[0085]
FIG. 8 is a diagram showing an outline of each function in the “setting change function 340”.
[0086]
The target setting function 340-1 is a function for setting data related to an ASIC (hereinafter referred to as a target) for designing an ASIC as a finished design product. Provided by the management function 310 ". Note that information relating to the target set by the designer (hereinafter referred to as “target information 803”) and CAD tool allocation information 802 described later are collectively referred to as setting change information 701.
[0087]
The CAD tool change function 340-2 is a function for allocating a CAD tool activated in each process of the design process for each process. The CAD tool corresponding to each process is limited, and information on the limited CAD tool is provided by the “environmental data management function 310”. The CAD tool allocation information 802 obtained here becomes a part of the setting change information 701 together with the target information 803 as described in the description of the target setting function 340-1.
[0088]
The input / output buffer changing function 340-3 is a function for changing the input / output buffer temporarily input in the upper process of the design, and the changed contents are stored as the input / output buffer information 801. The input / output buffer changing function 340-3 can be executed only in a specific process.
[0089]
The control rule determination function 340-4 is a function for determining a rule in each process controlled by the design management program 112 from the setting change information 701 obtained by the target setting function 340-1 and the CAD tool change function 340-2. Information regarding this rule is provided by the “environmental data management function 310”. The confirmed rule is handled as rule information 702 and affects the confirmation of the process state after the CAD tool is activated.
[0090]
Next, the “flow control function 350” is one of the functions of the “process management function 202”, and is a function for controlling the process state and managing the process state for each process managed by the design management program 112. . There are two specific functions: a design process confirmation function 350-1 and a process state management function 350-2. In order to realize the “flow control function 350”, the above-described selection information 601, setting change information 701, rule information 702, and the like are necessary.
[0091]
FIG. 9 is a diagram showing an outline of each function in the “flow control function 350”.
[0092]
The design process determination function 350-1 is a function for determining all the processes for designing the ASIC from the setting change information 701 and the selection information 601, and the designer advances the design along the determined process. The desired ASIC design can be realized.
[0093]
The process state management function 350-2 is a function for determining the process state of each process from the setting change information 701 and the rule information 702. The process state includes an executable state, an unexecutable state, a selected state, and an execution state. There are four types of states.
[0094]
Finally, the “information confirmation function 360” is one of the functions of the “process management function 202” and is a design auxiliary function. Many of these functions are for checking the progress of design, such as the message display function 360-1 and the history information display function 360-2. Although this function is not necessarily required for design, the design management program 112 adopts this function as necessary for the designer to efficiently design the ASIC.
[0095]
FIG. 10 is a diagram showing an outline of each function in the “information confirmation function 360”.
[0096]
The message display function 360-1 is a function for receiving a direct message from the CAD tool and displaying the information on a message panel described later on the CRT display. The message displayed on the message panel is “environmental data management”. To function 310 ". The transmitted message is managed as a message log data file 507.
[0097]
The history information display function 360-2 displays the history information from the “design data management function 300” on a history management panel (to be described later) on the CRT display, and at the same time designates the lock to the purge operation function 300-3. It is a function to perform. Further, the target information 803 can be referred to on the history management panel.
[0098]
Then, based on the hardware configuration of the design management apparatus 101 and the concept explanation of the process management program 112 described above, the embodiment of the present invention will be described in detail below.
[0099]
(First embodiment)
<Design process flow>
First, an outline of the design of a design using the design management apparatus 101 will be described.
[0100]
In order to design a desired design, it is necessary to advance the design stage according to a certain design method. In the present embodiment, each stage of this design is referred to as a “process”, and the entire work flow by such a plurality of “processes” is referred to as a “project”. Each process of this project includes processes such as system design, functional design, logic design, circuit design, mounting design, layout design, and test design. Usually, following such a design process, a design is completed through processes such as a manufacturing process and a test process.
[0101]
The design method as described above is actually often used for designing an integrated circuit developed for a specific application such as an ASIC. The ASIC in this embodiment includes full custom IC, semi-custom IC, ASSP (Application Specific Standard Product), PLD (Programmable Logic Array), and FPGA (Field Programmable Gate Array). It may be just a gate array, or it may be anything other than general-purpose products.
[0102]
In this embodiment, all the steps of the project are managed by one program, the design management program 112.
[0103]
Now, a basic processing flow when designing using the design management program 112 will be described with reference to FIG.
[0104]
After the design management program 112 is started ((1)), when the designer sets information on the ASIC used for the design, ie, the target ((2)), a predetermined project corresponding to the target is selected. The process group is displayed on the CRT display 103 ((3)). (At the same time, the rule information 702 for controlling it is determined.) Then, when an arbitrary executable process is selected by the designer (4), the process of the selected process is executed (4). (5)). As described above, when the selection and execution of executable processes (4 and 5) are sequentially performed from the first process to the final process, a desired design process is completed.
[0105]
In the following, an embodiment of the present invention will be described in detail based on this series of processing flows.
[0106]
<Process status display>
First, in the design management apparatus 101, when an activation command is input from the keyboard 102, the design management program 112 is activated, and a main panel 901 as shown in FIG. 12 is displayed on the screen on the CRT display 103. Similarly, the design management program 112 can also be input by keying in the name of the design management program 112 from the keyboard 102 or designating the icon representing the design management program 112 on the CRT display 103 with the mouse 104. When activated, the main panel 901 is displayed on the CRT display 103. Of course, the design management program 112 may be activated by an operation other than these methods.
[0107]
FIG. 12 is a diagram showing a main panel 901 displayed on the CRT display 103 when the design management program 112 is activated.
[0108]
In FIG. 12, 902 is an area where a process group managed by the design management program 112 is displayed, and 903 is an operation constituting a process selected from the process groups displayed in the area 902. This is the area where the contents are displayed. (As will be described later, each process is constituted by a further process group. Such a process is called “operation” in this embodiment.)
[0109]
Reference numeral 904 denotes a button group for inputting an instruction command, and the command is input by instructing the button group with the mouse 104 or the like. Reference numeral 905 denotes a target display area that displays target information 803. 906 is a [Start] button for instructing execution, and 907 is a [Cancel] button for instructing cancellation.
[0110]
Reference numeral 908 denotes a mouse cursor, which moves on the screen in response to an instruction from the mouse 104 and designates a desired position. In FIG. 9 and subsequent figures, the display of the mouse cursor 908 is omitted.
[0111]
Next, with respect to the main panel 901 as shown in FIG. 12, process contents and target information 803 are determined by input processing from the keyboard 102 and the mouse 104, and the process flow managed by the design management apparatus 101 is shown. The image is displayed in an area 902 on the main panel 901 as shown in FIG.
[0112]
FIG. 13 is a diagram illustrating an example when a plurality of processes are displayed in the area 902.
[0113]
In FIG. 13, each process that represents various processes is represented by each block indicating a process, which is given a name such as “ESDA” or “VHDL Simulation” displayed in the area 902. Yes. In FIG. 13, the process is expressed as a block. However, there is no problem even if the process is expressed by a square shape, a round shape, or just a character, and any process can be used as long as it can express the process. In the present embodiment, it is relatively easy to input a rectangle, it is easy for the designer to recognize that some processing is being performed in the process, and the work content in the process is easily imaged by characters. For this reason, a rectangle with letters was used.
[0114]
The arrows displayed between the processes are used for the purpose of facilitating the designer to recognize the connection between processes, the transmission of data between the processes, and the input. Of course, it is also possible to express this arrow with other things.
[0115]
A diagram represented by blocks and arrows in this region 902 is referred to as a process related diagram in this embodiment.
[0116]
FIG. 14 shows another example of the process related diagram as a similar example of the process related diagram of FIG.
[0117]
In the present embodiment, processing of each process and its state change will be described based on the process related diagram shown in FIG. In FIG. 14, each process is simply shown as process 1, process 21, process 22, and the like. For example, “ESDA” in FIG. 13 corresponds to step 1 in FIG.
[0118]
In FIG. 14, the direction of the arrow between step 1 and step 22 is different from that in FIG. 13 because the flow of generated data is different. In the process related diagram of FIG. 13, the data generated in the process written “Timing” is an upward arrow for use in the process written “VHDL Simulation”. On the other hand, in FIG. 14, only the reference is performed without generating data in step 22, or data that is not used in the subsequent steps is generated, and thus the directions of the arrows are reversed. In FIG. 14, the direction of the arrow between step 3 and step 43 is different from that in FIG. 13 for the same reason.
[0119]
Of course, it is needless to say that many processes using process related diagrams other than those shown in FIGS. 13 and 14 may exist.
[0120]
And the process which each block in FIG. 14 shows has four states, an executable state, an unexecutable state, a selection state, and an execution state. Here, the executable state is a state where the process can be executed when the designer instructs the execution of the process. On the other hand, the inexecutable state is a state in which when the designer instructs execution of a process, the instruction is ignored and the process is not executed. The selected state is a state in which the process is selected by an instruction from the designer, and the execution state is a state in which the process is just being executed.
[0121]
Here, since the CRT display 103 is a color display, the object in the process related diagram is displayed in color. In this case, the process in the inexecutable state described above is “red” and the process in the executable state is “blue”. Then, each state is displayed in four colors, such as “yellow” for the process in the selected state and “white” for the process in the execution state.
[0122]
Of course, each state may be any combination of colors, but here it is easy to express, easy to recognize, and the effect of color (for example, red is a caution or prohibition effect) The combination of color and state was determined in consideration of Further, as an identification method other than color, it is also possible to display an object specifying the state on or around the block indicating the process. Further, the state of the process is not limited to these four classifications, and may be three or less classifications or five or more classifications.
[0123]
Whether each step can be executed depends on whether each step satisfies or does not satisfy a condition called “executable condition”.
[0124]
The executable condition in the present embodiment mainly refers to a condition determined by the rule information 702. In general, a condition such as whether or not a process preceding the target process is executable, This means a condition such as whether or not the data generated in the process before the target process is data used when the process is executed.
[0125]
In addition, a condition such as whether or not there is a “derivative relationship” between data used at the time of execution of the target process and data generated in the process before that process is one of the executable conditions. It is. This “derivative relationship” will be described in the sixth embodiment.
[0126]
Now, a process of sequentially verifying the state of each process shown in the process-related diagram in the region 902 from the first process to the last process will be described in detail with reference to FIG.
[0127]
FIG. 15 is a flowchart of the process state verification process.
[0128]
First, in step S111, the first (first) process is recognized. Next, in step S112, the executable conditions in the process are confirmed, and in step S113, it is determined whether or not the executable conditions in the process are satisfied. If the condition is satisfied, the process proceeds to step S114, and the display of the process is changed to the display of the startable state (normally, the unverified process is an initial state without color). In step S116, the next process is recognized. After the movement, in step S117, it is determined whether or not the presence of the next process is recognized. If the next process is recognized, the process is performed again from step S112. If not recognized, it is determined that all processes have been completed, and the process state verification process is terminated. In step S112, if the executable condition is not satisfied, the process proceeds to step S115, the process display is changed to the display of the inoperable state, and then the process proceeds to step S116, where the executable condition is satisfied. The same process is performed.
[0129]
The verification process shown in FIG. 15 can change a process that is in an executable state to an inexecutable state when the state is not set in each process in the initial state, or by setting target information or a CAD tool. This process is performed when there is a characteristic (detailed later). This is because in these cases, all the states must be verified from the first step.
[0130]
However, when a certain process is executed, the change due to the execution is limited to the process after the process in which the execution process is performed. Therefore, it is useless to perform the verification from the first process. A process that simplifies this will be described in detail with reference to the flowchart of FIG.
[0131]
FIG. 16 is a flowchart of the simplified verification process of the process state.
[0132]
First, in step S221, the next process of the executed process is recognized. Next, in step S222, the executable conditions in the process are confirmed, and in step S223, it is determined whether or not the executable conditions in the process are satisfied. When the condition is satisfied, the process proceeds to step S224, and the process display is changed to the display of the startable state. In step S225, the next process is recognized. After the movement, in step S226, it is determined whether or not the presence of the next process is recognized. If the next process is recognized, the process is performed again from step S222. If not recognized, it is determined that all processes have been completed, and the process state verification process is terminated.
[0133]
In step S223, if the executable condition is not satisfied, the process proceeds to step S227, where the process display is changed to the display of the unstartable state, and the next process is recognized in step S228. After the movement, in step S229, it is determined whether or not the next process is recognized. If the next process is recognized, the process is performed again from step S227. If not recognized, it is determined that all processes have been completed, and the process state verification process is terminated.
[0134]
Since the verification process shown in FIG. 16 manages the design process in one direction, it must be managed so that it cannot proceed to the next process unless the previous process is finished, so that the designer does not injure the wrong design operation. Yes. That is, it is possible to prevent an executable process from existing after the infeasible process.
[0135]
As described above, by selectively performing the inspection process in two process states, it is possible to execute a process according to the situation.
[0136]
<Process execution and state change>
Now, various examples in which one process is selected and executed from among a plurality of processes in a state where the process related diagram is displayed in the area 902 on the main panel 901 will be described below. To do.
[0137]
First, the change in the state of steps 21 and 22 when the process of step 1 in FIG. 14 is executed, that is, the change of the state of a plurality of steps as the next process when the process of one step is executed. This will be described with reference to FIG.
[0138]
FIG. 17 is a diagram illustrating a change in the process state when the process 1 is executed.
[0139]
In FIG. 17, it is assumed that a process surrounded by a thick line as in process 1 is in an executable state, and a block surrounded in a thin line as in process 2 is in an inexecutable state. This is a convenient display method employed because color display is not possible in the figure. In FIG. 17, by instructing the block of step 1 with an input device such as the mouse 104, the block of step 1 is selected, and the [Start] button 906 on the main panel 901 of FIG. 13 is selected. Then, it is possible to execute the process 1 in the executable state that is in the selected state. When selecting again, the [Cancel] button 907 on the main panel 901 may be selected. The selection can be made again by selecting another process. For example, when the process 1 to the process 21 that are in the selected state are selected, if the process 21 is selected with the mouse 104 as it is, the selected state of the process 1 is canceled and the process 2 is selected.
[0140]
This execution method is also used in the execution described later. Of course, it is possible to select and execute a process by other execution methods.
[0141]
Here, when the step 1 in the executable state is executed, the state of the step 21 and the step 22 in the non-executable state in the next step of the step 1 is caused by the change of the executable condition by the execution of the step 1. The state changes to the four states shown in the lower part of FIG. In the lower part of FIG. 17, steps 1, 21, and 22 in the region 902 on the main panel 901 are extracted and displayed as a region 1001.
[0142]
First, if the execution of step 1 could not be terminated properly for some reason (hereinafter referred to as “abnormal termination”) or the execution of step 1 was terminated correctly (hereinafter referred to as “normal termination”) Nevertheless, if the feasible conditions for the steps 21 and 22 are not satisfied, the process states of the steps 21 and 22 do not change.
[0143]
Next, when step 1 is normally completed and only the executable condition of step 21 is satisfied, only step 21 is changed to an executable state, and when only the executable condition of step 22 is satisfied, Only step 22 changes to an executable state. Furthermore, when both the step 21 and the step 22 satisfy the feasibility condition, both change to an executable state.
[0144]
Of course, the execution state change of the process 21 and the process 22 may be performed from either.
[0145]
Now, a specific example of the state change due to the executable condition will be given. For example, in step 1, when data A that is an executable condition of step 21 and data B that is an executable condition of step 22 can be generated, when process 1 ends abnormally, In the case where neither data A nor data B can be generated even though the process 1 is normally completed, the process states of the process 21 and the process 22 do not change. In addition, when step 1 is normally completed and only data A is generated, only step 21 is changed to an executable state, and when only data B is generated, only step 22 is changed to an executable state. However, when both data A and data B are generated, both change to an executable state.
[0146]
Even in the case where there are three or more next processes, the state change is determined by verifying the feasible conditions of each process. In the present embodiment, when there are a plurality of subsequent processes for a process to be executed, the process state can always be determined by the procedure shown above.
[0147]
FIG. 18 shows the change in the state of step 3 when the process of step 21 in FIG. 14 is executed, that is, the change in the state of one process that is the next step when the process of one step is executed. It explains using.
[0148]
FIG. 18 is a diagram illustrating a change in the process state when the process of the process 21 is executed.
[0149]
Here, in the relationship between the process 21 in the process relation diagram in the upper part of FIG. 18 and the process 3 which is the next process, by executing the block of the process 21 on the process relation diagram, the state of the process 3 is changed.
[0150]
First, when the process 21 is normally completed and the executable condition of the process 3 is satisfied, the process 3 changes to an executable state. Conversely, if the process 21 ends abnormally, or if the executable condition of the process 3 is not satisfied even though the process 21 ends normally, the process state on the screen does not change.
[0151]
In addition, a change in the state of steps 41, 42, and 43 when the process of step 3 is executed will be described with reference to FIG.
[0152]
FIG. 29 is a diagram illustrating a change in the process state when the process 3 is executed.
[0153]
In the upper part of FIG. 29, portions of Step 41, Step 42, Step 43, Step 51, and Step 52 in the region 902 on the main panel 901 are extracted and displayed as a region 1003.
[0154]
First, the change in the feasible condition of the next step 41, step 42, and step 43 due to the execution of step 3 is verified. Since the verification method is the same as the method described above, detailed description thereof is omitted. When all the next steps are ready to be executed, the next steps, step 51 and step 52, are further verified.
[0155]
Thus, there is no limit on the number of steps to be executed and the next step, and the feasible conditions are verified by the number of the next steps at the end of each execution step.
[0156]
<Outline of process work>
By the way, each process shown by a block is further comprised of a plurality of processes (referred to as operations in this embodiment).
[0157]
FIG. 19 is a diagram illustrating a schematic display example of work contents in a process.
[0158]
For example, when the process 1 that can be executed in the process related diagram of the area 902 as shown in the upper part of FIG. 19 is selected by an input device such as the keyboard 102 or the mouse 104, the main panel 901 shown in FIG. In a region 903 that is a blank portion below the region 902, a work schematic diagram shown in the lower part of FIG. 19 is displayed.
[0159]
This figure shows the work contents in the process 1, and clearly shows that the work 1-1 is processed by the execution of the process 1. For example, in step 1, if data is generated by the arithmetic processing unit 106 executing a program stored in the program storage device 111, the operation 1-1 represents the program.
[0160]
The symbols displayed in operation 1-1 of this operation schematic diagram are not limited to blocks, but are not limited to characters written on a rectangle, as in the case of displaying processes. There may be.
[0161]
In FIG. 19, when a process other than the process 1 is selected on the screen by the input device such as the keyboard 102 or the mouse 104 in a state where the process 1 is selected, instead of the outline of the work of the process 1, Displays an outline of the work of the selected process.
[0162]
Next, FIG. 20 is a diagram illustrating a schematic display example of work when a plurality of works exist in one process.
[0163]
For example, if three operations are aggregated in the executable process 1, by selecting the process 1, the operation schematic diagram in the area 903 includes a block indicating three operations and an operation described later. Arrow buttons “↑ button 1101” and “↓ button 1102” for shortening the contents are displayed on the upper right and lower sides. By operating this arrow button, the work content can be shortened. This button can be located anywhere, and the arrow image can be replaced with another image. The display example in FIG. 20 is adopted in consideration of operability and recognizability.
[0164]
The contents of the three operations shown in this operation schematic diagram are, for example, data conversion in operation 1-1, and generation of other data by reading the data converted in operation 1-1 in operation 1-2. In the operation 1-3, for example, the data generated in the operation 1-2 is converted again.
[0165]
The display of the outline of the operation | work of another process can also be expressed by the same method.
[0166]
Next, FIG. 21 is a display example when the outline of the work shown in the display example of FIG. 20 is changed by the work shortening process.
[0167]
21 is the same as that shown in the lower part of FIG. 20. In the upper part of FIG. 21, the designer uses the input device such as the keyboard 102 and the mouse 104 to press the “↑ button 1101”. When the instruction is given, the work content changes to a state in which only the work 1-1 is displayed as shown in the lower left diagram of FIG. This indicates that the work executed in the process 1 is only the work 1-1. The “↑ button 1101” is originally a button for increasing the number of operations in the process, but in this case, since there can be at most three operations in the process 1, the “↑ button 1101” is used. The work schematic diagram changes to display a minimum number of work contents.
[0168]
On the contrary, when the “↓ button 1102” is instructed, the work outline diagram changes as shown in the lower right diagram of FIG. Since the “↓ button 1102” is a button for reducing the number of operations, the number of operations decreases from three to two.
[0169]
When the “↑ button 1101” is instructed in the state of the lower left figure of FIG. 21, the state of the lower right figure is obtained, and when the “↓ button 1102” is instructed, the number of operations has already been minimized. It changes to the state which displays all the work contents like. Further, when the “↑ button 1101” is instructed in the state shown in the lower right diagram of FIG. 21, the state is as shown in the upper diagram.
[0170]
Of course, the change in the number of operations by this shortening process is not limited to the case where the maximum number of operations in the process is 3, but may be any number. Further, when a process is executed after such a shortening process, only the work displayed in the work schematic diagram in the area 903 is executed.
[0171]
Here, referring again to FIG. 17, an example of a case where this shortening process and a change in the process state are related will be given.
[0172]
In FIG. 17, the process 1 has three work contents such as work 1-1, work 1-2, and work 1-3. The work 1-1 converts the original data into data A, and the work 1-2. In this example, data B is created from data A, and operation 1-3 converts data B to generate data C. In addition, it is assumed that the executable condition of the process 21 is data A and data B, and the executable condition of the process 22 is data B.
[0173]
Under this condition, by the shortening process, the content of the work in the process 1 is changed to the state of the work 1-1 only, for example, as shown in the lower left diagram of FIG. When the data is output, neither the feasible condition of the step 21 nor the feasible condition of the step 22 is satisfied, so that the state after the execution of the step 1 is the lower leftmost state in FIG.
[0174]
Also, by the shortening process, the work contents in the process 1 are set to the work 1-1 and the work 1-2 as shown in the lower right diagram of FIG. When A and data B are output, both the feasible condition of step 21 and the feasible condition of step 22 are satisfied, so the state after the execution of step 1 changes to the lower right state of FIG. .
[0175]
Now, the flow of processing relating to the execution of the steps described so far and the change in the state of the steps will be described in more detail with reference to the flowcharts of FIG. 22, FIG. 23 and FIG. In other embodiments to be described later, the processes shown in these flowcharts are the basis.
[0176]
First, FIG. 22 is a basic flowchart regarding the process of selecting and executing a process by the operation of the designer and changing the number of operations in the process.
[0177]
In the area 902 on the main panel 901, a plurality of processes are displayed as process related diagrams. In step S121, what is instructed in the area 902 is determined. If any of the processes is instructed by the mouse 104 or the like, the process proceeds to step S122, the instructed process is selected, and the mask of the [Start] button 906 is released in step S123. When the work schematic diagram of the instructed process is confirmed in step S124, the process proceeds to step S125, and the work schematic diagram is displayed.
[0178]
When the [Start] button 906 is selected in step S121 in the state where this work schematic diagram is displayed, the execution process is performed in step S126, the [Start] button 906 is masked in step S127, and the process is performed in step S128. Cancel the selected state. If the [Cancel] button 907 is selected in step S121, the work outline is hidden in step S129, the [Start] button 906 is masked in step S130, and the process selection state is canceled in step S131. .
[0179]
If a plurality of operations exist in the selected process and the “↓ button 1102” is selected in step S121, the operation schematic diagram is confirmed in step S132, and the operation schematic diagram is displayed in step S133. It is determined whether or not the number of works is 1 (that is, the minimum). If it is 1, the work is maximized in step S135. If it is not 1, the work is reduced by 1 in step S134, and step S136. Redisplay the work schematic with. When the “↑ button 1101” is selected in step S121, the work schematic diagram is confirmed in step S137. In step S138, it is determined whether or not the number of works in the work schematic diagram is maximum. In step S140, the work is set to 1. If it is not the maximum, the work is incremented by 1 in step S139, and the work schematic diagram is redisplayed in step S141.
[0180]
Now, the execution process of step S126 will be described in more detail using the flowchart of FIG.
[0181]
Since other processes cannot be performed in parallel while the execution process is being performed, the main panel 901 is masked in step S151. Masking the main panel 901 means locking the panel and buttons so that other operations cannot be performed during the execution process. In step S152, it is confirmed which process is selected, and in step S153, the selected process is changed to an execution state. In step S154, it is determined whether there is design data to be used when the CAD tool is activated. If design data does not exist, error processing is performed in step S155, and the process ends. If design data exists, confirmation of the success or failure of securing the work location (directory for discharging output data) is confirmed in step S156. If the design data is unsuccessful, error processing is performed in step S155. In step S157, version management preprocessing (version management processing before starting the CAD tool) is performed. Next, in step S159, arguments necessary for starting the CAD tool are set. Information and arguments regarding the CAD tool are acquired from the rule information 702.
[0182]
Next, in step S161, it is determined whether the CAD tool has been successfully activated. If the activation fails, the error process of step S155 is performed. If the activation is successful, the success or failure of the environment setting is determined in step S163. If the setting fails, the error process of step S155 is again performed. If the setting is successful, the CAD tool is terminated in step S166, and the processing result is confirmed in step S167. If the result is an error, error processing is performed in step S155, and if not, the process proceeds to step S168.
[0183]
Next, in step S168, post-processing of version management (version management processing after starting CAD tool) is performed, the process state is confirmed in step S169, and the mask of the main panel 901 is released in step S170. Finally, in step S171, the work schematic diagram is hidden.
[0184]
Now, the error processing in step S155 will be described in more detail using the flowchart of FIG.
[0185]
In step S181, the restoration environment is deleted, the process selected in step S182 is deselected, the mask of the main panel 901 is released in step S183, and the work schematic diagram is hidden in step S184.
[0186]
Next, the version management preprocessing in step S157 will be described in more detail with reference to the flowchart of FIG.
[0187]
In step S191, it is checked whether or not there is a previous version of data to be input to the CAD tool to be activated. If the previous version data does not exist, error processing is performed in step S155, and if it exists, the process proceeds to step S192 to acquire the current version. In step S193, a temporary version that is one generation ahead of the current version is created. In step S194, the environment is restored mainly by copying design data. However, the process is different only when the first version is set. In this case, only the process for creating a temporary version and the process for creating a boot environment are included.
[0188]
Further, the post-processing of version management in step S168 will be described in more detail using the flowchart of FIG.
[0189]
In step S201, it is confirmed whether or not there is design data output by starting the CAD tool. If the output data does not exist, error processing is performed in step S155, and if it exists, the process proceeds to step S202, and it is confirmed whether the message output by starting the CAD tool is a specific message. In the present embodiment, the check is performed with two patterns: a message for recognizing an error and a message for normal termination. In step S204, switching is performed to raise the temporary version created in step S193 of the preprocessing to the current version. In step S205, the processing result is confirmed. If the result is an error, an error process is performed in step S155. If not, the process proceeds to step S206 to perform a history management process.
[0190]
Next, the history management process in step S206 will be described in more detail with reference to the flowchart of FIG.
[0191]
In step S211, the state of the history management data, which is currently registered history information, is checked. In step S212, the relationship between the design data output from the CAD tool and the input derived data is associated with the derived data. Registration processing is performed, and in step S213, the registration result is determined. If the registration result is an error, error processing is performed in step S155. If not, the process proceeds to step S214, and it is determined whether the history management information data file 401 exists. If the file exists, backup management processing is performed in step S215, and writing to the file is performed in step S216. This backup management process is a process for the history file and is performed through the “environmental data management function 310”. If the history file does not exist, the process proceeds to step S216 as it is, and writing to the file is performed. In step S217, the writing result is determined. If the write result is an error, an error process is performed in step S155, and if not, the process ends.
[0192]
As described above, according to the present embodiment, a plurality of processes are integrated and managed, and the designer can easily identify the state of each process.
[0193]
Moreover, the designer can easily recognize the change in the state of the process by displaying the process whose state is changed by executing the process while changing the color.
[0194]
In addition, since work in the process can be set, a more flexible design is possible.
[0195]
(Second embodiment)
Next, a modified example related to the first embodiment will be given and described as a second embodiment.
[0196]
In the first embodiment, when a process in an inexecutable state appears, the next process is always in an inexecutable state. However, an embodiment in which this is not the case is referred to as a second embodiment. Listed.
[0197]
When the direction of the arrow between Step 1 and Step 22 in FIG. 14 is upward, the data generated in Step 1 and Step 22 is used in Step 21, that is, processing of a plurality of steps is executed. The change in the state of one process, which is the next process, will be described with reference to FIG.
[0198]
FIG. 28 is a diagram illustrating a change in the process state when the process 1 and the process 22 are executed.
[0199]
In the lower part of FIG. 28, portions of Step 1, Step 21, and Step 22 in the region 902 on the main panel 901 are extracted and displayed as a region 1002.
[0200]
In the relationship between the process 1 and the process 22 and the process 21 which is the next process, the process can be executed from two states. In the upper part of FIG. 28, only the process 1 can be executed on the left side. In some cases, the right side shows a case where both are executable. In addition, since it deviates from the concept of the design process of having a unidirectionality from left to right, the process 1 cannot be executed and the process 22 cannot be executed. Therefore, this case is excluded.
[0201]
Then, in these two states, when the execution of each or both of step 1 and step 22 ends normally, the executable condition of step 21 is verified. According to the verification of the step 21, the step 21 changes to an executable state at the time when the executable condition is satisfied.
[0202]
Specifically, first, when step 1 is in an executable state and step 22 is in an inexecutable state, if step 1 ends normally and the executable condition of step 21 is satisfied, step 21 is in an executable state If both Step 1 and Step 22 are in an executable state, both Step 1 and Step 22 end normally, and if both of the Step 21 executable conditions are satisfied, Step 21 is executed. It changes to a possible state.
[0203]
(Third embodiment)
Next, a modified example related to the first embodiment will be given and described as a third embodiment.
[0204]
The third embodiment is an embodiment in the case where execution of a plurality of steps changes the state of a plurality of next steps. The process state inspection method is not different from the previous one.
[0205]
14, the direction of the arrow between step 3 and step 42 is downward, the direction of the arrow between step 3 and step 43 is upward, and the data generated in step 41, step 42, and step 43 is The change in the state of the process when used in the process 51 and the process 52 through the process 41 will be described with reference to FIG.
[0206]
FIG. 30 is a diagram illustrating a change in the process state when the processes 41, 42, and 43 are executed.
[0207]
In the upper part of FIG. 30, portions of step 41, step 42, and step 43 in region 902 on main panel 901 are extracted and displayed as region 1004, and portions of step 41, step 51, and step 52 are displayed in region 1005. Is taken out and displayed.
[0208]
If the process 41 is executable, the design data generated in each of the processes 42 and 43 is used in the process 41, so both the process 42 and the process 43 must be in an executable state. . In FIG. 30, the state change of the area | region 1005 when all the processes 41, 42, and 43 are executable is shown.
[0209]
Here, when each execution of the process 41, the process 42, and the process 43 is normally completed, the feasible conditions of the process 51 and the process 52 are verified. When the feasible conditions of the step 51 and the step 52 are satisfied, the state of the step changes to an executable state. This state change may be the same as already described.
[0210]
(Fourth embodiment)
The work in the process described above is a so-called program, and the program used as the work can be selected from candidates already prepared in the program storage device 111. In the present embodiment, this is called a CAD tool. The CAD tool selection process will be described in detail below.
[0211]
First, when selecting a CAD tool, a CAD tool selection panel 1301 as shown in FIG. 33 is displayed on the main panel 901 on the CRT display 103 in accordance with an instruction from an input device such as the keyboard 102 or the mouse 104. On the CAD tool selection panel 1301, the CAD tool corresponding to each process is selected or changed. Usually, a default CAD tool is designated in advance for each process.
[0212]
FIG. 33 is a diagram showing a CAD tool selection panel 1301 displayed on the main panel 901.
[0213]
In FIG. 33, a triangular mark button 1302 of the CAD tool selection panel 1301 is a sub-window display button. When this button is designated by an input device such as the mouse 104, the button 1302 is displayed in a text area on the right side of the button. A sub window 1305 as shown in FIG. 34 displaying a plurality of CAD tool candidates to be displayed is displayed at an arbitrary position on the CAD tool selection panel 1301.
[0214]
Reference numeral 1303 denotes an [OK] button for confirming selection, and reference numeral 1304 denotes a [Cancel] button for instructing cancellation.
[0215]
Here, the plurality of CAD tools displayed on the CAD tool selection panel 1301 are “ <MainFlow Tool>"and"<SubFlowTool> ”is divided into two, for example, in FIG. 13, a series of processes from“ ESDA ”to“ Release ”is“ Main Flow ”, and“ Timing ”is supplementarily supported. The added process group is called “Sub Flow”.
[0216]
Further, items on the left side of the CAD tool selection panel 1301 indicate the respective processes displayed on the screen of FIG.
[0217]
At the time of execution of each process, the CAD tool selected by the CAD tool selection panel 1301 is displayed in the text area on the right side of the sub window display button 1302 and started as a program for performing the work in the process. The
[0218]
An operation example for changing the CAD tool corresponding to “VHDLSimulation tool” on the CAD tool selection panel 1301 in FIG. 33 will be described. The subwindow display button 1302 on the right side of “VHDLSimulation tool” is instructed to display the setting subwindow 1305 as shown in FIG. 34, and the CAD tool to be changed by this operation is changed to the keyboard 102, mouse 104, etc. Specify with the input device. If “toolJ” is instructed as shown in FIG. 34, the setting sub-window 1305 is hidden, and as shown in FIG. 35, the text area in the “VHDLSimulation tool” line on the CAD tool selection panel 1301 "toolJ" is displayed. In addition, also when changing a CAD tool with respect to another process, a change process is realizable by the same process.
[0219]
After the selection of the CAD tool is completed, the change contents are updated, and the change operation is ended by pointing the [OK] button 1303 at the lower right of the CAD tool selection panel 1301. After the [OK] button 1303 is designated, the CAD tool assignment information 802 changing process and the process state re-inspection process are executed.
[0220]
On the contrary, in order to ignore the changed contents and end the changing operation, the [Cancel] button 1304 at the lower right of the CAD tool selection panel 1301 is instructed. After the [Cancel] button 1304 is instructed, the panel is not displayed and the original CAD tool is displayed in the text area.
[0221]
Then, after the CAD tool selection process, the CAD tool allocation information 802 is changed. However, in the CAD tool selection process, if the CAD tool is not changed at all, this process is not performed.
[0222]
FIG. 36 is a diagram showing an outline of the flow of processing related to CAD tool selection processing and CAD tool allocation information 802 change processing.
[0223]
The CAD tool assignment information 802 stored in the hard disk device 105 is as shown in the upper left of FIG. With this CAD tool assignment information 802, it is possible to easily grasp which process activates which CAD tool. Therefore, the CAD tool information change process is a process of changing the CAD tool allocation information 802 based on the CAD tool change by the CAD tool change process described above.
[0224]
In FIG. 36, CAD tool allocation information 802 is like a table showing the relationship between processes and CAD tools. The upper diagram shows the state before the change, and the lower diagram shows the state after the change. Further, here, for convenience, processes constituting the process related diagram are expressed by alphabetic names such as process A, process B,.
[0225]
For example, when the CAD tool in the process B is changed from “bbb” to “BBB” by the CAD tool selection process described above, the data regarding the process and the CAD tool output at the end of the CAD tool selection process are shown in FIG. As shown in FIG. 5, the relationship of “process B = bbb” is changed to “process B = BBB”. Then, the change result is written in the CAD tool assignment information 802. As shown in FIG. 36, the CAD tool assignment information 802 is changed from the upper figure to the lower figure.
[0226]
In addition, in the process in which the CAD tool is changed by the CAD tool selection process described above, if the data required in the next process is not generated, the process state after the next process changes. Therefore, when the CAD tool in the process is changed, it is necessary to execute the state inspection process of each process again. Hereinafter, the state inspection process will be described in detail with reference to FIG.
[0227]
FIG. 37 is a diagram showing the state inspection process after the CAD tool selection process.
[0228]
First, in the state in the upper left of FIG. Here, the process 3 is in an executable state, and the process 21, that is, the data A generated by the CAD tool A is an executable condition for the process 3.
[0229]
Now, when the CAD tool activated in the step 21 is changed from the CAD tool A to the CAD tool B by the CAD tool selection process described above, the state inspection is performed again in order from the step 1 for each step. If the CAD tool B activated in the step 21 has not generated the data A, the executable condition of the step 3 cannot be satisfied, so that the step 3 becomes inexecutable.
[0230]
Then, the flow of processing relating to the selection and change of the CAD tool corresponding to each step will be described in detail below using the flowchart of FIG.
[0231]
FIG. 38 is a flowchart of processing relating to selection and change of a CAD tool.
[0232]
In step S231, a tool change instruction is received from the designer. In step S232, a CAD tool selection panel 1301 is displayed. In step S233, the main panel 901 is masked. In step S234, it is determined whether or not there is a CAD tool that has already been set. If there is a CAD tool that has already been set, an existing CAD tool is acquired in step S235. A default CAD tool is acquired via the “management function 310”, and the process advances to step S237 to display the acquired CAD tool.
[0233]
Then, in step S238, it is determined what kind of instruction has been given, and if a CAD tool change is instructed, the process proceeds to step S239 to select the CAD tool to be changed on the CAD tool selection panel 1301. In step S240, the CAD tool name selected in the text area is displayed. Then, the process returns to the instruction waiting state in step S238.
[0234]
If the [OK] button 1303 is selected in step S238, the process advances to step S243, the CAD tool setting information is confirmed, and the CAD tool allocation information 802 is updated. Next, in step S244, it is confirmed whether or not there is an existing CAD tool. If there is, a backup process is performed, and the process proceeds to step S246. If not, the process proceeds to step S246. In step S246, the updated CAD tool assignment information 802 is stored in the hard disk device 105. In step S247, the main panel 901 is unmasked, and in step S246, the CAD tool selection panel 1301 is hidden. .
[0235]
If the [Cancel] button 1304 is selected in step S238, the process proceeds to step S241. In step S241, the mask of the main panel 901 is released, and in step S242, the CAD tool selection panel 1301 is hidden. . In other words, the CAD tool that was being set is discarded.
[0236]
Thus, according to the present embodiment, the setting of the CAD tool in each process can be performed very easily.
[0237]
Also, by displaying the main flow and the subflow separately, the designer can easily identify both.
[0238]
In addition, since a desired one can be selected from among a plurality of displayed candidates, the selection process becomes efficient.
[0239]
In addition, since the process state after the change of the CAD tool is immediately verified, the designer can easily identify the state change of each process.
[0240]
Further, since the panel is masked during the selection process, malfunction can be prevented.
[0241]
(Fifth embodiment)
An ASIC (referred to as a target in this embodiment) used in the processing in the above-described process can be selected from candidates already prepared in the hard disk device 105. Hereinafter, the setting process of information related to the target, so-called target information 803, will be described in detail.
[0242]
First, when setting the target information 803, a target information setting panel 1501 as shown in FIG. 39 is displayed according to an instruction from an input device such as the keyboard 102 or the mouse 104. In the present embodiment, the process is started when the [Target] button of the button group 904 on the main panel 901 is selected or when target information is not set when a new project is registered.
[0243]
FIG. 39 is a diagram showing a target information setting panel 1501 displayed so as to be superimposed on the main panel 901.
[0244]
In FIG. 39, an upper area 1502 of the target information setting panel 1501 is a vendor name setting area, and a blank area on the right side is a text area, which displays the vendor name selected in a setting subwindow 1508 described later. . A triangular button 1503 to the right of “Vendor:” is a sub-window display button. When this button is designated by an input device such as the mouse 104, the button 1503 is displayed in the text area on the right side of the button. A setting sub window 1508 displaying a plurality of vendor name candidates to be displayed as shown in FIG. 40 is displayed at an arbitrary position on the target information setting panel 1501.
[0245]
Reference numeral 1504 denotes a detailed item display area for displaying detailed items of five targets “Vendor”, “SeriesType”, “SeriesName”, “Package”, and “PinNum”, and 1505 is displayed in an area 1504. This is a candidate display area for displaying detailed item candidates.
[0246]
Reference numeral 1506 is an [OK] button for confirming the selection, and 1507 is a [Cancel] button for instructing cancellation.
[0247]
A target information setting panel 1501 in FIG. 39 is a panel when target information has not yet been set. The target to be used is determined by setting the following elements from this state. There are five target detailed items of “Vendor”, “SeriesType”, “SeriesName”, “Package”, and “PinNum” in the area 1504, and these settings are made in this order. The setting procedure is shown below.
[0248]
The label “Vendor” in the area 1502 indicates the ASIC vendor. When a sub window display button 1503 on the right side of “Vendor” is instructed by an input device such as the mouse 104, a setting sub window 1508 displaying a plurality of ASIC vendors as shown in FIG. 40 is displayed as a target information setting panel 1501. Display above.
[0249]
Here, when “Company F” is designated as shown in FIG. 40, the setting sub-window 1508 is not displayed, and the text area on the right side of the area 1502 on the target information setting panel 1501 is displayed as shown in FIG. , "Company F" is displayed.
[0250]
When the vendor name is confirmed, the detailed item “SeriesType” as the next confirmed item is displayed as a candidate in the candidate display area 1505 as shown in FIG. When the designer designates a desired candidate with an input device such as the mouse 104, “SeriesType” is confirmed, and the detailed item is written in the detailed item display area 1504 as shown in FIG. Displays the detailed items of “SeriesName” which is the next fixed item of “SeriesType”. At that time, the data of “SeriesType” in the hard disk 105 is read and information including “SeriesName” and below is secured on the data storage device 110 so that it can be freely extracted. Note that reading this information is not limited to the determination of “SeriesType”. When “SeriesType” is determined by the same method, the elements “Package” and “PinNum” are displayed in the candidate display area 1505 as shown in FIG. Then, when all items are confirmed, the state becomes as shown in FIG.
[0251]
After the confirmed content is updated as the target information 803, the [OK] button 1506 is instructed with the mouse 104 or the like in order to end. On the contrary, in order to cancel the set detail item and end, the [Cancel] button 1507 is instructed with the mouse 104 or the like. The saving of the target information 803 in the hard disk device 105 will be described later.
[0252]
Also, processing from the case where target information 803 has already been determined as shown in FIG. 44 for the target information setting panel 1501 in the initial state as shown in FIG. 39 will be described.
[0253]
Normally, in the state where the target information 803 as shown in FIG. 44 is confirmed, “Package” and “PinNum” can be changed by operating the candidate display area 1505 on the right side of the panel in the same manner as before.
[0254]
Also, when changing the vendor name from the state of the target information setting panel 1501 in FIG. 44, the sub window display button 1503 on the right side of the “Vendor:” label in the area 1502 is designated using an input device such as the mouse 104. The subsequent operations up to the confirmation are the same as described above. After the vendor name is determined, other items that have been set up to that point are initialized, and the determination proceeds from the panel state as shown in FIG.
[0255]
When “-UP-” in the candidate display area 1505 on the right side of the panel is selected from the state of the target information setting panel 1501 in FIG. 44, the fixed display of the “Package” and “PinNum” items is initialized, and one is displayed. The previous detailed item “SeriesName” is displayed in the candidate display area 1505. The state of the panel is as shown in FIG.
[0256]
If “-UP-” is further selected, the confirmation operation is further returned by one, and if any candidate of “SeriesName” is selected, the confirmation operation is advanced by one and the state shown in FIG. 43 is obtained. . When the “-UP-” element is determined when “SeriesType” is determined, the target information setting panel 1501 returns to the initial state.
[0257]
In this way, the existing setting contents can be changed.
[0258]
When the target information 803 is set or changed, the target information 803 set or changed is stored in the hard disk device 105. The target information 803 here is a generic name of values for determining a target, and refers to the above-described five items (from “Vendor” to “PinNum”). The target information 803 also updates the contents of the setting change information 701 shown in the outline of the setting change in FIG.
[0259]
FIG. 45 is a diagram showing an outline of the flow of processing related to selection processing and storage of target information 803.
[0260]
New target information is determined by the detailed item setting process for the target information 803 before change in the upper left of FIG. Then, the new target information is written in the hard disk device 105 in such a manner that the current target information is changed to the confirmed new target information.
[0261]
By confirming or changing the target information 803, the process state must be re-inspected. This is because the target information 803 may be included in the execution conditions for determining the process state. For example, when a chip A is used, data A is necessary as an execution condition, and when a chip B is used, data B can be an execution condition. Below, the example is demonstrated.
[0262]
FIG. 46 is a diagram showing the state inspection process after the target information 803 setting process.
[0263]
In the upper left process state of FIG. 46, the CAD tool activated in process 21 is CAD tool A. In step 3, since the data A generated by the CAD tool A in step 21 is an executable condition, if the data A is generated in step 21, step 3 is in an executable state.
[0264]
Here, by changing the setting of the target information 803 as shown in FIG. 46, the execution condition of the step 3 changes from the data A to the data B. If the state inspection is performed again from the step 1 after this change processing, the data B is not generated in the step 21, and therefore the condition of the step 3 cannot be satisfied. Therefore, the process 3 changes to an inexecutable state like the process of the upper right of FIG.
[0265]
However, since the change in the process state varies depending on the execution condition of the process, it is not always as described above. That is, there may be no change in the process state, or there may be a change in two or more process states.
[0266]
The flow of the target information 803 setting process using the target information setting panel 1501 will be described in detail below with reference to the flowcharts of FIGS. 47, 48, and 49.
[0267]
FIG. 47 is a flowchart of target information 803 setting processing using the target information setting panel 1501.
[0268]
In step S251, the main panel 901 is masked. In step S252, the target information setting panel 1501 is displayed. In step S253, it is determined whether data already exists on the target information setting panel 1501. If data exists, the process proceeds to step S254. If the change setting is made and the data does not exist, the process proceeds to step S255 to perform the initial setting.
[0269]
Next, the flow of the initial setting process in step S255 will be described in more detail using the flowchart of FIG.
[0270]
The target information 803 is always set from the upper level to the lower level. That is, if the upper data is determined, the lower data candidates can be determined. The same applies to the change setting in step S254.
[0271]
In step S261, it is determined what instruction has been received. If an ASIC vendor name is specified, the [OK] button 1506 is masked in step S262, the detailed item display area 1504 is initialized in step S263, and the specified vendor is specified in step S264. Recognize names. Next, in step S265, through the “environmental data management function 310”, it is determined whether or not there is a designated vendor in the vendor data file 504 in which the vendor name to be used is registered. In step S266, the vendor information is acquired. In step S267, the vendor name is displayed. In step S268, a list of detailed items is displayed in the candidate display area 1505. When this process ends, the process returns to the instruction waiting state in step S261.
[0272]
If a detailed item (in this case, information other than the ASIC vendor name) is set in step S261 after the vendor name is specified, the item selected on the list in step S270 is set. Judgment processing is performed. Here, in the candidate display area 1505, when “UP”, which is a special character that has the meaning of returning the setting operation to one higher level, is designated, the process proceeds to step S276, and the next item list is displayed again in the candidate display area 1505. In step S277, the text area corresponding to the detailed item display area 1504 is initialized, and the process returns to step S261. If any other list item is designated, the process advances to step S271 to display the designated item in the corresponding text area in the detailed item display area 1504. In step S273, the next item is displayed in the candidate display area 1505. Redisplay the item list. Further, in step S274, it is determined whether or not the designated detailed item is the final setting item. If the designated detailed item is the final setting item, it is assumed in step S275 that all the detailed items have been confirmed, and the [OK] button 1506 is clicked. The mask is released and the process returns to step S261. If there are remaining detailed items to be set, the process directly returns to step S261.
[0273]
If the [OK] button 1506 is selected in step S261 after all the detailed items have been set, the process proceeds to step S278, where the set target information 803 is determined. In step S279, the previous information is displayed. Check if the target information of exists. If it exists, a backup process is performed in step S280, and the process proceeds to step S281. If not, the process proceeds to step S281. In step S281, the set target information 803 is stored in the hard disk device 105. In step S282, the target information setting panel 1501 is hidden. In step S283, the mask of the main panel 901 is released, and the process is performed. finish.
[0274]
If the [Cancel] button 1507 is selected in step S261 after all the detailed items have been set, the process proceeds to step S284, the target information setting panel 1501 is hidden, and in step S285. The mask of the main panel 901 is released, and the process ends. That is, the setting contents are invalidated and the setting process is terminated.
[0275]
Next, the flow of change setting processing in step S254 will be described in more detail using the flowchart of FIG.
[0276]
This is processing when target information 803 that has already been set exists.
[0277]
First, it is necessary to read the set target information 803 as compared with the case of the initial setting process. In step S291, the target information 803 is read. In step S292, the result of reading is determined. If the reading fails, the process proceeds to the flow indicated by (1) in FIG. If the reading is successful, in step S293, the vendor name in the read target information 803 is displayed in the vendor name text area 1502, and the detailed item is displayed in the detailed item display area 1504. In step S294, it is determined what instruction has been received.
[0278]
If an ASIC vendor name instruction is given, the process proceeds to the flow indicated by (2) in FIG. 48. If the [OK] button 1506 is selected, (4) in FIG. If the [Cancel] button 1507 is selected, the flow moves to the flow indicated by (5) in FIG.
[0279]
If the detailed item is set in step S294, a determination process is performed for the item selected on the list in step S295. In the candidate display area 1505, when “UP”, which is a special character having the meaning of returning the setting operation to one higher level, is designated, the process proceeds to step S297, the [OK] button 1506 is masked, and the candidate display is displayed in step S298. In the area 1505, the next item list is displayed again. In step S299, the corresponding text area in the detailed item display area 1504 is initialized, and the flow proceeds to the flow indicated by (2) in FIG. If any other list item is designated in the candidate display area 1505, the process proceeds to step S296, where the designated item is displayed in the text area of the detailed item display area 1504. In (2) of FIG. Move to the indicated flow.
[0280]
Thus, according to this embodiment, setting of target information can be performed very easily.
[0281]
In addition, since the vendor name and detailed information can be selected in a hierarchy, the designer can select information step by step.
[0282]
In addition, since a desired one can be selected from among a plurality of displayed candidates, the selection process becomes efficient.
[0283]
Further, since the selection hierarchy can be returned to the upper level, correction can be easily made when the selection is wrong.
[0284]
Further, since the process state after setting the target information is immediately verified, the designer can easily identify the state change of each process.
[0285]
Further, since the panel is masked during the selection process, malfunction can be prevented.
[0286]
(Sixth embodiment)
Next, the sixth embodiment will be specifically described below by taking the execution of steps 1 and 21 in FIG. 31 as an example.
[0287]
FIG. 31 is an example of a process related diagram in the region 902.
[0288]
In FIG. 31, all processes are surrounded by a thick line as being executable.
[0289]
Here, it is assumed that the pre-process of the process 21 is the process 1 and the process 22, and the executable condition of the process 21 is data generated in the process 1. Then, when the process 22 is executed, the state of the process 21 is not changed, so that the process related diagram does not change. This is the correct state.
[0290]
However, if data is no longer generated in the execution of step 1, the state of the steps after step 21 will not be verified if the verification after step 21 is not performed even though step 21 becomes inexecutable. As a result, the state remains in an executable state, and a contradictory state occurs.
[0291]
Therefore, in order to solve this problem, it is necessary to sequentially verify the steps after the executed step (see FIG. 16 for the verification in such a case).
[0292]
When such verification is performed, if data of different versions is generated by execution of step 1 whose version has been changed by a plurality of execution processes, step 21 in which the data from step 1 is an executable condition is in an executable state However, since the data generated in step 21 is generated by the previous version of data generated in step 1, the data generated in step 21 and the current execution process from step 1 There is no derivation relationship (to be described in detail later) with the output data, and all the processes after the process 3 are in an inexecutable state.
[0293]
Incidentally, when data is not generated in the execution of the process 1, since the process 21 also does not generate data, all processes after the process 21 change to an inexecutable state. Further, when step 22 is executed, there is no influence on step 21, so even if the steps after step 21 are verified, all the steps remain in an executable state.
[0294]
Here, the “derivative relationship” described above will be briefly described. In the design management apparatus 101, the derivation management function 300-2 of the “data management function 201” manages the “derivation relationship” of data.
[0295]
In other words, this is to manage which data is generated. That is, in the case of the above example, the current data of the step 21 is not generated based on the data generated in the step 1 after the version change, and therefore execution is not permitted.
[0296]
In the present embodiment, this “derivative relationship” is also one of the executable conditions.
[0297]
Such “derivation relationship” of data changes depending on the version change due to the process of the process, and the flow of the process has already been described in detail as the version management process in the flowcharts of FIGS. 25 and 26. So please refer to it.
[0298]
Here, with reference to the schematic diagram of FIG. 32, the change in the “derivation relationship” of data when the CAD tool selection process described in the fourth embodiment is performed will be described in detail.
[0299]
First, in FIG. 32, based on the version 1 data 1 (data 1v1-1201) generated in step 1, the CAD tool B generates version vB1 data A (data AvB1-1204) in step 21. In such a case, a “derivative relationship” occurs between the two data.
[0300]
In this state, when the CAD tool in the process 21 is changed from the CAD tool B to the CAD tool A by the CAD tool selection process, the data A does not exist in the CAD tool A in the process 21 at the time of the change. Therefore, when the version of the data 1 output by executing the process 1 changes from the version v1 to the version v3, the CAD tool A uses the data of the version vA1 based on the data 1 of the version v3 (data 1v3-1202). A (data AvA1-1203) is generated. As a result, a “derivative relationship” occurs between the data 1 of the version v3 (data 1v3-1202) and the data A of the version vA1 (data AvA1-1203).
[0301]
Further, the CAD tool in step 21 is returned from CAD tool A to CAD tool B. At that time, the data of the process 1 is the data 1 of the version v3 (data 1v3-1202), and the data of the process 21 is the data A of the version vB1 (data AvB1-1204). Since there is no “derivative relationship” between them, CAD tool B again uses version vB2 data A (data AvB2-1205) based on version v3 data 1 (data 1v3-1202). You need to create and create a “derivative relationship”.
[0302]
In this process flow, the process state changes to the process state in the upper right of FIG. 37 by the CAD tool selection process. Since the change in the process state differs depending on the execution condition of the process, it does not necessarily become as described above. That is, there may be no change in the process state, or there may be a change in two or more process states.
[0303]
For example, in the case where all processes are executable in FIG. 37, when the CAD tool in process 2 is changed from CAD tool A to CAD tool B as described above, CAD tool B does not hold data A. If there is no derivation relationship with data 1, step 3 is in an inexecutable state. At the same time, all the subsequent processes are in an inexecutable state as a result of the state inspection process described above.
[0304]
Next, a method for managing information (hereinafter referred to as derivation relationship information) indicating the “derivation relationship” between data will be described in more detail with reference to FIGS. In FIGS. 71 to 75, a model in which the three steps of step 1, step 2, and step 3 are sequentially processed in this order is considered.
[0305]
71 to 74 are diagrams showing a method of managing derivation relationship information between data.
[0306]
In FIG. 71, it is assumed that program A is assigned to process 1 and program B is assigned to process 2. Data 1.01 is generated by executing the process 1 using the program A. In addition, data 2.01 is generated by executing the process of step 2 using program B on the data 1.01 generated in step 1. At this time, a “derivative relationship” is established between data 1.01 and data 2.01. In the present embodiment, this derivation relationship information is stored in the data storage device 110 for each process.
[0307]
First, in the case of step 1, since there is no derivation source data,
NoData → Program A: Data 1.01
Recognize by the relationship. In the case of process 2, data 1.01 is used as the derivation source data.
Program A: Data 1.01 → Program B: Data 2.01
Recognize by the relationship. The expression shown here is merely an easy-to-understand description, and does not indicate the data configuration in the data storage device 110. Here, only the CAD tool (program) and the data generated by its execution are recognized and its “derivative relationship” is expressed. Of course, other conditions may be taken into account. .
[0308]
In the present embodiment, the presence / absence of the “derivative relationship” is verified from the relationship between the derivation relationship information and the version information of the current data (latest data) generated in each process. For example, in FIG. 71, it can be said that there is a “derivative relationship” between the data 2.01 which is the current data of step 2 and the data 1.01 which is the current data of step 1.
[0309]
Next, from the state of FIG. 71, as shown in FIG. 72, when the program assigned to step 2 is changed from program B to program C, step 2 has two data flows. One is a flow in which data is updated by the program B, and the other is a flow in which data is updated by the program C. After the program assigned to step 2 is changed, when step 2 is executed by program C, data 2.01 is generated as shown in FIG. 72, and this data becomes current data. Therefore, the derivation relationship information is
Program A: Data 1.01 → Program C: Data 2.01
Recognized by the relationship. Although the program that generated the data is different, the derivation source data is the same, so the version number 2.01 attached to the data is the same as in the case of the program B.
[0310]
Although the data flow of the program B and the program C is shown here, of course, the data flow is not limited to two and may be more than that.
[0311]
Next, from the state of FIG. 72, as shown in FIG. 73, data is regenerated in each step again in the order of step 1 and step 2. The version of each data is increased by 1 (hereinafter referred to as version upgrade). That is, as shown in FIG. 73, version 1 is upgraded to data 1.02 in step 1, and version 2.0 is upgraded to data 2.02 in step 2. At this time, the derivation relation information of data 2.02, which is the current data of process 2, is
Program A: Data 1.02 → Program C: Data 2.02
Recognized by the relationship. As can be seen from this relationship, it can be said that there is a “derivative relationship” between the data 2.02 which is the current data of the process 2 and the data 1.02 which is the current data of the process 1.
[0312]
Finally, from the state of FIG. 73, the CAD tool executed in step 2 is changed from program C to program B again. Then, although the current data of the process 1 remains as data 1.02, the current data of the process 2 returns to the data flow of the program B due to the change of the CAD tool and becomes the data 2.01. At this time, the derivation relationship information of data 2.01, which is the current data of process 2, is
Program A: Data 1.01 → Program B: Data 2.01
Therefore, it can be said that there is no “derivative relationship” with the data 1.02 which is the current data of the process 1.
[0313]
Therefore, in order to establish a derivation relationship with the current data in step 1, step 2 must be re-executed. As shown in FIG. 74, the re-execution of step 2 changes the current data of step 2 to data 2.02, so a “derivative relationship” is established with data 1.02 which is the current data of step 1. To do.
[0314]
Then, in connection with this series of process steps, the transition of the feasible state of each step, step 2, and step 3 will be described in detail below.
[0315]
FIG. 75 is a diagram showing a change in process state and a change in data version information.
[0316]
In FIG. 75, it is assumed that the executable condition of step 2 is the generation of data 1.xx in step 1, and the executable condition of step 3 is the generation of data 2.xx in step 2. In addition, as an initial state, a state where data is not yet generated in each process is considered.
[0317]
Now, the “derivation relationship” and the transition of the process state in the following eight processes will be described.
(1) Step 1 is executed to generate data 1.xx (hereinafter, it is assumed that the execution of the step always ends normally and necessary data is generated).
(2) Step 2 is executed.
(3) The tool assigned to step 2 is changed from program B to program C.
(4) Perform step 2.
(5) Perform step 1.
(6) Perform step 2.
(7) The tool assigned to step 2 is changed from program C to program B.
(8) Perform step 2.
[0318]
Here, first, only the process 1 is in an executable state, but the process 2 is also changed into an executable state by (1). Next, according to (2), step 3 is also changed to an executable state. Next, due to (3), since there is no “derivative relationship” between the current data of step 1 and the current data of step 2, step 3 becomes inexecutable. Then, because of (4), a “derivative relationship” is established between the current data of step 1 and the current data of step 2, so that step 3 becomes executable again.
[0319]
Further, because of (5), there is no “derivative relationship” between the current data of step 1 and the current data of step 2, so that step 3 becomes inexecutable again. Then, because of (6), a “derivative relationship” is established between the current data of step 1 and the current data of step 2, so that step 3 becomes executable again. Next, due to (7), since there is no “derivative relationship” between the current data in step 1 and the current data in step 2, step 3 becomes inexecutable again. Finally, because of (8), a “derivative relationship” is established between the current data in step 1 and the current data in step 2, so that step 3 becomes executable again.
[0320]
Thus, according to the present embodiment, since the difference in data version is also taken into consideration as an executable condition, more accurate verification can be performed when verifying the process state.
[0321]
(Seventh embodiment)
In order to perform the change process of the input / output buffer information in the present embodiment, a process of generating HDL (hardware description language) including the input / output buffer information in the process group executed by the design management program 112; It is essential to include two steps of changing the input / output buffer information in the generated HDL. Further, the input / output buffer information in this embodiment is used in an ASIC including an FPGA, and is the same as the input / output buffer information 801 in FIG.
[0322]
The input / output buffer information changing process will be described in detail below with reference to FIGS.
[0323]
FIG. 50 shows the work contents of process 1 and process 3 in the process related diagram in the process group display area 902 displayed in the work content display area 903.
[0324]
In the process related diagram of FIG. 50, first, HDL is generated in process 1, and then in step 3, the input / output buffer information in the HDL generated in process 1 is changed, and then the HDL is generated. An example of converting data into different data is shown. It is also possible to change the input / output buffer information again using the different data converted in step 3.
[0325]
Here, the contents of work in step 1 and step 3 in FIG. 50 will be described in detail.
[0326]
First, in the HDL generation process in step 1, data A, which is an HDL file including input / output buffer information, is generated according to an input instruction from the designer. This data A is used in step 3 after step 21. In this step 1, the data A may be generated by any method. For example, a design tool commercially available from an electric CAD vendor or a text editor may be used. In addition, the HDL may be generated not only in the process 1 but in other processes, but the HDL generation process must be performed before the input / output buffer information change process. This is because HDL includes input / output buffer information.
[0327]
Next, in step 3, based on the data A generated in step 1, the input / output buffer information in the data A is changed according to the instructions of the designer, and then used in the steps after step 3. Two operations are performed to convert data A to data B as appropriate.
[0328]
It should be noted that the work content of step 3 presented here is merely an example for explanation, and there may be processing other than the change of input / output buffer information and data conversion, and the processing order is not limited. In the present embodiment, in order to simplify the description, the processes other than the change of the input / output buffer information and the data conversion are not performed, and both processes are performed without changing the order.
[0329]
Here, the two work contents in the process 3 will be described in more detail.
[0330]
First, an input / output buffer information setting panel 2001 as shown in FIG. 51 is displayed on the main panel 901 on the CRT display 103 in accordance with an instruction from an input device such as the keyboard 102 or the mouse 104, and this input / output buffer information is displayed. On the setting panel 2001, the input / output buffer information is changed.
[0331]
FIG. 51 is a diagram showing an input / output buffer information setting panel 2001 displayed on the main panel 901.
[0332]
By the button operation on the input / output buffer information setting panel 2001, it is possible to switch from the default mode of the initial state to the three operation modes of the item setting mode, the group division mode, and the pin movement mode.
[0333]
In FIG. 51, an item setting mode is set by instructing a setting button 2002 using an input device such as a keyboard 102 or a mouse 104. Further, when the division button 2003 is designated, the group division mode is set, and when the movement button 2004 is designated, the pin movement mode is set. When an end button 2005 is instructed, the input / output buffer information setting panel 2001 is closed and the processing is ended.
[0334]
In FIG. 51, 2006 is a column for displaying group names, 2007 is a column for displaying input / output buffer names, and 2008 is a column for displaying pin information registered in each group. is there.
[0335]
Further, between the column 2006 and the column 2007, there are a column for displaying drive information and a column for displaying power supply voltage information. The drive information here is the amount of current that can be passed through the input / output buffer, and the power supply voltage information is the voltage of the power supply that supplies energy to the input / output buffer. The input / output buffer information in this embodiment includes all of these drive information, power supply voltage information, and input / output buffer names. (Note that temperature information may be included.)
[0336]
Note that 2009 is a line for displaying the related information of the group PG1, followed by the lines of the group PG2 and the group PG3. As described above, in FIG. 51, the pins are grouped. In this embodiment, the pin grouping is performed by the process management apparatus 101 of the input, output, input / output, etc. It is based on the difference of types. (You may judge by the name of the pin.)
[0337]
When the designer gives an instruction to execute step 3 using an input device such as the mouse 104, an input / output buffer information setting panel 2001 is displayed. On the input / output buffer information setting panel 2001, detailed information read from the data A, such as drive information, power supply voltage information, and input / output buffer names, is displayed for each group.
[0338]
In FIG. 51, in the group PG1, pin information is set in advance such as p1, p2, p3, etc., but drive information, power supply voltage information, and input / output buffer names are not set. This is because there was no existing setting information, or even if there was existing setting information, it was inconsistent with the grouped data. That is, conversely, if the existing setting information exists and matches with the grouped data, the details from the drive information on the input / output buffer information setting panel 2001 to the input / output buffer name column are detailed. Information will be displayed.
[0339]
Also, when there are a large number of pins, such as PG1 registration pins, only the displayable area is displayed. Of course, it is possible to enlarge the display area and display all the registered pins, but here, up to three are displayed in consideration of the appearance on the display.
[0340]
In FIG. 51, there are two columns of items for narrowing candidates for input / output buffer names between the group name column 2006 and the pin information column 2008, and the input / output buffer names are set. There is one column for this, and there are three columns in total, but of course the number of columns is not limited to three. There are two main methods for setting input / output buffer information as follows. One is a method of narrowing down input / output buffer name candidates by specifying drive information and power supply voltage information. The other is a method of directly narrowing down input / output buffer names without narrowing down. It is a method of setting.
[0341]
Now, setting of input / output buffer information by the former method will be described.
[0342]
First, when the designer designates the setting button 2002 at the top of the input / output buffer information setting panel 2001 using an input device such as the mouse 104, the item setting mode is set, and items can be set. Here, as shown in FIG. 52, when an area 2010 that overlaps a column corresponding to a target group (here, PG2) and a setting item (here, drive information) is designated by an input device such as a mouse 104 or the like. As shown in FIG. 53, a sub window 2011 displaying a list of element elements is displayed on the input / output buffer information setting panel 2001. Here, when the designer instructs to select a desired element from among them, the sub-window 2011 is closed, and the selected element is displayed in the area 2010.
[0343]
At this time, processing performed by the arithmetic processing unit 106 inside the apparatus will be described as follows.
[0344]
First, the arithmetic processing unit 106 writes the drive information instructed to be selected into the data storage device 110 that secures the group related information. When it is determined that the input / output buffer name candidates are sufficiently narrowed down, the designer is instructed to set the input / output buffer name next, and when it is determined that the narrowing down is insufficient. Instructs the designer to set the power supply voltage information, and when the designer sets the power supply voltage information, he further refines the candidates and finally sets the input / output buffer name to the designer. Instruct. A configuration may be adopted in which the designer himself / herself determines whether or not the candidate input / output buffer names are sufficiently narrowed down and makes further settings.
[0345]
The setting of the input / output buffer name is the same as the setting of the drive information and the power supply voltage information, and the sub-window 2011 is opened and an instruction is made with an input device such as the mouse 104. Here, when displaying the sub-window 2011, since the candidates for the input / output buffer names are narrowed down in advance by setting the drive information and the power supply voltage information, only the narrowed elements are displayed.
[0346]
Next, setting of input / output buffer information by the latter method will be described.
[0347]
In this case, since the input / output buffer name is set immediately without setting the drive information and the power supply voltage information, the candidates are not narrowed down, and all candidates of the input / output buffer name are displayed when the sub-window 2011 is displayed. Will be displayed. However, this setting method is effective when the number of input / output buffer name elements is small.
[0348]
Note that the drive information, power supply voltage information, and input / output buffer name displayed in the sub window 2011 correspond to the target information set in the fifth embodiment. That is, it can be said that the input / output buffer information is narrowed down in advance by setting the target information in the fifth embodiment.
[0349]
Next, group division processing in the input / output buffer information setting panel 2001 will be described in detail below.
[0350]
First, the group division process is a process of dividing one group displayed on the input / output buffer information setting panel 2001 into a plurality of groups. Originally, it is more efficient to set I / O buffer information for each group, but if there are pins that need to set different I / O buffer information in the same group, , Group division must be done.
[0351]
An example of group division processing will be given below.
[0352]
First, when the designer instructs the division button 2003 using an input device such as the mouse 104, the group division mode is set. Further, when the area where the column displaying the pin information and the group row to be divided are instructed, a sub-window similar to 2011 is displayed, and the instructed is displayed on the sub-window. The pins included in the group are displayed. Therefore, when the designer selects all the pins to be divided and instructs the end button 2005, the subwindow is hidden, and new group data based on the selected pin is stored in the data storage device 110. Is constructed and the original group is split into two. After the group division, one new group row is added on the input / output buffer information setting panel 2001, and the screen is displayed again.
[0353]
For example, assuming that there are ten pins PG1 to p10 in the group PG1 shown in FIG. 51, when the designer instructs the group PG1 to divide the even number pins, the even number pins are excluded from the group PG1 after the division. The group consisting of odd pins p1, p3, .., p9, and the group consisting of even pins p2, p4,. A certain PG1 ′ is given and registered in the data storage device 110, and the division of the group is completed. At this time, if the input / output buffer information is already set in the group PG1, the division including the input / output buffer information is performed, and the input / output buffer information of the group PG1 ′ newly generated after the division of the group is Same setting as group PG1. The input / output buffer information of the group PG1 ′ can be changed according to the setting process described above.
[0354]
Further, as a result of dividing the group, the designer may want to return some of the pins to the original group. In such a case, it is necessary to move the pins between groups. Hereinafter, an example of the pin movement process in the input / output buffer information setting panel 2001 will be described in detail.
[0355]
First, when the designer instructs the movement button 2004 using an input device such as the mouse 104, the pin movement mode is set. Further, when an area where the row of the group to which the pin is moved and the column displaying the pin information intersects is designated, a sub window similar to 2011 is displayed, and other sub windows are displayed on the sub window. All the movable pins of the group are displayed. Then, when the designer instructs to select all the pins to be moved and instructs the end button 2005, the sub-window is hidden, and between the groups in the data storage device 110 based on the selected pins. The pin is moved and the group data is reconstructed. After the pin is moved, on the input / output buffer information setting panel 2001, the pin information to which the selected pin is added is displayed in the pin information display area of the move destination group, and the pin information of the move source group is displayed. In the display area, pin information obtained by deleting the moved pin is displayed.
[0356]
For example, when moving p1 and pp1 of group PG1 and group PG2 to group PG3 shown in FIG. 51, the designer moves the pin information display area (area where ppp is displayed) of group PG3 with mouse 104 or the like. When instructed, a subwindow (not shown) having a pin information candidate similar in form to the subwindow 2011 is displayed. Further, p1 and pp1 are instructed on the subwindow, and the end button 2005 is instructed. The sub window is hidden, the pin information display area of group PG1 is changed to "p2, p3, p4, ...", and the pin information display area of group PG2 is displayed as "pp2, pp3" In addition, the pin information display area of the group PG3 is changed to “p1, pp1, ppp”.
[0357]
When the end button 2005 is instructed after the series of input / output buffer information change processing is completed, the input / output buffer information setting panel 2001 is closed, and at this time, the input / output buffer information is output. In addition, replacement processing of the input / output buffer information of data A and the set input / output buffer information is performed. Then, the data A changed by the replacement result is further converted into data B, and all the operations in step 3 are completed.
[0358]
Then, after the completion of all the operations in the step 3, when the state inspection of the step is performed again from the step 1, the state of the subsequent step can be determined according to the result of the input / output buffer information change process in the step 3. it can.
[0359]
Now, the flow of the input / output buffer information changing process using the input / output buffer information setting panel 2001 will be described in detail below with reference to the flowcharts of FIGS.
[0360]
FIG. 54 is a flowchart of pre-processing for changing input / output buffer information.
[0361]
In step S301, it is determined whether an HDL file exists. When it exists, it progresses to step S302, and when it does not exist, it progresses to step S312 and performs an error process. In the error processing in step S312, data is initialized and an error message is displayed. Next, in step S302, pin information such as the name and type of the pin connected to the highest block of the ASIC is extracted from the HDL file. In step S303, it is determined whether or not the extracted pin information exists. Check. If it exists, the process proceeds to step S304. If it does not exist, the process proceeds to error processing in step S312.
[0362]
Next, in step S304, the input / output buffer information setting panel 2001 is displayed, and in step S305, it is confirmed whether or not design data including the pin information extracted in step S302 exists for the change process. When it exists, it progresses to step S306, and when it does not exist, it progresses to the error process of step S312. Next, in step S306, those design data are read, and the process proceeds to step S307.
[0363]
In step S307, it is determined whether or not previously set information exists. If it exists, the process proceeds to step S310. If not, the process proceeds to step S308, and related information is grouped by pin information. Then, a series of processing is completed. In step S310, it is determined whether or not the previously set information matches the pin information read this time, that is, if they are substantially the same group. If they match, the process proceeds to step S311 and the previously set information is set. Based on the information, the related information is grouped, and a series of processing is completed. If they do not match, the process proceeds to step S308, where the related information is grouped based on the pin information, and the series of processing ends.
[0364]
After the end of this flowchart, the operation is waiting for the designer.
[0365]
FIG. 55 is a flowchart of input / output buffer information change processing following the preprocessing shown in FIG.
[0366]
In step S321, it is determined what instruction has been received. If it is determined that the setting button 2002 has been selected, it is determined in step S322 whether or not the item setting mode has already been entered. If the item setting mode has been entered, the process proceeds to step S323. The mode is canceled and the process returns to step S321. If another mode is selected, the process proceeds to step S324 to determine whether the default mode is the initial state. If it is not the default mode, the selected mode is canceled in step S325, and then the process proceeds to step S326. If it is the default mode, the process proceeds to step S326 as it is. In step S326, an item setting process is performed.
[0367]
If it is determined in step S321 that the division button 2003 has been selected, it is determined in step S327 whether the group division mode has already been entered. If the group division mode has been entered, step S328 is performed. , The mode is canceled, and the process returns to step S321. If another mode is selected, the process proceeds to step S329 to determine whether the default mode is the initial state. If it is not the default mode, the selected mode is canceled in step S330 and then the process proceeds to step S331. If it is the default mode, the process proceeds to step S331 as it is. In step S331, group division processing is performed.
[0368]
If it is determined in step S321 that the move button 2004 has been selected, it is determined in step S332 whether or not the pin movement mode has already been entered. If the pin movement mode has been entered, step S333 is determined. , The mode is canceled, and the process returns to step S321. If another mode is selected, the process proceeds to step S334 to determine whether the default mode is the initial state. If it is not the default mode, the selected mode is canceled in step S335 and then the process proceeds to step S336. If it is the default mode, the process directly proceeds to step S336. In step S336, pin movement processing is performed.
[0369]
If it is determined in step S321 that the end button 2005 has been selected, it is determined in step S337 whether the default mode is in the initial state. If it is not the default mode, the selected mode is canceled in step S338 and then the process proceeds to step S339. If it is the default mode, the process directly proceeds to step S339. In step S339, end processing is performed, and a series of processing ends.
[0370]
Next, the flow of the item setting process in step S326 will be described in more detail using the flowchart of FIG.
[0371]
In step S341, it is determined what instruction has been received. If it is determined that the area of the drive information column has been designated, it is determined in step S342 whether or not a sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S343, and the process returns to step S341. If it is not displayed, the process advances to step S344 to determine whether or not the instructed position is within the group row area. If it is determined that the area is out of the area, the process returns to step S341. If it is determined that the area is out of the area, the process proceeds to step S345 to determine the instructed group. In step S346, a sub window is displayed. In step S348, drive information of the instructed group is displayed on the sub window, and the process returns to step S341.
[0372]
If it is determined in step S341 that the area of the power supply voltage information column has been specified, it is determined in step S349 whether or not a sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S350 and the process returns to step S341. If not, the process proceeds to step S351 to determine whether or not the instructed position is within the group row area. If it is determined that the area is out of the area, the process returns to step S341. If it is determined that the area is out of the area, the process proceeds to step S352 to determine the instructed group. In step S353, a sub window is displayed. In step S354, the power supply voltage information of the instructed group is displayed on the sub window, and the process returns to step S341.
[0373]
If it is determined in step S341 that the input / output buffer name column area has been designated, in step S355, input / output buffer name display processing is performed, and the process returns to step S341.
[0374]
If it is determined in step S341 that an item in the sub-window has been selected, item designation processing is performed in step S356. In step S357, it is determined whether or not the input / output buffer name selection instruction has been completed. If it is determined that the input / output buffer name selection instruction has not ended, the process returns to step S341. Terminate the process.
[0375]
Next, the flow of input / output buffer name display processing in step S355 will be described in more detail using the flowchart of FIG.
[0376]
In step S361, it is determined whether a subwindow has already been displayed. If it is displayed, the sub-window is hidden in step S362, and the process ends. If not displayed, the process proceeds to step S363 to determine whether or not the instructed position is within the group row area. If it is determined that the area is out of the area, the process is terminated. If it is determined that the area is out of the area, the process proceeds to step S364 to determine the instructed group.
[0377]
In step S365, a sub-window is displayed. In step S366, it is determined whether drive information is set. If it is determined that it has been set, in step S367, the input / output buffer names are narrowed down based on the set drive information, and the process proceeds to step S368. On the other hand, if it is determined that it has not been set, the process directly proceeds to step S368. In step S368, it is determined whether power supply voltage information is set. If it is determined that it has been set, in step S369, the input / output buffer names are narrowed down based on the set power supply voltage information, and the process proceeds to step S370. If it is determined that it has not been set, the process proceeds to step S370 as it is. In step S370, the input / output buffer name to be displayed as a candidate is determined, and in step S371, it is displayed on the subwindow.
[0378]
Next, the flow of the item designation process in step S356 will be described in more detail using the flowchart of FIG.
[0379]
In step S381, it is determined what instruction has been received. If it is determined that the sub window is instructed, it is determined in step S382 whether or not an item in the sub window is instructed. If a portion other than the item is instructed, the process returns to step S381, and if an item is instructed, the instructed item is displayed in reverse in step S383, and the process returns to step S381.
[0380]
If it is determined in step S381 that an instruction for confirming the highlighted selection item has been issued, the confirmed selection item is displayed in the designated area on the input / output buffer information setting panel 2001 in step S384. To display. In step S385, the confirmed selection item is registered in the data storage device 110, and the process proceeds to step S386.
[0381]
In step S386, it is determined whether or not the confirmed selection item is an input / output buffer name. If it is determined that the selected item is an input / output buffer name, regardless of the previous narrowing-down process, in step S387, Drive information corresponding to the determined input / output buffer name is set, and in step S388, the corresponding power supply voltage information is set, and the process proceeds to step S391. If it is determined that the name is other than the input / output buffer name, the process advances to step S389 to determine whether the input / output buffer name has been set. If it is determined that it has been set, the input / output buffer name is initialized in step S390, and the process proceeds to step S391. If it is determined that it has not been set, the process proceeds to step S391. In step S391, the sub-window is hidden and the process ends.
[0382]
If it is determined in step S381 that the outside of the sub-window has been instructed, the sub-window is hidden in step S392, and the process ends.
[0383]
Next, the flow of group division processing in step S331 will be described in more detail using the flowchart of FIG.
[0384]
In step S401, it is determined what instruction has been received. If it is determined that the pin information row area has been designated, it is determined in step S402 whether or not a sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S403, and the process returns to step S401. If not displayed, the process proceeds to step S404 to display a subwindow, and in step S405, pin information is displayed on the subwindow, and the process returns to step S401.
[0385]
If it is determined in step S401 that an item in the sub-window has been instructed, it is determined in step S406 whether or not the instructed item is in a selected state. In step S407, the selection state of the instruction item is canceled, and the process returns to step S401. If it is in an unselected state, in step S408, the instruction item is selected, a display change such as inversion is performed, and the process returns to step S401.
[0386]
If it is determined in step S401 that an item outside the sub-window has been designated, it is determined in step S409 whether or not the sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S410 and the process returns to step S401. If it is not displayed, the process directly returns to step S401.
[0387]
If it is determined in step S401 that the end button 2005 has been selected, it is determined in step S411 whether the number of items in the selected state in the sub-window is zero. If the number of items is other than 0, the process proceeds to step S412, where the selected item is divided, and in step S413, the original group is divided based on the divided items. In step S414, a new group is created based on the divided items. In step S415, the group group including the new group is displayed again on the input / output buffer information setting panel 2001. In step S416, the subgroup is displayed. The window is hidden and a series of processing is terminated. If the number of items is 0 in step S411, the process proceeds to step S416 as it is and the subwindow is not displayed.
[0388]
Next, the flow of the pin movement process in step S336 will be described in more detail using the flowchart of FIG.
[0389]
In step S421, it is determined what instruction has been received. If it is determined that the pin information row area has been designated, it is determined in step S422 whether or not a sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S423, and the process returns to step S421. If not displayed, the process proceeds to step S424 to display a sub-window, and in step S425, the pin type of the instruction target group is acquired. In step S426, the same type of pin as the acquired type is extracted from the group other than the instruction target. In step S427, the extracted pin is displayed on the subwindow, and the process returns to step S421.
[0390]
If it is determined in step S421 that an item in the sub-window has been specified, it is determined in step S428 whether or not the specified item is in a selected state. In step S429, the selection state of the instruction item is canceled, and the process returns to step S421. If it is in the unselected state, in step S430, the instruction item is selected, a display change such as inversion is performed, and the process returns to step S421.
[0390]
If it is determined in step S421 that an item outside the sub-window has been designated, it is determined in step S431 whether or not the sub-window has already been displayed. If it is displayed, the sub-window is hidden in step S432, and the process returns to step S421. If it is not displayed, the process directly returns to step S421.
[0392]
If it is determined in step S421 that the end button 2005 has been selected, it is determined in step S433 whether or not the number of selected items in the sub-window is zero. If the number of items is other than 0, the process proceeds to step S434, and the selected item is moved to the instruction target group. In step S435, based on the moved item, the move source group is moved. Sort the pins in the previous group. In step S437, the group group in which the pins have been rearranged is displayed again on the input / output buffer information setting panel 2001. In step S438, the subwindow is hidden, and the series of processing ends. If the number of items is 0 in step S433, the process proceeds to step S438 as it is to hide the subwindow.
[0393]
Next, the flow of the termination process in step S339 will be described in more detail using the flowchart of FIG.
[0394]
In step S441, it is determined whether or not an item has been changed on the input / output buffer information setting panel 2001. If the change has been made, in step S442, an end panel including three buttons such as “save end”, “forced end”, and “cancel” is displayed, and the process proceeds to step S444. If no change is made, an end panel including two buttons such as “forced end” and “cancel” is displayed in step S443, and the process proceeds to step S444.
[0395]
In step S444, it is determined what instruction has been received. If it is determined that the “save end” button has been selected, backup processing is performed in step S445, the end panel is hidden in step S446, and the changed data is saved and updated in step S447. To end the process. If it is determined that the “forced end” button has been selected, the end panel is hidden in step S448 and the process ends. If it is determined that the “cancel” button has been selected, the end panel is hidden in step S449, and the process ends.
[0396]
Thus, according to the present embodiment, setting of input / output buffer information can be performed very easily.
[0397]
In setting the input / output buffer information, the input / output buffer name is determined by narrowing down the drive information and the power supply voltage information, so that the input / output buffer information can be set more efficiently.
[0398]
In addition, pin groups can be changed and divided more efficiently.
[0399]
In addition, changes in the input / output buffer information can be immediately reflected in the process relation diagram.
[0400]
(Eighth embodiment)
In the present embodiment, the design management program 112 performs a plurality of processes in parallel using a plurality of different design data when executing one project. In other words, design data of a plurality of types of patterns is properly used for one specification. In the present embodiment, such processing is referred to as multiple design processing.
[0401]
First, in order to perform this multiple design process, it is necessary to perform a process for setting information relating to a project as a work unit (hereinafter referred to as project information). In this embodiment, a project information setting panel 2101 is displayed on a display device such as a CRT display 103, and project information is set on the project information setting panel 2101.
[0402]
The project information setting panel 2101 is displayed on the CRT display 103 when the designer instructs the [Project] button at the left end of the button group 904 on the main panel 901 shown in FIG. The main panel 901 is displayed so as to overlap.
[0403]
FIG. 62 is a view showing a project information setting panel 2101 displayed on the main panel 901.
[0404]
In FIG. 62, a series of buttons 2102 from [New] to [Lib] at the top of the project information setting panel 2101 is a key for executing processing in the project information setting panel 2101. In the lower part of the left area 2103 of the project information setting panel 2101, a list of project names registered in the data storage device 110 or the like is displayed. A toggle button thereabove is for switching the state of the list display so as to simultaneously display the names of design data related to the multiple design process. Further, in the right area 2104 of the project information setting panel 2101, detailed information of the project selected from the list in the left area 2103 such as design data is displayed. Reference numeral 2105 denotes an [OK] button, and 2106 denotes a [Cancel] button.
[0405]
In the project information setting panel 2101 shown in FIG. 62, project information has not been set yet. Note that the project information setting process is not limited to the unset state as shown in FIG. 62, and can be started from a state in which project information has already been set.
[0406]
For the time being, first, in order to show the flow of processing in an easy-to-understand manner, a case where processing is performed from the initial state as shown in FIG. 62 will be described.
[0407]
In order to set the project information from the state shown in FIG. 62, it is first necessary to input information into five setting items such as the project name using the project information input panel 2107 shown in FIG. The project information input panel 2107 is displayed so as to overlap the project information setting panel 2101 by instructing the [New] button at the left end of the button group 2102 at the top of the project information setting panel 2101.
[0408]
In FIG. 63, there are two buttons under the five setting items, 2108 is an [OK] button, and 2109 is a [Cancel] button.
[0409]
Here, setting items on the project information input panel 2107 shown in FIG. 63 will be described. First, the name of the project is input in the item of “Project:” label. In addition, when inputting the name of the design data, the prefix of the name is input to the item of the “Prefix:” label, and the item of the “Prefix:” label is input to the item of the “Variation:” label. Enter the name of the design data after the prefix. Note that the name of the owner is set in the item of the “Owner:” label, and the type of designer is set in the item of the “Designers:” label.
[0410]
In FIG. 63, “test” is input to the item of “Project:” label as the name of the project, “ae” is input to the item of “Prefix:” label, and “Variation:” is the item of the design data. When “ae_test” is input, “tanaka” is input in the item of the “Owner:” label, the “Top” button of the “Designers:” label is instructed, and further, the “OK” button 2108 is instructed. The setting items of the project information are registered in the data storage device 110 as selection data 601 (see FIG. 6), and the project name “test” is registered in the group management data 505 (see FIG. 5). In the left area 2103 of the project information setting panel 2101, a candidate “test” is displayed in a selected state as shown in FIG. 64.
[0411]
Here, since “test” is selected, detailed information of the project “test” selected in the left area 2103 is displayed in the right area 2104 of the project information setting panel 2101.
[0412]
Next, as shown in FIG. 64, when detailed project information is displayed on the project information setting panel 2101, processing for changing design data of the project will be described.
[0413]
In order to change the design data of the project from the state of FIG. 64, the project information input panel 2107 shown in FIG. 63 is also used. 64, when the “ChgOwn” button in the button group 2102 at the top of the project information setting panel 2101 is instructed by the input device such as the mouse 104, the project information input panel 2107 is selected. Are displayed so as to overlap the main panel 901. The project information input panel 2107 displays the name of the selected project “test” and its detailed information.
[0414]
Here, in the project information input panel 2107, when a name different from the name of the design data of the project in the selected state is input to the item of the “Variation:” label, new design data is confirmed, and the project “ The design data of “test” can be changed.
[0415]
For example, when the design information name is changed from “ae_test” to “ae_test2” in the project information input panel 2107 in the display state of the project information setting panel 2101 as shown in FIG. 64, the right side of the project information setting panel 2101 The value of the item of the “Variation:” label in the area 2104 is changed from “ae_test” to “ae_test2”.
[0416]
When the toggle button at the upper part of the left area 2103 of the project information setting panel 2101 shown in FIG. 64 is designated, the display content of the list display area at the lower part of the left area 2103 changes as shown in FIG. In FIG. 65, the name of the part surrounded by [] in the list corresponds to the name of the design data. If the “Variation” label item becomes “ae_test2” due to the design data change process, the display is as shown in FIG. By providing this toggle button, the designer can easily know which design data the selected project uses.
[0417]
Also, in the left area 2103 of the project information setting panel 2101 shown in FIG. 64, when “test” is selected, the [ChgVar] button in the button group 2102 above the project information setting panel 2101 is the mouse 104 or the like. When multiple design data corresponding to the project “test” are set, a sub window displaying a list of design data candidates is displayed, and the designer displays a list of candidates. Desired design data can be selected.
[0418]
Such a project information setting process makes it possible to implement a multiple design process described later.
[0419]
Hereinafter, the multiple design process in this embodiment will be described. In this multiple design process, a process for switching a plurality of created design data, and a process for changing the display of a process related diagram based on it are performed.
[0420]
First, as shown in the example of the project information setting process, the project “test” has two design data “ae_test” and “ae_test2”. As shown in FIG. When the data “ae_test” is selected, the process-related diagram is in the state shown in the upper diagram of FIG. 67, and when the design data “ae_test2” is selected, the process-related diagram is in the state shown in the lower diagram of FIG. think of.
[0421]
As is apparent from FIG. 67, when the design data is “ae_test”, the process proceeds to steps 41, 42, and 43, and when the design data is “ae_test2”, only the process up to step 1 is processed. It can be seen that is not progressing. What should be noted here is that, in each of the two process-related diagrams, it is possible to create the same data for each process or to create different data.
[0422]
For example, the design data “ae_test” and “ae_test2” are the same in step 1, and data 1 is generated. In step 2 of the design data “ae_test”, tool A generates data 2A from data 1 In contrast, in step 2 of the design data “ae_test2”, the tool B generates data 2B from data 1. In such a case, it can be seen that the design data “ae_test” and “ae_test2” have the same beginning, but the processes in the subsequent steps are different. (Of course, there is no difference in processing in the steps after step 2.)
[0423]
In other words, depending on the design data, it is possible to change the CAD tool corresponding to the process, change the process execution condition, and further change the number of processes.
[0424]
Therefore, if the expected output data exists when executing a certain project, by performing multiple design processing for that project, from how to proceed to the processing content, to the CAD tool to be used, Since the design can be realized by a number of patterns, the expected output data can be obtained more efficiently. Of course, which pattern is used depends on how the designer or the design management program 112 is restricted.
[0425]
As described above, in the present embodiment, processing can be executed by a plurality of different methods for one project. Therefore, the designer determines the optimal method for project execution by judging the processing result. It is possible to obtain an optimum result. Further, at this time, only the design data is changed, and other information set at the beginning does not need to be changed, so that the work efficiency can be improved.
[0426]
Now, the flow of multiple design processing using the project information setting panel 2101 will be described in detail below with reference to the flowcharts of FIGS.
[0427]
FIG. 68 is a flowchart regarding multiple design processing.
[0428]
In step S451, it is determined whether information necessary for design, such as a process group and a CAD tool used therein, has been determined. If it has been confirmed, the process proceeds to step S452, and if it has not been confirmed, the process ends. Next, in step S452, it is determined what instruction has been given. If it is determined that the [Copy] button has been selected, the process advances to step S453 to perform masking processing for other operations on the project information setting panel 2101. In step S454, design data creation processing is performed. In step S455, the mask of other operations on the project information setting panel 2101 is canceled, and the process ends.
[0429]
If it is determined in step S452 that design data selection has been instructed, the process advances to step S456 to perform mask processing for other operations in the project information setting panel 2101. In step S457, design data selection processing is performed. I do. In step S458, masking of other operations on the project information setting panel 2101 is canceled, and the process ends.
[0430]
If it is determined in step S452 that the toggle button has been selected, the process proceeds to step S459, and the name of the design data is displayed in the list display area in the left area 2103 of the project information setting panel 2101 together with the name “Variation”. Determine if it is displayed. If it is determined that it is displayed, the process advances to step S460 to regenerate the project list so that the name “Variation” is removed, and the list is displayed in step S461. If it is determined that the name is not displayed, the process advances to step S462 to regenerate the project list so that the name “Variation” is added, and the list is displayed in step S463.
[0431]
Next, the flow of design data creation processing in step S454 will be described in more detail with reference to the flowchart of FIG.
[0432]
In step S471, the project information input panel 2107 is displayed, and in step S472, it is determined what instruction has been given. If it is determined that the input process for the item has been performed, the process proceeds to step S473, where the number of input characters is confirmed. If the number of input characters is within the default value in the item frame, the process proceeds to step S474, and if it is equal to or greater than the default value, the process proceeds to step S475 to display an error message. In step S474, it is confirmed whether or not existing data with the same data name exists in the item. If there is no existing data, the process proceeds to step S476. If there is, an error message is displayed in step S475. .
[0433]
Next, in step S476, it is confirmed whether or not there is a prefix in the input character string. If there is a prefix, the input character string is registered in step S478, the mask of the [OK] button 2108 is canceled in step S479, and the process returns to step S472. If there is no prefix, step S477 is performed. Then, a message prompting re-input is displayed, and the process returns to step S472.
[0434]
If it is determined in step S472 that the [OK] button 2108 has been selected, the flow advances to step S480 to copy the design data selected in step S457, and in step S481, the copied data is converted to data. Register in the storage device 110 or the like. However, in the design data copying process, up to which design process the design data is copied depends on the design environment and operation. In the present embodiment, the design data in “Step 1”, which is the highest design data, is copied.
[0435]
Next, in step S482, the original design data is rewritten with new design data, and in step S483, the name of the project is displayed together with the name of the new design data in the list display area of the left area 2103 of the project information setting panel 2101. In step S484, the project information input panel 2107 is not displayed, and the series of processing ends.
[0436]
If it is determined in step S472 that the [Cancel] button 2109 has been selected, the process proceeds to step S485, where the contents of the item are initialized, and in step S486, the project information input panel 2107 is hidden, Terminate the process.
[0437]
Next, the flow of design data selection processing in step S457 will be described in more detail using the flowchart of FIG.
[0438]
In step S491, a subwindow displaying a list of the set design data is displayed. This subwindow also includes an [OK] button and a [Cancel] button. Next, in step S494, it is determined what instruction has been given. If it is determined that the selection processing of the items displayed in the list in the sub-window has been performed, the process proceeds to step S495, and the selected item is highlighted. In step S496, it is confirmed whether or not the selected item exists. If it exists, the mask of the [OK] button is canceled in step S497, and the process returns to step S494. In step S498, a message indicating that is displayed, and the process returns to step S494.
[0439]
If it is determined in step S494 that the [OK] button on the sub-window has been selected, the process proceeds to step S499, and first, existing information is stored. Next, in step S500, it is determined whether or not the selected item exists. If it is determined that it exists, the process proceeds to step S501. If it is determined that it does not exist, that fact is displayed in step S505, and the process returns to step S494. In step S501, information on the selected design data is read. In step S502, detailed information is created based on the read information. In step S503, the detailed information is stored. In step S504, the sub-window is hidden, and the series of processing ends.
[0440]
If it is determined in step S494 that the [Cancel] button on the sub-window has been selected, the process proceeds to step S506, the sub-window is hidden, and the series of processing ends.
[0441]
As described above, according to the present embodiment, when a single project is executed, a plurality of processes are performed in parallel using a plurality of different design data. Therefore, the designer compares and contrasts a plurality of design results. Thus, the optimum design method can be easily confirmed.
[0442]
Note that the first to eighth embodiments of the present invention are not limited to a single device, and may be applied to a system including a plurality of devices connected to a network.
[0443]
【The invention's effect】
As described above in detail, according to the present invention, it is possible to consolidate and manage extremely complex design processes of increasingly higher-density and larger-scale designs, especially ASICs, and to achieve a more efficient design. There is an effect that it becomes possible.
[0444]
In addition, there is an effect that it is very easy to set and change the design object that is the basis of the design object and the processing program activated in each process.
[0445]
In addition, each process is displayed with a different color depending on its state, and when the process is executed or a processing program or design object is set or changed, the process color whose state changes is changed accordingly. By displaying, there is an effect that the designer can easily know the state of the process and its change.
[0446]
In addition, there is an effect that it is possible to change information on a design object that is a basis of a design object during design.
[0447]
In addition, there is an effect that a plurality of different design processes can be performed in parallel when designing a design object that is the basis of the design object.
[0448]
In addition, since the above-described effects can be achieved, the efficiency of the work can be significantly improved, so that the burden on the designer can be reduced and design errors can be reduced.
[Brief description of the drawings]
FIG. 1 is a hardware configuration diagram of a design management apparatus.
FIG. 2 is a conceptual diagram of processing by a design management program.
FIG. 3 is a diagram showing main functions of a design management program.
4 is a diagram showing an outline of a design data management function 300. FIG.
FIG. 5 is a diagram showing an outline of an environmental data management function 310;
6 is a diagram showing an outline of a project operation function 320. FIG.
7 is a diagram showing an outline of an activation control function 330. FIG.
8 is a diagram showing an outline of a setting change function 340. FIG.
9 is a diagram showing an outline of a flow control function 350. FIG.
10 is a diagram showing an outline of an information confirmation function 360. FIG.
FIG. 11 is a diagram showing an outline of the flow of design processing.
FIG. 12 is a diagram showing a main panel displayed on a CRT display.
FIG. 13 is a diagram showing a display example when a plurality of processes are displayed on the main panel.
FIG. 14 is a process related diagram used in the first embodiment.
FIG. 15 is a flowchart of process state verification processing;
FIG. 16 is a flowchart of a simplified verification process of a process state.
FIG. 17 is a diagram illustrating a change in process state when process 1 is executed.
FIG. 18 is a diagram showing a change in process state when process 21 is executed.
FIG. 19 is a diagram showing a work schematic diagram when there is one work in step 1;
FIG. 20 is a diagram showing a work schematic diagram in the case where there are three work in step 1;
FIG. 21 is a diagram showing processing for adjusting the number of operations in step 1;
FIG. 22 is a flowchart of in-process work number adjustment processing;
FIG. 23 is a flowchart of an execution process.
FIG. 24 is a flowchart of error processing.
FIG. 25 is a flowchart of pre-processing for version management.
FIG. 26 is a flowchart of post-processing of version management.
FIG. 27 is a flowchart of history management processing;
FIG. 28 is a diagram showing a change in the process state in the second embodiment.
FIG. 29 is a diagram showing a change in the process state when the process 3 is executed.
FIG. 30 is a diagram showing a change in a process state in the third embodiment.
FIG. 31 is a process related diagram used in the sixth embodiment.
FIG. 32 is a diagram illustrating a data derivation relationship;
FIG. 33 is a diagram showing a CAD tool setting panel.
FIG. 34 is a diagram showing a CAD tool setting sub-window;
FIG. 35 is a diagram showing a CAD tool selection panel after CAD tool setting.
FIG. 36 is a diagram showing a change process of CAD tool allocation information.
FIG. 37 is a diagram showing a state inspection process after CAD tool setting.
FIG. 38 is a flowchart of CAD tool setting processing.
FIG. 39 is a diagram showing a target information setting panel.
FIG. 40 is a diagram showing a target information setting sub-window;
FIG. 41 is a diagram showing a target information setting panel after a vendor name is confirmed.
FIG. 42 is a diagram illustrating a target information setting panel after SeriesType is determined.
FIG. 43 is a diagram showing a target information setting panel after SeriesName is determined.
FIG. 44 is a diagram showing a target information setting panel after Package / PinNum determination.
FIG. 45 is a diagram illustrating target information change processing;
FIG. 46 is a diagram showing a state inspection process after setting target information;
FIG. 47 is a flowchart of target information setting processing;
FIG. 48 is a flowchart of an initial setting process.
FIG. 49 is a flowchart of change setting processing;
FIG. 50 is a diagram showing the work contents of step 1 and step 3 in the process relation diagram.
FIG. 51 is a diagram showing an input / output buffer information setting panel.
FIG. 52 is a diagram showing an instruction area on the input / output buffer information setting panel.
FIG. 53 is a diagram showing a sub window panel on the input / output buffer information setting panel.
FIG. 54 is a flowchart of preprocessing for changing input / output buffer information;
FIG. 55 is a flowchart of input / output buffer information change processing;
FIG. 56 is a flowchart of an item setting process.
FIG. 57 is a flowchart of input / output buffer name display processing;
FIG. 58 is a flowchart of an item designation process.
FIG. 59 is a flowchart of group division processing;
FIG. 60 is a flowchart of pin movement processing.
FIG. 61 is a flowchart of an end process.
FIG. 62 is a diagram showing a project information setting panel.
FIG. 63 is a diagram showing a project information input panel.
FIG. 64 is a diagram showing an example of a display on the project information setting panel.
FIG. 65 is a diagram showing an example of a display on the project information setting panel.
FIG. 66 is a diagram showing an example of a display on the project information setting panel.
FIG. 67 is a diagram showing a state of a process related diagram when performing multiple design processing;
FIG. 68 is a flowchart of multiple design processing.
FIG. 69 is a flowchart of design data creation processing;
FIG. 70 is a flowchart of design data selection processing;
FIG. 71 is a diagram showing a method of managing derivation relationship information between data.
FIG. 72 is a diagram showing a method of managing derivation relationship information between data.
FIG. 73 is a diagram showing a method of managing derivation relationship information between data.
74 is a diagram showing a method of managing derivation relationship information between data. FIG.
FIG. 75 is a diagram showing process state transition and data version information change.
[Explanation of symbols]
101 Design management device
102 keyboard
103 CRT display
104 mouse
105 Hard disk device
106 arithmetic processing unit
107 Converter
108 Printer
109 bus
110 Data storage device
111 Program storage device
112 Design management program
113 CAD tools
201 Data management function
202 Process management function
204 Management database
205 design database
300 Design data management function
310 Environmental Data Management Function
320 Project operation function
330 Start-up control function
340 Setting change function
350 Flow control function
360 Information confirmation function
401 History management information data file
501 Initial information data file
502 Group information data file
503 Tool information data file
504 Vendor data file
505 Group management data
506 ASIC data
507 Message log data file
508 Lock information data file
601 Selection information
701 Setting change information
702 Rule information
801 I / O buffer information
802 CAD tool allocation information
803 Target information
901 Main panel
902 Process group display area
903 Work content display area
904 buttons
905 Target display area
906 Start button
907 Cancel button
908 Mouse cursor
1301 CAD tool selection panel
1302 Sub window display button
1303 OK button
1304 Cancel button
1305 Settings subwindow
1501 Target information setting panel
1502 Vendor name setting area
1503 Subwindow display button
1504 Detailed item display area
1505 Candidate display area
1506 OK button
1507 Cancel button
1508 Settings subwindow
2001 Input / output buffer information setting panel
2002 Setting button
2003 Split button
2004 Move button
2005 end button
2011 Subwindow
2101 Project information setting panel
2102 Button group
2103 Left area
2104 Right area
2105 OK button
2106 Cancel button
2107 Project information input panel
2108 OK button
2109 Cancel button

Claims (3)

A process management apparatus that manages by displaying the execution order of a plurality of processes on a display so as to be recognizable.
Storage means for storing derivation relation information of data generated in the plurality of steps;
Determining means for determining whether or not the plurality of steps are executable;
Display processing means for displaying on the display such that each of the plurality of steps can be executed based on the state determined by the determination means;
Said determining means, first data for use when the determination target process execution is generated in the first step is a pre-process of the determination target step, the second data is a prior step of the determination target step the second step in the case has been made live Te smell, the second data to the first data from the derivation relationship information stored by said storing means is a step after the first step Te If the second data is generated by a program selected from a plurality of programs executed in the second step, the determination target step can be executed. process management apparatus, characterized in that to determine that it is. It is a processing method of a process management apparatus that manages by displaying the execution order of a plurality of processes on a display so as to be recognizable,
A storage step in which the processing device stores the derivation relationship information of the data generated in the plurality of steps in a storage device;
A determining step in which the processing device determines whether or not the plurality of steps can be performed;
A display processing step for causing the processing device to display on the display such that each of the plurality of steps can be executed based on the state determined by the determination unit;
In the determination step, the processing device generates first data to be used at the time of execution of the determination target process in a first process that is a previous process of the determination target process, and second data is the determination target process. of a previous step in the case of made production Te second step odor is a step after the first step a, to the first data from the derivation relationship information stored in the storage device When there is a derivation relationship that the second data is generated and the second data is generated by a program selected from among a plurality of programs executed in the second step, the determination A processing method of a process management apparatus, characterized in that a target process is determined to be executable.   A storage medium storing a program for causing a computer to execute the processing method according to claim 2.

Images