JP2012181636A - Screen development support device, screen development support method and screen development support program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve efficiency in developing a screen of a web page and the like.SOLUTION: A repetitive screen generation device 100 extracts predetermined display tag information from display tag information on an HTML tag and the like included in a display code 107, and divides the extracted display tag information into source tag information on a JSP custom tag and the like previously associated with the display tag information and input data for the source tag information, with the same data identifier provided to the source tag information and the input data. The repetitive screen generation device 100 replaces the extracted display tag information in the display code 107 with the source tag information so as to set the source tag information as a source code 101 and the divided input data as test data 102.

Description

  The present invention relates to a technology that supports development of a screen such as a web page.

In the development of a screen such as a web page, it is common that the screen design is performed by a designer and the logic development is performed by a developer. In this case, it is necessary for the developer to manually convert the screen design created by the designer into source code, which places a burden on the developer.
Therefore, a technique for generating a dynamic screen from a source code and a technique for generating a source code from a dynamic screen are used (see Patent Documents 1, 2, and 3). In addition, a test system is used in which a dynamic screen is automatically generated from source code and test data, thereby confirming the operation of the source code created by the developer in a short time (see Patent Document 4).

JP 2003-150377 A JP 2004-246401 A JP 2003-316575 A JP 2006-099349 A

The techniques described in Patent Literatures 1, 2, and 3 cannot generate test data necessary for generating a dynamic screen from a dynamic screen. Further, with the technique described in Patent Document 4, source code and test data cannot be generated from a dynamic screen.
An object of the present invention is to generate source code and test data from a dynamic screen and improve the development efficiency of the dynamic screen.

The screen development support apparatus according to the present invention is:
A display code input unit for inputting a display code including a plurality of display tag information for generating display information to be displayed on the screen;
A tag extraction unit for extracting predetermined display tag information from a plurality of display tag information included in the display code input by the display code input unit;
The display tag information extracted by the tag extraction unit is source tag information previously associated with the display tag information and converted into display tag information using input data, and the source tag information. A tag separation unit that separates the input data from the input tag, and a tag separation unit that separates the source tag information and the input data with the same data identifier attached thereto,
A source code output unit for outputting a source code obtained by replacing the display tag information extracted by the tag extraction unit in the display code with the source tag information separated by the tag separation unit;
And a test data output unit that outputs the input data separated by the tag separation unit as test data.

  In the screen development support apparatus according to the present invention, by separating predetermined display tag information included in a display code (screen such as a web page) into source tag information and input data, the source code and test data are displayed from the display code. And generate Thereby, the development efficiency of a dynamic screen can be improved.

1 is a system configuration diagram of an iterative screen generation device 100 according to Embodiment 1. FIG. FIG. 3 shows an example of source code 101 according to the first embodiment. FIG. 4 shows an example of test data 102 according to the first embodiment. 5 is a flowchart showing a processing flow of a code / test data synthesis unit 105 according to the first embodiment. FIG. 3 shows an example of a display code 107 according to the first embodiment. 5 is a flowchart showing a processing flow of a code / test data separation unit 109 according to the first embodiment. The figure which shows an example of the hardware constitutions of the repetition type screen production | generation apparatus 100. FIG.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
In the following description, the processing device is a CPU 911 or the like which will be described later. The storage device is a ROM 913, a RAM 914, a magnetic disk device 920, etc., which will be described later. That is, both the processing device and the storage device are hardware.

Embodiment 1 FIG.
FIG. 1 is a system configuration diagram of an iterative screen generation device 100 (screen development support device) according to the first embodiment.
The iterative screen generation apparatus 100 receives the source code 101 and the test data 102 and outputs the display code 107, and also receives the display code 107 and outputs the source code 101 and the test data 102.
The source code 101 is program code for generating the display code 107. Here, as an example, it is assumed that the source code 101 is a program code described using JSP (Java Server Pages, registered trademark). The test data 102 is test data in which parameters used for generating the display code 107 are stored. The display code 107 is a program code that generates display information to be displayed on the screen. Here, as an example, it is assumed that the display code 107 is a program code described using HTML (HyperText Markup Language).

  The iterative screen generation apparatus 100 includes a source code input unit 103, a test data input unit 104, a code / test data synthesis unit 105 (tag conversion unit), a display code output unit 106, a display code input unit 108, and code / test data separation. Unit 109 (tag extraction unit, tag separation unit), source code output unit 110, and test data output unit 111.

  The source code input unit 103 reads the source code 101 from the storage device by the processing device and inputs it to the code / test data synthesis unit 105. The test data input unit 104 reads the test data 102 from the storage device and inputs it to the code / test data synthesis unit 105. The code / test data synthesizing unit 105 synthesizes the source code 101 and the test data 102 by a processing device, and generates a display code 107. The display code output unit 106 outputs the display code 107 generated by the code / test data synthesis unit 105 by the processing device and stores it in the storage device.

  The display code input unit 108 reads the display code 107 from the storage device by the processing device, and inputs it to the code / test data separation unit 109. The code / test data separating unit 109 separates the display code 107 into the source code 101 and the test data 102. The source code output unit 110 outputs the source code 101 separated by the code / test data separation unit 109. The test data output unit 111 outputs the test data 102 separated by the code / test data separation unit 109 by the processing device and stores it in the storage device.

FIG. 2 is a diagram illustrating an example of the source code 101 according to the first embodiment.
The source code 101 includes JSP custom tags (source tag information, JSP custom tags 201 and 202 in FIG. 2) that are dynamically converted into HTML tags (display tag information) using input data. Each JSP custom tag is given an ID attribute (data identifier) indicated as “id =...”. For example, the JSP custom tag 201 is assigned ID001 as an ID attribute, and the JSP custom tag 202 is assigned ID002 as an ID attribute.
Note that a JSP custom tag is a JSP tag defined by a developer, and defines what kind of HTML tag is converted for each JSP custom tag. Here, the JSP custom tag 201 is a jsp: Label tag of type. The jsp: Label tag becomes text data when converted to HTML. The JSP custom tag 202 is a jsp: TextBox tag of type. The jsp: TextBox tag becomes a text box when converted to HTML.

FIG. 3 is a diagram illustrating an example of the test data 102 according to the first embodiment.
In the test data 102, corresponding test data is described for each JSP custom tag included in the source code 101. In FIG. 3, the test data 102 is described in a text file format in which the ID attribute is taken on the left side, the test data corresponding to the right side is taken, and the left side and the right side are separated by the symbol “=”.
FIG. 3 shows test data 102 corresponding to the source code 101 shown in FIG. 2. Data 301 corresponding to the JSP custom tag 201 of the source code 101 and data 302 corresponding to the JSP custom tag 202 are shown. is described. In the data 301, the left side value is ID001, and the right side value is a label value. In the data 302, the left side value is ID002, and the right side value is a text box value.

FIG. 4 is a flowchart showing a process flow of the code / test data synthesis unit 105 according to the first embodiment.
(S11: Tag reading process)
The code / test data synthesis unit 105 sequentially reads each tag of the source code 101 input by the source code input unit 103.
(S12: Type determination process)
The code / test data synthesis unit 105 determines the type of the tag read in S11. Specifically, the code / test data synthesis unit 105 determines whether or not the read tag is a JSP custom tag, and determines the type of the JSP custom tag when the read tag is a JSP custom tag. .
If the read tag is a JSP custom tag (the tag to be converted in S12), the code / test data synthesis unit 105 advances the process to S13. On the other hand, if the read tag is not a JSP custom tag (a tag that is not a conversion target in S12), the code / test data synthesis unit 105 advances the process to S16.
(S13: Tag conversion process)
The code / test data synthesis unit 105 converts the JSP custom tag read in S11 into a corresponding HTML tag. For example, a jsp: Label tag is converted to a span tag, and a jsp: TextBox tag is converted to an input tag. The code / test data composition unit 105 attaches a tag identifier indicating a JSP custom tag of the conversion source and an ID attribute attached to the JSP custom tag of the conversion source to the converted HTML tag. Here, a tag identifier indicated as “type =...” And an ID attribute indicated as “id =...” Are attached to the HTML tag (see FIG. 5).
(S14: Test data acquisition process)
The code / test data composition unit 105 acquires data corresponding to the ID attribute assigned to the JSP custom tag read in S11 from the test data 102 input by the test data input unit 104. For example, in the case of a jsp: Label tag, since the ID attribute is ID001, the corresponding data is “label value”. In the case of the jsp: TextBox tag, the ID attribute is ID002, so the corresponding test data is “text box value”.
(S15: Test data setting process)
The code / test data synthesis unit 105 synthesizes the HTML tag converted in S13 and the data acquired in S14. It is assumed that how to synthesize the HTML tag and test data is preset for each JSP custom tag. For example, in the case of a jsp: Label tag, test data is set in the Inner Text of the span tag. If it is a jsp: TextBox tag, test data is set in InnerText of the input tag. InnerText is data between a start tag and an end tag.
(S16: Code addition process)
The code / test data synthesis unit 105 adds the HTML tag converted from S13 to S15 and synthesized test data to the display code 107 for the tag determined to be a JSP custom tag in S12. On the other hand, the code / test data synthesizing unit 105 adds the tag determined not to be a JSP custom tag in S12 to the display code 107 as it is or converted into HTML as usual.
(S17: End determination process)
The code / test data synthesis unit 105 determines whether all tags of the source code 101 input by the source code input unit 103 have been read.
When the code / test data composition unit 105 has read all the tags (YES in S17), the process is terminated. On the other hand, if there is a tag that has not been read (NO in S17), the code / test data synthesis unit 105 returns the process to S11 and reads the next tag.

FIG. 5 is a diagram illustrating an example of the display code 107 according to the first embodiment. 5 shows a display code 107 generated by the process shown in FIG. 4 from the source code 101 shown in FIG. 2 and the test data 102 shown in FIG.
The display code 107 is composed of a plurality of HTML tags, and some HTML tags include a tag identifier indicating a JSP custom tag corresponding as “type =...” And an ID attribute as “id =. And are given. For example, the HTML tag 501 is a span tag of an HTML tag, labeled as a tag identifier and ID001 as an id attribute. The HTML tag 502 is an input tag of an HTML tag, and “text” is assigned as a tag identifier, and “ID002” is assigned to an ID attribute.

FIG. 6 is a flowchart showing a processing flow of the code / test data separation unit 109 according to the first embodiment.
(S21: Tag reading process)
The code / test data separation unit 109 sequentially reads the HTML tags of the display code 107 input by the display code input unit 108.
(S22: Type determination process)
The code / test data separation unit 109 determines the type of the HTML tag read in S21. Specifically, the code / test data separation unit 109 determines whether or not a tag identifier is given to the read HTML tag, and if the tag identifier is given to the read HTML tag, Determine the type of tag identifier.
If the tag identifier is assigned to the read HTML tag (the tag to be converted in S22), the code / test data separation unit 109 advances the process to S23. On the other hand, when the tag identifier is not assigned to the read HTML tag (the tag that is not the conversion target in S22), the code / test data separation unit 109 advances the process to S26.
(S23: Test data extraction process)
The code / test data separation unit 109 extracts test data from the HTML tag read in S21. The test data extraction method is set in advance for each HTML tag and each tag identifier. For example, if span type = “label” tag or input type = “text” tag, the value of InnerText is acquired as test data. At this time, the code / test data separation unit 109 also acquires the value of the ID attribute assigned to the HTML tag.
(S24: Test data addition process)
The code / test data separation unit 109 adds the test data and the ID attribute acquired in S23 to the list of test data 102 for output. For example, if the HTML tag read in S21 is the HTML tag 501 shown in FIG. 5, the ID 001 is added to the left side value, and the label value is added to the right side value (see FIG. 3). If the HTML tag read in S21 is the HTML tag 502 shown in FIG. 5, the ID 002 is added to the left side value, and the text box value is added to the right side value (see FIG. 3).
(S25: Tag conversion process)
The code / test data separation unit 109 converts the HTML tag read in S21 into a corresponding JSP custom tag according to the tag identifier. For example, if the HTML tag is span type = “label”, it is converted to a jsp: Label tag, and if it is an HTML tag of input type = “text”, it is converted to a jsp: TextBox tag. The code / test data separation unit 109 attaches the ID attribute added to the conversion source HTML tag to the converted JSP custom tag. Here, an ID attribute shown as “id =...” Is attached (see FIG. 2).
(S26: Code addition process)
The code / test data separation unit 109 adds the JSP custom tag converted in S23 to S25 to the source code 101 for the HTML tag determined to have been assigned the tag identifier in S22. On the other hand, the code / test data separation unit 109 adds the tag determined to be assigned no tag identifier in S22 to the source code 101 as it is.
(S27: End determination process)
The code / test data separation unit 109 determines whether all HTML tags of the display code 107 input by the display code input unit 108 have been read.
When the code / test data separation unit 109 has read all the HTML tags (YES in S27), the process ends. On the other hand, when there is an HTML tag that has not been read (NO in S27), the code / test data separation unit 109 returns the process to S21 and reads the next HTML tag.

  Of the processes of the code / test data separating unit 109, S21, S22, and S27 are operations of the tag extracting unit, and S23 to S26 are operations of the tag separating unit.

  As described above, the iterative screen generation apparatus 100 can generate the display code 107 from the source code 101 and the test data 102, and can generate the source code 101 and the test data 102 from the display code 107. Therefore, by using the iterative screen generation device 100, the development efficiency of web pages and the like is improved.

For example, if the developer sets the ID attribute in the JSP custom tag when the source code 101 is manufactured, and sets the ID attribute in the data when the test data 102 is manufactured, the iterative screen generation device 100. Thus, the display code 107 can be automatically generated.
Conversely, for example, when a designer designs a screen, if a tag identifier corresponding to an HTML tag and an ID attribute are set, the source code 101 and test data 102 are automatically generated by the iterative screen generation device 100. Can be generated.
The iterative screen generation apparatus 100 can bidirectionally convert the source code 101 and the test data 102 to the display code 107 and convert the display code 107 to the source code 101 and the test data 102. Therefore, the source code 101 and the test data 102 produced by the developer are converted into the display code 107, the designer makes corrections, and the designer corrects the display code 107 into the source code 101 and the test data 102. Development work such that the developer makes corrections is also possible.
Therefore, by using the iterative screen generation device 100, the development efficiency of web pages and the like is improved.

In the above description, a program code described using JSP is used as the source code 101, and a program code described using HTML is used as the display code 107. However, of course, the source code 101 and the display code 107 are not limited to these, and may be described using other languages and technologies.
In the above description, the code / test data synthesis unit 105 performs the conversion process on the JSP custom tag. However, what the code / test data synthesizing unit 105 is subject to the conversion process is not limited to this, and the conversion process may be performed on a predetermined tag. For example, the identification information (tag name, etc.) of the target tag is stored in advance in the storage device, and the code / test data combining unit 105 refers to this identification information to determine whether or not to perform the conversion process. May be determined.

FIG. 7 is a diagram illustrating an example of a hardware configuration of the iterative screen generation device 100.
As shown in FIG. 7, the iterative screen generation apparatus 100 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program. Yes. The CPU 911 is connected to the ROM 913, RAM 914, LCD 901 (Liquid Crystal Display), keyboard 902 (K / B), and magnetic disk device 920 via the bus 912, and controls these hardware devices. Instead of the magnetic disk device 920 (fixed disk device), a storage device such as an optical disk device or a memory card read / write device may be used. The magnetic disk device 920 is connected via a predetermined fixed disk interface.

  An operating system 921 (OS), a window system 922, a program group 923, and a file group 924 are stored in the magnetic disk device 920 or the ROM 913. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 includes “source code input unit 103”, “test data input unit 104”, “code / test data synthesis unit 105”, “display code output unit 106”, “display code input unit 108” in the above description. ”,“ Code / test data separation unit 109 ”,“ source code output unit 110 ”,“ test data output unit 111 ”, and the like. The program is read and executed by the CPU 911.
In the file group 924, information, data, signal values, variable values, and parameters such as “source code 101”, “test data 102”, and “display code 107” in the above description are stored in “file” and “database”. Stored as each item. The “file” and “database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for the operation of the CPU 911 such as calculation / processing / output / printing / display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the operation of the CPU 911 for extraction, search, reference, comparison, calculation, calculation, processing, output, printing, and display. Is remembered.

In the above description, the arrows in the flowchart mainly indicate input / output of data and signals, and the data and signal values are recorded in a memory of the RAM 914, other recording media such as an optical disk, and an IC chip. Data and signals are transmitted online by a bus 912, signal lines, cables, other transmission media, and radio waves.
In addition, what is described as “to part” in the above description may be “to circuit”, “to device”, “to device”, “to means”, and “to function”. It may be “step”, “˜procedure”, “˜processing”. In addition, what is described as “˜device” may be “˜circuit”, “˜device”, “˜means”, “˜function”, and “˜step”, “˜procedure”, “ ~ Process ". Furthermore, what is described as “to process” may be “to step”. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored in a recording medium such as ROM 913 as a program. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes a computer or the like to function as the “˜unit” described above. Alternatively, the computer or the like is caused to execute the procedures and methods of “to part” described above.

  DESCRIPTION OF SYMBOLS 100 Repetitive type screen generation apparatus, 101 source code, 102 test data, 103 source code input unit, 104 test data input unit, 105 code / test data synthesis unit, 106 display code output unit, 107 display code, 108 display code input unit 109 code / test data separation unit, 110 source code output unit, 111 test data output unit.

Claims (7)

A display code input unit for inputting a display code including a plurality of display tag information for generating display information to be displayed on the screen;
A tag extraction unit for extracting predetermined display tag information from a plurality of display tag information included in the display code input by the display code input unit;
The display tag information extracted by the tag extraction unit is source tag information previously associated with the display tag information and converted into display tag information using input data, and the source tag information. A tag separation unit that separates the input data from the input tag, and a tag separation unit that separates the source tag information and the input data with the same data identifier attached thereto,
A source code output unit for outputting a source code obtained by replacing the display tag information extracted by the tag extraction unit in the display code with the source tag information separated by the tag separation unit;
A screen development support apparatus comprising: a test data output unit that outputs the input data separated by the tag separation unit as test data. The display code input unit inputs a display code in which a tag identifier indicating source tag information associated with the display tag information is embedded in at least a part of the display tag information,
The tag extraction unit extracts display tag information in which the tag identifier is embedded as the predetermined display tag information,
The tag separation unit separates the display tag information extracted by the tag extraction unit into source tag information indicated by the tag identifier embedded in the display tag information and input data to the source tag information. The screen development support apparatus according to claim 1, wherein The screen development support device further includes:
A source code input unit for inputting the source code output by the source code output unit;
A test data input unit for inputting the test data output by the test data output unit;
Source tag information included in the source code input by the source code input unit is test data input by the test data input unit, and the same data identifier as the data identifier attached to the source tag information is attached. A tag conversion unit that converts the test data as input into display tag information;
The screen development support according to claim 1, further comprising: a display code output unit that outputs a display code in which source tag information of the source code is replaced with display tag information converted by the tag conversion unit. apparatus. 4. The screen development support apparatus according to claim 3, wherein the tag conversion unit converts display tag information in which a tag identifier indicating source tag information of a conversion source is embedded. Display tag information for generating display information to be displayed on the screen, including source tag information converted to display tag information using input data, and inputting source code with a data identifier attached to the included source tag information A source code input unit,
A data input unit for inputting input data with a data identifier;
Source tag information included in the source code input by the source code input unit is input data input by the data input unit, and the same data identifier as the data identifier attached to the source tag information is attached. A tag conversion unit that converts input data into display tag information in which a tag identifier indicating the source tag information is embedded;
A screen development support device, comprising: a display code output unit that outputs a display code in which source tag information of the source code is replaced with display tag information converted by the tag conversion unit. A display device for inputting a display code including a plurality of display tag information for generating display information to be displayed on the screen by the processing device;
A tag extracting step for extracting predetermined display tag information from a plurality of display tag information included in the display code input in the display code input step by the processing device;
The processing device converts the display tag information extracted in the tag extraction step into source tag information previously associated with the display tag information and converted into display tag information using input data, and A tag separation step for separating the input data into the source tag information, the tag separation step for separating the source tag information and the input data with the same data identifier attached thereto,
A source code output step for outputting a source code in which the processing device replaces the display tag information extracted in the tag extraction step in the display code with the source tag information separated in the tag separation step;
A screen development support method, characterized in that the processing device includes a test data output step of outputting the input data separated in the tag separation step as test data. A display code input process for inputting a display code including a plurality of display tag information for generating display information to be displayed on the screen;
Tag extraction processing for extracting predetermined display tag information from a plurality of display tag information included in the display code input in the display code input processing;
The display tag information extracted in the tag extraction process is source tag information associated with the display tag information in advance and converted into display tag information using input data, and the source tag information. Tag separation processing for separating the input data into the input data, the tag separation processing for separating the source tag information and the input data with the same data identifier attached thereto,
A source code output process for outputting a source code obtained by replacing the display tag information extracted by the tag extraction process in the display code with the source tag information separated by the tag separation process;
A screen development support program for causing a computer to execute test data output processing for outputting input data separated by the tag separation processing as test data.

Images