JP2012063841A - Automatic program generating device and automatic program generating method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automatically generate a program including a screen design.SOLUTION: From screen mock-up data separately created with a design tool, attribution information that does not contain the data regarding a screen design is extracted. Then the attribution information is replaced so that it may be operated in cooperation with a processing program. Thereby, a screen program and a processing program can be generated, without affecting a screen design.

Description

  The present invention relates to an automatic program generation device and an automatic program generation method.

  When building an information system, an automatic program generation tool that automatically generates a source program is used to efficiently develop software. Here, the automatic program generation tool includes a technology that cooperates with the GUI screen design tool. Thereby, it is possible to enjoy the benefits of the above-described automatic program generation tool while ensuring the degree of freedom and creativity of GUI screen design (hereinafter referred to as screen design) by using the GUI screen design tool.

  For example, in the first prior art (Patent Document 1), first, a template serving as a basis for a screen design is created by using a source program generated by an automatic program generation tool as an input. Next, this template can be edited with a GUI screen design tool and combined with the original source program to create a target source program.

  In the second prior art (Patent Document 2), first, screen design information and screen component attribute information including information on screen items and events are extracted from the screen specifications created with the GUI screen design tool. To do. Next, from the extracted attribute information of the screen parts, a source program that is an interface for connecting to the business logic and a source program that realizes the behavior of the screen are automatically generated by a program automatic generation tool. Then, the target source program can be obtained by combining the source program that realizes the behavior of the screen and the attribute information of the screen components extracted from the screen specification.

JP 2007-265011 A JP 2004-302571 A

  However, the conventional method has the following problems.

  In the first conventional technique, a case where only a source program is modified after a developer creates a screen design will be considered. In this case, since the automatic program generation tool regenerates the screen design template from the corrected source program, the developer must recreate the screen design created before the source program correction. This increases the amount of work for the developer. This is because a screen design template is generated from a program generated by an automatic program generation tool.

  Further, in the second prior art, when a large number of screens or screens having a complicated design are created, the program automatic generation tool needs to extract and analyze all the attribute information of the screen parts from the screen specifications. Therefore, the process of the automatic program generation tool becomes complicated. Furthermore, it is difficult to ensure that there is no difference between the input screen specification and the screen design generated by the automatic program generation tool. This is because the program automatic generation tool extracts and analyzes all necessary information from the screen specification when generating a source program including a screen design.

  SUMMARY OF THE INVENTION An object of the present invention is to provide an automatic program generation apparatus and an automatic program generation method that can create a program including a screen relatively efficiently.

  An automatic program generation apparatus according to the present invention includes a dynamic information extraction unit that extracts, as first dynamic information, a set of screen component attribute information that meets a predetermined condition from screen mockup information that holds information about screen design. , Acquiring attribute information that can be acquired from the first dynamic information, converting the acquired attribute information into linkage information for generating a predetermined program, and acquiring the first dynamic information By complementing the attribute information that could not be performed using the linkage information, a dynamic information complementing unit that converts the first dynamic information into second dynamic information, and the first of the screen mockup information A screen mockup information replacement unit that replaces the attribute information of the screen component held by the first dynamic information with the attribute information of the screen component held by the second dynamic information, and the second dynamic information. And the replacement Comprises a linkage program generator for generating a linkage program that operates, the combined with a screen mockup information.

  In a preferred embodiment, the second dynamic information can hold identification information that can uniquely identify the second dynamic information, and the design information related to the business logic uniquely identifies the design information. Identifiable identification information can be held, and when the identification information of the second dynamic information is the same as the identification information of the design information, the attribute information held by the second dynamic information The business logic information correction unit that replaces the design information and the logic program that operates in combination with the replaced screen mockup information and the linkage program are generated based on the design information related to the replaced business logic. And a logic program generation unit.

  In a preferred embodiment, among the attribute information extracted from the first dynamic information, the attribute information that does not include information related to screen design may be converted into the cooperation information.

  In a preferred embodiment, when the screen mockup information is described in XML (extensible Markup Language), the attribute information is an element name, an attribute name, or an attribute value, and the predetermined information in the dynamic information extraction unit Is the dynamic information held by the screen mockup information when one or more of the attribute information in the dynamic information held by the screen mockup information and the attribute information as the extraction condition match May be extracted as the first dynamic information.

  In a preferred embodiment, the dynamic information complementing unit may generate the linkage information by converting a character string of the extracted attribute information according to a predetermined rule.

1 is a configuration diagram of an automatic program generation device in Embodiment 1. FIG. 3 is a flowchart illustrating a processing procedure in the first embodiment. 3 is a display example of a screen mockup in the first embodiment. 3 is an example of screen mockup information in the first embodiment. The example of the dynamic information (screen item component) in Example 1. FIG. 7 is an example of dynamic information (event component) in the first embodiment. The example of the replacement target component information (screen item component) in the first embodiment. The example of the replacement target component information (event component) in the first embodiment. An example of a method for extracting dynamic information (screen item parts) in the first embodiment. 9 illustrates an example of a method for extracting dynamic information (event component) in the first embodiment. An example of a method for complementing dynamic information (screen item parts) in the first embodiment. An example of a method for complementing dynamic information (event component) in the first embodiment. 7 is an example of a replacement rule used for replacing screen mockup information in the first embodiment. An example of a method for performing replacement (screen item parts) of screen mockup information in the first embodiment. An example of a method of performing replacement (event component) of screen mockup information in the first embodiment. An example of a method for performing replacement (others) of screen mockup information in the first embodiment. 6 illustrates an example of a method for generating a cooperation program in the first embodiment. The block diagram of the program automatic generation apparatus in Example 2. FIG. 9 is a flowchart illustrating a processing procedure in the second embodiment. 7 is an example of screen mockup information in the second embodiment. The example of the dynamic information (screen item component) in Example 2. FIG. 9 illustrates an example of a method for extracting dynamic information and identification information from screen mockup information according to the second embodiment. An example of a method for providing identification information to screen item parts of dynamic information and screen mockup information in the second embodiment. 10 is an example of business logic information in the second embodiment. 9 illustrates an example of a method for correcting business logic information in the second embodiment. 9 illustrates an example of a method for reflecting identification information in the second embodiment. 9 illustrates an example of a method for generating a logic program in the second embodiment. FIG. 10 is an example of a list of correction locations in the second embodiment.

  The purpose is to generate a program that reproduces the design of the screen mockup. (1) Extract the attribute information of the screen parts from the screen mockup information, and (2) Generate dynamic information by complementing the extracted attribute information. (3) Generate screen programs by replacing screen mockup information using dynamic information, and (4) Generate linkage programs that link with screen programs using dynamic information. did.

Example 1
FIG. 1 is a configuration diagram of an automatic program generation device according to the first embodiment of the present invention.

  As shown in the figure, the automatic program generation device 100 includes a CPU 101, a memory 102, an input device 103, an output device 104, and an external storage device 105. These 101, 102, 103, 104, and 105 are mutually connected via a bus. It is connected. Furthermore, the external storage device 105 includes a dynamic information extraction unit 106, a dynamic information supplementation unit 107, a screen mockup information replacement unit 108, a linkage program generation unit 109, a replacement target component information storage unit 110, and a screen mockup information storage unit. 111, a dynamic information storage unit 112, a screen program storage unit 113, and a linkage program storage unit 114. Among these, the dynamic information extracting unit 106, the dynamic information complementing unit 107, the screen mockup information replacing unit 108, and the cooperation program generating unit 109 are processing programs. Hereinafter, it is assumed that all processing programs are read into the memory 102 at the time of execution and executed by the CPU 101.

  The dynamic information extraction unit 106 extracts dynamic information. Details of the dynamic information will be described later. The dynamic information extraction unit 106 reads screen mockup information from the screen mockup information storage unit 111. The dynamic information extraction unit 106 reads replacement target component information from the replacement target component information storage unit 110. Next, the dynamic information extraction unit 106 extracts screen component attribute information that matches the replacement target component information from the screen mock-up information, and writes it as dynamic information in the dynamic information storage unit 112.

  The dynamic information complementing unit 107 reads the dynamic information from the dynamic information storage unit 112, supplements the attribute information that could not be extracted from the dynamic information, and writes it again in the dynamic information storage unit 112.

  The screen mockup information replacement unit 108 replaces at least a part of the screen mockup information using dynamic information. The screen mockup information replacement unit 108 reads screen mockup information from the screen mockup information storage unit 111 and further reads dynamic information from the dynamic information storage unit 112. Next, the screen mockup information replacement unit 108 replaces a part of the screen mockup information with the complemented dynamic information and writes it in the screen program storage unit 113.

  Based on the dynamic information read from the dynamic information storage unit 112, the cooperation program generation unit 109 generates a cooperation program that operates in combination with the screen mockup information, and writes the cooperation program in the cooperation program storage unit 114.

  The replacement target component information storage unit 110 holds replacement target component information. Details of the replacement target component information will be described later.

  The screen mockup information storage unit 111 holds screen mockup information input from the outside via the input device 103. Details of the screen mockup information will be described later.

  The dynamic information storage unit 112 holds dynamic information. Details of the dynamic information will be described later.

  The screen program storage unit 113 holds a screen program.

  The cooperation program storage unit 114 holds a cooperation program.

  Next, the processing of this embodiment will be described based on the flowchart of FIG.

  Step 200 is a step of inputting information about the screen design created by the developer using a design tool or the like to the screen mockup information storage unit 111 as screen mockup information. Here, the screen mockup information may be described in XML (extensible Markup Language) or the like. Note that the screen mock-up information holds key information for identifying screen items and key information for identifying events as attribute information of screen components. Here, a screen component holding key information for identifying a screen item is called a screen item component, and a screen component holding key information for identifying an event is called an event component. The information held by the screen item component includes, for example, key information related to a screen item for the user to input characters and the like on the screen, and a screen item for causing the user to display characters and the like on the screen. . The information held by the event component includes, for example, key information related to user operations that occur on the screen, such as button clicks and text inputs.

  FIG. 3 is a display example of a screen mockup, which can be created with a design tool or the like. Various tools such as FlexBuilder (registered trademark) or Fireworks (registered trademark) can be selected as the design tool.

  FIG. 4 is an example of screen mockup information described in XML. This is automatically generated as the corresponding screen mockup information when the screen mockup of FIG. 3 is created on the design tool. A part of the attribute value of the screen component is key information. Specifically, the key information of the screen component 401 is “EmployeeName” that is the attribute value of the attribute name “id”. Further, the key information of the screen component 402 is “trace ('Search Employee Event')” which is the attribute value of the attribute name “click”. Here, by setting the key information held by the screen component to an attribute value that does not affect the screen design, the same screen program as the mock-up screen can be generated later. The attribute name for key information is defined by replacement target component information described later.

  Returning to FIG. In step 201, first, the dynamic information extraction unit 106 reads screen mockup information and replacement target component information from the screen mockup information storage unit 111 and replacement target component information storage unit 110, respectively. Next, a screen component that matches the replacement target component information is extracted from the screen mockup information, and the set of attribute information is written in the dynamic information storage unit 112 as dynamic information. The dynamic information holds information related to input / output from the user, information related to processing contents and timing executed by the system in response to the occurrence of an event, and the like, and includes one or more attribute information.

  Next, an example of dynamic information in the present embodiment will be described with reference to FIGS.

  FIG. 5 is an example of dynamic information regarding screen items. In this embodiment, the dynamic information related to the screen item can hold, for example, a tag name 501, an item attribute name 502, an item attribute value 503, a dynamic attribute name 504, a dynamic attribute value 505, and an item variable name 506. For example, the dynamic information 507 holds “TextInput” as the tag name 501 and “id” as the item attribute name 502. Note that the dynamic information storage unit 112 can hold a plurality of pieces of dynamic information regarding screen items.

  FIG. 6 is an example of dynamic information regarding an event. In this embodiment, the dynamic information related to an event can hold, for example, an event attribute name 601, an event attribute value 602, and an event constant name 603. For example, the dynamic information 604 holds “click” as the event attribute name 601 and “trace ('ClearInputEvent')” as the event attribute value 602. Note that the dynamic information storage unit 112 can hold a plurality of pieces of dynamic information regarding events. One event component can hold key information related to a plurality of events. For screen parts that are both screen item parts and event parts, both dynamic information about screen items and dynamic information about events are written in the dynamic information storage unit 112.

  Next, in FIGS. 7 and 8, an example of replacement target component information is shown. The replacement target component information is information on screen components that may exist on the screen mockup, and is information on screen components that need to be replaced when the screen mockup information is converted into a screen program. The replacement target component information includes information related to attributes for extracting each key information from the screen item component and the event component. For example, when the screen mockup information is in the XML format, the replacement target component information is defined by an element name, an attribute name, an attribute value, and the like.

  In FIG. 7, tag names and attribute names of screen item parts that need replacement are defined. In this embodiment, the replacement target component information for the screen item component can hold a tag name 701, an item attribute name 702, and a dynamic attribute name 703. Specifically, the replacement target component information 704 holds “TextInput” as the tag name 701, “id” as the item attribute name 702, and “text” as the dynamic attribute name. Note that the replacement target component information storage unit 110 can hold a plurality of replacement target component information for screen item components.

  In FIG. 8, event attribute names of event parts that need to be replaced are defined. In this embodiment, replacement target component information for an event component can hold an event attribute name 801. Specifically, the replacement target component information 802 holds “click” as the event attribute name 801. It is assumed that the replacement target component information storage unit 110 can hold a plurality of replacement target component information for event components.

  Next, in FIGS. 9 and 10, an example of a method for extracting dynamic information is shown. In the extraction of dynamic information, the dynamic information extraction unit 106 first selects one of the replacement target component information held by the replacement target component information storage unit 110. Next, the dynamic information extraction unit 106 extracts a screen component from the screen mockup information on the condition of the tag name and the attribute name that the selected replacement target component information has. When a plurality of screen parts that meet the conditions are extracted, the attribute information (namely, tag name, attribute name, and attribute value) of the screen parts is written in the dynamic information storage unit 112 as dynamic information for all of them. In this process, screen component extraction and dynamic information writing are performed on all replacement target component information held by the replacement target component information storage unit 110.

  FIG. 9 is an example of extracting dynamic information regarding screen items. First, the dynamic information extraction unit 106 selects replacement target component information 900 from replacement target component information held in the replacement target component information storage unit 110. Next, the screen mockup information 903 is searched for a screen item part that matches the condition of the selected replacement target part information. When the replacement target component information 900 is used as a search condition, attribute information having a tag name 701 of “TextInput”, an item attribute name 702 of “id”, and a dynamic attribute name 703 of “text” is held. The screen parts to be searched are to be searched. As a result, the dynamic information extraction unit 106 extracts the screen item component 901 from the screen mockup information 400 as a search result. Next, “TextInput” of the part name 701, “id” of the item attribute name 702, and “text” of the dynamic attribute name 703, which are the search conditions, are the tag name 501 and the item attribute name of the dynamic information 902, respectively. 502 and dynamic attribute name 504 are stored. Further, the item attribute value “EmployeeName” and the dynamic attribute value “Taro Yamada” extracted from the screen item component 901 are stored as the item attribute value 503 and the dynamic attribute value 505 of the dynamic information 902, respectively. Next, the dynamic information 902 storing the attribute information is recorded in the dynamic information storage unit 112. In this process, the item variable name 506 is not stored and is blank.

  FIG. 10 is an example of extracting dynamic information related to an event. The extraction of the dynamic information related to the event is performed by the same method as the extraction of the dynamic information related to the screen item. First, the dynamic information extraction unit 106 selects replacement target component information 1000 from the replacement target component information held in the replacement target component information storage unit 110. Next, an event part that matches the condition of the selected replacement target part information is searched from the screen mockup information 1003. When the replacement target component information 1000 is used as a search condition, an event component holding attribute information whose event attribute name 801 is “click” is a search target. Accordingly, the dynamic information extraction unit 106 extracts the event component 1001 from the screen mockup information 1003 as a search result. Next, “click” of the event attribute name 801 that is the search condition is stored as the event attribute name 601 of the dynamic information 1002. Further, the event attribute value “trace (“ ClearInputEvent ”)” extracted from the event component 1001 is stored as the event attribute value 602. Next, the dynamic information 1002 storing the attribute information is recorded in the dynamic information storage unit 112. In this process, the event constant name 603 is not stored and is blank.

  Returning to FIG. In step 202, the dynamic information complementing unit 107 supplements the dynamic information. The dynamic information complementing unit 107 reads the dynamic information from the dynamic information storage unit 112, and complements the attribute information that is blank in step 201 among the attribute information held by the dynamic information according to a predetermined complementing rule. After that, the data is written in the dynamic information storage unit 112 again. Here, the predetermined complementing method is a method of filling a blank part of the dynamic information by mechanical conversion processing based on the attribute information already stored in the dynamic information. This step is repeated until processing of all the dynamic information held by the dynamic information storage unit 112 is completed.

  Next, FIG. 11 and FIG. 12 show examples of complementing dynamic information.

  FIG. 11 is an example of complementing dynamic information regarding screen items. The dynamic information complementing unit 107 first reads the dynamic information 1100 from the dynamic information storage unit 112. Next, the item attribute value 503 “EmployeeName” is converted into a character string “employeeName” according to a predetermined complement rule and stored as an item variable name 506.

  FIG. 12 is an example of complementing dynamic information related to an event. As for the dynamic information related to the event, the event attribute value 602 “trace ('ClearInputEvent')” is converted into a character string “CLEAR_INPUT_EVENT” according to a predetermined completion rule, as in the case of complementing the dynamic information related to the screen item. Stored as 603.

  Returning to FIG. In step 203, first, the screen mockup information replacement unit 108 reads the screen mockup information and the dynamic information from the screen mockup storage unit 111 and the dynamic information storage unit 112, respectively. Next, the screen mockup information replacement unit 108 extracts screen components that match the dynamic information from the screen mockup information. Next, the screen mockup information replacement unit 108 replaces the attribute information of the screen component of the screen mockup information according to a predetermined replacement rule. Next, the screen mockup information replacement unit 108 writes the replaced screen mockup information in the screen program storage unit 113. This step is repeated until the processing is completed for all the dynamic information held by the dynamic information storage unit 112.

  FIG. 13 shows an example of replacement rule definition. The replacement rule is composed of a pair of a replacement target attribute 1301 and a replacement attribute value 1302, and describes how to replace the attribute value of each attribute.

  FIG. 14 is a replacement example of screen item parts in the screen mockup information. The screen mockup information replacement unit 108 first reads the screen mockup information and the dynamic information related to the screen item from the screen mockup storage unit 111 and the dynamic information storage unit 112, respectively. Next, the screen mockup information replacement unit 108 selects the dynamic information 1400 from the dynamic information storage unit 112. Next, the screen mockup information replacement unit 108 uses the tag name, item attribute name, item attribute value, dynamic attribute name, and dynamic attribute value held by the selected dynamic information as search conditions, and screen mockup information. Extract screen item parts to be replaced. Here, the screen item component whose tag name is “TextInput”, item attribute name is “id”, item attribute value is “EmployeeName”, dynamic attribute name is “text”, and dynamic attribute value is “Taro Yamada” Becomes a search target, and the screen item part 1401 is extracted as a search result. Furthermore, the screen mockup information replacing unit 108 replaces the extracted attribute information of the screen component according to the replacement rule 1300 in FIG. The replacement rule 1300 describes that the item attribute value “Employeename” is replaced with the item variable name “employeeName” and the dynamic attribute value “Taro Yamada” is deleted. Note that the dynamic information 500 regarding the screen item does not hold the event attribute name and the event attribute value, and therefore no replacement is performed regarding the event attribute value.

  FIG. 15 shows an example of replacing event parts in the screen mockup information. First, the screen mockup information replacement unit 108 reads the screen mockup information and the dynamic information about the event from the screen mockup storage unit 111 and the dynamic information storage unit 112, respectively. Next, the screen mockup information replacement unit 108 selects the dynamic information 1500 from the dynamic information storage unit 112. Next, the screen mockup information replacement unit 108 uses the event attribute name and event attribute value held by the selected dynamic information as search conditions, and extracts event components to be replaced from the screen mockup information. Here, an event component whose event attribute name is “click” and whose event attribute value is “trace ('ClearInputEvent')” is a search target, and the event component 1501 is extracted as a search result. Further, the screen mockup information replacement unit 108 replaces the extracted attribute information of the event component according to the replacement rule 1300 in FIG. The replacement rule 1300 describes that the event attribute value “trace ('ClearInputEvent')” is replaced with a value “dispatchEvent (new Event (MyEvent.CLEAR_INPUT_EVENT))” created by substituting the event constant name.

  FIG. 16 shows an example of replacement that is necessary regardless of the dynamic information. Here, the replacement is performed by embedding information indicating the relation with the cooperation program generated in step 204 described later as a screen component 1600. The screen component 1600 is a screen component that does not hold key information related to screen items and key information related to events.

  Returning to FIG. In step 204, the cooperation program generation unit 109 reads dynamic information from the dynamic information storage unit 112, generates a cooperation program based on the dynamic information, and writes the generated cooperation program in the cooperation program storage unit 114. This step is repeated until the processing is completed for all the dynamic information held by the dynamic information storage unit 112. Here, the linkage program generated in this step is a program that operates in combination with the screen program stored in the screen program storage unit 113. Note that the processing content of the linkage program generated in this step varies depending on the architecture of the software to be generated. For example, there is a process of synchronizing display data of screen item parts with data stored in a temporary storage area. The linkage program generation unit 109 refers to the dynamic information, and the variable name, constant name, function name, data type name, variable value, constant value, or function in the template held in advance by the linkage program generation unit By using the attribute information of dynamic information such as the argument value of as a variable name, a linkage program is generated.

  FIG. 17 shows an example of cooperation program generation. Here, the linkage program generation unit 109 refers to the item variable name 506 “employeeName” of the dynamic information 1700 and uses it as a function name and a function argument value for the linkage program template. 1701 is generated.

  Returning to FIG. In step 205, the screen program and the cooperation program are read from the screen program storage unit 113 and the cooperation program storage unit 114 and output to the output device 104. The output device 104 may output as text data or binary data so that it can be handled by a computer, or may display characters or graphics on a monitor so that a developer can view the data.

  According to the present embodiment, since the information regarding the screen design in the screen mockup information is not changed, a program capable of reproducing the screen design similar to the screen mockup can be generated.

  According to this embodiment, since screen mock-up information is described in XML or the like, it can be applied, so that a screen design developer can use a favorite design tool capable of outputting in XML or the like.

(Example 2)
In the first embodiment, only the program associated with the screen is generated, but in the second embodiment, in addition to this, a business logic program that realizes operation of business data and change of display can be generated.

  FIG. 18 is a configuration diagram of the automatic program generation device according to the second embodiment. As illustrated in FIG. 18, the external storage device 105 includes, for example, a dynamic information and identification information extraction unit 1800, a dynamic information complement unit 107, a screen mockup information replacement unit 108, a cooperation program generation unit 109, and an identification information addition unit. 1801, business logic information correction unit 1802, identification information reflection unit 1803, logic program generation unit 1804, replacement target component information storage unit 110, screen mockup storage unit 111, dynamic information storage unit 112, screen program storage unit 113, cooperation A program storage unit 114, a business logic information storage unit 1805, a logic program storage unit 1806, a logic generation log storage unit 1807, and a logic template information storage unit 1808 are held. Note that, among the above-described constituent elements, the same reference numerals as those in FIG. 1 perform the same processing as in the first embodiment. In addition, the dynamic information and identification information extracting unit 1800, the dynamic information complementing unit 107, the screen mockup information replacing unit 108, the linkage program generating unit 109, the identification information adding unit 1801, the business logic information correcting unit 1802, and the identification information reflecting unit 1803 and the logic program generation unit 1804 are processing programs, and all processing programs are read into the memory 102 during execution and executed by the CPU 101.

  The dynamic information and identification information extraction unit 1800 extracts dynamic information and identification information. First, the dynamic information and identification information extraction unit 1800 reads screen mockup information and replacement target component information from the screen mockup information storage unit 111 and the replacement target component information storage unit 110, respectively. Next, the dynamic information and identification information extraction unit 1800 uses the replacement target component information as a search condition, and extracts a set of screen component attribute information from the screen mockup information. Furthermore, the dynamic information and identification information extraction unit 1800 also extracts identification information that uniquely identifies screen items and events, and uses the extracted attribute information and identification information of the screen parts as dynamic information as the dynamic information storage unit 112. Write to.

  The identification information giving unit 1801 gives identification information. First, the identification information adding unit 1801 reads the dynamic information that is blank because the identification information is undefined from the dynamic information storage unit 112. Next, the identification information adding unit 1801 reads the screen mockup information from the screen mockup information storage unit 111. Next, the identification information adding unit 1801 searches the screen mockup information for a screen component corresponding to the read dynamic information. Next, the identification information adding unit 1801 adds the newly generated identification information to the dynamic information and the screen component, and then writes them into the dynamic information storage unit 112 and the screen mockup storage unit 112, respectively.

  The business logic information correction unit 1802 corrects business logic information. The business logic information correction unit 1802 first reads business logic information from the business logic information storage unit 1805. Next, the business logic information correction unit 1802 refers to the dynamic information read from the dynamic information storage unit 112, corrects the business logic information, and writes the business logic information in the business logic information storage unit 1805 again.

  The identification information reflection unit 1803 reflects the identification information in the business logic information. First, the identification information reflection unit 1803 reads business logic information from the business logic information storage unit 1805. Next, the identification information reflection unit 1803 refers to the dynamic information read from the dynamic information storage unit 112, supplements or corrects the identification information with respect to the business logic information, and writes the business information to the business logic information storage unit 1805 again. .

  The logic program generation unit 1804 generates a logic program. First, the logic program generation unit 1804 reads business logic information and logic template information from the business logic information storage unit 1805 and the logic template information storage unit 1808, respectively. Next, the logic program generation unit 1804 generates a logic program with reference to the logic template information. Next, the logic program generation unit 1804 writes the generated logic program and unprocessed business logic information in the logic program storage unit 1806 and the logic generation log storage unit 1807, respectively.

  The business logic information storage unit 1805 holds business logic information input from the outside via the input device 103. The business logic information will be described later.

  The logic program storage unit 1805 holds a logic program. A logic program is a program generated from business logic information.

  The logic generation log storage unit 1807 holds business logic information that has not been generated when the logic program is generated.

  The logic template information storage unit 1808 holds logic template information. Details of the logic template information will be described later.

  Next, based on the flowchart of FIG. 19, the process of a present Example is demonstrated. It should be noted that steps 202, 203, and 204 perform the same processing as each step in the first embodiment.

  Step 1900 is a step in which information relating to the screen design created by the developer using a design tool or the like is input to the screen mockup information storage unit 111 as screen mockup information. Here, the screen component held by the screen mockup information in the second embodiment can hold identification information for uniquely identifying a screen item and an event.

  FIG. 20 shows an example in which the screen component holds identification information. The screen component 2001 holds identification information “XYY1-S124-32” as an attribute value of the uid attribute. Further, the screen component 2002 does not hold identification information.

  Returning to FIG. In step 1901, first, the dynamic information and identification information extraction unit 1800 reads screen mockup information and replacement target component information from the screen mockup information storage unit 111 and replacement target component information storage unit 110, respectively. Next, a screen component that matches the replacement target component information is extracted from the screen mockup information, and the set of attribute information is written in the dynamic information storage unit 112 as dynamic information. At this time, if identification information is given to the screen component, that information is also extracted.

  FIG. 21 shows an example of dynamic information related to screen items. In this embodiment, the dynamic information related to the screen item includes the part name 2101, the item attribute name 2102, the item attribute value 2103, the dynamic attribute name 2104, the dynamic attribute value 2105, the item variable name 2106, and the values of the identification information 2107. Can be held.

  FIG. 22 shows an example of extracting dynamic information related to screen items from screen mockup information. The extraction of dynamic information is performed by the same method as in step 201 in the first embodiment. Here, the identification information is extracted by extracting the attribute value holding the identification information from the screen component 2200 to be extracted. In FIG. 22, “XYY1-S124-32”, which is the attribute value of the uid attribute, is extracted as the attribute value of the identification information. If the screen component to be extracted does not hold the identification information, the identification information 2107 column in the dynamic information 2201 is left blank.

  Returning to FIG. In step 1902, the identification information adding unit 1801 first reads dynamic information whose identification information is blank from the dynamic information storage unit 112. Next, the screen mockup information is read from the screen mockup information storage unit 111. Next, a screen component corresponding to the read dynamic information is extracted from the screen mockup information. Next, the newly created identification information is added to the dynamic information. Further, the same identification information is given to the screen parts of the screen mockup information. Next, the dynamic information and the screen mockup information to which the identification information is added are written in the dynamic information storage unit 112 and the screen mockup information storage unit 112, respectively. This step is repeated until processing is completed for all dynamic information whose identification information is blank. In this step, no change is made to the dynamic information and the screen component information for which identification information has already been set.

  FIG. 23 shows an example in which identification information is given. First, the identification information adding unit 1801 acquires one piece of dynamic information 2300 whose identification information is blank from the dynamic information storage unit 112. Next, new identification information “XGMF-T357-K3” is generated and added as identification information of the acquired dynamic information 2300. Next, the screen component 2302 corresponding to the acquired dynamic information is read from the screen mockup information. Next, the same identification information as that given to the dynamic information 2300 is assigned to the acquired screen component 2302, and the screen component 2303 is converted.

  Returning to FIG. In step 1903, the dynamic information is read from the dynamic information storage unit 112 and output to the output device 104 in accordance with an instruction from the developer. At this time, the identification information may not be output.

  In step 1904, business logic information input from the developer through the input device 103 is written in the business logic information storage unit 1805. Here, the business logic information is information that defines an operation related to a change in business data or a display change, and an execution timing of the operation. The business logic information includes design information that needs to be edited with reference to dynamic information and design information that can be edited without referring to dynamic information. Among these, the design information that needs to be edited with reference to the dynamic information is made to hold the corresponding identification information.

  FIG. 24 shows an example of business logic information. The business logic information 2400 holds a logic name 2401 and a logic template 2402 as design information that can be edited without referring to dynamic information. In addition, a trigger event constant name 2403, a variable name (1) 2404, and a variable name (2) 2405 are held as design information that needs to be edited with reference to dynamic information. Identification information 2406 is also held for design information that needs to be edited with reference to dynamic information. Note that the design information of the logic template 2402 is information representing the relationship with the logic template information held by the logic template information storage unit 1808.

  Returning to FIG. In step 1905, first, the business logic correction unit 1802 reads business logic information from the business logic information storage unit 1805. Next, one piece of design information that needs to be corrected with reference to dynamic information is selected from the read business logic information. Next, dynamic information that holds identification information corresponding to the selected design information is extracted from the dynamic information storage unit 112. Next, the value of the design information selected above is corrected by the extracted dynamic information. Next, business logic information reflecting the corrected design information is written in the business logic information storage unit. This step completes the processing for all the design information that needs to be corrected by referring to the dynamic information among the design information of all the business logic information held by the business logic information storage unit 1805. Repeat until.

  FIG. 25 shows an example of business logic correction. First, the variable name (2) 2405 is selected from the business logic information 2400. Next, the dynamic information holding “XYY1-S124-32”, which is the value of the identification information corresponding to the selected design information, is extracted from the dynamic information storage unit 112 as the identification information. Next, the design information of the variable name (2) 2405 is overwritten with the value “division” of the item variable name of the dynamic information 2500 extracted above. As shown in FIG. 28, a list of corrected locations may be displayed for the developer.

  Returning to FIG. In step 1906, the developer edits the business logic information extracted from the business logic information storage unit via the input device 103. At this time, the identification information reflection unit 1803 acquires business logic information from the business logic information storage unit 1805. Next, one piece of design information edited by the developer is selected from the acquired business logic information. Next, the dynamic information corresponding to the selected design information is acquired from the dynamic information storage unit 112. Next, the identification information is overwritten on the design information selected above with the identification information held by the acquired dynamic information. If dynamic information corresponding to the selected design information does not exist in the dynamic information storage unit 112, the identification information of the selected design information is overwritten with a blank. This step is repeated until the processing is completed for all business logic information.

  FIG. 26 shows an example in which identification information is reflected. First, the identification information reflection unit 1803 selects “employeeNumber” of the variable name (1) 2404 which is the edited design information from the business logic information 2400 edited by the developer. Next, the dynamic information corresponding to the selected design information is acquired from the dynamic information storage unit 112. Since the identification information of the acquired dynamic information 2600 is “ORB0-1AKA-TS”, the identification information of the variable name (1) 2404, which is the design information selected above, is overwritten on “ORB0-1AKA-TS”.

  Returning to FIG. In step 1907, first, the logic program generation unit 1804 acquires logic template information from the logic template information storage unit 1808 based on the design information of the business logic information. Next, by using the design information of business logic information as the variable template information, such as variable name, constant name, function name, data type name, variable value, constant value, function argument value, etc. Generate a logic program. In this step, for business logic information including design information that does not hold identification information, the corresponding logic program is not generated and the business logic information is written in the logic generation log storage unit 1607. This is because the dynamic information that does not hold the identification information in this step is information that does not exist in the dynamic information storage unit 112. Further, this step is repeated until processing is completed for all business logic information held in the business logic information storage unit 1805. Here, the logic program is a program that realizes the contents of business logic information as a program.

  FIG. 27 shows an example of generating a logic program. First, the logic program generation unit 1804 acquires logic template information corresponding to the information of the logic template 2402 from the logic template information storage unit 1808. Next, the event constant name, variable name (1), and variable name (2) of the acquired logic template information 2701 are set to “CLEAR_INPUT_EVENT” and variable name (1) of the event constant name 2403 acquired from the business logic information 2400, respectively. A logic program is generated by complementing with “employeeNumber” in 2404 and “division” in variable name (2) 2405.

  Returning to FIG. Step 1908 is a step in which the developer acquires the program generated by the automatic program generation tool through the output device 104. This tool reads the generated screen program, linkage program, and business logic program from the screen program storage unit 113, the linkage program storage unit 114, and the logic program storage unit 1804 according to the instructions of the developer, and outputs them to the output device 104. Output. Further, when business logic information is stored in the logic generation log storage unit 1807, it may be acquired and output to the output device 104 together with the fact that the corresponding logic program has not been generated. The output may be output as text data or binary data so that it can be handled by a computer, or characters or graphics may be displayed on a monitor so that the developer can view it.

  According to this embodiment, when business logic information or a logic program is created while referring to dynamic information, the change of the dynamic information can be automatically reflected in the business logic and the logic program.

100 Program Automatic Generation Device 106 Dynamic Information Extraction Unit 107 Dynamic Information Supplementation Unit 108 Screen Mockup Replacement Unit 109 Cooperation Program Generation Unit 110 Replacement Target Component Information Storage Unit 111 Screen Mockup Storage Unit 112 Dynamic Information Storage Unit 113 Screen Program Storage unit 114 Cooperation program storage unit 1800 Dynamic information and identification information extraction unit 1801 Identification information addition unit 1802 Business logic information modification unit 1803 Identification information reflection unit 1804 Logic program generation unit 1805 Business logic information storage unit 1806 Logic program storage unit 1807 Logic Generation log storage unit 1808 Logic template information storage unit

Claims (7)

A dynamic information extraction unit that extracts, as first dynamic information, a set of screen component attribute information that meets a predetermined condition from screen mockup information that holds information about the screen design;
Acquire attribute information that can be acquired from the first dynamic information, convert the acquired attribute information into linkage information for generating a predetermined program, and acquire the first dynamic information. A dynamic information complementing unit that converts the first dynamic information into second dynamic information by complementing the attribute information that was not present using the linkage information;
A screen mockup information replacement unit that replaces the attribute information of the screen component held by the first dynamic information of the screen mockup information with the attribute information of the screen component held by the second dynamic information;
Based on the second dynamic information, a linkage program generation unit that generates a linkage program that operates in combination with the replaced screen mockup information;
An automatic program generation device comprising: The second dynamic information can hold identification information capable of uniquely identifying the second dynamic information, and the design information related to the business logic can uniquely identify the design information. Information can be held, and when the identification information of the second dynamic information is the same as the identification information of the design information, the design information is attribute information held by the second dynamic information. Business logic information correction part to replace
A logic program generating unit that generates a logic program that operates in combination with the replaced screen mock-up information and the cooperation program, based on design information related to the replaced business logic;
The program automatic generation device according to claim 1, further comprising:   The automatic program generation device according to claim 1, wherein the attribute information that does not include information related to a screen design among the attribute information extracted from the first dynamic information is converted into the linkage information. .   When the screen mockup information is described in XML (extensible Markup Language), the attribute information is an element name, an attribute name, or an attribute value, and the predetermined condition in the dynamic information extraction unit is the When the attribute information in the dynamic information held by the screen mockup information and one or more attribute information as the extraction condition match, the dynamic information held by the screen mockup information is changed to the first information. The automatic program generation apparatus according to claim 1, wherein the automatic program generation apparatus extracts the dynamic information.   The automatic program generating apparatus according to claim 1, wherein the dynamic information complementing unit generates the linkage information by converting a character string of the extracted attribute information according to a predetermined rule. A set of screen component attribute information that meets a predetermined condition is extracted as first dynamic information from screen mockup information that holds information about the screen design,
Acquiring attribute information that can be acquired from the dynamic information, converting the acquired attribute information into linkage information for generating a predetermined program, the attribute information that could not be acquired among the dynamic information By complementing using the linkage information, the first dynamic information is converted into second dynamic information,
Replacing the attribute information of the screen component held by the first dynamic information of the screen mockup information with the attribute information of the screen component held by the second dynamic information;
Based on the second dynamic information, a linkage program that operates in combination with the replaced screen mockup information is generated.
Automatic program generation method. When executed on a computer,
A set of attribute information of screen parts that meet a predetermined condition is extracted as the first dynamic information from screen mockup information that holds information about the screen design,
Acquiring attribute information that can be acquired from the dynamic information, converting the acquired attribute information into linkage information for generating a predetermined program, the attribute information that could not be acquired among the dynamic information By complementing using the linkage information, the first dynamic information is converted into second dynamic information,
Replacing the attribute information of the screen component held by the first dynamic information of the screen mockup information with the attribute information of the screen component held by the second dynamic information;
Based on the second dynamic information, a linkage program that operates in combination with the replaced screen mockup information is generated.
Computer program.

Images