JP2023075577A - Information processing apparatus, information processing method, and program - Google Patents

Abstract

To provide an information processing apparatus, an information processing method, and a program for easily creating a content that allows a customer to virtually see the execution of a plurality of events in application software for a real environment.SOLUTION: A method has: first selection means that selects any one of a plurality of screens displayed by application software; second selection means that selects any one of operations stored in association with the screen selected by the first selection means; and control means that performs control to generate instruction information instructing to sequentially execute a plurality of events including a first event for displaying the screen selected by the first selection means and a second event corresponding to the operation selected by the second selection means.SELECTED DRAWING: Figure 8

Description

The present invention relates to an information processing apparatus, information processing method, and program for virtually executing the operation of application software under development.

When creating application software for a customer, in order to understand the customer's needs, the application software is created through repeated meetings with the customer.

In particular, screens and operation procedures of application software are appropriately shared between customers and developers, and previews are repeated in order to match the image of the completed application software. Note that the application software may be abbreviated as an application hereinafter.

An effective means for previewing application software is a prototype developed application (prototype application).

A prototype application is an application for presenting production application software in the development stage to a customer, and is an application that allows screen transitions as if the production application software were running. The prototype application accepts customer-operated component operations (operations on screen components such as text input and GUI button depression), and performs screen transitions in the same manner as production application software. However, it does not search for data corresponding to component operations or output results, but displays preset output results. Since it does not search for data corresponding to operations on screen parts or output the results, the developer should check the image of the application software desired by the customer before generating business logic on the server side or in the production application software. can do. Since the customer and the developer can share the completed image of the production application software, it is possible to reduce discrepancies in the completed image between the two parties and reduce rework in development. In addition, when developing with MVP (Minimum Viable Product), the prototype application can obtain feedback from customers at an early timing, so it is possible to reduce development man-hours without spending man-hours on developing unnecessary functions. can contribute to

In addition to face-to-face explanations using the prototype application, where the human resources (developers, sales representatives, etc.) of the provider of the production application and the customer meet face-to-face, there are non-face-to-face situations where the human resources of the provider directly There are situations in which a prototype application is shown to a customer without any explanation. While the prototype application can be efficiently presented to the customer by not face-to-face and without explanation, the customer does not know how to operate the prototype application because there is no explanation from the provider's personnel if the prototype application is only distributed to the customer. It is also possible that they do not understand or that they do not fully understand. Therefore, when distributing the prototype application to the customer, it is conceivable to attach an explanatory document, or to provide an easy-to-understand video site or video application.

Japanese Patent Laid-Open No. 2004-100003 describes generalizing the function of an application for creating a replay moving image so that a replay moving image of a portion desired by the user can be created and viewed by other users.

JP 2014-106648 A

If it is possible to see the operation of the production application as a video as in Patent Document 1, the customer (the user who is provided with the production application) can understand how multiple events are executed in the application for this application. It is possible to understand in an easy-to-understand manner For example, after a first event of initial display of a screen, a second event of operation of a GUI button occurs, and screen transitions can be confirmed by watching a moving image. However, in the case of Patent Document 1, when creating a replay moving image of an arbitrary portion of an application, the replay moving image cannot be created unless the production application software is completed to an operable state. That is, during the development of the production application software, the server-side program and business logic in the production application software may not be completed, and it is not always possible to create a replay moving image. In other words, there is the problem that it is not possible to easily generate content that allows one to virtually see the execution of multiple events in production application software.

SUMMARY OF THE INVENTION Accordingly, it is an object of the present invention to facilitate the generation of content that allows users to virtually see the execution of multiple events in production application software.

The information processing device of the present invention includes:
first selection means for selecting one of a plurality of screens displayed by application software;
a second selection means for selecting one of the actions stored in association with the screen selected by the selection means;
a first event for displaying the screen selected by the first selection means;
Sequentially executing a plurality of events including: a second event corresponding to a specific process indicated by the action selected by the second selection means, the second event being performed without executing the specific process; and control means for controlling to generate instruction information for instructing.

According to the present invention, it is possible to easily generate content that enables virtual viewing of the execution of a plurality of events in production application software.

1 is a system configuration diagram according to an embodiment; FIG. 1 is a block diagram showing an example of a hardware configuration applicable as a program development device, an execution server, a database server, and a client device according to this embodiment; FIG. 10 is a flowchart of prototype application generation processing; 4 is a flowchart of prototype application execution processing; 9 is a flowchart of playback module generation processing; 9 is a flowchart of reproduction information definition reception processing; 4 is a flowchart of playback module execution processing; It is an example of a display concerning prototype application generation processing. It is an example of a display concerning prototype application generation processing. It is an example of a display concerning prototype application generation processing. It is an example of a display concerning a prototype application execution process. 4 is an example of a portion of a prototype application; 4 is an example of a portion of a prototype application; It is an example of a display concerning reproduction information definition acceptance processing. It is an example of the reproduction information definition generated by the reproduction information definition reception process. It is an example of a display concerning reproduction|regeneration module execution processing. It is an example of a display concerning reproduction|regeneration module execution processing.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
<First embodiment>
FIG. 1 is a system configuration diagram of this embodiment. This system includes a program development device 101 (an information processing device operated by a developer to generate a web application), an execution server 102 , a database server 103 and a client device 104 .

The program development device 101 defines screen layouts, database search instructions, and the like according to the developer's operation. The program development device 101 generates programs and applications.

In the present embodiment, the application software generated by the program development device 101 is a web application, but is not limited to this, and application software that operates on information processing devices such as mobile phones, smart phones, tablets, etc. It does not have to be application software, such as software, that utilizes communication by Web technology.

The execution server 102 executes application software developed by the program development device 101 . Also, it is possible to operate by connecting to the database server 103 .

The database server 103 is a database used by the developed application software, and may also be used for operation confirmation during development of the application software in this embodiment. For example, for use by developers, the database server 103 may consist of the same device as the program development device 101 and the execution server 102, or may be arranged in a network 105 such as a LAN.

The client device 104 (information processing device) is an end-user input terminal that operates an application program developed by the program development device 101 in cooperation with the execution server 102 . The client device 104 may be an information processing device such as a mobile terminal.

Any one of the program development device 101, the execution server 102, the database server 103, and the client device 104 may be arranged on the Internet such as a cloud, or several information processing devices may be arranged as one housing. good too.

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

In FIG. 2, a CPU 201 centrally controls each device connected to a system bus 204 .

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 realizing various functions of information processing apparatuses such as servers, clients, and apparatuses, which will be described later.

A RAM 202 functions as a main memory, a work area, a temporary save area, and the like for the CPU 201 .

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

If the input unit 209 is a touch panel, the user can give various instructions by pressing (touching with a finger or the like) an icon, cursor, or button displayed on the touch panel.

Also, the touch panel may be a touch panel, such as a multi-touch screen, capable of detecting positions touched by a plurality of fingers.

The output controller 206 controls the display of the output section 210 . Examples of the output unit 210 include a CRT, a liquid crystal display, and the like. It should be noted that the display of the notebook computer integrated with the main body is also included. Also, it may be a projector.

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

It should be noted that the CPU 201 enables display on the output unit 210 by executing outline font expansion (rasterization) processing to a display information area in the RAM 202, for example. Also, the CPU 201 enables a user's instruction with a mouse cursor or the like (not shown) on the output unit 210 .

A communication I/F controller 208 executes communication control processing with external devices via a network. For example, communication using TCP/IP is possible.

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

A procedure for generating a prototype application of Web application software (production application) will be described with reference to FIGS. 3 and 4 below. 3 and 4 are executed by the CPU 201 of the program development apparatus 101 executing a program recorded in the ROM 203 and developed in the RAM 202. FIG.

FIG. 3 is a diagram showing an example of a flowchart of a part related to prototype application generation processing in generation processing of web application software (hereinafter abbreviated as web application).

In S301, the CPU 201 of the program development apparatus 101 receives an input of the screen definition of the web application by the developer. This process is a process of receiving instructions from the user as to what kind of screen parts should be arranged (layouted) at what positions on the screen of the generated Web application and what kind of functions each screen part should have. The processing of S301 will be described with reference to FIG.

A component palette section 801 on the left side of the screen 800 in FIG. 8A is a list of components (GUI components) to be arranged on the screen, from which the user selects a GUI component to be arranged on the WEB application screen. A screen definition editor section 802 on the right side is an area for editing the display screen displayed on the screen of the Web application. FIG. 8 shows an example of generating a Web application that executes processing for registering a user ID and name in a database or the like.

For example, when the developer arranges the button icon 805 on the display screen of the Web application, the button component in the component palette section 801 is dragged and dropped as indicated by an arrow 803 and arranged. Similarly, a screen component layout example 804 is generated by arranging a text box 806 into which text can be input at the illustrated position. Note that the method of arranging screen components is not limited to the method of dragging and dropping from the component palette section 801 to the screen definition editor section 802, but also the method of moving already placed components, and the method of copying and pasting already placed components. may be Also, it may be possible to delete a part that has been placed once.

If there is a component including an action event (for example, the button icon 805) among the components arranged in the screen definition editor unit 802, the action for the button is registered. Specifically, when the button icon 805 is right-clicked or moused over for a predetermined period of time, an icon 811 is displayed. When the user clicks the displayed icon 811, a registration screen 812 (registration dialog) is displayed. In FIG. 8B, on the displayed registration screen 812, the user enters "Register" as the [Name] item, selects "Button" as the [Type] item from the drop-down menu, and selects "Next Screen" as the item. In this example, "user list screen" is selected from the down menu. In other words, the registration screen 812 of FIG. 8 is an example of registering the content that, when the button icon 805 with the name "registration" is pressed, the screen transitions to the "user list screen". An example of JSON data of the screen generated on this screen will be described with reference to FIG.

FIG. 12 is an example of the JSON data extracted from the screen of FIG. In the JSON code of FIG. 12, “instance003” surrounded by a frame 1204 is data representing the button icon 805 . In a frame 1201, a key "code" has a value "register" which means registration, and a key "name" has a value of "registration" entered on the registration screen 812 of FIG. 8B. "" and the key "nextUI" are set with "sampleUi002" (user list screen in the registration screen 812) indicating the next user list screen. A value corresponding to the key “actions” in the frame 1202 describes the processing to be executed when the button icon 805 is pressed in the production Web application. A value corresponding to the key "examples" in the frame 1203 describes the processing to be executed when the button icon 805 is pressed in the prototype application. In both cases, since the Web application is being created in the illustrated example, only the screen transition is set when the button icon 805 is pressed. Therefore, as shown in a frame 1205, "instance003" is set to "null" which does nothing when the key is "onClick". Returning to the description of the flowchart in FIG.

In S302 of FIG. 3, the CPU 201 of the program development apparatus 101 determines whether or not there is an input request for prototype data to be displayed on the screen when the prototype application is executed. The prototype data is data displayed on the web application screen when the prototype application is executed, and is values and diagrams preset by the developer as an example. In other words, prototype data is not data that is retrieved from a database or plotted from calculated data results as in a production environment. Prototype data is pre-populated or placed by a developer via an application development tool. In S302, if there is a request to input prototype data, the process proceeds to S303, and if there is no request to input prototype data, the process proceeds to S304. A screen display example when the user requests the input of prototype data will be described with reference to FIG. 8(c).

FIG. 8(c) is an example of a screen display when requesting input of prototype data. With the mouse over the button icon 805 on the screen 820, an icon 821a is displayed when the mouse is right-clicked or the mouse is over for a predetermined period of time. When the user clicks the displayed icon 821a, an option 821b is displayed. Option 821b is an option labeled "when clicked". By selecting and pressing (mouse clicking) the option 821b, an input request for prototype data is made. When the prototype data is input, when the human resources (developers, sales staff, etc.) on the side of providing the production application run the prototype application in a demonstration or the like, pressing the button icon 805 causes the prototype data to be displayed on the same screen. Alternatively, a screen displaying prototype data can be displayed on the transition destination screen. In this embodiment, an example in which prototype data is displayed on the transition destination screen (FIG. 9) will be described. Note that the same function as the icon 821a can also be performed by pressing the icon 822. FIG. When the icon 822 is pressed, the same option as the option 821b is displayed in the area 906 of FIG. 9A. Returning to the description of the flowchart in FIG.

In S303 of FIG. 3, the CPU 201 of the program development apparatus 101 generates a prototype displayed by the action specified in S302 (pressing the button icon, which is the action indicated by the selected option 821b, that is, "when clicked"). Accept data input. The process of accepting input of prototype data will be described with reference to FIGS. 9 and 10. FIG.

9 and 10 are screen examples for explaining the process of inputting prototype data. Since the next transition screen of the button icon 805 is not the user registration screen shown in the screen definition editor section 802 of FIG. The screen is switched to the screen 900 of FIG. 9A including a registrant list 902 (user list screen). Since the screen 900 is a screen for inputting prototype data, the title of the screen is changed from "parts palette" shown in the parts palette section 801 to "prototype settings" as shown in the prototype setting section 901 of FIG. 9(a). ing. The registrant list 902 is a transition destination screen (user list screen) that transitions when the button icon 805 is pressed, and is a screen generated in advance by the user. The registrant list 902 displays the IDs and names entered in the respective text boxes included in the screen component layout example 804 in FIG. 8A in a list format. The registrant list 902 includes an ID display area 903 , a name display area 904 and a registration date/time display area 905 . If multiple users are registered, they are displayed in a list format. The registrant list 902 corresponds to "sampleUi002" corresponding to the key "nextUi" in the frame 1201 in the JSON code of FIG.

In FIG. 9B, when the user wants to input prototype data, the item to be input (name display area 904 in the case of screen) is right-clicked or moused over for a predetermined time. Icons 911 and 912 are displayed accordingly. When the user clicks the displayed icon 911, the display is switched to the screen 920 shown in FIG. 9C, and a prototype data input dialog 921 is displayed. For example, as shown in the figure, by inputting a character string (value) "Noriyuki Tanigawa" in the prototype data input dialog 921 and pressing the OK button, it is registered as prototype data. The registered prototype data is displayed on the transition destination screen that is displayed in response to the action to be registered (pressing the button icon 805) when the prototype application is executed. As a result, for example, when the button icon 805 is pressed, a character string such as "Noriyuki Tanigawa" is displayed in the name display area 904 of the registrant list 902 of FIG. 10(a). As another example, a method for collectively inputting a plurality of prototype data will be described. When the user clicks the icon 912 in FIG. 9(b), the display is switched to that in FIG. 10(b). By inputting data in, for example, CSV format into an import field 1022 included in the prototype data list input dialog box 1021 and pressing an OK button 1024, the corresponding values can be registered as prototype data. Similarly, specification by file is also possible, and after pressing the icon 1023, an appropriate file can be selected and data can be input. An example of JSON code in which these prototype data are set will be described with reference to FIG.

FIG. 13 is an example of extracted JSON data after the input example shown in FIG. 10(b) has been entered. In the JSON code of FIG. 13, the value corresponding to the key "actions" in the frame 1302 describes the processing to operate and display in the production Web application. Data to be displayed when the prototype application is executed is registered in the value corresponding to the key “examples” in the frame 1301 , and data registered in the import column 1022 is registered in the frame 1301 .

FIGS. 11A and 11B show display examples when the generated prototype application is executed. The screen 1100 in FIG. 11A is a screen created by the operation of arranging components in the screen definition editor section 802 described above. A screen 1110 in FIG. 11B is a transition destination screen displayed in response to pressing of the registration button 1101 (the button corresponding to the button icon 805 described above) in FIG. It corresponds to list 902 . When the prototype application is running, regardless of whether or not data is entered in the ID input field 1102 and the name input field 1103 on the screen 1100 before transition, when the registration button 1101 is pressed, the screen 1110 in FIG. Registered prototype data 1111 is displayed. Prototype data 1111 is a display that reflects the values registered in the import column 1022 in FIG. 10B described above. Returning to the description of the flowchart in FIG.

In S304 of FIG. 3, the CPU 201 of the program development apparatus 101 determines whether or not there is a request (pressing of a save button (not shown)) to save the screen definition (arrangement of components, etc.) and prototype data. If there is a save request, the process proceeds to S305, and if there is no save request, the process proceeds to S306.

In S305, the CPU 201 of the program development apparatus 101 saves screen definition information and prototype data.

In S306, the CPU 201 of the program development device 101 determines whether a prototype application generation request has been received. If it is determined that a prototype application generation request has been made, the process proceeds to S307. On the other hand, if there is no prototype application generation request, the process transitions to S301.

In S307, the CPU 201 of the program development device 101 generates the source code of the prototype application. When generating the source code, the screen definition, screen transition definition, prototype data, etc. saved in S305 are read to generate the source code.

In S308, the CPU 201 of the program development device 101 compiles the source code generated in S507.

In S<b>309 , the CPU 201 of the program development device 101 deploys the prototype application compiled in S<b>508 to the execution server 102 . A prototype application is thus generated. Note that the generated program (prototype application) may be deployed as an SPA (Single Page Application) that runs on the client. From FIG. 4 onwards, an example of deployment as an SPA will be described. This completes the description of the flowchart in FIG.

Next, the flow of processing when the client device 104 executes the prototype application will be described with reference to FIG.

The flowchart in FIG. 4 shows the flow of processing that is started when a user accesses the prototype application generated by the processing in FIG. It should be noted that what is described as SPA below is the prototype application generated in FIG.

In S<b>401 , the CPU 201 of the client device 104 acquires the SPA deployed to the execution server and displays the SPA execution screen on the output unit 210 (display) of the client device 104 . As a result, the display as shown in FIG. 11A is performed.

In S402, the CPU 201 of the client device 104 accepts an action execution request from the user. Specifically, pressing of the registration button 1101 in FIG. 11A is accepted. At this time, the purpose of the user is to confirm the operation image for reproducing the image when using the production Web application. does not necessarily require user input.

In S403, the CPU 201 of the client device 104 determines whether or not the user has issued an action execution request. Specifically, it is determined whether the registration button 1101 in FIG. 11A has been pressed. If it is determined that there has been an action execution request (the registration button 1101 has been pressed), the process proceeds to S404, and if there is no action execution request from the user, the process returns to S402.

In S404, the CPU 201 of the client apparatus 104 determines whether the action execution request accepted in S402 involves screen transition. If it is determined that the action execution request accompanies screen transition, the process proceeds to S406, and if the action does not accompany screen transition, the process proceeds to S407.

In S405, the CPU 201 of the client device 104 displays a transition destination screen associated with the action execution request.

In S406, the CPU 201 of the client device 104 displays prototype data registered in the acquired SPA. A specific display example of the prototype data is the screen 1110, which is the transition destination screen described above with reference to FIG. 11(b). This is the end of the description of the flowchart in FIG.

Next, referring to FIG. 5, the flow of processing for generating a module (hereinafter referred to as a reproduction module) for displaying (reproducing) the prototype applications of the present embodiment in order by the program development apparatus 101 will be described. do. The generated playback module is a module that automatically and virtually sequentially executes a plurality of events. That is, when the reproduction module is executed, virtual execution of a plurality of events causes automatic screen transition like animation. Unlike the production environment, the virtual event execution outputs prototype data corresponding to the event without executing an event similar to the production environment. This process is a flowchart executed after the prototype application is generated in FIG.

In S501, the CPU 201 of the program development apparatus 101 executes reproduction information definition acceptance processing (processing for accepting reproduction information definition setting/editing) for generating a reproduction module. Details will be described later with reference to FIG. A reproduction information definition is instruction information for instructing the sequential execution of a plurality of events instructed by the user in the reproduction information definition acceptance process.

In S502, the CPU 201 of the program development apparatus 101 determines whether or not there is a request to save the reproduction information definition set or edited in S501. If there is a save request, the process transitions to S503, and if there is no save request, the process transitions to S504.

In S<b>503 , the CPU 201 of the program development device 101 saves the reproduction information definition in the execution server 102 .

In S504, the CPU 201 of the program development apparatus 101 determines whether or not there is a request to generate a reproduction module based on the saved reproduction information definition. If there is a reproduction module generation request, the process proceeds to S505, and if there is no reproduction module generation request, the process returns to S501.

In S505, the CPU 201 of the program development apparatus 101 generates the source code of the reproduction module corresponding to the saved reproduction information definition, compiles it in S506, and deploys it as SPA on the execution server 102 in S507. The generated reproduction module is generated so as to operate by referring to the reproduction information definition recorded in the execution server 102 .

Next, with reference to FIG. 6, the details of the reproduction information definition acceptance processing in S501 of FIG. 5 will be described. In the processing to be described later, "event" is a general term for things that change the screen due to execution of a generated playback module, and includes screen success, action, balloon display, and prototype data display.

In S601, the CPU 201 of the program development apparatus 101 reads the prototype application source code (including screen definition information, component information, screen transition information, and prototype data) generated in S307 of FIG. to display the playback information editing screen.

FIG. 14(a) shows a display example of a playback information edit screen (prototype operation record edit screen).

A UI definition selection area 1410 is an area that displays UI definitions (screens) defined in the prototype application or the corresponding application of the present application as options. At least one UI definition obtained from the source code of the prototype application is listed in the UI definition selection area. In the illustrated example, selection items 1411 to 1414 are displayed in the UI definition selection area 1410 . A selection item 1411 is “MENU”, which is an item for selecting a UI definition of a menu screen in which a plurality of menu items are defined in the production application. A selection item 1412 is "ML_QUERY", which is an item for selecting a UI definition of a screen for searching a mailing list address from a database or the like. A selection item 1413 is "MEMBER_LIST", which is an item for selecting a UI definition of a screen that displays a list of members of the participating mailing list. A selection item 1414 is "MEMBER_EDIT", which is a selection item of the UI definition of the screen for editing the members of the participating mailing list. The options displayed in the UI definition selection area 1410 are multiple options corresponding to multiple screens defined when the production application software is created.

The action selection area 1420 is an area that displays actions (operations) included in the UI definition selected in the UI definition selection area 1410 as options (selection items). By acquiring the UI definition of the prototype application in this way, it is possible to display a list of actions to be executed by the prototype application, and easily select an action to be described later. Each action represents a specific process to be performed in the production application.
The preview area 1430 is an area where a screen defined in the selected UI definition is displayed using GUI parts (display elements) defined in the selected UI definition. In addition, when speech balloons and value sets are registered in the playback order designation area 1440, these are also displayed on the screen defined in the UI definition so that it is possible to check how speech balloons and values are displayed. It has become.

The playback order designation area 1440 is: This is an area in which the events that are performed sequentially when the playback module is executed are arranged in order from top to bottom. The user can create a playback module that automatically executes the events in a desired order by arranging and registering the events to be executed by the playback module in the desired order in the playback order specification area 1440 from top to bottom. . Each event registered in the reproduction order designation area 1440 is held in the RAM 202 of the program development apparatus 101 and saved in the execution server 102 in response to a save instruction. The playback information definition 1500 in FIG. 15 and each event displayed in the playback order designation area 1440 correspond to each other. , respectively correspond to the frames 1502 to 1505 of . The playback information definition 1500 is instruction information for instructing the sequential execution of the screen access 1441 and the events 1442 to 1445 .

In S602 of FIG. 6, the CPU 201 of the program development apparatus 101 determines whether any option displayed in the UI definition selection area has been selected. If the UI definition option is selected by the user, the process proceeds to S603; otherwise, the process returns to S602 and waits for the UI definition to be selected.

In S<b>603 , the CPU 201 of the program development apparatus 101 acquires the action included in the UI definition selected in S<b>602 from the execution server 102 and displays it in the action selection area 1420 . More specifically, among the UI definitions of the production application, the actions included in the UI definition selected in S602 are acquired. In the example of FIG. 14A, "ML_QUERY" selected as the UI definition includes a search button, and an action (operation) of searching in response to clicking of the search button is defined. Therefore, in the action selection area 1420, an action selection item 1421 for initial display of the "ML_QUERY" screen and a search action selection item 1422 are displayed.

In S604, the CPU 201 of the program development apparatus 101 sets the UI definition selected in the UI definition selection in S602 (in the case of FIG. 14A, "ML_QUERY" in the selection item 1412) as screen access and stores it in the RAM. . The event corresponding to the screen access 1441 displayed in the reproduction order designation area 1440 is the event for displaying the selected UI-defined screen.

In S605, the CPU 201 of the program development apparatus 101 acquires from the execution server 102 the reproduction information definition recorded in association with the selected UI definition (the reproduction information definition in which the selected UI definition is registered as screen access). , is displayed as an event executed following the screen access 1441 in the reproduction order designation area 1440 according to the acquired reproduction information definition. If you have previously defined a play order associated with the selected UI definition. This will load a previously saved play order and allow you to make edits to it. If the reproduction information definition associated with the selected UI definition is not recorded in the execution server 102, it is newly created, and only the screen access 1441 is displayed in the reproduction order designation area 1440 at this timing. A preview area 1430 displays a preview of the GUI parts defined in the selected UI definition and the speech balloon and value set displayed in the reproduction order designation area 1440 .

In S606, the CPU 201 of the program development apparatus 101 displays the screen access editor 1450 to display the UI definition selected in S602.

In S607, the CPU 201 of the program development apparatus 101 determines whether the UI definition has been changed. If the UI definition has been changed, the process advances to step S603 to perform processing based on the changed UI definition. When another selection item is selected in the UI definition selection area 1410 or another UI definition is selected in the screen access editor 1450, it is determined that the UI definition has been changed. This makes it possible to define (set) playback information for another UI definition. If it is determined in S607 that the UI definition has not been changed, the process proceeds to S608.

In S<b>608 , the CPU 201 of the program development apparatus 101 determines whether or not an operation to add an event to the reproduction order designation area 1440 has been performed. The operation of adding an event is an operation of adding an action by selecting one of the selection items in the action selection area 1420 (clicking or dragging and dropping to the reproduction order designation area 1440), or pressing the add button 1446. shall be If there is an operation to add an event, the process proceeds to S609; otherwise, the process proceeds to S629.

In S<b>609 , the CPU 201 of the program development apparatus 101 determines whether the event addition operation determined in S<b>608 was an action addition operation. If the operation is to add an action, the process proceeds to S610; otherwise, the process proceeds to S611.

In S<b>610 , CPU 201 of program development device 101 adds the selected action to the tail end of the displayed (registered) event in reproduction order designation area 1440 . For example, by dragging and dropping the selection item 1422 of the action selection area 1420 to the reproduction order designation area 1440, the action "search" indicated by the selection item 1422 is added and displayed in the reproduction order designation area 1440 as an event 1445. .

If the addition operation of an event that is not an action, that is, pressing the add button 1446, the CPU 201 of the program development device 101 displays options to be added in S611. The options shall include "value set" and "balloon".

In S<b>612 , the CPU 201 of the program development apparatus 101 determines which of the options displayed in S<b>611 has been operated, “value set” or “balloon”. If "value set" is selected, proceed to S613; otherwise, that is, if "balloon" is selected, proceed to S621.

In S613, the CPU 201 of the program development apparatus 101 adds the "value set" event to the end of the displayed (registered) events in the reproduction order designation area 1440, and selects the added "value set" event. displayed. Because you can register multiple "value set" events in the playback order. Like the event 1442 shown, each value set is displayed with a serial number to identify it.

In S614, the CPU 201 of the program development device 101 displays the value set editor 1460 in the lower right portion of the edit screen (the area where the screen access editor 1450 is displayed in FIG. 14(a)). FIG. 14B shows a display example of the value set editor 1460 and the reproduction order designation area 1440 when the value set editor 1460 is displayed. FIG. 14B is a display example of a portion of the right side of the editing screen. A value set event 1442 is selected in the playback order designation area 1440, and a value set editor 1460 includes a target component setting field 1461 for selecting a target GUI component for which the value of the selected event 1442 is to be set. A value input field 1462 to be input and a delete button 1463 for accepting an instruction to delete the event of the value set being selected from the reproduction order designation area 1440 are displayed.

In S<b>615 , the CPU 201 of the program development apparatus 101 determines whether or not there is an operation to select a target component for setting a value. If there is an operation to select the target component, the process proceeds to S616; otherwise, the process proceeds to S617. The operation of selecting the target component is performed by selecting one of the options displayed in the pull-down menu displayed by operating the target component setting column 1461, for example. Before the user performs an operation to select a target component, any one of the GUI components included in the selected UI definition screen is selected by default (initial setting).

In S<b>616 , the CPU 201 of the program development apparatus 101 performs processing for changing the target part for setting the value in accordance with the operation of selecting the target part determined in S<b>615 . Specifically, the changed target part name is displayed in the target part setting field 1461 of the value set editor 1460, and the value that has already been input to the changed part is displayed in the value input field 1462. FIG. As for this value, the value recorded in the reproduction information definition illustrated in FIG. 15 is acquired and displayed. If the GUI component is a new GUI component for which data to be displayed as a value is not recorded in the reproduction definition information, the initial value of the value input column 1462 is blank.

In S617, the CPU 201 of the program development apparatus 101 determines whether or not there has been an operation of inputting a value in the value input field 1462 (an operation of inputting a value for the target component). If there is an operation to input a value, the process proceeds to S618; otherwise, the process proceeds to S619. A value is entered by, for example, selecting the value entry field 1462 and entering a character string using a keyboard or the like.

In S618, the CPU 201 of the program development apparatus 101 records (registers) the value input in the value input field 1462 in the reproduction information definition. Also, the input value is displayed on the target part displayed in the preview area 1430 . In the example of FIG. 14(b), "ML_ADDRESS" is selected as the target part, and "dev" is entered in the value input field 1462, so the information is displayed as in the frame 1502 of the reproduction information definition 1500 in FIG. be registered. Also, in the preview area 1430, the character string "dev" input in the value input field 1462 is displayed for the target GUI component 1431 ("ML address").

In S619, the CPU 201 of the program development device 101 determines whether or not the delete button 1463 has been pressed. If the delete button 1463 has been pressed, the process proceeds to S620; otherwise, the process proceeds to S608.

In S<b>620 , CPU 201 of program development device 101 deletes the selected value set from reproduction order designation area 1440 . At the same time, corresponding information is deleted from the reproduction information definition 1500 in FIG. As a result, screen transition corresponding to the deleted event is not performed when the playback module is executed.

In S621, the CPU 201 of the program development device 101 adds a "balloon" event to the end of the displayed (registered) events in the reproduction order designation area 1440, and displays the added "balloon" event in a selected state. do. This is because multiple "balloon" events can be registered in the playback order. Like event 1443 and event 1444 in the drawing, each speech balloon is displayed with a serial number to identify it.

In S622, the CPU 201 of the program development device 101 displays the value set balloon editor 1470 in the lower right portion of the edit screen (the area where the screen access editor 1450 is displayed in FIG. 14(a)). FIG. 14C shows a display example of the balloon editor 1470 and the reproduction order designation area 1440 when the balloon editor 1470 is displayed. FIG. 14C is a display example of a portion of the right side of the editing screen. A balloon event 1443 is selected in the playback order designation area 1440, and a target part setting field 1471 for selecting a target GUI part for displaying a balloon indicated by the selected event 1443 is displayed in the balloon editor 1470. . Also, a value input field 1472 for inputting a value and a delete button 1473 for receiving an instruction to delete the balloon event being selected from the reproduction order designation area 1440 are displayed. In this embodiment, an example has been described in which an event for displaying additional information (a character string entered in the value input field 1472) in the form of a speech bubble can be added to a GUI component. is not limited to Additional information may be displayed at the end of the leader line, or an annotation number may be added to write an annotation.

In S<b>623 , the CPU 201 of the program development device 101 determines whether or not there has been an operation to select a target component for displaying a balloon. If there is an operation to select the target component, the process proceeds to S624; otherwise, the process proceeds to S625. The operation of selecting the target component is performed by selecting one of the options displayed in the pull-down menu displayed by operating the target component setting column 1471, for example. Before the user performs an operation to select a target component, any one of the GUI components included in the selected UI definition screen is selected by default (initial setting).

In S<b>624 , the CPU 201 of the program development device 101 performs processing for changing the target part for displaying the balloon according to the operation of selecting the target part determined in S<b>623 . Specifically, the target part name after change is displayed in the target part setting field 1471 of the balloon editor 1470, and the value of the balloon that has already been input for the part after change is displayed in the value input field 1472 as the reproduction information of FIG. Read from definition and display. If the part has a newly added speech balloon, the initial value of the value input field 1472 is blank.

In S<b>625 , the CPU 201 of the program development device 101 determines whether or not there has been an operation to input a value in the value input field 1472 . If there is an operation to input a value, the process proceeds to S626; otherwise, the process proceeds to S627. A value is entered by, for example, selecting the value entry field 1472 and entering a character string using a keyboard or the like.

In S626, the CPU 201 of the program development apparatus 101 records or overwrites the value input in the value input field 1472 in the reproduction information definition used for generating the reproduction module. Also, the input value is displayed in a balloon displayed in the preview area 1430 (a balloon from the selected target part). In the example of FIG. 14(c), "ML_ADDRESS" is selected as the target part, and "Enter the ML address with prefix match" is entered in the value input field 1472. Therefore, the reproduction information definition 1500 of FIG. Information is registered as in a frame 1503 . Also, in the preview area 1430, the character string input in the value input field 1472 is displayed in the balloon 1418 displayed for the target GUI component 1431 (“ML address”).

In S627, the CPU 201 of the program development device 101 determines whether or not the delete button 1473 has been pressed. If the delete button 1473 has been pressed, the process proceeds to S628; otherwise, the process proceeds to S608.

In S<b>628 , CPU 201 of program development device 101 deletes the balloon selected from reproduction order designation area 1440 . Also, the corresponding balloon is deleted from preview area 1430 . At the same time, corresponding information is deleted from the reproduction information definition 1500 in FIG. As a result, balloons corresponding to deleted events are not displayed when the playback module is executed.

After shifting the process to S<b>629 , the CPU 201 of the program development apparatus 101 determines whether or not there is an operation to select the screen access 1441 of the reproduction order designation area 1440 . If the screen access 1441 is selected, the process proceeds to S630; otherwise, the process proceeds to S631.

In S630, the CPU 201 of the program development apparatus 101 displays the screen access 1441 of the reproduction order designation area 1440 in a selected state, and transitions to S606. Then, in S606, the screen access editor 1450 is displayed. That is, if screen access 1441 is selected while value set editor 1460 or balloon editor 1470 is displayed, screen access editor 1450 is displayed instead of value set editor 1460 or balloon editor 1470 .

In S<b>631 , the CPU 201 of the program development device 101 performs an operation of selecting the event of the value set from the events displayed in the reproduction order designation area 1440 and the GUI component displaying the value set displayed in the preview area 1430 . It is determined whether or not there has been any selection operation. If any operation has been performed, in S632, the event of the value set corresponding to the selection in S631 is displayed in a selected state in the reproduction order designation area 1440, and the process proceeds to S614. Then, at S614, the value set editor 1460 is displayed. That is, when the screen access editor 1450 or balloon editor 1470 is displayed and an event corresponding to a value set is selected, the value set editor 1460 is displayed instead of the screen access editor 1450 or balloon editor 1470 .

In S<b>633 , CPU 201 of program development device 101 determines whether an operation to select a balloon event or an operation to select a balloon displayed in preview area 1430 among the events displayed in reproduction order designation area 1440 has been performed. determine whether or not If any operation has been performed, in S634, the balloon event corresponding to the selection in S633 is displayed in a selected state in the reproduction order designation area 1440, and the process proceeds to S623. Then, in S623, the balloon editor 1470 is displayed. That is, when an event corresponding to a balloon is selected while screen access editor 1450 or value set editor 1460 is displayed, balloon editor 1470 is displayed instead of screen access editor 1450 or value set editor 1460 .

In S<b>635 , CPU 201 of program development apparatus 101 determines whether or not an action has been deleted from the events displayed in reproduction order designation area 1440 . If there is an operation to delete the action, the process transitions to S636; otherwise, the process transitions to S637. An operation to delete an action is, for example, an operation in which the user selects an action event in the playback order designation area 1440 with a mouse and presses [DEL] (delete key) or the like on the keyboard.

In S<b>636 , CPU 201 of program development apparatus 101 deletes the event of the target action from reproduction order designation area 1440 . At the same time, the corresponding event information is deleted from the reproduction information definition 1500 in FIG. For example, when the event 1445, which is the search action, is deleted in the reproduction order designation area 1440, the information within the frame 1505 of the reproduction information definition 1500 is deleted. After that, the process proceeds to S608.

In S<b>637 , CPU 201 of program development device 101 determines whether an operation to change the size and position of the balloon displayed in preview area 1430 has been received. If an operation to change the size or position of the balloon is accepted, the process proceeds to S638; otherwise, the process proceeds to S639. Specifically, for example, the user can select a balloon displayed in the preview area 1430 with the mouse and drag and drop the balloon with the mouse to change the display position of the balloon. This operation does not change the target GUI component from which the balloon is created. Also, by dragging and dropping the marks displayed at the four corners of the balloon displayed in the preview area 1430 with a mouse, the size of the balloon can be changed by enlarging or reducing it.

In S638, the CPU 201 of the program development device 101 changes the size and position of the selected balloon according to the operation accepted in S637. The changed size and position are recorded in the reproduction information definition 1500 . After that, the process proceeds to S608.

In S<b>639 , the CPU 201 of the program development device 101 determines whether or not an operation for rearranging the reproduction order (an operation for specifying the order) has been received. If there is a rearrangement operation, the process transitions to S640; otherwise, the process transitions to S640. The rearrangement operation is, for example, an operation in which the user drags and drops any of the events in the reproduction order designation area 1440 with the mouse to change the order of the events with other events. .

In S640, CPU 201 of program development device 101 rearranges the display positions of the events displayed in reproduction order designation area 1440 according to the operation received in S639. The changed order is recorded in the playback information definition 1500 (the "playback order" information is updated to the information in accordance with the changed playback order). After that, the process proceeds to S608. It is assumed that the first event (the first event in the playback order) cannot be changed from the screen access 1441 .

In S641, the CPU 201 of the program development apparatus 101 determines whether or not there is an instruction to close the editing screen shown in FIG. 4A and end the reproduction information definition acceptance process. For example, when the end button 1401 in FIG. 14A or the like is pressed, it is determined that there has been an instruction to end. If there is an instruction to end, the process of the flowchart of FIG. 6 is finished. Otherwise, the process proceeds to S642.

In S642, the CPU 201 of the program development device 101 determines whether or not the value set editor 1460 is displayed. If the value set editor 1460 is displayed, proceed to S615; otherwise, proceed to S643.

In S642, the CPU 201 of the program development device 101 determines whether or not the balloon editor 1470 is displayed. If the balloon editor 1470 is displayed, the process proceeds to S623; otherwise, the process proceeds to S607.

The processing described with reference to FIGS. 6 and 14 makes it possible to easily set and edit the reproduction information definition of the reproduction module.

Next, referring to FIG. 7, there is shown a flowchart of playback processing by the client device 104 executing the playback module generated in FIG.

In S701, the CPU 201 of the client device 104 acquires the SPA of the prototype application including the playback module deployed on the execution server 102 in S309.

At S702. A screen for accepting a reproduction request for the reproduction module included in the acquired SPA is displayed. A display example at this time is shown in FIG.

In S703, the CPU 201 of the client device 104 determines whether or not a prototype application reproduction request has been received. If the button 1601 in FIG. 16A has been operated, it is determined that a reproduction request has been made, and the process proceeds to S704. If not, the process returns to S702. It should be noted that, if the playback request is not accepted, the corresponding prototype data can be displayed in response to pressing of the "search" button in the example of FIG. 16(a). can.

In S<b>704 , the CPU 201 of the client device 104 acquires the reproduction information definition corresponding to the reproduction module from the execution server 102 .

In S705, events defined in the acquired reproduction information definition are acquired one by one in order. When the process first transits to S705, the first event, that is, the playback access is acquired. Playback access is a process of displaying a target screen definition UI screen.

In S706, the CPU 201 of the client apparatus 104 determines whether the event acquired in S705 is an event involving screen transition. If the event is associated with screen definition, the process proceeds to S707; otherwise, the process proceeds to S708.

In S707, the CPU 201 of the client device 104 executes the event acquired in S705. If the acquired event is a screen access, the screen is displayed according to the target UI definition screen. If the acquired event is a balloon, the balloon is displayed on the target GUI component according to the definition recorded in the reproduction information definition. If the acquired event is a value input (value set), a value according to the prototype data or playback information definition is displayed on the target GUI part. If the acquired event is an action (in a production environment, an event triggered by a user's operation), the prototype data corresponding to that action is displayed. If the action involves a screen transition, then in S707 the screen is switched to the transition destination screen, and then the prototype data defined for the action is displayed.

In S709, the CPU 201 of the client device 104 It is determined whether or not the event acquired in S705 is the last event in the reproduction information definition. If it is determined not to be the last event, the process advances to S706 to acquire and execute the next event. It should be noted that the transition from S709 to S705 is made after a predetermined time (for example, two seconds) has passed. As a result, a plurality of events defined in the reproduction information definition are sequentially executed at predetermined time intervals (for example, every two seconds). It should be noted that an example has been described in which this predetermined time, which is the transition waiting time, is fixed. The setting is not limited to this, and the user may be allowed to variably set for each event on the editing screen shown in FIG. 14 described above. If it is determined in S709 that it is the last process, then the process of FIG. 7 ends.

16(b) to 16(d), 17(a), and 17(b) show screen transition examples when the playback module is executed according to the playback information definition 1500 in FIG. 15 described above. indicates When the reproduction module is executed (reproduced), FIG. 16(b) is displayed according to the reproduction information definition 1500. After a predetermined time, the display transitions to FIG. The display automatically transitions in the order of FIG. 17(a) and FIG. 17(b).

FIG. 16(b) is a display based on the information recorded in the frame 1501 in which the reproduction order of the reproduction information definition 1500 is the first, and is a screen display according to the UI screen definition of UI_QUERY. This display is performed based on the information defined in UI_QUERY by referring to the screen definition information recorded in SPA.

FIG. 16(b) is a display based on the information recorded in the frame 1502, which is the second reproduction order of the reproduction information definition 1500. FIG. More specifically, the character string "Dev", which is the input value recorded in the reproduction information definition 1500, is displayed in a frame 1621 for the GUI component indicated by ML_ADDRESS, which is the input target. . A GUI component indicated by ML_ADDRESS is an input area for accepting data input from the user in the production application. However, when the reproduction module is executed, the character string "Dev" is automatically displayed without data input by the user (customer) watching the reproduction of the reproduction module.

FIG. 16D shows a display based on the information recorded in the frame 1503, which is the third reproduction order of the reproduction information definition 1500, and then displays the information recorded in the frame 1504, which is the fourth reproduction order. This is an example of display based on More specifically, according to the information indicated by the frame 1503, the balloon character string recorded in the reproduction information definition 1500 is displayed as indicated by a balloon 1631 for the GUI component indicated by the balloon target ML_ADDRESS. In addition, according to the information indicated by the frame 1504, the balloon character string recorded in the reproduction information definition 1500 is displayed as indicated by a balloon 1632 for the GUI component (search button 1616) indicated by SEARCN_BUTTON which is a balloon target. there is

FIG. 17A shows a display based on the information recorded in the frame 1505 whose reproduction order is the fifth in the reproduction information definition 1500, and then the information (not shown) recorded as the sixth reproduction order. This is an example of display based on More specifically, in accordance with the information indicated by the frame 1505, the action is recorded in correspondence with the action when the click, which is the operation indicated by the execution process, is performed on the GUI component (search button 1616) indicated by SEARCN_BUTTON, which is the execution target. display prototype data. Note that screen transition is not defined for the action of clicking the search button 1616, so a determination of No is made in S706, and the prototype recorded in association with the action of clicking the search button 1616 does not perform screen transition. Data 1701 is displayed. In the case of a production environment application, when the search button is clicked, the database is accessed and a search is performed using the character string input to the GUI component indicated by ML_ADDRESS as a search key. On the other hand, in the execution of this reproduction module, the corresponding prototype application is displayed without accessing the database and searching the GUI component indicated by ML_ADDRESS using the character string entered as the search key. process is performed. After that, a balloon is displayed according to the event that is the sixth in the playback order.
FIG. 17(b) is an example of display based on the information that the playback order of the playback information definition 1500 is the sixth or later. More specifically, in FIG. 17A, this is a display example after executing an event of cooking prototype data indicating a link destination, and then executing two events of displaying balloons. Since the action of clicking the link destination is defined as an action involving screen transition, S706 in FIG. 7 is determined as Yes, and screen 1710, which is the screen of the transition destination, is displayed in S707. After that, the screen 1710 displays the prototype data 1711 recorded in association with the click of the link destination. In the case of an application in a production environment, processing for accessing the clicked link destination is performed according to the click of the link destination. On the other hand, in executing the reproduction module, the process of accessing the link destination is not performed, but the process of displaying the corresponding prototype application is performed. After that, when two balloon display events are executed, the display of FIG. 17(b) is obtained.

With the above processing, it is possible to easily generate content (playback module) that allows one to virtually see the execution of multiple events in the production application software. By viewing this content, the customer (the user who is provided with the production application) can easily understand how multiple events are executed in the application for this application. Therefore, it is possible to save the time and effort of personnel (developers, sales representatives, etc.) who provide the production application to explain directly to the customer, and to make it possible for the customer to efficiently understand the operation of the production application. Furthermore, even if screen specifications change during development, the reproduction module reads and executes the changed UI definition, which has the effect of reducing man-hours required for correction. Furthermore, if you want to edit the playback module further (deleting or adding balloons, values, adding actions, etc.), you can read the existing playback information definition and edit it, so you don't have to recreate it from scratch. , the labor involved in editing can be reduced.

As described above, a recording medium recording a program for realizing the functions of the above-described embodiments is supplied to a system or device, and the computer (or CPU or MPU) of the system or device reads the program stored in the recording medium. Needless to say, the object of the present invention can also be achieved by reading and executing.

In this case, the program itself read from the recording medium implements the novel functions of the present invention, and the recording medium recording the program constitutes the present invention.

Examples of recording media for supplying programs 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 A disk or the like can be used.

Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also based on the instructions of the program, the OS (operating system) and the like running on the computer are actually executed. Needless to say, a case where part or all of the processing is performed and the functions of the above-described embodiments are realized by the processing are included.

Furthermore, after the program read from the recording medium is written in the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is read according to the instruction of the program code. It goes without saying that a case where a CPU or the like provided in a function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

Moreover, the present invention may be applied to a system composed of a plurality of devices or to an apparatus composed of a single device. Further, it goes without saying that the present invention can be applied to the case where it is achieved by supplying a program to a system or device. In this case, by loading a recording medium storing a program for achieving the present invention into the system or device, the system or device can enjoy the effects of the present invention.

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.

Furthermore, by downloading and reading out the program for achieving the present invention from a server, database, etc. on the network using a communication program, the system or device can enjoy the effects of the present invention. It should be noted that all configurations obtained by combining each of the above-described embodiments and modifications thereof are also included in the present invention.

101 Program development device 102 Execution server 103 Database server 104 Client device 105 Network

Claims (14)

first selection means for selecting one of a plurality of screens displayed by application software;
a second selection means for selecting one of the actions stored in association with the screen selected by the first selection means;
sequentially executing a plurality of events including a first event for displaying the screen selected by the first selection means and a second event corresponding to the action selected by the second selection means; and control means for controlling to generate instruction information for instructing. 2. The first selection means selects one of a plurality of options corresponding to a plurality of screens defined when the application software is created, in accordance with an operation of selecting one of the options. The information processing device according to . When one of the plurality of screens is selected by the first selection means, the control means selects the at least one action when there is at least one action stored in association with the selected screen. 3. The information processing apparatus according to claim 1, wherein the operation is controlled to be displayed as an option by said second selection means. 4. The information processing apparatus according to any one of claims 1 to 3, further comprising first receiving means for receiving an operation specifying an order of executing the plurality of events in the generated instruction information. . The second event executed based on the instruction information even when the action selected by the second selection means is an action including displaying a result of executing a specific process. 5. The information processing apparatus according to any one of claims 1 to 4, wherein is an event in which a predetermined display is performed without executing the specific process. further comprising second reception means for receiving input of additional information associated with the display element included in the screen selected by the first selection means;
4. The information processing apparatus according to any one of claims 1 to 3, wherein said plurality of events further include a third event for displaying additional information whose input is received by said second receiving means. . When one of the plurality of screens is selected by the first selection means, the control means, if there is the instruction information generated in association with the selected screen, 7. The information processing apparatus according to claim 6, wherein the selected screen and the additional information displayed in the third event are displayed. 8. An information processing apparatus according to claim 6, wherein said additional information is a character string. 9. The information processing apparatus according to any one of claims 6 to 8, wherein the additional information is information displayed in a balloon for a corresponding display element. Data to be automatically displayed in the input area included in the screen selected by the first selection means and for accepting data input from the user on the actual screen corresponding to the instruction information. It further has a third receiving means for receiving the input of
10. The information processing apparatus according to any one of claims 1 to 9, wherein said plurality of events further includes a fourth event for displaying data received by said third receiving means. The instruction information is information for instructing that the plurality of events are automatically sequentially executed without a user's operation after execution of the first event included in the instruction information. The information processing apparatus according to any one of claims 1 to 12. 12. The information processing apparatus according to any one of claims 1 to 11, further comprising generating means for generating source code of a program reflecting said instruction information. a first selection step of selecting one of a plurality of screens displayed by the application software;
a second selection step of selecting one of the actions stored in association with the screen selected in the first selection step;
sequentially executing a plurality of events including a first event for displaying the screen selected in the first selection step and a second event corresponding to the action selected in the second selection step; A control method for an information processing device, comprising: a control step of controlling to generate instruction information for instructing. A program for causing a computer to function as each means of the information processing apparatus according to any one of claims 1 to 12.

Images