JP5041986B2 - Component division support device, method and program thereof - Google Patents

Description

  The present invention relates to an apparatus for supporting component division performed by a software developer in software development using a database, and a method and program therefor.

  In software development, software to be developed is often divided into components immediately after the required specifications are determined. Here, a component means a function that is finally implemented as a program, a service interface that enables the function hidden inside the component to be referenced from outside the component, and data handled by the component function (software using a database). In the case of development, data is a database table). Here, the component division is to structure the functions and data defined by the requirement specifications, convert them into component functions, service interfaces, and tables that are component elements, and configure these components together.

  When developing large-scale software, many functions that are finally implemented as programs by component division and the data used by those functions can be organized into components at the initial stage of development. And finally it will be possible to develop high quality software. In addition, developers can be organized in units divided into components, and development can be carried out in units of components, making development easier. However, depending on how the components are divided, due to the dependency between the components, software with low quality is finally created, and it becomes difficult to develop components.

  Patent Document 1 proposes a method for evaluating module division of a program developed after software development. In Patent Document 1, the source code of a given program is analyzed, the class is targeted as a module, the dependency relationships between modules (calls between methods, etc.) are analyzed, and evaluation values for various dependency relationships by a predetermined formula Is calculated. This provides a judgment material for objective evaluation as to whether or not the module division has conventionally been dependent on the subjectivity.

JP2000-215045

  Patent Document 1 discloses a technique for evaluating module division of a program in which source code exists. However, regarding support for component division of software to be developed in the future, Patent Document 1 excludes the technology.

  In order to make it easier to develop software on a component-by-component basis, and finally to create high-quality software, the existence of dependencies that may be an obstacle to these factors should be specified in advance as a policy. It is conceivable to perform component division so as not to contradict. However, as the number of required specifications increases, the number of component division patterns increases, and it is difficult to select a component division pattern that does not violate all policies.

  Further, it may be necessary to re-divide the components by adding / changing the required specifications after dividing the components. At this time, reducing the influence on the already divided components and their elements and re-dividing the components so as not to violate the policy, the more the number of existing components and the number of additions / changes of requirement specifications, the more It becomes difficult.

  An object of the present invention is to provide a component division support apparatus, a method and a program for detecting dependency relations between component elements that violate a policy at the time of component division and outputting candidates for improvement measures for the detected illegal dependency relations. There is to do.

  The component division support apparatus according to the present invention is as follows. Service interface that is an element of the component of the development target software, a table, and a component element definition storage unit that stores definition data related to the dependency relationship between them, a dependency relationship that stores policy data that defines an illegal dependency relationship with respect to the dependency relationship A component storage unit that uses a policy storage unit, an improvement plan storage unit that stores a plan for improving a dependency relationship that violates a policy, and policy data that defines an illegal dependency stored in the dependency policy storage unit. Dependencies that are against the policy are detected by using a plan to detect a dependency that is against the policy from the dependencies that are stored in, and to improve the dependency that is against the policy stored in the improvement measure storage unit. A dependency analysis unit that outputs candidates for improvement;

  Another aspect of the present invention is a component division in which a computer having an input device, a display device, a storage device, and a processor stores the contents of each storage unit in the storage device and executes the processing of the dependency relationship analysis unit by the processor. A support method and a program thereof.

  According to the present invention, in the component division of the software to be developed, the user can check the dependency relationship between component elements that violates the dependency policy. In addition, since the improvement measures against the illegal dependency relationship are output, the component division work becomes easy.

  Hereinafter, embodiments of the present invention will be described in detail. As shown in FIG. 1, the component division support apparatus 100 according to this embodiment includes a component element definition editing unit 102, a component element definition operation unit 104, an improvement measure application unit 106, a dependency relationship analysis unit 108, and a component element definition storage unit 150. An improvement measure storage unit 170, a dependency relationship policy storage unit 180, and a dependency relationship analysis result storage unit 190. The arrows in the figure indicate the flow of data between components.

  As shown in FIG. 2, the component division support apparatus 100 is realized by using a computer system having a CPU (processor) 201, a main storage device (memory) 202, an input device 203, a display device 204, and an external storage device 205. The

  The component element definition storage unit 150, the improvement measure storage unit 170, the dependency relationship policy 180, and the dependency relationship analysis result storage unit 190 are stored in the external storage device 205, and with the execution of the program by the CPU 201, Data is read and written between them. The component element definition editing unit 102, the component element definition operation unit 104, the improvement measure application unit 106, and the dependency analysis unit 108 are programs stored in the main storage device 202 and executed by the CPU 201.

  FIG. 3 shows configurations of the component element definition storage unit 150, the improvement measure storage unit 170, the dependency relationship policy 180, and the dependency relationship analysis result storage unit 190.

  The component element definition storage unit 150 shown in FIG. 3A includes a component definition 3000, a service interface definition 3050, a table definition 3100, an inter-component dependency definition 3150, an inter-service interface dependency definition 3200, and a service interface / table dependency definition. 3250 and inter-table dependency definition 3300.

  The component definition 3000 is a table for storing component definition data. As shown in FIG. 8 as an example of data defined by the component definition 3000, the component definition 3000 includes a component ID 802 for uniquely identifying data defined by the component definition 3000, and a component name 804 representing the name of the component. Have

  The service interface definition 3050 is a table for storing definition data of service interfaces belonging to the components defined in the component definition 3000. The service interface is an interface that allows a function that is inside the component and hidden from the outside of the component (which eventually becomes a program) to be referenced from outside the component. As shown in FIG. 9 as an example of data defined by the service interface definition 3050, the service interface definition 3050 includes a service interface ID 902 for uniquely identifying the data defined by the service interface definition 3050, and the name of the service interface. A service interface name 904 to be represented, a belonging component ID 906 for designating a component to which the service interface belongs, and a definition fixed flag 908 indicating whether or not the data of the service interface definition can be changed.

  The table definition 3100 is a table for storing definition data of tables belonging to components defined in the component definition 3000. As shown in FIG. 10 as an example of data defined by the table definition 3100, the table definition 3100 includes a table ID 1002 for uniquely identifying data defined by the table definition 3100, a table name 1004 representing the name of the table, It has a belonging component ID 1006 for designating the component to which the table belongs, and a definition fixed flag 1008 indicating whether or not the data of this table definition can be changed.

  The inter-component dependency definition 3150 is a table for storing definition data of dependency between any two components defined in the component definition 3000. The inter-component dependency definition 3150 is an inter-component dependency ID for uniquely identifying data defined by the inter-component dependency 3150, as shown in FIG. 11 as an example of data defined by the inter-component dependency definition 3150. 1102, Relation source component ID 1104 for specifying component source data of dependency relation between components (dependence source), and relation destination component ID for specifying component of relation destination of component dependency relation (dependence destination) 1106.

  The inter-service interface dependency definition 3200 is a table for storing definition data of dependency between any two service interfaces defined by the service interface definition 3050. The dependency relationship between service interfaces means that a function that publishes a service interface (which finally becomes a program) refers to a service interface of another function in order to call the other function. The service interface dependency definition 3200 is a service interface for uniquely identifying data defined by the service interface dependency 3200 as shown in FIG. 12 as an example of data defined by the service interface dependency definition 3200. Inter-relationship ID 1202, relation-source service interface ID 1204 for specifying the service interface that is the source of the inter-service interface dependency, and destination service interface ID for specifying the service interface that is the target of the inter-service interface dependency 1206, and a definition fixing flag 1208 indicating whether or not the service interface dependency relationship definition data can be changed.

  The service interface / table dependency relationship definition 3250 is a table for storing dependency relationship definition data between the service interface defined by the service interface definition 2050 and the table defined by the table definition 3100. The dependency between the service interface and the table means that a function having the service interface (which finally becomes a program) refers to the table. The service interface / table dependency definition 3250 uniquely identifies data defined by the service interface / table dependency definition 3250 as shown in FIG. 13 as an example of data defined by the service interface / table dependency definition 3250. Service interface / table dependency ID 1302 for association, Service interface definition ID 1304 for specifying the service interface that is the association source of the service interface / table dependency, Table that is the association destination of the service interface / table dependency It has an association destination table ID 1306 for designating and a definition fixed flag 1308 indicating whether or not data of this service interface / table dependency relationship definition can be changed.

  The inter-table dependency definition 3300 is a table for storing definition data of dependency between any two tables defined by the table definition 3100. The dependency relationship between tables means a relationship existing between a foreign key of one table and a primary key of another table. The inter-table dependency definition 3300 is an inter-table dependency relationship for uniquely identifying data defined by the inter-table dependency definition 3300 as shown in FIG. 14 as an example of data defined by the inter-table dependency relationship definition 3300. ID 1402, relation source table ID 1404 for specifying the relation source table of inter-table dependency relation, relation destination table ID 1406 for specifying the relation destination table of inter-table dependency relation, and inter-table dependency definition A fixed definition flag 1408 indicating whether or not the data can be changed.

  The improvement measure storage unit 170 shown in FIG. 3 (b) has a fraud dependency improvement measure definition 3350.

  The illegal dependency improvement measure definition 3350 is for the illegal dependency detected by the dependency analysis unit 108, that is, the illegal service interface dependency, the illegal service interface / table dependency, and the illegal inter-table dependency. This is a table for storing pointers to programs for improving each illegal dependency relationship. The illegal dependency improvement policy definition 3350 is an illegal code for uniquely identifying the data defined by the illegal dependency improvement policy definition 3350, as shown in FIG. Dependency Improvement Measure ID 1502, Illegal Dependency Improvement Measure Program ID 1504 that is a pointer to an illegitimate Dependency Improvement Program to improve illicit dependency It has an illegal dependency policy ID 1508 for designating data of the illegal dependency policy definition 3400 targeted by the contents 1506 and the illegal dependency improvement measure program ID 1504.

  The dependency policy storage unit 180 shown in FIG. 3C has an illegal dependency policy definition 3400.

  The illegal dependency policy definition 3400 is a table for storing a pointer to the illegal dependency policy program for finding an illegal dependency in the dependency analysis unit 108. The illegal dependency policy definition 3400 is an illegal dependency policy for uniquely identifying data defined by the illegal dependency policy definition 3400, as shown in FIG. 16 as an example of data defined by the illegal dependency policy definition 3400. ID 1602, an illegal dependency policy program ID 1604 that is a pointer to an illegal dependency policy program for finding an illegal dependency, and the program specified by the illegal dependency policy program ID 1604 is detected as an illegal dependency It has an illegal dependency policy point (evaluation point) 1606 indicating the degree of illegality of the detected illegal dependency relationship, and an illegal dependency policy content 1608 indicating the content of the illegal dependency policy.

  The dependency analysis result storage unit 190 illustrated in FIG. 3D includes an illegal dependency analysis result 3500 and an illegal dependency improvement plan 3550.

  The unauthorized dependency analysis result 3500 is a table for storing the unauthorized dependency analysis result detected by the dependency analysis unit 108. The unauthorized dependency analysis result 3500 is an unauthorized dependency analysis for uniquely identifying data defined by the unauthorized dependency analysis result 3500, as shown in FIG. 17 as an example of data defined by the unauthorized dependency analysis result 3500. Result ID 1702, invalid dependency data ID, that is, invalid service interface dependency ID 1202, illegal service interface / table dependency ID 1302, or invalid inter-table dependency ID 1402 It has a dependency ID 1704 and an illegal dependency policy ID 1706 that specifies data 1602 of the illegal dependency policy definition 3400 in which the illegal dependency is detected.

  The illegal dependency improvement plan 3550 is an example of the data defined by the illegal dependency improvement plan 3550 as shown in FIG. Proposal ID 1802, illegal dependency analysis result ID 1804 that specifies illegal dependency analysis result 3500 data, illegal dependency improvement plan ID 1806 that specifies illegal dependency improvement plan definition 3350 data, and illegal dependency It has a fraud dependency improvement result evaluation point 1808 calculated from a fraud dependency evaluation point for the result of provisional application of improvement measures.

  The component element definition editing unit 102 will be described according to the processing flow of FIG.

  In step 402, an edit menu screen 1900 shown in FIG. Next, through the input device 203, a component definition edit button 1902, a service interface definition edit button 1904, a table definition edit button 1906, an inter-component dependency definition edit button 1908, an inter-service interface dependency definition edit button 1910, If it is determined that one of the service interface / table dependency definition edit button 1912, the inter-table dependency definition edit button 1914, and the improvement measure apply button 1916 is pressed, Step 404 to Step corresponding to the pressed button Processing is transferred to one of 420 (except step 418). If it is determined through the input device 203 that the end button 1918 in FIG. 19 has been pressed, the process ends.

  In step 404, the component definition editing screen 2000 shown in FIG. At this time, the data of the component definition 3000 is read from the component element definition storage unit 150, and the read data is displayed in a list as indicated by 2020 in FIG. When the data of the component definition 3000 is selected through the input device 203 as indicated by the cursor 2022, the component ID 2002 and the component name 2004 that are the contents of the data are displayed.

  When it is determined that the component name 2004 has been changed through the input device 203 and the registration button 2006 has been pressed, the data of the component definition 3000 reflecting the changed content is stored in the component element definition storage unit 150. In addition, the display of the list 2020 is changed to reflect the change.

  If it is determined that the new button 2012 has been pressed through the input device 203, a new component ID is generated and displayed in 2002, the component name 2004 is input through the input device 203, and the registration button 2006 is pressed. If it is determined, data of the component definition 3000 having the newly created component ID 2002 and the input component name 2004 is created and stored in the component element definition storage unit 150. The created component definition 3000 data is additionally displayed in the list 2020.

  When it is determined through the input device 203 that the end button 2010 in FIG. 20 has been pressed, the process proceeds to step 402. As described above, the user edits the data of the component definition 3000.

  In step 406, the service interface definition editing screen 2100 shown in FIG. At this time, the data of the service interface definition 3050 is read from the component element definition storage unit 150, and the read data is displayed in a list as indicated by 2120 in FIG.

  When the data of the service interface definition 3050 is selected as indicated by the cursor 2122 through the input device 203, the service interface ID 2102, the service interface name 2104, the affiliation component ID 2106, and the definition fixed flag 2108 that are the contents of the data are displayed. indicate.

  It is determined that the delete button 2112 has been pressed through the input device 203, the definition fixed flag 2108 is “FALSE”, and the service interfaces in the component element storage unit 150 related to the displayed service interface definition 3050 Referring to the data of the dependency relationship definition 3200 and the data of the service interface / table dependency relationship definition 3250, when the definition fixed flags 1208 and 1308 of these data are “FALSE”, the data of the displayed service interface definition 3050, The service interface dependency relationship definition 3200 data and the service interface / table dependency relationship definition 3250 data are deleted from the component element storage unit 150. Delete the deleted data from the list display 2120.

  If it is determined that the service interface name 2104 or the belonging component ID 2106 has been changed through the input device 203, the definition fixed flag 2108 is “FALSE”, and the registration button 2110 has been pressed, the service reflecting the changed contents Data of the interface definition 3050 is stored in the component element definition storage unit 150. Further, the display of the list 2120 is changed to reflect the changed contents.

  When the definition fixing flag 2108 is changed from “TRUE” to “FALSE” or “FALSE” to “TRUE” through the input device 203, the data of the service interface definition 3050 reflecting the changed contents is stored in the component element definition storage unit 150. . In addition, the display of the list 2020 is changed to reflect the change.

  When it is determined that the new button 2116 has been pressed through the input device 203, a new service interface ID is generated and displayed on 2102. The service interface name 2104, the affiliation component ID 2106, and the definition fixed flag are displayed through the input device 203. 2108 is input, and it is determined that the registration button 2110 has been pressed, it has a newly created service interface ID 2102, an input service interface name 2104, a belonging component ID 2106, and a fixed definition flag 2108. Data of the service interface definition 3050 is created and stored in the component element definition storage unit 150. Further, the data of the created service interface definition 3050 is additionally displayed in the list 2120.

  If it is determined that the end button 2114 in FIG. 21 has been pressed through the input device 203, the process proceeds to step 402. As described above, the user edits the data of the service interface definition 3050.

  In step 408, the table definition editing screen 2200 shown in FIG. At this time, the data of the table definition 3100 is read from the component element definition storage unit 150, and the read data is displayed in a list as indicated by 2220 in FIG.

  When the data of the table definition 3100 is selected through the input device 203 as indicated by the cursor 2222, the table ID 2202, the table name 2204, the affiliation component ID 2206, and the definition fixed flag 2208, which are the contents of the data, are displayed.

  It is determined that the delete button 2212 is pressed through the input device 203, the definition fixed flag 2208 is “FALSE”, and the service interface in the component element storage unit 150 related to the displayed table definition 3050 When the data of the table dependency definition 3250 and the data of the inter-table dependency definition 3300 are referred, and the fixed definition flags 1308 and 1408 of these data are “FALSE”, the data of the displayed table definition 3100 and this The data of the service interface / table dependency definition 3250 and the data of the inter-table dependency definition 3300 related to the are deleted from the component element storage unit 150. Delete the deleted data from the list display 2220.

  If it is determined that the table name 2204 or the belonging component ID 2206 has been changed through the input device 203, the definition fixed flag 2208 is “FALSE”, and the registration button 2210 has been pressed, the table definition reflecting the changed contents 3100 data is stored in the component element definition storage unit 150. In addition, the display of the list 2220 is changed to reflect the changed contents.

  When the definition fixing flag 2208 is changed from “TRUE” to “FALSE” or “FALSE” to “TRUE” through the input device 203, the data of the table definition 3100 reflecting the changed contents is stored in the component element definition storage unit 150. In addition, the display of the list 2220 is changed to reflect the changed contents.

  If it is determined that the new button 2216 has been pressed through the input device 203, a new table ID is generated and displayed on 2202, and the table name 2204, affiliation component ID 2206, and definition fixed flag 2208 are displayed through the input device 203. Is entered and the registration button 2210 is determined to have been pressed, the table definition 3100 having the newly created table ID 2202, the entered table name 2204, the belonging component ID 2206, and the definition fixed flag 2208 Is created and stored in the component element definition storage unit 150. Further, the data of the created table definition 3100 is additionally displayed in the list 2220.

  If it is determined that the end button 2214 in FIG. 22 has been pressed through the input device 203, the process proceeds to step 402. As described above, the user edits the data of the table definition 3100.

  In step 410, the inter-component dependency relationship definition editing screen 2800 shown in FIG. At this time, the data of the component definition 3000 related to the data of the inter-component dependency relationship definition 3150 is read from the component element definition storage unit 150, and a list of the read data is displayed in a matrix as indicated by 2820 in FIG. The vertical axis of the matrix indicates the relation source (dependence source) of the dependency relation between components, and the horizontal axis of the matrix indicates the relation destination (dependence destination) of the dependency relation between components. When there is a dependency relationship between components (the component shown on the vertical axis depends on the component shown on the horizontal axis), a check mark 2822 is displayed in the cell of the corresponding matrix.

  When a cell in the matrix with the check mark 2822 is selected through the input device 203, the component name of the relation source corresponding to the selected cell is set to the relation source name 2802, and the component name of the relation destination corresponding to the selected cell is selected. The relation name 2804 is displayed with the relation flag 2806 as “TRUE” to indicate that there is a relation. When a matrix cell without a check mark is selected via the input device 203, the related source component name corresponding to the selected cell is related to the related source name 2802, and the related destination component name corresponding to the selected cell is related. In order to indicate that there is no relationship in the name 2804, the relationship flag 2806 is displayed as “FALSE”.

  When the displayed relationship flag 2806 is “FALSE” is changed to “TRUE” and the registration button 2808 is pressed through the input device 203, a new dependency relationship is created between the components. The relation ID 1102 is generated, the component ID 802 corresponding to the relation source name 2802 is set as the relation source component ID 1104, and the component ID 802 corresponding to the relation destination name 2804 is set as the relation destination component ID 1106. Data is created, and the created data is stored in the component element definition storage unit 150. A check mark is displayed in the cell of the matrix 2820 corresponding to the created data.

  If the displayed relationship flag 2806 is “TRUE” without being changed and the registration button 2808 is pressed through the input device 203, the contents of the dependency relationship between the components (the relationship source name 2802 and the relationship destination name 2804 On the other hand, the data of the inter-component dependency definition 3150 displayed in the area 2801 is changed to the relation source name 2802 and the relation destination name 2804 displayed when the registration button 2808 is pressed. And the data of the changed inter-component dependency relationship definition 3150 is stored in the component element definition storage unit 150. In response to this data change, the check mark of the corresponding cell in the matrix 2820 is changed and displayed.

  If it is determined that the end button 2810 in FIG. 28 has been pressed through the input device 203, the process proceeds to step 402. As described above, the user edits the data of the inter-component dependency relationship definition 3150.

  In step 412, the inter-service interface dependency definition editing screen 2300 shown in FIG. 23 is displayed on the display device 204. At this time, the data of the component definition 3000 and the data of the service interface definition 3050 related to the data of the inter-service interface dependency definition 3200 and the data of the service interface definition 3050 are read from the component element definition storage unit 150, and a list of the read data is indicated by 2320 in FIG. Display by matrix as shown. The vertical axis of the matrix indicates the association source (dependence source) of the dependency relationship between service interfaces, and the horizontal axis of the matrix indicates the association destination (dependence destination) of the dependency relationship between service interfaces. If there is a dependency relationship between service interfaces (the service interface shown on the vertical axis depends on the service interface shown on the horizontal axis), a check mark 2322 is displayed in the cell of the corresponding matrix.

  In addition, the data of the illegal dependency analysis result 3500 is read from the dependency analysis result storage unit 190, and the dependency between service interfaces corresponding to the read data, that is, the dependency between illegal service interfaces is set to 2326. Hatched display as shown.

  When the cell of the matrix having the check mark 2322 is selected through the input device 203, the data content of the service interface dependency definition 3200 corresponding to the selected cell is displayed. The content of this display data is the illegal dependency policy content 2302 indicating the illegal dependency policy content 1608 of the illegal dependency policy definition 3400 data read from the dependency policy storage unit 180 (this is the service interface specified by the cursor 2324). (Existing when the inter-dependency is an invalid dependency (displayed by hatching)), the relation source name 2304 indicating the service interface name 904 of the relation source of the inter-service interface dependency 3200, and the relation of the inter-service interface dependency 3200 “TRUE” is the relationship destination name 2306 indicating the previous service interface name 904, the definition fixed flag 2308 corresponding to the definition fixed flag 1208, and the relationship flag 2310 indicating that there is a dependency between the service interfaces.

  When the cell 2328 of the matrix without the check mark is selected through the input device 203, the service interface name of the relation source of the data of the inter-service interface dependency definition 3200 corresponding to the selected cell 2328 is selected as the relation source name 2304. The service interface name of the association destination of the data of the dependency definition 3200 between service interfaces corresponding to the specified cell is displayed in the association destination name 2306, respectively. Further, the definition fixing flag 2308 is displayed as “FALSE”, and the relationship flag 2310 is displayed as “FALSE” to indicate that there is no dependency between service interfaces.

  When the displayed relationship flag 2310 is “FALSE” is changed to “TRUE” and the registration button 2312 is pressed through the input device 203, a new dependency is created between the service interfaces. Service interface that generates the inter-dependency ID 1202 and uses the service interface ID 902 corresponding to the relation source name 2304 as the relation source service interface ID 1204 and the service interface ID 902 corresponding to the relation destination name 2306 as the relation destination service interface ID 1206 Data of the interdependency relationship definition 3200 is created, and the created data is stored in the component element definition storage unit 150. A check mark is displayed in a cell of the matrix 2320 corresponding to the created data.

  If the registration button 2312 is pressed through the input device 203 without changing the displayed “TRUE” of the relationship flag 2310, the contents of the dependency relationship between the service interfaces (related source name 2304, related destination name 2306, and definition) Since at least one of the fixed flags 2308) has been changed, the relation source name 2304, the relation destination name 2306, which are displayed when the registration button 2312 is clicked, are displayed for the data of the corresponding service interface dependency definition 3200. Then, the data is changed to the definition fixed flag 2308, and the data of the changed inter-service interface dependency definition 3200 is stored in the component element definition storage unit 150. In response to this data change, the check mark of the corresponding cell in the matrix 2320 is changed and displayed.

  If “TRUE” of the displayed relationship flag 2310 is changed to “FALSE” and the definition fixed flag 2308 is “FALSE”, it is considered that the dependency relationship between the service interfaces is deleted, and the displayed service interface The data of the inter-service interface dependency definition 3200 corresponding to the inter-dependency is deleted from the component element definition storage unit 150. In response to this deletion, the check mark of the corresponding cell in the matrix 2320 is deleted.

  When the registration button 2312 is pressed through the input device 203 and the dependency check flag 2360 has a check mark, the processing of the dependency analysis unit 108 is called, and the matrix of 2320 reflecting the result of the dependency analysis is obtained by the method described above. It is recreated and displayed on the display device 204.

  If it is determined that the illegal dependency policy content 2302 is displayed and the improvement measure presentation button 2314 is pressed through the input device 203, the process proceeds to step 418.

  If it is determined that the end button 2316 in FIG. 23 has been pressed through the input device 203, the process proceeds to step 402. As described above, the user edits the data of the service interface dependency definition 3200.

  In step 414, the service interface / table dependency relationship definition editing screen 2400 shown in FIG. The component definition 3000 data, the service interface definition 3050 data, and the table definition 3100 related to the service interface / table dependency definition 3250 data are read from the component element definition storage unit 150, and a list of the read data is shown in FIG. Displayed in a matrix as shown in 2420. The vertical axis of the matrix indicates the service interface that is the association source of the service interface / table dependency, and the horizontal axis of the matrix indicates the table that is the association destination of the service interface / table dependency.

  If there is a dependency between service interface tables, a check mark 2422 is displayed in the corresponding matrix cell. In addition, the data of the illegal dependency analysis result 3500 is read from the dependency analysis result storage unit 190, and the dependency relationship between the service interface and the table corresponding to the read data, that is, the dependency relationship between the illegal service interface and the table is the corresponding cell. Show hatching 2426.

  When data of the service interface / table dependency definition 3250 corresponding to the cell hatched 2426 of the matrix is selected through the input device 203, the data of the selected service interface / table dependency definition 3250 Display the contents. The content of this display data is the illegal dependency policy content 2402 indicating the illegal dependency policy content 1608 of the illegal dependency policy definition 3400 data read from the dependency policy storage unit 180 (this is the service interface specified by the cursor 2424) Exists only when the inter-dependency is an illegal dependency), the relation source name 2404 indicating the service interface name 904 that is the relation origin of the dependency relation between the service interface and the table, and the relation destination of the dependency relation between the service interface and the table “TRUE” is the relation destination name 2406 indicating the table name 1004, the definition fixed flag 2408 corresponding to the definition fixed flag 1308, and the relationship flag 2410 indicating that there is a dependency between the service interface and the table.

  If a matrix cell 2428 without a check mark is selected through the input device 203, the service interface name that is the association source of the data in the service interface / table dependency definition 3250 corresponding to the selected cell 2428 is selected as the association source name. In 2402, the table name that is the association destination of the data of the service interface / table dependency definition 3250 is the association destination name 2406, the definition fixed flag 2408 is “FALSE”, and there is no dependency relationship between the service interface and the table. In order to indicate this, “FALSE” is displayed in the relationship flag 2410.

  When the displayed relationship flag 2410 “FALSE” is changed to “TRUE” and the registration button 2412 is pressed through the input device 203, a new dependency is created between the service interface and the table. A service interface that generates a table dependency ID 1302 and sets the service interface ID 902 corresponding to the related source name 2404 as the related source service interface ID 1304 and the table ID 1002 corresponding to the related destination name 2406 as the related destination table ID 1306 Create data of the table dependency definition 3250 and store the created data in the component element definition storage unit 150. A check mark is displayed in a cell of the matrix 2420 corresponding to the created data.

  When the registration button 2412 is pressed through the input device 203 without changing the displayed relationship flag 2410 “TRUE”, the contents of the dependency relationship between the service interface and the table (related source name 2404 or related destination name 2406) Or the definition fixed flag 2408) is changed, the data of the corresponding service interface / table dependency definition 3250 is displayed as the related source name 2404, the related destination name 2406 displayed when the registration button 2412 is pressed, and The definition is changed to the fixed definition flag 2408, and the data of the changed service interface / table dependency definition 3250 is stored in the component element definition storage unit 150. In response to this data change, the check mark of the corresponding cell in the matrix 2420 is changed and displayed.

  When “TRUE” of the displayed relationship flag 2410 is changed to “FALSE” and the fixed definition flag 2408 is “FALSE”, it is displayed because the dependency relationship between the service interface and the table is deleted. The data of the service interface / table dependency relationship definition 3250 corresponding to the dependency relationship between the service interface and the table is deleted from the component element definition storage unit 150. In response to this deletion, the check mark of the corresponding cell in the matrix 2420 is deleted.

  When the registration button 2412 is pressed through the input device 203 and the dependency check flag 2460 has a check mark, the processing of the dependency analysis unit 108 is invoked, and the matrix of 2420 reflecting the result of the dependency analysis is obtained by the method described above. It is recreated and displayed on the display device 204.

  If it is determined that the illegal dependency policy content 2402 is displayed and the improvement measure presentation button 2414 is pressed through the input device 203, the process proceeds to step 418.

  If it is determined that the end button 2416 in FIG. 24 has been pressed through the input device 203, the process proceeds to step 402. As described above, the user edits the data of the service interface / table dependency relationship definition 3250.

  In step 416, the inter-table dependency relationship definition editing screen 2500 shown in FIG. 25 is displayed on the display device 204. The data of the component definition 3000 and the data of the table definition 3100 related to the data of the inter-table dependency definition 3300 are read from the component element definition storage unit 150, and a list of the read data is expressed by a matrix as indicated by 2520 in FIG. indicate. The vertical axis of the matrix indicates the source of the inter-table dependency, and the horizontal axis of the matrix indicates the target of the inter-table dependency.

  If there is a dependency relationship between the tables, a check mark 2522 is displayed in the corresponding matrix cell. The data of the illegal dependency analysis result 3500 is read from the dependency analysis result storage unit 190, and the dependency relationship between the tables corresponding to the read data, that is, the dependency relationship between the incorrect tables is hatched and displayed 2526.

  When the cell of the matrix having the check mark 2522 is selected through the input device 203, the content of the inter-table dependency definition 3300 corresponding to the selected cell is displayed. The content of this display data is the illegal dependency policy content 2302 indicating the illegal dependency policy content 1608 of the illegal dependency policy definition 3400 data read from the dependency policy storage unit 180 (this is between the tables specified by the cursor 2524) Exists only when the dependency is an illegal dependency), the relation source name 2504 indicating the table name 1004 of the relation source of the inter-table dependency relation, the relation destination name 2506 indicating the table name 1004 of the relation destination of the inter-table dependency relation, and the definition The definition fixed flag 2508 corresponding to the fixed flag 1408 and “TRUE” as the relationship flag 2510 indicating that there is a dependency relationship between the tables.

  When a matrix cell 2528 without a check mark is selected through the input device 203, the table name of the relation source of the data of the inter-table dependency definition 3300 corresponding to the selected cell 2528 is selected as the relation source name 2504. The relation destination table name of the data in the inter-table dependency definition 3300 corresponding to the cell is set to the relation destination name 2506, the definition fixed flag 2508 is set to “FALSE”, and a relation flag is used to indicate that there is no dependency relation between tables. “FALSE” is displayed in 2510.

  When “FALSE” of the displayed relationship flag 2510 is changed to “TRUE” and the registration button 2512 is pressed through the input device 203, a new dependency relationship is created between the tables, so the inter-table dependency ID 1402 And create the data of the inter-table dependency definition 3300 with the table ID 1002 corresponding to the relation source name 2504 as the relation source table ID 1404 and the table ID 1002 corresponding to the relation destination name 2506 as the relation destination table ID 1406. The created data is stored in the component element definition storage unit 150. A check mark is displayed in a cell of the matrix 2520 corresponding to the created data.

  When the registration button 2512 is pressed through the input device 203 without changing the displayed “TRUE” of the relationship flag 2510, the contents of the dependency relationship between the tables (related source name 2504, related destination name 2506, and definition fixed) One of the flags 2508) is considered to be changed, and the data of the corresponding inter-table dependency definition 3300 is defined as the relation source name 2504 and the relation destination name 2506 displayed when the registration button 2512 is pressed. The data is changed to the fixed flag 2508, and the data of the changed inter-table dependency relationship definition 3300 is stored in the component element definition storage unit 150. In accordance with this data change, the check mark of the corresponding cell in the matrix 2520 is changed and displayed.

  If “TRUE” of the displayed relationship flag 2510 is changed to “FALSE” and the fixed definition flag 2508 is “FALSE”, it is considered that the dependency relationship between tables is deleted, and the table displayed in 2501 Data of the inter-table dependency relationship definition 3300 corresponding to the dependency relationship is deleted from the component element definition storage unit 150. In response to this deletion, the check mark of the corresponding cell in the matrix 2520 is deleted.

  When the registration button 2512 is pressed through the input device 203 and the dependency check flag 2560 has a check mark, the processing of the dependency analysis unit 108 is called and the matrix of 2520 reflecting the result of the dependency analysis is obtained by the method described above. It is recreated and displayed on the display device 204.

  If it is determined that the illegal dependency policy content 2502 is displayed and the improvement measure presentation button 2514 is pressed through the input device 203, the process proceeds to step 418.

  If it is determined through the input device 203 that the end button 2516 in FIG. 25 has been pressed, the process proceeds to step 402. As described above, the user edits the data of the inter-table dependency relationship definition 3300.

  23 to 25, when the registration button is pressed through the input device 203 and the dependency check flag is checked, the processing of the dependency analysis unit 108 is called. The processing of the dependency analysis unit 108 may be called at the stage of displaying or when the cell with the check mark is selected.

  The process moves from any of steps 412 to 416 in FIG. 4 (the process moves when any of the improvement plan presentation buttons in FIGS. 23 to 25 is pressed). In step 418, the illegal dependency improvement shown in FIG. 26 is improved. Measure application screen (1) 2600 is displayed on the display device 204. The illegal dependency policy content 2602 shows the content of the illegal dependency policy displayed on the screen where step 418 was called, and the illegal dependency relation source name 2604 shows the related source name displayed on the screen where step 418 was called. In the illegal dependency relation destination name 2606, the relation destination name displayed on the screen that called step 418 is displayed.

  The component of the inter-service interface dependency definition 3150, service interface / table dependency definition 3250, and inter-table dependency 3300 data corresponding to the invalid dependency relation source name 2604 and the invalid dependency relation destination name 2606 Read from the element definition storage unit 150. Invalid dependency analysis that has the same value as the dependency ID 1704 between the service interface dependency ID 1202, the service interface dependency ID 1302, and the table dependency ID 1402 of the read dependency definition data. Data of the result 3500 is read from the dependency analysis result storage unit 190. Data having the same value as the illegal dependency analysis result ID 1702 of the read illegal dependency analysis result 3500 in the illegal dependency relationship improvement measure definition 3350 is read from the dependency policy storage unit 180. The illegal dependency improvement measure contents 1506 of the read illegal dependency improvement measure definition 3350 are displayed as a table 2608 in ascending order of the illegal dependency improvement measure result evaluation point 1808.

  When it is determined that the improvement measure is selected by the cursor 2650 through the input device 203 and the improvement measure application button 2610 is pressed through the input device 203, the improvement measure application unit 106 applies the improvement measure selected in 2650. Call the process. When calling up the process of the improvement measure application unit 106, the incorrect dependency relationship improvement measure ID 1502 corresponding to the improvement measure selected in 2650 and the incorrect dependency relationship ID 1704 corresponding to 2604 and 2606 are passed. When the process of the improvement measure application unit 106 is completed, the component element definition (component definition 3000, service interface definition 3050 and table definition 3100, inter-component dependency definition 3150, inter-service interface dependency definition 3200 to which the improvement measure has been applied. , Service interface / table dependency definition 3250 and inter-table dependency definition 3300) are stored in the component element definition storage unit 150. If it is determined that the end button 2612 in FIG. 26 has been pressed through the input device 203, the process returns to the step that called step 418.

  In step 420, an unauthorized dependency relationship improvement measure application screen (2) 2700 shown in FIG. 27 is displayed on the display device 204. All the data of the illegal dependency improvement plan 3550 is read from the dependency analysis result storage unit 190. The table 2706 is created and displayed in ascending order of the illegal dependency improvement measure result evaluation point 1808 of the read illegal dependency improvement plan 3550 data.

  In creating the table 2706, the illegal dependence improvement result evaluation point 1808 of the read data of the illegal dependence improvement plan 3550 is displayed as an evaluation point 2720.

  In creating the table 2706, the data of the illegal dependency analysis result 3500 is read from the illegal dependency analysis result ID 1804 of the data of the read illegal dependency improvement plan 3550. The data of various dependencies (service interface dependency definition 3200, service interface / table dependency definition 3250, or table dependency 3300) is read from the illegal dependency ID 1704 of the read invalid dependency analysis result 3500 data. Data of the service interface definition 3050 or the table definition 3100 related to the read various dependency data is read. The service interface name 904 of the data of the read service interface definition 3050 or the table name 1004 of the data of the read table definition 3100 is displayed as the related source name 2718 or the related destination name 2720 of the illegal dependency 2712 in Table 2706.

  In creating the table 2706, the data of the illegal dependency improvement policy definition 3350 is read from the illegal dependency improvement policy ID 1806 of the read illegal dependency improvement plan 3550 data. Read the illegal dependency policy definition 3400 data corresponding to the illegal dependency policy ID 1508 of the read illegal dependency improvement measure definition 3350 data. The read illegal dependency policy content 1608 of the read illegal dependency policy definition 3400 data is displayed as the illegal dependency policy content 2714.

  In creating the table 2706, the data of the illegal dependency improvement policy definition 3350 is read from the illegal dependency improvement policy ID 1806 of the read illegal dependency improvement plan 3550 data. The illegal dependency improvement contents 1506 of the read illegal dependency improvement measure definition 3350 data are displayed as an improvement measure 2716.

  When it is determined that the improvement measure is selected by the cursor 2750 through the input device 203 and the improvement measure application button 2708 is pressed through the input device 203, the improvement measure application unit applies the improvement measure selected by the cursor 2750. Call process 106. When calling the process of the improvement measure application unit 106, the illegal dependency improvement measure ID 1502 corresponding to the improvement measure selected in 2750, and the illegal dependency ID 1704 corresponding to the related source name 2718 and the related destination name 2720 give. When the process of the improvement measure application unit 106 is completed, the component element definition (component definition 3000, service interface definition 3050, table definition 3100, inter-component dependency definition 3150, inter-service interface dependency definition 3200 to which the improvement measure is applied. , Service interface / table dependency definition 3250 and inter-table dependency definition 3300) are stored in the component element definition storage unit 150.

  If it is determined that the end button 2710 in FIG. 27 has been pressed through the input device 203, the process proceeds to step 402.

  The component element definition operation unit 104 will be described with reference to the table of FIG. In the table of FIG. 5, the vertical axis indicates each data existing in the main storage device 202 when the component element definition operation unit 104 is called (data read from the component element definition storage unit 150 in a part other than the component element definition operation unit 104). ) And the horizontal axis indicates the operation for each data.

  The meaning of ○ in the table shown in FIG. 5 means that the operation shown at the top of the corresponding column of ○ exists in the component element definition operation unit 104 for the data shown at the left of the corresponding row of ○. The meaning of x in the table shown in FIG. 5 means that the operation shown at the top of the corresponding column of x does not exist in the component element definition operation unit 104 for the data shown at the leftmost of the corresponding row of x. Any of the operations on the data indicated by ○ is called from the improvement measure applying unit 106 and executed. Hereinafter, each operation for the data indicated by ○ will be described.

  In the operation of addition 502 to the service interface definition 3050, the service interface definition 3050 is based on the service interface ID generated by the operation, the service interface name passed from the part that called the operation, the belonging component ID, and the definition fixed flag. And the created data is stored in the main storage device 202.

  In the deletion 504 operation for the service interface definition 3050, the data of the service interface definition 3050 corresponding to the service interface ID passed from the part that called the operation is deleted from the main storage device 202. However, if the data definition fixed flag of the service interface definition 3050 is “TRUE”, the error is returned to the caller of the operation without executing the operation, and the process is terminated.

  In the operation of move 506 for the service interface definition 3050, the data of the service interface definition 3050 corresponding to the service interface ID passed from the part that called the operation is read from the main storage device 202, and the read data is deleted from the main storage device 202 Then, the affiliation component ID of the read data is changed to the affiliation component ID passed from the part that called the operation, and the changed data is stored in the main storage device 202. However, if the data definition fixed flag of the service interface definition 3050 is “TRUE”, the error is returned to the caller of the operation without executing the operation, and the process is terminated. By the operation of the integration 508 with respect to the service interface definition 3050, the two existing service interfaces are integrated, one new service interface is created, and the two existing service interfaces to be integrated are deleted. The service interface created by the integration inherits the dependency relationship between the two service interfaces that are integration targets and the related service interfaces and tables. Next, the operation of the integration 508 for the service interface definition 3050 for realizing this will be described.

  Since the service interface IDs of the two service interfaces to be integrated are passed from the part that called the operation 508, data of the service interface definition 3050 corresponding to the passed one service interface ID (hereinafter referred to as “service interface A”). And the data of the service interface definition 3050 corresponding to the other passed service interface ID (hereinafter referred to as “service interface B”) is read from the main storage device 202. Mainly the service interface dependency definition data and the service interface / table dependency definition data having the same value as the service interface ID value of the service interface A and service interface B in the relation source service interface ID or the relation destination service interface ID. Read from the storage device 202.

  Next, the service interface definition 3050 data is created based on the service interface ID generated in the operation 508, the service interface name passed from the part that called the operation 508, the belonging component ID, and the definition fixed flag. The created data is stored in the main memory 202. Change the service interface ID of the relation source service interface ID or the relation destination service interface ID of the service interface dependency definition data and the service interface / table dependency definition data that was read from the main storage device 202 to the previously generated service interface ID. Then, the changed service interface dependency relationship definition data and the service interface / table dependency relationship definition data are stored in the main storage device 202.

  However, in this operation, when the definition fixed flags of the service interface A and the service interface B are “TRUE”, or the same value as the value of the service interface ID of the service interface A and the service interface B read from the main storage device 202 is set. If the fixed definition flag of the service interface dependency definition data and the service interface / table dependency definition data in the interface ID or related destination service interface ID is “TRUE”, the operation is not executed and the error is indicated. Return to the caller of, and end the process.

  In the operation of the definition fixed flag change 510 for the service interface definition 3050, the data of the service interface definition 3050 corresponding to the service interface ID passed from the part that called the operation is read from the main storage device 202, and the read data is read from the main storage device. The definition fix flag of the read data is changed to the definition fix flag passed from the part that called the operation 510, and the changed data is stored in the main storage device 202.

  In the operation of rename 512 for the service interface definition 3050, the data of the service interface definition 3050 corresponding to the service interface ID passed from the part that called the operation 512 is read from the main storage device 202, and the read data is read from the main storage device 202. The service interface name of the read data is changed to the service interface name passed from the part that called the operation 512, and the changed data is stored in the main storage device 202. However, if the data definition fixed flag of the service interface definition 3050 is “TRUE”, the operation is not executed, the error is returned to the caller of the operation 512, and the process is terminated.

In the operation of addition 502 to the table definition 3100, based on the table ID generated by the operation, the table name passed from the part that called the operation, the belonging component ID, and the definition fixing flag, the data of the table definition 3050 is created, The created data is stored in the main memory 202.
In the delete 504 operation for the table definition 3100, the data of the table definition 3050 corresponding to the table ID passed from the part that called the operation 504 is deleted from the main storage device 202. However, when the data definition fixing flag of the table definition 3100 is “TRUE”, the operation is not executed and the error is returned to the caller of the operation 504, and the process is terminated.

  In the operation of move 506 for the table definition 3100, the data of the table definition 3100 corresponding to the table ID passed from the part that called the operation 506 is read from the main storage device 202, the read data is deleted from the main storage device 202, The affiliation component ID of the read data is changed to the affiliation component ID passed from the part that called the operation 506, and the changed data is stored in the main storage device 202. However, when the data definition fixing flag of the table definition 3100 is “TRUE”, the error is returned to the caller of the operation without executing the operation, and the process is terminated.

  By the operation of the integration 508 for the table definition 3100, the existing two tables are integrated, a new table is created, and the existing two tables that are the integration targets are deleted. The table created by integrating takes over the dependency relationship between the two tables to be integrated and the related service interfaces and tables. Next, the operation of the integration 508 for the table definition 3100 for realizing this will be described.

  Since the table IDs of the two tables to be integrated are passed from the part that called the operation 508, the data of the table definition 3100 corresponding to the passed one table ID (hereinafter referred to as “table A”) and The data of the table definition 3100 corresponding to the other passed table ID (hereinafter referred to as “table B”) is read from the main storage device 202. The inter-table dependency definition data and the service interface / table dependency definition data having the same value as the table ID value of the table A and the table B in the relation source table ID or the relation destination table ID are read from the main storage device 202. Next, based on the table ID generated in the operation 508, the table name passed from the part that called the operation 508, the belonging component ID, and the definition fixed flag, data of the table definition 3100 is created, and the created data Is stored in the main memory 202. Changed the relation table ID or relation destination table ID value of the inter-table dependency definition data and service interface / table dependency definition data read from the main storage device 202 to the previously generated table ID. The inter-table dependency definition data and the service interface / table dependency definition data are stored in the main storage device 202.

  However, in the operation 508, when the definition fixed flag of the table A and the table B is “TRUE”, or the same value as the table ID value of the table A and the table B read from the main storage device 202 is set, When the definition fixed flag of the inter-table dependency definition data and the service interface / table dependency definition data held in the table ID is “TRUE”, the error is returned to the caller of the operation without executing the operation 508, End the process.

  In the operation of the definition fixed flag change 510 for the table definition 3100, the data of the table definition 3100 corresponding to the table ID passed from the part that called the operation 510 is read from the main storage device 202, and the read data is read from the main storage device 202. The definition fixing flag of the data that has been deleted and read is changed to a definition fixing flag passed from the part that called the operation 510, and the changed data is stored in the main storage device 202.

  In the rename 512 operation for the table definition 3100, the table definition 3100 corresponding to the table ID passed from the part that called the operation 512 is read from the main storage device 202, and the read data is deleted from the main storage device 202 and read. The table name of the data is changed to the table name passed from the part where the operation 512 is called, and the changed data is stored in the main memory 202. However, when the data definition fixing flag of the table definition 3100 is “TRUE”, the error is returned to the caller of the operation without executing the operation, and the process is terminated.

  In the operation of addition 502 to the inter-component dependency definition 3150, based on the inter-component dependency ID generated in the operation 502 and the relation source component ID and the relation destination component ID passed from the part that called the operation 502, the component The data of the interdependency definition 3150 is created, and the created data is stored in the main storage device 202.

  In the delete 504 operation for the inter-component dependency relationship definition 3150, the data of the inter-component dependency relationship definition 3150 corresponding to the inter-component dependency relationship ID passed from the part that called the operation 504 is deleted from the main storage device 202.

  In the operation of addition 502 to the inter-service interface dependency definition 3200, the inter-service interface dependency ID generated in the operation 502, the related service interface ID passed from the part that called the operation 502, the related service interface ID, and Based on the definition fixed flag, data of the dependency definition 3200 between service interfaces is created, and the created data is stored in the main storage device 202.

  In the delete 504 operation for the inter-service interface dependency definition 3200, the data of the inter-service interface dependency definition 3200 corresponding to the inter-service interface dependency ID passed from the part that called the operation 504 is deleted from the main storage device 202. . However, if the data fixed definition flag of the inter-service interface dependency definition 3200 is “TRUE”, the operation 504 is not executed, an error is returned to the caller of the operation, and the process is terminated.

  In the operation of the definition fixed flag change 510 for the inter-service interface dependency definition 3200, the data of the inter-service interface dependency definition 3200 corresponding to the inter-service interface dependency ID passed from the part that called the operation 510 is stored in the main memory 202. The read data is deleted from the main storage device 202, the fixed definition flag of the read data is changed to the fixed definition flag passed from the part that called the operation 510, and the changed data is changed to the main storage device 202. To store.

  In the operation of adding 502 to the service interface / table dependency definition 3250, the service interface / table dependency ID generated in the operation 502, the related service interface ID passed from the part that called the operation 502, the related table ID, Then, based on the definition fixed flag ID, data of the service interface / table dependency definition 3250 is created, and the created data is stored in the main storage device 202.

  In the deletion 504 operation on the service interface / table dependency definition 3250, the data of the service interface / table dependency definition 3250 corresponding to the service interface / table dependency ID passed from the part that called the operation 504 is stored in the main storage device 202. Delete from. However, if the data definition fixed flag of the service interface / table dependency relationship definition 3250 is “TRUE”, the operation 504 is not executed, an error is returned to the caller of the operation 504, and the processing is terminated.

  In the operation of the definition fixed flag change 510 for the service interface / table dependency definition 3250, the data of the service interface / table dependency definition 3250 corresponding to the service interface / table dependency ID passed from the part that called the operation 510 is mainly used. The data read from the storage device 202, the read data is deleted from the main storage device 202, the definition fixed flag of the read data is changed to the definition fixed flag passed from the part that called the operation 510, and the changed data is changed to the main data. It is stored in the storage device 202.

  In the operation of addition 502 for the inter-table dependency definition 3300, the inter-table dependency ID generated in the operation 502, the related source table ID passed from the part that called the operation 502, the related destination table ID, and the definition fixed flag ID Based on the above, the data of the inter-table dependency definition 3300 is created, and the created data is stored in the main memory 202.

  In the delete 504 operation for the inter-table dependency definition 3300, the data of the inter-table dependency definition 3300 corresponding to the inter-table dependency ID passed from the part that called the operation 504 is deleted from the main storage device 202. However, if the data definition fixed flag of the inter-table dependency definition 3300 is “TRUE”, the operation 504 is not executed, an error is returned to the caller of the operation 504, and the process is terminated.

  In the operation of the definition fixed flag change 510 for the inter-table dependency definition 3300, the data of the inter-table dependency definition 3300 corresponding to the inter-table dependency ID passed from the part that called the operation 510 is read from the main storage device 202, The read data is deleted from the main storage device 202, the definition fixed flag of the read data is changed to the definition fixed flag passed from the part that called the operation 510, and the changed data is stored in the main storage device 202. .

  The improvement measure applying unit 106 will be described according to the processing flow of FIG.

  From the part that called the improvement measure application unit 106 (step 418 or step 420 in FIG. 4 which is called by selecting the improvement measure application button 2610 in FIG. 26 or the improvement measure application button 2708 in FIG. 27, or the dependency relationship analysis unit 108 described later). Data of the illegal dependency improvement policy definition 3350 corresponding to the illegal dependency improvement policy ID passed is read from the improvement memory 170 (step 602).

  The illegal dependency improvement policy program ID 1504 corresponding to the read illegal dependency improvement policy definition 3350 of the read data is read from the main storage device 202 and executed (step 604). In the read illegal dependency improvement program, the process of the component element definition storage unit 150 is called as necessary, and after the process is completed, the process is returned to the caller of the operation. However, if an error occurs during the processing of the component element definition storage unit 150, the error is returned to the caller of the operation, and the process ends.

  The dependency relationship analysis unit 108 will be described according to the processing flow of FIG.

  The data of the illegal dependency policy definition 3400 stored in the dependency policy storage unit 180 is read (step 702).

  Component element definitions (component definition 3000, service interface definition 3050, table definition 3100, inter-component dependency definition 3150, inter-service interface dependency definition 3200, service interface / table dependency definition 3250, and inter-table dependency definition 3300) Data is read from the component element definition storage unit 150. Then, by reading the program corresponding to the illegal dependency policy program ID 1604 of the illegal dependency policy definition 3400 data from the main storage device 202 and executing it, the illegal dependency existing in the read component element definition data can be obtained. Discover (step 704).

  When an illegal dependency relationship is found by the illegal dependency policy program, a new illegal dependency analysis result ID 1702 is generated, and new illegal dependency analysis result 3500 data is created. The new data illegal dependency policy ID 1706 is the data illegal dependency policy ID 1602 of the illegal dependency policy definition 3400 having the pointer of the found illegal dependency policy program as the illegal dependency policy program ID 1604. The new data illegal dependency ID 1704 is the ID of the discovered illegal dependency (if the illegal dependency is a service interface dependency, it is the service interface dependency ID 1202, and the service interface / table dependency If there is a service interface / table dependency ID 1302, and if it is an inter-table dependency relationship, it is an inter-table dependency ID 1402). The data of the created illegal dependency analysis result 3500 is stored in the dependency analysis result storage unit 190. Further, an illegal dependency evaluation point is calculated from the illegal dependency policy point 1606 of the read illegal dependency policy definition 3400 data. The specification of the illegal dependency and the evaluation score of the illegal dependency will be described later using an example.

  If there is an illegal dependency relationship, the process proceeds to step 708; otherwise, the process ends (step 706).

  Read the data of the illegal dependency analysis result 3500 from the dependency analysis result storage unit 190, step out the data of the read invalid dependency analysis result 3500 one by one, and step by the number of data of the read invalid dependency analysis result 3500 The processing from Step 710 to Step 720 is repeatedly executed (Step 708, Step 722).

  Read the data of the illegal dependency policy definition 3400 that has the same value as the illegal dependency policy ID 1706 of the extracted illegal dependency analysis result 3500 data as the illegal dependency policy ID 1602, and then read the data of the read illegal dependency policy definition 3400 The data of the illegal dependency improvement measure definition 3350 having the same value as the illegal dependency policy ID 1602 of data as the illegal dependency policy ID 1508 is read. While fetching the data of the read illegal dependency improvement plan definition 3350 one by one, the processing of step 712 to step 718 is repeatedly executed for the number of data of the read illegal dependency improvement plan definition 3350 (steps 710 and 720). .

  In order to temporarily apply the data of the extracted illegal dependency improvement measure definition 3350, the process of the improvement measure application unit 106 is called. At this time, for the process of the improvement measure application unit 106, the illegal dependency improvement measure program ID 1504 of the improvement measure taken out in step 710 and the illegal dependency ID of the data of the illegal dependency analysis result 3500 taken out in step 708 1704 is passed (step 712).

  By reading the program corresponding to the illegal dependency policy program ID 1604 of the read illegal dependency policy definition 3400 data from the main storage device 202 and executing it, the service interfaces between the service interfaces or service interfaces to which the improvement measures are temporarily applied in step 712 The invalid dependency relationship existing between the tables and between the tables is identified, and the illegal dependency evaluation point is calculated from the illegal dependency policy point 1606 of the data of the illegal dependency policy definition 3400 read in step 702 (step 702). 714).

  A new illegal dependency improvement plan ID 1802 is generated, and data of a new illegal dependency improvement plan 3550 is created (step 718). The new data illegal dependency analysis result ID 1804 is the data of the illegal dependency analysis result ID 1704 of the illegal dependency analysis result 3500 extracted in step 708. The new data illegal dependency improvement policy ID 1806 is the data illegal dependency improvement policy ID 1502 of the illegal dependency improvement policy definition 3350 extracted in step 710. A new data fraud dependency improvement result evaluation point 1808 is obtained by subtracting the fraud dependency evaluation score calculated in step 704 from the fraud dependency evaluation score calculated in step 714. The data of the created illegal dependency improvement plan 3550 is stored in the dependency analysis result storage unit.

  In the following, the illegal dependency policy program for specifying an illegal dependency in step 704 and step 714 will be described. In the illegal dependency policy program, if the fixed definition flag (1208, 1308, or 1408) of each dependency data is “TRUE”, it is considered that the user has intentionally created a dependency, We will not violate policy unconditionally.

  An illegal dependency policy program corresponding to “Service call within the same component” 1620 of the illegal dependency policy definition 3400 will be described. “Service call within the same component” means that when a service interface of a component is disclosed (called from another), another service interface of the same component is executed during the execution of the function (process). Means to call. That is, there is a dependency relationship between service interfaces belonging to the same component. The service interface is a definition that the function is exposed to the outside of the component, and “service call within the same component” is contrary to the definition, and therefore it is an illegal dependency relationship.

  For example, in 1220, which is an example of the data of the service interface dependency definition 3200, the service interface specified by the association source service interface ID 1204 “Serv0011” has the component ID “Comp001” from the data of the service interface definition 3050. Belongs to a component. Further, the service interface specified by the related service interface ID 1206 “Serv0012” belongs to the component having the belonging component ID “Comp001” from the data of the service interface definition 3050. Furthermore, since the definition fixing flag is “FALSE”, the data of the dependency definition between service interfaces shown in 1220 is recognized as an incorrect dependency “service call within the same component”. The data (1720 in FIG. 7) of the illegal dependency analysis result 3500 is created. An illegal dependency relationship “service call within the same component” can be detected by the illegal dependency policy program that executes the processing shown in the above example.

  An illegal dependency policy program corresponding to “other component table direct reference” 1622 of the illegal dependency policy definition 3400 will be described. “Other component table direct reference” means that when a service interface belonging to a certain component is published (called from another), a table belonging to a different component is executed during the execution of the function (process). It is to refer. That is, there is a dependency relationship between a service interface belonging to a certain component and a table having another component. “Other component table direct reference” directly refers to the table of another component without using the service interface, so the maintainability is improved due to the influence of changing the table. It becomes a factor to decrease.

  For example, in 1310, which is an example of data in the service interface / table dependency definition 3250, the service interface specified by the association source service interface ID 1304 “Serv0011” has the component ID “Comp001” from the data in the service interface definition 3050. Belongs to a component. Further, the table specified by the relation destination table ID 1306 “Tbl0021” belongs to the component having the belonging component ID “Comp002” from the data of the table definition 3100. Further, since the fixed definition flag 1308 is “FALSE”, the data of the service interface / table dependency definition shown in 1310 is recognized as an illegal dependency “table reference of other component table directly”. Then, data (1722 in FIG. 7) of the illegal dependency analysis result 3500 is created. An illegal dependency relationship “directly referring to a table of another component” can be detected by the illegal dependency policy program that executes the processing shown in the above example.

  The illegal dependency policy program corresponding to “Difference between component dependency and service interface dependency” 1624 of the illegal dependency policy definition 3400 will be described. "Difference between component dependency and service interface dependency" means that a dependency relationship between service interfaces across components is opposite to other dependency relationships across components, resulting in mutual dependency between components It means a possible condition. As a result, the direction of the dependency relationship between service interfaces across components can be defined so as to conform to the dependency relationship between components, and mutual dependency between components can be prevented.

  In addition, “difference between component dependency and service interface dependency” means that there is a dependency between service interfaces belonging to these components even though there is no dependency between components. Accordingly, it is possible to prevent a dependency between service interfaces from being formed across the components even though it is determined that there is no dependency between the components defined in the process of component division.

  For example, in 1222 which is an example of the data of the service interface dependency definition 3200, the service interface specified by the association source service interface ID 1204 “Serv0021” is a component whose belonging component ID is “Comp002” from the data of the service interface definition 3050. Belonging to. Further, the service interface specified by the related service interface ID 1206 “Serv0011” belongs to the component having the belonging component ID “Comp001” from the data of the service interface definition 3050. On the other hand, since the relation source component ID 1104 of 1120 which is an example of the inter-component dependency definition data is “Comp001” and the relation destination component ID 1106 is “Comp0002”, the inter-table dependency relation and inter-component dependency relation The direction is reversed. Furthermore, since the definition fixed flag 1208 is “FALSE”, the data of the dependency definition 3200 between service interfaces shown in 1222 is an incorrect dependency “difference between dependency between components and dependency between service interfaces”. For example, in step 704, data of the fraud dependency analysis result 3500 (1724 in FIG. 7) is created. An illegal dependency relationship “difference between component dependency and service interface dependency” can be detected by the illegal dependency policy program that executes the process shown in the above example.

  An illegal dependency policy program corresponding to “difference between inter-component dependency and inter-table dependency” 1626 of the illegal dependency policy definition 3400 will be described. “Difference between component dependency and inter-table dependency” means that a certain inter-table dependency across components is opposite to other dependency across components, resulting in mutual dependency between components It means a possible condition. As a result, the direction of the inter-table dependency relationship between components can be defined so as to conform to the inter-component dependency relationship, and mutual dependency between components can be prevented.

  Further, “difference between inter-component dependency relationship and inter-table dependency relationship” also means that there is a dependency relationship between tables belonging to these components even though there is no dependency relationship between components. Accordingly, it is possible to prevent a dependency between tables from being created across the components even though it is determined that there is no dependency between the components defined in advance in the process of component division.

  For example, in 1410 which is an example of the data of the inter-table dependency definition 3300, the table specified by the relation source table ID 1404 “Tbl0021” belongs to the component having the belonging component ID “Comp002” from the data of the table definition 3100. Further, the table specified by the relation destination table ID 1406 “Tbl0011” belongs to the component having the belonging component ID “Comp001” from the data of the table definition 3100. On the other hand, the relation source component ID 1104 of 1120 which is an example of the inter-component dependency definition data is “Comp001” and the relation destination component ID 1106 is “Comp0002”, and the inter-table dependency relation and the inter-component dependency direction are reversed. The direction. Furthermore, because the definition fixed flag 1408 is “FALSE”, the data of the inter-table dependency definition 3300 shown in 1410 is recognized as an incorrect dependency “difference between inter-component dependency and inter-table dependency”. For example, in step 704, data (1726 in FIG. 7) of the fraud dependency analysis result 3500 is created. An illegal dependency relationship “difference between inter-component dependency relationship and inter-table dependency relationship” can be detected by the illegal dependency relationship policy program that executes the processing shown in the above example.

  In the above, as an example of the program of the illegal dependency policy program, “service call within the same component”, “direct table reference of other components”, “difference between dependency between components and dependency between service interfaces”, and “Difference between inter-component dependency and inter-table dependency” is shown, but various illegal dependency relations are also detected by executing processing to detect illegal dependency in the same way for other illegal dependency policy programs. Can be detected.

  Hereinafter, in order to explain in detail the application of the improvement measure in step 604 of FIG. 6, an example of data to be used will be described first. There are 820 and 821 as data of the component definition 3000 (FIG. 8). There is 920 as data of the service interface definition 3050 (FIG. 9). There are 1020 and 1022 as data of the table definition 3100 (FIG. 10). There is 1120 as data of the inter-component dependency definition 3150 (FIG. 11). There are 1310 and 1312 as data of the service interface / table dependency definition 3250 (FIG. 13). 1410 is data of the inter-table dependency definition 3300 (FIG. 14). This case is shown in FIG.

  In FIG. 29, 2902 is 820, 2904 is 821, 2906 is 920, 2908 is 1020, 2910 is 1022, 2912 is 1222, 2914 is 1220, 2916 is 1410, 2918 is 1120, Each corresponds. Also, if there are 1620, 1622, 1624, and 1626 as the data of the illegal dependency policy definition 3400 (FIG. 16), 2912 corresponding to “Other component table direct reference” 1622 and “Component” 2916 corresponding to “difference between inter-dependency relationship and inter-table dependency relationship” 1626 can be detected. Hereinafter, a case will be described in which three improvement measures for improving the “direct reference table of other components” 2912 in the component design example shown in FIG. 29 are applied.

  “Improper Dependency Improvement Measure Program” corresponding to 1520 Illegal Dependency Improvement Measure Program ID 1504 “hpro001”, which is an example of the data of the illegitimate dependency improvement plan definition 3350, This is an improvement to improve the “direct reference to other component table” by moving the service interface belonging to a certain component that directly refers to the table to another component that is the same as the table. The movement of the service interface is performed by the movement operation (506 in FIG. 5) with respect to the service interface definition 3050 of the component element definition operation unit 104.

  FIG. 30 shows the result of applying this improvement measure to the component design example 2912 shown in FIG. In the component design of FIG. 30, “service 11” 2906 is moved to “component 2” 2904, and “direct table reference of other components” in 2912 of FIG. 29 is improved. However, as shown in FIG. 30, 2914 newly becomes “directly refer to the table of another component”. 2912 in FIG. 29 can be improved by the illegal dependency relationship improvement program that executes the processing as shown in the above example.

  The service interface is directly connected to the “destination table move” which is an illegal dependency improvement program corresponding to the illegal dependency improvement program ID 1504 “hpro002” of 1522 which is an example of the data of the illegal dependency improvement plan definition 3350. This is an improvement measure that improves “direct reference to other component tables” by moving the referenced table to the same component as the service interface. The table is moved by a movement operation (506 in FIG. 5) with respect to the table definition 3100 of the component element definition operation unit 104.

  FIG. 31 shows the result of applying this improvement measure to the component design example 2912 shown in FIG. In the component design of FIG. 31, “table 21” 2910 has been moved to “component 1” 2902, and “direct reference to other component tables” 2912 has been improved. This also improves the incorrect dependency relationship 2916 “Difference between dependency relationship between components and dependency relationship between tables”. 2912 “Direct table reference of other components” can be improved by the unauthorized dependency improvement program that executes the processing as shown in the above example.

  “Create Destination Service Interface”, which is an illegal dependency improvement program corresponding to the illegal dependency improvement program ID 1504 “hpro003” of 1524 which is an example of the data of the illegal dependency improvement plan definition 3350, Add a new service interface that accesses the directly referenced table to the same component as the table, and refer to the table through the added service interface (deleting and adding dependencies between service interfaces). It is an improvement measure to improve “direct reference”. The new service interface is added by an additional operation (502 in FIG. 5) for the service interface definition 3050 of the component element definition operation unit 104. Further, the deletion and addition of the inter-service interface dependency are performed by deleting and adding (504 and 502 in FIG. 5) to the inter-service interface dependency definition 3200 of the component element definition operation unit 104.

  FIG. 32 shows the result of applying this improvement measure to the component design example 2912 shown in FIG. In the component design of FIG. 32, 2912 is deleted, and a new “service 22” 2920, a new inter-service interface dependency 2922, and a new inter-service interface / table dependency 2924 are added. 2912 “Direct table reference of other components” can be improved by the unauthorized dependency improvement program that executes the processing as shown in the above example.

  In the above, the illegal dependency improvement program for improving “direct reference to another component table” has been described as an example of the illegal dependency improvement program. However, the component element definition operation unit 104 is similarly applied to other illegal dependency improvement programs. This can be realized by using various operations and can improve each illegal dependency relationship.

Hereinafter, calculation of the illegal dependency evaluation points (the sum of the illegal dependency policy points 1606 for the component design) performed in step 704 and step 706 will be described using an example. In explaining the calculation example of the illegal dependency evaluation score, here, as the data of the illegal dependency policy definition 3400 (FIG. 16), “Service call within the same component” 1620, “Table direct reference of other component” 1622, Assume that there are “difference between component dependency and service interface dependency” 1624 and “difference between component dependency and inter table dependency” 1626. Further, each of the fraud dependency evaluation points will be described by taking the component design of FIGS. 29 to 32 as an example.
A description will be given of the calculation of the fraud dependency evaluation score in the component design shown in FIG. Since 2912 corresponds to “directly referencing tables of other components” 1622, there are five illegal dependency policy points. 2914 is 0 because there is no relevant illegal dependency policy. Since 2916 corresponds to “difference between inter-component dependency and inter-table dependency” 1626, there are three illegal dependency policy points. From the above, the unfair dependency evaluation points in the component design shown in FIG. 29 are 8 points (= 5 points + 0 points + 3 points).

  The calculation of the fraud dependency evaluation points in the component design shown in FIG. 30 will be described. 2912 is 0 because there is no corresponding illegal dependency policy. Since 2914 corresponds to “direct reference to other component table” 1622, the illegal dependency policy points are 5 points. Since 2916 corresponds to “difference between inter-component dependency and inter-table dependency” 1626, there are three illegal dependency policy points. From the above, the unauthorized dependency relation evaluation point in the component design shown in FIG. 30 is “8 points (= 0 points + 5 points + 3 points)”. At this time, the illegal dependency improvement result evaluation point 1808 (point indicating the degree of improvement compared with the original illegal dependency evaluation point 8 of FIG. 29 in FIG. 29) is 0, such as 1820 through step 718. Data of the illegal dependency improvement plan 3550 is created.

  The calculation of the fraud dependency evaluation points in the component design shown in FIG. 31 will be described. 2912, 2914, and 2916 are 0 points because there is no corresponding illegal dependency relationship policy. From the above, the unauthorized dependency relation evaluation point in the component design shown in FIG. 31 is “0 point (= 0 point + 0 point + 0 point)”. At this time, the unauthorized dependency relationship improvement result evaluation point 1808 is −8 points, and for example, data of an unauthorized dependency relationship improvement plan 3550 such as 1822 is created through step 718.

  Calculation of evaluation points in the component design shown in FIG. 32 will be described. 2914, 2922, and 2924 are 0 points because there is no corresponding illegal dependency relationship policy. Since 2916 corresponds to “difference between inter-component dependency and inter-table dependency” 1626, there are three illegal dependency policy points. From the above, the unauthorized dependency evaluation point in the component design shown in FIG. 32 is “3 points (= 0 point + 0 point + 0 point + 3 point)”. At this time, the unauthorized dependency improvement result evaluation score is −5, and for example, data of an illegal dependency improvement plan 3550 such as 1824 is created through step 718.

  From the above, the improvement measure “move related table” that is changed from the component design shown in FIG. 29 to the component design shown in FIG. 31 is the most effective improvement measure for improving the illegal dependency relationship.

  However, if the fixed definition flag of 1022 that is the data of the table definition is “TRUE”, the table cannot be moved, so the improvement measure “Move related table” cannot be performed (component element definition operation section (This causes an error in the move operation for the table definition of 104). Therefore, it is excluded from the improvement plan, and in this case, the improvement method of “related destination service interface creation” for changing from the component design shown in FIG. Is the most effective way to improve fraud dependency.

  In addition, from the definition of illegal dependency improvement result evaluation score, if the illegal dependency improvement result evaluation score is a positive number, it means that the illegal dependency relationship has increased by applying the improvement measures, indicating that it has been altered. Suggest.

  The improvement proposals are arranged in ascending order of the evaluation of improvement of the illegal dependency relationship in step 418 and step 420 of the component element definition editing unit 102, and are displayed on the display device 204 as 2608 in FIG. 26 and 2706 in FIG. Therefore, it becomes easy for the user to select an improvement measure that is highly effective in improving the illegal dependency relationship.

  According to the component division support device of the present embodiment, it is possible to detect a dependency relationship between component elements that violate a policy, and to present and apply improvement measure candidates to the detected illegal dependency relationship. As a result, it is possible to increase the certainty of the component division work.

It is a block diagram of the component division | segmentation assistance apparatus which concerns on embodiment of this invention. This is a computer system configuration for realizing a component division support apparatus. It is an example of a table structure of a component division | segmentation assistance apparatus. It is a processing flow of a component element definition edit part. It is a table | surface which shows an example of the processing content of a component element definition operation part. It is a processing flow of an improvement measure application part. It is a processing flow of a dependency analysis part. It is a figure which shows an example of a structure and data of a component definition. It is a figure which shows an example of a structure and data of a service interface definition. It is a figure which shows an example of a structure and data of a table definition. It is a figure which shows an example of a structure and data of a dependency relation definition between components. It is a figure which shows an example of a structure and data of a dependency relation definition between service interfaces. It is a figure which shows an example of a structure and data of a service interface table dependency relationship definition. It is a figure which shows an example of a structure and data of a dependency relation definition between tables. It is a figure which shows an example of a structure and data of a fraud dependency improvement policy definition. It is a figure which shows an example of a structure and data of an unauthorized dependency policy definition. It is a figure which shows an example of a structure and data of an unauthorized dependence relationship analysis result. It is a figure which shows an example of a structure and data of a fraud dependence improvement plan. It is an example of an edit menu screen. It is an example of a component definition edit screen. It is an example of a service interface definition edit screen. It is an example of a table definition edit screen. It is an example of a service interface dependency relationship definition edit screen. It is an example of a service interface / table dependency definition editing screen. It is an example of the inter-table dependency definition edit screen. It is an example of an improper dependence improvement measure application screen. It is an example of an improper dependence improvement measure application screen. It is an example of a dependency relationship definition edit screen between components. It is an example of component design. It is an example of component design. It is an example of component design. It is an example of component design.

Explanation of symbols

100: component division support device, 102: component element definition editing unit, 104: component element operation unit, 106: improvement measure application unit, 108: dependency analysis unit, 150: component element definition storage unit, 170: improvement measure storage unit 180: dependency policy storage unit, 190: dependency analysis result storage unit, 203: input device, 204: output device.

Claims (13)

Service interface that is an element of the component of the development target software, a table, and a component element definition storage unit that stores definition data related to the dependency relationship between them, and a dependency relationship that stores policy data that defines an illegal dependency relationship regarding the dependency A policy storage unit, an improvement measure storage unit that stores a plan for improving a dependency relationship that violates the policy, and a policy data that defines the illegal dependency relationship stored in the dependency policy storage unit; Detects a dependency relationship that violates the policy from the dependency relationship stored in the element definition storage unit, and uses a proposal to improve the dependency relationship that violates the policy stored in the improvement measure storage unit. Output a candidate for improving the dependency relationship against the policy Components division support apparatus characterized by having a relationship analysis unit. For each of the definition data stored in the component element definition storage unit, a fixed definition flag indicating whether the definition data can be changed is provided, and the dependency analysis unit detects a dependency relationship that violates the policy. When the definition fixed flag indicates whether the definition data is changed or not, corresponding to at least one of the dependency relationship against the policy and the definition data of the component element related to the dependency relationship, The component division support device according to claim 1, wherein the component division support device is excluded from detection targets of contradictory dependencies. For each of the definition data stored in the component element definition storage unit, a definition fixing flag indicating whether the definition data can be changed is provided, and the dependency relationship analysis unit is a dependency relationship against the detected policy. when outputting the candidate of improvement measures, according to claim 1, characterized in that to exclude improvement measures defined fixing flag to change the definition data indicating whether the definition data changes from the candidate of the improvements Component division support device. An evaluation score is provided for each of the policy data that defines the illegal dependency relationship stored in the dependency policy storage unit, and the dependency analysis unit uses the evaluation point to detect the policy The component division support apparatus according to claim 1, wherein the candidate is output together with an evaluation point indicating an improvement degree of the candidate of the contradictory dependency improvement plan. Service interface that is an element of the development target software component, table and definition data related to the dependency relationship between them, policy data that defines an illegal dependency relationship with respect to the dependency relationship, and a plan to improve the dependency relationship against the policy A storage device for storing, an input device for requesting registration of definition data related to the dependency relationship, and policy data for defining the illegal dependency relationship in response to a registration request for definition data related to the dependency relationship from the input device. Te, the registration requested dependency determines whether the dependency against the said policy, said when registration required dependency is determined to be dependency against the policy, the policy Using a proposal to improve the contradictory dependency, the modification of the dependency against the policy Components division assisting apparatus characterized by comprising: a processor determining a candidate proposal, a display device and for outputting the candidate of the determined improvement plan. The storage device stores, for each of the definition data, a definition fixing flag indicating whether or not the definition data can be changed, and the processor detects a dependency that violates the policy. When the definition fixed flag stored in the storage device indicates whether the definition data is changed or not, corresponding to at least one of the definition data of the component elements related to the relationship and the dependency relationship, the policy The component division support apparatus according to claim 5, wherein the component division support apparatus is excluded from detection targets of dependency relations contrary to the above. The storage device stores, for each of the definition data, a definition fixing flag indicating whether or not the definition data can be changed, and the processor outputs a candidate for a dependency improvement measure that violates the determined policy. The improvement measure for changing the definition data in which the definition fixed flag stored in the storage device indicates whether or not the definition data is changed is excluded from the candidates for the improvement measure. The component division support apparatus described. The input device accepts an input of a registration request for definition data related to service interfaces, tables, and dependency relationships between them, which are elements of components of the development target software, and stores them in a storage device. The processor stores the definition data related to the dependency relationships. In response to a registration request, the definition data stored in the storage device and policy data that defines an illegal dependency relationship with respect to the dependency relationship are used, and the dependency relationship requested for registration is a dependency relationship that violates the policy. An improvement plan for improving the dependency against the policy stored in the storage device when it is determined whether or not the dependency requested for registration is a dependency contrary to the policy Using data, seek candidates for improvement plan for dependency relationship that violates the policy, and the proposed improvement plan Components division support method and outputting to the display device candidate. The processor uses a definition fixing flag associated with each of the definition data to indicate whether the definition data can be changed, and detects a dependency that violates the policy. When the definition fixing flag corresponding to at least one of the component element definition data related to the dependency relationship indicates whether or not the definition data is to be changed, it is excluded from the dependency detection target that violates the policy. The component division support method according to claim 8. The processor uses the definition fixing flag associated with each of the definition data and indicates whether or not the definition data can be changed, and outputs a candidate for a measure for improving the dependency relationship that violates the determined policy. 9. The component division support method according to claim 8, wherein an improvement measure for changing definition data whose definition fixed flag indicates whether or not the definition data is changed is excluded from candidates for the improvement measure. A service interface that is an element of a development target software component stored in a storage device, a table and definition data related to the dependency between them, policy data that defines an illegal dependency related to the dependency, and a policy Using the improvement plan data for improving the contradictory dependency, a registration request for definition data relating to the dependency is input, and the policy data for defining the illegal dependency is defined in response to the definition data relating to the dependency. using, when the registration requested dependency determines whether the dependency against the said policy, the registration requested dependency is determined to be dependency against the said policy, said policy Dependency against the above policy using improvement plan data that improves dependency against the policy Seeking candidates for improvement idea relationship components divided support program, characterized in that to execute the steps of outputting a candidate of the determined improvement plan into the computer. When detecting a dependency relationship that violates the policy by using a definition fixed flag that indicates whether the definition data can be changed, associated with each of the definition data, the dependency relationship that violates the policy and the relationship to the dependency relationship When the definition fixing flag corresponding to at least one of the component element definition data indicates whether or not the definition data is to be changed, the computer is caused to perform a procedure for excluding from the dependency detection target against the policy. 12. The component division support program according to claim 11, wherein: When outputting a candidate for a measure for improving a dependency relationship that violates the determined policy, using the definition fixing flag associated with each of the definition data and indicating whether or not the definition data can be changed, the definition fixing flag is 12. The component division support program according to claim 11, which causes a computer to execute a procedure for excluding an improvement measure for changing definition data indicating whether or not the definition data is changed from candidates for the improvement measure.

Images