JP2015148925A - Program generation device and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technology for reducing a correction-affected range by improving legibility in the automatic generation of a GUI (Graphical User Interface) program.SOLUTION: Template selection means selects a template to be used for the source code of the program of a target screen on the basis of a screen configuration specified in a screen specification. Scenario definition creation means creates the scenario definition of screen transition on the basis of a processing scenario specified in the screen specification. Generation processing means generates a first automatic generation source code for achieving the screen configuration of the target screen and an operation corresponding to an input to the target screen by using the template and the scenario definition. Unique processing presence/absence determination means determines whether or not unique processing to be individually created is present. Model source code generation means generates, when it is determined that the unique processing is present, a second automatic generation source code as the model of a source code indicating the unique processing independently of the first source code.

Description

  The present invention relates to an apparatus and method for automatically generating a program having a GUI (Graphical User Interface).

  In an example of program development having a conventional GUI, screen design is first performed. In the screen design document, a GUI part and a callback part for an event generated from the GUI are defined. The programmer develops the GUI portion based on the screen design document. Subsequently, the programmer develops a callback portion for an event generated from the GUI based on the operation content defined in the screen design document. If necessary, the programmer develops a portion of common processing used in the GUI program. As the common process, for example, a process that is used in a plurality of locations of the GUI program, and therefore, there is a process that is commonly described so that it can be called from another part.

  FIG. 1 is a diagram for explaining the influence of a change in the screen design document in program development. The program developed by the above-described method includes GUI display source code 110, callback processing source code 120, and common processing source code 130. Therefore, when there is a change in the screen design document, the programmer modifies the GUI display unit source code 110 and the callback processing source code 120, and further modifies the common processing source code 130 as necessary. All the correction work is done manually.

  A technique for automating the development of a GUI program is disclosed in Patent Document 1. Patent Document 1 describes that “a UI (user interface) program for operating software is automatically generated from a system software UML design document and an interface program” (see the summary).

JP 2003-140893 A

  As described above, Patent Document 1 describes a method for automatically generating a GUI program from a UML design document and an interface program. However, in the method of Patent Document 1, the source code of the program is generated in a form in which a portion that realizes common processing and a portion that realizes unique processing not included in the common portion are mixed.

  Therefore, the readability of the automatically generated source code is low. Further, when the program needs to be corrected, work for reconstructing the entire target program occurs regardless of which part the correction is.

  An object of the present invention is to provide a technique for improving readability and reducing a range affected by correction in automatic generation of a GUI program.

  A program generation apparatus according to an aspect of the present invention is a program generation apparatus that generates a source code of a program having a graphical user interface based on a screen design document that defines a screen configuration and a processing scenario for a target screen. Based on the screen configuration specified in the screen design document, template selection means for selecting a template to be used for the source code of the program of the target screen, and based on the processing scenario specified in the screen design document, screen transition Using the scenario definition creating means for creating a scenario definition, the template and the scenario definition, a first automatically generated source code that realizes the screen configuration of the target screen and the operation for the input to the target screen is generated. Whether there is a generation processing means and unique processing that should be created individually A unique process presence / absence judging means for judging, and if there is the unique process, a template for generating a second automatically generated source code that is a template of the source code indicating the unique process in a form independent of the first source code Source code generation means.

  ADVANTAGE OF THE INVENTION According to this invention, in the automatic production | generation of a GUI program, the technique which improves readability and reduces the range affected by correction can be provided.

It is a figure for demonstrating the influence of the change of the screen design document in program development. It is a conceptual diagram which shows a mode that a GUI program automatic generation apparatus produces | generates an automatically generated source code. It is a figure which shows the example of a description of the table contained in the screen item design document 21. It is a figure which shows the example of a description of the table contained in the screen item design document 21 when there exists an original process. 2 is a block diagram showing a schematic configuration of a GUI program automatic generation device 10. FIG. It is a flowchart which shows the flow of operation | movement when the GUI program automatic generation apparatus 10 produces | generates the source code of a GUI program automatically. 5 is a diagram illustrating a description example of an input condition design document 40. FIG. 4 is a flowchart showing a flow of GUI program development using the GUI program automatic generation device 10.

  A GUI program automatic generation apparatus according to an embodiment of the present invention will be described with reference to the drawings.

  FIG. 2 is a conceptual diagram showing how the GUI program automatic generation device generates automatically generated source code. The GUI program automatic generation apparatus 10 analyzes each design document 20, 30, 40, 60, 70 for each of a plurality of target screens included in the GUI program, and automatically generates them using the source code template file 50. Source code 60 is generated. At that time, the GUI program automatic generation device 10 uses a common definition design document 70 common to a plurality of target screens.

  In developing a GUI program, a programmer firstly has a screen design document 20 in a format that can be analyzed by the GUI program automatic generation device 10, an interface design document 30 that defines a communication interface used for communication with another server, and a GUI program. The input condition design document 40 that defines the operation confirmation contents for each item is created. In addition, the programmer also creates a common definition design document 70 that prescribes the GUI program name, the GUI part name, and the association between the GUI part and the source code template file 50 in advance. Fix it.

  The screen design document 20 includes a screen item design document 21 and a scenario definition design document 22.

  In the screen item design document 21, information on the screen configuration of the target screen, for example, the definition and type of the GUI component displayed on the screen of the GUI program, and information input to the defined GUI component are defined.

  FIG. 3 is a diagram illustrating a description example of a table included in the screen item design document 21. Referring to FIG. 3, in the table 300, item names 301, control types 302, tab orders 303, content information 304, and arrangement information 305 of each GUI component are described in association with each other. A control type 302 indicates a type related to control of the GUI component of each item name 301. EDIT means an item that can be input or edited, PANEL means a fixed display item, and BTN means a button. A tab order 303 indicates the order in which the focus is moved by the Tab key. The display value of the content information indicates text to be displayed on the GUI component. The arrangement information 305 indicates the coordinates and size for displaying the GUI component.

  FIG. 4 is a diagram illustrating a description example of a table included in the screen item design document 21 when there is a unique process. Referring to FIG. 4, in table 500, action 501, control type 502, item name 503, and unique process name 504 are described in association with each other for each unique process. An action 501 indicates an operation for calling a unique process. An item name 503 indicates an item for calling an independent process, and a control type 502 indicates a type related to control of the item. The unique process name 504 is a name of the unique process. When it is not necessary to implement the unique process in the GUI program to be created, it is not necessary to describe the table 500 for calling the unique process in the screen item design document 21.

  On the other hand, the scenario definition design document 22 includes a plurality of scenarios such as a GUI screen that is a transition destination by an operation on the GUI screen, for example, a process scenario executed by an operation on the GUI screen created by the screen item design document 21 of each target screen. Related operations between GUI screens are defined.

  The source code template file 50 is a template file used for generating the automatically generated source code 60.

  The interface design document 30 defines a communication interface used by a computer in which a GUI program is installed for communication with other servers.

  The input condition design document 40 defines input conditions for making the input items in the screen item design document 21 normal. For example, in the case of “month”, a normal input value range from “1” month to “12” month is defined. This input condition design document 40 becomes the operation confirmation content for each item of the GUI program.

  The automatic generation source code 60 generated by the GUI program automatic generation apparatus 10 includes a GUI layout source code 61, an inter-screen scenario definition source code 62, a communication interface definition 63, a unit test source code 64, an event operation definition source code 65, Six types of original processing template source code 66 are included.

  The GUI layout source code 61 is source code for constructing the screen layout of the GUI program.

  The inter-screen scenario definition source code 62 is source code for constructing processing such as related operations between screens of the GUI program created by the GUI program automatic generation device 10.

  The communication interface definition 63 is a definition of the structure of a communication interface for performing data transmission / reception through communication with other servers, for example.

  The unit test source code 64 is source code for performing a test based on the input conditions described in the input condition design document 40. Conventionally, for GUI programs created from automatically generated source code, the operation check of the GUI part has to be performed manually, and even if there are many similar items, the same or similar operation check is performed on an item basis. However, in this embodiment, since the unit test can be automated, the test work is reduced.

  The event operation definition source code 65 is source code for constructing an operation when an event occurs in a GUI component defined by the GUI layout source code 61.

  The original process template source code 66 is a source code template generated when an independent process to be created individually is required in the GUI program, and the source code of the original process is additionally described therein.

  As described above, all six types of source code have different contents. The source code template file 50 includes various forms of source code template files for each of these source codes.

  The GUI program automatic generation device 10 acquires common definition information used in the GUI program from the common definition design document 70, combines the template file from the definition information described in the screen design document 20 using the information, and automatically generates source code 60 is generated.

  FIG. 5 is a block diagram illustrating a schematic configuration of the GUI program automatic generation device 10. Referring to FIG. 5, a template selection unit 15, a source code generation unit 16, a unique process presence / absence determination unit 17, a template source code generation unit 18, and a design document check unit 19 are included. Furthermore, the source code generation unit 16 includes an inter-screen scenario definition creation unit 161, a test code generation unit 162, a generation processing unit 163, and a communication interface identification unit 164.

  The template selection unit 15 selects a template to be used for the source code of the target screen program based on the screen configuration defined in the screen design document 20.

  The inter-screen scenario definition creation unit 161 creates a screen transition scenario definition based on the processing scenario defined in the screen design document 20.

  The generation processing unit 163 uses the template selected by the template selection unit 15 and the scenario definition created by the inter-screen scenario definition creation unit 161 to realize the screen configuration of the target screen and the operation for the input to the target screen. Various source codes (first automatically generated source code) to be generated are generated. The first automatically generated source code includes a GUI layout source code 61 and an inter-screen scenario definition source code 62.

  The unique process presence / absence determining unit 17 determines whether or not there is a unique process to be individually created in the GUI program of the target screen.

  If there is a unique process in the determination by the unique process presence / absence determining unit 17, the template source code generation unit 18 generates a template of the source code (second automatically generated source code) indicating the unique process independently from the first source code. Generated in the form.

  According to the present embodiment, the template part of the source code of the original process created separately from the automatic generation from the template and the part in the source code automatically generated from the template are generated independently of each other. The readability of the source code is improved, and the range affected by the modification can be limited to the automatically generated part or the original processing part.

  The communication interface specifying unit 164 specifies a communication interface used for communication with an external device such as another server.

  The generation processing unit 163 further uses the information of the communication interface specified by the communication interface specifying unit 164 to generate a communication interface definition that realizes the communication interface. The communication interface definition is also included in the first automatically generated source code.

  According to this, it is possible to automatically generate a GUI program having a desired communication interface.

  The test code generation unit 162 creates a test code that defines an input for testing a part included in the target screen.

  In this case, the generation processing unit 163 further generates unit test source code that gives unit test input to the source code of the target screen based on the test code for each of the components included in the target screen.

  According to this, it is possible to generate a unit test source program for unit testing the source code of the program of the target screen.

  The unit test source code is a source code of a program that gives an input for unit test to the first automatically generated source code created from the template. According to this, since the template is fixed in form, the first automatically generated source code that is relatively easy to define the input of the unit test is generated in an independent form. A test source program can also be generated.

  FIG. 6 is a flowchart showing an operation flow when the GUI program automatic generation device 10 automatically generates the source code of the GUI program. In FIG. 6, thin line arrows indicate the flow of processing, broken line arrows indicate file input, and thick line arrows indicate file output. The common definition design document 70, the screen design document 20, the source code template file 50, the input condition design document 40, and the interface 30 used for generating the source code of the GUI program are stored in the external storage device 80. In addition, the GUI layout source code 61, the inter-screen scenario definition source code 62, the communication interface definition 63, the unit test source code 64, the event operation definition source code 65, and the unique processing template automatically generated by the GUI program automatic generation apparatus 10 The source code 66 is stored in the external storage device 80.

  The GUI program automatic generation device 10 includes a memory 11 as a temporary storage area and a CPU 12 as a central processing unit. It operates on a computer device having a basic configuration in which timely information is stored in the memory 11 and the CPU 12 performs calculations with the information.

  When the automatic generation of the GUI program is started, the GUI program automatic generation apparatus 10 first stores the common definition design document 70 in the memory 11 (step 200). This is because the association information for associating the source code template file 50 with the GUI component and the information of the GUI program on another screen are acquired.

  When the acquisition of these pieces of information is completed, the GUI program automatic generation apparatus 10 then obtains the screen design document 20 of the target screen for automatic generation, the source code template file 50, and the input condition design document 40 as information for screen design. Obtained from the external storage device 80 and stored in the memory 11 (step 205).

  Next, the GUI program automatic generation device 10 checks each design document by the CPU 12 based on the information stored in the memory 11 so far (step 210). The check contents of the design document include, for example, whether the GUI part name described in the screen item design document 21 exists in the common definition design document 70, or there is an item that is not filled in. The design document can be checked using existing methods.

  When the design document check is completed, the GUI program automatic generation device 10 next acquires the common information acquired from the common definition design document 70 in step 200 based on the GUI part information described in the screen item design document 21. From the definition information, link information between the source code template file 50 and the GUI part information is referred to, and the corresponding source code of the source code template file 50 corresponding to the GUI part information described in the screen item design document 21 is acquired. , A GUI program is set (step 215). In step 215, the GUI layout source code 61 and the event action definition source code 65 of the GUI part are ready.

  Step 215 is repeatedly performed for all GUI parts described in the screen design document 20, and the GUI layout source code 61 and event action definition source code 65 of each GUI part are added to the GUI program (step 220).

  Next, the GUI program automatic generation device 10 acquires a processing scenario of an operation related to another GUI program from the scenario definition design document 22 for the GUI program created in step 220, and defines an operation definition of transition between screens. Build (step 230). In this step 230, the inter-screen scenario definition source code 62 is prepared.

  Since the basic operation part of the GUI program is completed at this stage, the GUI program automatic generation apparatus 10 uses the input condition design document 40 to perform each test for each GUI component constituting the GUI program. The test code is generated (step 235).

  A test code creation method for each GUI component will be described.

  As described above, a description example of the screen item design document 21 is shown in FIG. Referring to FIG. 3, the screen item design document 21 stores an item name 301, a control type 302, a tab order 303, content information 304, and arrangement information 305 as information on GUI parts constituting the GUI program. ing. The item name 301 is the name of a GUI component used in the GUI program to be designed. The control type 302 represents the type of GUI component. Here, the above is exemplified as the contents described in the screen item design document 21, but other information may be additionally defined.

  FIG. 7 is a diagram illustrating a description example of the input condition design document 40.

  The input condition design document 40 defines the input conditions for each GUI component that allows input such as text input and button operation. This is the design document for generating unit test code.

  In the table 400 of the input condition design document 40, a control type 401, an item name 402, and an input condition value 403 are described for each GUI component. The control type 401 represents the type of GUI component that performs the unit test. An item name 402 represents an item for which a unit test is performed. The input condition value 403 describes a basic value that falls into the item, a minimum value and a maximum value that can be input, and a value in a range that cannot be input. In addition, although what was shown in FIG. 7 was illustrated here, other information may be described additionally. In addition to the normal input conditions, the input conditions may be defined for the minimum input value and the maximum input value as much as the test is performed.

  Next, a test code creation method for each GUI component will be described with reference to FIGS. 3 and 4 of the present embodiment. The GUI program automatic generation device 10 extracts the control type 302 and the item name 301 from the screen item design document 21, searches the input condition design document for the control type 401 that matches the control type 302, and matches the search. From the results, an item having the same item name 301 and item name 402 is searched. If there is a matching line, the input condition is extracted from the input condition value 403, and the input test code for the GUI component is automatically generated. When designing another GUI program, if the same input items as the existing GUI program exist, create a screen item design document with the same definition as the control type 401 and the item name 402 defined in the created input condition design document 40 By doing so, the input condition design document 40 can be shared and used. The unit test source code 64 may generate a source code capable of operating alone, or may generate a source code using a general unit test program.

  After the test code generation for each component is completed in step 235, the interface for the other communication network used by the GUI program to be automatically generated is determined (step 240), and the target interface design document 30 is read into the memory 11 ( Step 245). Using the information prepared so far, the GUI layout source code 61, the inter-screen scenario definition source code 62, the communication interface definition 63, the unit test source code 64, and the event operation definition source code 65 are used in step 250. Is generated.

  It is checked whether or not the definition of the unique process as shown in FIG. 7 exists in the screen item design document 21 (step 255), and if it exists, as the template source code for describing the unique process, the unique process model source A code 66 is generated (step 260). A description example of the unique process in this embodiment will be described with reference to FIG.

  In the table 500 of FIG. 4 described above, an item name 503 indicates an item for calling an independent process, and a control type 502 indicates a type related to control of the item. The unique process name 504 is a name of the unique process. This defines the association information that associates the calling method (item name 503, control type 502, and action 501) with the callee function name (unique process name 504) for the unique process in the screen item design document 21. It is what.

  The action 501 defines what kind of operation is performed on the GUI component when the call destination function is called. The control type 502 and the item name 503 define which GUI component is unique processing. The unique process name 504 defines the function name of the call destination function.

  In the present embodiment, an example in which the definition of the part of the unique process is described in the screen item design document 21 is exemplified, but it may be created as an independent design document.

  Also, the control type 502 and the item name 503 in FIG. 4 are defined so as to be associated with the control type 302 and the item name 301 in FIG. 3, and the action defined in the action 501 is performed for the GUI component indicated by the control type 502 and the item name 503. The definition is set so that the function of the unique process having the unique process name 504 is called when the function is called.

  Further, in FIGS. 3, 4, and 7, each information is defined in a table format as an example, but the information may be defined in XML, CSV, or other formats.

  As described above, in this embodiment, when the GUI program is manufactured, the unique processing part is generated with the source code independent of the basic part of the GUI program, so that the readability of the source code can be improved. . Even if only the original part needs to be refurbished, the source code is independent, so it is only necessary to reconstruct the program for the original part.

  FIG. 8 is a flowchart showing the flow of GUI program development using the GUI program automatic generation apparatus 10.

  First, when developing a GUI program, the screen design document 20 is created as basic information to be generated by the GUI program automatic generation apparatus 10 (step 600). Next, the necessity of the unit test and necessary test contents are determined for the GUI part of the GUI program to be created, and the input condition design document 40 is created based on the determination (step 610). When the GUI program to be created uses a new communication interface for other servers, an interface design document 30 that defines the communication interface is created (step 620). If an existing communication interface is used, the interface design document 30 does not need to be created.

  Next, it is determined whether or not the common definition in the common definition design document 70 needs to be corrected, for example, when the common definition design document 70 already exists but there is correction such as adding a new GUI component (step 630). The common definition design document 70 is modified as necessary (step 640).

  As described above, after the creation of these design documents is completed, the design document is checked by the GUI program automatic generation apparatus 10 (step 210). If any deficiency exists in the design document, the design document is corrected (step 650), and the design document check is performed again until the deficiency disappears. When there is no deficiency in the design document, each source code is automatically generated by the GUI program automatic generation device 10 (step 250). If unique processing exists at this time, the GUI program automatic generation device 10 also generates a unique processing template source code 66. In the unique process template source code 66 generated at this time, only the function name defined by the unique process name 504 is defined. Therefore, if the unique process needs to be implemented, the unique process is implemented (step 660). In that case, confirmation of the part of the unique process implemented in step 660 is performed (step 670).

  Further, a unit test of the GUI program for the target screen using the unit test source code 64 is performed (step 680).

  Although not shown in the figure, if the expected operation does not occur in step 680, the process returns to step 650 and the subsequent operations are performed again. In the automatically generated source code 60 generated by the GUI program automatic generation apparatus 10 of the present embodiment, the part of the unique process and the part generated using the template are independent from each other. If not, step 660 and step 670 can be omitted.

  If the expected operation does not occur in step 670, it is only necessary to return to step 660 and perform the subsequent work again. When correction or design change occurs in the original processing part, in this embodiment, it is only necessary to correct the source code part in which the processing is implemented in the original processing template source code 66, and it is automatically generated from the template. It does not affect other source code that has been generated.

  The above-described embodiments of the present invention are examples for explaining the present invention, and are not intended to limit the scope of the present invention only to those embodiments. Those skilled in the art can implement the present invention in various other modes without departing from the spirit of the present invention.

DESCRIPTION OF SYMBOLS 10 ... GUI program automatic generation apparatus, 11 ... Memory, 12 ... CPU, 15 ... Template selection part, 16 ... Source code generation part, 161 ... Inter-screen scenario definition creation part, 162 ... Test code generation part, 163 ... Generation process part DESCRIPTION OF SYMBOLS 164 ... Communication interface specific | specification part, 17 ... Original processing presence determination part, 18 ... Template source code generation part, 19 ... Design document check part, 20 ... Screen design document, 21 ... Screen item design document, 22 ... Scenario definition design document 30 ... Interface design document, 300 ... Table, 301 ... Item name, 302 ... Control type, 303 ... Tab order, 304 ... Content information, 305 ... Arrangement information, 40 ... Input condition design document, 400 ... Table, 401 ... Control Type 402 ... Item name 403 ... Input condition value 50 ... Source code template file , 500 ... Table, 501 ... Action, 502 ... Control type, 503 ... Item name, 504 ... Unique process name, 60 ... Automatically generated source code, 61 ... GUI layout source code, 62 ... Inter-screen scenario definition source code, 63 ... Communication interface definition, 64 ... Source code for unit test, 65 ... Event action definition source code, 66 ... Original processing template source code, 70 ... Common definition design document, 80 ... External storage device

Claims (8)

A program generation device that generates a source code of a program having a graphic user interface based on a screen design document that defines a screen configuration and a processing scenario for a target screen,
Template selection means for selecting a template to be used for the source code of the program of the target screen based on the screen configuration defined in the screen design document;
Scenario definition creating means for creating a screen transition scenario definition based on the processing scenario defined in the screen design document;
Generation processing means for generating a first automatically generated source code that realizes a screen configuration of the target screen and an operation for an input to the target screen using the template and the scenario definition;
A unique process presence / absence judging means for judging whether or not there is a unique process to be created individually;
If there is the unique process, a model source code generation unit that generates a second automatically generated source code that is a model of the source code indicating the unique process in a form independent of the first source code;
A program generation device having: A communication interface specifying means for specifying a communication interface used for communication with an external device;
The generation processing means further uses the information of the communication interface specified by the communication interface specifying means to generate a communication interface definition that realizes the communication interface included in the first automatically generated source code.
The program generation device according to claim 1. A test code generating means for creating a test code that defines an input for testing a component included in the target screen;
2. The program according to claim 1, wherein the generation processing unit further generates unit test source code that gives an input for unit test to the source code of the target screen based on the test code for each of the components. 3. Generator.   4. The program generation apparatus according to claim 3, wherein the unit test source code is a source code of a program that gives an input for unit test to the first automatically generated source code. A program generation method for generating a source code of a program having a graphic user interface based on a screen design document that defines a screen configuration and a processing scenario for a target screen,
Based on the screen configuration specified in the screen design document, select a template to be used for the source code of the program of the target screen,
Create a screen transition scenario definition based on the processing scenario specified in the screen design document,
Using the template and the scenario definition, generate a first automatically generated source code that realizes a screen configuration of the target screen and an operation for input to the target screen,
Determine whether there is a unique process to be created individually,
If there is the unique process, a second automatically generated source code that is a template of the source code indicating the unique process is generated.
A program generation method comprising: Identify the communication interface used for communication with external devices,
Generating the first automatically generated source code provided with the communication interface using the information of the identified communication interface;
The program generation method according to claim 5. Furthermore, create a test code that defines input for testing the parts included in the target screen,
Based on the test code for each of the components, generate unit test source code that gives unit test input to the source code of the target screen.
The program generation method according to claim 5. The program generation method according to claim 7, wherein the unit test source code is a source code of a program that gives an input for unit test to the first automatically generated source code.

Images