JP2018028776A - Software asset management device, software asset management method, and software asset management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To specify a range of influence accompanying modification/alteration of software by narrowing down the range to an appropriate range.SOLUTION: A software asset management device is connected to information holding means that stores, in association with a module constituting a business system, an identifier of data accessed by the module and the type of access indicating the type of the access: creation, deletion, update, or reference, and comprises range of influence analysis means that selects, from data accessed by a designated module, one that is created, deleted, or updated, and extracts, from the information holding means, an identifier of the module accessing the selected data and outputs the extracted identifier.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a software asset management device, a software asset management method, and a software asset management program, and in particular, a software asset management device, a software asset management method, and a software asset that search an influence range associated with modification of a part of software. Regarding management programs.

  In order to identify the scope of impact when modifying / modifying software, a staff with know-how conducts a full-scale search of specifications and source code based on keywords related to the modification requirements and investigates the scope of impact based on experience. Is often performed.

  (A) However, there are cases in which the relationship between systems and functions is lost due to the loss of specifications due to long-term maintenance and modification. In this case, there is a problem that the influence range cannot be specified only by the investigation from the specification.

  In addition, since this survey depends on experience, the following problems occur.

  (B) Even if a program to be modified / modified is specified based on the correction requirements, the scope of the influence is limited to the source program that constitutes the program. However, even in other programs that do not have a direct calling relationship with the program to be corrected, a program that accesses common data may be the target of correction, and an oversight of the effect may occur. For this reason, degradation and unexpected bug embedding occur.

  For such a problem, Patent Document 1 stores the relationship between each program and a program in the business module that accesses the program, and accesses the changed data when the name and content of the changed data are input. Get the program name.

JP 2000-99571 A

  When the scope of influence is specified as a result of software modification / modification, there is a case where there is no influence depending on the data access method even between programs accessing common data. Since the system of Patent Document 1 determines the influence range only by determining whether or not data is being accessed, there is a possibility that an excessively wide range may be acquired as the influence range.

  An object of the present invention is to provide a software asset management device, a software asset management method, and a software asset management program that can solve the above-described problems and can appropriately narrow down the influence range.

  The software asset management apparatus according to one embodiment of the present invention relates to an identifier of data accessed by the module in association with a module constituting a business system, and the access is created, deleted, updated, or referenced. Connected to an information holding means for storing an access type indicating whether or not, the data to be created, deleted or updated is selected from the data accessed by the designated module, and the selected data is accessed An influence range analyzing unit that extracts and outputs an identifier of the module to be extracted from the information holding unit.

  The software asset management method according to an embodiment of the present invention relates to an identifier of data accessed by a module in association with a module constituting a business system, and whether the access is created, deleted, updated, or referenced. With reference to the information holding means for storing the access type indicating whether or not there is selected the data to be created, deleted or updated among the data accessed by the specified module, and the selected data is The identifier of the module to be accessed is extracted from the information holding means and output.

  A software asset management program according to an embodiment of the present invention relates to an identifier of data accessed by a module in association with a module constituting a business system, and the access is created, deleted, updated, or referenced. Select the data to be created, erased, or updated among the data accessed by the specified module to the computer connected to the information holding means for storing the access type indicating whether or not the selected An influence range analysis process for extracting and outputting an identifier of the module accessing the data from the information holding unit is executed.

  The software asset management apparatus according to the present invention can be narrowed down to an appropriate range when the affected range is specified along with the modification / correction of software.

FIG. 1 is a diagram showing a configuration of a software asset management system 10 according to the first embodiment. FIG. 2 is a diagram illustrating the structures of the A) information holding table and the B) link table stored in the information holding unit 8. FIG. 3 is a diagram showing a set of information items stored in the information holding table and the link table shown in FIG. FIG. 4 is a diagram showing the structure of a sales system taken as an example in the operation description of the software asset management device 3. FIG. 5 is a diagram (part 1) illustrating the structure of the information holding table, the link table, and the access type table. FIG. 6 is a diagram (part 2) illustrating the structure of the information holding table, the link table, and the access type table. FIG. 7 is a diagram (part 3) illustrating the structure of the information holding table, the link table, and the access type table. FIG. 8 is a diagram (part 1) illustrating a process of creating a program-data relation table based on the information holding table, the link table, and the access type table. FIG. 9 is a diagram (part 2) illustrating a process of creating a program-data relation table based on the information holding table, the link table, and the access type table. FIG. 10 is a diagram (part 3) illustrating a process of creating a program-data relation table based on the information holding table, the link table, and the access type table. FIG. 11 is a diagram (part 4) illustrating a process of creating a program-data relation table based on the information holding table, the link table, and the access type table. FIG. 12 is a diagram (No. 5) illustrating a process of creating a program-data relation table based on the information holding table, the link table, and the access type table. FIG. 13 is a diagram showing the structure of the program-data relationship table. FIG. 14 shows a process of creating an impact list based on the program-data relationship table (part 1). FIG. 15 shows a process of creating an impact list based on the program-data relationship table (part 2). FIG. 16 shows the process of creating the impact list based on the program-data relationship table (No. 3). FIG. 17 shows a process of creating an impact list based on the program-data relationship table (No. 4). FIG. 18 is a diagram showing a process of creating an impact list based on the program-data relationship table (No. 5). FIG. 19 shows a process of creating an impact list based on the program-data relationship table (No. 6). FIG. 20 is a diagram illustrating a determination matrix for the influence range analysis unit 71 to determine whether or not the change of the access type has a possibility of affecting other modules. FIG. 21 is a configuration diagram of the computer apparatus 600. FIG. 22 is a diagram illustrating the structure of the software asset management apparatus 3 according to the second embodiment.

<First Embodiment>
<Configuration>
FIG. 1 is a diagram showing a configuration of a software asset management system 10 according to the first embodiment. The software asset management system 10 includes a software asset management device 3, an input device 1 connected to the software asset management device 3, an output device 2, and an information holding unit 8.

  The information holding unit 8 is a repository that stores information for managing software assets, or a part thereof. The software asset management device 3 is a processing device that inputs, extracts, and analyzes information with respect to the information holding unit 8. The software asset management device 3 acquires information from the input device 1 operated by the user and displays the calculated result on the output device 2.

  The software asset management device 3 includes an information input unit 5 and an information analysis unit 7.

  The information input unit 5 performs various inspections and processes when inputting information to the information holding unit 8. The information input unit 5 includes an access type input unit 51 that extracts data and access types accessed by the program from the source code of the input program and stores them in the information holding unit 8.

  The information analysis unit 7 analyzes a range that may be affected when the software is modified / modified. The information analysis unit 7 includes an influence range analysis unit 71 that analyzes an influence range based on a shared relationship of data, and a higher-order and lower relationship analysis unit 72 that analyzes the influence range based on a hierarchical structure of software.

  FIG. 2 is a diagram illustrating the structures of the A) information holding table and the B) link table stored in the information holding unit 8.

  The information holding table is a table that stores a number, an information name, a division position, an information entity, an outgoing link, and an incoming link for each information item stored in the information holding unit 8. The information item is, for example, a program module, a data table, an input / output message, a group thereof, or a superordinate concept. Groups and superordinate concepts are hierarchical.

  The number is an information item identifier in the table. Since the division position is not related to the present invention, the description is omitted. The information entity is, for example, a module source code, an object code, and management information thereof. The items of the outgoing link and incoming link indicate the number of the related link that comes out of or enters the information item.

  Each link is registered in the link table. The link table includes, for each related link, a number (identifier in the table), an attribute to be described later, and start point information / end point information (information on which information item the related link is output from and which information item is connected). keeping. The relationship link includes a link indicating a lower structure and a link indicating association, and it can be determined from the attribute which link is the link.

  Specifically, the information holding table and the link table shown in FIG. 2 are examples in the case where the set of information items shown in FIG. 3 is stored.

  In FIG. 3, “sales department (subsystem)” is subordinate to “business flow (system)”, and “order processing (module)”, “inventory processing”, and “shipping instruction processing” are subordinate to “sales department”. Indicates a set of information items. In this set, “order form”, “manufacturing instruction sheet”, and “issue instruction sheet” are associated with “order process”, “inventory process”, and “issue instruction process”, respectively.

  In FIG. 2, for example, the fact that the “sales department” with the number 2 in the information holding table is below the “business flow” with the number 1 in the information holding table is represented by the related link with the number 1 in the link table. In the link table, the relational link of number 1 is a relational link indicating a subordinate structure starting from “business flow” of number 1 in the information holding table and ending in “sales department” of number 2 of the information holding table. Is shown.

  Similarly, the fact that “order form” is associated with “order processing” is expressed by a relational link of number 5 in the link table. In the link table, the relational link of number 5 is a relational link indicating an association starting from “order book” of number 6 in the information holding table and starting from “order processing” of number 3 in the information holding table. Show.

  The relational link indicating the association may or may not have meaning in the direction of the link. For example, a relationship link indicating an association from the module to the data may represent an update, and a relationship link from the data to the module may represent a reference. On the other hand, the relational link indicating the association between the module and the data may only indicate that the module accesses the data.

  Here, the items of the outgoing link and incoming link of the information holding table are information that can be obtained by searching the link table by the information holding table number, and are not essential items in structure. However, in actual operation, if the amount of information registered in the information holding unit 8 increases enormously, the search time of the link table is expected to have a large effect on the overall performance. As a means for speeding up, it is effective to have information on outgoing links and incoming links in the information holding table.

  Here, the information input unit 5 and the information analysis unit 7 of the software asset management apparatus 3 are composed of logic circuits. The information holding unit 8 is configured by a magnetic storage device or a semiconductor storage device.

  The software asset management device 3 may be realized by the computer device 600. FIG. 21 is a configuration diagram of the computer apparatus 600. The computer device 600 includes a processor 610, a main storage unit 630, and an external storage device 620 that are connected to each other via a bus 640. The processor 610 reads / writes data from / to the main storage unit 630 and the external storage device 620 via the bus 640. Further, the processor 610 executes a program 650 stored in the main storage unit 630. Note that the program 650 is initially stored in the external storage device 620, and the processor 610 may load the external storage device 620 from the external storage device 620 to the main storage unit 630 when the computer device 600 is initially set.

  Here, the main storage unit 630 is a semiconductor memory device. The external storage device 620 is a storage device such as a disk device or a semiconductor storage device.

  The processor 610 functions as the information input unit 5 and the information analysis unit 7 by executing the program 650, for example. That is, the processor 610 executes the program 650 to execute, for example, processing performed by the information input unit 5 and the information analysis unit 7. The main storage unit 630 or the external storage device 620 functions as the information holding unit 8.

<Operation>
FIG. 4 is a diagram showing the structure of a sales system often taken as an example in the following description of the operation of the software asset management device 3.

  The sales system is divided into three subsystems of order processing, inventory management processing, and delivery processing, and each is realized by an order processing program, an inventory confirmation program, and a delivery instruction program.

  The order processing program is composed of modules 1 to 3. The inventory confirmation program is composed of modules 4 to 6. The exit instruction program is composed of modules 7 to 9.

  Modules are programs, programs are subsystems, and subsystems are substructures of sales systems. The system, program, and module as in this example are registered in advance in the information holding table as information items, and the hierarchical relationship is registered as a relation link indicating the subordinate structure of the link table. Numbers 1 to 4 in A) and numbers 1 to 3 in B) are examples of pre-registered information about the order processing program. Numbers 1 to 4 in A) and numbers 1 to 3 in B) are examples of pre-registered information about the inventory confirmation program. Numbers 1 to 4 in FIG. 7A and numbers 1 to 3 in B) are examples of information registered in advance for the exit instruction program.

  For example, the information input unit 5 reads and registers the source program of each module and the structure definition information of the sales system. The software asset management apparatus 3 or the repository administrator may register this information manually.

  Further, in the sales system of FIG. 4, module 1 accesses the customer master, and module 3 accesses the product master and the order table as data. Module 4 accesses the order table, and module 5 accesses the inventory table. Module 7 accesses the product master and the order table, and module 9 accesses the inventory table.

  These data and access relationships are registered by the access type input unit 51 by the processing described below. For example, the information input unit 5 may read the definition information of each data and register the data such as the product master in the information holding table as information items.

<Processing flow 1>
The access type input unit 51 analyzes, for example, a module source program stored in the repository, and registers the data to be accessed and the access type in the information holding unit 8. The access type input unit 51 registers the type to be accessed according to the following determination condition.
When the access type input unit 51 detects the source code of a process for creating new data (file or record), such as CREATE of a file or WRITE of a record, the access type “Create (abbreviated as C)” is associated Register a relationship link that indicates
When the access type input unit 51 detects a source code of a process for reading data such as a READ of a record, the access type input unit 51 registers a relational link indicating an association of the access type “reference (abbreviated as R)”.
When the access type input unit 51 detects the source code of the data update process such as UPDATE or REWRITE of the record, the access type input unit 51 registers a relational link indicating the association of the access type “update (abbreviation U)”. In the case of REWRITE, since READ is also performed, a relational link indicating the association of “reference” is also registered.
When the access type input unit 51 detects the source code of the process of deleting data (file or record) such as file ELASE or record DELETE, the access type input unit 51 indicates the association of the access type “delete (abbreviation D)”. Register related links.
The access type input unit 51 performs only the definition of the file and record, and when detecting the source code of the process that does not access the data, the relationship indicating the association of the access type “definition only (abbreviated as X)” Register the link.

  Specifically, when the access type input unit 51 detects data access from the source program, for each access, the access type input unit 51 registers a relation link indicating the association with the target data in the information holding table and the link table, and sets the access type to the relation link. And register it in the access type table.

  For example, when the access type input unit 51 detects a reference to the customer master from the source code of the module 1, first, the customer master of the information item number 5 is registered in the information holding table of FIG. Next, the access type input unit 51 registers a relational link indicating the association of number 4 in the link table of FIG. Further, the access type input unit 51 registers in the link table and the information holding table of FIG. 5 that the related link is a related link between the module 1 with the information item number 2 and the customer master with the information item number 5. Finally, the access type input unit 51 registers in the access type table that the access type is a reference in association with the related link number 4.

  Further, for example, when the access type input unit 51 detects a reference to the inventory table from the source code of the module 5, first, the inventory table of the information item number 6 is registered in the information holding table of FIG. Next, the access type input unit 51 registers a related link indicating the association of number 5 in the link table of FIG. Further, the access type input unit 51 registers in the link table and the information holding table of FIG. 6 that the related link is a related link between the module 5 of the information item number 3 and the inventory table of the information item number 6. Finally, the access type input unit 51 registers that the access type is a reference in the access type table in association with the related link number 5.

  As described above, the access type input unit 51 detects data access from all the modules of the sales system of FIG. 4, and sets the data, the relationship link indicating the association, and the access type as the information holding table, the link table, and Register in the access type table. A), B), and C) of FIG. 5 are data examples after registration of the access type input unit 51 for the order processing program. A), B), and C) in FIG. 6 are examples of data after registration in the access type input unit 51 for the inventory confirmation program. A), B), and C) of FIG. 7 are data examples after the registration processing by the access type input unit 51 for the exit instruction program. 5, FIG. 6, and FIG. 7 all show a part of the table for the entire sales system.

<Processing flow 2>
The influence range analysis unit 71 in the information analysis unit 7 first searches the information holding table, the link table, and the access type table after the registration processing by the access type input unit 51, and analyzes the relationship information between the program and the data. Create a program-data relationship table.

  FIG. 13 shows the structure of the program-data relationship table. The program-data relationship table is a matrix indicating whether each module accesses the data in correspondence with the data, and what kind of access is used when accessing the data. That is, for example, the influence range analysis unit 71 creates the data shown in FIG. 13 from the data shown in FIGS. 5 to 7 for the three programs shown in FIG. The procedure will be described below.

  Step 1: The scope of influence analysis unit 71 creates a matrix by extracting a list of used modules on the horizontal axis and a list of used data on the vertical axis from the information holding table of each program. FIG. 8 shows an example of the matrix extracted from A) of FIG. 5, A) of FIG. 6, and A) of FIG.

  Step 2: The influence range analysis unit 71 selects data registered at the top of the matrix. In the example of FIG. 8, the influence range analysis unit 71 selects a customer master.

  Step 3: The influence range analysis unit 71 extracts a relation link related to the selected data and a module having the related link from the information holding table and the link table of each program. FIG. 9 shows a state in which the relation link of number 4 relating to “customer master” in FIG. 8 and the module 1 of the order processing program having the relation link are extracted from the information holding table and link table of FIG. Yes.

  Step 4: The influence range analysis unit 71 acquires the access type of the extracted related link from the access type table. FIG. 10 shows a state where the access type “reference” of the related link of number 4 extracted in FIG. 9 is acquired from the access type table of FIG.

Step 5: The influence range analysis unit 71 registers the extracted access type in the cell at the intersection of the selected data in the matrix and the extracted module. FIG. 11 shows a state after the extracted access type “reference (R)” is registered in the cell at the intersection of the selected data “customer master” and the extracted module “module 1” in the matrix.
At this time, when a plurality of access types are acquired, the influence range analysis unit 71 registers all the acquired access types. For example, when “creation” and “reference” are acquired, the influence range analysis unit 71 registers “CR”.

  Step 6: The influence range analysis unit 71 sequentially selects data registered in the matrix, and repeats Step 3 to Step 5 sequentially. FIG. 12 shows the access type “R”, the intersection of the selected data “product master” and the extracted module “module 3” in the matrix, and the selected data “product master” and the extracted module “module 7”. The state after registering in both cells at the intersection with is shown. FIG. 13 shows that access type registration has been completed for the remaining order table and inventory table.

  According to the above procedure, the influence range analysis unit 71 creates a program-data relationship table.

  The range-of-influence analysis unit 71 searches for a row in the program-data relationship table, so that a module having a relationship link with specific data can be grasped even between different programs.

  The software asset management device 3 or the repository administrator may register the program-data relationship table manually.

<Processing flow 3>
Next, the influence range analysis unit 71 creates an influence list in the following procedure for the module for which the influence range due to the modification without changing the access type is to be analyzed.

  First, the user designates a module for which the influence range is to be analyzed. For example, the user specifies that the module 3 is to be corrected within the range where the access type is not changed.

  The influence range analysis unit 71 specifies a list of data having a relational link with a specified module (for example, module 3) by searching the column of the module in the matrix of FIG. Delete the line. For example, from the column of module 3 in FIG. 13, the influence range analysis unit 71 specifies a product master and an order table that have a relationship link, and deletes a customer master and a stock table row that do not have a relationship link.

  In addition, the relation information between “module 3” and each piece of data having a relation link is confirmed. If the access type is reference (R) or definition only (X), the line of the data (product master) is also displayed. delete. This is because if the designated module only refers to or defines the data, the modification of the module does not affect other modules unless the access type is changed.

  FIG. 14 shows this state. In FIG. 14, the deleted line is shaded.

  Next, the influence range analysis unit 71 specifies a module (modules 4 and 7) that is related to the specified module (module 3) and the data (order reception table) that has a related link by searching the row of the data. To do. Next, the influence range analysis unit 71 deletes a column of modules having no relation link. At this time, when the relationship information is “definition only (X)”, the influence range analysis unit 71 also deletes the module column in which only the information of “definition only (X)” exists. This is because such a module is not a module using data. FIG. 15 shows this state. In FIG. 15, the deleted column is shaded.

  From the matrix left after the deletion (FIG. 16), it is possible to create an influence list of modules (modules 4 and 7) having an influence on the correction of “module 3”. FIG. 17 shows an influence list.

<Processing flow 4>
The influence range analysis unit 71 creates a list of influences by simulating modules that are likely to be affected by the following procedure with respect to modules that are scheduled to be modified with a change in access type.

  In the order processing of the sales system, an example will be described in which the influence range analysis unit 71 specifies an influential process (function) and module when a modification that changes the access type of the order table occurs.

  In this process, the module shown in FIG. 20 is subjected to the determination shown in FIG. 20 based on the program-data relation table created in the process flow 2, and an impact list is created and output.

  Step 1: A user designates a module to be modified and data whose access type is changed by the modification. For example, the user corrects the module 1 and designates that the access type to the inventory table is changed.

  Step 2: The influence range analysis unit 71 extracts a row of designated data (inventory table) from the program-data relationship table of FIG. FIG. 18 shows this state. In FIG. 18, the lines not extracted are shaded.

  Next, the influence range analysis unit 71 specifies a module that is related to the specified data (inventory table) by searching a row of the specified data in the matrix, and deletes a column of modules that are not related. At this time, if the relationship information is “definition only (X)”, the module in the column is also deleted. This is because the module is not a module using data. Furthermore, the influence range analysis unit 71 also deletes the column of the correction target module. FIG. 19 shows this state. In FIG. 19, the deleted column is shaded.

  Step 3: The influence range analysis unit 71 determines whether there is a possibility that the change of the access type may affect other modules according to the determination matrix of FIG. The decision matrix is a matrix in which the access type before correction is a row and the access type after correction is a column, and each cell of the matrix stores the presence or absence of the possibility of affecting other modules by changing the access type Yes.

  According to the decision matrix, the influence range analysis unit 71 may affect other modules if there is addition, deletion, or update of creation, deletion, update, or addition of only reference, definition, or Therefore, it is determined that there is no possibility of affecting other modules only by deletion. This is because even if only data reference or definition is added to or deleted from the specified module, other modules are not affected.

  If the modification of the specified module (module 1) corresponds to “none” in the determination matrix, the influence range analysis unit 71 outputs nothing as an influence list. On the other hand, if the modification of the specified module (module 1) corresponds to “Yes” in the determination matrix, the influence range analysis unit 71 determines the modules (modules 5 and 9) remaining from the table of FIG. Are output as an influence list in the modification of the specified module (module 1).

<Processing flow 5>
The higher-order / lower-order relationship analysis unit 72 in the information analysis unit 7 searches for related links of modules included in the effect list output in the process flow 3 or the process flow 4 and acquires an affected higher-order structure.

  The upper / lower relationship analysis unit 72 may acquire the upper structure sequentially by starting from the modules included in the influence list and tracing the relationship link indicating the lower structure of the link table in the reverse direction. Here, following the relational link indicating the subordinate structure in the reverse direction means that the relational link indicating the subordinate structure whose end point is the subordinate structure is identified from the link table, and reaches the superordinate structure that is the starting point of the relevant link. Is repeated in order. The hierarchical structure of the business system is not necessarily a tree structure. There may be a plurality of relational links having a certain lower structure as an end point, and in this case, the upper / lower relation analysis unit 72 searches for the plurality of relational link sequences.

  The upper / lower relationship analysis unit 72 may execute this processing as follows. In the following, as a specific example, a process for acquiring the upper structure of the module 7 related to the order reception table obtained in the process flow 3 is shown.

  Step 1: In this process, there is no need to explore the relationship between modules and data. Therefore, the upper / lower relationship analysis unit 72 excludes the relationship link indicating the association from the search target.

  Step 2: Module 8 is related to the delivery instruction program, but not related to module 7. Therefore, the upper / lower relationship analysis unit 72 excludes a relationship link indicating a lower structure whose direction of the relationship is a lower direction from the search target.

  Step 3: The above-mentioned two are excluded from the search target and all the remaining relation links are traced, and the upper-lower relationship analysis unit 72 acquires a higher-level structure (shipping instruction program, shipping processing, sales system) that affects the module 7. .

  Step 4: Similarly, the upper / lower relationship analysis unit 72 has an upper structure (order processing program, order processing, sales system) that affects the module 3 and an upper structure (stock management program, inventory) that affects the module 4. Management process, sales system).

  Even if the relationship between the sales system and the inventory management process, or the sales system and the issue process cannot be traced due to missing specifications or hierarchical structure information, this processing flow based on the data sharing relationship between modules Based on this, it becomes possible to grasp the relationship between the sales system and the inventory management process and the delivery process.

  Here, the upper / lower relationship analysis unit 72 may execute the process of “tracing all remaining relationship links” in step 3 using a generally known route search method such as the Dijkstra method.

  In the above example, the upper / lower relationship analysis unit 72 searches for relationships between functions, but may trace all relationship links existing in the repository. As a result, the upper-lower relationship analysis unit 72 can also specify the range of influence between systems.

<Effect>
The software asset management device 3 according to the present embodiment can narrow down to an appropriate range when specifying the range of influence associated with the modification / modification of software. The reason is that the influence range analysis unit 71 narrows down other modules that may be affected by the modification / modification of a certain module based on the target data and the access type of the data access of each module. This is because the influence range information is not output. That is, even when the software asset management apparatus 3 of the present embodiment has no relationship between programs, the software asset management device 3 determines the presence or absence of the influence between the programs by focusing on the data, and specifies the influence range.

  Furthermore, the software asset management apparatus 3 according to the present embodiment specifies the influence between programs via data, even if the specification is missing, so that the function between the systems can be determined from the relation information between the programs and data. It is possible to extract the influence between. The reason is that the influence range analysis unit 71 specifies the influence between the programs via the data, and based on the result, the upper and lower level relationship analysis unit 72 specifies the upper component of the program. That is, the software asset management apparatus 3 according to the present embodiment can search for higher-level information for a program, and can check whether there is an influence between systems or functions.

  Furthermore, the software asset management apparatus 3 according to the present embodiment can specify the range of influence before and after the modification accompanied by the change of the access type. This is because the influence range analysis unit 71 simulates a program correction case.

<Modification>
The influence range analysis unit 71 may increase or decrease the influence by weighting the access type with the influence degree in the part that analyzes the presence / absence of the influence between the programs from the access type to the data. Further, the influence range analysis unit 71 may evaluate the closeness between the data and the source program depending on the strength of the influence, or may narrow down the influence range by designating the output range of the influence degree.

  Further, the influence range analysis unit 71 may extract the number of relation links with the program for the data, and may evaluate the risk due to the correction of the data.

<Second Embodiment>
FIG. 22 is a diagram illustrating the structure of the software asset management apparatus 3 according to the second embodiment.

  The software asset management apparatus 3 according to the present embodiment is connected to the information holding unit 8. The information holding unit 8 stores an identifier of data accessed by the module and an access type indicating whether the access is created, deleted, updated, or referenced in association with the module constituting the business system. To do.

  The software asset management apparatus 3 according to the present embodiment includes an influence range analysis unit 71. The influence range analysis unit 71 selects data to be created, deleted, or updated from the data accessed by the designated module, extracts the identifier of the module accessing the selected data from the information holding means, and outputs it. .

  The software asset management device 3 according to the present embodiment can narrow down to an appropriate range when specifying the range of influence associated with the modification / modification of software. The reason is that the influence range analysis unit 71 narrows down other modules that may be affected by the modification / modification of a certain module based on the target data and the access type of the data access of each module. This is because the influence range information is not output.

  While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

  The present invention can be used for design and manufacturing in the software planning / development phase, remodeling support and failure analysis support in the software operation / maintenance phase. Furthermore, the present invention can also be used for impact analysis support and work man-hour estimation support through the above phases.

DESCRIPTION OF SYMBOLS 1 Input device 2 Output device 3 Software asset management apparatus 5 Information input part 7 Information analysis part 8 Information holding part 10 Software asset management system 51 Access type input part 71 Influence range analysis part 72 Higher-order relation analysis part 600 Computer apparatus 610 Processor 620 External storage device 630 Main storage unit 640 Bus 650 Program

Claims (10)

Information holding means for storing an identifier of data accessed by the module and an access type indicating whether the access is created, deleted, updated, or referenced in association with a module constituting a business system Connected to
The range of influence in which the data to be created, deleted, or updated is selected from the data accessed by the specified module, and the identifier of the module that accesses the selected data is extracted from the information holding means and output. A software asset management device comprising an analysis means.   The influence range analysis means receives the notification of addition or deletion of the access of creation, deletion or update of the specified data by the module due to the modification of the specified module. The module that performs the access to the data is extracted from the information holding means and output, while the information holding is performed when the notification is a modification only for the addition or deletion of the access to the specified data. The software asset management apparatus according to claim 1, wherein no extraction from means is performed. The information holding means further stores hierarchical relationship information indicating a hierarchical structure of components from the business system to the module,
3. The high-order / low-order relationship analysis means for extracting and outputting the high-order component in the hierarchical structure of the module extracted by the sound range analysis means from the hierarchy relation information. 2. The software asset management device according to item 1.   An access type input unit that extracts the identifier of the data that the module accesses and the access type from the source source program of the module that constitutes the business system, and stores the access type in the information holding unit. The software asset management device according to any one of claims 1 to 3, further comprising: The information holding means;
A software asset management system comprising the software asset management device according to any one of claims 1 to 4. Information holding means for storing an identifier of data accessed by the module and an access type indicating whether the access is created, deleted, updated, or referenced in association with a module constituting a business system See
Software assets for selecting the data to be created, deleted or updated from the data accessed by the specified module, and extracting and outputting the identifier of the module accessing the selected data from the information holding means Management method.   The modification of the specified module causes the access to the specified data when the module receives notification of addition or deletion of the access to create, delete or update the specified data. When a module is extracted from the information holding means and output, and when a notification is received that only corrects the addition or deletion of the access to the specified data, the extraction from the information holding means is not performed. The software asset management method according to claim 6. The information holding means further stores hierarchical relationship information indicating a hierarchical structure of components from the business system to the module,
The software asset management method according to any one of claims 6 to 7, wherein the higher-order component in the hierarchical structure of the module extracted by the sound range analysis means is extracted from the hierarchical relationship information and output.   7. The identifier of the data accessed by the module and the access type are extracted from the source source program of the module constituting the business system, and stored in the information holding unit. 9. The software asset management method according to any one of items 8. Information holding means for storing an identifier of data accessed by the module and an access type indicating whether the access is created, deleted, updated, or referenced in association with a module constituting a business system On a computer connected to
The range of influence in which the data to be created, deleted, or updated is selected from the data accessed by the specified module, and the identifier of the module that accesses the selected data is extracted from the information holding means and output. Software asset management program that executes analysis processing.

Images