JP5337666B2 - Component design support device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To support decision of granularity of a component to be applied to a system that is a development object. <P>SOLUTION: An information processor supports design of the system as the development object. The processor refers to information for the development object system, information for an existing system to be entirely or partially replaced by the development object system, and information showing restriction of granularity that is a unit showing the size of a component applied to the development object system, thereby deriving a granularity application plan that is a plan for the granularity of a component applicable to the development object system. The processor further refers to the derived granularity application plan, the information for the development object system, the information for the existing system, and information showing relationship between cost that is an expense associated with design, development and maintenance of the development object system and various evaluation items, thereby calculating the cost associated with design, development and maintenance of the development object system in application of the granularity application plan to the development object system. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a design support apparatus.

  A component collectively handles data and a program that handles the data. There is a component granularity as a unit representing the range of data and programs handled by one component, and there are several component granularities. For example, the granularity (hereinafter referred to as granularity 1) indicating the range of data and programs corresponding to the processing of data editing and data transmission performed in response to the user operating the system screen, and processing for accepting orders The granularity (hereinafter referred to as granularity 2) indicating the range of data and programs corresponding to one work in business, and the data and programs corresponding to the type of business transactions such as subsystems There is a particle size indicating the range (hereinafter referred to as particle size 3).

  A system to which a component is applied is designed after the granularity of the component is determined or on the premise of a certain granularity. As a technique for supporting system design on the premise of a certain granularity, there is a technique for organizing the relationship between subsystems interactively with a designer.

JP 2001-229213 A

  Since the difference in the granularity of components affects the design, development, and maintenance costs (hereinafter referred to as costs) of the system to be developed (hereinafter referred to as development target systems), determining the granularity is an important task. In spite of this, the system design work omits the granularity determination work, and tends to follow the granularity of components applied to systems with similar functions.

  The reason is that the task of determining the granularity of components is accompanied by difficulties. For example, the information on the development target system as information related to the design, development, and maintenance costs of the development target system to which the component is applied, or an existing system that will be partially or completely replaced by the development target system ( Since the following information is related to the granularity determination, the logic for determining the granularity becomes complicated. Further, when the development target system is composed of a plurality of layers as shown in FIG. 16, the combination of the granularity of components applied to the layers and the layers is, for example, for each layer as shown in FIG. Or a combination of component granularities for a plurality of layers as shown in FIG. 17B, or a plurality of granularities for one layer as shown in FIG. Can be combined, and there can be many combinations of component granularity and layers. Therefore, the derivation of the draft of the component granularity to be applied to the development target system and the calculation of the effect due to the application of the granularity are time consuming and require work based on experience.

The present invention has been made in view of such a background, and provides a design support apparatus that derives a proposal for applying a component granularity to a system to be developed and calculates an effect associated with the application of the granularity. Objective.

  The main invention of the present invention for solving the above-mentioned problems is a granularity application plan derivation processing unit for deriving a component granularity plan (hereinafter referred to as a granularity application plan) applicable to a development target system, and a plurality of A granularity application cost calculation processing unit for calculating an evaluation value (hereinafter referred to as a granularity application cost) of a granularity application plan used for determining a granularity application plan suitable for the system to be developed from the granularity application plans; .

  The main invention of the present invention registers information related to a system to which a component has been applied (hereinafter referred to as component application case information) as information used for calculation of a granularity application plan and a granularity application cost in the design support apparatus. Registered in the design support device using the component application case registration processing unit, the input desired case pattern derivation processing unit that derives the information necessary to register the component application case information in the design support device, and the component application case information A cost update processing unit for updating the value of the cost.

  According to the present invention, by deriving a granularity application plan and calculating a granularity application cost, it is possible to reduce the work performed by the designer and to increase the efficiency of determining the granularity of components applied to the system. Clarify the basis for determining the granularity by specifying the type of information used to determine the granularity, such as information on the system to be developed and information on existing systems, and specifying the logic for calculating the granularity application cost Therefore, it is possible to prevent the occurrence of different grounds for determining the granularity depending on the person who determines the granularity.

  In addition, in the registration of component application case information into the design support device, work for deriving the cost for each combination of granularity and layer applied to the layer included in the component application case information, and the design support device for the derived cost Compared to the case where component application case information is registered on a case-by-case basis, the information used to calculate the granularity application plan and the granularity application cost can be increased and the granularity application plan can be derived. The sex can be increased.

  In addition, the reliability of the value of the granularity application cost can be improved by replacing the value of the cost registered in the information used for the calculation of the granularity application plan and the granularity application cost with the value based on the component application case information.

It is a figure which shows the hardware constitutions and software constitutions of the design support system 1 which is one Embodiment of this invention. It is a figure which shows the hardware constitutions of information processing apparatus. It is a figure which shows the structural example of the information of a development object system. It is a figure which shows the structural example of the information of the existing system. It is a figure which shows the structural example of the information which shows a granularity application plan and a granularity application cost. It is a figure which shows the structural example of the information which manages the user who uses the design support system. It is a figure which shows the structural example of the information which shows the restrictions of the granularity of the component applied to a system. It is a figure which shows the structural example of the information which shows the decision tree for calculating a granularity application cost. It is a figure which shows the structural example of the information which shows the call direction of the layer which can be performed on a development object system. It is a figure which shows the structural example of the information which shows the cost which generate | occur | produces with the call between layers including the layer to which the granularity was applied. It is a figure which shows the structural example of the information which shows the order by which the path | route in which the decision tree for calculating a granularity application cost was searched, and the branch of the decision tree is referred. It is a figure which shows the flow of the process which derives a granularity application plan. It is a figure which shows the flow of the process which calculates a particle size application cost. It is a figure which shows the flow of a process which calculates the cost which generate | occur | produces with the call between the layers of a system. It is a figure which shows the flow of a process which calculates the reference order of the branch of the decision tree for calculating a granularity application cost. It is a figure which shows the example of the layer structure of a system. It is a figure which shows the example of the granularity of the component applied to the layer of a system. It is a figure which shows the hardware constitutions and software constitutions of the design support system 2 which is one Embodiment of this invention. It is a figure which shows the structural example of the information regarding the system to which the component was applied. It is a figure which shows the structural example of the information which shows whether the information regarding the system to which the component was applied has been registered into the decision tree for calculating the granularity application cost. It is a figure which shows the structural example of the information which needs the input to this design assistance apparatus, when calculating the cost for every layer to which the component was applied, or every combination of layers from the information regarding the system to which the component was applied. . It is a figure which shows the structural example of the information which shows the kind of method which calculated cost regarding the cost registered into the decision tree for calculating a granularity application cost. It is a figure which shows the structural example of the information which shows the calculation formula used for calculation of cost. It is a figure which shows the flow of a process which registers the information regarding the system to which the component was applied to the decision tree for calculating a granularity application cost. It is a figure which shows the flow of the process which derives | leads-out the information required in order to calculate the cost which is not registered into the decision tree for calculating a granularity application cost. It is a figure which shows the flow of the process which updates the cost which the decision tree for calculating a granularity application cost hold | maintains. It is a figure which shows the example of calculation of cost using component application example information. It is a figure which shows the example of a cost calculation using several component application example information.

  Hereinafter, the design support system 1 which is one Embodiment of this invention is demonstrated. When the system designer determines the granularity of a component to be applied to the system, the design support system 1 according to the present embodiment refers to information related to the design target system and definition information, and determines the granularity to be applied to the component. A value indicating the derivation of the draft and the evaluation of the draft of the granularity is calculated.

== System configuration ==
FIG. 1 is a diagram showing a hardware configuration and a software configuration of a design support system 1 according to an embodiment of the present invention. As shown in the figure, the design support system 1 of this embodiment includes a server computer 10 and a user computer 20. Each of the server computer 10 and the user computer 20 is connected to be communicable via a communication network 30. The communication network 30 is, for example, a LAN (Local Area Network) constructed by a dedicated telephone line network or Ethernet (registered trademark).

  The server computer 10 is an information processing apparatus that derives a granularity application plan and calculates a granularity application cost. The server computer 10 is, for example, a personal computer, a workstation, an office computer, a mainframe, or the like.

== Hardware ==
FIG. 2 is a diagram illustrating a hardware configuration of an information processing apparatus used as the server computer 10 and the user computer 20. As shown in the figure, the information processing apparatus includes a CPU 51, a memory 52, a hard disk 53, an input device 54, a display device 55, and a communication interface 56. The hard disk 53 stores various programs and data. The CPU 51 implements various functions by reading the program stored in the hard disk 53 into the memory 52 and executing it. The input device 54 is a user interface for inputting data, such as a keyboard and a mouse. The display device 55 is a user interface for displaying data, such as a display. The communication interface 56 is an interface for connecting to the communication network 30.

== User computer 20 ==
A user computer 20 in FIG. 1 is an information processing apparatus used by a user who uses the design support system 1. The user computer 20 is, for example, a personal computer, a workstation, an office computer, or the like. The user operates the user computer 20 to access the server computer 10 and obtains a granularity application plan and a granularity application cost as materials for determining the granularity of components applied to the development target system. The user computer 20 includes a user input information registration request processing unit 201, a user input information registration result display processing unit 202, an application granularity determination request processing unit 203, and an application granularity determination result display processing unit 204.

  The user input information registration request processing unit 201 accepts information input by the user (hereinafter referred to as user input information), transmits user input information to the server computer 10, and commands for requesting registration of user input information ( Hereinafter, the user input information registration request is transmitted to the server computer 10. The user input information specifically refers to information on a development target system and information on an existing system.

  The user input information registration result display processing unit 202 is a value indicating whether or not to register user input information sent as a response of the server computer 10 to the user input information registration request, and a value for uniquely identifying the registered development target system (hereinafter referred to as development). A target system ID) and a value uniquely identifying an existing system (hereinafter referred to as an existing system ID) are displayed.

  The application granularity determination request processing unit 203 is a development target system that is a target for derivation of a granularity application plan and calculation of a granularity application cost, which identifies a user who uses the design support system 1 (hereinafter referred to as a user ID). Receiving the development target system ID and the existing system ID of the existing system corresponding to the development target system indicated by the development target system ID, sending the user ID, the development target system ID, and the existing system ID to the server computer 10, and A command for requesting the derivation of the granularity application plan and the calculation of the granularity application cost (hereinafter referred to as a granularity application determination request) is transmitted to the server computer 10.

  The application granularity determination result display processing unit 204 displays a list of information that is sent as a response of the server computer 10 to the granularity application determination request and includes a combination of the granularity application plan and the granularity application cost.

== Server computer 10 ==
The server computer 10 in FIG. 1 performs processing for deriving a granularity application plan to be applied to the development target system and calculating a granularity application cost, and manages various data used in the server computer 10. The server computer 10 includes a user input information registration unit 101, a granularity application plan derivation processing unit 102, a granularity application cost calculation processing unit 103, an inter-layer call cost calculation processing unit 104, and a decision tree reference order update process for a granularity application cost calculation rule. Unit 105 and DBMS (DataBase Management System) 40. The DBMS 40 includes a development target system information holding table 151, an existing system information holding table 152, a granularity application plan holding table 153, a usage user management information 154, a granularity constraint information management table 155, a granularity application cost calculation rule management information 156, and between layers. It manages the call relationship management information 157, the inter-layer call cost management table 158, and the decision tree reference information management table 159.

  Note that the user input information registration unit 101, the granularity application plan derivation processing unit 102, the granularity application cost calculation processing unit 103, the inter-layer call cost calculation processing unit 104, the decision tree reference order update processing unit 105 for the granularity application cost calculation rule, The DBMS 40 is realized by the CPU 51 included in the server computer 10 reading out the program stored in the hard disk 53 to the memory 52 and executing it. Further, the development target system information holding table 151, the existing system information holding table 152, the granularity application plan holding table 153, the use user management information 154, the granularity constraint information management table 155, and the granularity application cost calculation rule management information 156 managed by the DBMS 40. The inter-layer call relationship management information 157, the inter-layer call cost management table 158, and the decision tree reference information management table 159 are realized as storage areas provided by the memory 52 and the hard disk 53.

  The development target system information holding table 151 stores development target system information (hereinafter referred to as development target system information). FIG. 3 is a diagram illustrating a configuration example of the development target system information stored in the development target system information holding table 151. As shown in the figure, the development target system information includes a development target system ID 1511, a layer type 1512 indicating a range of layers on the development target system affected by the development target system information, and a type of information of the development target system. A development target system information item 1513 to be shown, and a development target system information item value 1514 to indicate the value of the information indicated by the development target system item 1513 are included.

  The existing system information holding table 152 stores information on existing systems (hereinafter referred to as existing system information). FIG. 4 is a diagram illustrating a configuration example of existing system information stored in the existing system information holding table 152. As shown in the figure, in the existing system information, the existing system ID 1521, the layer type 1522 indicating the range of the layer on the existing system affected by the information of the existing system, the existing system information item indicating the type of information of the existing system 1523, and an existing system information item value 1524 indicating the value of the information indicated by the existing system item 1523.

  The granularity application plan holding table 153 stores a granularity application plan and a cost that is expected to be generated by applying the granularity application plan to the development target system (hereinafter referred to as a granularity application cost). FIG. 5 is a diagram illustrating a configuration example of the granularity application plan and the granularity application cost stored in the granularity application plan holding table 153. As shown in the figure, a granularity application plan ID 1531 indicating a value uniquely identifying the granularity application plan, a granularity application plan 1532, and a granularity application cost 1533 are included.

  The use user management information 154 stores information on users who use the design support system 1. FIG. 6 is a diagram illustrating a configuration example of information stored in the use user management information 154. As shown in the figure, a user ID 1541 is included.

  The granularity constraint information management table 155 stores information indicating the granularity constraints of components (hereinafter, granularity constraint information). FIG. 7 is a diagram illustrating a configuration example of the granularity constraint information stored in the granularity constraint information management table 155. As shown in the figure, a granularity type 1551 indicating the size of the granularity, a granularity restriction type 1552 indicating the type of granularity restriction, and a granularity restriction content 1553 indicating the content of the granularity restriction are included. Specifically, the granularity constraint content indicates whether or not a granularity can be applied to a layer and whether or not multiple types of granularity can be applied to a layer. For example, the value of the granularity type 1551 is “granularity 1”, the value of the granularity constraint type 552 is “applicability of granularity to the system layer”, and the value of the granularity constraint content 103 is “applicable: layer B, layer C The granularity constraint information of “layer U not applicable: layer E” indicates that “granularity 1 is applicable to layer B, layer C, and layer U, and not applicable to layer E”. In addition, the value of the granularity type 1551 is “combination of granularity 1 and granularity 2”, the value of the granularity constraint type 1552 is “existence of the exclusive relationship of the granularity applied to the layer”, and the value of the granularity constraint content 1553 is “exclusive” : Layer E, Layer B, Layer C, Layer U ”indicates that“ granularity 1 and granularity 2 cannot be applied simultaneously in any of layer E, layer B, layer C, and layer U ”. Show.

  The granularity application cost calculation rule management information 156 is information for calculating the effect of the granularity application on the development target system on the cost, and is represented as a so-called decision tree (hereinafter referred to as a granularity application cost decision tree). ) Is memorized. FIG. 8 is a diagram illustrating a configuration example of information stored in the rule application information 156 for calculating the granularity application cost. As shown in the figure, the relationship between the evaluation item and the value of the evaluation item is represented by a tree structure, and the granularity application cost is indicated at the end of the decision tree. Specifically, the evaluation items correspond to the type of layer, the type of granularity, the development target system information item 1513 of the development target system information holding table 151, and the existing system information item 1523 of the existing system information holding table 152.

  The inter-layer call relationship management information 157 stores information (hereinafter referred to as inter-layer call relationship information) indicating the layer call direction possible on the development target system. FIG. 9 is a diagram illustrating a configuration example of inter-layer call relationship information stored in the inter-layer call relationship management information 157. As shown in the figure, an inter-layer call relationship 1571 indicating inter-layer call relationship information is included. For example, when the value of the inter-layer call relationship 1571 is “layer U → layer E”, this indicates that the layer E can be called from the layer U.

  The inter-layer call cost management table 158 stores information related to a cost (hereinafter referred to as an inter-layer call cost) that occurs due to a call between layers including a layer to which the component granularity is applied. FIG. 10 is a diagram illustrating a configuration example of information stored in the inter-layer call cost management table 158. As shown in the figure, an inter-layer call pattern 1581 showing a combination of the granularity of components applied to a layer and a layer (hereinafter referred to as an inter-layer call pattern) in a call between layers, and an inter-layer to a development target system It includes a reference cost 1582 that indicates an evaluation of the application of the calling pattern.

  The decision tree reference information management table 159 includes a path on which the granularity application cost determination tree indicated by the granularity application cost calculation rule management information 156 is searched, and the granularity application cost determination tree on the granularity application cost determination tree. The order of referring to the branches is stored in association with the user who uses the design support system 1. Note that storing the order of referring to branches in advance aims to improve the efficiency of the search process of the decision tree. FIG. 11 is a diagram illustrating a configuration example of information stored in the decision tree reference information management table 159. As shown in the figure, a user ID 1591 indicating the user who requested the calculation of the granularity application plan and the granularity application cost, and an evaluation item 1592 indicating a value uniquely identifying the evaluation item corresponding to the node on the granularity application cost decision tree. Evaluation item value 1593 indicating the value of the evaluation item, evaluation item value selection count 1594 indicating the number of times the evaluation item value has been selected when calculating the granularity application cost, and evaluation item when calculating the granularity application cost The evaluation item value reference order 1595 indicating the order in which the values are referred to is included.

  The user input information registration unit 101 receives a user input information registration request and user input information transmitted from the user computer 20, registers user input information in a storage area, assigns a development target system ID, and assigns an existing system ID. Then, a value indicating whether user input information can be registered, a development target system ID, and an existing system ID are transmitted to the user computer 20. Specifically, the user input information is registered in the storage area by registering the development target system information included in the user input information in the development target system information holding table 151 and the existing system information included in the user input information. Registration in the system information holding table 152 is performed.

  The granularity application plan derivation processing unit 102 receives the granularity application determination request, the user ID, the development target system ID, and the existing system ID transmitted from the user computer 20, derives the granularity application plan, and applies the granularity of the derived granularity application plan. Registration in the plan holding table 153 is performed.

  The particle size application cost calculation processing unit 103 calculates the particle size application cost by applying the particle size application plan to the development target system, and transmits the information obtained by combining the particle size application plan and the particle size application cost to the user computer 20. .

  The inter-layer call cost calculation processing unit 104 calculates a cost caused by a call between layers including a layer to which the granularity is applied.

  The decision tree reference order update processing unit 105 of the granularity application cost calculation rule calculates the reference order of the branches of the granularity application cost determination tree indicated by the granularity application cost calculation rule management information 156 when calculating the granularity application cost. The calculated reference order is reflected in the decision tree reference order management table 159.

== Derivation of component application granularity plan and evaluation process of plan ==
Hereinafter, processing of the server computer 10 will be described. FIG. 12 is a diagram illustrating a processing flow of the granularity application plan derivation processing unit 102 when a granularity application determination request is received.

When the granularity application plan derivation processing unit 102 receives the granularity application determination request, the user ID, the development target system ID, and the existing system ID from the user computer 20 (S200), the existing system information corresponding to the received existing system ID is stored in the existing system. Obtained from the information holding table 152 (S205). Next, the granularity application plan derivation processing unit 102 acquires granularity constraint information from the granularity constraint information management table 155 (S210), refers to the acquired granularity constraint information and existing system information, and derives a granularity application plan (S215). ). Specifically, a combination contrary to the granularity constraint information and the existing system information is excluded from the combination of granularities applied to the layer, and the combination that is not excluded is handled as a granularity application plan. For example, when information indicating that “granularity 1 cannot be applied to layer E” is described in the granularity constraint information, a granularity combination that applies granularity 1 to layer E is excluded. Further, when information indicating information indicating that “new development of layer C cannot be performed” is described in the existing system information, a granularity combination that applies granularity to layer C is excluded. Next, the granularity application plan derivation processing unit 102 registers all derived granularity application plans in the granularity application plan holding table 153 (S220), and calls the granularity application cost calculation processing unit 103 (S225). At the time of calling, the user ID, the development target system ID, the existing system ID, and the existing system information are passed to the granularity application cost calculation processing unit 103.

FIG. 13 is a diagram illustrating a processing flow of the granularity application cost calculation processing unit 103. The granularity application cost calculation processing unit 103 acquires development target system information corresponding to the development target system ID from the development target system information holding table 151 (S300). Next, the granularity application cost calculation processing unit 103 acquires one granularity application proposal from the granularity application proposal holding table 153 (S305), and acquires one set of granularity and layer included in the acquired granularity application proposal ( S310). If the granularity application cost has not been calculated for the acquired granularity and layer combination (S315: Yes), the acquired granularity and layer combination, development target system information, existing system information, and granularity application cost calculation rule management With reference to the granularity application cost decision tree indicated by the information 156, the granularity application cost for the set of the obtained granularity and layer is calculated (S320), and information indicating the search path of the granularity application cost decision tree is obtained from the granularity and layer. The data is stored in a storage area such as the memory 52 in association with the set and the calculated granularity application cost. Note that the order of branches to be referred to in the granularity application cost decision tree follows the evaluation item value reference order 1595 of the decision tree reference order management table 159.

  When the granularity application cost is already calculated for the acquired granularity and layer pair (S315: No), the granularity application cost stored in the storage area such as the memory 52 in association with the granularity and layer pair. And the addition of the number of searches for the granularity application cost decision tree stored in the storage area associated with the granularity and layer pair. When the granularity application cost calculation processing unit 103 has acquired the granularity application cost for all the combinations of the granularity and the layer included in one granularity application proposal (S335: Yes), On the other hand, the sum of the granularity application costs calculated as the granularity application cost is handled as the granularity application cost of the granularity application plan, and the inter-layer call cost calculation processing unit 104 is called to obtain the inter-layer call cost (S340). When a set of granularity and layer included in one granularity application proposal includes a combination of granularity and layer for which acquisition of the granularity application cost has not been completed (S335: No), other granularities included in the granularity application proposal And a set of layers is acquired (S310).

  When the granularity application cost calculation processing unit 103 acquires the granularity application cost for all the granularity application proposals (S345: Yes), the granularity application cost is linked to the granularity application proposal in the granularity application proposal holding table 153. Registered in the granularity application cost 1533 (S350), sends a list of combinations of the granularity application plan and the granularity application cost to the user computer 20 (S355), and calls the decision tree reference order update processing unit of the granularity application cost calculation rule ( S360).

  FIG. 14 is a diagram illustrating a processing flow of the inter-layer call cost calculation processing unit 104. The inter-layer call cost calculation processing unit 104 acquires the inter-layer call relationship 1571 of the inter-layer call relationship management information 157 (S400), calculates the inter-layer call cost for each acquired inter-layer call relationship, The inter-layer call cost is calculated for the inter-layer call relationship (S405). Specifically, the inter-layer call cost is calculated by first combining the acquired inter-layer call relationship with the granularity information to be applied to the layer indicated in the granularity plan, and then the combined information and inter-layer call. The granularity and layer combination indicated in the inter-layer call pattern 1581 of the cost management table 158 are compared, and the value of the standard cost 1582 of the granularity and layer combination whose values match is obtained. Next, a value obtained by multiplying the acquired reference cost by the value of the business scale of the development target system information is handled as an inter-layer call cost.

  FIG. 15 is a diagram illustrating a processing flow of the decision tree reference order update processing unit 105 for the granularity application cost calculation rule. The decision tree reference order update processing unit 105 of the rule for calculating the granularity application cost calculates the decision tree reference information from the information indicating the search path of the decision tree and the information indicating the search frequency of the search path passed from the granularity application cost calculation processing unit 103. The number of evaluation item value selections, which is the number of times the evaluation item value corresponding to this branch is selected, is calculated, and the calculated evaluation item value selection number is added to the evaluation item value selection number accumulated 1594 (S500). Next, for each evaluation item, the reference value of the evaluation item value indicated in the evaluation item value reference order 1595 is changed according to the order of the largest evaluation item value selection count 1594 (S505).

  Hereinafter, the design support system 2 which is one Embodiment of this invention is demonstrated. The design support system 2 of the present embodiment supports the operation of registering component application case information in the rule management information 156 for calculating the granularity application cost. The component application case information indicates the component applied to the system layer. For each set of granularity and layer, a cost is calculated, information necessary for calculating the cost is derived, and the calculated cost is registered in the granularity application cost calculation rule management information 156. In addition, by using the component application case information among the costs registered in the granularity application cost calculation rule management information 156, the value can be updated with respect to the cost in which the cost value can be replaced with a more reliable value. Do.

== System configuration ==
FIG. 18 is a diagram showing a hardware configuration and a software configuration of the design support system 2 which is an embodiment of the present invention. As shown in the figure, the design support system 2 of this embodiment includes a server computer 11 and a user computer 21. Each of the server computer 11 and the user computer 21 is communicably connected via a communication network 30. The communication network 30 is, for example, a LAN (Local Area Network) constructed by a dedicated telephone line network or Ethernet (registered trademark).

  The server computer 11 is an information processing apparatus that registers component application case information. The server computer 11 is, for example, a personal computer, a workstation, an office computer, a main frame, or the like.

== User computer 21 ==
18 is an information processing apparatus used by a user who uses the design support system 2. The user computer 21 is, for example, a personal computer, a workstation, an office computer, or the like. The user operates the user computer 21 to access the server computer 11 and transmits component application case information to the server computer 11. The user computer 21 includes a component application case registration request processing unit 211 and a component application case registration result display processing unit 212.

  The component application case registration request processing unit 211 transmits information indicating that registration of component application case information is requested (hereinafter referred to as component application case registration request) and component application case information to the server computer 11.

  The component application case registration result display processing unit 212 displays various information transmitted from the server computer 11 to the user computer 21 as a result of transmitting the component application case registration request to the server computer 11.

== Server computer 11 ==
The server computer 11 in FIG. 18 performs processing for calculating the granularity application cost using the component application case information and the granularity application cost calculation rule management information 156, and manages various data used in the server computer 11. The server computer 11 includes a component application case registration processing unit 111, an input desired case pattern derivation processing unit 112, a cost update processing unit 113, and a DBMS (DataBase Management System) 40. The DBMS 40 includes a registration component application case holding table 171, an application case registration presence / absence holding table 172, an input desired case pattern holding table 173, a cost acquisition type holding table 174, a cost estimation formula holding table 175, and granularity application cost calculation rule management information. 156, inter-layer call relationship management information 157, and inter-layer call cost management table 158 are managed.

  The component application case registration processing unit 111, the input desired case pattern derivation processing unit 112, the cost update processing unit 113, and the DBMS 40 read the program stored in the hard disk 53 by the CPU 51 included in the server computer 11 to the memory 52. It is realized by executing. Also, a registration component application case holding table 171, an application case registration presence / absence holding table 172, an input desired case pattern holding table 173, a cost acquisition type holding table 174, a cost estimation formula holding table 175, and a granularity application cost calculation managed by the DBMS 40. The rule management information 156, the inter-layer call relationship management information 157, and the inter-layer call cost management table 158 are realized as storage areas provided by the memory 52 and the hard disk 53.

  The component application case holding table 171 for registration stores component application case information. The information included in the component application case information includes the type of component granularity applied to the system layer, the cost of the entire system due to application of the component (hereinafter referred to as total component application cost), and the development target system information holding table 151. This corresponds to the development target system information item 1513 and the existing system information item 1523 of the existing system information holding table 152. FIG. 19 is a diagram illustrating a configuration example of the component application case information stored in the registration component application case holding table 171. As shown in the figure, a registration component application case ID 1711 indicating a value for identifying component application case information and a registration component application case 1712 indicating the contents of the component application case information are included.

  The application case registration presence / absence holding table 172 stores information indicating whether or not the content of the component application case information has been registered in the rule management information 156 for granularity application cost calculation. FIG. 20 is a diagram illustrating a configuration example of information stored in the application case registration presence / absence holding table 172. As shown in the figure, the component application case reference ID 1721 for registration indicating the component application case, the granularity application layer 1722 indicating the combination of the granularity and the layer included in the component application case, and the component application case information are stored in the granularity application layer 1722. In the unit of the set of granularity and layer to be shown, the case of registered granularity case presence / absence 1723 indicating whether or not registered in the granularity application cost calculation rule management information 156 is registered in the case of registered granularity case presence / absence 1723 A granularity application cost calculation rule reference ID 1724 indicating a value uniquely identified in the cost calculation rule management information 156 is included.

  If the input desired case pattern holding table 173 cannot calculate the cost for each set of granularity and layer constituting the component application case information only from the component application case information and the granularity application cost calculation rule management information 156, Information indicating the characteristics of other component application examples necessary for calculating the cost is stored. FIG. 21 is a diagram illustrating a configuration example of information stored in the input desired case pattern holding table 173. As shown in the figure, it includes a registration component application case reference ID 1731 that indicates a value that uniquely identifies component application case information, and an input desired case pattern 1732 that indicates the characteristics of the component application case that is necessary for calculating the cost. .

  The cost acquisition type holding table 174 stores a cost value acquisition method and a value indicating the type of cost calculation method (hereinafter referred to as cost acquisition type) regarding the cost indicated in the granularity applied cost calculation rule management information 156. To do. The cost acquisition types are classified into three types, actual measurement values, first estimated values, and second estimated values. When the component application case has only one set of granularity and layer, the total component application cost value of the component application example becomes the cost value of the granularity and layer pair, and the cost acquisition type of that cost is the actual measurement value. deal with. Further, the cost calculated by the calculation formula using only the actual measurement value is handled as the first estimated value. Further, the cost calculated by the calculation formula using the first estimated value is handled as the second estimated value. FIG. 22 is a diagram illustrating a configuration example of information stored in the cost acquisition type holding table 174 information. As shown in the figure, the cost of the cost specified by the granularity application cost calculation rule reference ID 1741 and the granularity application cost calculation rule reference ID 1741 indicating values for identifying the costs in the granularity application cost calculation rule management information 156. A cost acquisition type 1742 indicating the acquisition type is included.

  The cost estimation formula holding table 175 includes information (hereinafter referred to as a cost estimation formula) including information specifying other costs used for calculating the cost and a calculation formula used for the calculation, and a cost using the cost estimation formula. The information indicating whether or not there is an update (hereinafter referred to as a cost update record) is stored. FIG. 23 shows a configuration example of information stored in the cost estimation formula holding table 175. As shown in the figure, a cost estimation formula 1751 and a cost update record 1752 are included.

The component application case registration processing unit 111 receives the component application case registration request and the component application case information transmitted from the user computer 21, registers the component application case information in the storage area, and the granularity and layer included in the component application case information. The cost of each set is acquired as an actual measurement value, or the estimated value of the cost is calculated, the various information including the cost is registered in the rule management information 156 for calculating the granularity application cost, and the user computer of the registration result of the component application case information 21 is transmitted. Specifically, the cost is calculated using a linear expression using subtraction. For example, as shown in FIG. 27A, the estimated cost of a system in which granularity 1 is applied to layer U, granularity 1 is applied to layer U, and granularity 2 is applied to layer C, as shown in FIG. This is calculated by subtracting the cost value of the system in which the granularity 2 is applied to the layer C as shown in FIG. Note that the cost of inter-layer calling is calculated as a constant according to the type of granularity included in the primary expression and the value of the business scale included in the component application example information, and is included in the primary expression. For registering component application case information in the storage area, specifically, a component application case ID for registration is assigned as a value for uniquely identifying the component application case information, and the component application case information is stored in the component application case holding table for registration. Add to 171.

  The input desired case pattern derivation processing unit 112 has a granularity and layer whose cost cannot be calculated only by the information of the component application case information and the granularity application cost calculation rule management information 156 among the granularity and layer pairs included in the component application case information. The characteristic (hereinafter referred to as an input desired case pattern) that should be possessed by another component application example (hereinafter referred to as an input desired case) that is necessary for calculating the cost is derived for the set. The derived feature refers to the type of component granularity applied to the layer. Hereinafter, an image of processing for calculating the granularity application cost using the input desired example will be shown. For example, from the information of the component application example having the characteristics shown in FIG. 28A, the estimated cost of the system in which the granularity 1 is applied to the layer U as shown in FIG. 28B, shown in FIG. 28C. As shown in FIG. 28 (d), the estimated cost of the system in which the granularity 2 is applied to the layer C and the estimated cost of the granularity 2 applied to the layer B are calculated. ), And the costs corresponding to the systems shown in FIGS. 28C and 28D are not registered in the granularity application cost calculation rule management information 156. In this situation, as shown in FIGS. 28 (e) and 28 (f), the combinations of layers and granularities shown in FIGS. 28 (b), 28 (c), and 28 (d) are combined. When component application case information exists, the estimated cost value corresponding to each system in FIGS. 28B, 28C, and 28D is referred to as a variable (hereinafter referred to as an estimated cost variable). A linear equation can be provided. Specifically, for the system of FIG. 28 (e), the sum of the estimated cost variable corresponding to FIG. 28 (b) and the estimated cost variable corresponding to FIG. 28 (c) is shown in FIG. A linear equation is provided so as to be equal to the value of the total component application cost. By providing a linear equation including an estimated cost variable for each of the component application case information shown in FIG. 28 (a), FIG. 28 (e), and FIG. 28 (f), the number of estimated cost variables A system of linear equations exists. It is possible to calculate the value of the estimated cost variable from this simultaneous linear equation, and the estimated value of the granularity application cost corresponding to each system of FIG. 28 (b), FIG. 28 (c), and FIG. I want. In this example, component application cases corresponding to FIGS. 28C and 28D are treated as input desired case patterns.

  The cost update processing unit 113 performs a process of increasing the reliability of the cost value held in the granularity application cost calculation rule management information 156. Specifically, out of the costs held by the rule management information 156 for calculating granularity applied costs, the cost value whose cost acquisition type is the first estimated value is updated with the cost value whose cost acquisition type is the actual measurement value. . Further, the cost acquisition type is updated as the second estimated value using the updated cost and the cost estimation formula used in the past.

== Component application case information registration process ==
Hereinafter, processing of the server computer 11 will be described. FIG. 24 is a diagram illustrating a processing flow of the component application case registration processing unit 111 when a component application case information registration request is received.

  When the component application case registration processing unit 111 receives the component application case registration request and the component application case information from the user computer 21, the component application case registration processing unit 111 assigns a value for uniquely identifying the component application case information, and then registers the component application case registration table. The component application case information is registered in 171 (S800). Next, the component application case registration processing unit 111 has already registered in the rule management information 156 for the granularity application cost calculation, for each granularity and layer pair constituting the component application case information, the cost corresponding to the granularity and layer pair. And the search result is registered in the registered granularity case absence 1723 of the application case registration presence / absence holding table 172 (S805). If there is a set that has not been registered in the granularity application cost calculation rule management information 156 among the set of granularity and layer constituting the component application case information received in S800 (S810: Yes), the process proceeds to S815. When all the costs corresponding to the combination of the granularity and the layer have been registered in the granularity application cost calculation rule management information 156 (S810: No), the cost update processing unit 113 is called (S860). At the time of calling, the component application case ID is passed to the cost update processing unit 113. After the cost update processing unit 113 performs the update processing of the cost value held in the granularity application cost calculation rule management information 156, the component application case registration processing unit 111 proceeds to S865. The processing contents of the cost update processing unit 113 are shown in the description of FIG.

  In S815, for the set of granularity and layer that has not been registered in the granularity application cost calculation rule management information 156 specified in S805 (hereinafter, referred to as an unregistered case), an estimated cost value is calculated. It is determined whether or not it is possible using the application case information and the rule application information for calculating granularity application cost 156. Specifically, in the application case registration presence / absence holding table 172, if there is one unregistered case for one component application case information, it is considered that the estimated cost can be calculated by a linear expression. In these cases, it is considered that calculation using a linear expression is not possible. When it is determined that the calculation is possible (S820: Yes), an estimated value of the cost of the unregistered case is calculated (S825). The processing content of S825 will be described later. When it is determined that the calculation is impossible (S820: No), the input desired case pattern derivation processing unit 112 is called (S835). When calling, the component application case ID is passed to the input desired case pattern derivation processing unit 112. After the input desired case pattern derivation processing unit 112 derives the input desired case pattern, the component application case registration processing unit 111 transitions to S840. The processing content of the input desired case pattern derivation processing unit 112 is shown in the description of FIG.

  In S825, the component application case registration processing unit 111 first describes in the registered granularity case presence / absence 1723 of the application case registration presence / absence holding table 172 that “registration in the rule management information 156 for granularity application cost calculation” is present. The cost is acquired from the granularity application cost calculation rule management information 156. Next, an estimated value of the cost of an unregistered case is calculated by subtracting the cost acquired from the granularity application cost calculation rule management information 156 from the component application total cost of the component application case information. Next, the cost acquisition type of the cost acquired from the granularity applied cost calculation rule management information 156 is acquired from the cost acquisition type holding table 174, and the cost acquisition type of the cost of the unregistered case is determined according to the value. . Next, assuming that the cost update processing unit 113 uses the component application case information for the next and subsequent registrations, the cost estimation formula used to calculate the estimated cost value and the cost acquisition type of the unregistered case are set. sign up. Specifically, the cost estimation formula is registered in the cost estimation formula 1751 of the cost estimation formula holding table 175 and the fact that “not updated” is indicated in the cost update record 1752 is registered. Further, the cost acquisition type is registered in the cost acquisition type 1742 of the cost acquisition type holding table 174, and the process proceeds to S830.

  In S830, the component application case registration processing unit 111 registers the estimated value of the cost of the unregistered case in the rule application information for calculating granularity application cost 156 together with the component application case information in the component application case holding table 171 for registration. The process proceeds to S865.

  In S840, the component application case registration processing unit 111 first acquires the input desired case pattern calculated by the input desired case pattern derivation processing unit 112 from the input desired case pattern 1732 of the input desired case pattern holding table 173. Next, component application case information corresponding to the input desired case pattern is acquired from the registration component application case 1712 in the registration component application case holding table 171 and information indicating the combination of granularity and layer is obtained from the acquired component application case information. And the information excluding the component total application cost and the input desired case pattern are transmitted to the user computer 11, and the input desired case information is received from the user computer 11 in S 845.

  In S850, first, the cost of an unregistered case is calculated using the received information on the input desired case. As shown in the explanation of the input desired case pattern derivation processing unit 112, the cost is calculated by providing a linear equation with the cost of each unregistered case as a variable for each information of the input desired case corresponding to the input desired case pattern. This is done by finding the value of the variable in the way of solving the simultaneous linear equations. Next, the cost acquisition type of the cost of the unregistered case is determined according to the value of the cost acquisition type of the other cost used for calculating the cost of the unregistered case. When the cost is acquired from the granularity applied cost calculation rule management information 156, the cost acquisition type is acquired from the cost acquisition type holding table 174. Next, it is assumed that the cost update processing unit 113 will use it when registering component application case information from the next time onward, and the cost estimation formula used to calculate the estimated value of the cost and the cost of the cost of the unregistered case Register the acquisition type. Specifically, the cost estimation formula is registered in the cost estimation formula 1751 of the cost estimation formula holding table 175 and the fact that “not updated” is indicated in the cost update record 1752 is registered. Further, the cost acquisition type is registered in the cost acquisition type 1742 of the cost acquisition type holding table 174, and the process proceeds to S855.

  In S855, the cost calculated in S850 is registered in the granularity application cost calculation rule management information 156 together with the component application case information in the registration component application case holding table 171, and the process proceeds to S865.

  In S865, information indicating that the registration of the component application case information into the design support apparatus is completed is transmitted to the user computer 11.

  FIG. 25 is a diagram illustrating a processing flow of the input desired case pattern derivation processing unit 112. First, the input desired case pattern derivation processing unit 112 uses the component application case information to derive an input desired case pattern used for deriving the cost of an unregistered case (S900). Specifically, an unregistered case is acquired from the application case registration presence / absence holding table 172, and a plurality of input desired case patterns are derived by combining the granularity and the layer combination indicated in the unregistered case. Next, the desired input case pattern derivation processing unit 112 registers the derived desired input case pattern in the desired input case pattern 1732 of the desired input case pattern holding table 173 (S905).

  FIG. 26 is a diagram showing a flow of processing of the cost update processing unit 113. The cost update processing unit 113 acquires the set of granularity and layer included in the component application case information from the application case registration presence / absence holding table 172 (S1000), and there is one set of granularity and layer included in the component application case information. If only (S1005: Yes), the process proceeds to S1010. If there are two or more pairs of granularity and layers (S1005: No), it is considered that the cost of the granularity application cost calculation rule management information 156 cannot be updated, and the process is terminated.

  In S1010, the cost update processing unit 113 first uses the granularity application cost calculation rule reference ID 1724 in the application case registration presence / absence holding table 172, and the granularity application cost calculation rule corresponding to the combination of the granularity and the layer acquired in S1000. The ID is acquired, and then the cost acquisition type corresponding to the acquired granularity application cost calculation rule ID is acquired from the cost acquisition type holding table 174.

  In S1015, when the value of the cost acquisition type is the first estimated value or the second estimated value (S1015: Yes), the process proceeds to S1020, and the value of the cost acquisition type is either the first estimated value or the second estimated value. If not (S1015: No), it is considered that there is no granularity application cost to be updated, and the process ends.

  In S1020, the granularity application cost calculation rule management information 156 specifies the granularity application cost calculated using the granularity application cost corresponding to the combination of the granularity and the layer. Specifically, from the cost estimation formula holding table 175, for the cost estimation formula corresponding to the granularity application cost calculation rule ID obtained in S1010, the value of the cost update record indicates “not updated”. Then, for the granularity application cost obtained from the cost estimation formula, value calculation and identification of the granularity application cost calculation rule ID are performed, and the process proceeds to S1025.

  In S1025, first, in the granularity application cost calculation rule management information 156, the cost value corresponding to the granularity application cost calculation rule ID acquired in S1010 is replaced with the component application total cost value of the component application case information. Next, in the granularity application cost calculation rule management information 156, the granularity application cost value corresponding to the granularity application cost calculation rule ID specified in S1020 is replaced with the granularity application cost value calculated in S1020. Also, in the cost acquisition type holding table 174, the value of the cost acquisition type 1742 corresponding to the granularity application cost calculation rule ID acquired in S1010 is changed to “actual value”, and the granularity application cost calculation rule acquired in S1010 The value of the cost acquisition type 1742 corresponding to the ID is changed to “first estimated value”. Further, in the cost estimation formula holding table 175, the value of the cost update record 1752 corresponding to the cost estimation formula used in S1020 is changed to indicate “updated”.

1 Design Support System 10 Server Computer 20 User Computer 30 Communication Network 40 DBMS
51 CPU
52 memory 53 hard disk 54 input device 55 display device 56 communication interface 101 user input information registration processing unit 102 granularity application plan derivation processing unit 103 granularity application cost calculation processing unit 104 inter-layer call cost calculation processing unit 105 Decision tree reference order update processing unit 151 Development target system information holding table 152 Existing system information holding table 153 Granularity application plan holding table 154 User management information 155 Granularity constraint information management table 156 Rule management information for granularity application cost calculation 157 Inter-layer call Relationship management information 158 Inter-layer call cost management table 159 Decision tree reference order management table 201 User input information registration request processing unit 202 User input information registration result display processing unit 203 Application granularity determination request processing unit 204 Application granularity determination result Display processing unit 11 Server computer 21 User computer 111 Component application case registration processing unit 112 Input desired case pattern derivation processing unit 113 Cost update processing unit 171 Registration component application case holding table 172 Application case registration presence holding table 173 Input desired case pattern holding Table 174 Cost acquisition type holding table 175 Cost estimation formula holding table 211 Component application case registration request processing unit 212 Component application case registration result display processing unit

Claims (3)

An information processing device that supports the design of a system to be developed,
Refer to the information on the development target system, the information on the existing system that the system will replace in whole or in part, and the information on the granularity constraint that is a unit indicating the size of the component applied to the development target system A granularity application plan derivation processing unit for deriving a granularity application plan that is a proposal of the granularity of components applicable to the development target system;
Granularity application cost calculation showing the relationship between the granularity application proposal, the development target system information, the existing system information, the cost associated with the design, development and maintenance of the existing system and various evaluation items See the rules information and
With the application of the granularity application proposal to the development target system, the granularity applied to each layer of the development target system is specified, and the granularity application cost determined for each granularity is reflected on the specified granularity. , A granularity application cost calculation processing unit that calculates a cost that is a cost associated with design, development, and maintenance of the development target system;
An information processing apparatus comprising: The information processing apparatus according to claim 1,
The particle size application cost calculation processing unit
When expressing the granularity application cost calculation rule information as a decision tree, the branch of the decision tree is referred to according to the information indicating the order of referring to the branch of the decision tree, and the information indicating the search path of the decision tree is stored. A searched route information storage unit ;
A decision tree reference order update processing unit that updates a reference order of the branches of the decision tree based on the information indicating the search path and information indicating a cumulative number of times the branches of the decision tree are referred to;
An information processing apparatus further comprising: An information processing apparatus according to claim 2 ,
The particle size application cost calculation processing unit
Information indicating the combination of the type of system layer included in the proposed granularity application and the granularity of components applied to the layer, and the granularity application cost calculated based on various types of information, the type of layer and the type of granularity The combination of the layer type and the granularity type included in the granularity application proposal when calculating the granularity application cost is the combination of the stored layer type and the granularity type. If it matches, the information processing apparatus is characterized in that the stored granularity application cost is obtained without searching the decision tree.

Images