JP2020024724A - Information processor, method for controlling information processor, and program - Google Patents

Abstract

To provide a mechanism which can generate a screen transition diagram by which the current screen transition state can be easily confirmed even while an application is being developed.SOLUTION: There is generated a list screen which can identify the connection between a screen as a transition source and a screen as a transition destination, using information on a screen definition used to generate an application using plural screens. This allows generation of a screen transition diagram by which a current screen transition state can be easily confirmed even while an application is being developed.SELECTED DRAWING: Figure 12

Description

  The present invention relates to an information processing device, a control method for the information processing device, and a program.

  2. Description of the Related Art In recent years, the use of business applications on the Web has been rapidly progressing within a company so that business can be performed without installing a special application on a client terminal. In such business application development sites, development tools that can easily create Web applications without programming are used in order to solve development skills shortages and personnel shortages. When such a development tool is used, a Web application can be automatically generated only by defining basic design information utilizing business and design know-how, even if the user does not have knowledge of a programming language.

  By the way, such a business application is designed to prepare multiple screens and transition from one screen to another, but it is necessary to create a screen transition diagram 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 the screen transition diagram is required. For example, Patent Document 1 discloses an operation by a system user. A screen transition diagram generation method for generating a screen transition that associates a transition source screen with a transition destination screen based on transition information indicating a transition from a screen included in a source code of an accepted screen to another screen is disclosed. ing.

JP 2012-108607 A

  By the way, during the development of a Web application, the specification of the screen transition is often changed during the development, and a screen transition diagram that allows the user to visually recognize the state of the screen transition even during the development. Is required.

  However, in the method of Patent Document 1, since the screen transition diagram is generated based on the operation by the system user, it can be said that it is difficult to confirm the state of the screen transition under development.

  In view of the above problems, an object of the present invention is to provide a mechanism that can generate a screen transition diagram that can easily confirm the current screen transition state even during the development of an application.

  In order to achieve the above object, the present invention stores definition information including screen information for identifying a screen, display items displayed on the screen, and transition destination screen information corresponding to the display items. An information processing apparatus comprising: a storage unit that performs an application using a plurality of screens based on the definition information stored in the storage unit; Screen information of the screen, acquisition means for acquiring the screen information of the transition destination corresponding to the display items displayed on the screen, using the screen information and the screen information of the transition destination acquired by the acquisition means, A transition screen generating unit that generates a list screen that can identify a connection between the object indicating the transition source screen and the object indicating the transition destination screen.

  In this way, by generating a list screen that can identify the connection between the screen of the transition source and the screen of the transition destination based on the information used when generating the application, even if the application is under development, A screen transition diagram that allows the user to easily confirm the screen transition state can be generated.

FIG. 1 is a diagram illustrating an example of a system configuration of a Web application automatic generation system (information processing system). FIG. 2 is a diagram illustrating a hardware configuration of a development terminal 101, a server 102, and a user terminal 103. FIG. 4 is a diagram for describing a functional configuration for creating a screen transition diagram of a Web application. FIG. 4 is a diagram for describing an example of a database definition 111. FIG. 4 is a diagram for describing an example of a data model definition 112. FIG. 4 is a diagram for explaining an example of a business process definition 113. FIG. 4 is a diagram for describing an example of an input / output definition 114. FIG. 3 is a diagram for explaining an application definition 110. 9 is a flowchart illustrating a flow when automatically generating a Web application. It is a flowchart for demonstrating the flow at the time of drawing a screen transition diagram. It is a figure showing the example of a screen which performs display setting of a screen transition action. It is an example of a screen transition diagram. It is an example of the screen transition diagram to which a memo was added. It is an example of a mode of adding the name of the memo of the screen transition diagram. It is a figure explaining a mode that an input-and-output definition is added via a screen transition diagram. It is a figure explaining a mode that an action definition is added via a screen transition diagram. It is an example of a screen transition diagram to which an input / output definition and an action definition are added. FIG. 10 is a diagram for explaining an example of an added input / output definition. FIG. 11 is an example of a screen transition diagram when a transition source screen and a transition destination screen are the same in a plurality of action definitions. FIG. 9 is an example of a screen transition diagram when there are many input / output definitions. FIG. 7 is a diagram illustrating an application definition screen on which hierarchical drawing or transition number drawing can be performed. It is a filter property setting screen of the application definition. 9 is a flowchart for explaining a flow when performing hierarchical drawing. It is an example of the screen transition diagram drawn hierarchically. It is a flowchart for demonstrating the flow at the time of performing transition number drawing. It is an example of the screen transition diagram in which the transition number is drawn.

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

  FIG. 1 is a diagram illustrating a system configuration of a Web application automatic generation system (hereinafter, also referred to as an information processing system) according to the present embodiment. In the Web application automatic generation system according to the present invention, the development terminal 101, the server 102 (server device), and the user terminal 103 communicate with each other via a network 105 such as a LAN (Local Area Network) or a WAN (Wide Area Network). Are connected to enable data communication.

  The Web application is an application that can execute a business application used in a company on the Web, and can perform business without installing a special application on a client terminal. Used. The Web application system of the present invention is a system that can automatically generate such a Web application from the requirement definition information that designates such a Web application without programming. By using such a system, business applications on the Web can be easily developed in each company even if development skills are insufficient.

  The development terminal 101 shown in FIG. 1 is a terminal used by a developer when a Web application (program) is automatically generated, and a development tool for automatically generating a program is installed. The requirements are defined in advance in this terminal, and the Web application 130 (program) is generated by reading in the development tool and performing the automatic generation process.

  The server 102 holds and operates a Web application (program) generated by the development terminal 101 and is used to provide a business application as a production environment. Then, access to the Web application 130 (program) via the user terminal 103 is accepted. Then, data generated using the Web application is stored in the database 140.

  The user terminal 103 is generally a terminal used by a user who uses a business application in a production environment. By connecting to the server 102 using the terminal, the user can use a Web-based application.

  FIG. 2 is a diagram illustrating a hardware configuration of the development terminal 101, the server 102, and the user terminal 103.

  The CPU 201 generally controls each device and controller connected to the system bus 204.

  The ROM 202 or the external memory 211 (storage means) includes a BIOS (Basic Input / Output System) or an operating system program (hereinafter, OS) as a control program of the CPU 201, a development terminal 101, a server 102, and a user terminal. Various programs and the like, which will be described later, necessary for realizing the functions executed by 103 are stored. The RAM 203 functions as a main memory, a work area, and the like for the CPU 201.

  The CPU 201 implements various operations by loading programs and the like necessary for executing processing into the RAM 203 and executing the programs.

  The input controller (input C) 205 controls input from an input device 209 such as a keyboard or a pointing device such as a mouse (not shown).

  The video controller (VC) 206 controls display on a display such as the display 210. The type of the display is assumed to be a CRT or a liquid crystal display, but is not limited thereto.

  The memory controller (MC) 207 is an adapter for a hard disk (HD), a flexible disk (FD), or a PCMCIA card slot that stores a boot program, browser software, various applications, font data, user files, edited files, various data, and the like. The access to the external memory 211 such as a card-type memory connected via the PC is controlled.

  A communication I / F controller (communication I / FC) 208 connects and communicates with external devices via a network, and executes communication control processing on the network. For example, Internet communication using TCP / IP is possible.

  Note that the CPU 201 enables display on the display 210 by executing, for example, an outline font developing (rasterizing) process on a display information area in the RAM 203. Further, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the display 210.

  Various programs and the like used by the development terminal 101, the server 102, and the user terminal 103 of the present invention to execute various processes described below are recorded in the external memory 211, and are loaded into the RAM 203 as necessary. Thus, the program can be executed by the CPU 201.

  Further, definition files and various information tables used by the program according to the present invention are stored in the external memory 211.

  FIG. 3 is a diagram illustrating a configuration diagram of a Web application automatic generation system and a functional configuration of a generated application and the like.

  The development terminal 101 includes a repository definition unit (Web application definition unit) 1000, a Web application generation unit 120 including a source code holding unit 121 and a generation processing unit 122, and a screen transition generation unit 1100.

  The repository definition unit 1000 is an application that sets which of the database definition 111, the data model definition 112, the business process definition 113, the input / output definition 114, and the definition file to use when generating a Web application. It has a definition 110 and screen transition diagram filter information 1006 used when rendering the screen transition diagram.

  The screen transition generation unit 1100 includes a screen data extraction unit 1101 that extracts screen data 1102 from data of the repository definition unit 1000, and a transition data extraction unit 1103 that extracts transition data 1104 from data of the repository definition unit 1000. I have. Further, the screen transition generation unit 1100 has a data-component conversion unit 1108 that converts the transition information including the screen data 1102 and the transition data 1104 into component data 1109, and uses the component data converted here. The screen transition drawing unit 1110 generates a transition screen and draws (displays) it on the screen transition canvas. The screen transition generation unit 1100 is a component that stores external screen data 1106 (icon) for the user to arbitrarily add an external screen to the screen transition canvas and tag data 1107 that the user attaches to the screen transition canvas in a sticky manner. When the user receives a designation of dragging and dropping an external screen icon or a sticky icon displayed on the screen transition diagram palette 1202, the screen transition drawing unit 1110 has a pallet unit 1105. Data 1107 is also drawn on the screen drawing canvas. Here, the screen transition canvas refers to a drawing area 1201 in FIG. 12 for drawing a transition screen diagram displayed on the display 210 or the like.

  The server 102 holds the Web application 130 generated by the generation processing unit 122 of the development terminal 101, performs processing according to a request from the user terminal 103, and performs input processing input from the user terminal 103. Data or the like is stored in the database 140.

(Automatic generation of Web application)

  Next, a flow when a developer automatically generates a Web application on the development terminal 101 will be described with reference to FIGS. FIGS. 4 to 8 show examples of definitions set in advance by a developer such as a database definition 111, a data model definition 112, a business process definition 113, an input / output definition 114, and an application definition 110 stored in the repository definition unit 1000 of FIG. It is shown.

  FIG. 4 shows a database definition 111 that stores the settings of a server accessed by a Web application. As shown in FIG. 4, the database definition includes a code 401 of the server 102, a server name 402, connection URL information 403, a server type 404, a database name 405, and a user name required when the application accesses the database. 406 and a password 407 are defined.

  FIG. 5 shows a data model definition 112 defined as schema information. As shown in FIG. 5A, each data model definition is managed by giving a code 501 and a name 502, and a detailed definition is also defined. For example, in the code “PRODUCT”, an item 510 shown in FIG. 5B and an operation code 520 shown in FIG. 5C are defined in detail.

  FIG. 5B defines an item code 511, an item name 512, an item 513 for setting whether to permit NULL, a number of digits 514, and a data type 515 as items to be accepted on the database.

  The item code 511 is a code for uniquely specifying a data model item in the data model. The name 512 is a name arbitrarily set by the user for the data model item. This is set so that the user can easily specify the data model item. Item 513 is an item for setting whether or not to allow empty data to be registered in the data model item. The number of digits 514 sets the number of digits of data that can be registered in the data model item. The data type 515 is an item for setting the data type of the data model item. Specify the type of data, such as characters, numbers, dates, etc. In this example, data model items from “PRODUCT_ID” to “PRODUCT_STOCK” are defined for the data model “PRODUCT”. Each item defined here matches the column name of the table of the database to which the Web application connects.

  FIG. 5C shows an operation code in which an operation for the data model is set, and an operation code 521, a name 522 of the operation, and an operation type 523 are defined. That is, the content of the operation is defined for the table associated with the data model. Here, the product data registration operation having the operation code “REGIST” is defined as the operation type “INSERT”, that is, the data input by the user registration operation is inserted into the database. Have been.

  FIG. 6 shows a business process definition 113 for defining a business flow of a Web application. As shown in FIG. 6A, each business process definition is managed by assigning a code 601 and a name 602, and a detailed logic definition is also defined. The business process code 601 is used as a code for designating a call from an input / output definition described later. As a detailed logic definition, as shown in FIG. 6B, a control code 611, a data model code 612, a function code 613, a parameter 614, and a work code 615 are set.

  The control code 611 indicates the operation type of the business logic. “IN” in this example indicates storage of input data variables to the business process. The work code 615 corresponds to the variable. “CALL” in this example indicates that the content of the function code 613 held by the data model code 612 is called. At the time of the call, the contents of the parameter 614 are passed as an argument.

  For example, in the business process definition of the code “REGIST_BP” in FIG. 6A, the following processing is performed in the setting order of the control code 611. In this example, the input content of the Web screen is received with a control code “IN”, and the received data is defined as a work code “INPUT”. Next, an operation on the data model "PRODUCT" is defined by the control code "CALL". That is, (1) First, as “IN” control, input data is acquired from the data model code 501 of PRODUCT (DM product) in FIG. At this time, a code “INPUT” is given to the work code. Next, (2) the “CALL” control is set as the operation code of the data model definition of FIG. 5C, and the “INSERT” processing is performed by inputting the input data (work code “INPUT”) read by the “IN” control. ) Is defined in the business logic to be performed.

  FIG. 7 shows the input / output definition 114 of each display item arranged on the Web screen. The items set here are displayed on the display screen of the user terminal 103, and are used as screens used by the user in a production environment. As shown in FIG. 7A, each input / output definition is managed by adding a code 701, a name 702, an input / output type 703, and the like, and detailed item definitions are also provided. For example, in the code “PRODUCT_REGIST_IO” in FIG. 7A, the item type 711, item code 712, name 713, display 714, processing formula 715, and next input / output 716 (screen information) as a transition destination shown in FIG. , A data model code 718 and a data model item code 719 are defined. In the present embodiment, an example of “IO” indicating a normal input / output screen and “MENU” indicating a menu screen as the input / output type 703 is shown. , "EXPORT" to indicate an export screen, "IMPORT" to indicate an import screen, "MATRIX" to indicate a matrix screen, and to indicate a form print screen Various input / output types such as “PRINT_FILE” and “MOBILE” indicating a portable terminal screen can also be defined.

  The item code 712 is a code (screen information) that uniquely specifies an item in the input / output definition. The name 713 is a name that the user arbitrarily names the input / output item. Set for easy identification of input / output items. The display 714 is for setting whether to display the defined input / output items on the screen. When it is not displayed, it is not displayed on the screen, and the information is held as hidden data. The next input / output 716 sets an input / output code to which a transition is made after a button is pressed for an input / output item whose item type is set to action. That is, a transition from one screen to another screen is defined. The next input / output parameter 717 is parameter information to be transferred at the same time as a screen transition after a button is pressed, for an input / output item whose item type is set to action. The data model code 718 sets a data model code related to the input / output item. Similarly, a data model item code 719 sets a data model item code related to the input / output item.

  In this example, the item defined as the item type “IO input / output” is an input / output item (“field” for inputting data and displaying data). An item defined as the item type “A action” is an action item (“button” for calling a process and transiting a screen). The item code “REGIST_ACT” in this example is an action item. “REGIST_BP” is defined in the processing formula 715 of the action item “REGIST_ACT”. The action of “REGIST_BP” is a definition indicating that the business process “REGIST_BP” is invoked. The code of “PRODUCT_LIST_IO” is defined as the next input / output destination. That is, when a “registration” action is performed by the user on the product registration screen on the application, the action defined by the processing formula of “REGIST_BP” is executed, and then the screen is displayed on “PRODUCT_LIST_IO” defined as the next input / output 716. Transition is defined. That is, “PRODUCT_LIST_IO” is the display screen information of the transition destination.

  Further, in the code “MAIN_MANU” in FIG. 7A, as shown in FIG. 7C, “PRODUCT_REGIST_IO” is defined so as to correspond to the input / output 716 next to the item code 712 “TO_PRODUCT_ID”. “PROCUCT_LIST_IO” is defined to correspond to the next input / output 716 of the code 712 “TO_PRODUCT_NAME”. That is, when the user performs the “go to product registration page” action on the main menu screen of the application, the screen transitions to “PRODUCT_REGIST_IO”, and when the user performs the “go to product list page” action on the main menu screen, “ It is defined that the screen transitions to “PRODUCT_LIST_IO”.

  FIG. 8A is a diagram illustrating an application definition 110 that defines input / output definitions used when generating a Web application. Each application definition 110, code 801 and application name 802 are set, and an input / output definition used as an initial screen can be defined as an initial input / output code 803. That is, the input / output definition specified as the initial input / output code 803 is a screen specified as the top layer of the transition screen diagram. The code 801 is a code capable of uniquely specifying an application in the entire definition file (also referred to as a project) stored in the repository definition unit 1000. The application name 802 is a name that can be arbitrarily set by the user for the application.

  Further, the input / output definition to which the application definition 110 belongs is set for each code as shown in a belonging definition setting screen 810 in FIG. 8B. On the affiliation definition setting screen 810, an input / output list 811, an affiliation input / output list 812, a button 813 for displaying a screen transition diagram, an add button 814, and a delete button 815 are displayed.

  The input / output list 811 displays all input / output codes of the input / output definition 1004 stored in the project. By selecting a desired number of input / output codes and pressing an add button 814, the user can be assigned to the application code as an assigned input / output. When the additional processing is performed, the input / output code is displayed in the belonging input / output list 812. Further, the user can remove the affiliation by selecting the input / output code displayed in the affiliation input / output list 812 and pressing the delete button 815.

  FIG. 9 shows a requirement definition such as a database definition 111, a data model definition 112, a business process definition 113, an input / output definition 114, and an application definition 110 stored in the repository definition unit 1000 as shown in FIGS. 6 is a flowchart for describing a flow when automatically generating a Web application. Such processing is realized by the CPU 201 of the development terminal 101 reading and executing the stored control program.

  First, in S901, the CPU 201 of the development terminal 101 receives a specification of the application definition 110 for generating a Web application from a user (a receiving unit).

  Next, in S902, the CPU 201 of the development terminal 101 reads the database definition 111 from the repository definition unit 1000. In step S903, the data model definition 112 is read from the repository definition unit 1000. In S904, the business process definition 113 is read from the repository definition unit 1000. In step S905, the input / output definition 114 is read from the repository definition unit 1000.

  Since such a definition is described in the XML format, in S906, the CPU 201 of the development terminal 101 analyzes the structure of the XML file, and stores necessary definition contents as object data in the memory.

  In step S907, the CPU 201 of the development terminal 101 functions as the generation processing unit 122 in step S907, reads a preset source code template from the source code holding unit 121, and stores the definition in the memory in step S908. A source code file in which data is embedded in a source code template, that is, a Web application is generated.

  As described above, the Web application is automatically generated by using the predefined requirement definition and the source code. The developer saves the Web application generated in this manner in the server 102 and ends the work of developing the business application.

(Screen transition diagram drawing process)

<First embodiment>

  Next, a flow of a screen transition diagram drawing process performed by a Web application developer or the like to confirm a screen transition state based on a requirement definition defined in advance will be described with reference to FIGS. .

  In a business application generated by a Web application or the like as described above, a plurality of screens are prepared and designed to transition from a screen to another screen. In order to grasp the flow of work, it is often required to create a screen transition diagram that can grasp the transition of the screen, but it is very complicated to manually create such a screen transition diagram, so it is simple There is a need for a mechanism that can create screen transition diagrams.

  In the present embodiment, a method for automatically creating a screen transition diagram by using an input / output definition used when automatically generating a Web application will be described.

  FIG. 10 is a flowchart illustrating a screen transition diagram generation process performed by the development terminal 101 used when automatically generating a Web application. When such a screen transition diagram generation process is performed, a screen transition diagram drawing process is performed using the input / output definition currently defined in the repository definition unit 1000.

  Such processing is realized by the CPU 201 of the development terminal 101 reading and executing the stored control program.

  First, in S1001, when the CPU 201 of the development terminal 101 presses a button 813 for displaying a screen transition diagram as shown in FIG. 8B in a state in which an application is specified by the user, it is determined that a drawing instruction has been issued. Accept.

  In S1002, the CPU 201 of the development terminal 101 reads all the input / output definitions defined in the repository definition unit 1000, and loops the following S1003 to S1006 for all the input / output definitions.

  In S1003, the CPU 201 of the development terminal 101 determines whether the input / output definition belongs to the application specified by the user in S1001. Specifically, it is determined whether or not to belong by referring to the belonging input / output list 812 corresponding to the application as shown in FIG. If it is determined in S1003 that the application does not belong to the application, the processing proceeds to the next input / output definition loop without performing the subsequent processing. If it is determined in step S1003 that the user belongs, the process proceeds to step S1004, in which the CPU 201 of the development terminal 101 functions as the screen data extraction unit 1101, and extracts the code 701 and name 702 of each item from the input / output definition as screen data 1102. And save it to memory. The screen data extracted here is not limited to the code 701 and the name 702, but may be any other information as long as the information is to be displayed on a screen transition diagram so that the screen can be identified by the user.

  Next, in step S1005, all action definitions belonging to the input / output definition are extracted, and the process of step S1006 is looped for all actions. Specifically, it indicates that the item type 711 as shown in FIG. 7B is set to “A action”. For example, in the case of the input / output definition “PRODUCT_REGIST_IO”, the item codes “REGIST_ACT” and “B” are extracted as the action definition.

  In step S1006, the CPU 201 of the development terminal 101 functions as the transition data extraction unit 1103, and, among the action definitions, information on the item code 712, name 713, next input / output 716, and next input / output parameter 717 of the input / output item of the action. It is extracted as transition data 1104 relating to the transition and stored in the memory. The transition data is not limited to these data, and may include a condition for transition (not shown) and an authority to transition (not shown). The setting of the transition data can be performed using, for example, a display setting screen 1150 of a screen transition diagram as shown in FIG.

  When the loop for all input / output definitions is completed, the process proceeds to S1007, in which the CPU 201 of the development terminal 101 functions as the data-component conversion unit 1108, and the screen data 1102 saved in S1004 from the memory and the transition saved in S1006. The data 1104 (transition information) is read, and the data is converted into components. Specifically, the object is converted into an object as described with reference to FIG.

  Next, in S1008, the CPU 201 of the development terminal 101 determines whether there is the same transition data in the drawing source screen (transition source screen) and the transition destination screen. If it is determined that the same transition data does not exist, the process advances to step S1011 to perform a screen transition diagram drawing process on the drawing area 1201 displayed on the display 210 or the like.

  FIG. 12 shows an example of a screen transition diagram drawn by such processing. The example shown here is a screen transition diagram in a case where the case where the drawing process is performed using the example shown in FIG. 7 is used. The drawing area 1201 includes a screen object 1203 on which the “MAINMENU_IO” of the code 701 extracted as the screen data and the “Main Menu” with the name 702 are drawn, and a “PRODUCT_REGIST_IO” of the code 701 extracted as the screen data. A screen object 1205 on which the “product registration” of the name 702 is drawn, and a screen object 1207 on which the “PRODUCT_LIST_IO” of the code 701 extracted as the screen data and the “product list” of the name 702 are drawn Is done. The transition information extracted as the transition data is indicated by an arrow. More specifically, as shown in FIG. 7C, when an action having a name 713 “to product registration page” that is “A action” is performed in the input / output definition of “MAIN MANU”, a screen is displayed on “PROCUT REGIST_IO”. It is defined that a screen transition to “PROCUT_LIST_IO” is made when an action having a name 713 “to product list page”, which is “A action”, is performed. The arrow is displayed to extend. A name 713 is displayed as an object 1204 and an object 1208 near the arrow. That is, the action name 713 is displayed as an object (display item).

  Note that, in the present embodiment, an example in which objects are connected by arrows will be described. Furthermore, in the present embodiment, all the objects of the screen are shown by the same rectangular frame, but the display method of the objects may be different for each type of the input / output type 703 shown in FIG. Specifically, the display method can be changed by changing the shape, such as a rectangle or an ellipse, or by performing color coding. By dividing the display method according to the input / output type in this manner, the screen type on the screen transition diagram can be easily identified.

  Also, as shown in FIG. 7B, it is defined in the input / output definition of “PRODUCT_REGIST_IO” that a screen transition to “PRODUCT_LIST_IO” is performed when an action with the name “register” of “A action” is performed. Therefore, an arrow extending from the object 1205 to the object 1207 is displayed, and the registered object 1206 is displayed. Note that, in the input / output definition of “PRODUCT_LIST_IO”, “BACK” is defined, but this definition defines that the screen returns to the previous screen although the next input / output is not defined. If such a screen is defined to return, the screen is drawn so that arrows appear for all screen data objects connected to the corresponding object 1205. However, when the transition destination is specified from another screen with respect to the screen, the visibility is reduced when a plurality of arrows are drawn. Object 1204, which is drawn with an arrow having a different shape from the arrow in the case where the arrow is drawn.

  As described above, the information necessary to generate the transition screen is obtained from the input / output definition used when generating an application using a plurality of screens, and the object indicating the transition source screen and the object indicating the transition destination screen are obtained. By generating a transition screen that is a list screen that shows the connection, the user can visually and easily recognize the state of the screen transition.

  By the way, a screen transition diagram palette 1202 is provided near the drawing area 1201, and as shown in FIG. 13, an object 1212 of an external system screen irrelevant to the application and an object 1213 indicating a flow of transition to the external system screen 1212 It is also possible to create a tag object 1222 to be used as an annotation.

  With reference to FIG. 14, a flow of generating an external system screen object will be described. When the user drags and drops an item on the external system screen 1211 from the screen transition diagram palette 1202 to the drawing area 1201, a new external system screen creation screen 1231 as shown in FIG. 14 is displayed. When the user inputs an input code 1232 and a name 1233 to be displayed as objects and presses an OK button 1234, an object 1212 shown in FIG. 13 reflecting such a name is generated. Further, after the user specifies the item of the straight line 1251 from the screen transition diagram palette 1202, the object 1203 and the object 1212 are sequentially specified and connected by an arrow, and the name is input. As shown in FIG. Object 1213 is displayed. When the user drags and drops an item of the tag 1212 from the screen transition diagram palette 1202 to the drawing area 1201, a tag object 1222 is displayed in the drawing area 1201. The user can freely input characters to the tag object 1222.

  Also, the action object that can be generated in the drawing area 1201 is not limited to a straight line, and an object that avoids a right angle or overlap can also be selected.

  Next, using FIG. 15 to FIG. 18, items not defined in the input / output definition as shown in FIG. 7 are added to the drawing area 1201 (on the list screen), so that new items are added to the input / output definition. The flow of creating is described. When the user drags and drops an input / output item 1241 and a menu item 1245 of the input / output area 1240 from the screen transition diagram palette 1202 to the drawing area 1201, an input / output definition object 1242 and a new input / output definition as shown in FIG. A creation screen 1243 is displayed.

  When the user inputs an input / output code 1242 to be displayed as an object and a name 1243 and presses an OK button 1244, such a name is reflected on the object 1242. Further, when the user specifies the item of the straight line 1251 from the screen transition diagram palette 1202 and then connects the object 1203 and the object 1242 in order, a new action definition screen 1251 as shown in FIG. 16 is displayed. When the user inputs an action code 1252 and a name 1253 to be set as objects and presses an OK button 1254, an arrow from the object 1203 to the object 1242 as shown in FIG. Object 1255 is displayed.

  When a series of flows described with reference to FIGS. 15 to 17 is performed, a definition is added to the input / output definition 114 stored in the repository definition unit 1000. For example, when the user drags and drops the input / output item 1241 and gives the input / output code 1242 of “CUSTOMER_REG_IO” and the name 1243 of “customer registration”, one new screen of “CUSTOMER_REG” is generated. Therefore, one is added to the input / output definition shown in FIG. 7A, and the input / output definition becomes as shown in FIG. 18A. In this example, since the input / output item 1241 is dragged and dropped, the input / output type 703 becomes “IO”. However, when the menu item 1245 is dragged and dropped, the input / output type 703 becomes “MENU”.

  Further, when the item of the straight line 1251 is selected and connected to the “MAIN_MANU” and the “CUSTOMER_REG_IO” by a straight line, the transition from the “MAIN_MANU” screen is performed, and thus the “MAIN_MANU” screen shown in FIG. One item of input / output definition of “MAIN_MANU” is added. Specifically, the item (FIG. 15) input as the input / output code 1242 and the name 1243 and the item (FIG. 16) input as the action code 1252 and the name 1253 correspond to “TO_CUSTOMER_REG” of the input / output definition shown in FIG. Are added as item code 712, name 713, and next input / output 716.

  Further, one item is added to the belonging input / output list 812 set on the belonging definition setting screen 810 in FIG. 8B, and an item 820 “CUSTOMER_REG_IO customer registration” is added as shown in FIG. 18C. You.

  In this way, the drawing developer can easily add a new screen while checking the state of the screen transition in the screen transition diagram during development.

  Returning to FIG. 10, the description of the flowchart will be continued. If it is determined in S1008 that the drawing source screen and the transition destination screen have the same transition data (if the transition source screen and the transition destination screen have acquired a plurality of the same transition data), the processing proceeds to S1009. On the other hand, the CPU 201 of the development terminal 101 groups the same transition data, and loops the processing of S1010 for the group.

  In step S1010, the CPU 201 of the development terminal 101 sets a position where the transition arrow is drawn so that the transition arrow does not overlap. Specifically, positions that are separated at equal intervals are set. By setting in this way, even if there is the same transition data in the drawing source screen and the transition destination screen, the arrows overlap as shown in FIG. 19 when the screen transition diagram is rendered in S1011. It can be drawn without any. FIG. 19 shows a case where three actions of “update 1901”, “registration 1902”, and “delete 1903” are specified as the transition destination screen (next input / output 716) of the product registration object 1205 and the product list object 1207. FIG. The arrows are arranged so as to be spaced apart from each other so that visibility is not reduced.

<Second embodiment>

  In the first embodiment, an example in which a screen transition diagram is created using all input / output definitions used for a Web application has been described. However, in the second embodiment, a part of the input / output definitions used for a Web application is described. An example in which a screen transition diagram is created by using is described. Note that, in the present embodiment, description of the same parts as in the first embodiment will be omitted, and the description will focus on the features of the second embodiment.

  FIG. 20A shows an example in which nine input / output definitions are registered in the belonging input / output list 812. A Web application using a large number of screens is described in the first embodiment. When a screen transition diagram using all input / output definitions is created in the same manner as in the case of FIG. 20, a large number of objects are arranged as shown in a drawing area 1201 in FIG. It is feared that it will.

  For this reason, in the present embodiment, there are provided a hierarchical drawing mode for drawing a predetermined number of layers from the initial screen set by the initial input / output code, and a transition number drawing mode for drawing around a screen having a predetermined number of transitions or more. ing. In this way, by allowing the user to draw using a desired drawing mode, it is possible to generate a screen transition diagram according to the application without lowering the visibility.

  In such a hierarchical drawing mode and a transition number drawing mode, drawing can be instructed by using a hierarchical drawing button 821 and a transition number drawing button 822 provided on an assignment definition setting screen 810 shown in FIG.

  First, the hierarchical drawing mode will be described with reference to FIGS.

  In the example shown in FIG. 20B, nine screens from an object 2001 on the main menu screen to an object 2006 on the product category editing screen are displayed, but “main menu” → “product registration” → “product category list” There are four stages of transitions from "" to "commodity category editing". The main menu is called hierarchy level 1, and the product category editing is called hierarchy level 4. In order to increase the visibility of the screen transition diagram, the user can narrow down the hierarchy level so that the hierarchy level desired by the user is displayed.

  FIG. 22 shows a filter property setting screen 2201 displayed by pressing the filter property 823 in FIG. By inputting the hierarchy level filter value 2202 and pressing the setting button 2204, the user can set the hierarchy to be displayed by the user as the screen transition diagram filter information 1006 (store it in the memory). Specifically, by setting the hierarchy level to “3”, the objects of the input / output screen of the hierarchy level of 3 or less are drawn.

  The numeral 824 displayed beside the input code of the belonging input / output list 812 on the belonging input / output setting screen 810 in FIG. 21 indicates the number of layers from the main menu screen (the initial screen set by the initial input / output code). It is. Such a hierarchy is calculated from the input / output definition stored in the memory. If it is set so that an object of an input / output screen of a hierarchy level of 3 or less is drawn, a code having a number 824 of 3 or less is drawn.

  FIG. 23 is a flowchart for explaining the flow when performing hierarchical drawing. Such processing is realized by the CPU 201 of the development terminal 101 reading and executing the stored control program.

  First, in S2301, when the CPU 201 of the development terminal 101 presses the hierarchy drawing button 821 as shown in FIG. 21 in a state where the application is specified by the user, the CPU 201 accepts that a drawing instruction specifying the hierarchy has been issued.

  In S2302, the CPU 201 of the development terminal 101 reads all the input / output definitions defined in the repository definition unit 1000, and loops the following S2303 to S2306 for all the input / output definitions.

  In S2303, the CPU 201 of the development terminal 101 determines whether the input / output definition belongs to the application designated by the user in S2301. Specifically, it is determined whether or not to belong by referring to the belonging / input / output list 812 corresponding to the application as shown in FIG. If it is determined in step S2303 that the application does not belong to the application, the processing proceeds to the next input / output definition loop without performing the subsequent processing. If it is determined in S2303 that the user belongs, the process proceeds to S2304, in which the CPU 201 of the development terminal 101 functions as the screen data extraction unit 1101, and extracts the code 701 and name 702 of each item from the input / output definition as screen data 1102. And save it to memory.

  Next, in step S2305, all action definitions belonging to the input / output definition are extracted, and the processing in step S2306 described below is looped for all actions.

  In step S2306, the CPU 201 of the development terminal 101 functions as the transition data extraction unit 1103, and stores information of the item code 712, name 713, next input / output 716, and next input / output parameter 717 of the input / output item of the action in the action definition. It is extracted as transition data 1104 relating to the transition and stored in the memory.

  When the loop for all the input / output definitions is completed, the process proceeds to S2307, where the CPU 201 of the development terminal 101 functions as the data-component conversion unit 1108, and the screen data 1102 (display item) saved from the memory in S2304 and S2306 The stored transition data 1104 (transition information) is read.

  In step S2308, the CPU 201 of the development terminal 101 calculates a hierarchy level for each screen from the screen data read from the memory and the related transition data (layer identification means).

  In S2309, the CPU 201 of the development terminal 101 obtains the number-of-layers filter value set by the user on the filter property setting screen 2201 or the like in FIG. 22 from the memory (layer number storage unit).

  In step S2310, the CPU 201 of the development terminal 101 extracts screen data and transition data corresponding to the layer number filter value (layer level) acquired in step S2309 from the screen data and transition data read in step S2307 (layer determination). means).

  In S2311, the CPU 201 of the development terminal 101 converts the data into a component (object).

  The description of S2312 to S2315 is the same as S1008 to S1011 of the first embodiment, and thus the description is omitted.

  FIG. 24 shows a screen transition diagram drawn in this manner. The screen object of the input / output definition with the hierarchy level of 4 or more is not drawn, but the screen object which is the input / output definition up to the drawing level 3 is drawn. When it is desired to view mainly the screen close to the initial screen set by the initial input / output code, the screen transition state can be confirmed with good visibility by setting the drawing in this way. In this embodiment, the initial screen set by the initial input / output code is the main screen, that is, the hierarchy level 1, but the main screen can be appropriately set on the filter property setting screen 2201 as shown in FIG. Hierarchical drawing may be performed centering on the set hierarchical level screen.

  Next, the transition number drawing mode will be described with reference to FIGS. 20, 21, 25, and 26.

  In the example shown in FIG. 20B, nine screens from the object 2001 on the main menu screen to the object 2006 on the product category editing screen are displayed, but it can be seen that the number of transition arrows differs for each screen. . For example, the product registration screen 2003 is associated with three transition arrows from the object 2001 on the main menu screen, the transition arrow to the object 2004 on the product list screen, and the transition arrow to the object 2005 on the product category list screen. On the other hand, the product category list screen 2005 has five transition arrows. The number of transition arrows related to (connected to) the screen in this way is called a transition number. In order to increase the visibility of the screen transition diagram, the user can cause the screen transition diagram to be drawn around a screen having a large number of transitions that the user wants to display.

  FIG. 22 shows a filter property setting screen 2201 displayed by pressing the filter property 823 in FIG. The user can set the number of transitions that the user wants to display by inputting the transition number filter value 2203 and pressing the setting button 2204. Specifically, by setting the transition number filter value to “6”, the transition number filter value is stored as screen transition diagram filter information 1106. By performing a drawing process using the filter value, a screen transition diagram is drawn around a screen to which six or more transition arrows are connected.

  The number 825 displayed beside the input code of the belonging input / output list 812 on the belonging input / output setting screen 810 in FIG. 21 is the number of transition arrows connected to the input / output screen. That is, it indicates the total of the number of actions transitioning from another screen and the number of actions transitioning to another screen. Such a transition number is calculated from the input / output definition action stored in the memory. When the setting is made so that the screen of the object of the input / output screen having the number of transitions of 6 or more is drawn as the center, the numeral 825 is drawn around the screen of 6 or more. When there are a plurality of six or more screens, a plurality of screens may be drawn simultaneously or one of them may be selected.

  FIG. 25 is a flowchart for explaining the flow when rendering the transition number. Such processing is realized by the CPU 201 of the development terminal 101 reading and executing the stored control program.

  First, in S2501, when the CPU 201 of the development terminal 101 presses the transition number drawing button 822 as shown in FIG. 21 in a state where the application is specified by the user, the CPU 201 accepts that a drawing instruction specifying the number of transitions has been issued. .

  In step S2502, the CPU 201 of the development terminal 101 reads all input / output definitions defined in the repository definition unit 1000, and loops the following steps S2503 to S2506 for all input / output definitions.

  In step S2503, the CPU 201 of the development terminal 101 determines whether the input / output definition belongs to the application specified by the user in step S2501. Specifically, it is determined whether or not to belong by referring to the belonging / input / output list 812 corresponding to the application as shown in FIG. If it is determined in step S2503 that the application does not belong to the application, the processing proceeds to the next input / output definition loop without performing the subsequent processing. If it is determined in step S2503 that the user belongs, the process proceeds to step S2504, in which the CPU 201 of the development terminal 101 functions as the screen data extraction unit 1101, and extracts the code 701 and name 702 of each item from the input / output definition as screen data 1102. And save it to memory.

  Next, in step S2505, all action definitions belonging to the input / output definition are extracted, and the process of step S2506 is looped for all actions.

  In step S2506, the CPU 201 of the development terminal 101 functions as the transition data extraction unit 1103, and stores information on the item code 712, name 713, next input / output 716, and next input / output parameter 717 of the input / output item of the action in the action definition. It is extracted as transition data 1104 relating to the transition and stored in the memory.

  When the loop for all input / output definitions is completed, the process proceeds to S2507, in which the CPU 201 of the development terminal 101 functions as the data-component conversion unit 1108, and the screen data 1102 saved in S2504 from the memory and the transition saved in S2506. The data 1104 is read.

  In S2508, the CPU 201 of the development terminal 101 calculates the value of the number of transitions for each screen from the screen data read from the memory and the related transition data (transition number specifying means).

  In S2509, the CPU 201 of the development terminal 101 acquires from the memory (transition number storage unit) the transition number filter value 2203 set by the user on the filter property setting screen 2201 or the like in FIG.

  In step S2510, the CPU 201 of the development terminal 101 extracts screen data and transition data corresponding to the transition number filter value 2203 acquired in step S2509 from the screen data and transition data read in step S2507 (transition number determination unit). .

  In step S2511, the CPU 201 of the development terminal 101 converts the data into components (objects).

  The description of S2512 to S2515 is the same as S1008 to S1011 of the first embodiment, and a description thereof will be omitted.

  FIG. 26 shows a screen transition diagram drawn in this manner. It is drawn centering on a screen object whose transition number is 6 or more. The screen object having the number of transitions less than 6 displays its own object, but does not display the subsequent transition arrow or the screen. When it is desired to view a screen having a desired number of transitions or more at the center, the screen transition state can be confirmed with good visibility by drawing in this manner. In the present embodiment, an example has been described in which a screen to which transition arrows having a set value or more are connected is described. However, a screen to which transition arrows having a set value or less (less than the set value) are connected may be drawn. .

  The present invention is, for example, possible as an embodiment as a system, an apparatus, a method, a program, a storage medium, or the like. Specifically, the present invention may be applied to a system including a plurality of devices. You may apply to the apparatus which consists of three apparatuses.

  The present invention also includes a software program for realizing the functions of the above-described embodiments, which is supplied directly or remotely to a system or an apparatus. The present invention also includes a case where the information processing apparatus of the system or the apparatus reads out and executes the supplied program code to achieve the above.

  Therefore, the program code itself installed in the information processing apparatus for realizing (executing) the functional processing of the present invention in the information processing apparatus also realizes the present invention. That is, the present invention includes the computer program itself for realizing the functional processing of the present invention.

  In this case, as long as it has the function of the program, it may be in the form of an object code, a program executed by an interpreter, script data supplied to the OS, or the like.

  Examples of a recording medium for supplying the program include a flexible disk, a hard disk, an optical disk, a magneto-optical disk, an MO, a CD-ROM, a CD-R, and a CD-RW. Further, there are a magnetic tape, a nonvolatile memory card, a ROM, a DVD (DVD-ROM, DVD-R), and the like.

  As another method of supplying the program, a browser on a client computer is used to connect to a homepage on the Internet. The computer program of the present invention or a compressed file including an automatic installation function can be supplied from the home page by downloading the file to a recording medium such as a hard disk.

  Also, the present invention can be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. In other words, the present invention also includes a WWW server that allows a plurality of users to download a program file for implementing the functional processing of the present invention on the information processing device.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and downloaded to a user who satisfies predetermined conditions from a homepage via the Internet to download key information for decryption. Let it. Then, it is also possible to execute the encrypted program by using the downloaded key information and to install the program on the information processing apparatus to realize the present invention.

  The functions of the above-described embodiments are implemented when the information processing apparatus executes the read program. In addition, the OS or the like running on the information processing apparatus performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written to a memory provided in a function expansion board inserted into the information processing device or a function expansion unit connected to the information processing device. Thereafter, based on instructions of the program, a CPU or the like provided in the function expansion board or the function expansion unit performs part or all of actual processing, and the functions of the above-described embodiments are also realized by the processing.

  It should be noted that the above-described embodiment is merely an example of the embodiment for carrying out the present invention, and the technical scope of the present invention should not be interpreted in a limited manner. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features.

101 Development Terminal 102 Server 103 User Terminal 130 Web Application 1100 Transition Screen Generation Unit

Claims (10)

Storage means for storing definition information including screen information for identifying the screen, display items displayed on the screen, and transition destination screen information corresponding to the display items,
A generation unit configured to generate an application using a plurality of screens based on the definition information stored in the storage unit,
Acquisition means for acquiring, from the storage means, screen information of a screen used in an application and screen information of a transition destination corresponding to a display item displayed on the screen,
Transition screen generation that generates a list screen that can identify a connection between an object indicating a transition source screen and an object indicating a transition destination screen using the screen information and the transition destination screen information acquired by the acquisition unit. Means,
Information processing device having   The information processing apparatus according to claim 1, wherein the transition screen generating unit displays the object indicating the transition source screen and the object indicating the transition destination screen so as to be connected by a line.   The transition screen generation unit, when the acquisition unit acquires a plurality of pieces of display information in which the transition source screen and the transition destination screen are the same, generates a list screen so that lines connecting the objects do not overlap. The information processing apparatus according to claim 2, wherein:   4. The information processing apparatus according to claim 1, wherein the transition screen generating unit also displays information of a display item on a list screen. 5. On the list screen generated by the transition screen generating means, receiving means for receiving addition of an object,
The information processing apparatus according to claim 1, further comprising: an adding unit that adds screen information corresponding to the object received by the receiving unit to the storage unit.   2. The image processing apparatus according to claim 1, wherein the receiving unit is capable of receiving screen information of the object whose addition has been received, a display item displayed in the screen information, and screen information of a transition destination corresponding to the display item. 6. The information processing apparatus according to 5. Layer specifying means for specifying a layer from a screen used as a main screen in an application based on the definition information stored in the storage means;
Among the screen information used in the application, a layer number storage unit that stores the layer number to be displayed on the list screen,
A hierarchy determining unit that determines an object to be displayed on the list screen by using the number of layers stored in the number-of-layers storage unit and the layer specified by the layer specifying unit;
The information processing apparatus according to claim 1, wherein the transition screen generation unit generates the list screen using the object determined by the hierarchy determination unit. Based on the definition information stored in the storage unit, a transition number specifying unit that specifies a transition number for each screen,
Among the screen information used in the application, a transition number storage unit that stores a transition number to be displayed on the list screen,
Using the number of transitions stored in the number-of-transitions storage means and the number of transitions specified by the number-of-transitions specifying means, further comprising a number-of-transitions determining means for determining an object to be displayed on the list screen,
The information processing apparatus according to claim 1, wherein the transition screen generation unit generates the list screen using the object determined by the transition number determination unit. A storage unit for storing definition information including screen information for identifying the screen, display items displayed on the screen, and transition destination screen information corresponding to the display items, the storage unit storing the definition information; Generating means for generating an application using a plurality of screens based on the defined information, and a control method of the information processing apparatus,
An acquisition step of acquiring, from the storage unit, screen information of a screen used in an application and screen information of a transition destination corresponding to a display item displayed on the screen;
Using the screen information acquired in the acquiring step and the screen information of the transition destination, generating a transition screen that can identify a connection between an object representing the transition source screen and an object representing the transition destination screen Process and
A control method having: A storage unit for storing definition information including screen information for identifying the screen, display items displayed on the screen, and transition destination screen information corresponding to the display items, the storage unit storing the definition information; Generating means for generating an application using a plurality of screens based on the defined information, a program executable by an information processing apparatus,
The information processing device,
Acquisition means for acquiring, from the storage means, screen information of a screen used in an application and screen information of a transition destination corresponding to a display item displayed on the screen;
Using the screen information acquired by the acquisition unit and the screen information of the transition destination, generating a transition screen that can identify a connection between an object representing a transition source screen and an object representing a transition destination screen means,
A program characterized by functioning as a program.

Images