JP6900864B2 - Information processing system, information processing device and information processing method - Google Patents

Description

The present invention relates to an information processing system, an information processing device, and an information processing method.

In recent years, services that provide functions that combine a plurality of functions (for example, scanning, printing, mail delivery, etc.) have become known. For example, there is known a service in which an electronic file (image file) generated by scanning is subjected to predetermined processing and then delivered by e-mail. Such a service is realized by executing one or more processes that realize each function as a series of processes.

Further, there is known an image forming apparatus that executes a series of processes based on an instruction sheet including processing information or the like representing one or more processes as a series of processes (see, for example, Patent Document 1).

However, in the above-mentioned conventional technique, in order for the user to use the service, for example, it is necessary to develop an application for executing a series of processes. On the other hand, application development may require specialized knowledge and experience regarding programming languages, for example.

One embodiment of the present invention has been made in view of the above points, and an object of the present invention is to support the development of an application.

In order to achieve the above object, one embodiment of the present invention is an information processing system including one or more information processing devices and having a plurality of programs that execute predetermined processes, respectively, and is a series of information processing systems using electronic data. For each application that executes processing, program identification information that identifies one or more programs that execute each processing of the series of processing and flow information that defines the execution order of one or more programs are provided as 1 The application storage means for storing the application associated with the application setting information in which the parameter information used for executing each of the above programs and the flow identification information for identifying the flow information are defined is connected to the information processing system. The receiving means for receiving the registration request including the application setting information created in the electronic device of one or more electronic devices and the application setting information included in the registration request received by the receiving means. Based on the defined parameter information, it is defined in the generation means for generating a test case indicating a combination of the parameter information for testing the execution of the series of processes, and the application setting information included in the registration request. One or more identified by the acquisition means for acquiring the flow information identified by the flow identification information and the program identification information defined in the flow information acquired by the acquisition means. By executing each of the above programs according to the execution order defined in the flow information using the combination of the parameter information indicated by the test case generated by the generation means, the series of processes can be performed. It has an execution means for testing execution.

According to one embodiment of the present invention, it is possible to support the development of an application.

It is a figure which shows an example of the system structure of the information processing system which concerns on 1st Embodiment. It is a figure which shows an example of the hardware configuration of the service providing system and the PC terminal which concerns on 1st Embodiment. It is a figure which shows an example of the hardware composition of the apparatus which concerns on 1st Embodiment. It is a figure which shows an example of the functional structure of the information processing system which concerns on 1st Embodiment. It is a figure which shows an example of the functional structure of the logic processing part which concerns on 1st Embodiment. It is a figure which shows an example of the type conversion information table. It is a figure which shows an example of the processing flow information. It is a sequence diagram which shows an example of the registration process of the application which concerns on 1st Embodiment. It is a figure which shows an example of a portal top screen. It is a figure which shows an example of the application registration screen (1/5). It is a figure which shows an example of the application registration screen (2/5). It is a figure which shows an example of the application registration screen (3/5). It is a figure which shows an example of the application registration screen (4/5). It is a figure which shows an example of the application registration screen (5/5). It is a figure which shows an example of application setting information. It is a figure which shows an example of a test screen. It is a figure which shows an example of the test result screen. It is a sequence diagram which shows an example of the test execution process which concerns on 1st Embodiment. It is a figure which shows an example of a test case. It is a figure which shows an example of the parameter information which an arbitrary character string can be set as a parameter value. It is a figure which shows an example of the test result information. It is a sequence diagram which shows another example of the test execution process which concerns on 1st Embodiment. It is a figure which shows an example of a parameter input screen. It is a sequence diagram which shows an example of the execution processing of the processing flow which realizes the OCR division service. It is a sequence diagram which shows an example of the whole processing when using the OCR division service. It is a figure which shows an example of the application screen of an OCR division application. It is a sequence diagram which shows another example of the test execution process which concerns on 1st Embodiment. It is a figure which shows an example of the functional structure of the information processing system which concerns on 2nd Embodiment. It is a sequence diagram which shows an example of the test execution process which concerns on 2nd Embodiment. It is a figure which shows another example of application setting information. It is a figure which shows an example of a component information.

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

[First Embodiment]
<System configuration>
First, the system configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram showing an example of a system configuration of the information processing system 1 according to the present embodiment.

The information processing system 1 shown in FIG. 1 includes a service providing system 10, a device 20, and a PC terminal 30, and is communicably connected via a wide area network N1 such as the Internet.

The service providing system 10 is realized by one or more information processing devices, and is realized by a series of processes in which one or more of a plurality of processes that realize various functions are combined via the network N1. Provide various services.

Here, the function is a function related to an electronic file such as a document file or an image file. Functions include, for example, printing, scanning, facsimile transmission, data format conversion, mail delivery, OCR (Optical character recognition) processing, processing, compression / decompression, storage in a repository, and the like.

A specific example of the service provided by the service providing system 10 according to the present embodiment will be described later. Hereinafter, a series of processes will also be referred to as a "processing flow".

The device 20 is various electronic devices used by the user. That is, the device 20 is, for example, an image forming device such as an MFP (Multifunction Peripheral), a PC (personal computer), a projector, an electronic whiteboard, a digital camera, or the like. The user can use various services provided by the service providing system 10 by using the device 20.

In the following, a plurality of devices 20, when distinguishing the each "device 20 _1", describes using a subscript as "device 20 _2" and the like.

The PC terminal 30 is, for example, a desktop PC, a notebook PC, a smartphone, a tablet terminal, or the like used by a user. The user can use various services provided by the service providing system 10 by using the PC terminal 30.

In the following, when distinguishing each of the plurality of PC terminals 30, the _{subscripts such as "PC terminal 30 1} " and "PC terminal 30 ₂ " will be used.

The configuration of the information processing system 1 shown in FIG. 1 is an example, and may be another configuration. For example, the information processing system 1 according to the present embodiment includes various devices that input and output electronic data, and even if these devices use various services provided by the service providing system 10. good.

<Hardware configuration>
Next, the hardware configurations of the service providing system 10 and the PC terminal 30 included in the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 2 is a diagram showing an example of the hardware configuration of the service providing system 10 and the PC terminal 30 according to the present embodiment. Since the service providing system 10 and the PC terminal 30 have the same hardware configuration, the hardware configuration of the service providing system 10 will be mainly described below.

The service providing system 10 shown in FIG. 2 includes an input device 11, a display device 12, an external I / F 13, and a RAM (Random Access Memory) 14. Further, the service providing system 10 includes a ROM (Read Only Memory) 15, a CPU (Central Processing Unit) 16, a communication I / F 17, and an HDD (Hard Disk Drive) 18. Each of these hardware is connected by a bus B.

The input device 11 includes a keyboard, a mouse, a touch panel, and the like, and is used by the user to input each operation signal. The display device 12 includes a display and the like, and displays the processing result by the service providing system 10. At least one of the input device 11 and the display device 12 may be used by connecting to the service providing system 10 when necessary.

The communication I / F 17 is an interface for connecting the service providing system 10 to the network N1. As a result, the service providing system 10 can perform communication via the communication I / F17.

The HDD 18 is a non-volatile storage device that stores programs and data. The programs and data stored in the HDD 18 include an OS (Operating System), which is basic software that controls the entire service providing system 10, application software that provides various functions on the OS, and the like.

The service providing system 10 may use a drive device (for example, a solid state drive: SSD) that uses a flash memory as a storage medium instead of the HDD 18. Further, the HDD 18 manages the stored programs and data by a predetermined file system and / or DB.

The external I / F 13 is an interface with an external device. The external device includes a recording medium 13a and the like. As a result, the service providing system 10 can read and write the recording medium 13a via the external I / F 13. The recording medium 13a includes a flexible disk, a CD, a DVD, an SD memory card, a USB memory, and the like.

The ROM 15 is a non-volatile semiconductor memory capable of holding programs and data even when the power is turned off. The ROM 15 stores programs and data such as a BIOS (Basic Input / Output System), an OS setting, and a network setting that are executed when the service providing system 10 is started. The RAM 14 is a volatile semiconductor memory that temporarily holds programs and data.

The CPU 16 is an arithmetic unit that realizes control and functions of the entire service providing system 10 by reading a program or data from a storage device such as the ROM 15 or the HDD 18 onto the RAM 14 and executing processing.

By having the hardware configuration shown in FIG. 2, the service providing system 10 and the PC terminal 30 according to the present embodiment can realize various processes as described later.

Next, a hardware configuration when the device 20 included in the information processing system 1 according to the present embodiment is an image forming apparatus will be described with reference to FIG. FIG. 3 is a diagram showing an example of the hardware configuration of the device 20 according to the present embodiment.

The device 20 shown in FIG. 3 includes a controller 21, an operation panel 22, an external I / F 23, a communication I / F 24, a printer 25, and a scanner 26. Further, the controller 21 has a CPU 31, a RAM 32, a ROM 33, an NVRAM 34, and an HDD 35.

The ROM 33 is a non-volatile semiconductor memory that stores various programs and data. The RAM 32 is a volatile semiconductor memory that temporarily holds programs and data. The NVRAM 34 stores, for example, setting information and the like. The HDD 35 is a non-volatile storage device that stores various programs and data.

The CPU 31 is an arithmetic unit that realizes control and functions of the entire device 20 by reading programs, data, setting information, etc. from the ROM 33, NVRAM 34, HDD 35, etc. onto the RAM 32 and executing processing.

The operation panel 22 includes an input unit for receiving input from the user and a display unit for displaying. The external I / F 23 is an interface with an external device. The external device includes a recording medium 23a and the like. As a result, the device 20 can read and / or write to the recording medium 23a via the external I / F 23. The recording medium 23a includes, for example, an IC card, a flexible disk, a CD, a DVD, an SD memory card, a USB memory, and the like.

The communication I / F 24 is an interface for connecting the device 20 to the network. As a result, the device 20 can communicate via the communication I / F 24. The printer 25 is a printing device that prints print data. The scanner 26 is a scanning device that reads a document and generates an electronic file (image file).

The device 20 according to the present embodiment can realize various processes as described later by having the hardware configuration shown in FIG.

<Services provided by the service provision system>
Here, the service provided by the service providing system 10 according to the present embodiment will be described. Hereinafter, the device 20 will be described as an image forming apparatus.

In the present embodiment, the "OCR division service" provides a service for page-dividing a PDF (Portable Document Format) file output by performing OCR processing on an electronic file (image file) generated by scanning a document in the device 20. Is expressed. Then, in this embodiment, the case where the service providing system 10 provides the OCR division service will be described.

Here, in order for the service providing system 10 to provide the OCR division service, it is necessary for the device 20 to register an application (application information 1000 described later) for using the OCR division service in the service providing system 10.

Therefore, in the present embodiment, a case where the PC terminal 30 registers an application for using the OCR division service and a case where the device 20 uses the OCR division service using the application will be described.

However, the services provided by the service providing system 10 are not limited to these. The service providing system 10 may provide, for example, a service of encrypting an electronic file generated by scanning a document in the device 20 and then delivering an e-mail.

Similarly, the service providing system 10 may provide a service of fax transmission after adding predetermined information to an electronic file generated by scanning a document in, for example, the device 20.

<Functional configuration>
Next, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. FIG. 4 is a diagram showing an example of the functional configuration of the information processing system 1 according to the present embodiment.

The PC terminal 30 shown in FIG. 4 has a browser 310 executed by, for example, a CPU 16 or the like. The user of the PC terminal 30 can use the browser 310 to register an application for using various services such as the "OCR division service" in the service providing system 10.

The device 20 shown in FIG. 4 has a browser 210 executed by, for example, a CPU 31 or the like. The user of the device 20 can use various services such as the "OCR division service" by using the browser 210. That is, the device 20 may have a browser 210, and does not need to have, for example, a dedicated application program for using various services provided by the service providing system 10.

The service providing system 10 shown in FIG. 4 includes an input / output service processing unit 110, a Web service processing unit 120, a document service unit 130, and a portal service unit 140. Each of these functional units is realized by a process of causing the CPU 16 to execute one or more programs installed in the service providing system 10.

Further, the service providing system 10 includes an application information storage unit 150, an application screen information storage unit 160, a portal screen information storage unit 170, and a test result information storage unit 180. Each of these storage units can be realized by using the HDD 18. At least one of these storage units may be realized by using a storage device or the like connected to the service providing system 10 via a network.

The input / output service processing unit 110 performs processing related to the service provided by the service providing system 10. Here, the input / output service processing unit 110 includes an application management unit 111 and a logic processing unit 112.

The application management unit 111 manages the application information 1000 stored in the application information storage unit 150. The application information 1000 is an application for using a service realized by a series of processes. In other words, the various services provided by the service providing system 10 are provided by the application information 1000.

Further, the application management unit 111 returns the processing flow information 1100 included in the application information 1000 in response to the request from the logic processing unit 112. The processing flow information 1100 is information that defines a series of processes that realize the service provided by the application information 1000.

Further, the application management unit 111 stores the application information 1000 in the application information storage unit 150 in response to a request from the portal service unit 140. As a result, the application information 1000 (application) that provides the service is registered in the service providing system 10.

The logic processing unit 112 acquires the processing flow information 1100 included in the application information 1000 from the application management unit 111 in response to a request from the Web service processing unit 120. Then, the logic processing unit 112 executes a series of processes (processing flow) for realizing the service provided by the application information 1000 based on the processing flow information 1100 acquired from the application management unit 111. As a result, the service providing system according to the present embodiment can provide various services such as "OCR division service". The details of the logic processing unit 112 will be described later.

The Web service processing unit 120 performs processing for the user to use various services using the browser 210 of the device 20. That is, the Web service processing unit 120 functions as an application server that provides a Web application (application information 1000) to the browser 210. Here, the Web service processing unit 120 has a screen configuration unit 121 and an application execution unit 122.

In response to a request from the browser 210, the screen configuration unit 121 sets the application included in the application screen information 2000 stored in the application screen information storage unit 160 and the application information 1000 stored in the application information storage unit 150. Information 1200 is returned.

The application screen information 2000 is information in which a template of a screen (application screen) for using the service provided by the application information 1000 is defined. The application screen information 2000 is information in which a template of the application screen is defined by, for example, HTML (HyperText Markup Language), XHTML (Extensible HyperText Markup Language), CSS (Cascading Style Sheets), Javascript (registered trademark), and the like.

Further, the application setting information 1200 is information in which various settings of the application (application information 1000) are defined. For example, in the application setting information 1200, among the parameter information used for executing a series of processes, the parameter information in which the parameter value is input by the user, the parameter information in which the parameter value is set by default, and the like are defined. Further, for example, the application setting information 1200 defines input items for the user to input parameter information on the application screen, display information on the application screen (for example, application name), and the like. The application setting information 1200 is information in which various settings of the application are defined by, for example, JSON (JavaScript Object Notation) or the like.

As a result, the device 20 displays the application screen for using the service provided by the service providing system 10 by the browser 210.

The application execution unit 122 transmits an execution request of the application (application information 1000) to the input / output service processing unit 110 in response to the request from the browser 210. Further, the application execution unit 122 shows a test result (test result) indicating a series of processing execution results (test results) based on the processing flow information 1100 included in the application information 1000 when the application (application information 1000) is tested. The information is stored in the test result information storage unit 180.

The application test is to confirm whether or not the application operates normally, for example, when a new application (application information 1000) is registered or when the settings of the registered application are modified. Is.

The document service unit 130 executes a predetermined process included in a series of processes (process flow) based on the process flow information 1100. Here, the document service unit 130 has an OCR processing unit 131 and the like.

The OCR processing unit 131 performs OCR processing on the electronic file to create a PDF file (PDF file with text) to which the text recognized by the OCR processing is added.

In addition to these, the document service unit 130 has various functions such as a compression / decompression processing unit for compressing or decompressing an electronic file, a data format conversion unit for converting the data format of an electronic file, and the like. The part may be included.

The portal service unit 140 performs processing for the user to register an application or the like using the browser 310 of the PC terminal 30. Here, the portal service unit 140 has a UI providing unit 141 and an application registration unit 142.

The UI providing unit 141 returns the portal screen information 3000 stored in the portal screen information storage unit 170 in response to the request from the browser 310. Here, the portal is a website on which applications can be registered using the browser 310.

The portal screen information 3000 is information in which various screens such as a portal top screen (portal top screen) and an application registration screen are defined. The portal screen information 3000 is information in which various screens are defined by a browser 210 such as HTML, XML, CSS, and Javascript.

As a result, the portal top screen and the application registration screen are displayed on the PC terminal 30 by the browser 310. Therefore, the user of the PC terminal 30 can perform the application (application information 1000) registration operation on the application registration screen.

The application registration unit 142 requests the application management unit 111 to register the application (application information 1000) in response to the request from the UI providing unit 141. That is, when the application registration operation is performed on the application registration screen, the application registration unit 142 requests the application management unit 111 to register the application.

The application information storage unit 150 stores the application information 1000. The application information 1000 is stored in the application information storage unit 150 in association with the application ID that identifies the application information 1000. The application ID is, for example, the URL (Uniform Resource Locator) of the application information 1000, the identification information included in the URL of the application information 1000, or the like.

Here, the application information 1000 includes processing flow information 1100 and application setting information 1200. For example, the application information 1000 that provides the OCR division service includes processing flow information 1100 that defines a series of processes that realize the service, and application setting information 1200 that defines various settings of the application information 1000. Is done. Hereinafter, the application information 1000 that provides the OCR division service is also referred to as an “OCR division application”.

The application information 1000 may include two or more processing flow information 1100 and two or more application setting information 1200.

As described above, the processing flow information 1100 is information in which a series of processes (processing flows) for realizing the service provided by the application information 1000 are defined. The details of the processing flow information 1100 will be described later.

Further, the application setting information 1200 is information in which various settings of the application (application information 1000) are defined as described above. The details of the application setting information 1200 will be described later.

The application screen information storage unit 160 stores the application screen information 2000. The application screen information 2000 is stored in the application screen information storage unit 160 in association with the application ID.

The portal screen information storage unit 170 stores the portal screen information 3000. The portal screen information 3000 is stored in the portal screen information storage unit 170 in association with a URL such as a portal top screen or an application registration screen.

The test result information storage unit 180 stores the test result information. The test result information includes the test result of the application, the tested test case, and the like.

The input / output service processing unit 110, the Web service processing unit 120, the document service unit 130, the portal service unit 140, and the like may be realized by different information processing devices.

Here, the detailed functional configuration of the logic processing unit 112 will be described with reference to FIG. FIG. 5 is a diagram showing an example of the functional configuration of the logic processing unit 112 according to the present embodiment.

The logic processing unit 112 shown in FIG. 5 includes a flow execution unit 301, a component management unit 302, a component group 303, a type conversion management unit 304, and a type conversion group 305. Further, the logic processing unit 112 has a type conversion information table 4000.

When the flow execution unit 301 receives the application execution request from the application execution unit 122, the flow execution unit 301 acquires the processing flow information 1100 corresponding to the execution request from the application management unit 111. Then, the flow execution unit 301 executes a series of processing (processing flow) based on the processing flow information 1100 acquired from the application management unit 111.

Here, a series of processes based on the process flow information 1100 is executed by combining components for executing each process included in the series of processes. A component is realized by a program, a module, or the like for executing a process that realizes a predetermined function, and is defined by, for example, a class or a function.

The component management unit 302 manages the components. The component management unit 302 generates a component in response to a request from the flow execution unit 301, and returns the generated component to the flow execution unit 301. Note that the generation of a component means, for example, expanding a component defined by a class, a function, or the like on a memory (for example, RAM 14).

The component group 303 is a set of components. The component group 303 includes an OCR component 1310 and a PDF component 1320.

The OCR component 1310 is a component for OCR processing an electronic file (image file). The OCR component 1310 performs the OCR processing of the electronic file by requesting the OCR processing unit 131 of the document service unit 130 for the OCR processing.

The PDF component 1320 is a component for creating a plurality of PDF files by dividing the pages of the PDF file.

In this way, each component executes a process that realizes a predetermined function. In addition to the above components, the component group 303 includes various components such as an encryption / decryption component for encrypting and decrypting an electronic file and a compression component for compressing an electronic file. Is done.

Further, each component included in the component group 303 has a component common I / F 1300. The component common I / F 1300 is an API (Application Programming Interface) commonly defined for each component, and includes an API for generating a component and an API for executing processing of the component.

In this way, since each component has the component common I / F 1300, the influence of the addition of the component or the like can be localized. That is, for example, components can be added without affecting the flow execution unit 301, the component management unit 302, and the like. As a result, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hours associated with the addition of a predetermined function (that is, the addition of a component for executing the process for realizing the function, etc.).

The type conversion management unit 304 manages the type conversion of the data type. Here, each component has a predetermined data type that it can handle. Therefore, the type conversion management unit 304 generates the type conversion included in the type conversion group 305 by referring to the type conversion information table 4000 shown in FIG. 6, for example, in response to the request from the component.

Then, the type conversion management unit 304 requests the generated type conversion to execute the type conversion process. Note that type conversion is realized by a program or module that executes data type type conversion processing, and is defined by, for example, a class or function. Further, the generation of type conversion means, for example, expanding the type conversion defined by a class, a function, or the like into a memory (for example, on the RAM 14).

The data types include, for example, the data type "InputStream" indicating stream data, "LocalFilePath" indicating the path (address) of an electronic file stored in a storage device, and "File" indicating the substance of the electronic file. And so on.

Here, the type conversion information table 4000 will be described with reference to FIG. FIG. 6 is a diagram showing an example of the type conversion information table 4000.

The type conversion information table 4000 shown in FIG. 6 has a data type before conversion, a data type after conversion, and a type conversion to be generated as data items. That is, the type conversion information stored in the type conversion information table 4000 is used to convert the data type before conversion to the data type after conversion for each of the data type before conversion and the data type after conversion. Information associated with type conversion.

The type conversion group 305 is a set of type conversions. The type conversion group 305 includes a first type conversion 1410 for converting the data type "InputStream" to "LocalFilePath". In addition to this, the type conversion group 305 includes, for example, a second type conversion for converting the data type "LocalFilePath" to "File".

Further, each type conversion included in the type conversion group 305 has a type conversion common I / F 1400. The type conversion common I / F1400 is an API commonly defined for each type conversion, and includes an API for generating a type conversion and an API for executing a type conversion process of the type conversion.

In this way, since each type conversion has a common I / F 1400 for type conversion, it is possible to localize the influence of the addition of type conversion and the like. That is, for example, type conversion can be added without affecting the type conversion management unit 304 or the like. As a result, in the service providing system 10 according to the present embodiment, it is possible to reduce the development man-hours associated with the addition of type conversion and the like.

Here, the processing flow information 1100 included in the application information 1000 that provides the OCR division service will be described with reference to FIG. 7. FIG. 7 is a diagram showing an example of processing flow information 1100.

The processing flow information 1100 shown in FIG. 7 is information in which a series of processing (processing flow) for realizing the OCR division service is defined.

The processing flow information 1100 shown in FIG. 7 includes a flow name 1101 that identifies the processing flow information 1100, and a flow detail 1102 that defines the processing content of each processing included in the processing flow.

The flow details 1102 includes a detailed processing definition 1110 that defines each process included in the processing flow, and a detailed processing definition 1120. The detailed processing definition 1110 and the detailed processing definition 1120 include "" dataName "" indicating the detailed processing name that identifies the detailed processing definition and "" component "" indicating the component name of the component for executing the processing. Is done. Further, the detailed processing definition 1110 and the detailed processing definition 1120 include "" operationName "" indicating the operation executed by the component and "" parameters "" in which the parameter information is defined.

The operation is a process executed by the component, and each component can execute one or more operations.

Specifically, "" detail0 "" is defined in "" detailName "" of the detailed processing definition 1110. The component name "" OCR "" of the OCR component 1310 is defined in the "" component "" of the detailed processing definition 1110. Further, in the "operationName" "of the detailed process definition 1110, the operation name" "process" "indicating that the OCR component 1310 executes the OCR process is defined. Further, parameter information and the like of the parameter name "" parameter "" are defined in "" parameters "" of the detailed processing definition 1110.

The print size of the PDF file output as a result of the OCR processing is set in the parameter information of the parameter name "" outputSize "". In the processing flow information 1100 shown in FIG. 7, "A4" is defined as the default parameter value in the parameter information of the parameter name "" outputSize "".

Similarly, "" detail1 "" is defined in "" detailName "" of the detailed processing definition 1120. The component name "" PDF "" of the PDF component 1320 is defined in the "" component "" of the detailed processing definition 1120. Further, in the "operationName" of the detailed processing definition 1120, the operation name "" dividedByPageNumbers "" indicating that the PDF component 1320 executes the process of dividing the PDF file by the page number is defined. Further, the parameter information used in the PDF component 1320 is defined in the "parameters" of the detailed processing definition 1120.

The processing execution order defined in each detailed processing definition is defined in order from the top in the flow details 1102. That is, in a series of processes (process flows) based on the process flow information 1100 shown in FIG. 7, the processes defined in the detailed process definition 1110 and the processes defined in the detailed process definition 1120 are executed in this order. However, the present invention is not limited to this, and the processing flow information 1100 may define, for example, information indicating the execution order of the processes defined in each detailed process definition.

<Details of processing>
Next, the details of the processing of the information processing system 1 according to the present embodiment will be described. First, a process in which the user of the PC terminal 30 registers the OCR division application in the service providing system 10 will be described with reference to FIG. FIG. 8 is a sequence diagram showing an example of application registration processing according to the present embodiment.

First, the browser 310 of the PC terminal 30 accepts an operation for displaying the portal top screen (display operation of the portal top screen) (step S801). The user of the PC terminal 30 can perform a display operation of the portal top screen by inputting the URL of the portal top screen into the address bar of the browser 310, for example.

When the browser 310 of the PC terminal 30 receives the display operation of the portal top screen, the browser 310 transmits the display request of the portal top screen to the UI providing unit 141 of the portal service unit 40 (step S802).

When the UI providing unit 141 of the portal service unit 140 receives the acquisition request of the portal top screen, the UI providing unit 141 acquires the portal screen information of the portal top screen from the portal screen information storage unit 170 (step S803). Then, the UI providing unit 141 returns the portal screen information acquired from the portal screen information storage unit 170 to the browser 310.

When the browser 310 of the PC terminal 30 receives the portal screen information of the portal top screen, the browser 310 displays, for example, the portal top screen G100 shown in FIG. 9 based on the portal screen information (step S804).

The portal top screen G100 shown in FIG. 9 is the top screen of the portal, and includes an “Application” button G110 for registering an application. Hereinafter, it is assumed that the user performs an operation of selecting the "Application" button G110 (application registration selection operation) on the portal top screen G100 shown in FIG.

The portal top screen G100 shown in FIG. 9 also includes a "Flow" button G120 for creating processing flow information 1100 and the like, a "Component" button G130 for registering components, and the like. In this way, on the portal top screen G100, in addition to registering the application, it is possible to create / execute the processing flow, register / update the component, and the like.

The browser 310 of the PC terminal 30 accepts the application registration selection operation performed by the user (step S805).

When the browser 310 of the PC terminal 30 receives the application registration selection operation, it transmits a display request for the application registration screen to the UI providing unit 141 of the portal service unit 40 (step S806).

When the UI providing unit 141 of the portal service unit 140 receives the display request of the application registration screen, the UI providing unit 141 acquires the portal screen information of the application registration screen from the portal screen information storage unit 170 (step S807). Then, the UI providing unit 141 returns the portal screen information acquired from the portal screen information storage unit 170 to the browser 310.

When the browser 310 of the PC terminal 30 receives the portal screen information of the application registration screen, the browser 310 displays, for example, the application registration screen G200 shown in FIG. 10 based on the portal screen information (step S808).

Here, a case where the user performs an application registration operation will be described with reference to FIGS. 10 to 14.

First, the application registration screen G200 shown in FIG. 10 is a screen for selecting the type of application to be registered by the user.

The application registration screen G200 shown in FIG. 10 includes a "print" button G210 for registering a print type application and a "scan" button G220 for registering a scan type application. In addition to the above, the application registration screen G200 shown in FIG. 10 has, for example, a "FAX" button for registering a FAX type application, a "Mail reception" button for registering a mail reception type application, and the like. May be included.

Further, the application registration screen G200 shown in FIG. 10 includes a "Next" button G240 and the like for transitioning to the next screen.

In the application registration screen G200 shown in FIG. 10, when the user selects either the "print" button G210 or the "scan" button G220, a description of the print type or a description of the scan type is displayed in the description column G230, respectively.

The print type is an application of a type in which an electronic file showing an execution result of a series of processes is printed by an image forming apparatus or the like. On the other hand, the scan type is an application of a type that executes a series of processes by inputting an electronic file generated by scanning in an image forming apparatus or the like.

Further, for example, the FAX type is an application of a type in which an electronic file showing an execution result of a series of processes is transmitted by FAX by an image forming apparatus or the like. Further, the mail reception type is an application of a type in which an image forming apparatus or the like executes a series of processes by inputting an electronic file attached to the received mail.

Hereinafter, it is assumed that the user selects the "scan" button G220 on the application registration screen G200 shown in FIG. 10 and then presses the "next" button G240. Then, the browser 310 accepts the operation and displays, for example, the application registration screen G300 shown in FIG.

The application registration screen G300 shown in FIG. 11 is a screen for the user to set basic information of the application.

The application registration screen G300 shown in FIG. 11 includes an "application name" input setting field G310 for setting an application name and a "design template" selection field G320 for selecting a screen format of the application screen. .. Further, on the application registration screen G300 shown in FIG. 11, an "authentication" selection field G330 for selecting authentication when using the application and a "display language" selection field G340 for selecting the display language of the application screen are displayed. And are included. Further, the application registration screen G300 shown in FIG. 11 includes a "Next" button G350 and the like for transitioning to the next screen.

In the "design template" selection field G320, for example, a "single screen format" in which the application screen is displayed on one screen, a "wizard format" in which the application screen is displayed interactively, and the like can be selected. Further, in the "authentication" selection field G330, "none" indicating that authentication is not used, "user authentication" indicating that authentication is used, and the like can be selected.

Hereinafter, it is assumed that the user performs an operation of pressing the "Next" button G350 after inputting the application name and making various selections as in the application registration screen G300 shown in FIG. Then, the browser 310 accepts the operation and displays, for example, the application registration screen G400 shown in FIG.

The application registration screen G400 shown in FIG. 12 is a screen for the user to set a series of processes (processing flow) for the application to be registered as detailed information of the application.

The application registration screen G400 shown in FIG. 12 includes a search field G410 for searching the flow name of the processing flow information 1100 stored in the application information storage unit 150, and a flow selection field G420 for selecting the flow name. Is included. The user can select a desired flow name from the flow selection field G420 after inputting a desired flow name or the like in the search field G410.

Further, the application registration screen G400 shown in FIG. 12 transitions to a summary display field G430 for displaying an outline of a series of processes based on the process flow information 1100 of the flow name selected in the flow selection field G420, and the next screen. Includes a "Next" button G440 for.

Further, on the application registration screen G400 shown in FIG. 12, an "update" button G421 for editing and updating the processing flow information 1100 of the flow name selected in the flow selection field G420, and a new processing flow information 1100 are displayed. Includes a "new" button G422 for creating. By pressing the "update" button G421, the user can edit and update the processing flow information 1100 of the flow name selected in the flow selection field G420. Further, the user can create the processing flow information 1100 by pressing the "new" button G422, and then select the flow name of the created processing flow information 1100 in the flow selection field G420.

Hereinafter, it is assumed that the user selects the flow name "ocr-divide" in the flow selection field G420 and then presses the "Next" button G440. Then, the browser 310 accepts the operation and displays, for example, the application registration screen G500 shown in FIG.

The application registration screen G500 shown in FIG. 13 is a screen for the user to set parameter information of a series of processes (processing flow) set on the application registration screen G400 shown in FIG. 12 as detailed information of the application.

The application registration screen G500 shown in FIG. 13 includes a “component” selection field G510 for selecting a component to execute each process included in the series of processes. Further, on the application registration screen G500 shown in FIG. 13, a "parameter information" setting field G520 for setting the parameter information of the component selected in the "component" selection field G510 and a "parameter information" setting field G520 for transitioning to the next screen are provided. The "Next" button G530 and the like are included.

The user can select a desired component from the "component" selection field G510 and then set various parameter information in the "parameter information" setting field G520. For example, when the user selects the PDF component 1320 from the "component" selection field G510, various settings of the parameter information used by the PDF component 1320 can be made in the "parameter information" setting field G520.

The "parameter information" setting field G520 includes, for example, "userInput", "displayname", "name", "inputType", and the like.

In "userInput", whether or not to let the user (user of the service) input the parameter value of the parameter information is set. For the parameter information in which "userInput" is checked, the user (service user) can input the parameter value on the application screen. On the other hand, for the parameter information in which "userInput" is not checked, the user cannot input the parameter value on the application screen, and the default parameter value is used.

Further, in "inputType", the input method on the application screen is set for the parameter information in which the setting item "select" is checked. In "iputType", for example, an input method "select" for selecting a desired parameter value from a list of parameter values, an input method "ext" for directly inputting a parameter value, and the like are set. In addition to these, for "inputType", for example, an input method for inputting coordinates on the screen, an input method for selecting a desired folder or file, or the like may be selected.

The parameter name of the parameter information is set in "name". In addition, the display name of the input item (item for inputting the parameter value) displayed on the application screen is set in "displayname".

As a result, the user can set whether or not to let the service user input the parameter value of the parameter information, the input method, and the like for the parameter information used by each component.

Hereinafter, it is assumed that the user performs an operation of pressing the "Next" button G530 after setting the parameter information used by each component. Then, the browser 310 accepts the operation and displays, for example, the application registration screen G600 shown in FIG.

The application registration screen G600 shown in FIG. 14 is a screen for the user to confirm various information (application setting information) set in FIGS. 10 to 13.

The application registration screen G600 shown in FIG. 14 includes an "application setting information" display field G610 and a "registration execution" button G620. The user can confirm various information set in FIGS. 10 to 13 in the "application setting information" display field G610.

Here, it is assumed that the user confirms the application setting information in the "application setting information" display field G610 and then presses the "register" button G620 (application registration operation). Then, the browser 310 accepts the application registration operation (step S809).

When the browser 310 accepts the application registration operation, it creates, for example, the application setting information 1200 shown in FIG. 15 (step S810).

Here, the application setting information 1200 will be described with reference to FIG. FIG. 15 is a diagram showing an example of the application setting information 1200.

The application setting information 1200 shown in FIG. 15 includes an application type 1201, an application name 1202, an application display name 1203, an authentication type 1204, and a flow name 1205. Further, the application setting information 1200 shown in FIG. 15 includes a design template type 1206, a default parameter 1207, and a user input parameter 1208.

The application type 1201 is the type of application selected on the application registration screen G200 shown in FIG. In the example shown in FIG. 15, "" app_type ":" scan "" indicating that the type of application is a scan type is defined.

The application name 1202 is an application name input in the “application name” input setting field G310 of the application registration screen G300 shown in FIG. In the example shown in FIG. 15, "" appName ":" OCR split application "" indicating that the application name is "OCR split application" is defined.

The application display name 1203 is an application name (title) displayed on the application screen. In the example shown in FIG. 15, it is defined that "OCR division" is displayed in Japanese and "OCR App" is displayed in English.

The authentication type 1204 is the authentication selected in the "authentication" selection field G330 of the application registration screen G300 shown in FIG. In the example shown in FIG. 15, "" loginType ":" none "" indicating that authentication is not performed is defined.

The flow name 1205 is a flow name selected in the flow selection field G420 of the application registration screen G400 shown in FIG. In the example shown in FIG. 15, it is defined that the flow name is "" ocr-divide "".

The design template type 1206 is a display format selected in the "design template" selection field G320 of the application registration screen G300 shown in FIG. In the example shown in FIG. 15, "" viewTemplate ":" one-screen format "" indicating that the application screen is displayed in the one-screen format is defined.

The default parameter 1207 defines parameter information in which the user does not input a parameter value on the application screen. That is, in the default parameter 1207, parameter information in which "userInput" is not checked is defined in the "parameter information" setting field G520 of the application registration screen G500 shown in FIG. In the example shown in FIG. 15, the default parameter value of the parameter information used in the process defined by the detailed process name “detail 0” (that is, the detailed process definition 1110 in FIG. 7) is defined. Specifically, the default parameter value "" English "" is defined for the parameter information of the parameter name "" language "".

As described above, the default parameter 1207 defines the parameter information in which the default parameter value is set. In other words, the default parameter 1207 defines parameter information for which the user does not set a parameter value.

The user input parameter 1208 defines parameter information in which a parameter value is input by the user on the application screen. That is, in the user input parameter 1208, the parameter information in which "userInput" is checked is defined in the "parameter information" setting field G520 of the application registration screen G500 shown in FIG.

In the example shown in FIG. 15, the parameter information used in the processing defined in the detailed processing name “detail 1” (that is, the detailed processing definition 1120 in FIG. 7) is defined. Specifically, an input definition 1210 is defined indicating that the parameter value of the parameter information of the parameter name "divisionPageRanger" is input to the user. Similarly, an input definition 1220 is defined indicating that the parameter value of the parameter information of the parameter name "divisionPageNumbers" is input to the user.

In the input definition 1210, "select" is defined in "" inputType "" indicating the input method of the parameter value. This indicates that the user is allowed to select the desired parameter value from the list of parameter values.

Further, in the input definition 1210, "" Each Pages "and" Special Pages "" are defined in "" options "" indicating parameter values that can be selected by the user. This indicates that the list of parameter values that can be selected by the user is "" Each Pages "" and "" Special Pages "".

In the input definition 1220, "ext" is defined in "" inputType "" indicating the input method of the parameter value. This indicates that the user is required to enter the parameter value in text (character).

Further, in the input definition 1220, "100" is used for "" max "" indicating the upper limit (upper limit value) of the parameter value that can be input by the user, and "0" is used for "" min "" indicating the lower limit (lower limit value). Is defined. This indicates that the parameter value that can be input by the user is a numerical value of 0 or more and 100 or less.

As described above, the user input parameter 1208 defines the parameter information for which the user inputs the parameter value on the application screen, the parameter value input method, the input constraint, and the like.

As described above, the application setting information 1200 includes display information (for example, title) displayed on the application screen, input items (items for inputting or selecting parameter values) on the application screen, input methods for the input items, and input. Constraints etc. are defined. Further, in the application setting information 1200, parameter information in which parameter values are set by default (that is, parameter information in which parameter values are not input or selected on the application screen) and the like are defined.

When the browser 310 creates the application setting information 1200, the browser 310 transmits an application registration request to the application registration unit 142 of the portal service unit 140 (step S811). The application registration request includes the application setting information 1200 created in step S810.

When the application registration unit 142 of the portal service unit 140 receives the application registration request, the application registration unit 142 transmits the registration request to the application management unit 111 of the input / output service processing unit 110 (step S812).

Upon receiving the application registration request, the application management unit 111 of the input / output service processing unit 110 registers the application (step S813). Then, the application management unit 111 returns the registration result to the browser 310.

That is, the application management unit 111 stores the application setting information 1200 included in the application registration request in the application information storage unit 150 in association with the application ID. Then, the application management unit 111 returns the registration result including the application ID to the browser 310.

As a result, the application information 1000 including the application setting information 1200 and the processing flow information 1100 of the flow name defined in the flow name 1205 of the application setting information 1200 is registered in the service providing system 10.

Next, when the registration result is returned, the browser 310 displays, for example, the test screen G700 shown in FIG. 16 (step S814).

The test screen G700 shown in FIG. 16 is a screen for executing the test of the application registered in the above-mentioned step S813. The user can evaluate the application (operation check, etc.) by executing the test of the application.

The test screen G700 shown in FIG. 16 includes a “test execution” button G710. Here, it is assumed that the user has performed an operation (test execution operation) of pressing the "test execution" button G710. Then, the browser 310 accepts the test execution operation (step S815).

When the browser 310 receives the test execution operation, the browser 310 performs the test execution process (step S816). In the test execution process, a test case for testing the application (that is, a combination of parameter information used in the processing flow) is generated, and the application is tested for each test case. The application test is performed by executing the processing flow of the application (that is, a series of processing based on the processing flow information 1100 included in the application information 1000) for each combination of the parameter information indicated by the test case. The details of the test execution process will be described later.

Then, when the test execution process is completed, the browser 310 displays, for example, the test result screen G800 shown in FIG. 17A or the test result screen G900 shown in FIG. 17B (step S817).

The test result screen G800 shown in FIG. 17A is a test result screen when the application test is successful (that is, when the test is completed normally in all the test cases).

On the other hand, the test result screen G900 shown in FIG. 17B is a test result screen when the application test fails (that is, when the test fails in at least one test case). The test result screen G900 shown in FIG. 17B includes a failure test case display column G810.

The failure test case display column G810 includes the execution time of the test case in which the test failed and the parameter information used for the test. This allows the user to know the combination of parameter information used in the test case where the test failed. This allows the user to modify the parameter information so that the test is successful. The parameter information displayed in the failure test case display column G810 is displayed based on the test result information stored in the test result information storage unit 180.

Here, the details of the process (test execution process) in step S816 will be described with reference to FIG. FIG. 18 is a sequence diagram showing an example of the test execution process according to the present embodiment.

First, when the browser 310 receives the test execution operation, it transmits a request for acquiring the application settings to the screen configuration unit 121 of the Web service processing unit 120 (step S1801). The application setting acquisition request includes the application ID returned from the application management unit 111 in step S813.

When the screen configuration unit 121 of the Web service processing unit 120 receives the application setting acquisition request, the screen configuration unit 121 transmits the acquisition request to the application management unit 111 of the input / output service processing unit 110 (step S1802).

Upon receiving the application setting acquisition request, the application management unit 111 of the input / output service processing unit 110 acquires the application setting information 1200 stored in association with the application ID included in the acquisition request from the application information storage unit 150. (Step S1803). Then, the application management unit 111 returns the application setting information 1200 acquired from the application information storage unit 150 to the screen configuration unit 121.

The screen configuration unit 121 of the Web service processing unit 120 acquires the application screen information 2000 for displaying the test result screen G800 and the test result screen G900 from the application screen information storage unit 160 (step S1804). Then, the screen configuration unit 121 returns the application screen information 2000 acquired from the application screen information storage unit 160 and the application setting information 1200 returned in step S1803 to the browser 310.

When the application screen information 2000 and the application setting information 1200 are returned, the browser 310 generates a test case by combining the parameter information from the application setting information 1200 by a method such as the all-pair method (pairwise method). (Step S1805).

For example, when the application setting information 1200 shown in FIG. 15 is returned, a test case is generated by combining the parameter information defined in the default parameter 1207 and the parameter information defined in the user input parameter 1208. ..

Specifically, "" language ":" English "" is defined in the default parameter 1207. Therefore, first, "" English "" is used as the parameter value of the parameter information of the parameter name "" language "".

Further, in the input definition 1210 of the user input parameter 1208, the selectable parameter values "" Each Pages "" and "" Special Pages "" of "" division Page Range "" are defined. Therefore, "" Each Pages "" and "" Special Pages "" are used as the parameter values of the parameter information of the parameter name "" division Page Range "".

Further, in the input definition 1220 of the user input parameter 1208, the upper limit value "100" and the lower limit value "0" of the parameter value of "" divisionPageNumbers "" are defined. Therefore, the upper limit value "100" and the lower limit value "0" are used as the parameter values of the parameter information of the parameter name "" divisionPageNumbers "".

Therefore, by combining the parameter values of the above parameter information, the four test cases shown in FIGS. 19A to 19D are generated. In this way, the test case is generated by combining the parameter values of one or more parameter information defined in the application setting information 1200. At this time, for example, when the parameter values are selectively defined, these selectively defined parameter values may be combined. Further, when the range in which the parameter value can be taken is defined, the parameter values such as the upper limit value, the lower limit value, and the intermediate value of the range may be combined.

In addition, there is also parameter information in which an arbitrary character string input by the user becomes a parameter value, for example, when the user is required to input a file name. Specifically, it is parameter information such that an arbitrary character string input by the user is used as a parameter value, such as the parameter information of the parameter name "" filename "" shown in FIG. 20 (a). In this case, for example, the browser 310 may generate a test case by combining a randomly generated character string as a parameter value of the parameter information with a parameter value of other parameter information.

Further, in the case of parameter information such as the parameter information of the parameter name "" filename "" shown in FIG. 20B, in which a character string of 0 characters or more and 100 characters or less is used as the parameter value, 0 characters or more. , And a character string of 100 characters or less may be randomly generated.

Further, when the default parameter value is defined in the processing flow information 1100, a test case may be generated in which the parameter information of the parameter value is also combined. For example, in the detailed processing definition 1110 of the processing flow information 1100 shown in FIG. 7, "" A4 "" is defined as the default parameter value of the parameter information of the parameter name "" outputSize "". Therefore, in this case, even if the test case is generated by combining the parameter information "" outputSize ":" A4 "" defined in the processing flow information 1100 in addition to the parameter information defined in the application setting information 1200. good.

Subsequent processes of steps S1806 to S1809 are executed for each test case generated in step S1805.

The browser 310 transmits an application execution request to the application execution unit 122 of the Web service processing unit 120 for each test case generated in step S1805 (step S1806). The application execution request includes the application ID, the flow name "ocr-divide" defined in the flow name 1205 of the application setting information 1200, the electronic file used for the test, and the parameter information indicated by the test case. Is included.

Here, the electronic file used for the test is, for example, dummy electronic data for the test.

Further, the parameter information indicated by the test case is a combination of the parameter information generated in step S1805.

For example, in the test case 1 shown in FIG. 19 (a), the parameter information includes "" language ":" English "", "" division Page Range ":" Each Pages "", and "" division Page Numbers ": 0". included.

Further, for example, in the test case 2 shown in FIG. 19 (b), as parameter information, "" language ":" English "", "" division Page Range ":" Each Pages "", and "" division Page Numbers ": 100". And are included.

Similarly, for example, in the test case 3 shown in FIG. 19 (c), as parameter information, "" language ":" English "", "" division Page Range ":" Special Pages "", and "" division Page Numbers ": 0. "Is included.

Similarly, for example, in the test case 4 shown in FIG. 19 (d), as parameter information, "" language ":" English "", "" division Page Range ":" Special Pages "", and "" division Pages "". : 100 ”is included.

When the application execution unit 122 of the Web service processing unit 120 receives the execution request of the application, the application execution unit 122 transmits the execution request to the logic processing unit 112 of the input / output service processing unit 110 (step S1807).

When the logic processing unit 112 of the input / output service processing unit 110 receives the execution request of the application, the logic processing unit 112 performs the execution processing of the processing flow (step S1808). That is, the logic processing unit 112 executes a series of processing based on the processing flow information 1100 of the flow name included in the request by using the parameter information included in the request. In this way, the test is performed by actually executing a series of processes based on the process flow information 1100 using the parameter information indicated by the test case. The details of the execution processing of the processing flow will be described later.

Then, the logic processing unit 112 returns the processing result of the execution processing of the processing flow to the application execution unit 122 of the Web service processing unit 120.

When the application execution unit 122 of the Web service processing unit 120 receives the processing result from the logic processing unit 112, the application execution unit 122 creates test result information based on the application ID, the test case, and the processing result, and the test result information storage unit. It is stored in 180 (step S1809). Then, the application execution unit 122 returns the processing result to the browser 310.

Here, the test result information created and stored by the application execution unit 122 will be described with reference to FIG. FIG. 21 is a diagram showing an example of test result information.

As shown in FIG. 21, the test result information includes an application ID, a test execution date, a final test result, a test case, and a test case result.

The app ID is the app ID of the tested application. The test execution date is the date when the test was conducted. The final test result is the final test result, and is "OK" when all the test case results are "OK". On the other hand, the final test result is "NG" when at least one test case result is "NG".

A test case is a tested test case (ie, a combination of parameter information). The test case result is a test result for each test case.

In this way, the test result information is associated with the final test result and the test result for each test case for each application tested.

As described above, in the information processing system 1 according to the present embodiment, the user can easily register the application (application information 1000) by setting, for example, the flow name and the parameter information of each component using the PC terminal 30. can do.

Moreover, in the information processing system 1 according to the present embodiment, when registering an application or modifying / updating an application, the processing flow of the application (that is, the processing flow based on the processing flow information 1100 included in the application information 1000) is performed. Can be tested. As a result, for example, it is possible to confirm whether or not the parameter value of the parameter information defined in the application setting information 1200 is correct, and evaluate the operation confirmation of the registered application and the modified / updated application. You will be able to do it.

Therefore, according to the information processing system 1 according to the present embodiment, for example, an application that provides various services even to a user (for example, a person in charge of planning) who does not have specialized knowledge or experience of a programming language or the like. Can be easily registered and tested.

In the present embodiment, the case where the test is executed for the registered application has been described. However, for example, the test may be executed before the registration and only the application whose test is successful may be allowed to be registered. ..

Here, as shown in FIG. 20, there is also parameter information in which a parameter value is input by the user. That is, when testing the processing flow of the application, the parameter value input by the user may affect the execution result of the processing flow. In such a case, if the parameter value input by the user does not exist, for example, the execution of the processing flow may fail or the processing flow may end abnormally in the middle. The parameter values input by the user include, for example, an email destination address, authentication information of an external cloud service, and the like.

Therefore, the test execution process in consideration of the case where the user needs to input the parameter value will be described with reference to FIG. 22. FIG. 22 is a sequence diagram showing another example of the test execution process according to the first embodiment. Since the processes of steps S2201 to S2204 and steps S221 to S2214 of FIG. 22 are the same as the processes of steps S1801 to S1804 and steps S1806 to S1809 of FIG. 18, the description thereof will be omitted.

Following step S2204, when the application screen information 2000 and the application setting information 1200 are returned, the browser 310 transmits a processing flow information acquisition request to the application management unit 111 (step S2205). The acquisition request includes the flow name defined in the flow name 1205 of the application setting information 1200.

When the application management unit 111 receives the acquisition request for the processing flow information, the application management unit 111 acquires the processing flow information 1100 of the flow name included in the acquisition request from the application information storage unit 150 (step S2206). Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 150 to the browser 310.

Subsequent processes in step S2207 are executed for each operation executed by the process flow based on the process flow information 1100. That is, it is executed for each operation name defined in "" operationName "" of the processing flow information 1100.

The browser 310 refers to at least one of the processing flow information 1100 and the application setting information 1200, and whether or not there is parameter information that requires the user to input the parameter value for the parameter information corresponding to the corresponding operation name. Is determined (step S2207). The browser 310 may determine, for example, whether or not there is parameter information that requires the user to input a parameter value for the parameter information corresponding to the corresponding operation name according to the following (1) to (4). good.

(1) The browser 310 refers to the processing flow information 1100 and determines whether or not a flag (user input flag) indicating that the user is required to input the parameter value is defined in the parameter information. In this case, if the user input flag is not defined in the parameter information, it may be determined that the user is required to input the parameter value of the parameter information.

(2) The browser 310 refers to the processing flow information 1100 and determines whether or not there is parameter information for which a default value is not defined. In this case, if there is parameter information for which the default value is not defined, it may be determined that the user is required to input the parameter value of the parameter information.

The default value of the parameter information may be defined in the application setting information 1200. Therefore, in this case, regarding the parameter information for which the default value is not defined in the processing flow information 1100, it is determined that the user is required to input the parameter value of the parameter information when the default value is not defined in the application setting information 1200. You may.

(3) The browser 310 refers to the processing flow information 1100 and determines whether or not there is parameter information in which the user input flag is defined and the default value is not defined. In this case, if there is parameter information in which the user input flag is defined and the default value is not defined, it may be determined that the parameter value of the parameter information is input. In this case as well, similarly to the above (2), if the default value is not defined in the application setting information 1200, it may be determined that the user is to input the parameter value of the parameter information.

(4) The browser 310 refers to the application setting information 1200 and determines whether or not the parameter information is defined in the user input parameter 1208. In this case, when the parameter information is defined in the user input parameter 1208, it may be determined that the user is to input the parameter value of the parameter information. The browser 310 may perform the determination according to (4) in addition to the determinations (1) to (3) above.

In step S2207, when it is determined that there is parameter information that requires the user to input the parameter value for the parameter information corresponding to the corresponding operation name, the subsequent processes of steps S2208 to S2209 are executed.

The browser 310 displays a parameter input screen for causing the user to input the parameter value of the parameter information (step S2208). Here, an example of the parameter input screen is shown in FIG. FIG. 23 is a diagram showing an example of a parameter input screen.

The parameter input screen G950 shown in FIG. 23 is a screen for inputting the parameter value of the parameter information “To” used for the processing of the operation name “mail transmission 1”. The user can specify the parameter value of the parameter information by pressing the OK button G952 after inputting the parameter value in the parameter input field G951.

Next, the browser 310 updates the parameter value of the parameter information defined in the processing flow information 1100 with the parameter value specified by the user on the parameter input screen displayed in step S2208 above (step S2209). .. As a result, the parameter value of the parameter information defined in the processing flow information 1100 is set to the parameter value input by the user.

By the processing of steps S2207 to S2209, the user can be made to input the parameter value for the parameter information that needs to be input by the user among the parameter information defined in the processing flow information 1100. ..

The browser 310 generates a test case from the application screen information 2000, the application setting information 1200, and the processing flow information 1100 by combining parameter information by a method such as an all-pair method (pairwise method) (step S2210).

As described above, in the information processing system 1 according to the present embodiment, when testing the processing flow of the application, the user can be made to input the parameter value of the parameter information. As a result, it is possible to prevent abnormal termination of the processing flow due to no parameter value being specified.

Next, the details of the process (execution process of the process flow) in step S1808 of FIG. 18 will be described with reference to FIG. 24. FIG. 24 is a sequence diagram showing an example of execution processing of a processing flow that realizes the OCR division service.

First, when the flow execution unit 301 receives the application execution request from the application execution unit 122, the flow execution unit 301 transmits the processing flow information acquisition request to the application management unit 111 (step S2401). The acquisition request includes the flow name "ocr-divide".

When the application management unit 111 receives the acquisition request for the processing flow information, the application management unit 111 acquires the processing flow information 1100 of the flow name "ocr-divide" included in the acquisition request from the application information storage unit 150 (step S2402). Then, the application management unit 111 returns the processing flow information 1100 acquired from the application information storage unit 150 to the flow execution unit 301.

Hereafter, the application management unit 111 will be described as having returned the processing flow information 1100 shown in FIG. 7 to the flow execution unit 301.

Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S2403).

That is, the flow execution unit 301 requests the acquisition of the component with the component name "" OCR "" defined in "" component "" included in the detailed processing definition 1110 of the processing flow information 1100 shown in FIG. 7. Send to 302.

Upon receiving the component acquisition request, the component management unit 302 generates a component having the component name "" OCR "" (that is, the OCR component 1310) (step S2404). The OCR component 1310 can be generated by using the API for generating the component defined in the component common I / F 1300.

Then, the component management unit 302 returns the generated OCR component 1310 to the flow execution unit 301. That is, the component management unit 302 returns, for example, the address on the memory (for example, RAM 14) in which the OCR component 1310 is expanded to the flow execution unit 301.

Next, the flow execution unit 301 transmits the component execution request to the OCR component 1310 (step S2405). The execution request includes data and parameter information.

Here, the data is an electronic file included in the execution request of the application received as the data type "InputStream". That is, the flow execution unit 301 passes the received electronic file as "data" (without being aware of the data type) to the OCR component 1310 and requests execution of the process. In the present embodiment, various types of information such as electronic files that are not conscious of the data type are simply referred to as "data". Further, the parameter information is the parameter information included in the execution request of the application.

Upon receiving the component execution request, the OCR component 1310 transmits the type conversion request to the type conversion management unit 304 (step S2406). The type conversion request includes data and designation of "LocalFilePath" indicating a data type that can be handled by the OCR component 1310.

Upon receiving the type conversion request, the type conversion management unit 304 checks whether or not the data type of the data included in the type conversion request matches the designated data type (step S2407).

Here, the data type of the data included in the type conversion request is "InputStream", while the specified data type is "LocalFilePath". Therefore, the type conversion management unit 304 determines that the data type of the data included in the type conversion request does not match the designated data type.

Then, the type conversion management unit 304 refers to the type conversion information table 4000 and specifies the type conversion for converting the data type "InputStream" to "LocalFilePath" (here, the first type conversion 1410 is specified). Will be.). Then, the type conversion management unit 304 generates the specified first type conversion 1410 (step S2408). The first type conversion 1410 can be generated by using the type conversion common I / F 1400.

Next, the type conversion management unit 304 transmits the execution request of the type conversion process to the first type conversion 1410 (step S2409). The execution request includes data.

Upon receiving the type conversion execution request, the first type conversion 1410 performs a type conversion process of converting the data type of the data included in the execution request from "Input Stream" to "Local File Path" (step S2410). Then, the first type conversion 1410 returns the data whose data type has been converted to the type conversion management unit 304.

When the type conversion management unit 304 receives the data from the first type conversion 1410, the type conversion management unit 304 transmits the data to the OCR component 1310 (step S2411).

When the OCR component 1310 receives the data from the type conversion management unit 304, the OCR component 1310 executes a process on the data using the parameter information (step S2412).

For example, when the execution request of the application includes the parameter information "" language ":" English "", the OCR component 1310 uses the parameter information in the electronic file indicated by the data by the OCR processing unit 131. On the other hand, OCR processing is performed in English.

Then, the OCR component 1310 returns the data indicating the electronic file (that is, the PDF file with text) after the OCR processing to the flow execution unit 301.

Next, the flow execution unit 301 transmits a component acquisition request based on the processing flow information 1100 to the component management unit 302 (step S2413).

That is, the flow execution unit 301 requests the acquisition of the component with the component name "" PDF "" defined in "" component "" included in the detailed processing definition 1120 of the processing flow information 1100 shown in FIG. 7. Send to 302.

Upon receiving the component acquisition request, the component management unit 302 generates a component having the component name "" PDF "" (that is, the PDF component 1320) (step S2414). The PDF component 1320 can be generated by using the API for generating the component defined in the component common I / F 1300.

Then, the component management unit 302 returns the generated PDF component 1320 to the flow execution unit 301. That is, the component management unit 302 returns, for example, the address on the memory (for example, RAM 14) in which the PDF component 1320 is expanded to the flow execution unit 301.

Next, the flow execution unit 301 transmits the component execution request to the PDF component 1320 (step S2415). The execution request includes data and parameter information.

Here, the data is the data returned from the OCR component 1310 (that is, the path indicating the electronic file (PDF file with text) after the OCR processing).

When the PDF component 1320 receives the component execution request, it transmits the type conversion request to the type conversion management unit 304 (step S2416). The type conversion request includes data and designation of "LocalFilePath" indicating a data type that can be handled by the PDF component 1320.

Upon receiving the type conversion request, the type conversion management unit 304 checks whether or not the data type of the data included in the type conversion request matches the designated data type (step S2417).

Here, the data type of the data included in the type conversion request is "LocalFilePath", and the designated data type is also "LocalFilePath". Therefore, the type conversion management unit 304 determines that the data type of the data included in the type conversion request matches the designated data type.

Then, the type conversion management unit 304 transmits the data included in the type conversion request to the PDF component 1320 (step S2418). In this way, when it is determined in the data type check (process in step S2417) that the data type of the data matches the specified data type, the type conversion management unit 304 generates the type conversion. Not performed.

When the PDF component 1320 receives the data from the type conversion management unit 304, the PDF component 1320 executes a process on the data using the parameter information (step S2419).

For example, it is assumed that the execution request of the application includes the parameter information "" division Page Range ":" Each Pages "" and the parameter information "" division Page Numbers ": 100". In this case, the PDF component 1320 uses these parameter information to perform the division processing of the electronic file (PDF with text) indicated by the data. Specifically, in this case, the PDF component 1320 divides each page after the page number "100" to create a PDF file with text.

Then, the PDF component 1320 returns the data indicating the electronic file after the division process to the flow execution unit 301.

As a result, the execution of a series of processes (process flows) based on the process flow information 1100 shown in FIG. 7 is completed. Thereby, the service providing system 10 according to the present embodiment can test the processing flow for realizing the service (OCR division service) provided by the OCR division application for each test case. Further, as will be described later, the OCR division service can be provided to the device 20.

Next, a case where the user of the device 20 uses the OCR division service will be described with reference to FIG. 25. FIG. 25 is a sequence diagram showing an example of overall processing when the OCR division service is used.

First, the browser 210 of the device 20 accepts an operation (display operation) for displaying the application screen of the OCR division service (step S2501). The user of the device 20 can perform the display operation of the application screen by inputting the URL of the application screen of the OCR division service into the address bar of the browser 310, for example.

When the browser 210 of the device 20 receives the display operation of the application screen of the OCR division service, it transmits a display request of the application screen of the OCR division service to the screen configuration unit 121 of the Web service processing unit 120 (step S2502). The display request of the application screen of the OCR division service includes the application ID of the application information 1000 that provides the OCR division service.

When the screen configuration unit 121 of the Web service processing unit 120 receives the display request of the application screen of the OCR division service, the screen configuration unit 121 transmits the application setting acquisition request to the application management unit 111 of the input / output service processing unit 110 (step S2503). .. The application setting acquisition request includes the application ID of the application information 1000 that provides the OCR division service.

Upon receiving the application setting acquisition request, the application management unit 111 of the input / output service processing unit 110 acquires the application setting information 1200 stored in association with the application ID included in the acquisition request from the application information storage unit 150. (Step S2504). Then, the application management unit 111 returns the application setting information 1200 acquired from the application information storage unit 150 to the screen configuration unit 121.

The screen configuration unit 121 of the Web service processing unit 120 acquires the application screen information 2000 stored in association with the application ID of the application information 1000 that provides the OCR division service from the application screen information storage unit 160 (step S2505). Then, the screen configuration unit 121 returns the application screen information 2000 acquired from the application screen information storage unit 160 and the application setting information 1200 returned in step S2504 to the browser 210.

The browser 210 of the device 20 displays, for example, the application screen G1000 shown in FIG. 26 based on the application screen information 2000 and the application setting information 1200 received from the screen configuration unit 121 (step S2506).

Here, the application screen G1000 shown in FIG. 26 is a screen for the user of the device 20 to use the OCR division service.

The application screen G1000 shown in FIG. 26 includes an application name G1010, a parameter value input area G1020, and a "start" button G1030. Further, the parameter value input area G1020 includes a division method input field G1021 and a division start page start number input field G1022.

The application name G1010 is displayed based on the application display name 1203 of the application setting information 1200 shown in FIG. When application names (titles) of a plurality of languages are defined in the application display name 1203, the application name of the language corresponding to the language setting of the browser 210 is displayed in the application name G1010.

Further, the division method input field G1021 and the division start page start number input field G1022 are displayed based on the user input parameter 1208 of the application setting information 1200 shown in FIG.

That is, the division method input field G1021 is displayed based on the input definition 1210 of the user input parameter 1208. Similarly, the split start page start number input field G1022 is displayed based on the input definition 1220 of the user input parameter 1208.

As described above, on the application screen for the user of the device 20 to use the service, the "application name and parameter value" input area is displayed based on the information defined in the application setting information 1200.

Here, in the application screen G1000 shown in FIG. 26, the user inputs (selects) a parameter value in the division method input field G1021 and the division start page start number input field G1022, and then presses the "start" button G1030. It is assumed that (execution operation) has been performed.

Then, the browser 210 of the device 20 accepts the execution operation (step S2507). Then, the browser 210 of the device 20 controls the scanner 26 to read the original and generate an electronic file (image file) (step S2508).

When the electronic file (image file) is generated, the browser 210 of the device 20 transmits an application execution request to the application execution unit 122 of the Web service processing unit 120 (step S2509). The application execution request includes the flow name "ocr-divide" defined in the flow name 1205 of the application setting information 1200, the electronic file generated in the above step S2508, and the parameter information.

Here, the parameter information is the parameter information defined in the default parameter 1207 of the application setting information 1200, and the parameter information in which the parameter value is input by the user on the application screen G1000.

When the application execution unit 122 of the Web service processing unit 120 receives the execution request of the application, the application execution unit 122 transmits the execution request to the logic processing unit 112 of the input / output service processing unit 110 (step S2510).

When the logic processing unit 112 of the input / output service processing unit 110 receives the execution request of the application, the logic processing unit 112 performs the execution processing of the processing flow (step S2511). That is, the logic processing unit 112 performs the execution processing of the processing flow described with reference to FIG. 24.

Then, the logic processing unit 112 returns the processing result of the execution processing of the processing flow to the browser 210 via the Web service processing unit 120. As a result, the service providing system 10 according to the present embodiment can provide the OCR division service.

Here, in the test execution process described with reference to FIG. 18, a case where a test case is generated by the browser 310 has been described, but the present invention is not limited to this. The test case may be generated by the service providing system 10, for example. The test execution process when the test case is generated by the service providing system 10 will be described with reference to FIG. 27. FIG. 27 is a sequence diagram showing another example of the test execution process according to the first embodiment. Since the processes of steps S2706 to S2709 of FIG. 27 are the same as the processes of steps S1806 to S1809 of FIG. 18, the description thereof will be omitted.

First, when the browser 310 receives the test execution operation, it transmits a test case generation request to the screen configuration unit 121 of the Web service processing unit 120 (step S2701). The test case generation request includes the application ID returned from the application management unit 111 in step S813 of FIG.

When the screen configuration unit 121 of the Web service processing unit 120 receives the test case generation request, the screen configuration unit 121 transmits the generation request to the application management unit 111 of the input / output service processing unit 110 (step S2702).

Upon receiving the test case generation request, the application management unit 111 of the input / output service processing unit 110 acquires the application setting information 1200 stored in association with the application ID included in the generation request from the application information storage unit 150. (Step S2703).

Next, the application management unit 111 of the input / output service processing unit 110 generates a test case from the application setting information 1200 acquired in the above step S2703 (step S2704). The test case generation method is the same as in step S1805 of FIG.

Then, the application management unit 111 returns the generated test case to the screen configuration unit 121 of the Web service processing unit 120.

Upon receiving the test case, the screen configuration unit 121 of the Web service processing unit 120 acquires the application screen information 2000 for displaying the test result screen G800 and the test result screen G900 from the application screen information storage unit 160 (step S2705). .. Then, the screen configuration unit 121 returns the application screen information 2000 acquired from the application screen information storage unit 160 and the test case returned in step S2704 to the browser 310.

As described above, in the information processing system 1 according to the present embodiment, a test case may be generated by the service providing system 10 and returned to the browser 310.

[Second Embodiment]
Next, the second embodiment will be described. In the second embodiment, a case where a test case is generated based on information about each component (hereinafter, referred to as “component information”) will be described. As a result, for example, when the default parameter value is defined in the component information, it becomes possible to generate a test case considering this default parameter value.

In the second embodiment, the differences from the first embodiment will be mainly described, and the description of the components substantially the same as those of the first embodiment will be omitted as appropriate. To do.

<Functional configuration>
First, the functional configuration of the information processing system 1 according to the present embodiment will be described with reference to FIG. 28. FIG. 28 is a diagram showing an example of the functional configuration of the information processing system 1 according to the present embodiment.

The service providing system 10 shown in FIG. 28 further includes a component information storage unit 190. The storage unit can be realized by using the HDD 18. The storage unit may be realized by using a storage device or the like connected to the service providing system 10 via a network.

The component information storage unit 190 stores the component information 1500. In the component information 1500, various information related to the component (for example, an operation that can be executed by the component, parameter information used to execute the operation, and the like) is defined.

<Details of processing>
Next, the details of the processing of the information processing system 1 according to the present embodiment will be described. Hereinafter, the details of the test execution process according to the present embodiment will be described with reference to FIG. 29. FIG. 29 is a sequence diagram showing an example of the test execution process according to the present embodiment. Since the processes of steps S291 to S2913 of FIG. 29 are the same as the processes of steps S1806 to S1809 of FIG. 18, the description thereof will be omitted.

First, when the browser 310 receives the test execution operation, it transmits a request for acquiring the application settings to the screen configuration unit 121 of the Web service processing unit 120 (step S2901). The application setting acquisition request includes the application ID returned from the application management unit 111 in step S813 of FIG.

When the screen configuration unit 121 of the Web service processing unit 120 receives the application setting acquisition request, the screen configuration unit 121 transmits the acquisition request to the application management unit 111 of the input / output service processing unit 110 (step S2902).

Upon receiving the application setting acquisition request, the application management unit 111 of the input / output service processing unit 110 acquires the application setting information 1200 stored in association with the application ID included in the acquisition request from the application information storage unit 150. (Step S2903).

Here and thereafter, it is assumed that the application setting information 1200 shown in FIG. 30 has been acquired in step S2903. In the application setting information 1200 shown in FIG. 30, the input definition 1210 of the user input parameter 1208 is different from that in FIG. That is, in the parameter information "" divisionPageRanger "" in the input definition 1210 of the application setting information 1200 shown in FIG. 30, "" text "" is defined in "" inputType "".

Next, the application management unit 111 of the input / output service processing unit 110 identifies the component name and the operation name from the processing flow information 1100 corresponding to the flow name 1205 of the application setting information 1200 acquired in step S2903 above (step). S2904).

For example, it is assumed that "ocr-divide" is defined in the flow name 1205 of the application setting information 1200 acquired in step S2903. In this case, the application management unit 111 specifies the component name “OCR” and the operation name “process” from the detailed processing definition 1110 of the processing flow information 1100 shown in FIG. Similarly, the application management unit 111 specifies the component name "PDF" and the operation name "divideByPageNumbers" from the detailed processing definition 1120 of the processing flow information 1100 shown in FIG. 7.

Then, the application management unit 111 returns the application setting information 1200 acquired in step S2903 and the component name and operation name specified in step S2904 to the screen configuration unit 121 of the Web service processing unit 120.

The screen configuration unit 121 of the Web service processing unit 120 acquires the application screen information 2000 for displaying the test result screen G800 and the test result screen G900 from the application screen information storage unit 160 (step S2905). Then, the screen configuration unit 121 returns the application screen information 2000 acquired from the application screen information storage unit 160, the application setting information 1200 returned in the above step S2904, and the component name and the operation name to the browser 310.

When the application screen information 2000, the application setting information 1200, the component name and the operation name are returned, the browser 310 transmits a component information acquisition request to the application execution unit 122 of the Web service processing unit 120 (step). S2906). The component information acquisition request includes the component name returned from the screen configuration unit 121.

When the application execution unit 122 of the Web service processing unit 120 receives the component information acquisition request, the application execution unit 122 transmits the acquisition request to the logic processing unit 112 of the input / output service processing unit 110 (step S2907).

Upon receiving the component information acquisition request, the logic processing unit 112 of the input / output service processing unit 110 acquires the component information 1500 of the component name included in the acquisition request from the component information storage unit 190 (step S2908).

For example, suppose that the component names included in the component information acquisition request are "OCR" and "PDF". In this case, the logic processing unit 112 acquires the component information 1500 of the component name “OCR” and the component information 1500 of the component name “PDF”.

Here, FIG. 31 shows an example of the component information 1500 having the component name “OCR”. The component information 1500 shown in FIG. 31 includes a component name 1501, an operation name 1502, and a parameter definition 1503.

In the parameter definition 1503, "" name "" indicating a parameter name, "" defaultValue "" indicating a default parameter value, and "optionValues" indicating a settable parameter value are defined.

Then, the logic processing unit 112 returns the acquired component information 1500 to the browser 310 via the application execution unit 122.

When the component information 1500 is returned, the browser 310 combines the parameter information from the application setting information 1200, the component information 1500, and the operation name to generate a test case (step S2909).

For example, in the parameter information "" divisionPageRanger "" in the input definition 1210 of the application setting information 1200 shown in FIG. 30, only "" text "" is defined in "" inputType "". Therefore, it is unclear what kind of value can be taken as the parameter value of the parameter information "" divisionPageRanger "".

Therefore, in this case, the browser 310 generates a test case from the parameter definition 1503 of the component information 1500 shown in FIG. 31 by using the default parameter value "" Each Pages "" of the parameter information "" division Page Range "".

In this way, for example, when an appropriate parameter value is not defined for the application setting information 1200, the browser 310 generates a test case using the default parameter value defined in the component information 1500. As a result, in the information processing system 1 according to the present embodiment, for example, a test using the parameter value is performed for an application in which the default parameter value defined in the component information 1500 is used in the execution of the processing flow. Will be able to.

The present invention is not limited to the above-described embodiment disclosed specifically, and various modifications and modifications can be made without departing from the scope of claims.

1 Information processing system 10 Service provision system 20 Equipment 30 PC terminal 110 Input / output service processing unit 111 Application management unit 112 Logic processing unit 120 Web service processing unit 121 Screen configuration unit 122 Application execution unit 130 Document service unit 131 OCR processing unit 140 Portal Service unit 141 UI provider 142 Application registration unit 150 Application information storage unit 160 Application screen information storage unit 170 Portal screen information storage unit 180 Test result information storage unit 210 Browser 310 Browser 301 Flow execution unit 302 Component management unit 303 Component group 304 type Conversion management unit 305 type conversion group 1000 application information 1100 processing flow information 1200 application setting information 2000 application screen information 3000 portal screen information 4000 type conversion information table

Japanese Patent No. 4039191

Claims (9)

An information processing system including one or more information processing devices and having a plurality of programs that execute predetermined processes.
For each application that executes a series of processes using electronic data, a program identification information that identifies one or more programs that execute each process of the series of processes and an execution order of one or more programs are defined. An application storage means for storing the application in which the generated flow information is associated with the application setting information in which the parameter information used for executing each of the one or more programs and the flow identification information for identifying the flow information are defined. ,
A receiving means for receiving a registration request including the application setting information created in one of one or more electronic devices connected to the information processing system.
Based on the parameter information defined in the application setting information included in the registration request received by the receiving means, a test case showing a combination of the parameter information for testing the execution of the series of processes is generated. Generation means and
An acquisition means for acquiring the flow information identified by the flow identification information defined in the application setting information included in the registration request from the application storage means, and
Each of the one or more programs identified by the program identification information defined in the flow information acquired by the acquisition means is generated by the generation means according to the execution order defined in the flow information. An execution means for testing the execution of the series of processes by executing the combination of the parameter information indicated by the test case.
Information processing system with. It has an application registration means for storing the application setting information received by the receiving means in the application storage means in association with the flow information identified by the flow identification information defined in the application setting information.
The generation means
The information processing system according to claim 1, wherein the test case is generated based on the parameter information defined in the application setting information registered by the application registration means. When the test by the execution means is successful, the application storage means associates the application setting information received by the receiving means with the flow information identified by the flow identification information defined in the application setting information. The information processing system according to claim 1, wherein the information processing system has an application registration means for storing the information. The generation means
The parameter information in which the boundary value of the range is set as the parameter value based on the parameter information defined in the application setting information and the information indicating the range of the parameter value that can be set for the parameter information. The information processing system according to any one of claims 1 to 3, wherein the test case including the above is generated. The generation means
The test case is based on the parameter information defined in the application setting information and the parameter information defined in the flow information identified by the flow identification information defined in the application setting information. The information processing system according to any one of claims 1 to 4, wherein the information processing system is generated. The generation means
At least one of the parameter information defined in the application setting information and the parameter information defined in the flow information identified by the flow identification information defined in the application setting information. The information processing system according to any one of claims 1 to 4, wherein the test case is generated based on the parameter information in which the parameter value input by the user is set. It has a specific means for specifying the program identification information defined in the flow information identified by the flow identification information defined in the application setting information included in the registration request received by the receiving means.
The generation means
The test case is based on the parameter information defined in the application setting information and the parameter information defined in the information about the program identified by the program identification information specified by the specific means. The information processing system according to any one of claims 1 to 4, wherein the information processing system is generated. An information processing device having a plurality of programs that execute predetermined processes.
For each application that executes a series of processes using electronic data, a program identification information that identifies one or more programs that execute each process of the series of processes and an execution order of one or more programs are defined. An application storage means for storing the application in which the generated flow information is associated with the application setting information in which the parameter information used for executing each of the one or more programs and the flow identification information for identifying the flow information are defined. ,
A receiving means for receiving a registration request including the application setting information created in one of one or more electronic devices connected to the information processing device.
Based on the parameter information defined in the application setting information included in the registration request received by the receiving means, a test case showing a combination of the parameter information for testing the execution of the series of processes is generated. Generation means and
An acquisition means for acquiring the flow information identified by the flow identification information defined in the application setting information included in the registration request from the application storage means, and
Each of the one or more programs identified by the program identification information defined in the flow information acquired by the acquisition means is generated by the generation means according to the execution order defined in the flow information. An execution means for testing the execution of the series of processes by executing the combination of the parameter information indicated by the test case.
Information processing device with. An information processing system including one or more information processing devices and having a plurality of programs that execute predetermined processes, respectively, for each application that executes a series of processes using electronic data. Program identification information that identifies one or more of the programs that execute processing, flow information that defines the execution order of one or more of the programs, parameter information used for executing each of the one or more programs, and the above-mentioned In an information processing method used in an information processing system having an application storage means for storing the application associated with the application setting information in which the flow identification information for identifying the flow information is defined.
A receiving procedure for receiving a registration request including the application setting information created in one of one or more electronic devices connected to the information processing system, and a receiving procedure.
Based on the parameter information defined in the application setting information included in the registration request received by the receiving procedure, a test case showing a combination of the parameter information for testing the execution of the series of processes is generated. Generation procedure and
An acquisition procedure for acquiring the flow information identified by the flow identification information defined in the application setting information included in the registration request from the application storage means, and
Each of the one or more programs identified by the program identification information defined in the flow information acquired by the acquisition procedure is generated by the generation procedure according to the execution order defined in the flow information. An execution procedure for testing the execution of the series of processes by executing the combination of the parameter information indicated by the test case.
Information processing method having.

Images