JPH0475135A - Program developing device - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a program development device, and particularly to a program development device that creates an executable program from a specification description.

[Prior Art] Conventional program development devices using general programming languages such as C language and FORTRAN are equipped with a function to register part or all of a program created by a user as a component in a library. There is. In such a program development device, each component is registered in a library in the form of a function. Therefore, the user can reuse the registered component by calling the registered component in the form of a function. Additionally, the user can update or delete the contents of registered parts. Furthermore, users can also reuse programs created by other users.

[Problems to be Solved by the Invention] In the conventional program development apparatus described above, the parts registered in the library can be reused by calling the parts in the form of a function. However, with conventional program development equipment, it is not possible to manage the functional specifications and input/output interfaces of each component registered in a library.
Management of the functional specifications of each component is left to the user.

Even the person who created the program may forget the functional specifications of the program over time, and the registered parts may no longer be reused. Therefore, when registering a program that a user has created as a component, the user must create a functional specification for the component in an environment separate from the program development environment of the program development device and save it. .

An object of the present invention is to facilitate the reuse of programs developed by users in a program development apparatus that creates executable programs from specification descriptions.

[Means for Solving the Problems] A program development device according to the present invention includes a specification description means;
It includes a conversion means and a parts management means.

The specification description is for the user to create a graphical specification description of the target program on the screen. The conversion means converts the specification description created by the specification description means into an executable program.

The parts management means has a function of registering the specification description created by the specification description means as part information and a function of presenting the registered parts information.

[Operation] According to the program development device according to the present invention, a specification description created by a user can be registered as part information. Further, the registered parts information can be presented. Therefore, the user can refer to registered component information at the level of specification description. It is also possible to convert registered component information into an executable program.

Therefore, the user can easily know the functional specifications of the registered parts and can easily reuse the registered parts.

[Example] Hereinafter, an example of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing the overall configuration of a program development apparatus according to an embodiment of the present invention.

This program development device includes a plurality of graphical editors E1 to En having drawing/editing functions according to different expression formats, and a main body device 1 that creates a program according to a specification given by a user.

The main device 1 includes an input/output device 10. It includes a mutual conversion device Cv, an execution device EX, a component management device CP1, an integrated file management device UF, and a display device DP.

Each of the graphic editors E1 to En is preferably realized by an independent process, and each of the graphic editors E1 to En can communicate with the main device 1. Here, figure editor E1~
The communication between each En and the main device 1 is as follows.
This is because, in consideration of ease of program development and future functional expansion, the processes of the graphic editors E1 to En are connected to the main unit 1 through interprocess communication using, for example, sockets.

The representation formats provided by the graphic editors E1 to En include a graphic representation format and a non-procedural description format.

The graphic representation format includes representation formats such as a functional block diagram and a sequence chart.

As shown in FIG. 2, a functional block diagram is an expression format that expresses the connection relationship between modules (units that have a sense of unity in software).

FIG. 2 is a diagram showing an example of a specification description format using a functional block diagram. In FIG. 2, the external module 10
A data connection relationship between the internal module 11 and the internal module 11 is shown. The external module 10 is a module that expresses an external function that is not subject to specification description. The internal module 11 is a module that expresses a function to be specified. A data arc 12 defines the flow of data between the external module 10 and the internal module 11 together with the input/output ports P1 to P4.

This internal module includes primitives and parts (partially completed specification descriptions, registered in files).

The sequence chart is a diagram showing the causal relationship of input/output data, the relationship of data transmission/reception between modules, etc., as shown in FIG. In FIG. 3, the external module 10
3 shows the flow of data between the internal module 11 and the internal module 11. In this sequence chart, a module and its port are indicated by a single order line (vertical line). The sequence line indicates the time axis and also represents the temporal relationship in which signals flow. The data flow between this module 10.11 is represented by signal line 13. This signal line 13 indicates data connections and causal relationships between modules.

Non-procedural description formats include expression formats shown in tabular formats such as relational tables and decision tables. The relational table shows the relational data structure as shown in FIG. In Figure 4, the relationship table is
An area 14 that displays the name of the table, an item name area 15 that displays the names of the items included in this table, and the data type of the item (int (integer), float (floating point), and String) );
It includes an area 17 where the actual data values of the items are input and output.

The decision table, as shown in FIG. 5, is an expression format representing the selection structure of processing. In FIG. 5, the decision table is divided into an area 18 for displaying the name of the decision table module, an area 19 for displaying judgment conditions, an area 20 for displaying the name of the process to be executed as a result of the judgment, and judgments regarding the conditions. and an area 22 that displays a judgment indicating whether or not to execute a process based on a condition judgment.

In addition to the above-mentioned representation formats, available representation formats include data block diagrams showing data inclusion relationships, and table operation diagrams showing structure data processing centered on relational operations.

FIG. 6 shows an example of the representation format using a data block diagram, and FIG. 7 shows an example of the representation format of the table manipulation diagram.

In FIG. 6, the data block diagram includes a data set name area 23, an area 24 that displays the number of elements included in the data in this area 23, and a member data name or lower order that constitutes the member of the data set in the area 23. An area 26 that displays the data set name of the hierarchy and the data type of member data (int, float, string, 5tru
ct). This area 24 is described only when the data has an array structure. Data type is 5t
In the case of ruct, this data indicates that it is hierarchical with respect to the lower level. Each data is AND connection 27
Or, the connection relationship is indicated by an OR connection 28.

The table operation diagram shown in FIG. 7 shows, as an example, a state in which relational tables 81 and B2 are processed according to a predetermined operation to form a new relational table B3. This operation is called a merger operation. The operations in the table operation diagram are not limited to this merging operation, but include various relational operations, classification operations, calculation operations, and the like. Relational operations are operations that manipulate tables to satisfy certain relationships. The classification operation is an operation of rearranging the rows of a table according to a predetermined order, such as alphabetical order or numerical order.

A calculation operation is an operation to obtain a calculation result such as a total value or an average value for a specific column of a table.

Returning to FIG. 1, the main device 1 combines information obtained from the graphical specification descriptions generated by the user using the graphic editors E1 to En to create construct information that includes control information necessary for program execution. a mutual conversion device Cv that generates the information, mutually converts information between graphic specification descriptions having different expression formats, and generates basic information between module hierarchies and presents it to a user; and a mutual conversion device cV.
An execution device EX that interprets and executes a program according to the construct information generated by the program and presents the execution results to the user, graphic editors E1 to En for describing graphic specifications, mutual conversion device Cv1, an execution device EX, and a parts management device CP. Input/output device 1 that manages communication for exchanging information with
0. and an integrated file management device UF that integrally manages data structures handled by each processing device EX and CV1CP.

The component management device CP registers a partially completed specification description in software as a "component" and manages operations for reusing the registered "component".

The construct information is information obtained by converting the generated specification description information so as to correspond to the operation method of the processing model including the control structure. A data-driven model is used as an example of this processing model. In order to use this data-driven model as a processing model, it is necessary to generate control nodes and control arcs. In the construct information, nodes are associated with modules of specification description information, and arcs are associated with data connections between modules.

The input/output device 10 has functions of an interface with a user, execution control of each processing device based on instructions from the user, and management of data exchanged between the processing devices.

The interface with the user includes the following:

0 Specification description in expression format using diagram/shape editor,
■ Display of mutual conversion results, ■ Pair addition function, ■ Citation function,
Includes ■prototyping function, ■parts registration/reuse, and ■document output.

The following methods can be used to describe specifications in each expression format using a graphic editor.

(a) The user specifies the type of expression format and the name of the specification description. This specification description name is specified when reusing an already registered specification description, and when creating a new specification description, a new specification description name is input.

(b) Specify graphical elements and expression formats in the existing specification description in order to make the already written specification more detailed or to proceed with the description in a hierarchical manner.

In this case, specifications are written using an expression format corresponding to the designated graphical element.

Specifications can be written for the same module in different expression formats. In this case, the mutual conversion device CV informs the editor of the corresponding expression format according to the internal mutual conversion rule table search, and this corresponding converted expression format is displayed to the user. Since one specification description can be executed using different expression formats, it becomes easier to understand the description contents from multiple aspects, and it becomes possible to create a more complete specification.

The association function is a function that associates semantically equivalent information (for example, data or function modules) between different expression formats. This function is required to interrelate various types of independently written specification information in order to sequentially integrate specifications written according to various expression formats.

That is, as shown in FIG. 8, the module M7 expressed in a functional block diagram can also be expressed using an operation table diagram. Module M7 represented in this table operation diagram
and M7 shown in the functional block diagram are semantically equivalent. In this case, the modules M7 expressed in different expression formats are related to each other as being semantically the same, as indicated by the arrows in the figure. This operation is called a "matching" operation.

Furthermore, each expression format may share information with each other. In this case, the amount of work during writing can be reduced by quoting the already written specification information when writing in another expression format.

This use of information written in one expression format in another expression format is called "quotation." For example, the module M10 shown in a relational table as shown in FIG. 8 is the same as the table M10 expressed in a table manipulation diagram. In this case, as shown by the arrow in the figure, the table MIO of the relational table is cited when describing in accordance with the expression format in the table operation diagram. Similarly, table M8 in the table manipulation diagram is the same as table M8 expressed as a relational table.

In this case as well, M8 expressed in the relational table is cited when writing in accordance with the expression format of the table manipulation diagram.

The prototyping function is a function for checking the execution results of partially completed specification descriptions. In this prototyping, the execution results of the specification description can be confirmed independently for each layer. The user specifies input/output data and creates input data during prototyping according to the specified data structure.

The interface for parts registration/reuse instructs the parts management device CP to register parts and use the registered parts.

The document output function outputs graphical specification descriptions written for each expression format to a printer as a hard copy for specification descriptions written using various expression formats, and can be used as is as a software design document. possible.

The interface between the input/output device IO and each processing device will be explained. First, the interface with the graphic editor will be explained.

The input/output device IO controls the startup and termination of various graphic editors designated by the user. It also manages information required when starting and terminating the editor, such as the name of the input specification description and the type of graphic editor. This operation includes:

(a) When the user specifies the type of expression format and the name of the specification description, the input/output device 10 activates the graphic editor corresponding to the specified expression format, and at the same time changes the name of the specification description to this activation. Pass it to the created shape editor.

(b) Each graphic editor is provided with a function for starting other graphic editors. The input/output device is notified of the graphical element (graphical element included in the operation tool displayed by the editor) specified in an editor and the type of expression format. The type and shape of the symbol of this graphic element differs depending on the type of expression format. The input/output device 10 activates a graphic editor corresponding to the specified expression format, and sends the specified graphic element to the activated graphic editor.

(c) Termination control of specification description. Each graphic editor is equipped with a termination operation tool. This termination operation tool notifies the input/output device 10 of termination of the graphic editor. In response to this termination notification, the input/output device 0 saves information such as the name of the created specification description and the type of editor, and then terminates the graphic editor that notified the termination.

The input/output device IO also provides an interface with a graphics editor and interconverter. When describing specifications using various expression formats, or when using multiple specification descriptions mutually, the input/output device 10 performs the following processing with the graphic editor and the mutual conversion device CV.

(a) The drawing information described by the user is sequentially sent to the mutual conversion device Cv via the input/output device IO at the stage when each graphic element is described. The mutual conversion device is this input/output device 10
The data is returned to the output device IO, which has undergone a predetermined process (described later) in accordance with the information given from the user.

In this case, the returned data is specification information that can be expressed in a different expression format corresponding to the input specification description information. The data returned from the mutual conversion device Cv is attached with an identifier ID of the specification description of the return destination together with the processing result. The input/output bag 51FIO specifies the specification description corresponding to this identifier ID, and returns the processing result formed by the mutual conversion device Cv to the destination graphic editor. Further, when the mutual conversion device Cv detects a contradiction in the input specification description, the input/output device 10 presents a message indicating the detection of this contradiction to the user.

(b) The input/output device 10 determines whether or not the two graphic elements specified by the user on the two graphic editors in the specification writing process can be logically correlated. .

If the correspondence is possible, the input/output device 10 returns the same logical specification information to both graphic editors. If the correspondence is not possible, a message indicating this inability is presented to the user.

(c) Quotation When quoting specification information between multiple graphic editors, the input/output device ■0 transfers the drawing information and specification information of the graphic element specified by the user on the graphic editor to the quotation light graphic editor. .

Next, the interface between the input/output device 10 and the execution device EX will be explained. Input data information and position information of input/output data required during execution (for example, prototyping) of the execution device EX are transmitted from the graphic editor to the input/output device IO in the same manner as when writing specifications. The input/output device 10 has an execution handler (
(not shown). When this preprocessing is completed, the input/output device IO starts the execution device EX in response to an execution start instruction from the user. The execution result data is sent from the above-mentioned execution handler to the input/output device IO.
is displayed on the display device DP via. This display device D
The display on P is executed, for example, by activating an output result display routine.

The interface between the input/output device 10 and the parts management device CP includes the following.

(a) Interface when registering parts When the specification description created by the user is partially completed, the specification description information and part name of the registration target specified by the user are sent to the parts management device cp via the input/output device IO. transmitted to.

(b) Interface when reusing parts The part name specified by the user on the graphic editor is transmitted to the parts management device CP via the input/output device IO. The component management device CP searches for component information corresponding to the given component name via the file management device UF, and returns the searched component information to the activated graphic editor via the input/output device IO.

If the user wants to refer to parts information, input/output device I
When O starts the parts specification display routine based on instructions from the user, this graphically expressed parts information is displayed on the display device DP.

The functions of the mutual conversion device CV will be explained. This mutual conversion device CV integrates the contents of specification descriptions written by users using various colloquial expression formats to generate an effective executable program, and also converts specific aspects of a given specification description ( It has the function of converting information acquired from one representation format or hierarchy into another representation format. Here, the executable program is a program obtained by converting construct information having a structure dependent on a processing model (data-driven model) so as to match the execution method of the virtual machine.

FIG. 9 shows an example of the structure of the specification description information integrated by the mutual conversion device CV. This specification description information includes module information MI, sequence information SI, and data structure information DI.

The module information MI is information regarding the operations of individual modules constituting this software system and the data connections between the modules. This module information is
The hierarchical relationship between each module is generated based on the specification description using a functional block diagram. This module information also integrates data structure information through data connection relationships between modules. Module information is functional module,
Contains information regarding the decision table module and structure data manipulation module, respectively. The information of each module corresponds to processing contents that can be defined in each expression format of a functional block diagram, a decision table, and a table operation diagram expressed by the graphic editor. Each module will be explained below.

(A) Functional module: A functional module is information about internal submodules that constitute a module and information about data connection relationships between each submodule. Attributes included in the submodule information correspond to descriptive elements provided by the functional block diagram, and include primitives, parts, internal modules, files, branches, white canes, and the like. The hierarchical structure of modules is saved by attaching module IDs (identifiers) attached to modules whose submodules define detailed information.

Data connection relationships between modules are associated with arcs in the functional block diagram. This arc represents the relationship between the data producing submodule and the data consuming submodule. The data structure of data is managed by referring to data structure information using a data set ID.

(B) A decision table module is information that indicates information regarding a selection process based on information obtained from a decision table by a process executed based on a condition determination and a determination result.

The relationship between the content of each condition determination and the corresponding process to be executed is managed by the event ID.

(C) Structure manipulation module information is information that expresses information regarding structure data manipulation based on information obtained from the table manipulation diagram using data to be manipulated and operations that act on each data. The correspondence between the data to be operated and each operation is managed by the data ID and operation ID. The data structure of each data is Dataset I
It is managed by D by referring to data structure information.

Data structure information is information regarding the definition of the type and structure of data consumed/produced by the software system. The hierarchical relationship of the data structure is generated based on the description using the data block diagram. This data structure information is
It includes inclusive data structure information, relational data structure information, etc., and includes atom information as data without structure.

(A) Inclusive data information is information indicating the structure of data in an inclusive/exclusive relationship. This included data information is
For each component data, the hierarchical relationship of the data structures is preserved by having a data set ID given to the data structure that defines the detailed structure.

(B) The relational data structure is information indicating the basic data type of each item data that constitutes the relational data.

(C) Atom information is information indicating the basic data type (int, float string) regarding atom data.

The sequence information includes attributes of the sequence line and information on signal lines output to the sequence line. In this sequence information, since it is possible to define a plurality of sequences for one module, these relationships are managed using sequence IDs.

(A) Sequence line information is information indicating attributes related to vertical lines representing submodules in the sequence chart. The attributes of the sequence line include internal modules, files, etc., and each corresponds to a descriptive element of the sequence chart. Correspondence with submodules in module information is managed by module sub-ID.

(B) Signal line information is information indicating data connections between sequential lines (hereinafter referred to as signal lines) in the sequence chart. This signal line information also shows the causal relationship of the human data by managing the information of the a sequence group that is connected to the human power of the signal line and outputted at the same time. Correspondence with data dependence in module information is managed by arc ID.

As described above, the relationships between each piece of information constituting the specification description information are all managed by the identifier ID. As mentioned above, this identifier ID includes a dataset ID that identifies data structure information, a module ID that identifies module information, a module sub-ID that identifies internal sub-modules that make up the module, and a data connection between internal sub-modules. Contains the arc ID etc. Every time new information is added, the mutual conversion device CV adds a new confusant ID.
Generate and manage.

As shown in Figure 9, in the structure of the main descriptive information,
Specification contents described using multiple graphic editors are hierarchical, and include data reference relationships 32, module hierarchical relationships 33, and common definition information relationships for the same module 34.
including. Therefore, by using these relationships as a basis, specification description information for the entire target software system can be generated from partial specification descriptions defined in a plurality of different expression formats.

Specification description information that integrates each piece of information obtained using these individual expression formats is managed by the identifier ID as described above.

Examples of the data structure of specification description information obtained by integrating information obtained from such individual expression formats are shown in FIGS. 10 to 15.

Figure 10 shows the data structure in the specification description, Figure 11 shows the structure of sequential line information, and Figure 12 shows the structure of signal line information.
FIG. 13 shows the structure of relational data, FIG. 14 shows the structure of included data, and FIG. 15 shows the structure of atoms. In the structure of the specification description information shown in FIGS. 10 to 15, by referring to the identifier ID attached to each piece of information, the presence or absence of correspondence and the presence or absence of change are determined.

FIG. 16 is a flow diagram showing the operation of the mutual conversion device.

Hereinafter, the operation of this mutual conversion device Cv will be briefly explained with reference to the operation flow diagram of FIG. 16. Generation of specification description information is performed based on communication with the editor via the input/output device IO.

In step S1, the editor or input/output device 10
Data is given from. This data is specification description information, end command information, specification description creation start information, etc. If it is determined that the given information is an end command (step S2), the mutual conversion device Cv performs desired processing such as closing the file, and then ends its operation.

In cases other than the end command, the mutual conversion device CV generates necessary specification description information according to the given data (step S4). The generated specification description information is used to access the file management device UF, and the contents of the specification description information file are updated with the generated specification description information (step S5).

On the other hand, the mutual conversion device CV generates construct information from the given specification description information (step S6). Regarding this generated construct information, the original construct information file is updated depending on whether the newly generated construct information is added or changed by accessing the file management device UF again.

Next, this mutual conversion device Cv searches for conversion rules that are stored in advance in the form of a table. By searching this conversion rule table, it is determined whether there is data that has the same meaning as the input data. That is, it is analyzed whether information given from a certain editor can be converted into an object in another quantitative expression format (for example, the correspondence between modules in a functional block diagram and vertical lines in a sequence chart) (step S9). If an object that can be converted to another representation format is found through this analysis, convert it into a corresponding graphical object that can be converted (step 510), and show the converted graphical object obtained as a result of this conversion. Send the data to the corresponding editor via the input/output device IO (step 511)
. The editor receiving the transmission at this time is an editor that can express this convertible object.

When all of this conversion processing is completed (step 512),
The mutual conversion device Cv again waits for a semantically organized graphical object to be sent from the editor or the input/output device.

In step S9, if there is no convertible graphical object, the mutual conversion device Cv notifies the input/output device 10 of this fact, and enters a state of waiting for data from the editor or the input/output device 10.

Here, when one semantically grouped graphical object is updated when the result data written by the user is input via the input/output device IO, the one grouped graphical object can interact with each other. It is sent to the conversion device CV.

Further, when a convertible graphical object is searched for in step S9, if a plurality of convertible graphical objects exist, a graphic editor is started that provides a representation format corresponding to each of the plurality of graphical objects. Ru. The graphical elements in the expression format provided by the simultaneously activated graphical editors are simultaneously displayed on the display device DP, for example, by a multi-window.

Next, an example of information exchange between the graphic editor and the mutual conversion device CV will be described with reference to FIGS. 17A and 17B. In the example shown in FIGS. 17A and 17B, there is a case where a graphic editor whose representation format is a functional block diagram is activated and the mutual conversion device Cv generates a specification description based on the representation format of the functional block diagram. Shown as an example.

In response to activation of a module definition or data structure definition editor by a user via the input/output device 10, the mutual conversion device Cv generates new module information or data structure information. The type of module or data to be generated is determined from the type of graphic editor activated. At the same time, the mutual conversion device c2 generates a module ID or data set ID for the generated module information or data structure information and transmits it to the activated graphic editor. In FIG. 17A, the module ID is transmitted to the graphic editor E. In FIG.

In figure editor E, when a user adds a new internal module on that editor, this figure editor E
transmits the undefined module sub-ID together with the transmitted module ID and information indicating the attributes of the module to the mutual conversion device CV.

In response to the given undefined module sub-ID, the mutual conversion device Cv generates an internal module, generates a module sub-ID for identifying this new sub-module information, and transmits it to the graphic editor E. do.

In the graphic editor E, when information regarding an existing internal module is changed or deleted in the functional block diagram, this change or deletion information is transmitted to the mutual conversion device CV together with the corresponding module sub-ID. In response to this information, the mutual converter CV changes or deletes the corresponding submodule information.

When a plurality of internal modules are generated, arcs indicating data connections between the internal modules are written on the graphic editor E. In response, the graphic editor E inputs the module sub-ID that identifies the module that sends the data, the port ID that indicates the data output port of this internal module, the destination module sub-ID that inputs the data, and the module that this destination module uses to input the data. The destination port ID identifying the receiving port and the undefined arc ID are transmitted to the mutual conversion device CV. The interconversion device Cv generates an arc in the internal module in response to the given information, and adds predetermined information to the given undefined arc to identify this arc.
It is transmitted as D to the graphic editor E. Next, when the data structure for the arc to be identified is specified by this arc ID, the graphic editor transmits the data set ID indicating this specified data structure together with the corresponding arc ID to the mutual conversion device C2. The mutual conversion device CV registers the data set ID according to this given information. Next, with reference to FIG. 17B, an explanation will be given of the operation when generating a module with a hierarchical structure.

For existing internal modules in the functional block diagram,
When the user starts another graphic editor to define the details of this existing internal module, the graphic editor that started it responds by adding a new module ID and module sub-ID. A lower module ID (undefined) for identifying the module is transmitted to the conversion device Cv. The conversion device Cv generates new module information in response to this given information, and adds the module ID of the upper module at that time to the generated module (lower module). Thereby, the lower module ID is determined. The module ID of this generated module (lower module) is transmitted to the editor activated to define its details, and is also transmitted to the editor that initiated this activation. After that, when the description for the lower module is completed, the activated graphic editor will send out the module ID, along with information to indicate it.
The module sub ID and lower module ID are transmitted to mutual conversion device C■.

In response to this information, the conversion device CV generates coupling information between the upper module and the lower module.

From the graphics editor on the activation side, information on the module ID corresponding to the lower module is sent to the mutual conversion device CV in accordance with the sequence of changing internal module information. Thereby, the hierarchical structure of module information is realized as a reference relationship from both upper and lower sides using this identifier ID.

The reference relationship between data and data structure information in data dependence of operations is realized as follows. When a correspondence relationship between an arc and a data structure description is established through the operation of pair addition in multiple graphic editors, the dataset ID acquired at that time is transmitted to the mutual conversion device Cv according to the change sequence of data dependency information. be done. This saves the structure of input/output data in the module, making it possible to extract the access sequence and lock range to the structure data.

As described above, by managing all the specification description information constituting each module, the identifier ID is used to manage the relationship between each piece of information.

An example of generating a specification description of the entire software system using this hierarchical representation will be explained.

FIG. 18 is a diagram showing an example of creating more accurate module information from this hierarchical structure information. As shown in FIG. 18, in the upper layer specification description 41, the content expressed as the data transmission/reception relationship between module FOO and module FOI is explained in detail by the lower layer of each module. 42 and 43,
By associating these in mutual conversion device CV, module FOO merges data a and data b to derive data C, while module FOI derives data C.
The structure that receives this, outputs data d, and returns this output d to module FOO is analyzed. As a result, the input/output data b and the data d of the functional module are the same data, and the repetitive structure 44 in which the data d is repeatedly used can be pressure-introduced.

The functional module P controls the operation of the functional module representing "merge" and the rTF gate that transmits data as is; the "authenticity determination gate". The details of this control become clear by using the lower modules for the functional module P.

FIG. 19 is a diagram showing an example of a configuration for generating construct information from a combination (specification description) of park expression formats, which is performed in this mutual conversion device. In the specification diagram 45 expressed as a functional block diagram, module P
Regarding S, it cannot be determined whether the operation content is simply data copying or selection structure.

However, by associating the descriptions 50 and 51 of the decision table with the respective modules P and S, the module P selects one of the modules F1 to F3 depending on the magnitude relationship of the input data x and y. The branching module S is controlled to control the branching module S.
In accordance with the data from module P, a structure for transmitting data b to any of modules F1 to F3 is determined. This determines the selection structure of the module P, and further enables generation of control information for branch control in the branch module S. This makes it possible to generate construct information 46 that includes control information for the processing model.

The above-described embodiment shows a case where information for generating a construct is obtained by integrating a plurality of expression formats. However, as shown in FIGS. 20 and 21, it is also possible to reversely generate (mutually convert) information in individual expression formats from the integrated information.

FIG. 20 is a diagram illustrating mutual conversion between a functional block diagram and a sequence chart. In Figure 20,
Internal module information 6 obtained from the functional block diagram 60
1 is converted into ordinal line information 62, and an ordinal line on the sequence chart is generated according to this ordinal line information. Here, the conversion from internal module information to sequential line information is performed in the mutual conversion device CV as described above, and this information is transmitted to a graphic editor whose representation format is a sequence chart, and this graphic editor is activated. , a sequence line on the sequence chart is generated on the display device.

In the following explanation as well, information is exchanged between this mutual conversion device and a graphic editor that expresses functional block diagrams and sequence charts.

Further, in the sequence chart 63, the internal module M2 is further added to the order line information 62 obtained from the sequence chart 60. This sequence line information indicating the newly generated internal module is converted to internal module information on the functional block diagram, and the internal module is generated on the functional block diagram. At this time, signal line information (signal lines A-D) obtained by forming signal lines in the sequence chart is converted into data dependency information.

As a result, an arc corresponding to the generated signal line is generated in the functional block diagram 64. This provides data flow between each module. However, the port connections are undefined in this newly generated functional block diagram 65 because the signal line information only indicates the flow of data and does not indicate which ports of the module are connected. A display 68 indicating this is given to the user. The user looks at this and defines the port.

In FIG. 20, an initial state 62 of the sequence chart is generated from information 60 obtained from the functional block diagram, and a description is added to the sequence chart 62 in the initial state, that is, generation of internal modules and data. A flow is attached, and the contents of the functional block diagram are generated and added according to the added sequence chart description 63 to obtain a new functional block diagram 65. In this case, in the newly formed functional block diagram, by presenting the incomplete part 68 in the functional block diagram where the port is undefined to the user, it is possible to prompt the user to write new information, making it more accurate. This makes it possible to construct a software system that is easy to use.

Furthermore, by using mutual conversion processing, lower layer information in the hierarchical description can be generated.

In the specification description shown in FIG. 21, a functional block diagram 72 is formed from the information expressed in the sequence chart 71, and a lower module 73 for module M1 and a lower module 74 for module M2 in this functional block diagram 72 are formed. ing. When a new sequence chart 75 is given to this mutual conversion configuration, that is, when a structure in which the module M1 receives data A from an external module and sends out data D is described, the mutual conversion device CV performs the following: The information obtained in this sequence chart 75 is added to the already given module 72. In this case, by detecting a match between the data ID and the data A, it is recognized that the module M1 receives the data A and derives the data B and D. From this structure, by considering the lower module 73 of the hierarchical representation, it can be seen that Ml has a branch structure in its lower structure and includes lower modules Mll and Ml2 that derive data B and data D, respectively. Detected. In this case, module M2
Since the relationship between data B and data C is preserved in the case of the sequence chart 71, its lower structure 78 has the same expression as the lower module 74.

Furthermore, when a new sequence chart 79 is created for the sequence chart 71 shown in FIG. 21, a functional block diagram is obtained according to the information acquired from this created sequence chart. In this case, by detecting the match of the data ID with respect to data B, if data A and data D have an exclusive data structure, it is determined that the lower module Mll that receives data A and the lower module Mll that receives data M2 have an exclusive data structure for module M1. A merge structure 80 is generated, which includes a module M12 and a lower structure that derives data B by merging the outputs of the modules Mll and M12.

Next, the functions of the execution device EX will be explained. Execution device E
X includes a conversion unit that converts construct information generated by the mutual conversion device Cv into an executable program according to the operation method of an execution model (virtual machine), and an execution unit that executes prototyping.

The executable format information obtained by converting the construct information includes connection information that expresses the flow of processing represented by the data flow and the structure of each process, and number links (various IDs) that appear in this connection information. It is broadly divided into constant information, data structure information, and file information. In this execution format information as well, connection information is grouped for each layer, and this node number is uniquely generated while maintaining a relationship in which corresponding ports are linked between layers. When the execution unit in the execution unit EX executes a predetermined specification, it tracks the connections of nodes and executes the program in sequence. Therefore, conversion into an information format suitable for this execution means conversion into an information format in which connection relationships between nodes are indicated by arc information attached to this node information.

Next, the operation of this execution device EX will be explained with reference to FIG. 23, which is an operation flow diagram.

In FIG. 23, the operation flow of the execution device EX is displayed using a sequence chart. The user specifies a data arc into which data on the specification description is to be input. A graphic editor corresponding to this specified data arc is activated, an input window is opened, and displayed on the display device DP. A template corresponding to the data structure of the specified data arc is displayed in the input window. Input data is set by filling this template. Setting the output data is the same as setting the input data, and when you specify the data arc whose data you want to monitor in the specification description, an output window is opened and a template corresponding to the data structure of the specified data arc is displayed.

This user-specified input data is input to the input/output device tIo.
, integrated file management device UF via mutual conversion device @CV
The data will be updated manually. When data update management is completed in this file management device UF, information indicating the completion is transmitted to the input/output device IO via the mutual conversion device Cv. When the user instructs the start of prototyping execution, this execution start instruction is sent to the input/output device.
0 to the execution unit EX. The execution device EX refers to the area in which the input data set in the manual window in the integrated file management device UF is written, reads this input data, and executes the program corresponding to the specified specification description.

The execution device EX reads input data from the integrated file management device UF, tracks the connections of the nodes included in the execution format information, sequentially executes the functions set in the nodes, and outputs the output data to the arc. Get the output data when When the execution device EX obtains the output data, it writes the output data to the integrated file management device UF. This updates the output data. When the integrated file management device notifies the execution device EX of the completion of this data update, the execution device EX then notifies the input/output device IO of the completion of prototyping.

When the input/output device [10 receives this execution completion, the conversion device NCv
Notify the end of execution. In response to the completion of this execution, the mutual conversion device CV refers to the output data written in the integrated file management device UF, reads out the output data, and transmits it to the input/output device 10.

The input/output device 10 displays the given output data on the display device jDP.
Display in the output window that was opened earlier.

As mentioned above, simulations targeting any hierarchy in the specification description can be executed by simply setting the input data and output data format, so the created specifications can be checked and reviewed. .

Next, the parts management device CP will be explained with reference to FIGS. 24 to 27.

A complete specification in a specification description is called a "part". This component is managed by the component management device CP.

The integrated file management device UF, as shown in FIG.
It includes an information area 110 in the specification description and a parts information area (parts information file) 120. Information area 1 in specification description
10 contains multiple specification files 11 corresponding to multiple specifications.
1 is stored. Each specification file 111 includes multiple modules 112. Each module 112 consists of specification description information 113 and construct information 114. On the other hand, the information in the parts information file 120 is classified into a plurality of groups 121 corresponding to the developed software. Each group 121 includes multiple user files 122. Each user file 122 includes a plurality of pieces of component information 123.

Each part information 123 consists of specification description information 124 and construct information 125.

Generally, different software to be developed requires different parts. Therefore, if component information is classified into groups for each developed software, the user does not have to look at component information of unrelated groups when referring to components. Furthermore, by classifying component information into user files for each user, it is possible to prevent unrelated users from viewing the user files.

The information area 110, specification file 111, and module 122 in the specification description are identified, and links L11, L12 .
By tracing L13, desired specification description 113 or construct information 114 can be specified.

Also, the parts information file 120, group 121, user file 122, and parts information 123 are specified, and the links L21, L22. By tracing L23, the specification description information 124 or construct information 125 within the desired component information 123 can be specified.

Note that each piece of construct information includes a component availability flag. The component possible flag is set to "ON" when the corresponding module is described to the level of components or primitives that are basic operations, that is, when the module does not include any undefined modules. .

In other cases, the component availability flag is set to "OFF".

Next, the component registration function, component reference function, and component quotation function of the component management device CP will be explained with reference to FIGS. 25, 26, and 27.

■ Part registration function As shown in FIG. 25, the user selects "part registration" from the menu provided by the input/output device 10, and specifies the module name of the module to be registered as a part using the editor (step 521). .

The component management device CP searches the information area 110 in the specification description via the integrated file management device UF, and refers to the component possible flag of the construct information 114 in the specified module 112 (step 522).

If the parts availability flag is “ON” (step 823)
, the user selects group 12 in the parts information file 120.
1, the user name that specifies the user file 122, and the component information name that specifies the component information 123 as information necessary for classification.
(Step 524)
. The parts management device CP refers to the information necessary for classification and stores a predetermined user file 122 in the parts information file 120.
The module 112 that should be registered as a component within is registered as new component information 123. This allows, for example,
As shown in FIG. 24, an information area 110 in the specification description,
Link L3 formed by specification file name B and module name q is part information file 120 and group name G
1. The link is changed to link L4 connected to user file name X (step 525).

If the component availability flag is "OFF" (step 823), the component management device CP displays on the display device DP via the input/output device IO that the component cannot be registered as a component (step 526).

■ Parts reference function As shown in FIG. 26, the user selects "parts reference" from the menu provided by the input/output device 10 (step 5).
31). Then, the user provides search conditions such as group name and user file name using the editor (step 5).
32).

The component management device CP refers to the component information file 120 in the integrated file management device UF via the input/output device IO, and provides the input/output device IO with a list of component names of components that match the search conditions. The input/output device IO starts the editor and
A parts reference window (reference WD) is opened and a parts name list is displayed (step 833).

The user selects a component name to be referenced from the component name list displayed in the component reference window (reference WD) (step 534). The input/output device IO gives the component name to the component management device CP. The parts management device CP searches for the corresponding part information 123 in the parts information file 120 based on the part name, and stores the part information 123 in the input/output device!
0 to the parts specification editor. The part specification editor displays the part information. The component information displayed here is the top-level functional block diagram (step 535).

If the user wishes to refer to detailed specifications (step 5)
36), use the editor to instruct the parts management device CP about the detailed specifications to be referenced (Step 1.B 537). The parts management device CP provides the instructed detailed specifications to the parts specification editor via the input/output device 10. The part specification editor displays the given detailed specifications (step 538).
. If you wish to refer to further detailed specifications, step 8
Steps 36 to 63g are repeated. If the detailed specifications are not to be referenced, the user uses the editor to instruct the parts management device CP to end the part reference (step 5).
39).

■ Parts quoting function As shown in Figure 27, if you want to quote parts while writing specifications using each editor, select ``Parts'' in the drawing mode of the functional block diagram editor or sequence chart editor. "Citation" (step 541). Then, the user uses the editor to provide search conditions such as group name and user name to the parts management device CP (step 542).

The component management device CP refers to the component information file 120 and provides the input/output device 10 with a list of component names of components that match the search conditions among the registered components. The input/output device 10 starts the editor, opens a window for quoting parts, and displays a list of parts names (step 843).
.

The user selects the part name displayed in the part reference window.
Select the part name to be quoted from the list (step 544)
). The input/output device 10 requests component information corresponding to the selected component from the component management device CP. Parts management device CP
refers to the component information file 120 via the integrated file management device UF and reads the component information 123 corresponding to the selected component name to the input/output device ■0 (step 545).
The input/output device 10 further sends the component information 123 given by the component management device IO to an editor that attempts to quote this component information. The editor draws based on the supplied component information and notifies the input/output device 10 of changes in the specification description (step 546).

Next, the functions of the integrated file management device UF will be explained. Information regarding the contents of the specification description handled by this development device is expressed as one integrated file. The function of manipulating this file is realized by the integrated file management device UF as a data structure manipulation command. The integrated file management device UF is connected to other processing devices (input/output device 10, mutual conversion device Cv1 execution device , and parts management device CP), and integrally manages internal data structures expressing specification description information.

Other processing devices that use the integrated file management device UF are:
The operation code for the required data structure operation and the information required for the data structure operation are passed to the integrated file management device UF. Integrated file management device U
F executes the instructed data structure operation and returns the execution result to the processing device that called the integrated file management device UF.

As data structures used in the program development apparatus according to the present invention, a square (atom) and a list structure are employed. This is because by using this list structure, structures such as "array", "record", and "vector" can be expressed. When using this list structure, (1) access to an element by subscript (identifier) and (2) access to an element by key matching are executed.

In this list structure, the logical identifier rfid for the identifier (name) of the entire data structure to be processed is
J, and a logical identifier rd i dJ for identifying an array in which one element is a data area of the size of the array element indicated by ``5izej'' in the data structure identified by ``fid''. By using these identifiers, the access area in the file is determined.

When the integrated file management device UF is referenced using the data structure of the file, reference and update are performed using the data name.

Each processing device operates in parallel while exchanging information with each other. Therefore, multiple access requests are generated to the integrated file management device UF. Since these accesses occur dynamically, the processing device that uses the integrated file management device UF cannot determine whether multiple accesses are occurring. Furthermore, even if it is possible to determine that multiple accesses have occurred, the processing device that requested the access will not be able to access the file later. can't know. For this reason,
The integrated file management device UF includes a mechanism for ensuring consistency for a series of accesses regarding files in a multi-process environment. As such a mechanism,
When the user of the integrated file management device UF makes an access request, it notifies the integrated file management device UF whether to subsequently request access to the same record of the same file and what kind of access request to make. By doing so, a lock control mechanism for locking a necessary range of files in the integrated file management device UF is provided.

Lock control is implemented as one primitive. There are two types of files managed by the integrated file management device UF: temporary files and permanent files. Temporary files are consumed once they are used. Permanent files are saved before and after the target program is executed. When executing primitives that use files, a temporary file is always created to write to. Next, a specific example of creating a software system using a program development apparatus according to an embodiment of the present invention will be described.

Now, let's consider the case of writing a module to search by "key" in an inventory management problem. Now, as a specific problem, I will describe the following problem.

The search data is a list of items. This item list has the structure of ``item list: 2 item code, item name, quantity, and supplier.'' The search item (key) is the product name code or quantity. For searches using quantity as the "key",
List the items corresponding to the given quantity or more of the item code.

First, as shown in FIG. 28, the interface with the outside is described. The system to be described is a product name search module 91 that manually inputs product name codes and outputs a corresponding list.
It includes an a1 item list file 91b1, an external module (user) 91c, and a quantity search module 91d that inputs quantities and outputs a corresponding list. This description from a functional aspect is expressed by a functional block diagram 91.

At this time, the module information expressed in this functional block diagram 91 is converted into a sequence chart and displayed (see the lower right part of FIG. 28).

Next, as shown in FIG. 29, the order relationship of data flow between each module will be described. The first sequence chart 92 describes a product name search sequence, and the second sequence chart describes a quantity search sequence. This sequence chart 92 and 93
The signal line described in is immediately converted to a data arc on the functional block diagram 94 and displayed. At this time, since the port information is not reflected in the sequence chart, the port information will be described in the functional block diagram 94.

Here, although the relationship between data is described using a sequence chart, the relationship between data may also be described using a functional block diagram. By mutually converting and reflecting common information between different expression formats in this way, inconsistencies between descriptions can be avoided.

Next, the data structure is described as shown in Figure 130. A relevant list (not shown) and a product list are described in a relational table 95, and product name codes and quantities are described in a data block diagram 96. In the example shown in FIG. 30, only the minimum required product name code and quantity are described in the applicable list. The described data structure, the data arc on the functional block diagram, and the signal line on the sequence chart are correlated by a matching operation. By using this association operation, complicated naming work is relieved.

Next, as shown in FIG. 31, the details of the internal module will be defined. In FIG. 31, the product name search module 91a included in the modules to be described is a file operation, so it is described using a table operation diagram 96. In this table operation diagram 96, the input/output information has already been converted and reflected according to the functional block diagram described earlier. The structure of the table data in this table operation diagram 96 is quoted from the relational tables 95a and 95b. The cited data structure is associated with the original relational table. Therefore, if the original relational table data structure is changed, the data structure in this table operation diagram 96 is also changed. This can prevent forgetting to make changes due to changes in specifications.

By describing the product name search module using the table operation diagram shown in FIG. 31, its specification description is completed and becomes executable. For this executable product name search module, the third
As shown in Figure 2, we perform prototyping to verify the specifications. That is, the product code of the product list 96a is used as input data, and the corresponding list 96b is used as output data.

The product name code included in the product list is entered in the product code of the product list 96a. Thereafter, by the execution of the apparatus, the item corresponding to this item name code 3 is displayed on the corresponding list along with its corresponding quantity. According to the execution results obtained through this prototyping, the specification description contents are changed in accordance with the target specification, and then executed again to verify.

After this, when the description of the specifications of the search system is completed, this is one partially completed module and is registered as a "component".

According to the program development apparatus of the above embodiment, specifications can be described from multiple angles, and specifications that are complete at the level of specification description can be registered as parts. Therefore, the user can view the specifications of the registered parts from multiple angles at the level at which the specifications are currently being written. Thereby, the user can easily check whether the component matches the specification to be written, and can improve the productivity of the program by reusing the component.

[Effects of the Invention] As described above, the present invention has the function of registering the specification description created by the user as part information and the function of presenting the registered part information. The contents of the registered parts can be easily known, and registered parts can be easily reused. Therefore, the efficiency of program development is improved.

[Brief explanation of drawings]

FIG. 1 is a diagram schematically showing the overall configuration of a program development apparatus according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a functional block diagram that is one of the specification description expression formats used in the present invention. Third
The figure shows one of the specification description expression formats that can be used in this invention.
FIG. 2 is a diagram illustrating a sequence chart. Fourth
The figure shows one of the specification description expression formats used in this invention.
FIG. 2 is a diagram illustrating a relational table. FIG. 5 is a diagram illustrating a decision table, which is one of the specification description expression formats that can be used in the present invention. FIG. 6 is a diagram illustrating a data block diagram that is one of the specification description expression formats that can be used in the present invention. FIG. 7 is a diagram illustrating a table operation diagram, which is one of the specification description expression formats that can be used in the present invention. FIG. 8 is a diagram illustrating "quote" and "correspondence" operations when a specification is described using a plurality of expression formats. FIG. 9 is a diagram showing an example of the structure of specification description information generated in a program development apparatus that is an embodiment of the present invention. FIG. 10 is a diagram showing a list of the configuration of specification description information used in the program development apparatus according to the present invention. FIG. 11 is a diagram showing the structure of sequence line information included in specification description information. Figure '1a12 is a diagram showing the structure of the signal line information shown in Figure 10. Figure 13 is the first
FIG. 2 is a diagram showing the structure of relational data shown in FIG. FIG. 14 is a diagram showing the structure of the included data shown in FIG. 10. FIG. 15 is a diagram showing the structure of the atom shown in FIG. 10. FIG. 16 is a flow diagram showing the operation of the mutual conversion device in the program development device according to the present invention. FIGS. 17A and 17B are diagrams illustrating a data transmission/reception sequence between the graphic editor, which is a specification description expression means, and the mutual conversion device. W, Figure 18 is a diagram illustrating an aspect of generating construct information from a combination of a plurality of colloquial expression formats. FIG. 19 is a diagram illustrating another example of generating construct information from a combination of a plurality of colloquial expression formats. FIG. 20 is a diagram illustrating a mode of mutual conversion between a functional block diagram and a sequence chart executed in the mutual conversion device. FIG. 21 is a diagram illustrating an example of a mode in which lower layer information in the hierarchical description of sequence specification information is generated using a mutual conversion function between a sequence chart and a functional block diagram. FIG. 22 is a diagram illustrating another example of generating lower layer information in the hierarchical description of the specification description using the mutual conversion function. FIG. 23 is a sequence chart showing the prototyping execution operation in the program development apparatus according to the present invention. 24th
The figure is a diagram schematically showing information stored in the integrated file management device. FIG. 25 is a flowchart for explaining the parts registration function of the parts management device. FIG. 26 is a flowchart for explaining the component reference function of the component management device. FIG. 27 is a flowchart for explaining the parts quotation function of the parts management device. 28, FIG. 29, FIG. 30, FIG. 31, and FIG. 32 are diagrams showing a specific example of specification description using the program development apparatus according to the present invention. In the figure, 1 is the main unit, IO is the input/output device, CV is the mutual conversion device, EX is the execution device, cp is the parts management device,
UF is an integrated file management device, E. E1 to En are editors, and DP is a display device. Note that the same reference numerals in each figure indicate the same or corresponding parts. Figure 3 Figure 4 Figure 5 Figure 11 Figure 12 Figure 13 Figure 14 Figure 16 E Figure 77A O Input/output system C ■ Module information creation Figure 18 Figure 178 v Figure 19 Figure 20 Figure 22 Figure 21 Island Figure 27 Procedural amendment alpha bar 0 November 14, 1990 2, Name of the invention Program development device 3, Relationship with the person making the amendment Case Patent applicant address Nagaike-cho, Abeno-ku, Osaka City 22 No. 22 Name (
504) Sharp Corporation (3 others) Haruo Tsuji Tsuji 4, Agent address: 2-1-29 Minamimorimachi, Kita-ku, Osaka Sumitomo Bank Minamimorimachi Building Telephone: Osaka (06) 361-2021 (f
t) 6. Figure 31 of the drawing to be amended 7. Contents of the amendment (1) No. 3 of the inscribed drawing (no change in content). Figure 1 is attached as a separate sheet.

Claims (1)

[Scope of Claims] Specification description means for a user to create a graphical specification description regarding a target program on a screen; conversion means for converting the specification description created by the specification description means into an executable program; A program development device comprising a parts management means having a function of registering a specification description created by a specification description means as parts information and a function of presenting the registered parts information.