JP2006163855A - Web application development support device, and development support method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a Web application development support device for distributed development of an image design and business logic without requiring a developer, etc., to consider a framework in developing a Web application using the framework. <P>SOLUTION: A ValueObject defining part 101 is a class for holding an input/output item between a presentation layer and a business logic layer constituting a part of the Web application. Definition information of the ValueObject class is stored in an image specification information storage part 103. An image specification defining part 102 hierarchically manages the transition of the display screen and business logic in the Web application. The image specification information storage part 103 stores the definition information of the specification of each display screen and business logic. A presentation layer source code automatic generation part 104 generates a presentation layer source code 110, based on the definition information stored in the picture specification information storage part 103. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a Web application development support apparatus and development support method, and more particularly to an apparatus and method for supporting the development of a Web application using a framework such as Struts.

In recent years, in web application development that constitutes large-scale systems, for the purpose of improving efficiency by distributed development of screen design and business logic, a business processing part (model) and a layout part for displaying on a browser An MVC (model-view-controller) model may be employed that divides (view) into a control part (controller) that controls a business part and a layout part.
In such an MVC model, screen transition and business logic are described for each page, so in order to check the contents of the business logic and the screen transition status, refer to the source code for each page, It was necessary to distinguish the business logic part and the page transition part. In particular, in the case of large-scale system development, it has been difficult to grasp the overall picture of screen transitions described on each page.
In such distributed development, recently, a framework suitable for the MVC model is used in order to further improve the efficiency of development and to make it easy to grasp business logic, screen transition, and the like. As such a framework, for example, Struts based on J2EE (Java2 Enterprise Edition, “JAVA” is a registered trademark of Sun Microsystems, Inc.) is often used. Here, the Web application using Struts has a presentation layer including a setting file, a controller (ActionServlet), and a form Bean class. In the configuration file, all screen transitions, business logic associations, input parameters, etc. are described in advance. One controller accepts all requests from the client, and based on the information described in the configuration file Event execution and distribution to appropriate pages. Further, input / output information of each page is exchanged with the controller using a form bean.
As described above, when a framework such as Struts is used, it is possible to check the overall image of the hierarchical structure of screen transitions, and to easily and easily display a display screen and business logic that are distributed and developed. It is possible to link appropriately.

On the other hand, as a development support apparatus for improving the efficiency of Web application development, a device having means for generating Servlet, Jsp, and Bean source codes constituting a Web application is conventionally known ( For example, see Patent Document 1.)
JP 2001-344105 A

  In the Web application development support apparatus described in Patent Document 1, for each of Servlet, Jsp, and Bean, a correspondence definition table is generated based on detailed design information created in advance by a developer or the like, and each design information, It is possible to generate each source code of Servlet, Jsp, and Bean using the correspondence definition table and each template.

However, when a framework is used in distributed development of a Web application, each developer is required to have knowledge of the framework, and the process of implementing the setting file, controller, form bean, and the like described above is included. Because it is necessary, the development work cannot always be performed efficiently.
In addition, since the development support apparatus described in Patent Document 1 is not intended to use a framework, it is possible to grasp the entire image of the generated Web application, such as the hierarchical structure of each screen transition. It was difficult.
In the development support apparatus described in Patent Document 1, detailed design information corresponding to the specifications of the development support apparatus must be created in advance for each of Servlet, Jsp, and Bean in order to generate source code. Therefore, it is necessary to determine specific specifications for screen design, business logic, etc., and it may take time to create design information. It was not a thing.

  The present invention is to solve the above-mentioned problems, and as a Web application development support device using a framework, it generates details only by generating a linkage portion between a display screen and business logic based on simple definition information. The purpose is to provide a Web application development support device that eliminates the need for creating design information and makes it possible to concentrate on screen design and business logic implementation without making each developer aware of the framework. To do.

In order to solve the above-mentioned problems, the present invention has a setting file that describes the transition of the display screen and the association between the display screen and the business logic. Value object definition information that defines a class that holds an input / output item between a presentation layer and a business logic layer, the development support apparatus for a Web application having a presentation layer that performs transition and a business logic layer, and the display Screen specification information storage for storing screen transitions of screens and screen specification definition information that defines the association between each display screen and business logic, and input of input / output items on each display screen, and as the above value object definition information, Screen specification information storage Receiving the input of the ValueObject definition part stored in the screen, the screen transition definition information and event execution definition information for each display screen, and the business logic definition information corresponding to the event execution definition information, and the screen specification definition information A screen specification definition unit stored in a specification information storage unit, and a means for generating the presentation layer and a business logic model constituting the business logic layer based on the definition information stored in the screen specification information storage unit It is characterized by providing.
In addition, the screen specification definition unit includes means for acquiring screen specification definition information stored in the screen specification information storage unit and hierarchically displaying screen transitions of the display screen and business logic. .
Also, screen specifications for storing transition information of the display screen, screen specification definition information that defines the association between the display screen and the business logic, and value object definition information that defines input / output items between the presentation layer and the business logic layer. An information storage unit; a value object definition unit that stores the value object definition information in the screen specification information storage unit; a screen specification definition unit that stores screen specification definition information in the screen specification information storage unit; and the screen specification information storage A web application development support method by a web application development support apparatus comprising a source code generation unit that generates a part of a presentation layer of a web application based on each definition information stored in the unit, wherein the ValueObject definition unit includes each table Accepting input of input / output items on the screen, and storing it in the screen specification information storage unit as the ValueObject definition information, the screen specification definition unit including screen transition definition information and event definition information for each display screen, Receiving input of business logic definition information corresponding to event definition information and storing it as screen specification definition information in a screen specification information storage unit; and the source code generation unit is stored in the screen specification information storage unit A presentation layer including display screen transition information and a configuration file describing association between the display screen and business logic based on each definition information, and a controller that executes an event or performs page transition based on the description of the configuration file; Business logic that constitutes the business logic layer And a step of generating a stationery.

With the above configuration, in the present invention, for example, in web application development using a framework such as Struts, it is possible to generate a source code of a part excluding screen design and business logic. This makes it possible to concentrate on screen design or business logic implementation. Accordingly, even a developer who does not have accurate knowledge about the framework can perform appropriate distributed development.
In addition, since the screen transition of each display screen and associated business logic is hierarchically displayed based on the screen specification definition information, it is possible to grasp the screen transition etc. without checking the contents described in the setting file. It becomes possible.

Hereinafter, a Web application development support apparatus according to an embodiment of the present invention will be described with reference to the drawings. In the present embodiment, an example of a Web application development support apparatus used for developing a Web application that uses Struts as a framework will be described.
FIG. 1 is a block diagram showing a schematic configuration of a Web application development support apparatus according to the present embodiment.
The Web application development support apparatus 100 generates a source code 110 indicating a presentation layer that constitutes a part of a Web application to be developed, and includes a ValueObject definition unit 101, a screen specification definition unit 102, and screen specification information. A storage unit 103 and a presentation layer source code automatic generation unit 104 are provided.
The ValueObject definition unit 101 stores, in the screen specification information storage unit 103, definition information of a ValueObject class that is a class that holds input / output items between a presentation layer and a business logic layer that constitute a part of a Web application.
The screen specification definition unit 102 hierarchically manages the transition of the display screen and business logic of the Web application, and stores the definition information of the specifications of each display screen and business logic in the screen specification information storage unit 103.
The presentation layer source code automatic generation unit 104 generates the presentation layer source code 110 based on the definition information stored in the screen specification information storage unit 103.

FIG. 2 is a diagram illustrating an example of a schematic configuration of a Web application including a presentation layer generated by the Web application development support apparatus 100 according to the present embodiment.
The Web application 200 includes a presentation layer 210, a business logic increase 220, and a database layer 230.
The presentation layer 210 performs processing for receiving a client request and displaying the processing result, processing for calling business logic, and the like. This example shows the case where Struts is used for the Web application framework. In this case, the Struts setting file 211 in the XML format in which screen transition information is described, the client request is received, and the business logic is called. , An action class 212 as a controller that performs processing for setting a business logic result, an action form bean class 213 that holds client input data, a JSP file 214 that implements a screen design, and the like.
The business logic layer 220 includes a business logic class 221 that performs business processing, and the database layer 230 includes a database access class 231 that accesses a database and acquires or registers data.
The Web application development support apparatus 100 according to the present embodiment includes, in the Web application 200, a Struts setting file 211 that configures the presentation layer 210, an action class 212, an action form Bean class 213, and a business that configures the business logic layer 220. A template of the logic class 221 is generated as the presentation layer source code 110.

FIG. 3 is a flowchart showing an overview of presentation layer source code generation processing performed by the Web application development support apparatus 100 according to the present embodiment.
In the Web application development device 100, the ValueObject definition unit 101 displays a definition screen, stores the valueObject information arbitrarily defined by the user in the screen specification information storage unit 103 (step 301), and the screen specification definition unit 102 defines it. A screen is displayed, and screen information and business logic information arbitrarily defined by the user are stored in the screen specification information storage unit 103 (step 302).
The presentation layer source code automatic generation unit 104 acquires the screen specification information stored in the screen specification information storage unit 103, and generates the presentation layer source code 105 (step 303).

  Next, a development support processing method performed by the Web application development support apparatus 100 according to the present embodiment will be described based on an example of a definition screen displayed on a developer terminal or the like.

FIG. 4 is a diagram illustrating an example of a ValueObject definition screen displayed by the ValueObject definition unit 101.
In the ValueObject definition screen 400 shown in FIG. 4, as setting items related to the ValueObject, the ID 401 of the ValueObject, the type 402 indicating whether the ValueObject is an input item or an output item, the description 403 of the ValueObject, and the item name (property) of each Item of the ValueObject class ) 404, item type 405, and item description 406. Here, a plurality of item names 404, types 405, and explanations 406 can be defined.

FIG. 5 is a diagram illustrating an example of a screen specification definition screen displayed by the screen specification definition unit 102.
A screen specification definition screen 500 shown in FIG. 5 includes a screen transition display unit 510 that hierarchically displays display screens and business logic transitions based on information stored in the screen specification information storage unit 103, as will be described later. A setting definition unit 520 that defines settings of the elements 511 displayed on the display unit 510.
The element 511 displayed on the screen transition display unit 510 corresponds to a display screen such as JSP and a business logic called by an event such as a screen link or a button click.
In this example, an example of the setting definition unit 520 when the element 511 indicating the display screen is selected in the screen transition display unit 510 is illustrated.
In the setting definition unit 520, as setting items related to the display screen, each input field of the screen name 521, the URI 522, the output VO 523 indicating the value object holding the output item of the display screen, and the event setting unit 530 generated on the display screen, Event add / edit / delete buttons 531 to 533, an event name 534, an event type 535, an input VO 536 indicating a value object holding an event input item, a logic ID 537 for uniquely identifying the business logic, and a transition destination after the event Each of the input fields of the transition destination URI 538 indicating "."

FIG. 6 is a diagram illustrating another example of the screen specification definition screen displayed by the screen specification definition unit 102.
A screen specification definition screen 600 illustrated in FIG. 6 illustrates a setting definition unit 620 when an element 611 indicating business logic is selected in the screen transition display unit 610.
In the setting definition unit 620, as business logic setting items, a business logic name 621, a business logic ID 622, a business logic class name 623, a business logic method name 624, an input VO 625 indicating business logic arguments, and a return value of the business logic Each input field of the output VO 626 indicates the following. For the input VO 625 and the output VO 626, a scope such as “request” or “session” can be defined.

Hereinafter, a specific example of the screen specification information generation process performed using each definition screen described above will be described.
In this example, the Web application is composed of two screens: an input screen having a form for inputting a customer number, and an output screen for outputting customer information corresponding to the customer number input on the input screen. Note that this Web application uses Struts as a framework.

First, a class that holds each input / output item on the input / output screen is defined on the ValueObject definition screen.
FIG. 7 is a diagram showing a ValueObject definition screen for defining a class that holds input items on the input screen.
In the ValueObject definition screen 700, the developer defines “CustomerNo” as the ID 701, “Input” as the type 702, “ValueObject holding a customer number” as the description 703, and “no, String, Customer number "is defined.
FIG. 8 is a diagram showing a ValueObject definition screen for defining a class that holds output items on the output screen.
In the ValueObject definition screen 800, the developer defines “Customer” in the ID 801, “Output” in the type 802, “ValueObject holding customer information” in the description 803, and “no,” in the ValueObject items 804 to 807. "String, customer number", "name, String, name", "address, String, address", "tel, String, phone number" are defined.
The ValueObject definition unit 101 stores the contents defined in each of the above ValueObject definition screens 700 and 800 in the screen specification information storage unit 103.

Next, screen specifications related to the input / output screen and business logic are defined on the screen specification definition screen.
FIG. 9 is a diagram showing a screen specification definition screen for defining the screen specification of the input screen.
In the screen specification definition screen 900, the developer defines “input screen” in the screen name 901 and “/input.jsp” in the URI 902, and “output, Form, customerNo, search, / output” in the event setting unit 904. .Jsp "is defined. In the screen specification of the input screen shown in this example, the output VO 903 is blank.
FIG. 10 is a diagram showing a screen specification definition screen for defining a customer information search screen specification that is a business logic called by an event on the input screen.
In the screen specification definition screen 900, the developer sets “business information search” as the business logic name 1001, “search” as the ID 1002, “sample.CustomerLogic” as the class 1003, and “search” as the method 1004 as the input VO 1005. “CustomerNo, request” is defined in the output VO 1006 and “customer, request” is defined.
FIG. 11 is a diagram showing a screen specification definition screen for defining the screen specification of the output screen.
In the screen specification definition screen 1100, the developer defines “output screen” as the screen name 1101, “/output.jsp” as the URI 1102, and “customer” as the output VO 1103. In this example, the ValueObject item is not defined on the output screen.
The screen specification definition unit 101 stores the contents defined in each of the above screen specification definition screens 900, 1000, 1100 in the screen specification information storage unit 103, and the screen specification definition screens 900, 1000, 1100 based on the stored contents. Change the display contents of the screen transition display section.

FIG. 12 shows, as an example of the screen specification information stored in the screen specification information storage unit 103, information stored in the value object definition unit 101 based on the contents defined in the value object definition screen shown in FIGS. 11 is a diagram showing information stored in the screen specification definition unit 102 based on the contents defined in the screen specification definition screen shown in FIG.
The screen specification information 1200 is generated, for example, as an XML (Extensible Markup Language) file, and includes, as shown in FIG. 11, ValueObject information 1210, business logic information 1220, and screen information 1230.
The value object information 1210 includes definition information 1211 for the value object defined in the value object definition screen 700 shown in FIG. 7 and definition information 1212 for the value object defined in the value object definition screen 800 shown in FIG.
The business logic information 1220 includes definition information 1221 about the business logic defined in the screen specification definition screen 1000 shown in FIG. The value of the input-vo attribute or output-vo attribute in the definition information 1221 corresponds to the value of the id attribute in the definition information 1211 and 1212 of the value object information 1210.
The screen information 1230 includes definition information 1131 for the input screen defined in the screen specification definition screen 900 shown in FIG. 9 and definition information 1232 for the output screen defined in the screen specification definition screen 1100 shown in FIG. included. Note that the value of the logic attribute of the <event> tag in the definition information 1231 corresponds to the value of the id attribute of the <businessness-logic> tag in the definition information 1221 of the business logic information 1220. Also, the value of the forward attribute of the <event> tag corresponds to the value of the path attribute of the <boundary> tag in the definition information 1232.

FIG. 13 is a flowchart showing a processing procedure for displaying a screen transition based on the screen specification information stored in the screen specification information storage unit 103 by the screen specification definition unit 102.
In this process, the top screen is designated in advance by the developer. For example, in the screen specification information 1200 shown in FIG. 12, the input screen is designated as the top screen.
The screen specification definition unit 102 repeats the following processing for the screen information included in the screen specification information (step 1301).
The screen specification definition unit 102 reads the screen information, sets a node based on the definition information of the screen information (step 1302), and repeats the following processing for the event included in the screen information (step 1303).
The screen specification definition unit 102 reads the business logic information based on the business logic ID set in the event logic included in the screen information (step 1304), and adds the business logic as a child node of the current node (step 1304). 1305).
Next, the screen information set in the transition destination URI of the event in the screen information is read (step 1306), and the screen is added to the child node of the business logic (step 1307).
The above processing is repeated for the screen information and business logic information included in the screen specification information, and the result is hierarchically displayed on the screen transition display portion of the screen specification definition screen (step 1308).
For example, in the case of the screen specification information 1200 shown in FIG. 12, the screen information 1230 is read. First, the “input screen” is set as the highest node based on the definition information 1231 of the input screen as the top screen. Next, based on the business logic ID “search” of the event included in the definition information 1231 of the input screen, the definition information 1221 of the business logic information 1220 is read, “customer information search” is added to the child node, and the definition information 1231 The definition information 1232 of the output screen is read based on the path of the transition destination URI, and “output screen” is set as a child node of the business logic “customer information search”.
Based on the above processing results, each node is hierarchically displayed on the screen transition display unit. The root hierarchy can be designated as a root by selecting the displayed screen.
Therefore, the developer can easily grasp the screen transition of the Web application by displaying the screen transition display unit without confirming the description of the setting file, and the correction work or the like is facilitated.

Hereinafter, a process in which the presentation layer source code automatic generation unit 104 generates the presentation layer source code 110 based on the screen specification information stored in the screen specification information storage unit 103 will be described.
FIG. 14 is a flowchart showing a processing procedure for generating the source code of the value object class and the action form bean class based on the value object information.
The presentation layer source code automatic generation unit 104 repeats the following processing for each definition information included in the value object information (step 1401).
First, each definition information of value object information is read (step 1402), a value object class is generated (step 1403), and an attribute and a setter / getter of the attribute are generated for each <property> tag (step 1404). In the generation of the ValueObject class, the first character of the value of the id attribute of the <value-object> tag is capitalized, and then the class name is added with Value. The type name of the attribute is the value of the type attribute of the <property> tag, and the variable name of the attribute is the value of the name attribute of the <property> tag.
Next, it is determined whether or not the value of the type attribute of the <value-object> tag is “input” (step 1405).
If the value of the type attribute is “input” as a result of the determination, an action form Bean class is generated (step 1406), and the attribute and the setter of that attribute are set for each <property> tag, as in the case of the valueObject class. / Getter is generated (step 1407), and the definition of the action form Bean class is added to the Struts setting file (step 1408). In the generation of the action form Bean class, first, the ActionForm that is a Struts class is inherited as a parent class. The type name of the attribute of the action form Bean class is the value of the type attribute of the <property> tag, and the variable name of the attribute is the value of the name attribute of the <property> tag. A <form-Bean> tag is added to the Struts setting file with the value of the id attribute of the <ValueObject> tag as the value of the name attribute and the value of the class name as the value of the type attribute.
On the other hand, if the value of the type attribute is not “input” in step 1405, the next definition information is processed without generating the action form Bean class.
By repeating the above processing, a ValueObject class and an action form Bean class are generated.

FIG. 15 is a flowchart showing a processing procedure for generating a template source code of a business logic class constituting the business logic layer corresponding to the presentation layer based on the business logic information.
The presentation layer source code automatic generation unit 104 repeats the following processing for each definition information included in the business logic information (step 1501).
First, each definition information of business logic information is read (step 1502), and a business logic class having a class attribute value of a class attribute of a <businessness-logic> tag is generated (step 1503).
Next, a method of the value of the method attribute of the <business-logic> tag is generated (step 1504). In the generation of a method, when an input-vo attribute is defined in the definition information, a ValueObject corresponding to the value is used as an argument of the method. If the input-vo attribute is not defined, the argument is empty. Further, when the output-vo attribute is defined in the definition information, the ValueObject corresponding to the value is set as the return value of the method. When the output-vo attribute is not defined, it is a void type.
When there are a plurality of business logic information definition information, the above process is repeated, and generation of a template source code of the business logic class is repeated.

FIG. 16 is a flowchart showing a processing procedure for generating the action class source code based on the screen information.
The presentation layer source code automatic generation unit 104 repeats the following processing for event information included in each definition information of the screen information (step 1601).
First, each event information is read, and an action class having a class name with the first letter of the name attribute value of the <event> tag capitalized and then added with an action is generated (step 1602).
Next, the Action class that is the class of Struts is inherited as the parent class, and the execute method is overridden (step 1603). The Action class handles the processing of business logic implemented in the corresponding Bean etc. in response to the request, and the Action method of the Action class is called by the ActionServlet, and authentication, validation, etc. Process will be executed and appropriate business logic will be called.
In the generation of an action class, when the input-vo attribute of the <businesses-logic> tag corresponding to the logic attribute of the <event> tag is defined in the definition information, the execute method corresponds to the input-vo attribute. The action form bean class generated by the value object information is acquired, and a process of copying the data to the value object generated by the value object information corresponding to the input-vo attribute is generated.
If the <business-logic>tag's input-vo attribute corresponding to the <event>tag's logic attribute is defined, the action method bean class generated from the value object information corresponding to the input-vo attribute by the execute method Is generated, and a process of copying the data to the ValueObject generated by the ValueObject information corresponding to the input-vo attribute is generated. In addition, a process for calling a method indicated by the method attribute of the <business-logic> tag corresponding to the logic attribute of the <event> tag is generated using the ValueObject generated by the ValueObject information corresponding to the input-vo attribute as an argument.
If the input-vo attribute is not defined, a process for calling a method indicated by the method attribute of the <business-logic> tag corresponding to the logic attribute of the <event> tag is generated without an argument.
When the output-vo attribute of the <businessness-logic> tag corresponding to the logic attribute of the <event> tag is defined, a process for returning the processing result is generated.
The action class definition generated by the above processing is added to the Struts setting file (step 1604). Specifically, a character string with “/” at the beginning of the name attribute value of the <event> tag of the definition information is set as the value of the path attribute, the class name of the action class is set as the value of the type attribute, and the logical attribute is set. An <action> tag is added in which the value of the input attribute in the definition information of the corresponding business logic information is the value of the name attribute, and the value of the input attribute in the definition information of the business logic information is the value of the scope attribute. Further, a <forward> tag is added in which “success” is the value of the name attribute and the forward attribute value of the <event> tag is the value of the path attribute.

Specific examples of the source code generated by the presentation layer source code automatic generation unit 104 by the above processing are shown in FIGS.
FIG. 17 is a diagram illustrating an example of source code indicating an input ValueObject class generated based on the definition information 1211 included in the ValueObject information 1210.
In the input ValueObject class 1700, a class name, an attribute, and a setter / getter of the attribute are generated based on the attribute values of the <ValueObject> tag and the <Property> tag of the definition information 1211.
Specifically, “CustomerNoValue” is set as the class name, and an attribute “no” relating to the customer number and a setter / getter of the attribute are generated.
FIG. 18 is a diagram illustrating an example of the source code of the action form Bean class generated based on the definition information 1211 included in the value object information 1210.
In the action form Bean class 1800, a class name, an attribute, and a setter / getter of the attribute are generated based on the attribute values of the <ValueObject> tag and the <Property> tag of the definition information 1211 in substantially the same manner as the input ValueObject class 1700. ing.
FIG. 19 is a diagram illustrating an example of source code indicating an output ValueObject class generated based on the definition information 1212 included in the ValueObject information 1210.
In the output ValueObject class 1900, class names, attributes, and setter / getters of the attributes are generated based on the attribute values of the <ValueObject> tag and the <Property> tag of the definition information 1212 in substantially the same manner as the input ValueObject class 1700. Yes.
Specifically, “CustomerValue” is set as the class name, each attribute “no”, “name”, “address” and “tel” regarding the customer number, name, address and telephone number, and setter / getter of each attribute. Has been generated.

FIG. 20 is a diagram showing a business logic template source code generated based on the definition information 1221 included in the business logic information 1220.
In the business logic model source code 2000, a class name and each method are generated based on each attribute value of the <business-logic> tag of the definition information 1221, and a business logic description part is included.
Specifically, “sample.CustomerLogic” is set as a class name, and a “search” method is generated.

FIG. 21 is a diagram showing the source code of the action class generated based on the definition information 1231 of the screen information 1230.
In the action class source code 2100, a class name and a writing method are generated based on the definition information 1221 of the business logic information 1220 referred to based on each attribute value and logic attribute value of the <event> tag of the definition information 1231.
FIG. 22 is a diagram illustrating a source code of a Struts setting file in which definition information is added based on ValueObject information and screen information.
The source code 2200 of the Struts setting file describes action form Bean class, action class setting information, and screen transition information based on the definition information 1211 and 1311 of the value object information 1210 and the screen information 1230.

As described above, the Web application development support device according to the present embodiment generates a Struts setting file, an action class, an action form bean class that constitutes a presentation layer, and a business logic class template corresponding to each class. This allows developers to concentrate on screen design and business logic implementation.
Further, since the defined screen transitions are hierarchically displayed on the screen specification definition screen based on the screen specification information, it is easy to grasp and edit the screen transitions.

In the embodiment described above, the case where Struts is used as a framework has been described. However, the present invention is not limited to this, and a class or the like corresponding to another framework may be generated.
Moreover, each definition part and source code generation part which comprise the Web application development assistance apparatus of this invention may be comprised with a different terminal, respectively.

It is a block diagram which shows schematic structure of the web application development assistance apparatus which concerns on one embodiment of this invention. It is a figure which shows schematic structure of the web application using Struts. It is a flowchart which shows the outline | summary of the process by the web application development assistance apparatus which concerns on one embodiment of this invention. It is a figure which shows an example of a screen structure of a ValueObject definition screen. It is a figure which shows an example of a screen structure of a screen specification definition screen (screen specification definition). It is a figure which shows an example of a screen structure of a screen specification definition screen (business logic definition). It is a figure which shows an example of ValueObject definition. It is a figure which shows an example of ValueObject definition. It is a figure which shows an example of a screen specification definition. It is a figure which shows an example of a business logic definition. It is a figure which shows an example of a screen specification definition. It is a figure which shows an example of the source code which shows screen specification information. It is a flowchart which shows the screen transition display process procedure which a screen specification definition part performs. It is a flowchart which shows the source code production | generation process procedure which a presentation layer source code automatic generation part performs. It is a flowchart which shows the source code production | generation process procedure which a presentation layer source code automatic generation part performs. It is a flowchart which shows the source code production | generation process procedure which a presentation layer source code automatic generation part performs. It is a figure which shows an example of the source code of produced | generated ValueObject. It is a figure which shows an example of the source code of the produced | generated action form Bean. It is a figure which shows an example of the source code of produced | generated ValueObject. It is a figure which shows an example of the source code of the produced | generated business logic model. It is a figure which shows an example of the source code of the produced | generated action class. It is a figure which shows an example of the source code of the produced | generated Struts setting file.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 Web application development support apparatus, 101 ValueObject definition part, 102 Screen specification definition part, 103 Screen specification information storage part, 104 Presentation layer source code automatic generation part, 110 Presentation layer source code

Claims (3)

A presentation layer that has a configuration file that describes the screen transition of the display screen and the association between the display screen and the business logic, and that executes the event according to the request from the client and the page transition based on the configuration file, and the business logic layer A development support apparatus for a web application having
ValueObject definition information that defines the class that holds the input / output items between the presentation layer and the business logic layer, and screen specification definition information that defines the screen transition of the display screen and the association between each display screen and the business logic. A screen specification information storage unit for storing;
A ValueObject definition unit that accepts input of input / output items on each display screen and stores the value in the screen specification information storage unit as the ValueObject definition information;
A screen that receives input of screen transition definition information and event execution definition information for each display screen, and business logic definition information corresponding to the event execution definition information, and stores the screen specification definition information in the screen specification information storage unit A specification definition part;
A Web application development support device comprising: the presentation layer and a means for generating a business logic model constituting the business logic layer based on each definition information stored in the screen specification information storage unit . The screen specification definition part
Obtaining screen specification definition information stored in the screen specification information storage unit;
2. The Web application development support apparatus according to claim 1, further comprising means for hierarchically displaying the display screen and the screen transition of the business logic. Screen specification information storage for storing display screen transition information, screen specification definition information that defines the association between the display screen and business logic, and value object definition information that defines input / output items between the presentation layer and the business logic layer In the screen specification information storage unit, the value object definition unit that stores the value object definition information in the screen specification information storage unit, the screen specification definition unit that stores the screen specification definition information in the screen specification information storage unit, and the screen specification information storage unit A web application development support method by a web application development support apparatus comprising a source code generation unit that generates a part of a presentation layer of a web application based on each stored definition information,
A ValueObject definition unit that accepts input of input / output items on each display screen, and stores it as the ValueObject definition information in the screen specification information storage unit;
The screen specification definition unit accepts input of screen transition definition information and event definition information for each display screen and business logic definition information corresponding to the event definition information, and the screen specification definition storage unit stores the screen specification information as the screen specification definition information. The step of storing in
Based on each definition information stored in the screen specification information storage unit, the source code generation unit includes a setting file that describes display screen transition information and the association between the display screen and business logic, and a description of the setting file. A Web application development support method, comprising: a presentation layer including a controller that executes an event or transitions based on an event; and a step of generating a business logic template that constitutes the business logic layer.

Images