Information processing system, processing method and program thereof

Abstract

To provide a mechanism for easily generating a screen transition diagram of a screen displayed in an execution environment of a Web system.SOLUTION: Provided is an information processing device for generating a program to be executed in a Web system in accordance with an input / output definition corresponding to a screen displayed on a client device used in the Web system, comprising: identifying means for, in accordance with action information included in the input / output definition, identifying an input / output definition of a transition destination; determination means for, in accordance with the input / output definition of the transition destination identified by the identifying means, determining transition configurations in an input / output definition to become a reference; and screen transition diagram generation means for, in accordance with the transition configurations determined by the determination means, generating a screen transition diagram corresponding to each of specified screens to be used in a generated program.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] Screen transition diagram of display Information processing system The present invention relates to a processing method and a program thereof. [Background technology]

[0002] In recent years, business applications are rapidly being converted to the Web so that business can be carried out without installing special applications on client terminals. In the development of such business applications, development tools that allow easy creation of Web applications without programming are being used to solve the lack of development skills and manpower. By using such development tools, even if you do not have knowledge of programming languages, you can automatically generate Web applications by simply defining basic design information using business and design know-how.

[0003] By the way, such web applications are designed to have multiple screens and transitions from one screen to another, and a screen transition diagram may be created to understand the overall business flow.

[0004] Creating such screen transition diagrams manually is cumbersome, so there is a demand for a system that can create screen transition diagrams automatically.

[0005] In particular, when developing a Web application, the specifications of screen transitions often change during development, and Patent Document 1, for example, discloses a technology for generating screen transition diagrams that allow users to visually recognize the state of screen transitions even during development. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2016-173721 A Summary of the Invention [Problem to be solved by the invention]

[0007] However, since a Web application has many screens, displaying a screen transition diagram can become complicated and difficult to view.

[0008] Furthermore, when a Web application is executed, the user operates the application via a screen, so a screen transition diagram based on that screen is desirable; however, the technology in Patent Document 1 displays a screen transition diagram centered on screens with a predetermined number of transitions or more, which is unsuitable for the environment in which Web applications are executed.

[0009] Therefore, the object of the present invention is to Yu For users, circle Easy-to-understand screen transition diagram display The purpose of this study is to provide a mechanism for this. [Means for solving the problem]

[0010] a diagram display control means for controlling to display a screen transition diagram showing a transition relationship between a transition source screen and a transition destination screen of an application; The above Showing transition relations mark Related to Object of display Control to Object Representation A control means; The above Object In response to receiving instructions to 、 The Object Related to mark an item display control means for controlling to display items to be passed from the transition source screen to the transition destination screen of the transition relationship indicated by the item display control means; of Preparation It is characterized by the above. Effect of the Invention

[0011] According to the present invention, a more suitable screen transition diagram can be generated. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing a system configuration according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration applicable to each device in the present embodiment. [Diagram 3] FIG. 2 is a diagram showing an outline of processing in the program development device 101. [Figure 4] FIG. 13 is a diagram showing an outline of processing after the processing of the program development device 101. [Diagram 5] 13 is a flowchart showing an example of an entire Web application and screen specification document generation process. [Figure 6] FIG. 13 is a diagram illustrating an example of a definition structure. [Figure 7] 13 is a flowchart illustrating an example of a process for generating a screen specification document. [Figure 8] 13 is a flowchart illustrating an example of a search information creation process. [Figure 9] 13 is a flowchart illustrating an example of a screen list information creating process. [Figure 10] 13 is a flowchart illustrating an example of a screen specification information generating process. [Figure 11] 13 is a flowchart illustrating an example of a screen item specification information creating process. [Figure 12] 13 is a flowchart showing an example of a screen transition diagram creating process. [Figure 13] FIG. 11 is a diagram illustrating an example of application settings. [Figure 14] FIG. 13 is a diagram illustrating an example of an input / output definition. [Figure 15] FIG. 13 is a diagram showing an example of an input / output layout definition screen. [Figure 16] FIG. 11 is a diagram illustrating an example of setting information of a hierarchical level. [Figure 17] 1A and 1B are diagrams illustrating an example of a screen transition diagram and data of the transition diagram. [Figure 18] FIG. 11 is a diagram showing an example of a screen transition diagram when an icon is operated. [Figure 19] FIG. 13 is a diagram showing an example of a screen specification document. [Figure 20] 13 is a flowchart showing an example of a display control process in a screen specification document. [Figure 21] FIG. 2 is a diagram illustrating an example of a functional configuration showing characteristics of the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[0015] Program development device 101 defines screen layouts and database search instructions, etc., according to operations by a developer. Program development device 101 alone may accept input from the developer and have program development server 102, described later, perform actual program generation processing and application generation processing, or program development device 101 alone may process program generation and application generation.

[0016] In this embodiment, the application generated by the program development device 101 is a Web application, but this is not limited to this, and the application may not be an application that uses communication via Web technology, such as an application that runs on an information processing device such as a mobile phone, smartphone, or tablet, or embedded software.

[0017] Program development servers 102a to 102b (information processing devices) develop programs according to instructions of a developer inputted by program development device 101. Program development server 102a may be placed in network 106 such as a LAN, and program development server 102b may be placed on the Internet or on the cloud.

[0018] The database servers 103a-103b (information processing devices) are databases used by developed applications, and may be used for checking operation during development in the present invention. For example, the database server 103 for use by a developer may be configured as the same device as the program development device 101, or may be placed in a network 106 such as a LAN (database server 103a). It may also be placed on the Internet or on the cloud (database server 103b). In addition, 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.

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

[0020] The application clients 104a to 104b (information processing devices) are user input terminals that operate application programs developed by the program development device 101 in cooperation with the application server 105. They may be located within a network 106 such as a LAN (application client 104a), or may be located on the Internet or on the cloud (application client 104b). They may also be information processing devices such as mobile terminals.

[0021] FIG. 2 is a block diagram showing an example of each hardware configuration applicable to 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.

[0022] In FIG. 2, a CPU 201 comprehensively controls each device connected to a system bus 204 .

[0023] The ROM 203 or the external memory 211 also stores an operating system (OS), which is a control program for the CPU 201, and programs for implementing various functions of information processing devices, such as servers, clients, and devices, which will be described later.

[0024] The RAM 202 functions as a main memory, a work area, a temporary save area, and the like for the CPU 201.

[0025] The input controller 205 controls input from an input unit 209. In an information processing device, examples of the input unit 209 include a keyboard and a pointing device such as a mouse.

[0026] The output controller 206 controls the display of the output unit 210. As the output unit 210, for example, a CRT or a liquid crystal display can be used.

[0027] The external memory controller 207 controls access to an external memory 211 that stores a boot program, various applications, font data, user files, edit files, printer drivers, etc. In addition, various tables and parameters for implementing various functions of each server, client, device, etc. 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, a smart media, etc.

[0028] A communication I / F controller 208 executes a process for controlling communication with external devices via a network.

[0029] A program 212 for implementing 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 required.

[0030] Next, basic processing in this embodiment will be described with reference to the configuration diagrams of Figures 3 and 4. Details of the processing that characterizes this embodiment will be described with reference to the flowcharts of Figures 5, 7 to 12, and 20 (particularly Figure 12).

[0031] 3 is a configuration diagram showing an overview of the processing of program development device 101. Program development device 101 is a device intended to automatically generate a Web application based on a definition file defined by a developer who develops the Web application. 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. In addition to the above, it also has a hierarchical level setting unit 415 and a screen transition diagram generation unit 439 as features of this embodiment.

[0032] The repository definition section 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, an application resource file 411, a document resource file 412, a header / footer file 413, a related document 414, and a hierarchy level setting 415. These files are input and created by a developer via a Web application development tool. That is, the repository definition section 401 manages, as input / output definition information, input definition information that defines items input to a program as arguments and output definition information that defines items output from the program as processing results.

[0033] Next, a description will be given of the Web application generation unit 416. Information generated by the Web application generation unit 416 is stored in the external memory 211.

[0034] The Web application generation unit 416 analyzes the repository definition unit 401 using a repository definition analysis unit 417, and generates a Web application 443 consisting of compiled Java code 444 and HTML / JSP / JavaScript 445 in a source code compilation unit 419 via a Web application code generation unit 418 (Java is a registered trademark).

[0035] The repository definition analysis section 417 reads 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 section 401 and analyzes them.

[0036] That is, Web application generation unit 416 is an example of a means for storing rules for generating a program used in a Web application.

[0037] The Web application generation unit 416 generates source code (JSP) in a 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 imported and a compiled file is generated in a source code compilation unit 419. The source code compilation unit 419 then deploys the compiled file to an application server. The source code, compiled file, and deployed data are collectively referred to as program data.

[0038] More specifically, the generated source code is roughly divided into server and client source codes. The server source code is compiled to generate a compiled file, while the client source code is not compiled and is placed as a file on the program development device 101. This file is used for deployment to the application server 105.

[0039] Also, a Java program (Java is a registered trademark) is generated for the server, which is compiled immediately after generation into a class file, and the class file is deployed. For the client, JSP / JavaScript / CSS is generated, which is deployed as is without being compiled.

[0040] The deployed module is a 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 rules for generating a program used in a Web application. For example, source code is generated according to predetermined rules.

[0041] Next, a description will be given of the screen specification document generating unit 420. Information generated by the screen specification document generating unit 420 is stored in the external memory 211.

[0042] A screen specification document generation unit 420 analyzes a repository definition unit 401 by a repository definition analysis unit 421. The screen specification document generation unit 420 generates a screen specification document 448 consisting of HTML / CSS / JavaScript 449 and an image file 450 via 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, a cover generation unit 429, a header / footer generation unit 430, and a screen transition diagram generation unit 439 (Java is a registered trademark).

[0043] The screen transition diagram generating unit 439 has a screen transition data extracting unit 440 that extracts data necessary for the screen transition diagram, a screen block generating unit 441, and a screen transition diagram layout composing unit 442.

[0044] At that time, the screen transition diagram layout configuration unit 442 reflects the layout to the screen list generation unit 422, the screen specification generation unit 423, the screen HTML generation unit 424, the screen item specification generation unit 425, and the search function generation unit 426 based on 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, and further reflects the decoration of the entire document in the screen specification document 448 using built-in design information 437 and user-created design information 438 via the document theme management unit.

[0045] Further, the language-specific document replacement processing unit 432 sets language-specific files in the cover generating unit 429 and the header / footer generating unit 430 .

[0046] That is, the screen specification document generating unit 420 uses the input / output definition 403 to generate a document that explains the definition (screen) of the Web application.

[0047] FIG. 4 is a block diagram showing an outline of the processing performed by the application server 105, the Web server 107, and the application client 104. As shown in FIG.

[0048] The application server 105 is a server that deploys the files generated by the Web application generation unit 416 and executes a Web application 443. The Web application 443 includes compiled Java code 444 and HTML / JSP / JavaScript 445 files (Java is a registered trademark). It also links to a database 446.

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

[0050] An example of the screen specification document displayed on the application client 104 is shown at 1900 in FIG.

[0051] In this embodiment, the application server 105 and the Web server 107 are separate from each other, but they may be configured to run in the same housing.

[0052] 5 is a diagram showing an example of a flowchart of the entire process of generating a Web application and a screen specification document. Note that each step of the following flowchart is executed by the CPU 201 of each device.

[0053] In step S500, program development device 101 receives an input of a definition for automatic generation of a Web application. Specifically, for a Web application (project) to be developed, the application code, name, application type, etc. are set in application setting 1300 in Fig. 13.

[0054] For this Web application (project), data model definitions, input / output definitions, and business process definitions are set. These definitions are set arbitrarily by the user on the setting screen that automatically generates the Web application, but they may also be configured to load definitions that have been generated in advance.

[0055] Also, in the belonging input / output list 1301, it is set which input / output definitions are to be attached (used).

[0056] The input / output definition is defined using the data set in Figures 14 and 15. Also, the hierarchical level of the screen transition diagram to be displayed in the screen specification document is set in advance, and the setting information of 1600 in Figure 16 is stored. In this embodiment, the hierarchy is set to one level, as shown in 1601.

[0057] In step S 501 , when the program development device 101 accepts a Web application generation instruction from the user, it reads the application definition 402 of the repository definition section 401 stored in the external memory 211 into the RAM 202 .

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

[0059] 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 section 401.

[0060] We will now explain how to generate the input / output definition 403. As described above, the setting of the input / output definition 403 itself is performed in advance, such as in step S500. First, on the input / output layout definition screen 1500 in Fig. 15, objects (fields and action buttons) are placed on the screen editor by drag-and-drop operations or the like.

[0061] Furthermore, for the action button, a condition is set in 1501 in Fig. 15. In 1502, a transition screen (definition of the next input / output) when the action button is pressed is set.

[0062] An example of the input / output definition corresponding to Fig. 15 is 1403 in Fig. 14. In 1403 in 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 a separate record.

[0063] The input / output definitions for each screen are shown as 1400 to 1403. Note that, in addition to the screen definition, the next input / output settings can also set definitions related to import and export processing.

[0064] In 1404, by setting the identification information of "(at) NODOC" for the input / output definition, it is possible to control so that a screen specification document is not generated individually. Although a screen specification document is not generated, it is displayed as an object in the screen transition diagram. "(at) NODOC" will be explained below as "NODOC".

[0065] In this embodiment, a diagram showing the structure of the set definition is 600 in FIG. 6, and a structure corresponding to 1400 to 1403 is 601.

[0066] The definition corresponding to the action button has values ​​such as item type, item code, name, next input / output, etc. For the next input / output, the screen (definition) to which the action will move next is set. In this embodiment, the screen transition diagram is color-coded by item type in particular, and the transition destination is determined by the next input / output to generate the screen transition diagram.

[0067] 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 section 401. The business process definition 405 is set in advance in step S500. The business process definition 405 defines the flow of processing received data. For example, it defines logic for checking for duplication of input data and registering it. The business process definition is also a known technique in the development of Web applications, so a description thereof will be omitted.

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

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

[0070] In step S507, the screen specification document generation unit 420 of the program development device 101 generates a screen specification document 448. The repository definition analysis unit 421 analyzes the read definition and stores it in memory, and each generation unit references it as appropriate. In addition, the layout configuration unit 427 lays out each component of the document created by each generation unit to configure a screen specification document.

[0071] The process of generating the screen specification document will be described in detail in Fig. 7, but an image of the generated screen specification document is 1900 in Fig. 19. The generated screen specification document is saved in association with the corresponding input / output definition code (e.g., PRODUCT_REGIST_IO, etc.).

[0072] Here, the screen specification document in FIG. 19 will be explained.

[0073] Reference numeral 1901 denotes a search function, which is capable of searching for and displaying inputs and outputs that contain a specified character string from the screen specification document.

[0074] Reference numeral 1902 denotes a list of screen specification documents that can be displayed. The list is displayed in correspondence with the list of inputs and outputs designated in 1301. When the user operates (clicks, etc.), the screen specification document for that input and output is displayed in the right pane.

[0075] A screen specification area 1903 displays the attributes set in the input / output definition.

[0076] Reference numeral 1904 denotes a screen HTML area, which displays the screen image of the input / output definition in HTML.

[0077] Numeral 1905 denotes a screen item specification area. It displays a list of attributes of input / output items corresponding to the screen. The attributes are displayed corresponding to "1" to "6" in 1904.

[0078] Reference numeral 1906 denotes a screen transition diagram area. The source and destination of the transition of the input and output of the document being displayed are displayed in a screen transition diagram. The generation of this screen transition diagram will be described in detail with reference to FIG.

[0079] A related document area 1907 displays links to related documents.

[0080] 7 is a diagram showing an example of a flowchart for generating a screen specification document. Note that each step of the following flowchart is executed by the CPU 201 of the device.

[0081] In step S701, the output filter management unit 431 reads the document filter definition 409. The output filter management unit 431 stores document filter information in memory, and the information is appropriately referenced by various generating units.

[0082] The document filter determines, for example, the attributes (items) and input / output types (IO, MENU, DIALOG) to be displayed in 1900 in Fig. 19, and can be set by the developer as desired. This filters the information displayed in 1900 in Fig. 19.

[0083] In step S702, the header / footer generation unit 430 checks whether or not there is a header / footer file 413. If there is a header / footer file 413, in step S703, the header / footer generation unit 430 creates a header / footer. The header / footer here is not shown in 1900 in FIG. 19, and for example, in addition to 1900, a header section and a footer section can be written in JSP. The header section is a section that displays, for example, a company logo. Also, the footer section is a section that displays, for example, a copyright.

[0084] In step S704, search function generation section 426 creates search information. Details will be described with reference to the flowchart in FIG.

[0085] In step S705, screen list generating section 422 creates a screen list. Details will be described with reference to the flowchart in FIG.

[0086] The process from step S706 to step S719 is repeated for the number of input / output definitions. In this embodiment, since there are three input / output definitions (main menu, product list, and product registration) as shown in FIG.

[0087] In step S707, the screen specification document generating unit 420 checks whether or not "NODOC" is specified in the input / output definition. If so, the screen specification document for that input / output definition is not output, and processing moves to the next input / output definition.

[0088] The "NODOC" designation is specified in 1404 and is managed in memory for each piece of input / output definition information. 1404 is a screen image diagram in which "NODOC" is designated in the input / output definition.

[0089] In step S708, the screen specification document generation unit 420 inquires of the output filter management unit to check whether the input / output type (MENU, IO, etc.) of the input / output definition is set as an output target. It is assumed that the developer has set in advance whether to set it as an output target.

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

[0091] In step S709, the screen list generating unit 422 outputs a screen list based on the information created in step S705. Specifically, this is to output HTML information to be displayed in 1902.

[0092] In step S710, screen specifications generating unit 423 creates and outputs screen specifications. The screen specifications creation and output process will be described with reference to the flowchart in FIG.

[0093] In step S711, screen HTML generation unit 424 creates and outputs screen HTML. Data of 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 input / output layout definition screen 1500, and a number is assigned to each item.

[0094] In step S712, screen item specifications generating section 425 creates and outputs screen item specifications. The screen item specification creation and output process will be described with reference to the flowchart in FIG.

[0095] In step S713, the related document generating unit 428 checks whether the related document 414 is set. If it is set, the process proceeds to step S714, and if it is not set, the process proceeds to step S715.

[0096] In step S714, the related document generating unit 428 creates link information for the related document and outputs it to the HTML file.

[0097] In step S715, screen transition diagram generating unit 439 creates and outputs a screen transition diagram. The screen transition diagram creation and output process will be described with reference to the flowchart in FIG.

[0098] In step S716, the header / footer generating unit 430 determines whether or not a header / footer has been created in step S702. If a header / footer has been created, the process proceeds to step S717, and if not, the process proceeds to step S718.

[0099] In step S717, header / footer generating unit 430 outputs the created header / footer to the HTML file.

[0100] In step S718, search function generating section 426 outputs to an HTML file based on the information created in step S704.

[0101] In step S720, cover page generation unit 429 determines whether cover page file 410 has been set. If cover page file 410 has been set, the process proceeds to step S721. If cover page file 410 has not been set, the process ends.

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

[0103] 8 is a diagram showing an example of a flowchart for creating search information. Note that each step of the following flowchart is executed by the CPU 201 of the device.

[0104] Search function generator 426 repeats the processes from step S801 to step S805 for the number of input / output definitions.

[0105] In step S802, it is determined whether or not "NODOC" is specified in the input / output definition. If "NODOC" is specified, the process proceeds to step S804. If "NODOC" is not specified, the process proceeds to step S803. If "NODOC" is specified, search information for that input / output is not created, and the process proceeds to processing of the next input / output definition.

[0106] In step S803, an inquiry is made to the output filter management unit 431 to determine whether the input / output type (see 1400) of the input / output definition is set as an output target. If it is not set as an output target, search information for that input / output is not created, and processing proceeds to the next input / output.

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

[0108] 9 is a diagram showing an example of a flowchart for creating screen list information. Note that each step of the following flowchart is executed by CPU 201 of the device.

[0109] The screen list generating unit 422 repeats the process from step S901 to step S905 for the number of input / output definitions.

[0110] In step S902, it is determined whether or not "NODOC" is specified in the input / output definition. If "NODOC" is specified, the process proceeds to step S905, and if "NODOC" is not specified, the process proceeds to step S903. If "NODOC" is specified, screen list information (corresponding to 1901) for that input / output definition is not created, and the process proceeds to the next input / output definition.

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

[0112] In step S904, screen list information corresponding to the input / output definition is created. Specifically, a part is generated based on the code and name (see 1400) of the input / output definition. A link to the generated screen specification document is added to this part, and pressing the part makes it possible to obtain and display the target screen specification document.

[0113] 10 is a diagram showing an example of a flowchart for creating screen specification information. Note that each step of the following flowchart is executed by CPU 201 of the device.

[0114] The screen specification generating unit 423 repeats the process from step S1001 to step S1004 for the number of attributes of the input / output definition.

[0115] In step S1002, the output filter management unit 431 is inquired of to determine whether the attribute of the input / output definition is set as an output target. If it is not set as an output target, the input / output attribute information is not created and the process moves to the next input / output attribute. If it is set as an output target, the process moves to step S1003.

[0116] In step S1003, input / output attribute information (corresponding to 1903) is generated.

[0117] In step S1005, screen specification generating unit 423 outputs the screen specification to an HTML file based on the input / output attribute information.

[0118] 11 is a diagram showing an example of a flowchart for creating screen item specification information. Note that each step of the following flowchart is executed by CPU 201 of the device.

[0119] The screen item specification generating unit 425 repeats the process from step S1101 to step S1110 for the number of items in the input / output definition.

[0120] In step S1102, it is determined whether or not "NODOC" is specified for the input / output item. If so, screen item specification information for that input / output item is not created, and processing moves to the next input / output item. If no such specification is specified, processing moves to step S1103.

[0121] In step S1103, it is determined whether the input / output item is a non-display item. If it is a non-display item, the process proceeds to step S1104.

[0122] In step S1104, the output filter management unit 431 is inquired of to determine whether or not the hidden item is set as an output target. If it is not set as an 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 set as an output target, the process moves to step S1105.

[0123] In step S1105, the output filter management unit 431 is inquired of to determine whether the input / output item type of the input / output item is set as an output target. If it is not set as an 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 set as an output target, the process moves to step S1106.

[0124] The processes from step S1106 to step S1109 are repeated for the number of input / output item attributes of the input / output items.

[0125] In step S1107, it is determined whether or not the attribute of the input / output item is set as an output target by inquiring of the output filter management unit 431. If it is not set as an output target, the input / output item attribute information is not created, and the process moves to the next input / output attribute. If it is to be output, the process proceeds to step S1108.

[0126] In step S1108, screen item specification information is generated.

[0127] In step S1111, screen item specification generating section 425 outputs screen item specifications to an HTML file based on the screen item specification information (corresponding to 1905).

[0128] 12 is a diagram showing an example of a flowchart for creating a screen transition diagram. Note that each step of the following flowchart is executed by the CPU 201 of the device.

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

[0130] In step S1202, input / output item codes and names (see FIG. 14) and screen data (corresponding to 1503 in FIG. 15) are extracted from the input / output definition.

[0131] In step S1203, all action definitions are extracted from the input / output definitions and saved in memory. An action definition is a definition whose item type is "Action." Note that an action (search, register, delete, cancel) is set to be automatically executed when an event occurs due to a user operation, etc.

[0132] The processes from step S1204 to step S1206 are repeated the number of times equal to the number of action definitions.

[0133] In step S1205, transition data is extracted from the action definition and saved in memory. The transition data is the setting value of the next input / output in FIG. 14. With reference to 1413, information is saved that can specify that when the registration button is pressed on the product registration screen, a transition to the product list screen will occur. With reference to 1411 and 1412, information is saved that can specify that the product registration screen will transition from the main menu and the product list screen. That is, this shows an example of a specification process that specifies the input / output definition of the transition destination according to the action information included in the input / output definition.

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

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

[0136] The data of the target screen and transition screen extracted by the screen transition data extraction unit 440 is The screen block generating unit 441 repeats the process from step S1210 to step S1214. This process is for generating data parts that are to be the transition source and transition destination used in the transition diagram.

[0137] In step S1211, the input / output that causes a screen transition is converted into a data part (block). When converting to a data part, a data part (rectangle object) that includes the code and name values ​​of 1400 is generated. When converting (generating) a data part, the input / output type of 1400 is color-coded so that it can be identified. Color information is defined in advance according to the type, but may be set arbitrarily by the developer.

[0138] In other words, the input / output definition corresponding to the screen specification document being generated serves as the basis, and the process can be described as generating objects corresponding to this basis input / output definition and the input / output definition of the transition destination or source.

[0139] In step S1212, it is determined whether or not "NODOC" is specified in the input / output definition. If it is specified, the link to the screen specification document of that input / output definition is not created, and the process moves to the next input / output. If it is not specified, the process moves to step S1213.

[0140] In step S1213, a link to the screen specification document generated corresponding to the input / output definition is created in the generated data part. Since the file name of the screen specification document and the like are generated in advance according to rules, it is possible to generate the link at this timing. Note that the link may be created when the processing in FIG. 7 is completed (when the screen specification document is completely generated).

[0141] When "NODOC" is specified, a screen specification document is not generated, but since it is desirable for the user to recognize it as a transition source or transition destination, it can be confirmed on the screen transition diagram.

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

[0143] Here, when transitioning to the same screen using action information (when the same next input / output exists), the action information is managed so that it can be displayed together in the screen transition diagram.

[0144] In step S1215, the screen transition diagram layout configuration section 442 sets the position where the data component is drawn. Specifically, when a screen specification document for a product registration screen (input / output definition for product registration) is being generated, the position is determined so that the data component of the product registration screen is in the center (position on the HTML5 canvas). With reference to Fig. 17, this is the position 1705. Information indicating the canvas is 1701. That is, this shows an example of a process for arranging an object corresponding to a reference input / output definition in a form that is easily recognized by the user.

[0145] In step S1216, the data parts are classified into groups of transition sources and transition destinations. 17, screen transition information is created by classifying the target screen and other screen data into source and destination groups as shown in 1702. 1706 is the source information and 1707 is the destination information.

[0146] The processes from step S1217 to step S1221 are repeated for each group classified in step S1216.

[0147] In step S1218, the positions (positions on the HTML5 Canvas) for drawing the data components of each group are set. The drawing positions are set to the left of the position determined in step S1215 for the source data component, and to the right for the destination data component. If there are multiple data components in the same group, they are positioned vertically. The drawing positions are determined according to predetermined rules.

[0148] In step S1219, the positions at which transition arrows representing transitions connecting each data component are drawn are set.

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

[0150] That is, the processes in steps S1210 to S1221 show an example of a determination process for determining a transition configuration in a reference input / output definition according to the input / output definition of the transition destination identified by the identification process.

[0151] Step S1222 draws a screen transition diagram on a canvas based on the settings for drawing the screen transition diagram set in steps S1215 to S1221. That is, this shows an example of a screen transition diagram generation process that generates screen transition diagrams corresponding to each of the specified screens used in the program to be generated according to the transition configuration determined by the determination process. This is also a process that generates a screen transition diagram so that action information can be arbitrarily displayed.

[0152] Here, we will explain the image when the screen transition diagram is drawn. Figure 17 shows the screen transition diagram and the data of the transition diagram.

[0153] Numeral 1700 is an image diagram of a screen transition diagram of an input / output definition (PRODUCT_REGIST_IO) that is the target of the screen specification document output. Numeral 1701 is HTML of the screen transition diagram portion. Numeral 1702 is screen transition information. Numeral 1703 is an icon that is displayed when an icon displayed on the screen transition diagram is clicked. Numeral 1704 is a data part of the transition destination determined from the setting value of the next input / output of 1413. Numeral 1705 indicates a data part of the input / output definition (PRODUCT_REGIST_IO) that is the target of the screen specification document output, and is placed in the center of the canvas.

[0154] Fig. 18 shows a screen transition diagram when the action information icon 1703 in Fig. 17 is operated. Fig. 18 is an image diagram of the screen transition diagram when the icon is operated. Reference numeral 1800 denotes an example of action information display, and reference numeral 1801 denotes an example of action information of a product list displayed when the icon is pressed. Reference numeral 1801 is information related to the action of 1412.

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

[0156] Furthermore, when there are a plurality of pieces of action information for the same transition destination, the information on the action displayed in 1801 is displayed on the screen transition diagram so that the plurality of pieces of action information can be displayed together.

[0157] In this way, it is possible to easily generate screen transition diagrams suitable for each specified screen (input / output definition) based on that screen. Since screen transition diagrams suitable for each screen specification document can be generated, it becomes possible for the user to easily understand what screen transitions will be caused by what actions based on the screen they are viewing.

[0158] 20 is a diagram showing an example of a flowchart of display control in a screen specification document. Note that each step of the following flowchart is executed by the CPU 201 of the device.

[0159] The application client 104 accesses the Web server 107 and acquires a screen specification document (HTML). The acquired screen specification document is displayed on the display unit. As described above, an example of the display of the screen specification document is shown in FIG.

[0160] In step S2001, an operation from the user is accepted via the screen list 1902. Specifically, a click on the screen specification document of the input / output definition to be displayed is accepted.

[0161] In step S2002, the screen specification document of the selected input / output definition is obtained from the Web server 107 according to the link in the screen list 1902, and is displayed (1908). Note that the link includes a code (e.g., PRODUCT_REGIST_IO) corresponding to the screen, and the screen specification document corresponding to this code is obtained.

[0162] In step S2003, it is determined 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.

[0163] In step S2004, the action information is displayed. A display example of the action information is shown in 1801. This action information is also acquired from the Web server 107.

[0164] In step S2005, it is determined whether a data part has been clicked. Specifically, it is determined whether a data part such as 1704 has been selected. If a data part has been selected, the process proceeds to step S2006. If no data part has been selected, the process ends (waits for an operation).

[0165] In step S2006, the code contained in the selected data part is obtained. For example, "PRODUCT_LIST_IO" in 1707 is obtained.

[0166] In step S2007, a 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. Also, the acquired screen specification document is displayed.

[0167] In this embodiment, the system is described as generating and constructing a Web application, but the system may also be a system that operates as a Web service that communicates in XML format.

[0168] Next, an example of a characteristic functional configuration in this embodiment will be described with reference to FIG.

[0169] The functional configuration in FIG. 21 is that of a program development device 101, but it may be a server as long as it is a device capable of program development. In other words, when using a system that can be developed in a cloud environment, it can be replaced with a server functional configuration. In other words, it can be called an information processing device that generates a program to be executed in a Web system. It is also 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 to be displayed on a client device used in the Web system.

[0170] The identifying unit 2101 is a functional unit that identifies a transition destination input / output definition in accordance with action information included in the input / output definition.

[0171] The determining unit 2102 is a functional unit that determines a transition configuration in a reference input / output definition in accordance with the input / output definition of the transition destination identified by the identifying unit 2101 .

[0172] The screen transition diagram generating unit 2103 is a functional unit that generates a screen transition diagram corresponding to each of the designated screens used in the program to be generated, in accordance with the transition configuration determined by the determining unit 2102 .

[0173] 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.

[0174] Moreover, the screen transition diagram generating unit 2103 is a functional unit that generates a screen transition diagram so that the action information acquired by the acquiring unit 2104 can be arbitrarily displayed.

[0175] In addition, the screen transition diagram generation unit 2103 is a functional unit that generates a screen transition diagram including multiple action information of the input / output definition, and when there is multiple action information for the same transition destination, so that the multiple action information can be displayed together.

[0176] The screen transition diagram generating unit 2103 is a functional unit that places an object that displays the action information at a position related to the transition in the screen transition diagram.

[0177] The document generation unit 2105 is a functional unit that generates a document that displays the specifications of the input / output definition in accordance with the input / output definition.

[0178] Moreover, the screen transition diagram generating unit 2103 is a functional unit that generates a screen transition diagram corresponding to the document generated by the document generating unit 2105 .

[0179] The screen transition diagram generating unit 2103 is a functional unit that generates an object corresponding to a reference input / output definition and a destination or source input / output definition.

[0180] The object is generated so as to be linked to a document generated by the document generation unit 2105, and is created by the screen transition diagram generation unit 2103. The object is generated so as to be identifiable according to the type of the input / output definition.

[0181] The reference input / output definition is an input / output definition used when generating a document in the document generation unit 2105, and the screen transition diagram generation unit 2103 generates a screen transition diagram in which objects corresponding to the reference input / output definition are arranged in a form that is easy for the user to recognize.

[0182] This concludes the detailed description of this embodiment.

[0183] In this embodiment, a screen transition diagram for each screen displayed in the execution environment of a Web application can be easily generated.

[0184] As described above, it goes without saying that the object of the present invention can be achieved by supplying a recording medium on which a program that realizes the functions of the above-mentioned embodiments is recorded to a system or device, and having the computer (or CPU or MPU) of that system or device read and execute the program stored on the recording medium.

[0185] In this case, the program itself read out from the recording medium will realize the novel functions of the present invention, and the recording medium on which the program is recorded will constitute the present invention.

[0186] Examples of recording media for supplying the program include flexible disks, hard disks, optical disks, magneto-optical disks, CD-ROMs, CD-Rs, DVD-ROMs, magnetic tapes, non-volatile memory cards, ROMs, EEPROMs, silicon disks, etc.

[0187] Furthermore, it goes without saying that the functions of the above-mentioned embodiments are not only realized by the computer executing a program it has read, but also includes cases where an OS (operating system) running on the computer performs some or all of the actual processing based on the instructions of the program, and the functions of the above-mentioned embodiments are realized through that processing.

[0188] Furthermore, it goes without saying that this also includes cases where a program read from a recording medium is written into a memory provided on a function expansion board inserted into a computer or a function expansion unit connected to a computer, and then a CPU or the like provided on the function expansion board or function expansion unit performs some or all of the actual processing based on the instructions of the program code, thereby realizing the functions of the above-mentioned embodiments.

[0189] The present invention may be applied to a system consisting of multiple devices, or to an apparatus consisting of a single device. Needless to say, the present invention can also be applied to a case where the object is achieved by supplying a program to a system or apparatus. In this case, the effect of the present invention can be enjoyed by the system or apparatus by reading a recording medium storing a program for achieving the present invention into the system or apparatus.

[0190] The program may be in the form of object code, program code executed by an interpreter, script data supplied to an OS (operating system), or the like.

[0191] Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or device can enjoy the effects of the present invention. Note that the present invention also includes configurations that combine the above-mentioned embodiments and their modified examples. [Explanation of symbols]

[0192] 101 Program Development Equipment 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

1. a diagram display control means for controlling to display a screen transition diagram showing a transition relationship between a transition source screen and a transition destination screen of an application; an object display control means for controlling to display an object related to the mark indicating the transition relation; an item display control means for controlling, in response to receiving an instruction for the object, to display an item to be passed from a transition source screen to a transition destination screen of the transition relationship indicated by a mark related to the object; An information processing system comprising:

2. The diagram display control means specifies the transition relationship based on definition information for generating a program for running the application.

2. The information processing system according to claim 1,

3. The diagram display control means specifies the transition relationship based on an input / output definition of a screen of the application.

3. The information processing system according to claim 1 or 2,

4. The diagram display control means specifies the transition relationship based on action information included in the input / output definition.

4. The information processing system according to claim 3,

5. The diagram display control means specifies the transition relationship based on identification information of a transition destination screen defined in the action information.

5. The information processing system according to claim 4,

6. The diagram display control means specifies the transition relationship based on identification information of the transition destination screen defined as definition information of the transition source screen.

6. The information processing system according to claim 1, wherein:

7. The diagram display control means generates a document including a specification of a screen of the application, and controls to display the screen transition diagram together with the generated document.

7. The information processing system according to claim 1, wherein:

8. The document includes a screen image of the application and information on screen items.

8. The information processing system according to claim 7,

9. The screen transition diagram includes information on at least one of a transition source screen and a transition destination screen, the transition number of which is up to a predetermined number based on each of two or more screens.

9. The information processing system according to claim 1, wherein:

10. The predetermined number is a number based on information input in advance by a developer of the application.

10. The information processing system according to claim 9,

11. The predetermined number of setting files is set by a reading unit. The diagram display control means controls to display the screen transition diagram based on the predetermined number set in the setting file.

11. The information processing system according to claim 9 or 10,

12. A generating unit for generating a program for operating the application is further provided, The diagram display control means controls to display a transition diagram showing a transition relationship between two or more screens displayed by executing the program generated by the generation means.

12. The information processing system according to claim 1, wherein:

13. The screen transition diagram is displayed on a client device that uses the application.

13. The information processing system according to claim 1, wherein:

14. The instruction is an instruction from a user who uses the application.

14. The information processing system according to claim 1,

15. a diagram display control step of controlling to display a screen transition diagram showing a transition relationship between a transition source screen and a transition destination screen of the application; an object display control step of controlling to display an object related to the mark indicating the transition relation; an item display control step of controlling to display an item to be passed from a transition source screen to a transition destination screen of the transition relationship indicated by a mark related to the object in response to receiving an instruction for the object; A processing method for causing an information processing system to process the above.

16. A program for causing a computer to function as each of the means of the information processing system according to any one of claims 1 to 14.

Images