JP5084665B2 - Component linkage scenario integrated development environment providing system, scenario creation support method, and program - Google Patents

Description

  The present invention relates to a component-linked scenario integrated development environment providing system, a scenario creation support method, and a program that support creation of a scenario in which a plurality of components are linked.

In recent years, a project to replace an existing telephone network with a next generation network (NGN) is being advanced. In NGN, the telephone network is converted to IP (Internet Protocol), which facilitates the linkage between the Web service and the telecom network, and is expected to create a new service. A web service is a service component (requested part) that is handled as a part for performing a service on the web.
Examples of a development tool for a service scenario (service cooperation application) that links such Web services include, for example, a service composition engine that is a service cooperation application development tool disclosed in Patent Document 1, and Microsoft Popfly (non-patent document 1). Registered trademark) has been proposed.
The service composition engine disclosed in Patent Document 1 proposes a service according to the user's preference and situation by the composition engine finding and executing various components based on a service execution scenario.
In addition, the technique disclosed in Non-Patent Document 1 creates an application that links service components on a browser. In addition, there are a function for solving input / output of a service component having a connection history based on past connection results, a recommendation function for a frequently used mashup service, and the like.
JP 2005-196676 A Microsoft popfly (registered trademark), [online], Microsoft Corporation, [searched on June 27, 2008], Internet <http://www.popfly.com/>

  However, in the above-described service composition engine, in order to describe a service template, it is necessary to create a scenario that links a plurality of Web services. Since the service scenario is created manually by the development user, it is difficult to create the service scenario depending on the skill and development experience of the development user.

  In the technology shown in Non-Patent Document 1 described above, when creating a service cooperation application, it is assumed that there is no change in input / output variables between the service components to be linked, and service components that can change the input / output variables. Has the problem of not being able to recommend. Therefore, when it is necessary to convert variables when linking service components in this way, the development user must create a conversion function using Extensible Stylesheet Language Transformations (XSLT). Learning will be required.

  Therefore, as described above, it is necessary to search for a service component to be connected and to resolve input / output conversion between service components in the development environment of the service cooperation application. For this reason, the development of the service integration application becomes complicated by the implementation of the input / output conversion solution for each searched service component for the development user. There is a problem of being one.

  The present invention has been made to solve the above-mentioned problems in consideration of such circumstances, and its purpose is to select and select service component candidates that match the service scenario image to be developed by the development user. An object is to provide a component linkage scenario integrated development environment providing system, a scenario creation support method, and a program that enable a development user to easily create a scenario for linking a plurality of service components.

  In order to solve the above problems, the present invention is based on a development support system that supports the creation of a scenario indicating a processing procedure in which a component cooperation scenario integrated development environment providing system cooperates a plurality of components providing a service, and the scenario A component-linked scenario integrated development environment providing system including an execution control system for executing linked processing of the component, wherein the development support system is a signal for requesting creation of a scenario including a main component as a component to be linked, In response to an input of a scenario creation request signal including identification information of the main component, a scenario development unit that generates a scenario for linking the main component with another component that is a linking component; Based on a scenario including a component as a component to be linked, a weight value indicating the degree of association between the main component and another component is calculated, the linked component is selected based on the calculated weight value, and the selected linked component A component cooperation scenario integrated development environment providing system, comprising: a component recommendation processing unit that outputs identification information to the scenario development unit.

  In addition, the component recommendation processing unit of the present invention calculates the weight value based on the number of linkages with the main component for each component.

  The execution control system of the present invention includes an execution history information storage unit that stores execution history information for each scenario, and executes a scenario according to an input of a scenario execution request, and executes execution history information of the executed scenario. A service control unit that writes to the execution history information storage unit, and the component recommendation processing unit calculates the weight value based on the number of times of cooperation execution with the main component for each of the components calculated based on the execution history information. It is characterized by that.

  In addition, the execution control system of the present invention executes a user information storage unit that stores user information of the scenario and scenario execution history information by the user in association with each other and an input of a scenario execution request. A service control unit for writing the scenario execution history information to the user information storage unit, and the scenario creation request signal received by the scenario development unit indicates target person information indicating an attribute of a provision target person of the scenario to be created The component recommendation processing unit reads scenario execution history information corresponding to the provision target person information from the user information storage unit, and based on the read scenario execution history information, the provision target person The number of times of cooperation execution with the main component executed by the component is calculated for each component, and the provided pair thus calculated is calculated. And calculates the weight values based on the coordination number of executions performed by the user.

  Further, the scenario development unit of the present invention is based on the scenario including the cooperation component corresponding to the identification information of the cooperation component input from the component recommendation processing unit, and the main component as components to be cooperated, A scenario for linking the main component and the linkage component is created.

Further, the scenario creation support method of the present invention includes a development support system that supports creation of a scenario indicating a processing procedure for coordinating a plurality of components that provide services, and an execution control system that executes cooperation processing of the components based on the scenario A scenario creation support method in a component linkage scenario integrated development environment providing system including the identification information of the main component as a signal for requesting creation of a scenario in which the development support system includes the main component as a component to be linked A weight value indicating the degree of association between the main component and other components is calculated based on the process of receiving a scenario creation request signal including the scenario including the main component as a component to be linked among a plurality of scenarios. , A process of selecting based-out collaboration components in weight value calculated is the scenario generation support method characterized in that it comprises a step of generating a scenario to link with the coordination components selected and the main component .

  The program of the present invention includes a development support system that supports creation of a scenario indicating a processing procedure for coordinating a plurality of components that provide services, and an execution control system that executes cooperation processing of the components based on the scenario. In response to the input of a scenario creation request signal including identification information of the main component as a signal requesting the creation of a scenario including the main component as a component to be linked with the computer of the development support system in the component linkage scenario integrated development environment providing system A scenario development unit that generates a scenario for linking the main component with another component that is a linkage component, and a scenario that includes the main component as a component to be linked among a plurality of scenarios. And calculating a weight value indicating the degree of association between the main component and another component, selecting the link component based on the calculated weight value, and outputting identification information of the selected link component to the scenario development unit It is a program characterized by functioning as a component recommendation processing unit.

According to the present invention, in the component cooperation scenario integrated development environment providing system, the component recommendation processing unit of the scenario development support system determines the degree of relevance to the main component based on the existing scenario that links the main component with other components. Based on the selected component, the scenario development department decided to create a scenario that links the selected component with the main component.
As a result, the component recommendation processing unit selects the component, so that the development user can create a scenario without searching for a component suitable for cooperation from many components to the main component. There is an effect that the time can be shortened.

Also, according to the present invention, the component recommendation processing unit calculates the weight value for each component based on the number of linkages with the main component.
As a result, a weight value corresponding to the number of linkages with the main component in the existing scenario can be calculated for each component as the degree of relevance. Therefore, it is possible to create a scenario including a component that is more suitable for linkage with the main component. There is an effect that it becomes possible.

Further, according to the present invention, the component recommendation processing unit calculates the weight value based on the number of times of cooperation with the main component for each component based on the execution history information of the scenario executed in the execution control system.
Thereby, since the weight value according to the number of times of cooperation can be calculated, there is an effect that it is possible to create a scenario including a component more suitable for cooperation with the main component.

  Further, according to the present invention, the execution control system includes a user information storage unit that stores scenario execution history information for each user of the executed scenario, and the component recommendation processing unit provides a scenario to be created The scenario execution history information corresponding to the target person attribute indicating the user attribute is read from the user information storage unit. The component recommendation processing unit can calculate the weight value according to the number of times of cooperation with the main component executed by the provider based on the read scenario execution history information. This makes it possible to create a scenario including components that are more suitable for the user.

Further, according to the present invention, the scenario development unit creates a scenario for linking the main component and the linked component based on the existing scenario including the linked component and the main component selected by the component recommendation processing unit. did.
Thus, the scenario development unit creates a scenario for linking the main component and the linked component based on the input / output conversion between the linked component and the main component described in the existing scenario. As a result, input / output conversion between service components can be resolved, so that it is possible to reduce the overall processing time required for scenario creation and the burden on the development user regardless of the scenario development skills of the development user. There is an effect of becoming.

A component cooperation scenario integrated development environment providing system 1 according to an embodiment of the present invention will be described below with reference to FIG.
FIG. 1 is a schematic block diagram showing a component cooperation scenario integrated development environment providing system 1 according to this embodiment. The component cooperation scenario integrated development environment providing system 1 includes a component 40-1 to 40-n that provides a Web service and a scenario 30 in which a procedure for linking a plurality of components 40-1 to 40-n is described. The execution control system 10 that executes the cooperation processing of the components 40-1 to 40-n based on the scenario 30 in response to the scenario use request from the user terminal device 3, and the scenario that responds to the scenario creation request from the development terminal device 2 A scenario development support system 20 as a development support tool is provided, and is connected to a development terminal device 2 and a user terminal device 3 as user terminal devices of the component cooperation scenario integrated development environment providing system 1.

The development terminal device 2 is a computer terminal connected to the scenario development support system 20 of the component cooperation scenario integrated development environment providing system 1, and is created in the scenario development support system 20 in accordance with the operation of the scenario development user. A scenario creation request including concept information is transmitted, and a response from the scenario development support system 20 is received.
The creation target scenario concept information is information indicating the characteristics of the scenario to be created. Here, the creation target scenario concept information is, for example, information including identification information of a main component input by an input operation by a development user and target person attribute information. .

  Here, the main component is a component included in the scenario to be created as one of the components to be linked. By using the identification information of the main component as the creation target scenario concept information, it is indicated that the scenario to be created has a feature that the component to be linked includes the main component. Further, the target person attribute information is information indicating characteristics of a target user in a scenario to be created, that is, a user who is assumed as a main user group of the created scenario. For example, gender, age, residential area, service Any end-user attribute information indicating the characteristics of the user, such as a usage time zone and a service usage location, can be applied as target person attribute information.

  The user terminal device 3 is a computer terminal connected to the execution control system 10 of the component cooperation scenario integrated development environment providing system 1, and requests a scenario use request to the execution control system 10 in accordance with an operation of a user who is a scenario user. And a response transmitted from the execution control system 10 is received.

<Outline of Component Link Scenario Integrated Development Environment Providing System 1>
Next, an outline of the processing of the component cooperation scenario integrated development environment providing system 1 will be described, and each configuration will be described in detail. In the component cooperation scenario integrated development environment providing system 1, the execution control system 10 executes a scenario in response to a scenario use request from the user terminal device 3, responds to the execution result, and accumulates scenario execution history information. The scenario development support system 20 responds to a scenario creation request from the development terminal device 2 and a scenario that matches a development user's request based on the existing scenario 30 and the scenario execution history information stored in the execution control system 10. Create

<Configuration of component linkage scenario integrated development environment providing system 1>
In the component cooperation scenario integrated development environment providing system 1, the scenario 30 is an already developed scenario in which a procedure for linking any one of the components 40-1 to 40-n is described. Hereinafter, a plurality of components linked by the scenario 30 will be referred to as “scenario 30 linked components”. In the present embodiment, the reference relationship is defined as follows.

In a scenario in which the cooperation components A, B, and C cooperate in this order, the cooperation component B executes a web service using the output of the cooperation component A as an input value, and the execution result is obtained when the web service of the cooperation component C is executed. An example of a scenario with input values will be described. In this scenario, when a Web service is executed using information output from another linkage component (here, linkage component A) as an input value, such as linkage component B, “linkage component B is a component that calls linkage component A. That is, it is a reference source component of the linkage component A ”.
On the other hand, the linkage component B is called by the linkage component C. At this time, the linkage component B is referred to as “the component referenced by the linkage component C, that is, the reference destination component of the linkage component C”.

  In addition, although one scenario 30 is illustrated as an example of a scenario in FIG. 1, the component cooperation scenario integrated development environment providing system 1 has a plurality of unique identification information assigned as existing developed scenarios. There is a scenario 30 in advance. For example, the scenario 30 can be applied to any scenario that has already been developed, such as a scenario developed by the scenario development support system 20 or a scenario developed by a development user. In the present embodiment, as an example, the plurality of scenarios 30 will be described as scenarios developed in the scenario development support system 20.

  The components 40-1 to 40-n are service components that provide Web services, and provide, for example, a search system, a map providing function, and a service for notifying neighboring store information according to location information of a user to be used. It is a service component (also called a required part). The components 40-1 to 40-n are service components that can be called by a Web standard interface such as SOAP (Simple Object Access Protocol).

The execution control system 10 is a computer that includes a service control unit 11 and a traffic management database 12. The execution control system 10 performs scenario execution processing in response to a scenario use request input from the user terminal device 3 and accumulates scenario execution history information. .
In the execution control system 10, the service control unit 11 performs user authentication and authorization in accordance with a scenario use request including identification information of an execution target scenario input from the user terminal device 3 and executes the scenario. Further, the execution control system 10 updates the scenario execution history information stored in the traffic management database 12 at the time of scenario execution.

The traffic management database 12 is a storage device that stores information related to users and scenario execution history information. FIG. 2 is a diagram illustrating a data configuration example and a data example of information stored in the traffic management database 12 in a table format.
As shown in the figure, the information stored in the traffic management database 12 is two-dimensional tabular data consisting of rows and columns. The user ID is user user identification information, and the user is the user name. Each column includes a name, user attribute information, and contract scenario information permitted to be used by the user. Each row of information about this user exists for each user ID.

As described above, the user attribute information is information indicating the characteristics of the user, and for example, gender and age will be described as examples of user attribute information. In addition, when a user uses a scenario, the user contracts a scenario to be used by registering subscriber information in advance, and the user attribute information is information registered when the scenario is used.
The contract scenario information is information consisting of the following items: scenario ID, which is the identification information of the scenario contracted by the user, the number of times the scenario has been used by the user, and an access log indicating the scenario usage history by the user. Yes, it exists for each scenario that the user subscribes to. The scenario usage count may be the total usage count from the time of contract, the daily usage count, or the monthly usage count.

  Next, the scenario development support system 20 will be described. The scenario development support system 20 is a computer that includes a scenario development GUI (Graphical User Interface) 21, a component recommendation processing unit 22, and a recommendation learning database 23, and responds to a scenario creation request input from the development terminal device 2. In response, a scenario is created, and the created scenario is returned to the development terminal device 2 as a recommended scenario. In other words, the scenario development support system 20 is a development support system that operates as a development environment that allows a development user to easily create a scenario. In the development environment on the GUI, the development user responds to a request from the development user. It has a function to propose a scenario.

In the scenario development support system 20, the scenario development GUI 21 is connected to the development terminal device 2, and the cooperation component selected by the component recommendation processing unit 22 in response to the scenario creation request from the development terminal device 2 and the existing scenario. Based on 30, a scenario for linking linked components is created.
The component recommendation processing unit 22 calculates a weight value indicating the degree of cooperation with the main component for each other component, selects another component with a high calculated weight value as a cooperation component, and uses the scenario development GUI 21 to select information on the selected cooperation component. Output to.

Specifically, the component recommendation processing unit 22 reads the learning information table from the recommendation learning database 23 using the main component identification information included in the scenario creation request as a search key, and the traffic management database 12 of the execution control system 10 stores it. Read scenario execution history information. The component recommendation processing unit 22 uses connection information between components used in a scenario created in the past, a learning information table which is component reference information, and use of a scenario used by a user corresponding to target person attribute information. Based on the situation, weights are added to the scenario usage history by the user corresponding to the target person attribute information to calculate the weight value indicating the degree of cooperation with the main component, and other components with high calculated weight values are linked components Choose as.
In addition, as a target person attribute information, you may use the time slot | zone which used the scenario, the sex information of the user who used, the frequency | count of use, etc.

  The learning database for recommendation 23 stores information on linked components in the scenario created by the scenario development support system 20 as a learning information table for each component. FIG. 3 is a diagram showing a data configuration example of the learning information table stored in the recommendation learning database 23 and a data example of the learning information table of the main component as a specific example. As shown in the figure, the learning information table is a two-dimensional tabular data composed of rows and columns. In the component corresponding to the table, information on the component of the reference source, information on the component of the reference destination Each column includes items of average processing time, component usage frequency, and weight value.

The component of the reference source is a component that calls the component corresponding to the learning information table (here, the main component) in the existing scenario 30, that is, the component that uses the output information of the main component as an input value. The reference destination component is a component that is referenced by a component corresponding to the learning information table.
The reference source component information includes, for each reference source component, the reference source component ID that is identification information of the reference source component, the number of calls of this reference source component (the number of reference sources), and the number of calls. Have. Further, the information of the reference destination component includes items of a reference destination component ID, the reference destination number of the reference source component, and the reference count for each reference destination component.

The number of main component calls is the total number of combinations in which the main component and other components are linked in order among the combinations in which the main component and other components are directly linked in a plurality of scenarios 30.
In addition, the number of calls in the main component is the number of times of execution of the combination that cooperates in the order of the main component and other components, that is, the total number of times that the scenario including this combination is executed in the execution control system 10.

The reference number of the main component is the total number of combinations in which the main component and the other component are linked in order among the combinations in which the main component and the other component are directly linked in the plurality of scenarios 30.
The number of times of reference in the main component is the number of times of execution of a combination that cooperates in the order of other components and main component, that is, the total number of times that a scenario including this combination is executed in the execution control system 10.

Next, an outline of a processing flow of the entire system will be described with reference to FIG. 4 regarding a flow of operation processing in the component cooperation scenario integrated development environment providing system 1. Details of the scenario creation process will be described with reference to FIG. 5 using a specific example.
FIG. 4 is a flowchart showing an outline of processing of the component cooperation scenario integrated development environment providing system 1.

The development terminal device 2 transmits a scenario creation request including the target person attribute information of the scenario development support system 20 and the main component ID to be used to the scenario development GUI 21 according to the input operation of the development user (step S1).
The scenario development GUI 21 outputs a component recommendation request including the received scenario creation request to the component recommendation processing unit 22 (step S2). The component recommendation processing unit 22 reads the scenario execution history from the traffic management database 12 of the execution control system 10 (step S3), and reads the learning information table corresponding to the main component ID from the recommendation learning database 23 (step S4).

The recommendation learning database 23 calculates a weight value reflecting the target person attribute information based on the read scenario execution history and the learning information table (step S5). Here, the weight value reflecting the target person attribute information is based on the scenario execution history of the user corresponding to the target person attribute information, by adding a predetermined value to the weight value of the component executed by the user, This is the value to be calculated.
The component recommendation processing unit 22 selects a cooperation component that cooperates with the main component in descending order of the calculated weight value, and outputs cooperation component information including identification information of the selected cooperation component to the scenario development GUI 21 (step S6).

  The scenario development GUI 21 creates a scenario for linking the main component and the linked component selected by the component recommendation processing unit 22 based on the linked component information input from the component recommendation processing unit 22 (step S7). Here, the scenario development GUI 21 reads a scenario for linking the main component and the input linked component among a plurality of existing scenarios 30 and creates a scenario to be created based on the description of the read scenario. To do. Next, the scenario development GUI 21 responds to the development terminal device 2 using the created scenario as a recommended scenario (step S8).

  On the other hand, when the execution control system 10 receives a scenario use request including the scenario ID to be used and the user ID from the user terminal device 3 (step S10), the service control unit 11 authenticates and authorizes the user. If it is authenticated, the scenario corresponding to the scenario ID is executed. Further, the service control unit 11 updates the scenario execution history of the traffic management database 12 every time the scenario is executed (step S11).

  Next, based on the identification information of the main component input in the scenario development support system 20, details of an algorithm for recommending a scenario will be described with reference to a specific example. To recommend a scenario, based on input information, select a cooperation component to be linked by the scenario development support system 20 from the components 40-1 to 40-n, and create a scenario to link the selected linkage components with each other. The scenario is output to the development terminal device 2 as a recommended scenario.

  FIG. 5 is a diagram illustrating a specific example of a scenario creation procedure in the scenario development support system 20. The development user who operates the development terminal device 2 transmits the identification information of the main component and the target person attribute information indicating the target user to be used to the scenario development support system 20 via the development terminal device 2. At this time, it is assumed that the development user wants to develop a scenario targeting young men using the rental car reservation component.

  Next, the scenario development GUI 21 of the scenario development support system 20 outputs a component recommendation request to the component recommendation processing unit 22, and the component recommendation processing unit 22 reads the learning information table of the rental car reservation component from the recommendation learning database 23. Further, the component recommendation processing unit 22 reads out a list of scenarios used by young men and scenario execution history information from the traffic management database 12.

  Next, the component recommendation processing unit 22 calculates, for each component, a weight value that reflects the usage frequency and reference information for each component based on the read scenario execution history information. For example, the component recommendation processing unit 22 increases the weight value by adding a predetermined value to the weight of a component having a high frequency of component use by young men from the scenario execution history information. The table shown in FIG. 5 is a table that is temporarily created by the component recommendation processing unit 22 and is a table in which a reference relationship to the rental car reservation component for each component is associated with a weight value.

Here, the usage frequency for each component in the table temporarily created by the component recommendation processing unit 22 is obtained based on the scenario execution history read from the traffic management database 12, and the number of times each component is used is obtained. It is the value divided by the number of times.
Also, the weight value is calculated by adding the number of times each component references the main component (the number of reference sources) and the number of times each component is called from the main component (the number of reference destinations) in the existing scenario 30. Based on the total number, the component having the largest total number is set to have the highest weight, and the weight value is set to 1 for all components in the table of the component recommendation processing unit 22.

  In this figure, the component recommendation processing unit 22 selects the map component having the highest weight value in the table as the linkage component, and sets the reference source number “21” and the reference destination number “2” for the selected map component. Compare. Since the map component refers to the number of reference to the rental car reservation component, that is, the number of reference sources is large, the component recommendation processing unit 22 selects the map component as a linkage component that refers to the rental car reservation component. Next, as the component with the highest weight value, select the event information component as the linkage component, compare the number of reference sources and the number of reference destinations, and since the number of reference destinations is large, Select the event information component.

  Here, if the number of reference sources for the event information component is larger than the number of reference destinations, the event information component is selected as the linkage component that references the rental car reservation component. This selection process is repeated a predetermined number of times as desired by the development user, and the scenario development GUI 21 creates a scenario that links the event information component, the rental car reservation component, and the map component selected by the component recommendation processing unit 22.

  As described above, according to the present embodiment, the development user uses the development terminal device 2 as the creation target scenario concept information for the development target terminal device 2 as the creation target scenario concept information. Thus, there is an effect that it becomes possible to create a scenario without coding the scenario.

  In addition, the component recommendation processing unit 22 selects a component to be linked with the main component based on an existing scenario including the main component, so that the development user selects another component to be linked with the main component. Scenarios can be created without

  In addition, the component recommendation processing unit 22 uses the past usage history as the number of linkages (the number of references and the number of calls) with the main component in the existing scenario and the scenario execution history stored in the traffic management database 12. By selecting a linkage component based on the history, it is possible to select a component that is frequently used for linkage to the main component, that is, a component that has already been used, as a linkage component of a scenario to be created. By creating a scenario using a combination of these frequently used components, the development user must create a useful scenario that can provide a linked service with high utility value to the user. Is possible.

  In addition, the scenario development support system 20 creates a scenario that provides a linked service based on a combination of components that are frequently used by the target person, based on the scenario use history used by the user corresponding to the target person attribute information. Accordingly, there is an effect that the development user can create a scenario capable of providing a cooperation service with high utility value specialized for each target person attribute. In addition, by using the scenario usage history written in the traffic management database 12 by the service control unit 11 of the execution control system 10, the component recommendation processing unit 22 selects a linked component to be linked to the main component based on the latest service usage status. There is an effect that it becomes possible to select.

  In addition, since the component recommendation processing unit 22 selects a linkage component to the main component based on the past usage history of the existing scenario, the scenario development GUI 21 receives the input between the main component and the linkage component in the scenario to be created. A description of output conversion can be described based on an existing scenario. As a result, the development user can create a scenario without coding, and the development work time per scenario can be shortened. Furthermore, there is an effect that a development user who does not have special technology such as a small business owner or a service planner can easily create a scenario.

  In the above-described embodiment, the component cooperation scenario integrated development environment providing system 1 has been described as an example in which the scenario 30 and the components 40-1 to 40-n are provided. However, the present invention is not limited to this. Thus, the execution control system 10 may execute a scenario outside the component cooperation scenario integrated development environment providing system 1.

  Further, the component recommendation processing unit 22 may calculate a weight value based on the number of references and the number of calls. Further, the component recommendation processing unit 22 may calculate the weight value using only the number of executions by the user corresponding to the target person attribute information.

Note that the execution control system 10, the scenario development support system 20, the development terminal device 2, and the user terminal device 3 described above have a computer system therein. The operation processes of the service control unit 11 of the execution control system 10, the scenario development GUI 21 of the scenario development support system 20, and the component recommendation processing unit 22 are stored in a computer-readable recording medium in the form of a program. The above processing is performed by the computer system reading and executing the program. The “computer system” herein includes a CPU, various memories, an OS, and hardware such as peripheral devices.
Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.

4 is recorded in a computer-readable recording medium, and the program for realizing the functions of the execution control system 10 and the scenario development support system 20 shown in FIG. May be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to create a scenario recommended for a development user.
The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

Further, the “computer-readable recording medium” means a volatile memory (for example, DRAM (Dynamic DRAM) in a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. Random Access Memory)), etc., which hold programs for a certain period of time.
The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.
The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

It is a block diagram which shows the whole structure of the component cooperation scenario integrated development environment provision system 1, the development terminal device 2, and the user terminal device 3 by one Embodiment of this invention. It is a figure which shows the data structural example of the traffic management database 12 in the embodiment. It is a figure which shows the data structural example of the learning database 23 for recommendation in the embodiment. It is a flowchart which shows the flow of operation | movement of the component cooperation scenario integrated development environment provision system 1 in the embodiment. It is a figure which shows the specific example of the scenario creation procedure in the embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Component cooperation scenario integrated development environment provision system 2 Development terminal device 3 User terminal device 10 Execution control system 11 Service control part 12 Traffic management database 20 Scenario development support system 21 Scenario development GUI
22 component recommendation processing unit 23 learning database for recommendation 30 scenario 40-1 component 40-1 to 40-n component

Claims (7)

A component-linked scenario integrated development environment providing system comprising a development support system that supports creation of a scenario indicating a processing procedure for linking a plurality of components that provide services, and an execution control system that executes linked processing of the components based on the scenario Because
The development support system includes:
As a signal that requests creation of a scenario that includes the main component as a component to be linked, the main component and other components that are linked components are linked in response to the input of a scenario creation request signal that includes identification information of the main component. A scenario development department that generates a scenario to be
Based on a scenario including the main component as a component to be linked among a plurality of scenarios, a weight value indicating a degree of association between the main component and another component is calculated, and the linked component is selected based on the calculated weight value. And a component recommendation processing unit that outputs identification information of the selected linked component to the scenario development unit. The component recommendation processing unit
The system according to claim 1, wherein the weight value is calculated for each component based on the number of linkages with the main component. The execution control system includes:
An execution history information storage unit for storing execution history information for each scenario;
A service control unit that executes a scenario in response to an input of a scenario execution request and writes execution history information of the executed scenario in the execution history information storage unit;
The component recommendation processing unit
3. The component-linked scenario integrated development environment according to claim 1, wherein the weight value is calculated based on the number of times of linking execution with the main component for each of the components calculated based on the execution history information. Offer system. The execution control system includes:
A user information storage unit that stores user information of the scenario and scenario execution history information by the user in association with each other;
A service control unit that writes scenario execution history information executed in response to an input of a scenario execution request to the user information storage unit,
The scenario creation request signal received by the scenario development unit further includes target person information indicating an attribute of a target person of the scenario to be created,
The component recommendation processing unit
The scenario execution history information corresponding to the provision target person information is read from the user information storage unit, and based on the read scenario execution history information, the number of times of cooperation execution with the main component executed by the provision target person is calculated. The component cooperation scenario integrated development environment according to any one of claims 1 to 3, wherein each component is calculated and the weight value is calculated based on the calculated number of times of cooperation executed by the provider. Offer system. The scenario development department
Based on the scenario including the cooperation component corresponding to the identification information of the cooperation component input from the component recommendation processing unit and the main component as components to be linked, the main component and the cooperation component are linked. The system for creating a component-linked scenario integrated development environment according to any one of claims 1 to 4, wherein a scenario is created. A component-linked scenario integrated development environment providing system comprising a development support system that supports creation of a scenario indicating a processing procedure for linking a plurality of components that provide services, and an execution control system that executes linked processing of the components based on the scenario Scenario creation support method in
The development support system is
Receiving a scenario creation request signal including identification information of the main component as a signal requesting creation of a scenario including the main component as a component to be linked; and
Among the plurality of scenarios, based the main component in the scenario involving a cooperation target component, the main component and calculates a weight value indicating the degree of association with other components, based-out collaboration components in calculated weight value The process of selecting
A scenario creation support method comprising: generating a scenario for linking the main component with the selected linked component. A component-linked scenario integrated development environment providing system comprising a development support system that supports creation of a scenario indicating a processing procedure for linking a plurality of components that provide services, and an execution control system that executes linked processing of the components based on the scenario Development support system computer in
As a signal that requests creation of a scenario that includes the main component as a component to be linked, the main component and other components that are linked components are linked in response to the input of a scenario creation request signal that includes identification information of the main component. Scenario development department that generates scenarios
Based on a scenario including the main component as a component to be linked among a plurality of scenarios, a weight value indicating a degree of association between the main component and another component is calculated, and the linked component is selected based on the calculated weight value. And a program for causing the scenario recommendation unit to output identification information of the selected linked component to the scenario development unit.

Images