JP6795766B2 - Information processing device and its processing method and program - Google Patents

Description

The information processing device for generating a program, its processing method, and the program.

In recent years, in a company, business applications are rapidly becoming Web-based so that business can be performed without installing a special application on a client terminal. At the development site of such business applications, development tools that can easily create Web applications without programming are used in order to solve the shortage of development skills and personnel. By using such a development tool, even if the user does not have knowledge of a programming language, a Web application can be automatically generated only by defining basic design information by utilizing business / design know-how.

By the way, such a Web application is designed to prepare multiple screens and transition from one screen to another, but it is necessary to create a screen transition diagram in order to grasp the overall business flow. There is.

Since it is complicated to manually create such a screen transition diagram, a mechanism capable of automatically creating a screen transition diagram is required.

In particular, when developing a Web application, the screen transition specifications are often changed during development, and a screen transition diagram that allows you to visually recognize the state of the screen transition even during development. For example, Patent Document 1 discloses a technique for producing the above.

Japanese Unexamined Patent Publication No. 2016-173721

By the way, since a Web application has many screens, displaying a screen transition diagram results in a complicated diagram, which makes the environment difficult to see.

Further, when the Web application is executed, since the user operates the screen via the screen, a screen transition diagram based on the screen is desirable, but in the technique of Patent Document 1, a screen having a predetermined number of transitions or more is displayed. Since the screen transition diagram is displayed in the center, there is a problem that it is not suitable for the environment at the time of executing the Web application.

Therefore, an object of the present invention is to provide a mechanism for easily generating a screen transition diagram of a screen displayed in the execution environment of a Web system.

An information processing device that generates a program to be executed in the Web system according to the input / output definition corresponding to the screen displayed on the client device used in the Web system, and the input / output of the transition destination according to the action information included in the input / output definition. According to the specific means for specifying the definition, the determination means for determining the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific means, and the transition configuration determined by the determination means. It is characterized by including a screen transition diagram generation means for generating a screen transition diagram corresponding to each of the designated screens used in the generated program.

According to the present invention, it is possible to easily generate a screen transition diagram of a screen to be displayed in the execution environment of the Web system.

It is a figure which shows the system configuration in this embodiment. It is a figure which shows the hardware configuration which can apply to each apparatus in this embodiment. It is a figure which shows the processing outline in the program development apparatus 101. It is a figure which shows the processing outline after the processing of the program development apparatus 101. It is a flowchart which shows an example of the whole Web application and screen specification document generation processing. It is a figure which shows an example of the structure of a definition. It is a flowchart which shows an example of the generation process of a screen specification document. It is a flowchart which shows an example of the search information creation process. It is a flowchart which shows an example of screen list information creation processing. It is a flowchart which shows an example of the screen specification information creation process. It is a flowchart which shows an example of screen item specification information creation processing. It is a flowchart which shows an example of the screen transition diagram creation process. It is a figure which shows an example of an application setting. It is a figure which shows an example of an input / output definition. It is a figure which shows an example of an input / output layout definition screen. It is a figure which shows an example of the setting information of a hierarchy level. It is a figure which shows an example of the data of a screen transition diagram and a transition diagram. It is a figure which shows an example of the screen transition diagram when an icon is operated. It is a figure which shows an example of a screen specification document. It is a flowchart which shows an example of the display control processing in a screen specification document. It is a figure which shows an example of the functional structure which shows the feature in this embodiment.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 shows an example of the configuration of a program development device (information processing device used by a developer to generate a Web application), a program development server, a database server, an application client (client device), and an application server according to the present invention. It is a system configuration diagram (information processing system).

The program development device 101 defines a screen layout, a database search instruction, and the like according to the operation of the developer. The program development device 101 alone may accept input from the developer and cause the program development server 102 described later to perform actual program generation processing and application generation processing, or the program development device 101 alone may perform program generation and application generation. It may be processed.

In this embodiment, the application generated by the program development device 101 is a Web application, but the application is not limited to this, and an application or embedded software that operates in an information processing device such as a mobile phone, a smartphone, or a tablet. , It does not have to be an application that uses communication by Web technology.

The program development server 102a-102b (information processing device) develops a program according to the developer's instruction input by the program development device 101. The program development server 102a may be arranged in a network 106 such as a LAN, and the program development server 102b may be arranged on the Internet or the cloud.

The database servers 103a to 103b (information processing apparatus) are databases used by the developed application, and in the present invention, they may be used for operation confirmation and the like at the time of development. For example, the database server 103 may be configured by the same device as the program development device 101 for use by the developer, or may be arranged in a network 106 such as a LAN (database server 103a). It may also be located on the Internet or in the cloud (database server 103b). Further, when the program development device 101 cooperates with the program development server 102, the program development server 102 and the database server 103 may be configured in the same device.

The application servers 105a to 105b (information processing devices) execute the application developed by the program development device 101. It may be arranged in a network 106 such as a LAN (application server 105a), or may be arranged on the Internet or the cloud (application server 105b). Further, it can operate by connecting to the network 106, the Internet, and the database server 103 on the cloud.

The application clients 104a to 104b (information processing devices) are user input terminals that operate the application program developed by the program development device 101 in cooperation with the application server 105. It may be arranged in a network 106 such as a LAN (application client 104a), or may be arranged on the Internet or the cloud (application client 104b). It may be an information processing device such as a mobile terminal.

FIG. 2 is a block diagram showing an example of each hardware configuration applicable as the program development device 101, the program development server 102, the database server 103, the application client 104, and the application server 105 according to the present invention.

In FIG. 2, the CPU 201 comprehensively controls each device connected to the system bus 204.

Further, the ROM 203 or the external memory 211 stores an operating system (OS), which is a control program of the CPU 201, and a program for realizing various functions described later of the information processing device such as each server, client, and device.

The RAM 202 functions as a main memory, a work area, a temporary shunting area, and the like of the CPU 201.

The input controller 205 controls the input from the input unit 209. Examples of the input unit 209 include pointing devices such as a keyboard and a mouse in the information processing device.

The output controller 206 controls the display of the output unit 210. Examples of the output unit 210 include a CRT and a liquid crystal display.

The external memory controller 207 controls access to the external memory 211 that stores the boot program, various applications, font data, user files, edit files, printer drivers, and the like. In addition, various tables and parameters for realizing various functions of each server, client, device, etc. are stored. Examples of the external memory 211 include a hard disk (HD), a flexible disk (FD), a compact flash (registered trademark) connected to a PCMCIA card slot via an adapter, smart media, and the like.

The communication I / F controller 208 executes a communication control process with an external device via the network.

The program 212 for realizing the present invention is recorded in the external memory 211, and is executed by the CPU 201 by being loaded into the RAM 202 as needed.

Next, the basic processing in the present embodiment will be described with reference to the configuration diagrams of FIGS. 3 and 4. The details of the characteristic processing in this embodiment will be described with reference to the flowcharts of FIGS. 5, 7 to 12, and 20 (particularly FIG. 12).

FIG. 3 is a configuration diagram showing an outline of processing of the program development device 101. The program development device 101 is a device for the purpose of automatically generating a Web application based on a definition file defined by a developer who develops a Web application. The program development device 101 is composed of a repository definition unit 401, a Web application generation unit 416, and a screen specification document generation unit 420. Further, in addition to the above, the layer level setting 415 and the screen transition diagram generation unit 439 are provided as features in the present embodiment.

The repository definition unit 401 includes an application definition 402, an input / output definition 403, a data model definition 404, a business process definition 405, a database definition 406, a document definition 407, a screen HTML data 408, a document filter definition 409, a cover file 410, and an application resource. It includes a file 411, a document resource file 412, a header / footer file 413, related documents 414, and a hierarchy level setting 415. These files are input and created by the developer via the Web application development tool. That is, the repository definition unit 401 manages the input definition information that defines the items input as arguments to the program and the output definition information that defines the items output as the processing result from the program as input / output definition information.

Next, the Web application generation unit 416 will be described. The information generated by the Web application generation unit 416 is stored in the external memory 211.

The Web application generation unit 416 analyzes the repository definition unit 401 by the repository definition analysis unit 417, and the Web including the Java code 444 compiled by the source code compilation unit 419 and the HTML / JSP / Javascript 445 via the Web application code generation unit 418. Generate application 443 (Java is a registered trademark).

The repository definition analysis unit 417 shall read and analyze the database definition 406, the application definition 402, the data model definition 404, the input / output definition 403, and the business process definition 405 from the repository definition unit 401.

That is, the Web application generation unit 416 is an example of a means for storing a rule for generating a program used for a Web application.

The Web application generation unit 416 generates a source code (JSP) in the Web application code generation unit 418 using the code generation rules stored in the external memory 211 and the contents analyzed by the repository definition analysis unit 417. .. This source code is taken in and a file compiled by the source code compilation unit 419 is generated. Then, the source code compilation unit 419 deploys the compiled file to the application server. The source code, compiled files, and deployed data are also collectively referred to as program data.

More specifically, the generated source code is broadly divided into server and client. The source code for the server is compiled to generate a compiled file, and the source code for the client is not compiled and is placed on the program development device 101 as a file. Deploy to application server 105 using this file.

Also, for the server, a Java program (Java is a registered trademark) is generated, and immediately after it is generated, it is compiled into a class file, and the class file is deployed. For clients, JSP / Javascript / CSS are generated, and they are not compiled and are deployed as they are.

The deployed module is the Web application 443. Specifically, when deployed, a file with the extension ".war" is placed on the application server. That is, the Web application generation unit 416 stores the rules for generating the program used for the Web application. For example, the source code is generated according to a predetermined rule.

Next, the screen specification document generation unit 420 will be described. The information generated by the screen specification document generation unit 420 is stored in the external memory 211.

The screen specification document generation unit 420 analyzes the repository definition unit 401 by the repository definition analysis unit 421. The screen specification document generation unit 420 includes a screen list generation unit 422, a screen specification generation unit 423, a screen HTML generation unit 424, a screen item specification generation unit 425, a search function generation unit 426, a related document generation unit 428, and a cover page generation unit 429. A screen specification document 448 composed of HTML / CSS / JavaScript449 and an image file 450 is generated via a header / footer generation unit 430 and a screen transition diagram generation unit 439 (java is a registered trademark).

The screen transition diagram generation unit 439 includes a screen transition data extraction unit 440 that extracts data necessary for the screen transition diagram, a screen block generation unit 441, and a screen transition diagram layout configuration unit 442.

At that time, the screen transition diagram layout configuration unit 442 sets the screen list generation unit 422, the screen specification generation unit 423, and the screen by the area output setting 434 and the area size setting 435 of the document area setting management unit 433 via the output filter management unit 431. The layout is reflected in the HTML generation unit 424, the screen item specification generation unit 425, and the search function generation unit 426, and the entire document is decorated using the built-in design information 437 and the user-created design information 438 via the document theme management unit. Is reflected in the screen specification document 448.

Further, the language-specific document replacement processing unit 432 sets a language-specific file in the cover generation unit 429 and the header / footer generation unit 430.

That is, the screen specification document generation unit 420 generates a document explaining the definition (screen) of the Web application by using the input / output definition 403.

FIG. 4 is a configuration diagram showing an outline of processing of the application server 105, the Web server 107, and the application client 104.

The application server 105 is a server that deploys the file generated by the Web application generation unit 416 and executes the Web application 443. The Web application 443 includes a compiled Java code 444 and a file of HTML / JSP / Javascript 445 (Java is a registered trademark). It is also linked with the database 446.

The Web server 107 stores the screen specification document 448 generated by the screen specification document generation unit 420, and transmits the screen specification document to the application client 104 in response to a request from the application client 104.

A display example of the application client 104 of the screen specification document is 1900 in FIG.

In the present embodiment, the application server 105 and the Web server 107 are in separate housings, but they may be executed in the same housing.

FIG. 5 is a diagram showing an example of a flowchart of the entire Web application and screen specification document generation process. The CPU 201 of each device executes each step in the following flowchart.

In step S500, the program development device 101 receives the input of the definition for automatic generation of the Web application. Specifically, as the Web application (project) to be developed, the application code, name, application type, etc. are set in the application setting 1300 of FIG.

Data model definition, input / output definition, and business process definition are set for this Web application (project). These definitions are arbitrarily set by the user on the setting screen for automatically generating the Web application, but may be configured to read the definitions generated in advance.

Further, in the affiliation input / output list 1301, which input / output definition belongs (uses) is set.

The input / output definition is defined using the data set in FIGS. 14 and 15. Further, the screen transition diagram hierarchy level to be displayed in the screen specification document is also set in advance, and the setting information of 1600 in FIG. 16 is stored. In the present embodiment, as shown by 1601, the hierarchy is set to one hierarchy.

In step S501, when the program development device 101 receives the Web application generation instruction by the user, the program development device 101 reads the application definition 402 of the repository definition unit 401 stored in the external memory 211 into the RAM 202.

In step S502, the program development device 101 reads the data model definition 404. The data model definition 404 is registered as the repository definition unit 401. The data model definition 404 is registered by mapping the items on the database on the data model setting screen (not shown). Generally, one table and one data model are created. Since the creation of the data model definition is a known technique in the development of Web applications, the description thereof will be omitted.

In step S503, the program development device 101 reads the input / output definition 403. The input / output definition 403 is registered as the repository definition unit 401.

The generation of the input / output definition 403 will be described. As described above, the setting itself of the input / output definition 403 is performed in advance such as step S500. First, on the input / output layout definition screen 1500 of FIG. 15, objects (fields and action buttons) are arranged on the screen editor by drag-and-drop operation or the like.

Further, the condition is set for the action button in 1501 of FIG. Set the transition destination screen (definition of next input / output) when the action button is pressed in 1502.

An example of the input / output definition corresponding to FIG. 15 is 1403 of FIG. In 1403 of FIG. 14, in addition to the definition corresponding to the action button, the definition of the text field set on the input / output layout definition screen 1500 is displayed in another record.

The input / output definitions for each screen indicate 1400 to 1403. In addition to the screen definition, it is also possible to set the definition for import and export processing for the next input / output.

In 1404, by setting the identification information of "(at) NODOC" for the input / output definition, it is possible to control so that the screen specification document is not generated individually. The screen specification document is not generated, but it shall be displayed as an object of the screen transition diagram. "(At) NODOC" will be described below as "NODOC".

The figure showing the structure of the set definition in this embodiment is 600 in FIG. 6, and the structure corresponding to 1400 to 1403 is 601.

The definition corresponding to the action button has values such as item type, item code, name, and next input / output. For the next input / output, the screen (definition) to move to the next is set by the action. In the present embodiment, the screen transition diagram is color-coded according to the item type, the transition destination is determined by the next input / output, and the screen transition diagram is generated.

In step S504, the program development device 101 reads the business process definition 405. The business process definition 405 is registered as the repository definition unit 401. The business process definition 405 is preset in step S500. Further, the business process definition 405 defines the flow of processing of the received data. For example, it defines a logic that checks for duplication of input data and registers it. The business process definition is also omitted because it is a known technology in the development of Web applications.

In step S505, the program development device 101 reads the database definition 406 of the repository definition unit 401 stored in the external memory 211 into the RAM 202. It is assumed that the database definition 406 is generated in advance.

In step S506, the Web application generation unit 416 of the program development device 101 acquires information from each definition / file of the read repository definition unit 401 and generates the source code of the Web application (for example, Web application 443). Specifically, it is generated based on "input / output definition", "data model definition", and "business process definition". The generated source code also includes files used for providing Web applications such as HTML, JSP, and Javascript (registered trademark) in which programming languages are described.

In step S507, the screen specification document generation unit 420 of the program development device 101 generates the screen specification document 448. The repository definition analysis unit 421 analyzes the read definition, stores it in the memory, and appropriately refers to it from each generation unit. In addition, the layout configuration unit 427 lays out each component of the document created by each generation unit to form a screen specification document.

The process of generating the screen specification document will be described in detail in FIG. 7, and the image of the generated screen specification document is shown in FIG. 19 of 1900. The generated screen specification document is saved corresponding to the corresponding input / output definition code (for example, PRODUCT_REGIST_IO).

Here, the screen specification document of FIG. 19 will be described.

1901 indicates a search function. It is possible to search and display the input / output including the specified character string from the screen specification document.

1902 is a list in which screen specification documents can be displayed. Displayed corresponding to the input / output list specified in 1301. The input / output screen specification document is displayed in the right pane by the user's operation (click, etc.).

1903 is a screen specification area. Display the attributes set in the I / O definition.

1904 is a screen HTML area. The screen image of the input / output definition is displayed in HTML.

1905 is a screen item specification area. List the attributes of the input / output items corresponding to the screen. Attributes are displayed corresponding to "1" to "6" of 1904.

1906 is a screen transition diagram area. The transition source and transition destination of the input / output displayed in the document are displayed in the screen transition diagram. The generation of this screen transition diagram will be described in detail in FIG.

1907 is the relevant document area. Display links to related documents.

FIG. 7 is a diagram showing an example of a flowchart for generating a screen specification document. The CPU 201 of the device executes each step in the following flowchart.

In step S701, the output filter management unit 431 reads the document filter definition 409. The output filter management unit 431 stores the document filter information in the memory, and the information is appropriately referred to by various generation units.

The document filter determines, for example, the attributes (items) to be displayed in 1900 of FIG. 19 and the input / output types (IO, MENU, DIALOG), and can be arbitrarily set by the developer. This filters the information displayed in 1900 of FIG.

In step S702, the header / footer generation unit 430 confirms the presence / absence of the header / footer file 413. If there is a header / footer file 413, the header / footer generation unit 430 creates the header / footer in step S703. The header / footer referred to here is not shown in 1900 of FIG. 19, and for example, in addition to 1900, the header portion and the footer portion can be described by JSP. The header part is a part for displaying a company logo, for example. Further, the footer portion is, for example, a portion for displaying a copyright.

In step S704, the search function generation unit 426 creates the search information. Details will be described with reference to the flowchart of FIG.

In step S705, the screen list generation unit 422 creates a screen list. Details will be described with reference to the flowchart of FIG.

The processing from steps S706 to S719 is repeated for the input / output definition. In this embodiment, as shown in FIG. 14, since there are three input / output definitions (main menu, product list, and product registration), the input / output definition is repeated three times.

In step S707, the screen specification document generation unit 420 confirms whether or not "NODOC" is specified in the input / output definition. If specified, the screen specification document for the input / output definition is not output, and the process moves to the next input / output definition process.

The "NODOC" designation is the one specified in 1404, and each input / output definition information is managed by the memory. 1404 is a screen image diagram in which "NODOC" is specified for the input / output definition.

In step S708, the screen specification document generation unit 420 queries the output filter management unit and confirms whether the input / output type (MENU, IO, etc.) of the input / output definition is set as the output target. It is assumed that the developer has set in advance whether to output.

If it is not the output target, the screen specification document of the input / output definition is not the output target and moves to the next input / output process.

In step S709, the screen list generation unit 422 outputs a screen list based on the information created in step S705. Specifically, it outputs HTML information displayed in 1902.

In step S710, the screen specification generation unit 423 creates and outputs the screen specification. The screen specification creation / output processing will be described with reference to the flowchart of FIG.

In step S711, the screen HTML generation unit 424 creates and outputs the screen HTML. The data of the screen HTML data 408 is incorporated into each display component of the screen HTML. This screen HTML is data corresponding to the screen laid out on the input / output layout definition screen 1500, and numbers are assigned to each item.

In step S712, the screen item specification generation unit 425 creates and outputs the screen item specification. The screen item specification creation / output processing will be described with reference to the flowchart of FIG.

In step S713, the related document generation unit 428 confirms whether or not the related document 414 is set. If it is set, the process is transferred to step S714, and if it is not set, the process is transferred to step S715.

In step S714, the related document generation unit 428 creates link information of the related document and outputs it to the HTML file.

In step S715, the screen transition diagram generation unit 439 creates and outputs the screen transition diagram. The screen transition diagram creation / output process will be described with reference to the flowchart of FIG.

In step S716, the header / footer generation unit 430 determines whether or not the header / footer has been created in step S702. If it has been created, the process is transferred to step S717, and if it has not been created, the process is transferred to step S718.

In step S717, the header / footer generation unit 430 outputs the created header / footer to an HTML file.

In step S718, the search function generation unit 426 outputs to an HTML file based on the information created in step S704.

In step S720, the cover generation unit 429 determines whether the cover file 410 is set. If the cover file 410 is set, the process proceeds to step S721. If the cover file 410 is not set, the process ends.

The cover file 410 is a file showing a top screen to be displayed in the area of 1908. If this top screen does not exist, the screen specification document corresponding to the first screen (definition) in the screen list is displayed. For example, the main menu.

FIG. 8 is a diagram showing an example of a flowchart for creating search information. The CPU 201 of the device executes each step in the following flowchart.

The search function generation unit 426 repeats the processes from step S801 to step S805 for the number of input / output definitions.

Step S802 determines whether or not the input / output definition has "NODOC" designation. If "NODOC" is specified, the process is transferred to step S804, and if "NODOC" is not specified, the process is transferred to step S803. If "NODOC" is specified, the input / output search information is not created, and the process moves to the next input / output definition process.

In step S803, the output filter management unit 431 is inquired to determine whether or not the input / output type (see 1400) of the input / output definition is set as the output target. If it is not the output target, the search information for that input / output is not created, and the process moves to the next input / output process.

In step S804, search information is created. The search information is information including a character string for searching in the screen specification document. For example, it is a setting value of an input / output definition and is text-based data for searching a keyword input in 1901. The created search information is stored in the external memory.

FIG. 9 is a diagram showing an example of a flowchart for creating screen list information. The CPU 201 of the device executes each step in the following flowchart.

The screen list generation unit 422 repeats the processes from step S901 to step S905 for the number of input / output definitions.

Step S902 determines whether or not the input / output definition has "NODOC" designation. If "NODOC" is specified, the process is transferred to step S905, and if "NODOC" is not specified, the process is transferred to step S903. If "NODOC" is specified, the screen list information (corresponding to 1901) related to the input / output definition is not created, and the process proceeds to the next input / output definition process.

Step S903 queries the output filter management unit 431 and determines whether or not the input / output type (see 1400) of the input / output definition is set as the output target. If it is not the output target, the search information for that input / output is not created, and the process moves to the next input / output process.

In step S904, screen list information corresponding to the input / output definition is created. Specifically, a component is generated based on the input / output definition code and name (see 1400). A link to the generated screen specification document is given to this part, and when the part is pressed, the target screen specification document can be acquired and displayed.

FIG. 10 is a diagram showing an example of a flowchart for creating screen specification information. The CPU 201 of the device executes each step in the following flowchart.

The screen specification generation unit 423 repeats the processes from step S1001 to step S1004 for the number of attributes of the input / output definition.

Step S1002 inquires at the output filter management unit 431 and determines whether or not the input / output definition attribute is set as the output target. If it is not the output target, the input / output attribute information is not created and the process moves to the next input / output attribute process. If it is the output target, the process is moved to step S1003.

Step S1003 creates input / output attribute information (corresponding to 1903).

In step S1005, the screen specification generation unit 423 outputs the screen specifications to the HTML file based on the input / output attribute information.

FIG. 11 is a diagram showing an example of a flowchart for creating screen item specification information. The CPU 201 of the device executes each step in the following flowchart.

The screen item specification generation unit 425 repeats the processes from step S1101 to step S1110 for the number of input / output definition items.

Step S1102 determines whether or not the input / output item has "NODOC" designation. If specified, the screen item specification information of the input / output item is not created, and the process moves to the next input / output item process. If not specified, the process is transferred to step S1103.

Step S1103 determines whether the input / output item is a hidden item. If it is a hidden item, the process is moved to step S1104.

Step S1104 inquires at the output filter management unit 431 and determines whether or not the hidden item is set as the output target. If it is not the output target, the screen item specification information of the input / output item is not created and the process moves to the next input / output item. If it is an output target, the process is moved to step S1105.

Step S1105 queries the output filter management unit 431 and determines whether or not the input / output item type of the input / output item is set as the output target. If it is not the output target, the screen item specification information of the input / output item is not created, and the process moves to the next input / output item. If it is an output target, the process is moved to step S1106.

The processing from step S1106 to step S1109 is repeated for the number of input / output item attributes of the input / output item.

Step S1107 inquires at the output filter management unit 431 and determines whether or not the attributes of the input / output items are set as output targets. If it is not the output target, the input / output item attribute information is not created and the process moves to the next input / output attribute process.
If it is the output target, the process is moved to step S1108.

Step S1108 creates screen item specification information.

In step S1111, the screen item specification generation unit 425 outputs the screen item specifications to an HTML file based on the screen item specification information (corresponding to 1905).

FIG. 12 is a diagram showing an example of a flowchart for creating a screen transition diagram. The CPU 201 of the device executes each step in the following flowchart.

The screen transition data extraction unit 440 repeats the processes from step S1201 to step S1207 for the number of definitions of the input / output definitions. In this embodiment, since there are three input / output definitions, the process is repeated three times.

Step S1202 extracts the input / output item code and name (see FIG. 14) and screen data (corresponding to 1503 in FIG. 15) from the input / output definition.

In step S1203, all action definitions are extracted from the input / output definitions and stored in the memory. The action definition is a definition whose item type is "A action". It should be noted that an action definition is set in which an action (search, registration, deletion, cancellation) is automatically executed when an event occurs due to a user operation or the like.

The process from step S1204 to step S1206 is repeated for the number of action definitions.

In step S1205, transition data is extracted from the action definition and stored in the memory. The transition data is the next input / output setting value shown in FIG. With reference to 1413, when the registration button is pressed on the product registration screen, information that can identify the transition to the product list screen is saved. Further, referring to 1411 and 1412, the product registration screen stores information that can be identified as transitioning from the main menu and the product list screen. That is, an example of a specific process for specifying the input / output definition of the transition destination according to the action information included in the input / output definition is shown.

Step S1208 reads the hierarchy level setting file 1600. In this embodiment, the hierarchy level is "1" as shown in 1601.

In step S1209, the transition of the data of the screen to be processed this time (for example, the definition of the product registration screen) from the memory saved in step S1202 and step S1205 and the hierarchical level setting read from the setting file such as 1600 in step S1208. Read the data.

The data for the target screen and the transition screen extracted by the screen transition data extraction unit 440,
The screen block generation unit 441 repeats the processes from step S1210 to step S1214. This process is a process of generating data components that are transition sources and transition destinations used in the transition diagram.

Step S1211 converts the screen transition input / output into data components (blocks). When converting to a data part, a data part (rectangular object) including a 1400 code and a name value is generated. When converting (generating) data components, they are color-coded so that the 1400 input / output types can be identified. The color information is defined in advance according to the type, but the developer may set it arbitrarily.

In addition, the input / output definition corresponding to the generated screen specification document is the standard, and if an object corresponding to the input / output definition that is the standard and the input / output definition of the transition destination or transition source is generated, it can be paraphrased as processing. Is.

Step S1212 determines whether or not the input / output definition has "NODOC" designation. If specified, the link to the screen specification document of the input / output definition is not created, and the process moves to the next input / output process. If not specified, the process is transferred to step S1213.

Step S1213 creates a link to the screen specification document generated corresponding to the input / output definition in the generated data component. Since the file name of the screen specification document is generated in advance according to the rules, it is possible to generate the link at this timing. The link may be created at the timing when the process of FIG. 7 is completed (the timing when the screen specification document is completely generated).

When "NODOC" is specified, the screen specification document is not generated, but it is desirable for the user to recognize the transition source and transition destination, so that the screen specification document can be confirmed on the screen transition diagram.

Step S1223 generates action information. Specifically, the action information (1501) used on the transition source screen (input / output definition) is collected. This action information becomes the information displayed by pressing the 1703 icon. This is an example of the acquisition process for acquiring the action information related to the transition source or transition destination in the screen transition diagram.

Here, when the action information transitions to the same screen (when there is the same next input / output), the action information is managed so that it can be displayed collectively in the screen transition diagram.

In step S1215, the position where the screen transition diagram layout component 442 draws the data component is set. Specifically, when the screen specification document for the product registration screen (input / output definition of product registration) is generated, the position is determined so that the data component of the product registration screen is in the center (on HTML5 Canvas). Position of). With reference to FIG. 17, it is the position of 1705. The information indicating the Canvas is 1701. That is, it shows an example of the process of arranging the objects corresponding to the reference input / output definitions in a form that can be easily recognized by the user.

Step S1216 classifies the data components into groups of transition source and transition destination.
With reference to FIG. 17, as shown in 1702, screen transition information is created by classifying the target screen and other screen data into transition source and transition destination groups. 1706 is the transition source information, and 1707 is the transition destination information.

The processes from step S1217 to step S1221 are repeated for the groups classified in step S1216.

Step S1218 sets the position (position on the Canvas of HTML5) for drawing the data component of each group. As for the drawing position, the position of the transition source data component is set at the position to the left of the position determined in step S1215, and the position of the transition destination data component is set at the right position. If there are multiple data components in the same group, set them to be positioned vertically. The drawing position is determined according to a predetermined rule.

Step S1219 sets a position for drawing a transition arrow representing a transition connecting each data component.

Step S1220 sets a position for drawing an icon for displaying action information. That is, it shows an example of the process of arranging the object for displaying the action information at the position related to the transition in the screen transition diagram.

That is, the process of steps S121-10 to S1221 shows an example of the determination process of determining the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific process.

Step S1222 draws the screen transition diagram on the canvas based on the settings for drawing the screen transition diagram set in steps S1221 to S1215. That is, an example of the screen transition diagram generation process for generating the screen transition diagram corresponding to each of the designated screens used in the generated program according to the transition configuration determined by the determination process is shown. In addition, it is a process of generating a screen transition diagram so that action information can be displayed arbitrarily.

Here, an image when the screen transition diagram is drawn will be described. FIG. 17 is a diagram showing screen transition diagram and transition diagram data.

Reference numeral 1700 is an image diagram of a screen transition diagram of an input / output definition (PRODUCT_REGIST_IO) that is a target of screen specification document output. Reference numeral 1701 is HTML of the screen transition diagram portion. Reference numeral 1702 is screen transition information.
Reference numeral 1703 is an icon displayed when the icon displayed on the screen transition diagram is clicked. Reference numeral 1704 is a transition destination data component determined from the set value of the next input / output of 1413. Reference numeral 1705 indicates a data component of the input / output definition (PRODUCT_REGIST_IO) to be output of the screen specification document, and is arranged in the center on the canvas.

Further, FIG. 18 shows a screen transition diagram when the action information icon of 1703 in FIG. 17 is operated. FIG. 18 is an image diagram of a screen transition diagram when the icon is operated. 1800 is a diagram showing an action information display example, and is an action information example of a product list displayed when 1801 presses an icon. Further, 1801 is information regarding the action of 1412.

The information regarding the action to be displayed in 1801 is acquired from the memory when the transition diagram is drawn in step S1222. That is, it is an example of the acquisition process for acquiring the action information related to the transition source or transition destination in the screen transition diagram.

Further, the information regarding the action to be displayed in 1801 is displayed on the screen transition diagram so that the plurality of action information can be collectively displayed when there are a plurality of action information for the same transition destination.

In this way, it is possible to easily generate a screen transition diagram suitable for each screen based on the designated screen (input / output definition). Since a screen transition diagram suitable for each screen specification document can be generated, it is possible to easily grasp what kind of screen transition is performed by what kind of action based on the screen confirmed by the user. It will be possible.

FIG. 20 is a diagram showing an example of a flowchart of display control in a screen specification document. The CPU 201 of the device executes each step in the following flowchart.

The application client 104 accesses the Web server 107 to acquire the screen specification document (HTML). Display the acquired screen specification document on the display. As described above, FIG. 19 shows a display example of the screen specification document.

Step S2001 accepts an operation from the user via the screen list 1902. Specifically, it accepts clicks on the screen specification document of the input / output definition that you want to display.

In step S2002, the screen specification document of the selected input / output definition is acquired from the Web server 107 and displayed according to the link of the screen list 1902 (1908). In addition, the link includes a code corresponding to the screen (for example, PRODUCT_REGIST_IO), and it is assumed that the screen specification document corresponding to this code is acquired.

Step S2003 determines whether or not the action information icon 1703 is selected in the screen transition diagram 19 of the screen specification document. If the icon 1703 is selected, the process proceeds to step S2004. If the icon 1703 is not selected, the process proceeds to step S2005.

Step S2004 displays the action information. An example of displaying action information is 1801. This action information is also acquired from the Web server 107.

Step S2005 determines whether or not the data component has been clicked. Specifically, it is determined whether or not a data component such as 1704 is selected. If a data component is selected, the process proceeds to step S2006. If no data part is selected, it ends (waits for operation).

Step S2006 acquires the code possessed by the selected data component. For example, 1707 "PRODUCT_LIST_IO" is acquired.

In step S2007, the target screen specification document is requested from the Web server based on the acquired code, and the screen specification document corresponding to the code is acquired. In addition, this acquired screen specification document is displayed.

Although the present embodiment has been described as a system for generating and constructing a Web application, it may be a system that operates as a Web service that exchanges in XML format.

Next, an example of the functional configuration showing the features in the present embodiment will be described with reference to FIG.

The functional configuration of FIG. 21 is the functional configuration of the program development device 101, but it may be a server as long as it is a device capable of program development. That is, when using a system that can be developed in a cloud environment, it is possible to replace it with the functional configuration of the server. That is, it can be paraphrased as an information processing device that generates a program to be executed by the Web system. Further, it is an information processing device that generates a program to be executed in the Web system according to the input / output definition corresponding to the screen displayed on the client device used in the Web system.

The identification unit 2101 is a functional unit that specifies the input / output definition of the transition destination according to the action information included in the input / output definition.

The determination unit 2102 is a functional unit that determines the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific unit 2101.

The screen transition diagram generation unit 2103 is a functional unit that generates a screen transition diagram corresponding to each of the designated screens used in the generated program according to the transition configuration determined by the determination unit 2102.

The acquisition unit 2104 is a functional unit that acquires action information related to the transition source or transition destination in the screen transition diagram.

Further, the screen transition diagram generation unit 2103 is a functional unit that generates a screen transition diagram so that the action information acquired by the acquisition unit 2104 can be arbitrarily displayed.

Further, the screen transition diagram generation unit 2103 includes a plurality of action information of the input / output definition, and when there is a plurality of action information for the same transition destination, the screen transition can be displayed collectively. It is a functional part that generates a figure.

Further, the screen transition diagram generation unit 2103 is a functional unit that arranges an object for displaying the action information at a position related to the transition in the screen transition diagram.

The document generation unit 2105 is a functional unit that generates a document that displays the specifications of the input / output definition according to the input / output definition.

Further, the screen transition diagram generation unit 2103 is a functional unit that generates a screen transition diagram corresponding to the document generated by the document generation unit 2105.

Further, the screen transition diagram generation unit 2103 is a functional unit that generates an input / output definition as a reference and an object corresponding to the input / output definition of the transition destination or the transition source.

The object is generated by the document generation unit 2105 so as to link with the document generated by, and is created by the screen transition diagram generation unit 2103. The object is identifiable according to the type of input / output definition.

The reference input / output definition is an input / output definition used when the document generation unit 2105 generates a document, and the screen transition diagram generation unit 2103 uses an object corresponding to the reference input / output definition as a user. Generates a screen transition diagram arranged in a form that is easy to recognize.

This is the end of the detailed description of this embodiment.

In the present embodiment, a screen transition diagram for each screen to be displayed in the execution environment of the Web application can be easily generated.

As described above, the recording medium on which the program that realizes the functions of the above-described embodiment is recorded is supplied to the system or the device, and the computer (or CPU or MPU) of the system or the device stores the program in the recording medium. Needless to say, the object of the present invention can be achieved by reading and executing.

In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium on which the program is recorded constitutes the present invention.

Recording media for supplying programs include, for example, flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EEPROMs, and silicon. A disk or the like can be used.

Further, by executing the program read by the computer, not only the function of the above-described embodiment is realized, but also the OS (operating system) or the like running on the computer is actually operated based on the instruction of the program. Needless to say, there are cases where a part or all of the processing is performed and the processing realizes the functions of the above-described embodiment.

Further, after the program read from the recording medium is written to the memory provided in the function expansion board inserted in the computer or the function expansion unit connected to the computer, the function expansion board is based on the instruction of the program code. It goes without saying that there are cases where the CPU or the like provided in the function expansion unit performs a part or all of the actual processing, and the processing realizes the functions of the above-described embodiment.

Further, the present invention may be applied to a system composed of a plurality of devices or a device composed of one device. It goes without saying that the present invention can also be applied when it is achieved by supplying a program to a system or device. In this case, by reading the recording medium in which the program for achieving the present invention is stored into the system or device, the system or device can enjoy the effect of the present invention.

The form of the program may consist of object code, program code executed by an interpreter, script data supplied to an OS (operating system), and the like.

Further, by downloading and reading a program for achieving the present invention from a server, database, or the like on the network by a communication program, the system or device can enjoy the effect of the present invention. It should be noted that all the configurations in which each of the above-described embodiments and modifications thereof are combined are also included in the present invention.

101 Program development device 102 Program development server 103 Database server 104 Application client 105 Application server 106 Network 107 Web server 201 CPU
202 RAM
211 External memory

Claims (10)

An information processing device that generates a program to be executed in a Web system according to the input / output definitions corresponding to the screens displayed on the client device used in the Web system.
A specific means for specifying the input / output definition of the transition destination according to the action information included in the input / output definition, and
A determination means for determining the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific means, and
An information processing apparatus comprising: a screen transition diagram generating means for generating a screen transition diagram corresponding to each designated screen used in a generated program according to a transition configuration determined by the determining means. Further provided with an acquisition means for acquiring action information related to the transition source or transition destination in the screen transition diagram.
The information processing device according to claim 1, wherein the screen transition diagram generation means can arbitrarily display the action information acquired by the acquisition means and generates a screen transition diagram. The screen transition diagram generation means includes a plurality of action information of the input / output definition, and when there are a plurality of action information for the same transition destination, the screen transition diagram can be displayed collectively. The information processing apparatus according to claim 2, wherein the information processing apparatus is generated. The information processing device according to claim 2 or 3, wherein the screen transition diagram generating means arranges an object for displaying the action information at a position related to the transition in the screen transition diagram. A document generation means that generates a document that displays the specifications of the input / output definition according to the input / output definition.
The information processing apparatus according to any one of claims 1 to 4, wherein the screen transition diagram generating means generates a screen transition diagram corresponding to a document generated by the document generating means. The screen transition diagram generation means is characterized in that an object corresponding to a reference input / output definition and an input / output definition of a transition destination or a transition source is generated.
The information processing apparatus according to claim 5, wherein the object is generated so as to be linked to a document generated by the document generation means. The information processing apparatus according to claim 6, wherein the object is identifiablely generated according to the type of the input / output definition. The reference input / output definition is an input / output definition used when a document is generated by the document generation means.
Any one of claims 5 to 7, wherein the screen transition diagram generating means generates a screen transition diagram in which objects corresponding to the reference input / output definitions are arranged in a form that can be easily recognized by the user. The information processing device described in. It is a processing method of an information processing device that generates a program to be executed in a Web system according to an input / output definition corresponding to a screen displayed on a client device used in the Web system.
A specific step to specify the input / output definition of the transition destination according to the action information included in the input / output definition, and
A determination step for determining the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific step, and
A processing method including a screen transition diagram generation step that generates a screen transition diagram corresponding to each of the designated screens used in the generated program according to the transition configuration determined by the determination step. An information processing device program that generates a program to be executed in a Web system according to the input / output definitions corresponding to the screens displayed on the client device used in the Web system.
The information processing device
A specific means for specifying the input / output definition of the transition destination according to the action information included in the input / output definition, and
A determination means for determining the transition configuration in the reference input / output definition according to the input / output definition of the transition destination specified by the specific means, and
A program for functioning as a screen transition diagram generation means for generating a screen transition diagram corresponding to each of the designated screens used in the generated program according to the transition configuration determined by the determination means.

Images