Information processing device, information processing method, and program

Abstract

An information processing device 1 that generates an application architecture model and a data architecture model, from a business architecture model that models processes and objects on the basis of business requirements. The information processing device 1 comprises an API information storage unit 15 that stores information about industry standard API. A recommended AA / DA calculation unit 19 extracts, from the business architecture model, information about business processes and information about business objects used by the business processes, for each business process in the business architecture model. The recommended API calculation unit 20 calculates recommendation levels for the business processes, for each industry standard API. The recommended AA / DA calculation unit 19 constructs AA elements on the basis of the names of the industry standard API that have the highest recommendation levels, connects these to the business processes, constructs DA elements on the basis of the names of resources that are used by the industry standard API that has the highest recommendation level, connects these to business objects, and generates an application architecture model and a data architecture model.

Description

[Technical field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] A framework for formulating an enterprise architecture using a hierarchical structure of business architecture, data architecture, application architecture, and technology architecture is known (Non-Patent Document 1). In the framework of Non-Patent Document 1, each architecture model is constructed in the order of business architecture, application architecture and data architecture, and technology architecture. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “Welcome to the TOGAF Standard, Version 9.2”, The Open Group, Internet <URL: https: / / pubs.opengroup.org / architecture / togaf9-doc / arch / > Summary of the Invention [Problem to be solved by the invention]

[0004] In the framework of Non-Patent Document 1, it is recommended to utilize industry standards and current elements as much as possible when constructing application architecture and data architecture. However, there is a problem that it is a heavy burden to investigate information that can be used to construct application architecture and data architecture from a huge amount of industry standard information. In addition, there is a problem that when current elements and industry standards are combined and used, there is a high possibility that parts of the data definition will not match.

[0005] The present invention has been made in view of the above, and aims to make it easier to utilize industry standards and current elements when formulating an enterprise architecture. [Means for solving the problem]

[0006] An information processing device according to one aspect of the present invention is an information processing device that generates an application architecture model and a data architecture model from a business architecture model in which processes and objects are modeled based on business requirements, and API name and API overview, as well as resource names and resource overviews used by the industry standard API and a storage unit for storing, for each process included in the business architecture model, Process name and process overview and the object used by the process Object Name and Object Description Extract from the business architecture model Based on the similarity between the process name and the API name, the similarity between the process outline and the API outline, the similarity between the object name and the resource name, the similarity between the object outline and the resource outline, and the relationship between the utilization relationship between the process and the object and the operation of the industry standard API, Calculate a recommendation level for each of the industry standard APIs, and select the industry standard API with the highest recommendation level. API name Based on the above, construct an AA element and link it to the process, and the resource used by the industry standard API with the highest recommendation is Resource name and a generation unit that generates the application architecture model and the data architecture model by constructing DA elements based on the above and linking them to the objects.

[0007] An information processing method according to one aspect of the present invention is an information processing method for generating an application architecture model and a data architecture model from a business architecture model in which processes and objects are modeled based on business requirements, the method comprising: API name and API overview, as well as resource names and resource overviews used by the industry standard API For each process included in the business architecture model, Process name and process overview and the object used by the process Object Name and Object Description Extract from the business architecture model Based on the similarity between the process name and the API name, the similarity between the process outline and the API outline, the similarity between the object name and the resource name, the similarity between the object outline and the resource outline, and the relationship between the utilization relationship between the process and the object and the operation of the industry standard API, Calculate a recommendation level for each of the industry standard APIs, and select the industry standard API with the highest recommendation level. API nameBased on the above, construct an AA element and link it to the process, and the resource used by the industry standard API with the highest recommendation is Resource name and binds the DA elements based on the objects to generate the application architecture model and the data architecture model. Effect of the Invention

[0008] The present invention allows enterprise architectures to more easily leverage industry standards and current state of the art elements. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a functional block diagram showing an example of the configuration of an information processing device according to the present embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of industry standard API information held by an information processing device. [Diagram 3] FIG. 3 is a diagram illustrating an example of information on resources used by industry standard APIs held by an information processing device. [Figure 4] FIG. 4 is a diagram illustrating an example of a business architecture model. [Diagram 5] FIG. 5 is a diagram illustrating an example of an application architecture model. [Figure 6] FIG. 6 is a diagram illustrating an example of an application architecture model generated by the information processing device. [Figure 7] FIG. 7 is a flowchart showing an example of a process flow for generating an application architecture model. [Figure 8] FIG. 8 is a diagram showing an example of business processes and business objects extracted from a business architecture model. [Figure 9] FIG. 9 is a diagram showing an example in which application functions and data objects are linked to the business processes and business objects of FIG. [Figure 10]FIG. 10 is a flowchart showing an example of the flow of a process for obtaining consistency of data objects. [Figure 11] FIG. 11 is a diagram showing an example of how similarities between a data object and a resource and between a data object and a sub-resource are calculated. [Figure 12] FIG. 12 is a diagram showing an example in which information on a current data object is added to a data object constructed based on resources of a recommended API. [Figure 13] FIG. 13 is a diagram showing an example in which a current data object is replaced with a data object constructed based on the resource of a recommended API. [Figure 14] FIG. 14 is a diagram illustrating an example of a hardware configuration of an information processing device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0011] FIG. 1 is a functional block diagram showing an example of the configuration of an information processing device 1 according to the present embodiment. The information processing device 1 according to the present embodiment is a device that holds information on industry-standard application programming interfaces (APIs), and when a business architecture model (hereinafter referred to as "BA") in which processes and objects are modeled based on business requirements is input, constructs application architecture (hereinafter referred to as "AA") elements and data architecture (hereinafter referred to as "DA") elements to be linked to the BA based on the industry-standard API, and generates an application architecture model and a data architecture model (hereinafter referred to as "AA / DA"). When identifying an industry-standard API to be used when constructing the AA elements and the DA elements, the information processing device 1 extracts information on the business process and business object included in the BA, and calculates the recommendation level of each API based on the similarity between the extracted information and the information of each API. The information processing device 1 constructs the AA elements and the DA elements based on the API with the highest recommendation level.

[0012] Furthermore, the information processing device 1 may input AA elements and DA elements to be used as AA / DA elements for the ideal (To-Be) BA in the current (As-Is) AA / DA. In other words, functions to be reused from the current system may be input. At this time, the information processing device 1 may provide information for achieving consistency between the DA elements constructed from the resources of the recommended API and the DA elements used from the As-Is.

[0013] The information processing device 1 shown in Figure 1 includes an API information registration unit 11, a BA registration unit 12, an AA / DA registration unit 13, a policy registration unit 14, an API information memory unit 15, a BA memory unit 16, an AA / DA memory unit 17, a policy memory unit 18, a recommended AA / DA calculation unit 19, a recommended API calculation unit 20, a matching unit 21, and an output unit 22.

[0014] The API information registration unit 11 inputs information on industry standard APIs and registers them in the API information storage unit 15. An industry standard API is a standard specification defined by a standardization organization or the like, and is an interface specification for using a device or a service. Examples of industry standard APIs include TeleManagement Forum (TMF) Open APIs, 3rd Generation Partnership Project (3GPP) APIs, and Metro Ethernet Forum (MEF) APIs. Note that the APIs stored in the API information storage unit 15 are not limited to these. Industry standard APIs other than those mentioned above may also be registered.

[0015] 2 and 3 show examples of information stored in API information storage unit 15. FIG. 2 is an example of information about an industry standard API. In the example of FIG. 2, for each API, an API record including an API ID, industry standard name, API name, API overview, operation, resource ID, and resource overview is registered in API information storage unit 15. The API ID is an identifier for identifying the API in information processing device 1. The industry standard name is the name of the industry standard that defines the API. The API name is the name of the API. The API overview is a description of the functions of the API, etc. The operation is an operation on the resource (get, post, patch, or delete). The resource ID is an identifier for identifying the resource used by the API. The resource overview is a description of the resource used by the API.

[0016] FIG. 3 is an example of resource information used by an industry standard API. In the example of FIG. 3, for each field included in the resource, a resource record including a resource ID, resource name, field name, type, field summary, and sub-resource ID is registered in API information storage unit 15. The resource ID is an identifier for identifying a resource in information processing device 1, and corresponds to the resource ID of the API record. The resource name is the name of the resource. The field name is the name of the field included in the resource. The type indicates the data type of the field. The field summary is a description of the field. The sub-resource ID is a resource ID that indicates the resource linked to the field.

[0017] The BA registration unit 12 inputs the To-Be BA created by the architect and registers it in the BA storage unit 16. The architect creates a BA using a tool, for example, and inputs the created BA to the BA registration unit 12. A generation unit is made up of a recommended AA / DA calculation unit 19 and a recommended API calculation unit 20, which will be described later, and generates a To-Be AA / DA corresponding to the To-Be BA input by the BA registration unit 12.

[0018] An example of a To-Be business architecture model is shown in Figure 4. In the example of Figure 4, the BA is composed of five business processes 110A-110E and three business objects 120A-120C. A business process is a procedure for realizing a desired vision. A business object is information used by a business process. The direction (read or write) of use of a business object by a business process is indicated by an arrow. For example, in the BA of Figure 4, business process 110A generates business object 120A, and business process 110B uses business object 120A.

[0019] The AA / DA registration unit 13 inputs the AA elements and DA elements to be used in To-Be among the AA / DA of As-Is, registers them in the AA / DA storage unit 17, and also links the AA elements and DA elements to be used in To-Be to the BA of To-Be. The BA of To-Be is stored in the BA storage unit 16. The AA / DA of As-Is is modeled on the current system. For example, the architect registers AA elements and DA elements corresponding to applications to be used in To-Be in the current system as AA elements and DA elements to be used in To-Be, and links them to the BA of To-Be.

[0020] An example of an As-Is application architecture model is shown in Fig. 5. In the example of Fig. 5, an application function 210A and three data objects 220A to 220C used for To-Be are shown. The application function 210A is an AA element, and the data objects 220A to 220C are DA elements. Fig. 5 also shows the BA of As-Is.

[0021] The policy registration unit 14 inputs a policy indicating which of the DA elements of the As-Is and the DA elements constructed from the resources of the recommended API is to be prioritized, and registers the policy in the policy storage unit 18. This policy is referred to when the reconciliation unit 21 described later performs reconciliation of the DA elements of the As-Is.

[0022] The recommended AA / DA calculation unit 19 constructs AA elements and DA elements to be linked to the business processes and business objects included in the BA of To-Be based on the recommended API obtained by the recommended API calculation unit 20, and generates AA / DA. More specifically, the recommended AA / DA calculation unit 19 extracts information on the business processes and information on the business objects used by the business processes for each of the business processes included in the BA of To-Be from the BA, and transmits them to the recommended API calculation unit 20. The information transmitted by the recommended AA / DA calculation unit 19 to the recommended API calculation unit 20 includes, for example, the business process name, the business process overview, the business object name, the business object overview, and the use direction (read or write) of the business object. Based on the information on the API record of the recommended API returned from the recommended API calculation unit 20, the recommended AA / DA calculation unit 19 constructs an application function to which an industry standard name and an API name are assigned, and links it to the business process, and constructs a data object to which an industry standard name and a resource name are assigned, and links it to the business object.

[0023] FIG. 6 shows an example of a business architecture model and an application architecture model of To-Be. The application architecture model shown in FIG. 6 is the AA / DA generated by the recommended AA / DA calculation unit 19. In the example of FIG. 6, application functions 210A-210E linked to business processes 110A-110E and data objects 220A-220D linked to business objects 120A-120C are shown. The application function 210A and three data objects 220A-220C enclosed in a frame 230 are AA elements and DA elements utilized from As-Is. The four application functions 210B-210E and data object 220D enclosed in a frame 240 are AA elements and DA elements constructed by the recommended AA / DA calculation unit 19 based on the recommended API.

[0024] Among the business processes of BA, those to which the AA element of As-Is is linked are excluded from the processing of the recommended AA / DA calculation unit 19. In the example of Fig. 6, the business process 110A to which the application function 210A of As-Is is linked is excluded from the processing.

[0025] The recommended API calculation unit 20 calculates the recommendation level of each API from the information received from the recommended AA / DA calculation unit 19 and the information of industry standard APIs held in the API information memory unit 15, and returns the recommended API with the highest recommendation level to the recommended AA / DA calculation unit 19.

[0026] The recommended API calculation unit 20 calculates, for example, the similarity between the business process name and API name, the business process overview and API overview, the business object name and resource name, and the business object overview and resource overview for each API record held in the API information storage unit 15, by a method of calculating the similarity between two sentences in natural language processing. Note that TF-IDF or the like can be used to vectorize the sentences. The cos similarity method or the like can be used to calculate the similarity.

[0027] Furthermore, the recommended API calculation unit 20 quantifies the relationship (similarity) between the direction of use and the operation of the API record for the use of the business object of the business process. For example, the recommended API calculation unit 20 assigns a value of 1 if the direction of use is read and the operation is get, assigns a value of 1 if the direction of use is write and the operation is post, patch, or delete, and assigns a value of 0 for other combinations.

[0028] The recommended API calculation unit 20 calculates a recommendation level from the similarity level calculated above to obtain a recommended API. For example, the recommended API calculation unit 20 multiplies the similarity level by a value indicating the direction of use to calculate the recommendation level.

[0029] The matching unit 21 matches the DA element of As-Is included in the AA / DA generated by the recommended AA / DA calculation unit 19 and the recommended API calculation unit 20 with the DA element constructed from the resources of the recommended API based on the policy stored in the policy storage unit 18. When the DA element of As-Is is emphasized, the matching unit 21 makes the DA element of As-Is included in the AA / DA a DA element constructed from the resources of the recommended API, and provides information to replace the fields of the DA element with the fields included in the DA element of As-Is. When the recommended API is emphasized, the matching unit 21 replaces the DA element of As-Is included in the AA / DA with the DA element constructed from the resources of the recommended API.

[0030] The output unit 22 outputs the AA / DA generated by the recommended AA / DA calculation unit 19 and the recommended API calculation unit 20 in a format that can be read by a tool used by the architect. This tool may be the same as the tool with which the architect created the BA, and the architect can check the state in which the BA and the AA / DA are linked on the tool. The architect checks the AA / DA generated by the information processing device 1 and makes corrections, etc. When the reconciliation unit 21 processes the DA element of As-Is, the output unit 22 outputs the AA / DA including the DA element processed by the reconciliation unit 21.

[0031] When AA / DA of As-Is is not used, the information processing device 1 does not need to include the AA / DA registration unit 13, the policy registration unit 14, the AA / DA storage unit 17, the policy storage unit 18, and the matching unit 21.

[0032] Next, the AA / DA generation process by the recommended AA / DA calculation unit 19 and the recommended API calculation unit 20 will be described with reference to the flowchart in Fig. 7. It is assumed that the BA of To-Be is held in the BA storage unit 16. The following process is executed for each business process included in the BA. Business processes to which the application function of As-Is is linked are excluded. For example, in the example shown in Fig. 6, the process is executed for the four business processes 110B to 110E excluding the business process 110A.

[0033] In step S11, the recommended AA / DA calculation unit 19 extracts information about the business process to be processed from the BA storage unit 16. When extracting the business process information, the recommended AA / DA calculation unit 19 also extracts information about the business objects used by the business process and the usage direction. In the example of Fig. 8, the recommended AA / DA calculation unit 19 extracts "alarm information reception" as the business process 110, and extracts "alarm information" as the business object 120 used by the business process 110. The recommended AA / DA calculation unit 19 also extracts information (usage direction) that the business process 110 reads the business object 120.

[0034] In step S12, the recommended API calculation unit 20 calculates a recommendation level for each API record held in the API information storage unit 15 based on the information extracted in step S11 and the API record information, and returns the API record with the highest recommendation level to the recommended AA / DA calculation unit 19.

[0035] In step S13, the recommended AA / DA calculation unit 19 constructs an AA element and a DA element from the information of the API record received from the recommended API calculation unit 20 and links them to the BA. In the example of FIG. 9, the recommended AA / DA calculation unit 19 acquires the industry standard name, API name, and resource name from the recommended API record, constructs an application function 210 to which a character string of "TMF_XX_API" including the industry standard name and API name is assigned, and links it to the business process 110, and constructs a data object 220 to which a character string of "TMF_XX Resource" including the industry standard name and resource name is assigned, and links it to the business object 120. The architect can determine which API to use from the character strings assigned to the application function 210 and the data object 220. The application function 210 and the data object 220 may include information of the recommended API record or may include information of the resource record.

[0036] Next, the matching process of the As-Is data objects by the matching unit 21 will be described with reference to the flowchart of Fig. 10. The following process is executed for all of the As-Is data objects included in the AA / DA generated by the recommended AA / DA calculation unit 19. For example, in the example shown in Fig. 6, it is executed for the three data objects 220A, 220B, and 220C in the frame 230.

[0037] In step S21, the matching unit 21 extracts business processes that use business objects linked to the As-Is data object. For example, for the data object 220A in Fig. 6, two business processes 110A and 110B that use the business object 120A linked to the data object 220A are extracted.

[0038] In step S22, the matching unit 21 extracts a recommended API of the application function that the recommended AA / DA calculation unit 19 has linked to the business process extracted in step S21. For example, in the example shown in FIG. 6, the recommended API of application function 210B linked to business process 110B is extracted. The recommended API can be extracted from the industry standard name and API name given to application function 210B. Note that application function 210A linked to business process 110A is an As-Is application function and was not constructed by the recommended AA / DA calculation unit 19.

[0039] In step S23, the matching unit 21 extracts resources by referring to the API record of the recommended API. Specifically, the matching unit 21 extracts a resource record that corresponds to the resource ID of the API record. If a sub-resource ID is specified in the resource record, the matching unit 21 also recursively extracts the resource record of that resource ID. For example, since the API record of API ID=1 shown in FIG. 2 specifies resource ID=1, the matching unit 21 extracts the resource record of resource ID=1 shown in FIG. 3 and also extracts the resource record of sub-resource ID=5.

[0040] In step S24, the matching unit 21 calculates the similarity between the data object As-Is and each resource and each sub-resource extracted in step S23, and sets the resource or sub-resource with the maximum similarity as the matching target of the data object As-Is. FIG. 11 shows an image of calculating the similarity between the data object 220 As-Is and the resource 310 and the sub-resource 320. The matching unit 21 compares each field of the data object 220 with each field of the resource 310 and the sub-resource 320, and calculates the similarity for each of the resource 310 and the sub-resource 320. For example, the matching unit 21 calculates the similarity between the resource 310 and the sub-resource 320 from the similarity of the field type, the field name, etc. The resource 310 or the sub-resource 320 with the maximum similarity is set as the matching target of the data object 220.

[0041] In step S25, the matching unit 21 refers to the policy registered in the policy storage unit 18 and determines whether to prioritize the As-Is or the resources of the recommended API.

[0042] When As-Is is important, the matching unit 21 constructs a new data object from the resources or sub-resources to be matched obtained in step S24, and assigns correspondence information to replace the fields of the new data object with the fields of the As-Is data object. In the example of Fig. 12, a data object constructed from the sub-resource 320 is linked to the business object 120, and information is assigned to replace the fields of the sub-resource 320 with the fields of the As-Is data object 220.

[0043] When the resource of the recommended API is important, the matching unit 21 replaces the As-Is data object with a new data object constructed based on the matching target resource or sub-resource obtained in step S24. In the example of Fig. 13, the data object constructed from the sub-resource 320 is linked to the business object 120.

[0044] As described above, the information processing device 1 of the present embodiment includes an API information storage unit 15 that holds information on industry standard APIs. The recommended AA / DA calculation unit 19 extracts, for each of the business processes included in the business architecture model, information on the business process and information on the business object used by the business process from the business architecture model. The recommended API calculation unit 20 calculates the recommendation level for each of the industry standard APIs. The recommended AA / DA calculation unit 19 creates an application function based on the name of the industry standard API with the highest recommendation level and links it to the business process, creates a data object based on the name of the resource used by the industry standard API with the highest recommendation level and links it to the business object to generate an application architecture model and a data architecture model. This makes it possible to generate an application architecture model and a data architecture model that utilize industry standard APIs.

[0045] The information processing device 1 described above may be, for example, a general-purpose computer system including a central processing unit (CPU) 901, a memory 902, a storage 903, a communication device 904, an input device 905, and an output device 906 as shown in Fig. 14. In this computer system, the information processing device 1 is realized by the CPU 901 executing a predetermined program loaded onto the memory 902. This program can be recorded on a computer-readable recording medium such as a magnetic disk, an optical disk, or a semiconductor memory, or can be distributed via a network. [Explanation of symbols]

[0046] 1. Information processing device 11 API Information Registration Section 12 BA Registration Department 13 AA / DA Registration Department 14 Policy Registration Section 15 API information storage section 16 BA Memory Section 17 AA / DA memory section 18 Policy Storage 19 Recommended AA / DA Calculation Section 20 Recommended API Calculation Section 21 Matching section 22 Output section

Claims

1. An information processing device that generates an application architecture model and a data architecture model from a business architecture model in which processes and objects are modeled based on business requirements, a storage unit for storing API names and API overviews of industry standard APIs, as well as resource names and resource overviews used by the industry standard APIs; a generation unit that extracts, for each process included in the business architecture model, a process name and a process outline of the process and an object name and an object outline of an object used by the process from the business architecture model, calculates a recommendation level for each of the industry standard APIs based on a similarity between the process name and the API name, a similarity between the process outline and the API outline, a similarity between the object name and the resource name, a similarity between the object outline and the resource outline, and a relationship between a utilization relationship between the process and the object and an operation of the industry standard API, constructs an AA element based on an API name of the industry standard API having the highest recommendation level and links it to the process, and constructs a DA element based on a resource name of a resource used by the industry standard API having the highest recommendation level and links it to the object, thereby generating the application architecture model and the data architecture model. Information processing device.

2. 2. The information processing device according to claim 1, a current model registration unit that inputs a current application architecture model and a current data architecture model and links current AA elements and current DA elements included in the current application architecture model and the current data architecture model to processes and objects included in the business architecture model; The present invention provides a system for integrating the current DA elements included in the application architecture model and data architecture model generated by the generation unit with resources used by the industry standard API. Information processing device.

3. 3. The information processing device according to claim 2, The matching unit extracts the process that uses the object linked to the current DA element, extracts the AA element built based on the industry standard API from among the AA elements linked to the process, and matches the resource used by the industry standard API corresponding to the extracted AA element with the current DA element. Information processing device.

4. 4. The information processing device according to claim 3, The matching unit replaces the current DA element with a new DA element constructed from resources using the industry standard API, and assigns correspondence information between the information held by the new DA element and the information held by the current DA element to the new DA element. Information processing device.

5. An information processing method for generating an application architecture model and a data architecture model from a business architecture model in which processes and objects are modeled based on business requirements, comprising: The computer Retaining API names and API summaries of industry standard APIs, as well as resource names and resource summaries used by the industry standard APIs; For each process included in the business architecture model, a process name and a process overview of the process and object names and object overviews of objects used by the process are extracted from the business architecture model; Calculating a recommendation level for each of the industry standard APIs based on the similarity between the process name and the API name, the similarity between the process summary and the API summary, the similarity between the object name and the resource name, the similarity between the object summary and the resource summary, and the relationship between a utilization relationship between the process and the object and an operation of the industry standard API; Constructing an AA element based on an API name of the industry standard API with the highest recommendation level and linking it to the process, constructing a DA element based on a resource name of a resource used by the industry standard API with the highest recommendation level and linking it to the object, thereby generating the application architecture model and the data architecture model. Information processing methods.

6. 5. A program for causing a computer to operate as each unit of the information processing device according to claim 1.

Images