JP2000242477A - Preparation supporting tool and specification verifying tool for software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To facilitate change and customizing due to the user of a sequence software. SOLUTION: This device is provided with a data base 3 for storing software components, a library 2 for managing of storing/extracting and aligning/ classifying software components to this data base 3 and a CAD device 4 for generating a data flow chart, a variable work sheet and component information on the basis of software components extracted from the data base 3. Thus, the user can easily perform the change or addition of a function block through the CAD device 4 and cost-reduction is attained.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a function block (F) used in sequence software or the like.
The present invention relates to a software creation support tool for facilitating change and customization of B) from the user side.

[0002]

2. Description of the Related Art Conventionally, as a tool of this kind, there is a PLC loader currently under development. This corresponds to a high-level language (ST: structured-text, IL: instruction-language) conforming to IEC (International Electrotechnical Commission) 1131, ladder chart (LD), and sequential function chart (SFC). Thus, it is possible to provide an extended FB adapted to each application. The extended FB includes a sequence section and a processing section, which are described in a programming language such as ST or IL.

[0003]

As described above, the extension F
Since B is described in a programming language such as ST or IL and is intuitive, it is generally impossible for the user to easily change or customize the sequence software. In addition, if the manufacturer has individually dealt with the extended FB according to the request of the user, there is a problem that the development period and the development cost are increased. Therefore, an object of the present invention is to enable the user to change and customize the extended FB easily and at low cost.

[0004]

In order to solve such a problem, according to the first aspect of the present invention, a database for storing software components and storing / retrieving, organizing, and classifying the software components in the database are provided. And a CAD device for generating a data flow diagram, a variable worksheet and component information based on software components extracted from the database.

[0005] In the first aspect of the present invention, when a predetermined number of software components are registered, the library automatically builds an upper layer, attaches a predetermined address code thereto, and registers the layer in the database. In addition, the address code can be notified to a registrant of the software component (the invention of claim 2), or the library gives the CAD device external shape information of the software component. (The invention of claim 3),
Alternatively, an input unit for creating and inputting a state transition table from a state transition diagram can be provided for the library (the invention of claim 4).

According to the fourth aspect of the present invention, the input unit for creating a state transition table from the state transition diagram can extract item information from the state transition diagram and create a state transition table from the item information. (Invention of claim 5).
In the invention according to claim 4 or 5, the predetermined information is extracted from the state transition table, and the extracted information is sequentially applied to a template of a program language, thereby converting the extracted information into a machine-executable source file. (Invention of claim 6). Further, according to the invention of claim 6, the information extracted from the state transition table can be information including a state transition destination, a state processing, a state transition processing, and an event (the invention of claim 7). .

[0007] In the first aspect of the present invention, the library can be provided with an input section for creating and inputting a function expansion table from a function expansion diagram (the invention of claim 8).
In the invention according to claim 8, in the input unit for creating a function expansion table from the function expansion diagram, each function is extracted from the function expansion diagram, and a parent function and a child function connected to the parent function in the order of their function numbers. Can be sequentially extracted to create a function expansion table (the invention of claim 9). In the invention of claim 9, the child function name of the lowest layer is extracted from the function expansion table, and the child function name is extracted. Can be used as a search key to call a software component and convert it into a program language (the invention of claim 10).

[0010] According to the eleventh aspect of the present invention, a database for storing software components, a library for storing, retrieving, organizing, and classifying software components from the database, and data based on the software components retrieved from the database. A CAD apparatus for generating flow diagrams, variable worksheets, and component information;
The library comprises an input unit for creating and inputting a state transition table from a state transition diagram, and a specification verifying unit for verifying the validity of the software specification by simulation based on the state transition table. It is characterized by the following.

In the above invention, the specification verification unit may include an event operation unit that outputs an event from an external signal, a state transition processing unit that performs a state update process based on the state transition table, A function to simulate the operation of an external device by inputting a trace unit that records state transitions, a display unit that displays state transitions, and a software component that defines a state transition table, state processing, and state transition processing. The present invention can include a simulation unit that outputs a calculation result to a block, executes a simulation while inputting an output of a function block, and outputs the result to the trace unit and a display unit.

[0010]

FIG. 1 is a block diagram showing an embodiment of the present invention. In the figure, 1 is ST or IL
A software component input unit for inputting and registering software components as subroutines and functions of the smallest unit for realizing individual functions into a tool, which is described in a programming language such as In response to the instruction, the software component is registered in the database 3, the software components in the database 3 are organized and classified, or the software component is read out from the database 3, and the library 3 stores the software component. The database 4 is a drawing device such as a CAD (Computer Aided Design) device that generates a data flow diagram, a variable worksheet, and component information based on software components extracted from the library 2.

For example, when the number of software components registered from the software component input unit 1 becomes a predetermined number or more, the library 2 adds a new component to the software component group in order to hierarchically manage the components. And a function of notifying the maker via the software component input unit 1 of an address code on a database storing the component name. The library 2 also has a function of, when a software component is selected on the CAD device 4, providing the CAD device 4 with external shape information (size, width, etc.) of the component.

FIG. 2 shows an example of a database. this is,
An example is shown in which eight software components having software component names 0 to 6 and 10 are registered. Each of the software components is a component for event detection, and its attributes are an address code and an input. Indicates that there is a signal name, output signal name, software component body, etc.

Therefore, when a certain user wants to change a certain extended FB, the user takes out the corresponding extended FB from the database 3 via the CAD device 4 and the library 2 and displays it on the CAD device 4. By changing the software components and their attributes on the screen, a data flow diagram, an input / output variable worksheet, and component information can be created. A language source file is created from this component information via a language conversion tool (not shown), and this and an input / output variable worksheet are input to the PLC loader under development, thereby creating executable software. can do.

When changing or customizing the extended FB, attention may be paid to a state transition diagram or a function development diagram that is familiar to the user. That is, if a state transition table can be created from a state transition diagram or a function development table can be created from a function development diagram, it is easy to convert them to ST language or IL language. Therefore, by inputting a state transition diagram and a function development diagram to the software component input unit shown in FIG. 1 and having a function of creating a state transition table and a function development table from this, it is easy to change and customize the extended FB. Become.

First, a method of creating a state transition table from a state transition diagram will be described with reference to FIGS. An element is defined as a state, and a connecting line (hereinafter called an arc) connecting the elements is defined as a state transition condition (event). A state number is assigned to each element. Process number SA to be always executed Register The arc has information on a start point state and an end point state, and a state number is registered for each state. As the attribute information of the arc, the state transition condition (event) number E And the processing number TA to be executed at the time of state transition Is defined. FIG. 3A is a state transition diagram showing elements and arcs and their relationships.
FIG. 3B shows the result of extracting the item information from the state transition diagram of FIG.

Next, each element is identified, the state numbers of the elements are arranged on the horizontal axis, and the vertical axes are arranged in the order of event numbers. Then, the end item number is extracted from the information of each arc whose start item number and state number match in order of the state number, and the transition destination state number (arc) is set at the intersection (hereinafter also referred to as a matrix) of each state and each event. An end state number) and a process number to be executed at the time of state transition are output, and a state transition table as shown in FIG. 4 is created. A portion where "-" is written in the matrix indicates that no transition occurs.

A method of converting the state transition table obtained as described above into a program language will be described. In the state transition table as shown in FIG. 4, a state transition condition (event) is arranged on the vertical axis, and a state is arranged on the horizontal axis.
State transition destination 2) Processing executed when in state (processing at state: SAX) (X is the state number of each state) 3) Processing executed at state transition (processing at state transition: TAX) (X is each State number of the state). A state transition processing unit (not shown) converts the state transition table into a predetermined programming language using the state variable S.

FIG. 5 shows an example in the case of conversion into ST language. This extracts predetermined information from the state transition table,
The extracted information is sequentially applied to a model (also referred to as a template) for expressing in a programming language, thereby converting the extracted information into a machine-executable source file. The symbol on the right side of the equal sign (=) of the event indicates a signal name, and SA0 to SA2 and TA0 to TA2 indicate software component names, respectively.

Next, a method of creating a function expansion table from a function expansion diagram will be described. As shown in FIG. 6A, the function development diagram shows the functions in detail in a hierarchical structure and is shown in a tree structure, and a function number is automatically registered for each function. As the attribute information of each detailed function, the parent number of the function is registered, and the parent function and the child function are connected by an arc. The attribute information of this arc includes: 1) parent function number,
A child function number is added.

To convert such a function development diagram into a function development table: 1) For example, from the function development diagram shown in FIG.
The item information is extracted and each function is identified as shown below. Each function is arranged on the vertical axis in the order of its function number, and the horizontal axis shows the parent function,
.. Are arranged in the order of child function 1, child function 2,. 2) Extract the child function connected by an arc to the parent function and its child function in the order of the function number, extract the child function 2 that is arc-connected to the child function 1, and so on. Create a function spreadsheet.

The conversion from the function development table to the program language is performed by calling a software component using the lowermost child function as a search key. Therefore, as shown in FIG. 8, software components (here, an example described in ST language is shown) corresponding to the child function name at the bottom layer (here, described as the last child function name) in advance. It shall be registered in the database. Then, the last child function name is identified from the function expansion table as shown in FIG. 9A, and the software component as shown in FIG. 8 is called from the database by using the name as a search key. For example, as shown in FIG. S
Convert to T language.

By the way, in the development and design of a program, usually, specification examination, system design, program design,
Work proceeds in the order of coding and debugging, but bugs are often introduced upstream in the process. For this reason, there is a problem that a large amount of time and development costs are required in the last debugging process. In addition, since the debugging process is the final process of product shipment and cannot absorb the delay, there is also a problem that the product shipment time is delayed. Therefore, in the present invention, the following is performed.

FIG. 10 is a block diagram showing a configuration capable of dealing with a bug. The configuration shown in FIG. 1 is additionally provided with a specification verification unit. FIG. 11 is a schematic explanatory diagram of the specification verification process. Here, it is shown that the input state transition diagram is converted into a state transition table, and the specification verification unit 5 verifies the software specifications based on the state transition table. In addition,
When the occurrence of a problem is detected by the specification verification unit 5, the state transition diagram is corrected. This focuses on the fact that if the Petri net theory is applied, the validity of the specification can be mathematically easily verified from the state transition table. This enables the validity of the specification to be verified at the design stage.

FIG. 11 shows a detailed example of the specification verification unit. That is, the specification verification unit 5 includes an event calculation unit 51B, a state transition processing unit 52B, a trace unit 53B, a display unit 54B, a simulation unit 51A, and the like. 52A is a function block that simulates an external operation. The event operation unit 51B receives an external signal and outputs an event. The state transition processing unit 52B updates the state from the event and the state transition table.
The display unit 54B traces and displays the state number and the simulation result. The simulation unit 51A simulates the state process and the state transition process described in the state transition table, inputs the result to a function block 52A that simulates the operation of an external device, and inputs the output of the function block 52A. The simulation is performed, and the result is output to the trace unit 53B and the display unit 54B.

When extracting item information from the state transition diagram and creating a state transition table from the item information or extracting item information from the function development diagram and creating a function development table from the item information, For example, a tool called an idea processor can be used.

[0026]

According to the present invention, a subroutine or a function described in a programming language such as ST or IL is registered in a database in the form of a software component and provided. By selecting software components for realizing functions and connecting each software component with a CAD device, customization and change become easy. Further, even when the extended FBs are individually handled according to the user's request, the development time and the development cost can be reduced. Since the user can easily create the software and verify the validity of the software, the burden on the manufacturer for individual handling is greatly reduced.
In addition, since debugging can be performed with a simple configuration, the accuracy of specifications can be improved at the design stage of program development, rework can be prevented, and development efficiency can be improved.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an embodiment of the present invention.

FIG. 2 is an explanatory diagram illustrating a configuration example of a database.

FIG. 3 is an explanatory diagram of an example of conversion from a state transition diagram to item information.

FIG. 4 is an explanatory diagram of an example of conversion from item information to a state transition table.

FIG. 5 is an explanatory diagram of an example of conversion from a state transition table to an ST language.

FIG. 6 is an explanatory diagram of an example of conversion from a state development diagram to item information.

FIG. 7 is an explanatory diagram of an example of conversion from item information to a state development table.

FIG. 8 is an explanatory diagram illustrating an example of a software component database.

FIG. 9 is an explanatory diagram of an example of conversion from a state expansion table to an ST language.

FIG. 10 is a block diagram showing a configuration capable of dealing with a bug.

FIG. 11 is a schematic explanatory diagram of a specification verification process.

FIG. 12 is a block diagram illustrating a detailed example of a specification verification unit in FIG. 10;

[Explanation of symbols]

DESCRIPTION OF SYMBOLS 1 ... Software component registration part, 2 ... Library, 3 ... Software component database, 4 ... Drawing device (CAD device), 11 ... State transition diagram input part, 12 ... Document conversion part, 5 ... Specification verification part, 51B ... Event operation unit, 52
B: state transition processing unit, 53B: trace unit, 54B: display unit, 51A: simulation unit, 52A: function block.

Claims (12)

[Claims] 1. A database for storing software components, a library for storing, retrieving, organizing, and classifying software components from the database, a data flow diagram and a variable work based on the software components retrieved from the database. A software creation support tool, comprising: a CAD device for generating sheet and component information. 2. The library automatically builds an upper layer when a predetermined number of software components are registered, registers the upper layer with a predetermined address code, registers the layer in the database, and stores the address code in the database. 2. The software creation support tool according to claim 1, wherein notification can be made to a registrant of the software component. 3. The software creation support tool according to claim 1, wherein the library provides the CAD device with outer shape information of a software component. 4. The software creation support tool according to claim 1, wherein an input unit for creating and inputting a state transition table from a state transition diagram is provided for the library. 5. An input unit for creating a state transition table from the state transition diagram, extracting item information from the state transition diagram,
The software creation support tool according to claim 4, wherein a state transition table is created from the item information. 6. A machine-executable source file by extracting predetermined information from the state transition table and sequentially applying the extracted information to a program language template. 5. The software creation support tool according to any one of 5. 7. The information extracted from the state transition table,
7. The software creation support tool according to claim 6, wherein the information includes a state transition destination, a state transition process, a state transition transition process, and an event. 8. The software creation support tool according to claim 1, wherein an input unit is provided for creating and inputting a function expansion table from a function expansion diagram to the library. 9. An input unit for creating a function expansion table from the function expansion diagram extracts each function from the function expansion diagram, and sequentially extracts a parent function and child functions connected to the parent function in order of their function numbers. 9. The software creation support tool according to claim 8, wherein the function development table is created by using the software. 10. The method according to claim 9, wherein a child function name at the lowest layer is extracted from the function expansion table, and the software component is called up using the child function name as a search key and converted into a program language. Software creation support tool. 11. A database for storing software components, a library for storing, retrieving, organizing, and classifying software components in the database;
A CAD device that generates a data flow diagram, a variable worksheet, and component information based on software components extracted from the database; an input unit that creates and inputs a state transition table from a state transition diagram to the library; A software specification verification tool, comprising: a specification verification unit that verifies the validity of the software specification based on the state transition table by simulation. 12. The specification verifying unit includes: an event computing unit that outputs an event from an external signal; a state transition processing unit that performs a state update process based on the state transition table; and a trace that records a state transition. And a display part for displaying state transitions, a state transition table and software components that define state-time processing and state-time processing, and output calculation results to a function block that simulates the operation of an external device. 12. The software specification verification tool according to claim 11, further comprising: a simulation unit that executes a simulation while receiving an output of a function block, and outputs a result of the simulation to the trace unit and a display unit.