JPH08249169A - Specification generating method and device therefor - Google Patents

Abstract

PURPOSE: To finely designate the levels of a describing content in a high-order specification by varying the level of a logical element in the high-order specification to be generated at the time of combining the logical elements and generating the high-order specification where the logical elements are divided into much larger levels from a low-order specification where the logical elements are divided into small levels. CONSTITUTION: An inter-logical element division point judgement function 13 sets division points among the logical elements, which are included in the low- order specification, for converting the logical elements included in the low-order specification into abstract logical elements corresponding to an abstract degree that a user requests. An abstract logical element conversion function 14 converts the combination of the logical elements included in a division section into the abstract logical elements defined in a logical element definition file 42. Then, a display information generation function 15 generates display position data of the respective logical elements on a display device based on the logical elements of high-order specification data held in a high-order specification file 32, information of the connection relation and shape data of the logical elements, which are held in a logical element definition file 42.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and apparatus for creating specifications, and more particularly to specifications for software design support to support reuse and maintenance work of users' already developed software. It is related to the creation, and the specification of the upstream process (hereinafter also referred to as the "upper specification") that describes the outline of the process from the specification of the downstream process (hereinafter also referred to as the "lower specification") that describes the detailed process When changing the level of the high-level specification, when creating the high-level specification, and by considering the importance of the data calculated by each process, the high-level specification is created to streamline the software design work and TECHNICAL FIELD The present invention relates to a specification creating method and apparatus suitable for improving the property.

[0002]

2. Description of the Related Art Conventionally, as a method for improving software productivity, there is known a method of reusing at least a part of a software document constituting a developed system to develop a new system.

When a new system is developed by reusing the software that constitutes the already-developed system, first, as in the above method, the software product of the already-developed system, that is, a high-level programming language for a computer is used. Examine the source code of the program described in, the functional specifications of the software, etc. to determine which part of the software is reusable or which part needs to be modified. Was being conducted.

However, in many cases, the specifications of the upstream process of the developed system do not exist, or even if they exist, the contents do not match the software products such as the program and the specifications of the downstream process. In such cases, it was extremely difficult to determine which part of the downstream software product of the developed system could be reused.

Therefore, as a method for solving this problem,
For example, there is an "automatic generation method of software specifications" described in Japanese Patent Application Laid-Open No. 1-237726. According to this method, the upstream process software product is semantically matched with the downstream process software product by reversely generating the upstream process software product from the program or the downstream process software product.

[0006]

The method according to the above-mentioned prior art is based on the description contents of the software product in the downstream process.
Extract and aggregate the items of the same description items such as files that are input or output in the process of processing, combine these aggregated items and the items that exist independently to create network-like item information, and create the network-like item information. It was a method of converting the expression format of each placed item and generating the target specifications. In other words, this method was a method of aggregating the description contents of the same items such as matching input or output files, so to speak, common items, and facilitating the understanding of the processing relationship between these common items.

However, the above-mentioned prior art does not consider the ease of use of the software product in the upstream process to be generated, and has the problem of lacking flexibility. This is because, in the above-described conventional technology, how finely the description content of the specification of the upstream process to be generated is described, that is, the abstraction degree when abstracting the software product of the downstream process is Is fixed,
This is because it was impossible for the user to specify this degree of abstraction. From this, in the method according to the above-mentioned conventional technique,
The process description of the specification of the upstream process required by the user and the generated process description are inconsistent, which may cause a problem that it is difficult to fully understand the process content of the program.

Further, when generating the specifications of the upstream process,
Since the size of the paper to be printed and the detailed description of processing are irrelevant, it is possible to generate specifications for upstream processes that have a layout that is disproportionate to the size of the paper, or specifications that do not fit within the paper size. There was a problem that it generated.

Further, there is no method for describing the processing contents depending on the importance of the output data of each processing of the upstream process, and there is a problem that it is difficult to make a specification of the upstream process focusing on the important data.

The present invention has been made to solve the above-mentioned problems, and its purpose is to generate a level specification of an upper specification when a specification of an upstream process is generated from a software specification of a downstream process. It is to provide a method and a device for creating a specification that allows users to specify the details in detail.

It is another object of the present invention to provide a specification creating method and apparatus capable of creating a specification of an upstream process having a layout matching the size of a paper when the created specification is printed. .

Further, it is an object of the present invention to provide a method and apparatus for creating a specification, which pays attention to the importance of the data output by each process, and can confirm how the important data is processed in the upstream process. .

[0013]

In order to achieve the above object, the configuration of the invention according to the specification creating method of the present invention is configured by a logic element describing a certain processing unit and a series in which the logic element is connected. A description rule of a specification describing a series of processing is defined, and from the lower specification in which the logic element is divided into small levels, the logic elements of the lower specification are combined to obtain a logically equivalent logic. In the specification creating method of converting a device into an element and creating a high-level specification document in which the logic element is divided into larger levels, the level of the logic element of the created high-level specification document is made variable. .

More specifically, in the specification creating method, the variable level is determined by the abstraction value (V1) requested by the user or the paper size value (Vs) of the specification. It is a thing.

More specifically, in the specification creating method, (1) an abstraction parameter setting step including a process of setting a value (Vl) of the abstraction level requested by the user or a size value (Vs) of the specification. (2) a division point setting step including a process of setting division points between the logic elements of the lower specification, and (3) a logic between the start point and the end point of the division points of the section formed by the division points. Abstract logic element selection step including a process of selecting another predetermined logic element according to the combination of elements, and (4) converting the logic element in this section into another selected logic element, A logic element reconstruction step for generating data of a high-order specification,
The steps (1) to (4) are performed in this order.

More specifically, in the above specification creating method, the dividing point setting step (2) includes a weight (Vg1) predetermined for each type of the logic element and an abstraction degree requested by the user. The processing includes comparing the magnitudes of the values (Vl) and setting the division points between the logic elements based on the result.

More specifically, in the specification creating method, when the logic element reconfiguring step (4) reconfigures the logic elements to generate the data of the high-order specification, the high-order data is generated. It includes a process of generating a size (Vs ') required to display the specification, and (5) compares this Vs' with the size of the size value (Vs) of the specification requested by the user, There is an abstraction parameter changing step including a process of changing the value (Vl) of the abstraction parameter based on this result, and (Vl) the step (5) is performed after each of the steps (1) to (4). When the value (V1) of the abstraction parameter is changed, the steps (1) and (2) are performed again.

Next, in order to achieve the above object, another configuration according to the specification creating method of the present invention is that a series of processing is performed by a logic element describing a certain processing unit and a series in which the logic element is connected. , The logic rules of the specifications are defined, and the logic elements of the logic specifications are divided into small levels, and the logic elements of the logic specifications are combined to convert them into semantically equivalent logic elements. Then, in the specification creating method for creating a higher-level specification in which the logic elements are divided into larger levels, the higher-order specifications created by paying attention to the data dimension of the data handled by the processing described in each of the logic elements. The division point is determined according to the specified data dimension of the logic element of the specification.

More specifically, in the specification creating method, a combination of data dimensions of one or more data handled by the processing described in each logic element is described in the logic element for each logic element. It has an inter-logical element data analysis step including a process of converting into a data dimension after execution of the process.

More specifically, in the specification creating method, the weight of the predetermined data dimension (Vg2) is compared with the magnitude of the abstraction value (Vl) required by the user, and the result is compared. Based on this, processing for setting division points between the logic elements is included.

More specifically, in the method for creating specifications according to the first configuration or the second configuration, a predetermined weight (Vg
1), or the weight of the data dimension (Vg2), or a means for inputting information as to what data dimension the combination of the data dimensions is converted into, and for each type of the input logic element. Predetermined weight (Vg
1), or a weighting (Vg2) of the data dimension, or a definition file holding information about what data dimension the combination of the data dimension is converted into, and a means for inputting them. Information on what kind of data dimension the input weight (Vg1) predetermined for each type of the logic element or the weight of the data dimension (Vg2) or the combination of the data dimensions is converted to The values are held in the definition files, and when the specifications are created, the held values or information are used.

In order to achieve the above object, the configuration of the invention according to the specification creating apparatus of the present invention describes a series of processes by a logic element describing a certain processing unit and a sequence in which the logic element is connected. From the lower specification where the description rules of the specification are defined and the logic element is divided into small levels, the logic elements of the lower specification are combined and converted into a semantically equivalent logic element, In a specification creating device for creating a higher-level specification document in which logic elements are divided into larger levels, the level of the logic element in the higher-level specification document to be created is made variable.

More specifically, in the specification creating apparatus, the variable level is determined by the abstraction value (V1) requested by the user or the paper size value (Vs) of the specification. It was made to be a thing.

More specifically, in the above specification creating apparatus, an abstraction parameter setting means including means for setting a value of abstraction (Vl) requested by a user or a size value (Vs) of the specification, and the lower order Predetermined according to a combination of division points setting means including means for setting division points between the logic elements of the specification, and logic elements between the start point and the end point of the division points of the section formed by the division points. Abstract logic element selection means including means for selecting another selected logic element, and logic element reconfiguration for converting the logic element in this section into another selected logic element to generate data of the upper specification And means.

More specifically, in the above specification creating apparatus, the dividing point setting means sets a predetermined weight (Vg1) for each type of the logic element and an abstraction value (Vl) requested by the user. And a means for setting the division points between the logic elements based on this result.

Further, more specifically, in the above-mentioned specification creating apparatus, when the logic element reconfiguring means reconfigures the logic elements to generate the data of the high-order specification, the high-order specification generated is displayed. And a size value (Vs) of a specification required by the user is compared, and abstraction is performed based on the result. An abstraction parameter changing means including a means for changing the value (Vl) of the parameter is provided.

Next, in order to achieve the above-mentioned object, another configuration of the invention relating to the specification creating apparatus of the present invention is to use a series of logic elements that describe a certain processing unit and a series in which the logic elements are connected. The description rule of the specification describing the processing of the above is defined, and the logical elements of the sub-specifications are combined from the sub-specifications in which the logic elements are divided into small levels, and a logical element equivalent in meaning is formed. In the specification creating device that creates a higher-level specification in which the logic elements are divided into larger levels, paying attention to the data dimension of the data handled by the processing described in each of the logic elements,
The division point is determined according to the specified data dimension of the logic element of the high-order specification to be created.

More specifically, in the specification writing apparatus, a combination of data dimensions of one or more data handled by the processing described in each logic element is described in the logic element for each logic element. It is provided with an inter-logical element data analysis means including a means for converting into a data dimension after execution of processing.

More specifically, in the specification creating device, the weight of the predetermined data dimension (Vg2) is compared with the magnitude of the abstraction value (Vl) requested by the user, and the result is compared. Based on this, processing for setting division points between the logic elements is included.

More specifically, in the specification creating device having the first configuration or the second configuration, a predetermined weight (Vg) is set for each type of the logic element of each of the subordinate specifications.
1), or a means for inputting the weight (Vg2) of the data dimension, or information as to what data dimension the combination of the data dimensions is converted into, and the type of each of the input logic elements. Predetermined weight (Vg
1), or the weight of the data dimension (Vg2), or a definition file that holds information about what data dimension the combination of the data dimensions is converted to.

[0031]

According to the present invention, the parameter of the abstraction level of the specification of the upstream process required by the user of the design support apparatus is set,
According to the value of the abstraction degree parameter, the division points between the logic elements that constitute the software specification of the downstream process are set.
Then, by selecting the logic element forming the specification sheet in the upstream process corresponding to the combination of the logic elements included between the division points, the logic element forming the specification sheet in the upstream process is automatically selected. By reconfiguring these selected logic elements based on the information of the division points of the specifications of the downstream process, the specifications of the software of the upstream process are automatically generated. Further, this division point determines a magnitude relationship between a value (Vg1) according to a predetermined abstraction degree for each logic element and the value of the abstraction degree parameter (Vl) requested by the user, and uses this result. To automatically set.

Therefore, it is possible to automatically generate a high-level specification having a fine description content of the process according to the degree of abstraction requested by the user.

Further, in the present invention, the parameter (Vs') required for displaying the whole as well as the information on the display position of each logic element when the result of reconfiguring the logic element is displayed on the display device. ) Is generated,
The parameter is compared with the value of the abstract parameter (Vs) related to the size of the specification requested by the user, and if the user's request is not satisfied, the abstract parameter (Vl) related to the level of the design process. You can change the value of.

As a result, it becomes possible to automatically generate the specifications of the upstream process according to the parameters related to the size of the specifications requested by the user, and the layout has a disproportionate layout with the size to be printed. It is possible to eliminate the generation of specifications and specifications that are too large to be printed.

Further, in the present invention, the combination of the dimension of the value represented by the plurality of data which is referred to or updated in the process of executing the target software,
For each logic element that composes the specifications, the dimension of the data transferred between the logic elements is analyzed by the process of converting the dimension corresponding to the logic element to the dimension after execution, and the dimension and specification of the value represented by the data The value of the parameter related to the abstraction level of the call is determined, and the division point between the logic elements is set based on this value. In other words, display important data for users,
It is possible to automatically generate the data of the specifications of the upstream process, omitting other intermediate calculation results. Therefore, it is possible to generate a high-level specification document that displays important data for the user.

[0036]

Embodiments of the present invention will be described below with reference to FIGS. 1 to 42. The following embodiments relate to a specification creating method and apparatus that can be used for design support regarding software that realizes a control function in a plant. That is, it is intended to support the user's understanding of the processing contents of software by converting the data of the specifications of the downstream process, which describes the details of the detailed processing, into the specifications of the upstream process that outlines the processing. Is.

[First Embodiment] A first embodiment of the present invention will be described below with reference to FIGS. 1 and 2, 5 and 6, and FIGS. (I) Input and Output of Specification Creation Device The specifications of the software targeted in this embodiment are programmable controller for plant control (hereinafter, "PC").
Command) to a central processing unit (hereinafter referred to as “CPU”) is described by associating with a logic element, and data transfer and a processing execution order are described by a sequence consisting of the logic element and its connection relationship. To do.

First, the input and output of the specification creating apparatus will be specifically described with reference to FIGS. FIG. 5 is a diagram showing a subordinate specification which is input to the specification creating device according to the first embodiment of the present invention. FIG. 6 is a diagram showing a high-level specification document which is an output of the specification document creating apparatus according to the first embodiment of the present invention.

The logic elements 2a-2j shown in FIG. 5 represent the instructions of the PC shown in Table 1 below. That is, the specification shown in FIG. 5 describes the operation of each instruction of the PC.

The specification creating apparatus according to the present invention inputs a lower level specification as shown in FIG. 5 and creates an upper level specification describing a rough outline of the processing.

[0041]

[Table 1]

(II) System Configuration of Specification Creation Apparatus and Data Structure for Specification Creation Next, a first embodiment of the present invention will be described with reference to FIGS. 1 and 2, FIGS. 16 to 21 and 23. The system configuration of the specification creating apparatus and the data structure for creating specifications will be described. FIG. 1 is a schematic diagram of functional blocks and data files of a software specification creating apparatus according to a first embodiment of the present invention. FIG. 2 is a schematic diagram showing the hardware configuration of the software specification creating apparatus according to the first embodiment of the present invention. FIG. 16 is a schematic diagram showing the lower specification data 501. FIG. 17 shows logic element detailed data 502a.
It is a schematic diagram showing. FIG. 18 is a schematic diagram showing the abstract logic element related data 502b. FIG. 19 is a schematic diagram showing the abstract logic element conversion rule data 503. FIG.
FIG. 6 is a schematic diagram showing logical element record data 504. FIG. 21 is a schematic diagram showing the path record data 505 according to the first embodiment of the present invention. FIG. 23 is a schematic diagram showing the upper specification data 500.

First, the data structure for creating specifications will be described. The low-level specification file 31 stores the data of the low-level specification document to be converted, and the high-level specification file 32 stores the data of the high-level specification document generated as a result of the conversion.

The lower specification file 31 is the lower specification data 501 shown in FIG. 16 as the data of the drawing of the specification.
Hold. This lower specification data 501 is a record No. indicating the record number. 5a, a logic element ID 5 that represents a predetermined identification code for each type of logic element
b, a reference memory address 5c representing an address of information for interfacing a memory or an interface for reading or writing data when executing an instruction corresponding to each logical element, and a logical element for executing the instruction next Next element record No. representing the record number of Hold 5d.

The reference memory address 5c is, for example, M1 in the case of the logic element 2a, and is displayed below the location where the logic element of the specification is displayed. The next element record No. 5d is the record No. of the logic element next to the logic element. Is represented. That is, the lower specification data 5 of the logic element connected by the solid line 4 in FIG.
Record No. of the corresponding item of 01. Is represented.

If there is no logical element for executing the next instruction, the next element record number. I promise to put "-1" in 5d.

The upper specification file 32 holds the upper specification data 500 shown in FIG. This upper specification data 500 is structurally lower specification data 501.
Is the same as.

The abstraction parameter file 41 holds the value "Vl" of the degree of abstraction requested by the user. Here, the degree of abstraction is a value that defines the level of the higher-level specifications that are output, and promises that the higher the value, the greater the description of the processing of the high-level specifications.

The logic element definition file 42 holds the logic element detailed data 502a shown in FIG. 17 and the abstract logic element related data 502b shown in FIG.

The detailed logic element data 502a is the logical element ID 5b of the logical element to be converted, the data 5e of the shape when the logical element is displayed on the display device, the instruction 5f to the PC corresponding to the logical element, and the degree of abstraction. In consideration of the above, it is composed of a weight value “Vg1” 5g indicating the value of the degree of importance of the logic element when the upper file is generated.
The larger the weight value Vg1, the more important the logic element is, and the finer it is displayed in the higher-level specifications.

The abstract logic element related data 502b includes a logic element ID 5b of the abstract logic element and data 5e of the shape of the abstract logic element.

Here, the "abstract logic element" is a process in which one or more logic elements are combined and associated with each other as one logic element. That is, it can be understood that lower logical elements are combined to form a higher logical element.

The abstract logic element conversion rule file 43 holds the abstract logic element conversion rule data 503 shown in FIG.

The abstract logic element conversion rule data 503 is
A combination of one or more subordinate logic elements ID5b1;
It is composed of abstract logic elements 5b2 corresponding to them.

The logic element connection data file 44 is formed by extracting logic element data from the specification data, and the logic element record data 50 shown in FIG.
4 holds the path record data 505 shown in FIG.

The logical element record data 504 is a record No. indicating the record number. 5h, logic element ID
5b, the weight 5g of the logical element, and the next pass record No. 5 representing the record number in the pass record data 505 described next. It consists of 5i.

The pass record data 505 is a record No. indicating the record number. 5i, regarding the path connecting the logic elements, the record No. in the logic element record data 504 of the logic element connected to the first end point. 5b
1, the weight 5g1 of the logic element, and the path connecting the logic elements, the record No. in the logic element record data 504 of the logic element connected to the second end point. 5b
2, a weight 5g2 of the logic element, and a division flag 5j indicating whether or not to divide the logic element in the path. Each item of the pass record data 505 represents the connection information between the logic elements, and is also referred to as a "pass record" hereinafter.

Next, each function of the specification creating apparatus shown in FIG. 1 will be described. The input data editing function 11
This is a function of writing the value “Vl” corresponding to the abstraction degree of the upper specification requested by the user into the requested abstraction degree file 30.

The inter-logical element data relation analysis function 12 refers to the data of the logical element definition file 42 and reads the necessary data 501 of the lower specification file 31. And
The data is analyzed to analyze the logic element record data 50.
4 and pass record data 505 and write them in the logic element connection data file 44.

The inter-logical element division point determination function 13 refers to the abstraction parameter file 41 to read the path record data 505 of the logical element connection data file 44, and the division flag 5j of this path record file 505.
Is determined and written to the division flag 5j, and the path record data 505 is updated. Then, it has a function of writing the updated path record data 505 to the logic element connection data file 44.

The abstract logic element conversion function 14 uses the logic element record data 504 of the logic element connection data file 44.
And the path record data 504 are read, and the combination of the logic element ID 5b of the logic element included in the section in which the division flag 5j of the path record data 505 is set and the lower logical element ID 5b1 of the abstract logic element conversion rule file 503. The combination is compared and the matching combination is changed to the abstract logic element ID 5b2. At the same time, the data of the path record data 505 is also corrected according to the change of the data of the logic element record data 504. Then, it is a function of generating the upper specification data 500 from the logic element record data 504 and the path record data 505 of the logic element connection data file 44.

The display information generation function 15 reads the high-level specification data 500, and the shape 5e of the logic element record data.
Is a function for generating data including the display position of the logic element to be displayed on the display device 55 described below.

Next, the hardware configuration of the specification creating apparatus according to the present invention will be described with reference to FIG.

The CPU 51 performs the specification creating method of the present invention according to the data and the program stored in the memory 52. The external storage device 53 stores the various files described above. The input device 54 is specifically a mouse or a keyboard, and can input commands and parameters to the specification creating device. Display device 55
Is a CRT display or a liquid crystal display, and can display specifications.

(III) Processing Procedure of Specification Writing Method Next, a processing procedure of the specification writing method according to the first embodiment of the present invention will be described with reference to FIGS. 34 to 40.
In the following, this embodiment will be described with appropriate reference to the functional blocks and files shown in FIG. The lower specification file 31 includes the lower specification data 501 and the logic element definition file 42 shown in FIG.
17 and the abstract logic element related data 502b shown in FIG. 18, and the logic element conversion rule file 43 contains the abstract logic element conversion rule data 503 shown in FIG. It should be held. In addition, an abstraction parameter file 41,
It is assumed that there is no data in the logic element connection data file 44.

(1) Outline of Processing Procedure of Specification Writing Method First, the outline of processing procedure of the specification writing method will be described with reference to FIG. FIG. 34 is a general flowchart showing the outline of the processing procedure of the specification creating method according to the first embodiment of the present invention.

First, the input data editing function 11 writes the value "Vl" of the abstraction degree of the upper specification required by the user in the abstraction parameter file 41 (step 10).
0).

Next, the logic element data analysis function 12
The data 501 of the lower specification file is read, the data of the logic element in the lower specification is analyzed, and from the result, the logic element record data 504 and the path record data 5 are obtained.
05 and write them in the logic element connection data file 44 (step 110).

Next, in order to convert the logic elements included in the lower-level specifications into the abstract logic elements corresponding to the degree of abstraction requested by the user, the inter-logical-element dividing point determination function 13 determines whether the logic elements included in the lower-level specifications are connected to each other. The division point of (step 12
0). That is, the value of column 5j of the division flag of the path record data 505 generated in step 110 is set. In the present embodiment, the value of the column 5j of the division flag is promised to be "1" when the connection between the logic elements, that is, the path is divided, and "0" when not divided.

Next, the abstract logic element conversion function 14 converts the combination of logic elements included in the section divided as a result of the processing of step 120 into the abstract logic element defined in the logic element definition file 42 (step 130). ).

Next, the display information generating function 15 generates data for displaying the upper specification data 501 as a graphic (step 140). That is, the data of the logic elements and their connection relations of the high-level specification data 501 held in the high-level specification file 32 and the shape data of each logic element held in the logic element definition file 42 (the shape 5e of the logic element detailed data 502a, Based on the shape 5e) of the abstract logic element related data 502b, the data of the display position of each logic element on the display device is generated.

(2) Details of Step 110 of Analyzing Data of Logic Element in Lower Specification Document Next, the step 110 of analyzing data of the logic element in the lower specification document will be described in more detail with reference to FIG. Let me explain. FIG. 35 is a detail flowchart showing the processing procedure of step 110 for analyzing the data of the logic element in the lower specification.

The inter-logical element data analysis function 12 reads the lower specification data 501 and analyzes the relationship between the logical element in the lower specification and the next logical element (step 11).
1). This means that, for example, in the specification 1 of FIG. 5, the logic element connected to the solid line 4, that is, the relationship information of the logic element 2a and the logic element 2b is generated.

Next, the reference memory address 5c data of the lower specification data 501 is analyzed, and the item (path record) of the path record data 505 is generated according to whether or not the reference memory address 5c is common (step). 115).

(3) Details of Step 111 for Analyzing the Next Logical Element Relationship Next, the step 111 for analyzing the next logical element relationship will be described in more detail with reference to FIG. FIG. 36 is a detail flowchart showing the processing procedure of step 111 for analyzing the next logical element relationship.

In this step, the logic element relationship is analyzed from the lower specification data 501 shown in FIG. 16 and the logic element detailed data 502a shown in FIG. 17, and the logic element record data 504 shown in FIG. The path record data 505 shown in FIG. 21 is generated.
That is, the weight corresponding to each logical element of the lower specification data 501 is taken to be the logical weight value 5g of the logical element record data 504, and the item corresponding to the path connected to each element is taken as the item of the path record data 505. No. Is set to the next pass record 5g.

Each item of the path record data 505 represents a path between logic elements. One end is a first end point, and a pair of end points is a second end point. 5b1 and 5b2, and their weights are set to 5g1 and 5g2, respectively.

First, make a notational promise. For example, 5 is used to represent the 5h column of the logic element record data 504.
It will be written with a combination of codes such as 04-5h.

Further, N in the logic element record data 504
Column 5b of the th record is replaced with brackets [] 5
04 [N] -5b.

First, the value "1" is set in the variable "recNo".
Is set (step 1111). Variable "recN
"o" is used for a counter.

Next, a new record is added to the logic element record data 504, and the "record N" of this record is added.
o. The value of "recNo" is set in "504-5h" (step 1112).

Next, the value of 501 [recNo] -5b is copied to 504 [recNo] -5b (step 1113).

Next, in the logic element definition file 502a, the value of the column 502a-5b of the logic element ID is 5
04 [recNo] -5b, the value of the column 504-5g of the logical element weight (Vg1) of the record equal to the value of 50 is set to 50.
4 [recNo] -5g (step 111)
4).

Next, if the value of 501 [recNo] -5d is 0 or more, that is, if there is a logic element to be connected next, the process proceeds to step 1116, and if not, the process proceeds to step 1125 (step 1115). .

Next, a new record is added to the path record data 505 (step 1116).

Next, the value of 504 [recNo] -5h is set to the record No. column 505-5b of the first endpoint element.
1 is copied (step 1117).

Next, the value of 504 [recNo] -5g is copied to the column 505-5g1 of the weight of the first endpoint element (step 1118).

Next, the next element record N is added to "recNo".
The value of o501 [recNo] -5d is set (step 1119).

Next, a new record is added to the logic element record file 504 (step 1120).

Next, as in step 1113, 501
The value of [recNo] -5b is changed to 504 [recNo]-
5b is copied (step 1121).

Next, as in step 1114, the value of the weight of the logic element is copied (step 1122).

Next, the record No. of the second end point element is copied. That is, 504 [recNo] -5h is changed to 505
-5b2 is copied (step 1123).

Next, the weight (Vg1) of the second end point element is copied (step 1124). That is, 504 [re
cNo] -5g is copied to 505-5g2.

Then, from step 1115 to step 1
If the value of 501-5d is “−1”,
Repeat until the next logic element runs out.

Next, it is checked whether or not the lower specification data 501 has the next record. If the next record exists, the process proceeds to step 1126. If not, the process of step 111 is completed (step 1125). ).

Next, the value of "recNo" is incremented by "1" (step 1126).

As described above, in the step 111 of analyzing the next logical element relationship, the processing of the steps 1112 to 1125 is repeated until there is no data of the lower specification.

(4) Step 11 of analyzing the reference memory
Details of Step 5 Next, referring to FIG. 37, Step 1 of analyzing the reference memory
Let us explain 15 in more detail. FIG. 37 is a detail flowchart showing the step 115 of analyzing the reference memory.

In this step, referring to the reference memory address 5c of the lower specification data 501 shown in FIG. 16, when the reference memories match, the same process is described, and a path is added to each of the path record data. Record No. of the logic element at the end point of The values are set to 5b1 and 5g2.

First, integer variables "recNo_1" and "re"
The values of "cNo_2" are set to "1" and "2", respectively (step 1151). These recNo_1 and re
cNo_2 is used for the counter.

Next, the record N of the lower specification data 501
o. The value of the column 5c of the "reference memory address" of the record whose column is equal to recNo_1 and recNo_2 is compared (step 1152).

As a result, if the values match, that is,
When the logic elements of recNo_1 and recNo_2 have the same memory as the reference memory, steps 1153 to
The processing of step 1157 is executed.

If they do not match, the process proceeds to step 1158.

Next, the path record of the path record data 505 generated in step 111 is added (step 1153).

Next, the value of 504 [recNo_1] -5h is set to the first endpoint. Record No. Copy to 505-5b1 (step 1154).

Next, the value of 504 [recNo_1] -5g is set to the first endpoint. The weight is copied to 505-5g1 (step 1155).

Next, the value of 504 [recNo_2] -5h is set to the second endpoint. Record No. Copy to 505-5b2 (step 1156).

Next, the value of 504 [recNo_2] -5g is set to the second endpoint. Copy to weight 505-5g2 (step 1157).

Next, recNo is written in the lower specification data 501.
It is checked whether there is a record next to _2, and if there is, go to step 1159;
(Step 1158).

At step 1159, the value of recNo_2 is incremented by "1".

Then, the processes of the above steps 1152 to 1159 are repeated until the last record of the lower specification data 501.

Next, recNo is written in the lower specification data 501.
It is checked whether or not there is a record next to _1, and if there is, proceed to step 1161. If not, it means that the analysis of the reference memory has been completed for all the lower specification data 501 (step 1160). The value of recNo_1 is incremented by "1".

Then, the above steps 1152 to 1161 are repeated until the last record of the lower specification data.

(5) Details of Step 120 for Selecting Path Split Points Between Logic Elements Next, step 120 for selecting path split points between logic elements will be described in more detail with reference to FIG. FIG. 38 shows
It is a detail flowchart which shows step 120 which selects the path | pass division point between logic elements.

In this step, the value "Vl" of the degree of abstraction requested by the user is compared with the weight values 5g1 and 5g2 of the logic elements set in the path record data 505, the division points are determined, and the path record data 505 is stored. This is a step of setting a value to the division flag 5j.

First, the logic element division point determination function 13
The value "Vl" of the degree of abstraction requested by the user is read from the abstracted parameter data file 41 and copied into the variable V (step 1201).

Next, the value of the variable "recNo" is set to "1" (step 1202).

Next, at step 1203, the value of the first end point element.Weight 505 [recNo] -5g1 of the path record data 505 of the logic element connection data file 44 and the second end point element.Weight 505 [recNo] -5g2. For each value of V, and if either value is greater than V, that is,

[0119]

## EQU1 ## If 505 [recNo] -5g1> V or 505 [recNo] -5g2> V is satisfied, the process proceeds to step 1204. If not, the process proceeds to step 1205 (step 1204).

In step 1205, the division flag 505
[1] is set in [recNo] -5j. That is, when a logical element having a weight greater than the value of the degree of abstraction requested by the user exists at the end point, the path corresponding to this path record is divided, and the level of the output specification is lowered. Make something.

Finally, the re of the path record data 505 is
It is checked whether there is a record next to the record corresponding to cNo, and if there is a record, the process returns to step 1203.

In this way, steps 1203-12
The processing of 05 is performed on all the records of the path record file.

If there is no next record, the process ends.

(6) Details of Step 130 of Converting Logic Element Included in Divided Section into Abstract Logic Element Next, step 130 of converting the logic element included in the divided section into an abstract logic element with reference to FIG. Will be explained in more detail. FIG. 39 is a detail flowchart showing step 130 of converting a logic element included in the divided section into an abstract logic element.

This step replaces the logic element of the lower specification with the abstract logic element of the upper element in accordance with the division point set in step 120 and with reference to the abstract element conversion rule data 503 shown in FIG. As a result, the higher specification data 5 shown in FIG.
This is a step of generating 01.

First, the value of the variable "recNo" is set to "1", and an array holding a plurality of data, "workI" is set.
The data of "D" and "workMem" are cleared (step 1301).

Next, in the variable “pasRecNo”, the next path record No. of the record recNo of the logic element record file 504 of the logic element connection data file 44 is set. 5
04 [recNo] -5i is copied (step 130)
2).

Next, the record pasRecN of the path record file 505 of the logic element connection data file 44 is recorded.
the value of the division flag of o

[0129]

## EQU2 ## It is checked whether 505 [pasRecNo] -5j = 1 holds, and if it holds, step 13
The procedure proceeds to 04, and if not satisfied, the procedure proceeds to step 1306 (step 1303). That is, if the logical element is not divided by the path of pasRecNo, step 13
Proceed to 06.

When the equation 2 holds, workI
The logical element ID held in D, that is, the logical element included in the section between the division points is converted into an abstract logical element, and the higher specification data 500 is generated from this result (step 130).
4).

Next, workID and workMem
Is cleared (step 1305).

When the equation 2 is not satisfied, wo
At the end of rkID, the logical element ID 504 [recN of the record recNo of the logical element record file 504 is recorded.
o] −5b is added (step 1306).

Next, at the end of workMem, the record rec of the lower specification data 501 of the lower specification file 31.
The value of the reference memory address 501 [recNo] -5c of No is added (step 1307).

Next, recNo is set to the second end point of the record pasRecNo of the path record file 504. Record No. The value of 505-5b2 [pasRecNo] is copied (step 1308).

Next, pasRecNo contains the next path record No. of the record recNo of the logic element record file 505. The value of 504-5i [pasRecNo] is copied (step 1309).

Next, in step 1310,

[0137]

[Mathematical formula-see original document] It is checked whether or not pasRecNo> 0 holds, and if it holds, that is,
If there is a logic element connected next to the logic element of recNo, the process returns to step 1302. If not established, it is checked in step 1311 whether there is a record next to the recNo of the logic element record.

If there is the next record, step 1
Proceed to 312. If not, the process ends (step 13).
12).

At step 1312, "1" is added to the value of recNo to clear the contents of workID and workMem.

(7) Details of Step 1304 of Converting to Abstract Logic Element and Writing to Upper Specification File Next, step 1304 of converting to an abstract logic element and writing to the upper specification file will be described in more detail with reference to FIG. Try. FIG. 40 is a detail flow chart showing step 1304 of converting into an abstract logic element and writing into the high-level specification file.

First, the value "1" is set in the variable "ruleNo" (step 1351).

Next, the combination of the logic element IDs of the logic elements included in the divided section and the abstract logic element conversion rule data 503 held in the abstract logic element conversion rule file 43.
The value of the logic element ID 503 [ruleNo] -5b1 is compared with the value (step 1352). And step 1
The result of 352 is checked, and if they match, the process proceeds to step 1354, and if they do not match, step 135.
5 (step 1353).

In step 1355, it is checked whether there is a record next to ruleNo in the abstract logic element conversion rule data 503. Then, if there is the next record, the process proceeds to step 1356, and if not, the process proceeds to step 1357 (step 1355).

In step 1356, the variable "ruleN
The value obtained by adding "1" to the value of "o" is set again in ruleNo, and the process returns to step 1352. That is, a combination of logic element IDs of logic elements included in the divided section,
The logic element ID 503 [ru of the abstract logic element conversion rule data 503 held in the abstract logic element conversion rule file 43
[leNo] -5b1 match or until the end of the data of the abstract logic element conversion rule 503 is reached, the processes of steps 1352 to 1355 are repeated.

Now, in step 1353, the combination of the logic element IDs of the logic elements included in the divided section and the logic element ID 503 [ruleNo] -of the abstract logic element conversion rule 503 held in the abstract logic element conversion rule file 43.
When it is determined that the values of 5b1 match, the variable "newI
D ”is an abstract logic element ID 503 [ruleNo] -5b
The value of 2 is set (step 1354).

Also, in step 1355, ruleNo
When it is determined that there is no next record, that is, the combination of the logic element IDs of the logic elements included in the divided section and the logic element 5b of the abstract logic element conversion rule data 503.
If there is no match for the value of 1, step 135.
In step 7, "ID99" is set to the variable "newID" as the logic element ID of the default abstract logic element.

As a result of the above steps 1351-1357, the logic element ID of the abstract logic element corresponding to the combination of the logic element IDs of the logic elements included in the divided section can be set in the variable "newId".

Next, in the processing of steps 1358 to 1363, a record of the upper specification data 500 is created and written in the upper specification file 32.

The format of the upper specification data 500 which is the data of the upper specification file 32 is the same as the format of the lower specification data 501 of the lower specification file 31.

Next, as the value of the variable "oldRec",
Record N of the last record of the high-level specification file 32
o. The value of 5a is set (step 1358).

Next, as the value of the variable "newRec", o
Set the value of ldRec + 1 (step 135
9).

Next, oldRe of the upper specification data 500
The value of newRec is set as the value of the column of the next element record 5d of the record of c (step 136).
0).

Next, newRe of the upper specification data 500
As the value of the column of the logic element ID 5b of the record of c,
The value of newID is set (step 1361).

Next, newRe of the upper specification data 500
The value of workMem is set as the value of the column of the reference memory address 5c of the record of c (step 136).
2).

Next, newRe of the upper specification data 500
"-1" is set as the value of the column of the next element record 5d of the record of c (step 1363).

A record of the high-level specification data 500 can be generated by the above processing of steps 1358 to 1363.

(IV) Application to Specific Data Next, the case where the specification creating method according to this embodiment is applied to specific data will be described with reference to FIGS. 16 to 23 and 34. FIG. 22 is a schematic diagram showing the path record data after the value setting according to the first embodiment of the present invention.
FIG. 23 is a schematic diagram showing the high-level specification data 500 according to the first embodiment of the present invention, as described above. It is assumed that the value of V1 input in step 110 of FIG. 34 is 5.

Further, as described above, it is assumed that the data of FIG. 16 is set in the lower specification data 501. Similarly, the logic element detailed data 502a includes the data shown in FIG.
7 is the abstract logic element related data 502b,
It is assumed that the data in FIG. 18 has been set. further,
It is assumed that abstract logic element conversion rule data 503 as shown in FIG. 19 is set between these logic elements and abstract logic elements.

Based on these data, step 11
When the processing of 0 is executed, the logical element record data 504 of FIG. 20 and the path record data 505 of FIG. 21 are generated by the inter-logical element data analysis function 12.

Next, when step 120 is executed, as shown in FIG.
A value is set to the division flag of 1 as shown in FIG.

Then, the generation result obtained by executing step 130 is the high-level specification data 500 shown in FIG.

Finally, from the upper specification data 500 and the display data, the upper specification document as shown in FIG. 6 is displayed on the display device 55. This bi (i =
Each of the logic elements 1, ...
Record No. corresponds to the record i. Also,
Although not shown in the figure, it is also possible to print the specifications from the printing device.

(V) Features of the Present Embodiment As described above, according to the method and apparatus for creating a specification according to the present embodiment, the data (definition) of a logic element is assigned the weight (importance) of the logic element. It is possible to hold the data (Vg1), input the degree of abstraction (Vl) required by the user, and automatically generate a higher-level specification document corresponding to it, and display it on the display device. .

Therefore, the user can easily understand the contents of the processing of the existing software. That is, according to the present embodiment, when the user tries to reuse the existing software, the overall processing flow of the software,
It is possible to generate specifications that show the details of the processing at various stages such as the details of the processing, and by using this specification, when the software is changed for another purpose, the changes and the effects of the changes The user can easily understand the ripple points of.

[Embodiment 2] A second embodiment of the present invention will be described below with reference to FIGS. 3, 7 and 8, 24 and 25. In the above-described first embodiment according to the present invention, the software product of the intended upstream process uses the abstraction parameter (hereinafter, referred to as level value (Vl)) related to the level, that is, the stage of the design process, to the user. , And generated the corresponding specifications.

On the other hand, in the present embodiment, it is assumed that a high-level specification is displayed and printed, and parameters relating to the size of the paper to be printed on the user and the number of sheets (hereinafter, the size value ( Vs)) is input to generate an upper-level specification document to be output, and when displaying and printing, it is determined whether or not the parameter can be displayed and printed. If the parameter does not match the parameter input by the user, the level value (Vl) is changed to regenerate the data of the specification of the higher level so that the size value (Vs) requested by the user is met. It realizes automatic generation of higher-level specifications.

(I) Input and Output of Specification Writing Device First, the input and output of the specification writing device according to the second embodiment of the present invention will be described with reference to FIGS. FIG. 7 is a diagram showing that the sheet size and the number of sheets are input on the parameter setting screen. FIG. 8 is a diagram showing a high-level specification document which is an output of the specification document creating apparatus according to the second embodiment of the present invention.

Also in this embodiment, the input lower specification is:
Similar to the first embodiment, it is assumed that the specifications are shown in FIG. Also, the level value V1 of the degree of abstraction requested by the user is
Let's say 5 as in the first embodiment.

In this embodiment, as shown in FIG. 7, the paper size is input to the input area 62a and the number of sheets is input to the input area 62b from the parameter setting screen 62 displayed on the display device 55. Here, the paper size is an output medium for displaying and printing the high-level specifications to be output (mainly paper is assumed).
And the number of sheets is the number of sheets to output the output medium.

In FIG. 7, "A4" is entered in the input area 62a,
Enter "1" as the number of sheets and enter A4
It indicates that the size (Japanese Industrial Standard A row No. 4) is used to output one sheet.

FIG. 8 schematically shows the high-level specifications output according to this value, and it is understood that the two central blocks are compressed into one.

(II) System Configuration of Specification Writing Device and Data Structure for Creating Specifications Next, referring to FIG. 3, the system configuration and specifications of the specification writing device according to the second embodiment of the present invention. The data structure for creation will be described. FIG. 3 is a schematic diagram of a functional block and a data file of the specification creating apparatus according to the second embodiment of the present invention.

This embodiment differs from the first embodiment in that the abstraction result evaluation function 16 and the size value request abstraction degree changing function 1
7 is added.

The abstraction result evaluation function 16 evaluates the output specification data, obtains the size value thereof, and determines whether or not the size value conforms to the size value requested by the user.

The request abstraction degree changing function 17 uses the size value (V
s) is to change the level value (Vl) as requested by the user.

Other system configurations and data structures are as follows.
This is the same as the first embodiment.

(III) Processing Procedure of Specification Writing Method Next, the processing procedure of the specification writing method according to the second embodiment of the present invention will be described with reference to FIGS. 24, 25 and 41. In the present embodiment, a process for the lower specification data 501 shown in FIG. 16 similar to that of the first embodiment will be described as an example, focusing on a part of the process different from the first embodiment, and will be described based on specific numerical values.

FIG. 24 is a schematic diagram showing the path record data 505 according to the second embodiment of the present invention. Figure 25
Is the high-level specification data 500 according to the second embodiment of the present invention.
It is a schematic diagram showing. FIG. 41 is a general flowchart showing the outline of the processing procedure of the specification creating method according to the second embodiment of the present invention.

This flowchart is obtained by adding steps 150, 160 and 170 to the flowchart of FIG.

Further, in this embodiment, in step 100, in addition to the level value "Vl" of the degree of abstraction requested by the user, which is also performed in the first embodiment, the input data editing function 11 The size value “Vs” to be input is written in the abstraction parameter data file 41.

It is assumed that the input is made from the parameter setting screen as described above. In this case, the input data editing function 11 is 26 (c) which is the effective length of the "A4" paper.
m) multiplied by the number of sheets of paper 1 (sheet), that is, 26
Is written in the abstract parameter data file 41 as the size value Vs. In other words, Vs can be thought of as the area the user is trying to use for creating specifications,
In this case, it means that the user wants to store the specifications in A4 size or less.

Further, in the present embodiment, the input data editing function 11 writes the value “5” preset as the initial value as the level value into the abstraction parameter data file 41 as Vl.

In this embodiment, since the level value of the abstracted parameter data file 41 is Vl = 5, the processing from step 110 to step 140 is executed in the same way as in the first embodiment. That is, step 13
As a result of 0, the high-level specification data 501 generated by the abstract element conversion function 14 and written in the high-level specification file 32 is shown in FIG.
It has the value shown in 6.

Next, the abstraction result evaluation function 16 reads the data for display on the display device of the high-level specification generated in step 140 from the high-level specification file 32, and calculates the length required for display from this data. Yes (Step 15)
0).

In this embodiment, it is assumed that the length required for displaying each logic element is set to "6 cm" in advance. At this time, the high-level specification data 5 shown in FIG.
Since there are 6 logic elements in 01, it is calculated that the length required for display is Vs ′ = 6 cm × 5 = 30 cm. Further, the abstraction result evaluation function 16 uses the requested size value Vs from the abstraction parameter data file 41.
Is read and compared with the calculation result of Vs ′. That is,
It is evaluated whether or not Vs>Vs' holds. In this example, since Vs = 26, and Vs ′ = 30, it is determined that Vs> Vs ′ does not hold. That is, it is determined that the generation result of the specification in which the setting value of the level value is the initial value "5" does not satisfy the paper size (one A4 paper) requested by the user.

As the process, if Vs> Vs 'is satisfied, the process is terminated, and if Vs>Vs' is not satisfied, the process proceeds to step 170 (step 15).
0).

At step 170, the level value Vl is reset so that the specification generation result satisfies the required size value Vs. That is, the requested abstraction degree changing function 17 reads the level value Vl from the abstraction parameter data file 41, and writes the value obtained by adding “1” to the abstraction parameter data file 41 again. In the case of the example used in the description of the present embodiment, a value obtained by adding "1" to "5" to Vl, that is, "6" is set and written in the abstract parameter data file 41.

The above steps 110 to 170 are executed as follows.
The process is repeated until Vs>Vs' is satisfied in step 150, that is, until the size required by the user is reached.

In this embodiment, when the value of Vl is "6",
The pass record generation result is shown in the pass record data 505 of FIG. In Table 9, since the Vl value is "6", the division flag of the path whose "record No." is "5" is changed from "1" to "0". At this time, the high-level specification generation result is as shown in the high-level specification data 501 in FIG. 25. Since the number of logic elements is 4, Vs ′ = 24, and Vs> Vs ′ is satisfied, and the processing ends. To do.

(IV) Features of the Present Embodiment As described above, according to the specification creating apparatus of the present embodiment, with respect to the parameters relating to the size of the specification, the value requested by the user and the automatic generation of the specification By comparing it with that of the result and adjusting the parameters related to the level of the design process so as to match the user's request and regenerating the specification, the upper specification according to the size of the specification requested by the user Since it is possible to automatically generate, it is particularly convenient when the paper size and the number of sheets that can be used at the time of printing are limited.

[Embodiment 3] Hereinafter, a third embodiment of the present invention will be described with reference to FIGS. 4, 9 to 15, and 26 to 33.
Will be explained. In the first embodiment, for each type of logic element, a value related to the degree of importance of the logic element is determined in advance,
Utilizing this, a high-level specification of the level of the design process required by the user was generated. Therefore, the importance of data handled in the process of processing with the same type of logic element (hereinafter, Vg1
However, they were treated in the same way.

However, it is assumed that there are two logic elements of a type that inputs certain data and outputs the result of the operation, in the specification of the lower process. At that time, the operation result of one logic element is an intermediate result of the processing by the software, which is meaningful to the designer,
The operation result of the other logic element may be mere work data. That is, one of the calculation results may be easy for the user to understand the specifications by knowing it, but the other may not be so meaningful even if it is known.

In the present embodiment, such logical elements of the same type are set in more detail by using the attributes of the data referenced / updated by the logical elements, and the detailed weights are set. Thus, the division point between the logic elements is determined. Specifically, the designer may assume the case where the data having the dimension of length is to know the result, but the data relating to the voltage is not so interested.

As a result, the specification of the upper process, which is easier for the user to understand, is automatically generated, and the work efficiency of the user is improved. In addition, the present embodiment improves the operability for the user by having the step of editing the definition of the logic element and the abstract logic element conversion rule.

(I) Input and Output of Specification Writing Device First, the input and output of the specification writing device according to the third embodiment of the present invention will be described with reference to FIGS.
FIG. 9 is a diagram showing a subordinate specification which is input to the specification creating apparatus according to the third embodiment of the present invention. FIG. 10 is a diagram showing that a weight value is being input on the logic element weight setting screen. FIG. 11 is a diagram showing that the association between the logic element and the abstract logic element is registered on the abstract logic element registration screen. FIG. 12 is a diagram showing that the data dimension and the weight are input in the data dimension definition screen. FIG.
FIG. 6 is a diagram showing a memory address, a data name, and a data dimension being input in the data dimension registration screen. FIG.
FIG. 4 is a diagram showing that the logic element, the first data dimension, the second data dimension, and the result data dimension are input on the data dimension conversion rule registration screen. FIG. 15 is a diagram showing a subordinate specification which is an input of the specification creating device according to the third embodiment of the present invention.

The lower specification which is the input of this embodiment is shown in FIG.
It shall be composed of a combination of logic elements as shown in. Then, the high-level specifications shown in FIG. 15 are created. In this specification, the dimension of data is displayed on the output of the logic element.

Next, the user inputs information regarding the data dimension of the logic element. As for these data, the screen is displayed on the display device 55 as follows, and after the data is input,
It is written in the logic element definition file 42 by the input data editing function 11.

On the logic element weight setting screen shown in FIG. 10, the user sets the weight value (Vg
1) (This is reflected in 502a-5g shown in FIG. 17) is set.

On the abstract logic element registration screen shown in FIG. 11, the user sets a pair of a logic element (corresponding to 503-5b1 in FIG. 19) and an abstract logic element (corresponding to 503-5b2 in FIG. 19). Perform. When input, the shape of the logic element is displayed on the screen by using the data of the shapes 502-5e of FIG. When input, the input data editing function 11 writes the input data into the abstract logic element conversion data of the abstract logic element conversion rule file 43.

On the data dimension definition screen shown in FIG. 12, the user sets the value of the weight (Vg2) for the data dimension. In the figure, the weight is set to "10" for the data dimension "mm". When input, the input data editing function 11 causes the data dimension definition file 46
Write to the data of.

On the data dimension registration screen shown in FIG. 13, the user can select the memory address "M100", data name,
Set the data dimension. In the figure, the logic element has related information in the memory address “M100”, the data name is “speed command”, and the dimension of the data is “digi”.
It is set to be "t". When input, the input data editing function 11 writes the input data in the data dictionary 510 of the lower specification file 31.

In the data dimension conversion rule registration screen shown in FIG. 14, the user sets the result data dimension when the first data dimension and the second data dimension are calculated for each. In the figure, for the logic element with the logic element ID “ID3”, the first data dimension is “digit”,
It is set that the result data dimension becomes "cm" when the second data dimension is "cm / digit". When input, the input data editing function 11 writes the input data in the data dimension conversion rule file 45.

As described above, by inputting the data dimension conversion rule, it becomes possible to synthesize one data dimension from two or more data dimensions.

Although not shown in the figure, this embodiment
Further, in response to the user's request, the data of the lower specification file 31 is displayed on the display device 55, and the modification result of the specification input by the user to the lower specification is displayed as the lower specification file 31.
You can also write in.

(II) System Configuration of Specification Creation Device and Data Structure for Specification Creation Next, the specification creation device according to the third embodiment of the present invention will be described with reference to FIGS. 4 and 26 to 29. The system configuration and the data structure for creating specifications will be described. FIG.
It is a schematic diagram of a functional block and a data file of a specification creating apparatus according to a third embodiment of the present invention. FIG. 26 is a schematic diagram showing the lower specification data 501 according to the third embodiment of the present invention. FIG. 27 is a schematic diagram showing the data dictionary information 510. FIG. 28 shows data dimension conversion rule data 51.
It is a schematic diagram showing 1. FIG. 29 is a schematic diagram showing the data dimension definition data 512. In the present embodiment, a data dimension analysis function 18 is added as a functional block to the first embodiment, and a data dimension conversion rule file 45 and a data dimension definition file 46 are added as data files.

Here, the data dimension analysis function 18 converts the dimension attribute of the data whose value is referred to / updated by the logic element included in the specification into the dimension displayed in the logic element of the upper specification. It is a function. The data dimension conversion rule file 45 holds information on a combination of data dimensions before and after processing for each type of logic element. The data dimension definition file 46 holds information on combinations of values (Vg2) related to the importance of data for each dimension of data.

The lower specification of the present embodiment internally holds data as specification data as shown in FIG. The data description method is the same as in the first embodiment.

Furthermore, in this embodiment, as the specification data input to the system, in addition to the above-mentioned logic element configuration data, reference and update of values are performed in the course of the processing of the target software as shown in FIG. There is data dictionary information 510 that holds the attribute information for each piece of data. The data dictionary information 510 includes a memory address 6a in which information used by software is stored and a data name 6
b, the value of dimension 6c of the data is held. For example, in the data dictionary information shown in FIG.
In the second record, the related information is the memory address "M10".
It means that the data means the value of “speed signal”, and the dimension of the data is “m / mim”.

This data dictionary information is held in the lower specification file 31, which is the same as the lower specification data 501.

The data dimension conversion rule data 511a and 511b shown in FIG. 28 are held in the data dimension conversion rule file 45. The data dimension conversion rule data 511a and 511b are the dimension 6c-1 of the first data referred to in the processing of the logic element and the second dimension 6c-1 referred to in the processing thereof.
Data dimension 6c-2 and result data dimension 6c-3 of the data generated as a result of the processing. That is, the result data dimension is held for each combination of the first data dimension and the second data dimension for each logic element.

Of these, the data 511a is a logic element for obtaining the result of multiplication of two data, that is, FIG.
It is the data dimension conversion rule for the logic element having the logic element ID “ID3” shown in FIG. This is "m / mi
The data obtained as a result of multiplying the data having the dimension of “n” and the data having the dimension of “mm / m” is “mm / mi
It has a dimension of "n". In addition, No. 511b data. 1 is a data dimension conversion rule for the logic element of "ID4" shown in FIG. In addition, 51
No. 1b of the data. 2 is a logic element that obtains the result of division of two data, that is, "ID
4 is a data dimension conversion rule for a logic element having a logic element ID of "4".

Data dimension definition data 5 shown in FIG.
12 is held in the data dimension definition file 45. The data dimension definition data 512 includes the data dimension 6c and the weight (Vg2) 6 related to the design process for each data dimension.
It is composed of the value of d.

(III) Processing Procedure of Specification Writing Method Next, a processing procedure of the specification writing method according to the third embodiment of the present invention will be described with reference to FIGS. 30 to 33 and 42. FIG. 30 is a schematic diagram showing the logic element record data 504 after the value setting according to the third embodiment of the present invention. FIG. 31 is a schematic diagram showing the path record data 515 after the value setting according to the third embodiment of the present invention. FIG. 32 is a schematic diagram showing the path record data 515 after the division flag is set according to the third embodiment of the present invention. FIG. 33 is a schematic diagram showing the upper specification data 500 according to the third embodiment of the present invention. FIG. 42 is a general flowchart showing the processing procedure of the specification creating method according to the third embodiment of the present invention.

In the following, the present embodiment will be specifically described by focusing on the part different from the first embodiment, assuming that the input described in (I) is performed.

The flowchart showing the flow of processing of this embodiment is obtained by adding steps 180 and 190 to the flowchart of the first embodiment shown in FIG.

First, the user inputs the information regarding the logic element and its data dimension as described in (I). When there is an input, the input data editing function 11 writes the data in the predetermined format of the corresponding data files 31, 41 to 43, 45, 46 (step 180).

Next, the data relation analysis function 12 between logic elements
Sets values in the logic element record data 504 and the path record data 515 to be written in the logic element connection data file 44 (step 110). The values are set in the examples shown in FIGS. 30 and 31. The data format of this embodiment is the same as the path record data 515 of the first embodiment, with columns for data dimension "dimension" 6d and data attribute "weight" 5g3 added. The processing of data other than those is the same as that of the first embodiment.

Next, the data dimension analysis function 18 analyzes the dimension of the data to be updated as a result of the processing of each logic element in the specification, and the result is the data attribute of the path record data 515 of FIG. "Dimension" 6d and the data of "weight" 5g3 of the data attribute are set (step 190).

That is, the data dimension analysis function 18 determines the dimension (dimension A) of the data updated as a result of the processing of the logical element connected before the logical element for the logical element registered in the logical element record file 504. And the result data dimension (dimension C) that matches the dimension (dimension B) of the data of the memory address referenced by the logic element.
Create Specifically, it is selected from the data dimension conversion rules 511 held in the result data dimension conversion rule file 45, and this dimension C is set as the data attribute. Set it to dimensions 515-6d. In addition, the data dimension analysis function 18 searches the data dimension definition file 46 for the weight (Vg2) corresponding to the dimension C, and if there is this value, sets it as the data attribute.
The weight is set to 515-5g3. If the value of the weight corresponding to the dimension C is not in the data dimension definition file 46, the data dimension analysis function 18 sets “0” as the default value of the weight corresponding to the dimension C to the path record file 5
15 data attributes. The weight is set to 515-5g3.

Although the above is the processing concerning the data dimension, the data dimension analysis function 18 corresponds to the data dictionary 510 of the lower specification file 31 when the processing of the logic element is the data updating processing for the memory. The value of the data dimension 510-6c of the data at the memory address 510-6a is rewritten to the dimension C.

Here, the dimension A is the data attribute of the record of the path with the logic element connected before each logic element in the path record file 515. Dimension 515-6
It is a d value, and the dimension B can refer to the data dictionary 510 of the lower specification file 31.

Through the processing of step 190 described above, the data dimension to be referenced / updated and its weight can be set by the logic element during the processing of the specification.

Next, in step 120, the inter-logic element division point determination function refers to the path record file 515 of the logic element connection data file 44 and sets the division point between the logic elements. That is, by this process, the division flag is set in the path record file as shown in FIG. This processing is the flowchart of FIG. 38 of the first embodiment, the path record file is changed from 505 to 515, and the judgment processing of step 1203

[0224]

[Expression 4] Data attribute. The determination of weight (515-5g3)> V is added. The other processes are the same as those in the first embodiment.

Further, the processing contents of steps 130 and 140 in FIG. 34 are the same as those in the first embodiment.

By this processing, the division flag is set in the path record file as shown in FIG.

The upper specification data 500 of FIG. 33 generated as a result of the above processing is written in the upper specification file 32.

(IV) Features of this Embodiment As described above, according to the specification creating apparatus of this embodiment, the importance of the data handled in the course of processing the logic elements in the specifications is different. In this case, weighting is applied according to the dimension of each data. That is, by further using the attribute of the data referenced / updated by the logic element, the weight between the logic elements is set in more detail, and the division point between the logic elements is determined based on the detailed weight, thereby further utilizing the weight. It is possible to automatically generate specifications for higher-level processes that meet the needs of the user to know the data, and improve the work efficiency of the user. Further, according to the present embodiment,
By having the step of editing the definition of the logic element and the abstract logic element conversion rule, it is possible to improve the operability of the user.

[0229]

According to the present invention, when the specification of the upstream process is generated from the software specification of the downstream process, it is possible to finely specify the level of the description content of the high-order specification, and the user's needs. It is possible to provide a specification creating method and apparatus suitable for the specification.

Further, according to the present invention, there is provided a specification creating method and apparatus capable of creating a specification of an upstream process having a layout that is in harmony with the size of paper when printing the created specification. You can

Further, according to the present invention, attention is paid to the importance of the data output by each process, and it is possible to confirm how the important data is processed in the process of the upstream process, and a specification creating method and apparatus. Can be provided.

[Brief description of drawings]

FIG. 1 is a schematic diagram of functional blocks and data files of a software design support device according to a first embodiment of the present invention.

FIG. 2 is a schematic diagram showing a hardware configuration of a software design support apparatus according to the first embodiment of the present invention.

FIG. 3 is a schematic diagram of functional blocks and a data file of a specification creation device according to a second embodiment of the present invention.

FIG. 4 is a schematic diagram of functional blocks and a data file of a specification creation device according to a third embodiment of the present invention.

FIG. 5 is a diagram showing a lower-level specification which is input to the specification creating apparatus according to the first embodiment of the present invention.

FIG. 6 is a diagram showing a high-level specification document which is an output of the specification document creating apparatus according to the first embodiment of the present invention.

FIG. 7 is a diagram illustrating a case where a paper size and the number of sheets are input on a parameter setting screen.

FIG. 8 is a diagram showing a high-level specification document that is an output of the specification document creating apparatus according to the second embodiment of the present invention.

FIG. 9 is a diagram showing a lower-level specification which is input to the specification creating apparatus according to the third embodiment of the present invention.

FIG. 10 is a diagram illustrating a case where a weight value is input on a logic element weight setting screen.

FIG. 11 is a diagram showing that the association between a logic element and an abstract logic element is registered on the abstract logic element registration screen.

FIG. 12 is a diagram showing that the data dimension and the weight are input in the data dimension definition screen.

FIG. 13 is a diagram showing that a memory address, a data name, and a data dimension are input on the data dimension registration screen.

FIG. 14 is a diagram showing that a logic element, a first data dimension, a second data dimension, and a result data dimension are input on the data dimension conversion rule registration screen.

FIG. 15 is a diagram showing a subordinate specification which is an input of the specification creating apparatus according to the third embodiment of the present invention.

FIG. 16 is a schematic diagram showing lower specification data 501.

FIG. 17 is a schematic diagram showing logic element detailed data 502a.

FIG. 18 is a schematic diagram showing abstract logic element related data 502b.

FIG. 19 is a schematic diagram showing abstract logic element conversion rule data 503.

20 is a schematic diagram showing logical element record data 504. FIG.

FIG. 21 is a schematic diagram showing the path record data 505 according to the first embodiment of the present invention.

FIG. 22 is a schematic diagram showing pass record data after setting values according to the first embodiment of the present invention.

FIG. 23 is a schematic diagram showing high-level specification data 500 according to the first embodiment of the present invention.

FIG. 24 is a schematic diagram showing path record data 505 according to the second embodiment of the present invention.

FIG. 25 is a schematic diagram showing upper specification data 500 according to the second embodiment of the present invention.

FIG. 26 is a schematic diagram showing lower specification data 501 according to the third embodiment of the present invention.

27 is a schematic diagram showing data dictionary information 510. FIG.

FIG. 28 is a schematic diagram showing data dimension conversion rule data 511.

29 is a schematic diagram showing data dimension definition data 512. FIG.

FIG. 30 is a schematic diagram showing logical element record data 504 after setting values according to the third embodiment of the present invention.

FIG. 31 is a schematic diagram showing the path record data 515 after the value setting according to the third embodiment of the present invention.

FIG. 32 is a schematic diagram showing the path record data 515 after the division flag is set according to the third embodiment of the present invention.

FIG. 33 is a schematic diagram showing the upper specification data 500 according to the third embodiment of the present invention.

FIG. 34 is a general flowchart showing an outline of a processing procedure of a specification creating method according to the first embodiment of the present invention.

FIG. 35 is a detail flowchart showing the processing procedure of step 110 for analyzing the data of the logic element in the lower specification.

FIG. 36 is a detail flowchart showing the processing procedure of step 111 for analyzing the next logical element relationship.

FIG. 37 is a detail flowchart showing step 115 of analyzing a reference memory.

FIG. 38 is a step 1 of selecting a path dividing point between logic elements.
It is a detail flowchart which shows 20.

FIG. 39 is a detail flowchart showing step 130 of converting a logic element included in a divided section into an abstract logic element.

FIG. 40 is a detail flow chart showing step 1304 of converting to an abstract logic element and writing to a file.

FIG. 41 is a general flowchart showing an outline of a processing procedure of a specification creating method according to the second embodiment of the present invention.

FIG. 42 is a general flow chart showing a processing procedure of a specification creating method according to the third embodiment of the present invention.

[Explanation of symbols]

1 ... Specification document, 2 ... Logic element, 3 ... Reference memory address, 4 ...
Paths, 5 ... Data file columns, 11-18 ... Functional blocks, 31, 32, 41-46 ... Data files, 5
1 ... CPU, 52 ... Memory, 53 ... External storage device, 54
... input device, 55 ... display device, 100, 110, 11
1, 115, 120, 130, 140, 1111-11
24, 1151-1116, 1201-1205, 13
01-1312, 1351-1363 ... Processing step,
500-515 ... Each data.

─────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] June 29, 1995

[Procedure Amendment 1]

[Document name to be corrected] Drawing

[Correction target item name] All drawings

[Correction method] Change

[Correction content]

[Figure 5]

[Figure 6]

FIG.

[Fig. 2]

[Figure 7]

[Figure 8]

[Figure 9]

FIG. 11

[Fig. 12]

[Figure 3]

[Figure 10]

[Fig. 13]

FIG. 14

FIG. 19

FIG. 29

[Figure 4]

FIG. 15

FIG. 16

FIG. 17

FIG. 18

FIG. 20

FIG. 21

FIG. 22

FIG. 23

FIG. 25

FIG. 24

FIG. 26

FIG. 27

FIG. 28

FIG. 30

FIG. 31

FIG. 32

FIG. 33

FIG. 34

FIG. 35

FIG. 38

FIG. 36

FIG. 37

FIG. 39

FIG. 40

FIG. 41

FIG. 42

 ─────────────────────────────────────────────────── ─── Continuation of front page (72) Inventor Yoshiteru Miyasaka 5-2-1 Omika-cho, Hitachi-shi, Ibaraki Hitachi Ltd. Omika factory

Claims (18)

[Claims] 1. A description rule of a specification for describing a series of processes is defined by a logic element that describes a processing unit and a sequence in which the logic element is connected, and the logic element is divided into small levels. From the specified lower specifications, combine the logic elements of those lower specifications,
In the specification creation method, in which the logic element is converted to a semantically equivalent logic element and the logic element is divided into larger levels, the level of the logic element of the created high-level specification is made variable. A method for creating specifications, which is characterized in that 2. The variable level is determined by a value (V1) of abstraction degree requested by a user or a paper size value (Vs) of a specification.
How to create the described specifications. 3. The value (V) of the degree of abstraction requested by the user (V)
l) or an abstraction parameter setting step including a process of setting the size value (Vs) of the specification, and (2) a dividing point setting step including a process of setting a dividing point between the logic elements of the lower specification. (3) An abstract logic element selection step including a process of selecting another predetermined logic element according to a combination of logic elements between a start point and an end point of a division point of a section formed by the division points, (4) A logic element reconfiguring step of converting a logic element in this section into another selected logic element to generate data of a high-order specification, and (1) to (4) above. The method of claim 2, wherein each step is performed in this order. 4. The division point setting step (2) compares the weight (Vg1) predetermined for each type of the logic element with the magnitude of the abstraction value (Vl) requested by the user. 4. The method according to claim 3, further comprising the step of setting division points between the logic elements based on the result. 5. When the logic element reconfiguring step (4) reconfigures the logic element to generate the data of the high-order specification, the size required to display the high-order specification generated ( Vs ′) is generated, and (5) this Vs ′ is compared with the size of the size value (Vs) of the specification required by the user, and the value of the abstraction parameter ( Vl) is included in the abstract parameter changing step, and step (5) is performed after each of the steps (1) to (4) to change the value (V1) of the abstract parameter. 4. The specification creating method according to claim 3, wherein if there is, the steps (1) and (2) are performed again. 6. A description rule of a specification describing a series of processes is defined by a logic element that describes a processing unit and a sequence in which the logic element is connected, and the logic element is divided into small levels. From the specified lower specifications, combine the logic elements of those lower specifications,
In a specification creating method for converting a logical element into a semantically equivalent logical element and creating a high-level specification document in which the logical element is divided into larger levels, data data handled by the processing described in each of the logical elements A method of creating specifications, characterized in that the division point is determined according to the data dimension in which the logical elements of the created upper specification are specified, focusing on the dimensions. 7. A combination of data dimensions of one or more data handled by the process described in each of the logic elements is converted into a data dimension after execution of the process described in the logic element for each of the logic elements. 7. The method for creating a specification according to claim 6, further comprising a step of analyzing data between logic elements including a process of performing. 8. The weight (Vg) of the predetermined data dimension
7. The method according to claim 6, further comprising the step of comparing 2) with the magnitude of the value (Vl) of the degree of abstraction requested by the user, and setting a division point between the logic elements based on the result. How to create specifications. 9. What kind of data dimension is a predetermined weight (Vg1) for each type of the logic element of the lower specification, a weight of the data dimension (Vg2), or a combination of the data dimensions? And a weight (Vg1) that is predetermined for each type of the logic element that has been input, or the weight of the data dimension (Vg
2), or a definition file that holds information about what kind of data dimension the combination of the data dimensions is converted into, and by the means for inputting them, in advance for each kind of the input logic element. The definition file holds information on what kind of data dimension the defined weight (Vg1), the weight of the data dimension (Vg2), or the combination of the data dimensions is converted into, and the specification file 9. The specification creating method according to claim 4, claim 7 or claim 8, wherein the held values or information are used when creating. 10. A logic element for describing a processing unit,
The description rule of the specification that describes a series of processes is defined by the sequence in which the logic elements are connected, and the logic elements of the sub-specifications are selected from the sub-specifications in which the logic elements are divided into small levels. A combination of
In a specification creation device that creates a higher-level specification in which logic elements are converted into semantically equivalent logic elements and the logic elements are divided into larger levels, the level of the logic elements in the higher-level specification created is made variable. A specification creation device characterized in that 11. The variable level is determined by a value (V1) of abstraction level requested by a user or a sheet size value (Vs) of a specification.
Specification writing device described in 0. 12. An abstraction level value (Vl) requested by a user
Alternatively, abstraction parameter setting means including means for setting the size value (Vs) of the specification, division point setting means including means for setting division points between the logic elements of the lower specification, and the division points Abstract logic element selection means including means for selecting another predetermined logic element according to the combination of logic elements between the start point and the end point of the division point of the possible section, and the logic element in this section The specification creating apparatus according to claim 11, further comprising: a logic element reconfiguring unit that converts the selected logic element into another logic element and generates data of a higher specification. 13. The division point setting means compares a predetermined weight (Vg1) for each type of the logic element with a magnitude of an abstraction level value (Vl) requested by the user, and the result is obtained. 13. The specification creating apparatus according to claim 12, further comprising means for setting a division point between the logic elements based on the above. 14. The size (Vs) required for displaying the generated upper specification when the logical element reconfiguring unit reconfigures the logical element and generates the data of the upper specification.
′) Is generated, Vs ′ is compared with the size value (Vs) of the specification required by the user, and the value (Vl) of the abstraction parameter is changed based on this result. 2. An abstraction parameter changing means including a means for performing is provided.
2. Specification creation device described in 2. 15. A logic element that describes a processing unit,
The description rule of the specification that describes a series of processes is defined by the sequence in which the logic elements are connected, and the logic elements of the sub-specifications are selected from the sub-specifications in which the logic elements are divided into small levels. A combination of
In a specification creating device that creates a higher-level specification document in which logic elements are converted into logically equivalent logic elements and the logic elements are divided into larger levels, the data data handled by the processing described in each of the logic elements A specification preparation device characterized in that the division point is determined according to the data dimension in which the logical element of the higher specification to be created is specified, focusing on the dimension. 16. A combination of data dimensions of one or more data handled by the processing described in each of the logic elements,
16. The specification creating device according to claim 15, further comprising: inter-logical element data analysis means including means for converting each of the logical elements into a data dimension after execution of processing described in the logical element. 17. A predetermined weight of the data dimension (V
16. The method according to claim 15, further comprising the step of comparing g2) with the magnitude of the value (Vl) of the degree of abstraction requested by the user, and setting a division point between the logic elements based on the result.
Described specifications creation device. 18. What kind of data dimension is a predetermined weight (Vg1) for each type of the logic element of the lower specification, or a weight of the data dimension (Vg2), or a combination of the data dimensions? And a weight (Vg1) that is predetermined for each type of the logic element that has been input, or the weight of the data dimension (Vg
2) or a definition file that holds information about what kind of data dimension the combination of the data dimensions is converted into, and
6. The specification creation device according to claim 6 or claim 17.