KR20080104057A - Source program creation support system - Google Patents
Source program creation support system Download PDFInfo
- Publication number
- KR20080104057A KR20080104057A KR1020087024625A KR20087024625A KR20080104057A KR 20080104057 A KR20080104057 A KR 20080104057A KR 1020087024625 A KR1020087024625 A KR 1020087024625A KR 20087024625 A KR20087024625 A KR 20087024625A KR 20080104057 A KR20080104057 A KR 20080104057A
- Authority
- KR
- South Korea
- Prior art keywords
- box
- flow chart
- source program
- user
- screen
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present invention provides a source program creation support system for easily creating a source program including event processing.
The flow chart creation module 10, which supports creating a flow diagram corresponding to a source program to be created on a PC screen, displays a list of basic plates such as input / output lines and boxes included in the flow diagram, and the user Whenever a plate is selected and its placement position is specified on the monitor screen, the selected plate is displayed at that placement position. When an event box for creating an event processing program is selected, an event flow including a virtual event waiting box and a return terminal also automatically displays the initial box group. The flow chart analysis converting module 40 converts the generated flow chart into source code by converting the generated flow chart into source code. However, when a virtual event waiting box is included, the flow chart analysis converting module 40 reads and embeds the event definition module into the source program.
Description
The present invention relates to a source program creation support system, which is a CASE (Computer Assisted Software Engineering) tool, and more particularly, does not require advanced knowledge of a program when creating a source program of a computer. Under support, a system is provided that makes it easy to write a source program in a computer language.
Recently, system development in a general-purpose system is usually performed in the order of a system analysis process, a system design (functional design, data design) process, a program design process, a programming process, and a testing (verification) process. In addition, the systemization work flow also creates a systemization function summary and an input / output definition document, and divides into a system, a subsystem, a process, a program, and a module based on the document, and defines specifications in detail from the overview.
When creating a document of such a specification, the subsystem related diagram, subsystem outline, process related diagram, business function flow diagram, process outline, process flow diagram, program outline, program structure diagram, module (program module) outline, coding In each step, the document is created one by one while maintaining the logic relationship based on the document of the upstream step.
At this time, the document forms are unique to each one, and in order to create a variety of documents in various forms in this manner, an enormous number of steps and time are required.
In addition, the program is made by an experienced programmer with a high level of programming knowledge, which is impossible for personnel who do not have programming knowledge.
In order to solve the problem of such a prior art example, the apparatus and method which let automatic programming be made under computer support, as described in the following
The production management program automatic generation device of
Moreover, although the automatic programming method of
In addition, when a specification change occurs or a bug fix is required, it is a different type of document. Therefore, from these documents, it is very complicated to pursue the logic associated with a plurality of processes. It needs number and time. Therefore, in many cases, only the source program is changed without changing the document. In such a case, the logic of the specification and the logic of the source program are not maintained.
In a program including an event process (a program having input processing from a screen, a keyboard, and the like in C language), the program of the screen input processing becomes an input standby state from an input screen display state. In addition, the program waits for processing until an event signal (for example, an Enter signal from the keyboard) that is a specific signal for input completion is received. In a program including such event processing, when a plurality of events occur randomly, it has conventionally been difficult to clearly and properly describe an event waiting state in the middle of a flow.
In addition,
For example, when creating a name address program for inputting a name, a furigana, a zip code, an address, and a furigana on the screen, an input operator is displayed. It is necessary to create a program in consideration of not inputting in the display order of the input screen. That is, the operator usually moves the cursor to the input field of the displayed arbitrary item and inputs or corrects data. In this case, the event is generated randomly by the position of the cursor. It is necessary to correspond to the processing performed at random.
In addition, when a user creates a flow chart that is a premise for creating such a program, it is necessary to be able to clearly and plainly display an event waiting state. However, in the flowchart input device of
The source program is usually composed of a combination of data definition, screen definition, and main program.
In order to define the data, conventionally, in order to define the data, the file layout sheet is described by aligning the digit positions of the items, and when an item is added, deleted, or changed in the digits of the item, the digit positions are fixed again, and the description is repeated. Doing. In addition, detailed item definition by subdividing an item must perform the same operation. In many cases, changes occur frequently during development, and since such work is performed every change, it takes time and effort. In addition, it is necessary to code the file layout information described for each program.
In addition, in order to perform screen definition, rough sketching of the screen outline definition is performed by hand manually, and the screen layout is created based on this. When creating the screen layout, the positions of lines, items, and the like need to be mapped to the X-Y coordinates on the screen, but these coordinate values must also be defined in source code along with the line and item attributes. In addition, it is necessary to code the screen layout information described for each program. Therefore, in order to perform screen definition by the conventional method, work efficiency is low because of the complicated order and difficulty of water retention.
[Patent Document 1]
Japanese Patent Laid-Open No. 6-214769
[Patent Document 2]
Japanese Patent Application Laid-Open No. 9-91146
[Patent Document 3]
Japanese Patent Application Laid-Open No. 11-296357
As described above, although an automatic programming apparatus and method have already been proposed, any one of them is specialized for a particular use, and in particular, an event waiting state in a case where a plurality of events and processing corresponding thereto randomly occur is shown on a flowchart. It is not intended to be appropriate.
In addition, as described above, creating the data definition and the image definition of the source program by the conventional method is very troublesome, and the work efficiency is poor.
The present invention has been made to solve such a problem.
It is a first object of the present invention to provide a source program creation support system having a flow chart creating means for properly displaying an event waiting state in a case where a plurality of events and processes corresponding thereto randomly occur. It is.
A second object of the present invention is to provide a source program creation support which includes a flow chart creating means for achieving the above-described first object, and allows an arbitrary source program to be easily created by a person without advanced knowledge. To provide a system.
A third object of the present invention is to enable a source program creation support system that achieves the above-described second object to create a data definition included in a source program with high work efficiency.
A fourth object of the present invention is to enable a screen definition included in a source program to be created with high work efficiency in a source program creation support system that achieves the above-described second object.
A fifth object of the present invention is to enable verification of a created source program in a source program creation support system that achieves the above-described second object, and to provide the result in a form that is easy for the user to understand.
In order to achieve the above object, the present invention relates to a source program creation support system for creating a source program by dialogue with a user using a computer-readable program, which corresponds to a source program to be created. A flow chart creating means for supporting the creation of a flow chart on a monitor screen, and a flow chart analysis converting means for interpreting the flow chart created by the flow chart creating means and converting the flow chart into source code to convert the flowchart into source code; In the source program creation support system,
Flow chart creation means,
A basic plate including a start terminal, an end terminal, an inflow line, an outflow line, and a plurality of boxes included in a flowchart, and a plurality of event processes each driven by a plurality of randomly generated events. Plate list display means for displaying a list including a start plate so as to be selectable by a user;
A plate arrangement means for displaying a shape of a plate selected at the arrangement position whenever the user selects a plate from the displayed plate list and designates the arrangement position on the monitor screen.
When the event processing program start plate included in the plate list is selected, an event flow including a virtual event waiting box indicating a waiting state for event occurrence and a return terminal connected to an outlet line is connected to the virtual event waiting box. Plate arranging means including means for displaying the image on the flow chart creation area;
And a specification setting means for displaying a text box for inputting a specification corresponding to the processing content to a user on a box arranged on a monitor screen, and storing the input specification in association with the box.
Flow diagram analysis conversion means,
Means for determining that the event processing program is to be determined as an event processing program and reading the event processing definition installed as part of the OS on the computer in use, when the flow to be converted to the source program is also included;
Means for analyzing the linkage of boxes in the flowchart to obtain linkage information for each box;
Means for generating a module of the source program of each box by converting the specifications set in each box in the flowchart into source code, and incorporating linkage information of boxes corresponding to the converted source code;
Provided is a source program creation support system, characterized in that it comprises a means for generating a source program by integrating a source program module in which read event processing definitions and box linkage information are incorporated.
In the above-described source program creation support system according to the present invention, the event flow diagram initial box group includes, in addition to the virtual event wait box and the return terminal, two judgment boxes arranged in series downstream of the start terminal and the event wait box. And two processing boxes respectively connected to the judgment box by outlet lines from the judgment box, and the outlet lines preferably include at least processing boxes connected to the return terminals.
Further, the flow chart creation means further includes plate deletion means for deleting the plate when the user instructs the deletion of the plate disposed in the flow chart creation area, and a plate other than the initial box group for the event flow is also newly created. When disposed in an area, it is preferable to include means for automatically displaying a processing box and its outflow line downstream of the plate in a display form different from that of the disposed plate. In this case, preferably, the plate list displayed by the plate list display means of the flow chart creation means includes an event processing program end plate, and the plate arrangement means is virtual in the flow chart displayed in the flow chart creation area. When the event processing program termination plate included in the plate list is selected while the event waiting box is included and the processing box and other outgoing lines of the other display types are included, the processing box and the outflow of the other display types are selected. The line is automatically deleted, and at the bottom of the bottom judgment box, a judgment box in which one outlet line is connected to the return terminal is added, and the other outlet line of the judgment box is returned, and the own outlet line is returned. It is comprised so that the process box connected to the terminal may be added.
Further, in the above-described source program creation support system according to the present invention, the system further includes a model library that stores in advance a plurality of functions, which are source program modules corresponding to each of a plurality of processing contents, in association with the function name. The specification setting means of the flow chart creation means is configured to present the contents of the plurality of functions in the model library and the function names to the user so that the user can selectively input the function name stored in the model library as a specification. Means, and the flow chart analysis converting means reads a function corresponding to the function name from the library when the flow chart to be converted has a box in which the function name stored in the model library is set as a specification. It is preferable that it is comprised so that.
The flow chart creating means includes means for executing a hierarchical descending function for creating a flow chart of an upper layer and a detailed flow chart of the lower layer. The specification setting means of the flow chart creating means includes: In order to be able to selectively input the flow diagram ID for specifying the flow diagram of the lower layer as a specification of the specification, means for presenting the contents of the flow diagram of the lower layer and the flow diagram ID to the user is provided. Is preferably configured to read a program module corresponding to the flow chart ID from the storage means when there is a box in which the flow chart ID is set as a specification in the flow chart to be converted.
Further, in the source program creation support system according to the present invention described above, the flow chart creation means also displays a title input box for inputting a processing title in a box arranged on a monitor screen, and associates the input title with the box. It is preferable to include a title setting means for storing. In this case, the specification setting means and the title setting means of the flow chart creation means each time the box setting means displays the box on the monitor screen. It may be comprised so that it may be possible. Moreover, when only the specification setting means of a flow chart preparation means is provided, you may comprise the said specification setting means so that specification setting is possible every time a box is displayed on a monitor screen by a plate arrangement means.
Further, in the source program creation support system according to the present invention described above, the flow chart creating means further provides the user with a guidance including a plurality of questions set in advance for the flow chart creation, and the user is asked about the questions of the guidance. As a guidance means for interactively creating a flow chart based on the response inputted by the question, the question includes a question of the number of tasks, and automatically determines the number of decision boxes and processing boxes based on the user's response to the question. It is desirable to have guidance means for displaying on a monitor screen. In this case, suitably, the flow chart preparation means also acquires a time-lapse history between the guidance provided by the guidance means and the user's response to the guidance, and also displays the time-lapse history on the monitor screen. A maker means is provided.
Further, in the source program creation support system according to the present invention described above, the flow chart creating means shows a plurality of boxes by detailing the processing contents of at least one box of the first flow chart and the first flow chart created in advance. As a derivative relationship display means for displaying the relationship with the second flow chart on the monitor screen, when the original box specified in detail is selected while the first flow chart is displayed on the monitor screen, the box is used instead of the box. Preferably, derivative relationship display means for displaying a plurality of boxes in the corresponding second flow diagram is provided.
In addition, the above-described source program creation support system according to the present invention further includes a tree structure based on the dialogue with the user on the monitor screen for the data definition of the source program of the data used in the flowchart created by the flowchart creation means. The screen definition of the source definition of the screen used in the flow chart created by the flow chart creation means and the data definition creation means defined in accordance with the created data layout and on the monitor screen. It is preferable to have screen definition creation means for creating a screen based on a dialog and defining it based on the position and size of the elements of the created screen. In this case, it is preferable that the flow chart analysis converting means further comprises means for combining the source definition created based on the flow chart with the data definition and screen definition created by the data definition creating means and the screen definition creating means.
Further, the above-described source program creation support system according to the present invention further includes verification means for verifying the created source program, wherein the verification means displays a flow diagram corresponding to the source program to be verified on the monitor screen. On the displayed flow diagram, the user pauses the run of the source program, acquires a processing result, sets a pause set point for displaying the pass history and the processing result, and sets a path set point for acquiring only the processing result. Means, a means for running a source program to be verified, for displaying a route of passage according to the progress of the process on the flow diagram corresponding to the source program, and when the process reaches a pause set point; Means for pausing and displaying a history of passage of the pause set point and the pass set point; When the set point is reached, it is preferable to include means for displaying the value of the preset variable on the flowchart as a list of variables.
The present invention is configured as described above, and the event waiting state when a plurality of events and processing corresponding thereto randomly occurs can be appropriately represented on a flowchart, and a flow chart including such an event waiting state is also shown. Since it is only necessary to convert to a source program, generation of a source program including an event waiting state becomes easy. At this time, the identity between the logic of the specification in the flowchart and the logic of the source program is maintained.
In the case where a guidance means is provided, the user is prompted with the guidance, and a flow chart is automatically generated based on the guidance, so that the flow chart corresponding to the source program to be created is more easily created by the user. Done. Further, by providing the derivative relationship display means, the user can easily grasp the relationship between the original flow diagram and the development flow diagram in which the flowchart is developed, that is, the progress of the derivative and the progress of the logic of the program.
Moreover, by providing the data definition creation means and the screen definition creation means, a user can create a data definition while visually confirming the data definition of a tree structure, and can create a screen definition only by creating a screen on a monitor screen. have. Therefore, the data definition and the screen definition are easily created and repaired.
Moreover, by providing the verification means, it is possible to actually run the created source program and perform verification, and the result can be reflected in the modification of the source program.
1 is a block diagram showing a schematic configuration of a source program creation support system according to the present invention;
FIG. 2A is a block diagram showing a schematic configuration of a flow chart creation module in the system shown in FIG. 1; FIG.
2B is a block diagram showing a schematic configuration of a flow diagram analysis conversion module in the system shown in FIG. 1;
FIG. 2C is a block diagram showing a schematic configuration of a verification module in the system shown in FIG. 1; FIG.
3 is a flow chart showing an operation of the flow chart creation module shown in FIG. 2B;
4A is a schematic diagram showing a list of plates displayed by a function of a flow chart creation module;
4B is a schematic diagram of a screen shot displayed by the function of the flowchart drawing module;
4C is a schematic diagram of a screen shot displayed by a function of a flowchart creation module based on a dialogue with a user;
4D is a schematic diagram of a screen shot displayed by a function of a flowchart drawing module based on a dialogue with a user;
Fig. 4E is a schematic diagram of a screen shot displayed by the function of the flowchart creation module based on the dialogue with the user.
4F is a schematic diagram of a screen shot displayed by a function of a flowchart creation module based on a dialogue with a user;
4G is a schematic diagram of a screen shot displayed by a function of a flow chart creation module based on a dialogue with a user;
4H is a schematic diagram of a screen shot showing an image flow chart after completion displayed by a function of a flow chart creation module based on a dialogue with a user;
FIG. 5 is a schematic diagram of a screen shot showing a title flow diagram created by the title being input by the user in the image flow diagram shown in 4h; FIG.
6 is a schematic diagram of a screen shot showing an outline flow diagram created by inputting a specification to a user in the image flow diagram shown in FIG. 4H;
7A is a schematic diagram showing a screen shot showing an input screen for inputting a title and specification into a judgment box;
FIG. 7B is a screen shot showing a state in which a title and specification are input by a user on the input screen shown in FIG. 7A;
7C is an explanatory diagram showing master data of a judgment box in an input state as shown in FIG. 7B;
7D is an explanatory diagram showing an example of master data of a processing box in a state in which a specification is input;
7E is a flowchart for explaining an image flow diagram creation process executed by the event waiting notation function of the flowchart creation module, a screen shot,
7F is a screen shot showing an event flow diagram initial box group displayed by the event waiting notation function;
FIG. 7G is a screen shot showing a state in which another box is added to the display state of FIG. 7F by the event waiting notation function; FIG.
FIG. 7H is a screen shot showing an image flow diagram completed by adding an event flow diagram end box group to the display state of FIG. 7G by an event waiting notation function; FIG.
FIG. 7I is a screen shot showing a state in which a title flow diagram is created by inputting a title into the image flow diagram shown in FIG. 7G;
FIG. 7J is a screen shot showing a state in which a specification is entered in the image flow diagram shown in FIG. 7G to create an overview flow diagram,
8 is an explanatory diagram for explaining a hierarchical descending function at the time of creating a detailed flowchart in the flowchart creation module;
9A is a screen shot automatically displayed when a flowchart is created by the guidance function of the flowchart creation module;
FIG. 9B is an explanatory diagram illustrating guidance content and user response by the guidance function in the flowchart creation module; FIG.
Fig. 9C is a screen shot displayed at the time of creating a flow chart by the guidance function in the flow chart creation module based on the dialogue with the user,
9D is a screen shot displayed at the time of creating a flow chart by the guidance function in the flow chart creation module based on the dialogue with the user,
Fig. 9E is a screen shot displayed at the time of creating a flow chart by the guidance function in the flow chart creation module based on the dialogue with the user,
9F is a screen shot displayed at the time of creating a flow chart by the guidance function in the flow chart creation module based on the dialogue with the user,
Fig. 10A is an explanatory diagram illustrating guidance data in which the contents of guidance obtained at the time of creation of the flow diagram by the pacemaker function and the guidance function in the flow chart creation module and the user response are stored with the passage of time;
10B is a schematic diagram showing a guidance time table created from the guidance data shown in FIG. 10A;
11A is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11B is a schematic diagram of a screen shot displayed by the function of the data definition creation module based on the dialogue with the user;
11C is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11D is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11E is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11F is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11G is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11H is a schematic diagram of a screen shot displayed by a function of a data definition creation module based on a dialogue with a user;
11I is a schematic diagram of a screen shot of a file layout after completion, which is displayed by a function of a data definition creation module based on a dialogue with a user;
11J is an explanatory diagram showing an example of record data in the file layout shown in FIG. 11I;
12A is a screen shot showing an example of a screen to be created by a function of a screen definition creating module;
12B is a schematic diagram showing a list of screen definition plates displayed by the function of the screen definition creating module;
12C is a screen shot showing an attribute input screen of a frame field displayed by the function of the screen definition creation module;
12D is a screen shot showing an attribute input screen of a button field displayed by a function of the screen definition creation module, together with a frame previously created by the function,
12E is a screen shot showing a button created and displayed by the function of the screen definition creation module;
12F is a screen shot showing an attribute input screen of a character field displayed by the function of the screen definition creation module;
12G is a screen shot showing the line field attribute input screen displayed by the function of the screen definition creation module;
12H is a screen shot showing a numeric field attribute input screen displayed by the function of the screen definition creating module;
13A is an explanatory diagram for explaining the conversion to the C ++ language executed by the function of the flow diagram analysis conversion module;
13B is an explanatory diagram for explaining the conversion to the BASIC language executed by the function of the flow diagram analysis conversion module;
FIG. 13C is a flowchart showing processing when converting a flow diagram including event processing into a source program, which is executed by a function of the flow diagram analysis conversion module; FIG.
FIG. 13D illustrates a source program converted from a flow diagram including event processing; FIG.
FIG. 13E is a diagram of a source program subsequent to the source program illustrated in FIG. 13E;
14A is a screen shot showing a state in which a pose and a path set point are set on a flowchart by a function of a verification module;
14B is a screen shot showing a list of pass histories acquired and displayed by the function of the verification module;
14C is a screen shot showing a list of variable values acquired and displayed by the function of the verification module;
FIG. 15 is a diagram showing a representation of a flowchart of a program including event processing, which is assumed from a flowchart created by a conventional example.
EMBODIMENT OF THE INVENTION Hereinafter, preferred embodiment of the source program creation support system of this invention is described with reference to drawings.
The system of the present invention is constituted by a computer program installed in a PC. When the program is largely divided into functions, as shown in Fig. 1, the flow
Flowcharting Module (10)
It is for creating a flowchart of a program to be created, and has a function of completing an outline / detailed flowchart based on selection and arrangement of boxes by a user on a PC screen, and input of a title and specification. . At this time, the hierarchical descending function is used to define the logical relations while performing the association from the outline to the details and the upper flow chart and the lower flow chart, and all are related from the top flow chart to the bottom flow chart. At the same time, specification definition can be performed. The generated outline / detailed flow chart is stored as attribute data including input / output relationships for each box included in the flow chart.
As a result, the work for creating the flow chart is efficient, and even when the specification change needs to be made, the changed part can be confirmed on the flow chart, so the work for specification change is also efficient.
Create Data Definition Module (20)
On a PC screen, a user creates a file layout in a tree shape. The file level and record level are defined in accordance with the guidelines. The record item can define new items and attributes by selecting the top, bottom, left, and right sides of the data definition processing box. If the top / bottom side is selected, define a new item in the parallel position above and below the item. If the left side is selected, a new item is defined at the upper layer position of the item, and if the right side is selected, a new item is defined at the lower layer position of the item. The deletion of an item is performed by the user selecting a target position. When a change in the number of digits (bytes) or the like of an item occurs, the number of digits is automatically adjusted by changing the item attribute. The created data definition is stored as attribute data for each item.
Since all the processing necessary for data definition can be performed on the PC screen, and data definition can be created while visually confirming the data definition of the tree structure, the creation and maintenance of the data definition are efficient.
Screen definition creation module (30)
A screen layout is created on a PC screen using a function that applies a graphic process utilized for graphic creation. At this time, the user first selects the screen elements included in the screen layout from the list of screen elements, inputs the definition contents of the screen elements, and designates a position and a size on the screen so that each screen element included in the screen layout is selected. Write. Specification changes and bug fixes are performed by moving, adding or deleting screen elements such as lines and plates to required positions. The created screen definition is stored as attribute data (including position and size data) for each screen element.
Since all the processing necessary for screen definition can be performed on the PC screen, and screen definition can be created while visually confirming, the screen definition can be easily created and repaired.
Flowchart Analysis Conversion Module (40)
The data definition and screen definition created by the
Verification module (50)
The created source program is run to verify the program. On the PC screen, a flow chart corresponding to the source program to be run is displayed, and when the source program is run, the route of the processing is displayed on the flow chart. Moreover, a user can set a pause point and a pass point to arbitrary points on the passage route of the said flowchart. When the program processing reaches the position where the pause point is set, the processing is paused, various variable values in the flow diagram at that time are obtained and displayed, and the passing history of the pause point and the pass point is displayed. When the program processing reaches the position where the path point is set, various variable values in the flow diagram at that time are acquired, but the processing continues. If an error occurs during a program run, the box and the processing line are displayed in the error list. As a result, the operation of the created source program can be verified, and if there is a mistake, it becomes easy to detect and correct it.
As shown in FIG. 2, the function of the
The outline functions of these
Image Flow Charting Module (11)
Based on the dialogue with the user, an image flow diagram of the main program is created. An image flow chart is a flow chart which defines only a box and its connection relationship. This module includes an event
Title Flow Charting Module (12)
In each box of the created image flow diagram, a title flow diagram is created by inputting the title of the processing in the box to the user. In addition, a title means the summary of a process.
Overview Flow Diagram Definition Module (13)
In each box of the created title flow diagram, a process flow chart is input to the user to create an outline flow chart of the program.
Overview Flow Diagram New Creation Module (14)
Whenever the user sets a box to be included in the flow chart by dialogue with the user, the outline flow chart is completed by inputting a specification (or specification and title) into the box.
Guidance Module (15)
The order of thinking for creating the flow diagram is also provided to the user as a guidance message. The guidance message is done in the form of a query response to define the specifications of each box, thus completing the overview flow diagram. In the option, if the preset time elapses during the question and answer, the user is prompted to input another question.
Pacemaker Modules (16)
In the guidance mode, a limit of the response time is set for the query response during the flow chart creation, and when the time limit elapses, the author is notified of the job by another query response such as "I do not know". In addition, by analyzing the elapsed time of the process, the skill and clumsiness of the creator is determined to suggest work improvement.
Detailed Flow Diagram Definition Module (17)
The hierarchical descending function is provided, and a flow chart (detailed flow chart) of each floor from the first lower floor level to the lowest floor level in the created flow chart is created based on the dialogue with the user.
When the flowchart creation mode is selected and the
On the other hand, if it is determined in step S1 that the image flow diagram creation mode is not selected, and it is determined in step S5 that the outline flow and the new creation mode are selected, the flow advances to step S6, and the outline flow also shows the
In addition, in step S1, it is determined that the image flow diagram creation mode is not selected. In step S5, it is determined that the outline flow also does not select the new creation mode. In step S7, it is determined that the guidance mode is selected, and in step S8. If it is determined that the pacemaker mode is selected, the process proceeds to step S9 and the
When any one of steps S4, S6, and S10 ends, and the detailed flow diagram definition mode is selected, the flow advances to step S11, and the detailed flow
In this way, when the detailed flowchart to the lowest layer is completed and it is determined by step S12, the process by the
As shown in FIG. 2B, the function of the flow
The function of the
The system of the present invention also includes a database (DB) for storing data relating to the functions of the above modules. As shown in Fig. 1, the DB includes a flowchart plate master DB1, a flowchart file DB2, a guidance master DB3, a guidance data DB4, a data definition file DB5, a screen definition plate master DB6, a screen definition file DB7, a language master DB8, A coded technology master DB9, a source program file DB10 and a pass history / variable value file DB11 are provided.
These databases store the following data.
Flowchart plate DB1
Reference plates, such as a start terminal, an end terminal, a processing box, a judgment box, a screen display box, a printing box, a discharge line, and an outflow line, which are used at the time of creating the flowchart by the function of the
Flowchart file DB2
The data for each box in the flowchart created by the function of the
Guidance Master DB3
Flows executed by the
Guidance data DB4
When creating the flow executed by the
Data definition file DB5
The data definition set on the PC screen by the function of the data
Plate Master for Screen Definitions DB6
The element of the plate required for screen creation, such as a box and a button, used when creating the screen definition by the screen
Screen definition file DB7
The screen definition set on the PC screen by the function of the screen
Language master DB8
A check table of the specification language of the user input and the source code which are referred to when converting the flow diagram created by the function of the flow diagram
Code Technical Master DB9
The matching table between the arrangement position of the specification of the user input and the arrangement of the source code, which are referred to when the flowchart is created by the function of the flow diagram
Source program files DB10
The flow diagram also stores the source program created by the function of the
Notification history / variable value file DB11
When the created source program is run and verified by the
Next, the configuration of the system of the present invention will be described in more detail by referring to the image displayed on the PC screen by the functions of the
When the user starts the source program creation application of the present invention on the PC screen and selects the flow chart creation mode, the flow
When the image flow
After that, when the user selects the screen display box, the judgment box, and the file processing box in order from the displayed plate list, as shown in Fig. 4C, the screen input processing box A, the flow chart creation display area of the PC screen, The judgment box B and the file processing box C are displayed, and whenever the respective boxes are displayed, the lower discharge lines a, b1, and c are displayed at the lower end thereof. In addition, whenever a box is newly displayed, it is automatically updated and displayed so that the dashed process box and the dashed outflow line may be located at the lower end thereof. In the example of FIG. 4C, since the file processing box C becomes the last selected box, a broken line processing box and a broken line outgoing line are automatically displayed at the lower end of the bottom outflow line c.
When the user selects the right front end of the judgment box B in the state shown in FIG. 4C, as shown in FIG. 4D, the right outflow line b2 is automatically displayed at the right end of the judgment box B. As shown in FIG. Then, the broken processing box and the bottom outflow line in the state of FIG. 4C are automatically deleted, and the broken processing box and the right outflow line are automatically displayed on the right side of the determination box B. FIG. When the user selects the right end of the right outflow line b2 in the state shown in Fig. 4D, as shown in Fig. 4E, the outflow outflow line connected to the right outflow line b2 is displayed (connected outflow outflow line b2). ], The dashed processing box and the bottom discharge line are displayed at the bottom thereof.
Subsequently, when the user selects the treatment box from the plate list, as shown in Fig. 4F, the treatment box D and its lower discharge line d are newly arranged, and at the lower end of the lower discharge line, the treatment box Is automatically displayed as a dashed line (or flashing state). In addition, the bottom discharge line is automatically displayed in broken lines at the bottom of the processing box. In order to flow the lower outlet line d into the one outlet line c, the lower outlet line d at the lower end of the treatment box D and the lower outlet line c at the lower end of the pile processing box C are selected. As shown in FIG. 4G, the lower outlet line of the newly disposed treatment box D is coupled to the lower outlet line c, and the connected outlet line d is displayed. Thereafter, when the user selects the judgment box E, sets the outflow line, and selects the print processing box F and the end terminals in order, an image flow diagram as shown in Fig. 4H is created. At this time, when the user selects a "numbering" button (not shown) on the PC screen in order to assign a process sequence number, a box number as shown in Fig. 4H is automatically attached to each box. Each time a box is selected and arranged, a temporary box number may be assigned, and a regular box number may be assigned when a "numbering" button is selected.
After creating an image flow chart, if a user wants to delete a box from the flow chart, the box is deleted by selecting "Delete" from a menu displayed by the user selecting the box. If one box is to be added, the addition is performed by the user selecting a box from the plate list and moving the cursor to a position to be inserted. After such a change is executed, the box number is reattached by selecting the "numbering button" again.
The type of each box and the connection relationship between the boxes included in the created image flow chart correspond to the box number, the flow diagram name, and the flow diagram ID, and the flow diagram is stored in the file DB2.
Next, when the user selects the title flow chart creation mode, the title flow
FIG. 5 shows a state in which a title is input to each box of the image flow diagram shown in FIG. 4H and a title flow diagram is created. The flow diagram of this example is "NIPPO-HIZUKE". The input title of each box is associated with the box number, for example, "screen input processing" is associated with
When creation of the title flow diagram is completed and the user selects the outline flow diagram definition mode, the outline flow
FIG. 6 shows a state in which an outline flowchart is created by inputting specifications of each box of the image flow diagram shown in FIG. 4H.
In the above, the case where a title and a specification are input on each screen was demonstrated. Instead of the above configuration, the functions of the title flow
When the user selects the judgment box (box number 3) in the image flow diagram shown in FIG. 4H, an input screen as shown in FIG. 7A is displayed. A plurality of input fields are displayed on the screen, and field numbers Fxxx are associated with these input fields. The input line (inflow line), output line (outflow line), the current box number, and the next box number inputted at the time of creation of the image flow are displayed together with one title input field and four specification input fields which are not input. In addition, the input field is also displayed in the settable position of the inflow / outflow ship and the settable position of the branch condition, which were not set at the time of creation.
In the example of FIG. 7A,
As shown in FIG. 7B, the user inputs "date check" into the title input field F021 on the screen shown in FIG. 7A, and enters "Dl (data name)" (F011) and "050303" into four specification input fields. If (F013), "date" (F012) and "today" (F014) are input, a master of
In addition, when a user selects the process box of
In this manner, the titles and specifications of all the boxes in the image flow diagram are input, and as a result, a master for each box is created. The created box master is associated with the flow diagram ID of the flow diagram and stored in the flow diagram file DB2.
In the above description, after creating an image flow diagram as shown in FIG. 4H, it is assumed that a title and a specification are input for each box. However, an overview flow diagram is generated by starting the
Thereby, the box master as shown to FIG. 7C (for determination box) and FIG. 7D (for processing box) is created.
In addition, one or more of the image flow
Here, the flow of FIG. 7E for the function of creating the flow chart containing the waiting state of the several randomly generated event performed by the event waiting
First, when the user intends to create a flow chart including a plurality of event waiting states, the flow chart creation mode is selected. As a result, as described above, when the flow
In this state, when the user selects an event box from the displayed plate list, the image flow
Then, the event waiting
If the user has a box (including an outflow line and an inflow line) to be added to the flow chart displayed on this screen, the user selects an appropriate box from the plate list and designates the arrangement position with a cursor. The event
In FIG. 7G, in the flow diagram on the screen shown in FIG. 7F, the user adds three judgment boxes (
In such a state, when the user selects the event end box from the plate list, the event
In this way, an image flow chart corresponding to a program including event processing is created, and when the event
When the user selects the "Title Flow Diagram Creation Mode" in order to input the title and branching conditions into the respective boxes of the image flow diagram thus created, the title flow diagram creation module is activated as described above, and the image flow diagram is activated. In each box and outflow line in the figure, the user can input a title and branching conditions. When the program intended to be created by the user is a name address registration program, for example, as shown in Fig. 7I, a title and a branch condition are input. In the example shown in Fig. 7I,
In addition, even if the user is inputting a title and branch condition, if there is an unnecessary box, it can be deleted by selecting the box and selecting the "Delete" menu as described above. If there is a box to which an event processing box is to be added, as described above, the user can add a box by selecting the box from the plate list and moving the cursor to the position to be inserted.
As described above, whenever the user selects one or an appropriate number of boxes from the plate list and displays the flow in the creation area, the user can input the title, input / output line, and branch condition (in the case of the judgment box) of the box. You may make it work.
The created title flow and the flow are also stored in the file DB2.
When the input of the title and the branch condition is completed, the user next selects the "Overflow flow diagram definition mode" in order to enter the specification, and the outline flow
In addition, as described above, in the coded description master DB9, a library of program modules that are already created in correspondence with a box with a high frequency of use is stored, and a program module ID that specifies these program modules, that is, a function name is used as a specification. You can enter In Fig. 7J, the specifications "GPG_01 ()", "GPG_02 ()", and "GPG_02 ()" inputted into the boxes of boxes Nos. 2 to 4 are function names corresponding to these boxes.
In addition, as will be described later with reference to FIG. 8, a box following a complicated process in the outline flow diagram is generally developed as a flow diagram of a lower layer by the hierarchical descending function of the detail flow
The outline flow
The specifications entered in the
The outline flow diagram thus created and the flow are also stored in the file DB2.
As is apparent from the above, the flowchart of the program including the event processing created under the support of the system of the present invention can display the event waiting state in a state that is easy for the user, even when the event processing occurs randomly. Therefore, the user can easily create a flow chart that matches the intended processing contents.
In addition, conventionally, the language described in the processing box is a description in accordance with the format peculiar to the manufacturer's language in order to create a source program. In the system of the present invention, free writing can be performed without being restricted to the language-specific format of the maker. Such a notation method is called "new notation" in this specification, and can make a specification in the language which a user reader understands easily by this. That is, the written user language is converted into a maker language format at the time of source code conversion via the language master. Therefore, by using this function, the general computer language (C, C ++, Java, etc.) after conversion can be freely selected at the time of conversion to source code.
The conversion from the specification to the source code is described in detail later.
Next, when the detail flow definition mode is selected, the detail
As shown in Fig. 8, when function B is set in the processing box of the main flow diagram A, which is a schematic flow diagram, and the function B has a complicated structure, the user designates the function B on the flowchart and descends the hierarchy. When the menu is selected, the flow chart creation screen for processing function B is automatically displayed. The sub-flow chart B is created by talking to the user on the screen and performing the same processing as that of the above-described schematic flow chart. If the created subflow diagram B contains the function C, when the user designates the function C and selects the hierarchical descending menu, the flow chart creation screen of the function C is displayed and the subflow diagram C is created. . If C also includes the function D in the subflow, the subflow for processing the function D also creates D.
By repeating the above steps in this way, a subflow diagram of any hierarchy can be created, and thus, even if the processing in the main flow diagram is complicated, such a function of the detailed flow diagram definition module 17 (layer descending function) ), The flow chart of the lowest layer can be easily created.
When the user attempts to create a schematic flow diagram and selects the guidance mode, the
FIG. 9B shows an example of data stored in the guidance master DB3. In addition to the initial flow form, the guidance master DB3 stores contents to be asked to the user as guidance data in correspondence with the level form of the flow diagram. .
After displaying the initial flow form, the
Subsequently, for a question of title names of the first to third tasks, for example, "daily report processing", "end of month processing", and "end of year processing" are entered, in the judgment box and processing box shown in Fig. 9C, The corresponding title is automatically displayed. Subsequently, when the user responds to the question about the task to be added and says that there is an additional task, and the title of the fourth task is " aggregation processing " If there are no further tasks, the number of functions of the first "daily report processing" is queried (for example, "how many functions of daily report processing") are asked, and in response to that, 3 functions are inputted. As shown in Fig. 9E, the daily report processing box in Fig. 9D is deleted, and three judgment boxes and three processing boxes are automatically displayed. Then, if the user acquires that the three processing contents are "registration process", "correction process", and "delete process", the flow chart as shown in Fig. 9F is displayed as a result.
In this way, a schematic flow chart can be created by repeatedly displaying the guidance and the user response based on the guidance stored in the guidance master DB5. The contents of the schematic flow chart are stored in the flow chart file DB2 as described above, and the query response contents are stored in the guidance data DB4 as guidance data.
At this time, it is common to advance to a plurality of processes, as one process includes a plurality of processes (originally), and one of the plurality of processes includes a plurality of processes (first development). In this specification, such a case is referred to as "derivative relationship", the original box is called the derived box, and the plurality of advanced boxes of the box are called the derived box. For example, when a title flow diagram as shown in FIG. 9D is created, the "daily report" box (box number 9), the judgment box (
In the system of the present invention, such derivative relations and flows are also stored in the file DB2. For example, the box master of the derived box (
This representation of derivatives makes it easier to grasp the progress of derivation and the progress of the logic of the program.
When the user selects the pacemaker function, the
The time until the user responds to the question by the
The contents of the outline flow diagram completed by the functions of the
FIG. 10A illustrates data stored in the guidance data DB4 when executed in the pacemaker mode. In addition, when the guidance mode other than the pacemaker mode is executed, data on time is not stored in the guidance data DB4, and only the relationship between the question and the response thereto is stored.
10B shows the guidance data shown in FIG. 10A as a guidance time table. The
Next, the data
In this state, when the user selects the "confirm" button (not shown), as shown in Fig. 11B, the file information box "KOKYAKU-F" is automatically generated and displayed at the lower position of the "file layout", and The record length is 123 and the customer file is displayed.
Next, the input screen of the item information box as shown in FIG. 11C is displayed. When an item attribute (item name, Japanese name, type, number of digits) is input on this input screen, and the user selects a confirmation button, a screen as shown in Fig. 11D is displayed. In this example, the item name = R1000, Japanese name = name record, type = character, digit = 123, and a record information box of "Rl000" is automatically generated and displayed at the bottom of "KOKYAKU-F", and the record length is 123. To be and to be a full name record.
When creating a detail item (i.e., a lower layer item) of record information of record name "R1000", the user instructs the right end of the box of "R1000". As a result, as shown in Fig. 11E, an item information box is generated at the lower layer position of the box and displayed in broken lines. Indicates a position (right end of the box) selected by the user. Then, the input screen of the item information box as shown in FIG. 11C is displayed again. When the user enters an item attribute on the screen, for example, item name = K1100, Japanese name = key portion, and digits = 7, as a result, the item information box "Kl100" is automatically created and displayed as shown in Fig. 11F. , And also a key portion and seven digits are displayed. In the same way, the lower item box and its attributes are set in turn.
When a new item information box is to be created on the same floor, the user designates the upper side or the lower side of the box of the layer. As a result, as shown in Fig. 11G, a new item information box is generated above or below (but on the same floor) of the item information box and displayed as broken lines. In the example of FIG. 11G, either the lower side of the item "Kl110" is selected, or the upper side of the item "Kl130" is selected.
When a new item information box is to be created on the upper layer of the already set item information box, the user designates the left side of the item information box. As a result, as shown in Fig. 11H, a new item information box is generated and displayed in one layer (main layer) of the item information box.
Also for these tentatively generated item information boxes, the attribute information is displayed on the file layout screen by the user inputting and determining attributes on the input screen of the item information box shown in FIG. 11C.
In this way, the file layout of the data definition information as shown in Fig. 11I is created in a tree structure and completed. The created file layout is stored in the data definition information file DB5.
If record layout "R1000" in the file layout in the completed or incomplete state is selected, the contents of this item are output in the form shown in Fig. 11J. When it is necessary to modify the file layout of the completed or incomplete state, for example, when a new item needs to be added, a blank as shown in Fig. 11J is used. If no blanks exist or if the digits are insufficient, an alarm is displayed.
Next, the structure of the
When the user wants to create a frame (display frame) FR, when the frame plate is selected in the screen definition plate list, the frame field attribute input screen shown in Fig. 12C is automatically displayed. On this screen, the user inputs the thickness of the line, the line type, and the color of the line (or changes the initial value displayed in advance), and on the screen layout area, the user moves the cursor by operating the mouse to input the input thickness and line type. And graphics drawing of colored lines are executed to display a frame (frame FR in FIG. 12D). The X-Y coordinates of the generated frame are automatically acquired. The various attributes shown in FIG. 12C are associated with the frame ID and stored in the screen definition file DB7.
Subsequently, the user selects a button plate from the screen definition plate list, inputs an attribute from the button field attribute input screen shown in Fig. 12D, and moves and operates the cursor, so that various buttons are created on the screen as shown in Fig. 12E. . The title on the button ("Return", "Search", "Head", "Earth") is displayed by the user inputting the title in the display character field of the button field input screen shown in FIG. 12D. In addition, the X-Y coordinates of the start position and end position of each button are automatically obtained by reading the position coordinates of the created button. The various attributes shown in FIG. 12D are associated with each button ID and stored in the screen definition file DB7.
Similarly, screen elements of character fields, lines, and fixed characters are created, and the screen shown in Fig. 12A is created. And those definitions are stored in the screen definition file DB7. 12F to 12H show attribute input screens of character fields, lines, and numerical fields, and these attribute information are stored in the screen definition file DB7 in association with the respective IDs.
After the detailed flowchart is created and the data definition and the screen definition are created, when the user selects the conversion mode and starts the flowchart
When the flowchart is completed without contradiction, the source
By the way, the language described in the processing box is usually a description in accordance with the format peculiar to the manufacturer's language in order to create a source program. In the system of the present invention, free writing can be performed without being restricted to the language-specific format of the maker. Such a notation method is called "new notation" in this specification, and, accordingly, a specification can be created in a language easily understood by a user's original. That is, the written user language is converted into a maker language format at the time of source code conversion via the language master. For this reason, using this function, it is possible to freely select the general-purpose languages (C, C ++, BASIC, Java, etc.) after the conversion to the source code.
Refer to Language Master DB8 and Coded Technology Master DB9 to convert the new notation type specification that becomes the user language to the C ++ language, but the correspondence between the new notation type specification stored in the language master DB8 and the source code of the C ++ language. To illustrate.
Processing contents "Combines the character string of area A and the character string of area B and stores it in area A"
New notation method: A + = B;
C ++: stract (A, &B);
Becomes
The processing content "adds the value of the J area to the value of the C area, and stores the result in the C area. And add 1 to the value in the J area.
New notation method: C = C + J
J = J + 1
C ++ language: C = C + J J ++;
Processed contents "Add 1 to the numerical value of the area. Then, add the value of the J area to the value of the C area, and store the result in the C area.
New notation method: J = J + 1
C = C + J
C ++ language: C = C + J ++ J;
Comparison operators (equal sign, inequality sign, greater than or equal to)
New notation method: = ≠ ≤ ≥
C ++ language: ==! = <=> =
Contents of processing "Stop processing for the specified time (stop time: milliseconds)"
New notation method: Cyudan (but the stop time is set to 1.5 seconds as standard)
C ++ language: Sleep (1500), but the stop time is between 1.5 seconds
Processing contents "The specified sound continues to sound for the specified time (frequency: Hz, duration: millisecond)"
New notation method: Oto (but set at 1/4 second as 900 Hz as standard)
C ++ language: Beep (900, 250) (specified if it rings for 1/4 second at 900 Hz)
Processing contents "Display character of" input error ""
New notation method: Hyoji (800200)
C ++ language: ADCHAR (meaning "input error" in field 800200)
Processing contents "displayed in the specified color"
New notation: Aka Midori Ao
C ++ language: RGB (255,0,0) RGB (0,255,0) RGB (0,0,255)
New notation method: Kuro Siro
C ++ language: RGB (0,0,0) RGB (255,255,255)
The correspondence between the new notation method and the C ++ language exemplified above is stored in the language master DB8. In addition, such a correspondence relationship is created and stored according to the type of computer language required. In addition, in the case of the new notation system, since it becomes the language notation which a user is accustomed to, you may use hiragana or katakana etc. instead of the alphabet.
For example, when the processing content is "set the color of the character to red to display an error message, sound an alarm, and wait for 1.5 seconds", in the new notation method and the C ++ language, the following is expressed.
New notation type error message processing
Text (Aka);
Hyoji (800200, "Input error.");
Oto;
Machi;
Error message notation in C ++ language
SetTextColor (RGB (255, 0, 0));
ADCHAR (800200, "Input error.");
Beep (900, 175);
Sleep (1500)
Therefore, according to the system of the present invention, when the specification content is input in the flow chart, it is possible to input normally in a plain language of the user's original, and the displayed user language is converted into C language or the like through the language master table. Even if the user does not know the computer language, input is easy.
The conversion operation to the source code will be described taking the judgment box (box number 3) set as shown in Fig. 7B as an example.
The process box content analysis module 22 (FIG. 2B) of the flow diagram
That is, since the processing box type is "06" indicating the judgment box, the technical master corresponding to "06" is read from the coded technical master DB9. Then, the process box number "3" is copied to the position of the process number, and the data names "D1" and "050303" of the left term and the right term are respectively copied to the corresponding positions. In addition, the language master DB8 is searched for, and "= =" of the C ++ language corresponding to the branch condition "=" is read and copied to the judgment term. In addition, the box numbers of the branch at the time of determination and the branch at the time of determination are obtained from the master data of the flow diagram file DB2 and copied to the corresponding positions.
As a result of assigning data as shown in Fig. 13A, the following source program (C ++ language) is generated.
G03: if (D1 == 050303) [goto G54;]
else [goto G19;]
On the other hand, in the case of the BASIC language, as shown in Fig. 13B, data is allocated.
G03, if D1 = 050303 GOTO G54.
GOTO G19.
The source program of is obtained.
Here, the flow diagram including the event waiting process shown in FIG. 7J will be described in detail with reference to the flow diagram of FIG. 13C as an example in which the flow diagram including the event waiting process is converted to the C ++ language. At this time, it is assumed that an OS including an event processing definition program module, such as MicroSoft, is installed in the user's PC.
When the flow chart
The model library group includes functions corresponding to the function names of the initial processing box before drawing (box number 2), the initial screen processing box (box number 3), and the initial processing box after drawing (box number 4) for screen processing. The box
Subsequently, in step S86, the process box
Then, the process box
Subsequently, in step S90, the process box
As a result, the flow chart is converted into a source program. 13D and 13E (FIG. 13E is a continuation of FIG. 13D) show an example of the source program created in this way. Naturally, it is not necessary to judge and process in the order shown in Fig. 13C. For example, steps S88 and S89 may be performed at the front of step S82, and other appropriate modifications are possible.
In this way, the flow chart
In this way, the master data of all the boxes in the flowchart are read from the flowchart file DB2, the data is replaced with an array of the programming language designated by the user, and then converted into the source program of the language. As described above, the source program converted from the flowchart is stored in the created source program file DB13 together with the source code of the data definition and the screen definition used for the program.
The source program converted by the flow analysis
Next, the
On the outflow line of the flowchart, the user sets the point at which the pause function (=) and the path function (●) are executed as shown in Fig. 14A. The pause function is a function of acquiring the execution result (including the values of various variables) of the process until reaching the set point, and pausing the process when the set point is reached. The path function is a function of acquiring the execution result (including the values of various variables) of the process until reaching the set point, and continuing the process without pausing.
And when the source program created corresponding to the said flow chart is run, a process will be performed, displaying the progress route on a flowchart by the function of the process passage route display module 31 (FIG. 2C). When the process shifts to the lower flow chart during the run of the source program, the lower flow chart is displayed by the hierarchical lowering function, and the passage route is also displayed on the flow chart.
During the execution of the process, the function of the process result acquisition / display module 32 acquires, as a pass history, the order of passing the set point of the pause function and the set point of the pass function, and the process passes in advance. The value of the set variable is acquired every time the processing of the box containing the variable is completed and stored in the passage history / variable value file DB11.
For example, as shown in FIG. 14A, when the pose set point S013 is set and the path set points P009 and P010 are set, when the process proceeds to the pose set point S013, the program is processed. Is paused. Then, the process result acquisition / display module 32 refers to the pass history / variable value file DB11 and passes the pause set point S013 and the pass set points P009 and P010 until the pause. The history is searched and displayed as a list of pass histories, and the values of various preset variables in the flowchart are displayed as a list of variable values.
14B and 14C show such a pass history list and a variable value list. In the example of the passage history list shown in Fig. 14B, after passing through the pass setting points P0O9 and P010 three times, respectively, branching is made from the judgment box of
If an error occurs during the run of the created source program, the function of the process error display module 33 displays the box number and the process line as an error table on the PCC screen.
In this way, since the source or the like of the bug occurrence can be displayed by verifying the source program, the modification is easy.
Resumption of the paused processing is executed by selecting a resume button (not shown).
Since this invention is comprised as mentioned above, even a user who does not have advanced knowledge can easily create arbitrary source programs, and since the created flow chart is converted into a source program, the specification in a flow chart The sameness of the logic of and the logic of the source program is maintained. In particular, the event waiting state when a plurality of events and processing corresponding thereto randomly occur can be appropriately represented on the flowchart.
In addition, since the user's input is prompted by the guidance and a flow chart is automatically generated based on the user's input, the flow corresponding to the source program to be created is made easier. In addition, since the derivative can be provided to the user, which is a relationship between the original flow chart and the progress flow chart in which the flowchart is advanced, the user can easily grasp the progress of the derivative and the progress of the logic of the program.
In addition, the user can create the data definition while visually confirming the data definition of the tree structure on the PC screen, and can create the screen definition only by creating the screen on the PC screen. Therefore, the data definition and the screen definition are easily created and repaired.
Further, verification can be performed by actually running the created source program, and the result can be reflected in the modification of the source program.
Claims (15)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2006063999A JP3850867B1 (en) | 2005-04-19 | 2006-03-09 | Source program creation support system |
| JPJP-P-2006-00063999 | 2006-03-09 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| KR20080104057A true KR20080104057A (en) | 2008-11-28 |
Family
ID=38474678
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020087024625A KR20080104057A (en) | 2006-03-09 | 2006-08-29 | Source program creation support system |
Country Status (3)
| Country | Link |
|---|---|
| KR (1) | KR20080104057A (en) |
| CN (1) | CN101379466B (en) |
| WO (1) | WO2007102232A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106371823A (en) * | 2016-08-22 | 2017-02-01 | 广州酷狗计算机科技有限公司 | Code block generation method and apparatus |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPS6154539A (en) * | 1984-08-27 | 1986-03-18 | Hitachi Ltd | Input system of program specifications |
| JPH0623987B2 (en) * | 1984-10-29 | 1994-03-30 | 株式会社日立製作所 | Interactive drawing method |
| JPS61249149A (en) * | 1985-04-26 | 1986-11-06 | Mitsubishi Electric Corp | Program tracing device |
| JPH0916385A (en) * | 1995-06-30 | 1997-01-17 | Toshiba Corp | Application development method and device |
| JP3611061B2 (en) * | 1996-02-05 | 2005-01-19 | 本田技研工業株式会社 | Graphic creation device |
| JPH10293686A (en) * | 1997-04-18 | 1998-11-04 | Hitachi Ltd | Tracking program generating method and device |
| JPH11296357A (en) * | 1998-04-08 | 1999-10-29 | Oki Electric Ind Co Ltd | Flow chart input device |
| JP2003076546A (en) * | 2001-09-03 | 2003-03-14 | Minoru Kano | Method for plotting graphic, method for plotting flow chart and method for generating computer program from flow chart |
-
2006
- 2006-08-29 WO PCT/JP2006/316923 patent/WO2007102232A1/en active Application Filing
- 2006-08-29 KR KR1020087024625A patent/KR20080104057A/en not_active Application Discontinuation
- 2006-08-29 CN CN2006800530675A patent/CN101379466B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007102232A1 (en) | 2007-09-13 |
| CN101379466A (en) | 2009-03-04 |
| CN101379466B (en) | 2011-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5161211A (en) | Method and system of specification processing | |
| US5287449A (en) | Automatic program generation method with a visual data structure display | |
| CN107544437A (en) | Procedure editing device, method and storage medium | |
| CN115576950A (en) | Report generation method based on JSON configuration file | |
| JP3850867B1 (en) | Source program creation support system | |
| KR20080104057A (en) | Source program creation support system | |
| JP2004157927A (en) | Creating system for business form input, creating program and creating method | |
| JP4629183B2 (en) | Requirement specification description support apparatus and method, and recording medium | |
| US5812981A (en) | Method of creating a data item object suitable for an application from a standard object oriented part | |
| Niere | Visualizing differences of UML diagrams with Fujaba | |
| WO2006114899A1 (en) | Source program creation support system | |
| JP2001273342A (en) | Product manufacturing method and product manufacturing support method | |
| JP2009087144A (en) | Development support device and development support program | |
| US7120616B2 (en) | Method for specifying, executing and analyzing method sequences for recognition | |
| US20010002834A1 (en) | Method for inputting and acquiring requirement | |
| JP2001273125A (en) | Method and system for automatically generating source program, and program recording medium therefor | |
| JP3310415B2 (en) | CAD equipment | |
| JPH0588863A (en) | Program development supporting system | |
| CN112596475B (en) | System safety analysis system based on process control | |
| JPS61267870A (en) | Form production processing system | |
| EP0315172A2 (en) | Automatic program generation method with a visual data structure display | |
| JP2003058370A (en) | Source code generation system | |
| JP2000148232A (en) | Display image data generation system of central monitor and control equipment | |
| EP0726517A1 (en) | A computer aided program generating system | |
| CN117819197A (en) | Control method and system of automatic flow, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| WITN | Withdrawal due to no request for examination |