JP5197128B2 - Dependency Estimation Device, Dependency Estimation Program, and Recording Medium - Google Patents

Description

  The present invention relates to an inter-product dependency estimation device for estimating a dependency between products in software development.

Conventionally, a user records a dependency relationship between files by manually describing a file name having a correlation (dependency relationship) as setting information in a certain file, and by referring to the setting information, Files that may be affected by changing the target file are listed (Patent Document 1).
JP 2000-47861 A, “Affected Range Detection Device and Affected Range Detection Method”

In the prior art, the user has to manually describe the dependency relationship between files, and thus has the following problems.
(1) There is a possibility that the dependency relationship is not changed when the file contents are changed, and the development is proceeded, so that the reliable dependency relationship cannot be presented to the user.
(2) Since the dependency relationship is directly described in the file, it is deleted by mistake during the file change operation, and the dependency relationship cannot be presented to the user.

  The present invention has been made to solve the above-described problems, and automatically builds and estimates file dependencies, and automatically updates the dependencies as the file contents change. With the goal.

The dependency relationship estimation apparatus according to the present invention includes:
A storage unit for storing data;
Accepts input of product data including the product name that is the name of the product and the product content that is the content of the product, and the user name, and the product that has the same product content as the accepted product content It is determined whether or not the data exists in the storage unit. If it is determined that the data does not exist, a version number that distinguishes the product data having the same product name is given to the accepted product data, and the assigned product data is assigned. A product receiving unit that stores the version number, the received product data, the date information indicating the current date and time, and the change information including the received user name in association with each other;
When the product name is received and the product name is received, the product data having the received product name that is the product name received from the product data stored in the storage unit is specified for each version number. Identify the change information corresponding to each of the deliverable data specified for each version number, and follow the prescribed rules based on the specified change information and other deliverables represented by the accepted deliverable name and other It is characterized by having an accuracy calculation unit for calculating the accuracy of the dependency relationship with the deliverable represented by the deliverable name.

  According to the present invention, it is possible to provide an apparatus that automatically calculates the accuracy of file dependency.

  The inter-product dependency estimation device described in the following embodiment records “change information” and “retrieve information” of a product in software development. For example, the device is generated with a short time difference by the same developer. Estimate that the dependencies between deliverables are high, and present related related deliverables that may be affected to the changeable deliverables to the developer.

Embodiment 1 FIG.
The first embodiment will be described with reference to FIGS.

  FIG. 1 is a diagram illustrating an example of an appearance of a product dependency estimation apparatus 1001 realized by a computer. In FIG. 1, the inter-product dependency relationship estimation apparatus 1001 includes a system unit 830, a display apparatus 813 having a CRT (Cathode / Ray / Tube) or LCD (liquid crystal) display screen, and a keyboard 814 (Key / Board: K / B). ), Mouse 815, FDD 817 (Flexible Disk Drive), compact disk device 818 (CDD: Compact Disk Drive), printer device 819, and the like, which are connected by cables and signal lines.

  FIG. 2 is a diagram illustrating an example of hardware resources of the inter-product dependency relationship estimation apparatus 1001 realized by a computer. In FIG. 2, the inter-product dependency relationship estimation apparatus 1001 includes a CPU 810 (also called a central processing unit: a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program. The CPU 810 is connected to a ROM (Read Only Memory) 811, a RAM (Random Access Memory) 812, a display device 813, a keyboard 814, a mouse 815, a communication board 816, an FDD 817, a CDD 818, a printer device 819, and a magnetic disk device 820 via a bus 825. And control these hardware devices. Instead of the magnetic disk device 820, a storage device such as an optical disk device or a flash memory may be used.

  The RAM 812 is an example of a volatile memory. Storage media such as the ROM 811, the FDD 817, the CDD 818, and the magnetic disk device 820 are examples of nonvolatile memories. These are examples of a storage device or a storage unit, a storage unit, and a buffer. The communication board 816, the keyboard 814, the FDD 817, and the like are examples of an input unit and an input device. The communication board 816, the display device 813, the printer device 819, and the like are examples of an output unit and an output device.

  The communication board 816 is connected to a network (such as a LAN). The communication board 816 may be connected not only to the LAN but also to a WAN (wide area network) such as the Internet or ISDN.

  The magnetic disk device 820 stores an operating system 821 (OS), a window system 822, a program group 823, and a file group 824. The programs in the program group 823 are executed by the CPU 810, the operating system 821, and the window system 822.

  The program group 823 stores a program for executing a function described as “unit” in the description of the embodiment described below. The program is read and executed by the CPU 810.

  The file group 824 includes “determination result”, “calculation result”, “extraction result”, “generation result”, and “processing result” in the description of the embodiment described below. Information, data, signal values, variable values, parameters, and the like are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 810 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, output, printing, and display. Information, data, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory during the CPU operations of extraction, search, reference, comparison, operation, calculation, processing, output, printing, and display. Is remembered.

  In the description of the embodiments described below, data and signal values are stored in RAM 812 memory, FDD 817 flexible disk, CDD 818 compact disk, magnetic disk device 820 magnetic disk, other optical disks, mini disks, DVD (Digital). -It records on recording media, such as Versatile and Disk. Data and signals are transmitted on-line via the bus 825, signal lines, cables, and other transmission media.

  Further, in the description of the embodiments described below, what is described as “to part” may be “means”, “to circuit”, and “to device”, and “to step” and “to”. “Procedure” and “˜Process” may be used. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 811. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 810 and executed by the CPU 810. That is, the program causes the computer to function as “to part” described below. Alternatively, the procedure or method of “to part” described below is executed by a computer.

  FIG. 3 is a block diagram of the inter-product dependency relationship estimation apparatus 1001 according to the first embodiment. The inter-product dependency relationship estimation apparatus 1001 includes an input unit 10, a file reception unit 20, a storage unit 30, a changed part input unit 40, an influence range detection unit 50, and an output unit 60. The influence range detection unit 50 includes an accuracy calculation unit 51 and an influence destination file detection unit 52.

(1) The input unit 10 receives input from the user.
(2) The file receiving unit 20 receives the input file (file name, file content) and user name, and registers them in the storage unit 30 as a file and change information (user name, change time, etc.).
(3) The storage unit 30 holds version-managed files, file change information, and organization table data.
(4) The changed part input unit 40 specifies a file to be changed.
(5) The influence range detection unit 50 is performed by the influence destination file detection unit 52 and the accuracy calculation unit 51. The accuracy calculation unit 51 calculates the accuracy of dependency between files based on the change information. The affected file detection unit 52 acquires change information corresponding to the input file name from the storage unit 30, calculates the accuracy using the accuracy calculation unit 51, and outputs an affected file and a list of the accuracy to the output unit 60. To pass.
(6) The output unit 60 displays a list of affected file names and their accuracy to the user.

Next, storage data held in the storage unit 30 will be described. FIG. 4 is a UML (Unified Modeling Language) class diagram showing the data structure of stored data held in the storage unit 30.
(1) The file 111 records unit data for managing the history.
(2) The version 112 is data for managing the history of file contents. A new version is created each time it is changed. Multiple versions can exist for one file. Has a file name for access in a version. The file name is unique for all files at a given time.
(3) The file content 113 records the content of a file in a certain version.
(4) A user 114 who has an authority to access the storage unit 30 is recorded and is identified by a user name.
(5) In the team 115, a development team that is a group of users is recorded as system chart data, and the team is configured by a user or a team.
(6) The change information 116 records who has changed to the contents of a certain version.

  The connection between these data indicates that data from one side can be referred to the other. The data structure shown in FIG. 4 is an example. When a file ID is used instead of recording a file name, a file and a version are recorded as one data, a change content is recorded in change information, The case where the team is not recorded can be considered, but in any case, the present embodiment is essentially applicable.

  Next, the operation will be described.

(Processing of the file reception unit 20)
FIG. 5 is a UML activity diagram showing the processing procedure of the file reception unit 20.
(Step 1.) The file reception unit 20 receives an input of a file (file name, file content) and a user name via the input unit 10.
(Step 2.) The file reception unit 20 acquires the current date and time as the change date and time in order to record the change information. The current date and time is obtained from, for example, an OS (Operating System).
(Step 3.) The file receiving unit 20 generates change information including the user name and the change date and time.
(Step 4.) The file receiving unit 20 compares the file content of the file stored in the storage unit 30 with the file content of the input file.
(Step 5.) When the file contents are the same, the file receiving unit 20 ends the process. If the file contents are different, the process proceeds to step 6.
(Step 6.) The file receiving unit 20 registers the file (file name, file content) and the change information in the storage unit 30. Further, at the time of registration, a version number and a file ID for distinguishing the contents of files having the same file name are assigned. The file receiving unit 20 stores the version number, the received file (file name, file content), and the change information in the storage unit 30 in association with each other.

FIG. 6 is a diagram illustrating, for example, the state of the storage unit 30 at a certain point of time in a UML object diagram. FIG. 6 shows a state where no file is registered yet. In FIG. 6, the project organization table data is recorded in advance, and there are Taro, Jiro, and Saburo as developers. Taro and Jiro belong to the library development team, and the entire project team includes the library development team and Saburo. Indicates that it belongs to.
FIG. 7 shows that from the state of FIG. A state after Java (registered trademark) is registered at 0:00:00 on January 1, 2008 is shown. In FIG. 7, the newly registered file main. Java (registered trademark), version (version number 1), file contents, and change information are recorded, and the change information records that Taro has changed.
FIG. 8 shows that from the state of FIG. The state after changing the contents of Java (registered trademark) at 11:00:01 on January 1, 2008 is shown. In FIG. 8, the file main. A new version (version number 2), contents, and change information are recorded in Java (registered trademark), and the change information records that Taro has changed.

(Process of affected file detection unit 52)
FIG. 9 shows the processing procedure of the affected file detection unit 52. In the inter-product dependency estimation apparatus 1001 according to the first embodiment, a file (file name, file content) is received by the file receiving unit 20 and sequentially stored in the storage unit 30, and the input unit 10 and changed portion input In this embodiment, when a file name is input to the affected file detection unit 52 via the unit 40, an accuracy calculation unit 51 described later is activated.
(Step 1.) The affected file detection unit 52 receives an input of a file name via the input unit 10 and the changed part input unit 40.
(Step 2.) The affected file detection unit 52 passes the input file name to the accuracy calculation unit 51, and the dependency relationship between the file represented by the input file name and the file represented by another file name The accuracy is calculated using the accuracy calculation unit 51.
(Step 3.) The affected file detection unit 52 receives the accuracy of dependency between files from the accuracy calculation unit 51, and uses the input file name as the affected file and other files as the affected file. Further, the accuracy of the dependency relationship is added, and the list is passed to the output unit 60.

(Processing of the accuracy calculation unit 51)
FIG. 10 shows a processing procedure of the accuracy calculation unit 51. As an example, it is assumed that the file name A is input from the affected file detector 52, and the recorded change information is as shown in FIG.
(Step 1.) The accuracy calculation unit 51 searches for and identifies the version having the file name input from the affected file detection unit 52 from the latest version (version number) of the file. Then, change information corresponding to the version is specified. Then, the change information immediately after that is paired. Furthermore, past versions of the same file are tracked, and the change information and the change information immediately after that are paired. For example, if the change information of the file A is specified as shown in FIG. 12, the accuracy calculation unit 51 extracts the change information immediately after it as a pair. As a result, five pairs of (A, B), (A, C), (A, B), (A, D), and (A, B) are extracted.
(Step 2.) The accuracy calculation unit 51 selects only pairs in which the changers corresponding to each change information are the same for the change information pairs. For example, in FIG. 1 and 2 are selected because the changer is taro. On the other hand, the change information No. In 20 and 21, since file A is changed to taro and file D is changed to jiro, they are not selected. The selection result is as shown in FIG.
(Step 3.) The accuracy calculation unit 51 receives the set of selected pairs of change information as input and calculates the accuracy of the dependency relationship using an accuracy function. As the accuracy function, for example, a function called “sum of reciprocals of change time difference (unit: minutes)” so that the accuracy becomes higher as the change time difference is shorter. FIG. 15 shows the output in such a case. In addition, as a method of extracting a pair of change information, as shown in FIG. 16, all files changed between a change of a certain file (A in FIG. 16) and the next change can be used. Various methods other than the method of forming a pair are conceivable.

(Accuracy function variation)
In addition to the accuracy function, various other functions can be considered, including the following.
(1) A function having a change time difference as a parameter, such as “sum of inverse square of change time difference”.
(2) A function having a change amount as a parameter. If the contents are changed drastically, there is a high possibility that the dependency relationship will be changed so far, which is useful when it is necessary to relatively increase the accuracy of the dependency relationship due to the latest change.
(3) A function having the change time as a parameter. This is useful for lowering the dependency when resting or at night.

  In addition, as a method for selecting a pair of change information, there may be a case where another user who belongs to the same team changes the information. In that case, as the accuracy function, a function (such as a weighted sum) having an argument of the accuracy when the same user changes and the accuracy when a different user who belongs to the same team changes can be considered.

  As described above, by calculating the accuracy of the dependency relationship using the change information etc., the dependency relationship can be followed along with the file content change, and the user can delete the dependency relationship by mistake. Can be prevented.

Embodiment 2. FIG.
The second embodiment will be described with reference to FIGS. In the second embodiment, the following functions are added from the first embodiment.
(1) In order to clearly indicate the affected range (a set of files), not only a list of affected files and their accuracy is listed for a certain affected source file (the first embodiment), but also between file sets A function (accuracy calculation unit 51) for calculating the dependency and its accuracy is added. In the second embodiment, the accuracy calculation unit 51 has this function.
(2) In order to intuitively understand the affected file and its accuracy, a function (influence range display unit 201) for listing and visually displaying the affected file and the accuracy is added.
(3) In order to improve the processing time when inquiring the affected file, add a function to save the accuracy calculation result to the affected file. In the second embodiment, the accuracy calculation unit 51 has this function.

FIG. 17 is a block diagram of the inter-product dependency relationship estimation apparatus 1002 according to the second embodiment.
(1) The accuracy calculation unit 51 has substantially the same function as that of the first embodiment, but is activated each time change information is added to the storage unit 30, and the calculated accuracy depends on the dependency relationship in FIG. 111-2) is recorded in the storage unit 30.
(2) The affected file detection unit 52 outputs the affected file and its accuracy to the affected range display unit 201 based on the accuracy of the dependency (111-2) recorded in the storage unit 30.
(3) The influence range display unit 201 processes a list, a chart, a graph, and the like for display regarding the accuracy of the dependency file and the dependency relationship.
(4) Other functions of the inter-product dependency relationship estimation device 1002 are the same as those of the inter-product dependency relationship estimation device 1001 of the first embodiment.

  Next, data held in the storage unit 30 will be described. FIG. 18 shows data held in the storage unit 30. The dependency (111-2) is a record of the accuracy of dependency between files. It has an association with the affected file and the affected file. Other data is the same as in FIG. 2 of the first embodiment.

  Next, the operation will be described.

(Process of affected file detection unit 52)
The processing procedure of the affected file detection unit 52 is shown in FIG. As described above, the accuracy calculation unit 51 is activated each time change information is added to the storage unit 30, and the accuracy of the dependency relationship calculated by the accuracy calculation unit 51 is the dependency relationship (111-2 shown in FIG. ). The following steps are cases where the affected file detection unit 52 accepts a set of file names in this state.
(Step 1.) The affected file detection unit 52 receives an input of a set of file names via the input unit 10 and the changed part input unit 40. The file name set may be a single file name.
(Step 2.) The affected file detection unit 52 receives the dependency data (dependency relationship (111-2)) related to the file having the file name included in the input file name set from the storage unit 30. get.
(Step 3.) The affected file detection unit 52 acquires the accuracy and the affected file from the acquired dependency data. Here, it is also possible to recursively acquire the affected file, such as a file that further affects the affected file.
(Step 4.) The affected file detection unit 52 sets the affected file, affected file, and accuracy as one set, and outputs the set.

(Processing of the influence range display unit 201)
The processing procedure of the influence range display unit 201 is shown in FIG. As an example, assume that the data output from the affected file detector 52 is as shown in FIG.
(Step 1.) The influence range display unit 201 distributes processing according to an output format. The output format can be specified by input from the input unit 10 or by specifying it as setting information in the storage unit 30.
(Step 2.) The influence range display unit 201 converts the list into a list format and outputs it. Examples of output when only one file name is given and when a plurality of file names are given are shown in FIGS. 22 and 23, respectively.
(Step 3.) The influence range display unit 201 converts the graph into a graph format and outputs it. The file is expressed by a node, the dependency is expressed by an edge, and the edge emphasis level (including the case where the edge is not displayed) is changed and displayed according to the accuracy. Examples of output when only one file name is given and when a plurality of file names are given are shown in FIGS. 24 and 25, respectively.
(Step 4.) The influence range display unit 201 converts it into a chart format and outputs it. Set and display the influence source file, the influence destination file, and the accuracy for the axis. Examples of output when only one file name is given and when a plurality of file names are given are shown in FIGS. 26 and 27, respectively.

  As described above, by updating the accuracy of dependency each time change information or the like in the storage unit 30 is changed, it is possible to prevent a decrease in efficiency when examining the affected file, and between a plurality of files and By visually displaying the accuracy of the dependency relationship, it is possible to visually grasp the influence range and the accuracy of the dependency relationship.

Embodiment 3 FIG.
The third embodiment will be described with reference to FIGS. In the third embodiment, in order to be able to estimate the dependency relationship more reliable than in the second embodiment, information when the file is extracted is recorded as the extraction information, and the dependency relationship is estimated together with the change information.

FIG. 28 shows a block diagram of the inter-product dependency relationship estimation apparatus 1003 of the third embodiment.
(1) The accuracy calculation unit 51 calculates and records the accuracy of dependency between files based on the access information (including both the above-described change information and extraction information described later). The accuracy calculation unit 51 is activated every time the access information in the storage unit 30 is changed.
(2) The file retrieval unit 301 retrieves a file from the storage unit 30 and records the file name, user name, and retrieval date / time of the retrieved file as retrieval information.
(3) Other functions are the same as those in the inter-product dependency estimation device 1002 of the second embodiment.

  Next, data held in the storage unit 30 will be described. FIG. 29 shows data held in the storage unit 30. In the extraction information (118-3), the name of the user who extracted the file, the date and time, and the file name of the extracted file are recorded. Other data is the same as in FIG. 18 of the second embodiment.

  Next, the operation will be described.

(Processing of file retrieval unit 301)
FIG. 30 shows a processing procedure of the file retrieval unit 301.
(Step 1.) The file retrieval unit 301 receives input of a file retrieval condition and a user name via the input unit 10.
(Step 2.) The file retrieval unit 301 acquires a file satisfying the condition from the storage unit 30.
(Step 3.) The file extraction unit 301 records the acquired file (file name), user name, and extraction time (current time) in the storage unit 30 as extraction information.
(Step 4) The extracted file is transferred to the output unit 60.

(Processing of the accuracy calculation unit 51)
The processing procedure of the accuracy calculation unit 51 is shown in FIG. In FIG. 31, the change information of FIG. 10 is access information.
(Step 1.) The accuracy calculation unit 51 extracts the access information corresponding to the file name and the access information immediately after that as a pair.
(Step 2.) The accuracy calculation unit 51 selects only the pair in which both operators (changer or viewer) have the same access information pair.
(Step 3.) The accuracy calculation unit 51 calculates the accuracy using an accuracy function. The same thing as the accuracy calculation unit 51 in the first embodiment can be considered in various ways in the access information pair extraction method, the accuracy function, and the access information pair selection method in the third embodiment. Furthermore, the access information pair extraction method is for some or all cases of (change information, change information), (change information, extraction information), (removal information, change information), (removal information, extraction information). It is also possible to extract pairs. Similarly, regarding the accuracy function, it is conceivable to set an individual accuracy function according to the type of pair to be extracted.

  As described above, by recording the extraction information when the file is extracted, it is possible to record the dependency relationship when creating another file while looking at one file, and to increase the reliability of the dependency relationship. it can.

Embodiment 4 FIG.
The fourth embodiment will be described with reference to FIGS. The fourth embodiment aims to improve the development work efficiency of the user by presenting only those having high dependency relationships to the user. Therefore, a function (dependency relationship estimation unit 401) for estimating the presence or absence of the dependency relationship from the accuracy is added.

  FIG. 32 is a block diagram illustrating the inter-product dependency relationship estimation apparatus 1004 according to the fourth embodiment. The dependency relationship estimation unit 401 statistically estimates the presence / absence of a dependency relationship from the set of dependency relationship accuracy, and outputs only the affected file estimated to have a dependency relationship. Other functions are the same as those in the third embodiment.

  The data held in the storage unit 30 is the same as in the third embodiment.

  Next, the operation will be described.

(Processing of dependency estimation unit 401)
FIG. 33 shows a processing procedure of the dependency relationship estimation unit 401. As an example, it is assumed that an input as shown in FIG.
(Step 1.) The dependency relationship estimation unit 401 divides the dependency relationship set into units to be estimated. For example, as a division method, all input sets, the case where the influence source files are the same (FIG. 34), the case where the influence destination files are the same (FIG. 35), and the like can be considered. As a method for specifying the unit to be divided, a method of recording in the storage unit 30 or inputting from the input unit 10 can be considered.
(Step 2.) If there is a set of dependency relationships that have not been estimated, the dependency relationship estimation unit 401 proceeds to Step 3. If not, the process ends.
(Step 3.) The dependency relationship estimation unit 401 distributes the presence or absence of the dependency relationship using a statistical method. As a technique to be used, a method of recording in the storage unit 30 or inputting from the input unit 10 can be considered. For example, there is a way of distribution as shown in FIG. In this case, only what is determined to be dependent is output.

The following are examples of statistical methods for allocating the presence or absence of dependencies, and various other estimation methods are conceivable.
(1) Dependency sets are arranged in ascending order of accuracy, and where there is a maximum difference in the accuracy of adjacent boundaries, those with higher accuracy are dependent and those with lower accuracy are dependent. A method to determine that there is no relationship.
(2) Similarly, a method of dividing by an average value, a method of dividing by a mode value, a method of dividing by a median value, and the like.
(3) Similarly, a method of dividing by a boundary value that maximizes the difference between the average values of a set larger than the boundary value and a smaller set.
(4) A method of determining that there is a dependency if the accuracy threshold value set in advance is exceeded, and that there is no dependency if the threshold value is lower.

  As described above, by estimating the presence / absence of a dependency relationship from the accuracy of a set of dependency relationships, it is possible to present only a product having a dependency relationship with high accuracy to the user.

Embodiment 5 FIG.
Next, a fifth embodiment will be described with reference to FIGS. In the fifth embodiment, the dependency between items can be estimated even when a plurality of items are described in one file.

Hereinafter, the “deliverable” is a target whose dependency is defined between the two, for example, a term including the following.
(1) One file.
(2) Items to be grasped for dependency in one file.
(3) An object generated inside the system using a web-based form or the like.
(4) A table in the database and one record in the table.

FIG. 37 is a block diagram illustrating the inter-product dependency relationship estimation apparatus 1005 according to the fifth embodiment.
(1) extracts a product from a file input from the input unit 10.
(2) The shaping unit 502 shapes the product retrieved from the storage unit 30 so that the user can easily edit it, and outputs it to the output unit 60.
(3) Although the file is handled in the fourth embodiment, the fifth embodiment is the same as the fourth embodiment except that the item is handled as a product.

  Next, data held in the storage unit 30 will be described. FIG. 38 shows data held in the storage unit 30. What is handled as a file in the fourth embodiment is the same as that in the fourth embodiment except that a file is handled as a product in the fifth embodiment.

  Next, the operation will be described.

(Processing of the product extraction unit 501)
FIG. 39 shows the processing procedure of the product extraction unit 501.
(Step 1.) The product extraction unit 501 receives input of a file (file name, file content) and a user name.
(Step 2.) The product extraction unit 501 extracts a product by applying a product extraction program to the input file. The product extraction program may be recorded in advance in the storage unit 30 or input from the input unit 10.
(Step 3.) The product extraction unit 501 outputs the extracted product and the user name to the product reception unit (20-5). The operation of the product receiving unit (20-5) is the same as that of the file receiving unit 20 of the fourth embodiment.

(Processing of the shaping unit 502)
The processing procedure of the shaping unit 502 is shown in FIG.
(Step 1.) The shaping unit 502 applies a shaping program with the set of retrieved products as an input. The shaping program may be recorded in advance in the storage unit 30 or input from the input unit 10.
(Step 2.) The shaping unit 502 outputs the shaped product set to the output unit 60.

  As described above, when a plurality of items are described in one file, the dependency relationship between the items can be recorded.

Embodiment 6 FIG.
The sixth embodiment will be described with reference to FIGS. In the sixth embodiment, the dependency relationship manually input by the user and the dependency relationship calculated by the system are allowed to coexist, thereby increasing the reliability. Therefore, a function for receiving user input (dependency relationship manual setting unit), a function for reading dependency relationships from documents created by the user for other purposes (dependency relationship extracting unit), and the like are added.

  FIG. 41 is a block diagram of the inter-product dependency relationship estimation apparatus 1006 according to the sixth embodiment.

(1) Deliverable reception unit 20:
The product receiving unit 20 has a function of receiving the input product and user name, registering the product and change information (user name, change time, etc.) in the storage unit 30, and starting the accuracy calculation program 64. Have.
(2) Deliverable unit 301:
The product takeout unit 301 has a function of taking out the product from the storage unit 30, recording the product taken out as extraction information, the user name, and the date and time of extraction, and starting the accuracy calculation program 64.
(3) Dependency manual setting unit 601:
The dependency relationship manual setting unit 601 has a function of recording, in the storage unit 30, the affected product and the affected product and the accuracy between them specified by the user.
(4) Dependency extraction unit 602:
The dependency relationship extraction unit 602 has a function of extracting dependency relationships from project management document data from which dependency relationships can be extracted, and is activated when the project management document data is updated.
(5) Total accuracy calculator (51-6):
The overall accuracy calculation unit (51-6) calculates the overall accuracy based on the accuracy calculated by various accuracy calculation programs 64 (various accuracy calculation programs stored in the storage unit 30 as described below). Has the function to calculate. Other functions are the same as those in the fifth embodiment. As the project management document data from which the dependency relationship can be extracted, for example, there are the following trouble report and change request table.

(1) Disability notification form:
The failure communication form is a document in which a detected failure and a deliverable that needs to be changed to repair the failure are recorded.
(2) Change request form:
The change request form records a product that needs to be changed by another development team with respect to a product changed by a certain development team.

  Next, data held in the storage unit 30 will be described. FIG. 42 shows data held in the storage unit 30.

(1) Accuracy calculation program 64:
The accuracy calculation program 64 is a program for calculating or setting the accuracy between deliverables. For example, (a) a program executed by the dependency relationship manual setting unit 601 and (b) a program executed by the dependency relationship extraction unit 602 shown in the functional configuration diagram of the sixth embodiment,
(C) The program executed by the overall accuracy calculation unit (51-6) is applicable. Further, the program executed by the accuracy calculation unit 51 in (d) of the fifth embodiment is also applicable. Other,
(E) Various programs are conceivable, including a program that calculates the degree of similarity between deliverables using words that appear in the deliverables and outputs them as the accuracy of dependency.

* In the accuracy calculation program 64 of FIG. 42, whether or not the accuracy calculation program 64 is activated when a product is changed is executed when the product in the storage unit 30 is changed via the product acceptance unit 20. The presence / absence of setting is determined in consideration of the power accuracy calculation program 64. For example,
Accuracy calculation program 64 of (a), (b) and (c) above
Does not need to be started when changing,
The programs (d) and (e) need to be activated when they are changed.

Similarly, in the accuracy calculation program 64 of FIG. 42, whether or not the accuracy calculation program 64 is activated when a product is taken out is determined when the product in the storage unit 30 is taken out via the product take-out unit 301. The presence / absence of the setting is determined in consideration of the accuracy calculation program 64 to be executed. For example, the accuracy calculation program 64 (a), (b), (c), and (e) does not need to be activated at the time of reading, but (d) requires activation at the time of reading.

(2) Dependency 63:
In the dependency relationship 63 of FIG. 42, the dependency relationship between deliverables is recorded. In addition to the accuracy, record the date and time of the calculation and whether it is a dependency to be fixed. One dependency is recorded for each set of the influence source product, the influence destination product, the accuracy calculation program 64, and the calculated date and time.

* In the calculated date and time, the date and time when the accuracy calculation program 64 outputs the accuracy is recorded. The data may be recorded for the purpose of calculating the total accuracy in consideration of the possibility that the manually set date and time may be recorded and the maintenance may not be performed with time.

  * It is data for artificially setting that there is a dependency regardless of the accuracy of the dependency, whether the dependency should be fixed. This data is recorded for the purpose of, for example, manually determining the dependency after conducting a detailed investigation of the dependency between deliverables.

(1) Documents to be changed:
The change target description document is a document in which a product (for example, a file) to be changed is described in the project management document data. For example, the change target description document A includes information that the file X, the file Y, and the file Z are files that need to be changed.
(2) Dependency description document:
The dependency description document is a document in which the impact source product and the impact target product are described in the document data for project management. The dependency relationship description document B includes, for example, information that the file X is an influence source and the file Y is an influence destination. Other data is the same as in the fifth embodiment.

  FIG. 43 is a diagram for explaining the main operation of the sixth embodiment. FIG. 44 is a diagram for explaining processing of a change target description document according to the sixth embodiment. First, a description will be given with reference to FIG.

(1) The product receiving unit 20 receives input of product data including a product name that is the name of a product and product content that is the content of the product. The product receiving unit 20 determines whether or not product data having the same product content as the received product content exists in the storage unit 30 as in the case of the first embodiment or the fifth embodiment. When the product receiving unit 20 determines that the product does not exist, the product receiving unit 20 assigns a version number for distinguishing product data having the same product name to the received product data, and the assigned version number, the received product data, Are stored in the storage unit 30 in association with each other. FIG. 43 shows a state in which the product data X1 (version number 1), product data Y1 (version number 1), and product data Z1 (version number 1) are stored in the storage unit 30.
(2) In addition, the dependency relationship manual setting unit 601 (dependency relationship receiving unit) determines the influence destination affected by the change of the product name of the product data that is the influence source and the product content of the product data of the influence source. The storage unit 30 receives an input of a product name pair consisting of a product name of product data of the product data and a specified pair that is specified in advance, and the accuracy of dependency that is set in advance for the specified pair. To record. FIG. 43 shows a case where the designated pair of the influence source “X” and the influence destination “Y” and the accuracy 3 are received.
(3) The accuracy calculation unit 51 (individual accuracy calculation unit) receives the product name and uses the received product name that is the received product name among the product data stored in the storage unit 30 as an influence source. , Create a pair of product names that are affected by the change of the product content of the product data of the received product name of the received product name of the product data stored in the storage unit 30 Create as a pair. The accuracy calculation unit 51 acquires the received product name from the storage unit 30 or the affected product detection unit 52 every time a product is stored or every time a product is taken out. The acquisition path can be freely set by the implementation. Then, the accuracy calculation unit 51 sets the accuracy of the dependency relationship between the product data having the received product name of the influence source and the product data having the product name of the influence destination for each of the created pairs. By executing the calculation program, each accuracy calculation program is calculated individually. FIG. 43 shows a case where the accuracy calculation unit 51 accepts “deliverable product name = X” as the accepted deliverable product name. When the accuracy calculation unit 51 receives “product name = X”, the accuracy calculation unit 51 uses “X” as an influence source, and the created pair “X, Y”, “ X, Z ". “X, X” is not shown in FIG. 43, but may be created. As shown in FIG. 43, the accuracy calculation unit 51 (individual accuracy calculation unit) uses a plurality of accuracy calculation programs P1 to Pn having different rules for determining the accuracy, and uses “X, Y”, “X, Z”. Calculate the accuracy of the created pair.
(4) The overall accuracy calculation unit (51-6) receives the reception result among the accuracy of each of the created pairs calculated individually by the accuracy calculation unit 51 and the accuracy recorded in the storage unit 30 by the dependency relationship manual setting unit 601. Using the accuracy of the specified pair with the object name as the influence source, the accuracy of the dependency for each created pair is recalculated as the overall accuracy. That is, the total accuracy calculation unit (51-6), for “X, Y”, each accuracy calculated by the accuracy calculation programs P1 to Pn and the specified pair “X → Y” recorded by the dependency relationship manual setting unit 601. = 3 ”is used to calculate the total accuracy of the created pair“ X, Y ”, and the accuracy of the created pair“ X, Z ”is calculated by the accuracy calculation programs P1 to Pn. The total accuracy is calculated from each accuracy.
(5) In addition, the dependency relationship manual setting unit 601 receives input of a specified pair and dependency relationship determination instruction information for instructing determination of the dependency relationship of the specified pair. FIG. 43 shows a case where the dependency relationship manual setting unit 601 receives a specified pair “X, Z” and dependency relationship determination instruction information about the specified pair. The overall accuracy calculation unit (51-6) records the dependency relationship of the specified pair corresponding to the dependency relationship determination instruction information received by the dependency relationship manual setting unit 601 as confirmed, and records it in the storage unit 30. That is, in the case of FIG. 43, the total accuracy calculation unit (51-6) records the dependency relationship of the designated pair “X, Z” in the storage unit 30 as confirmed.

(In the case of documents to be changed)
FIG. 44 shows a case where the product receiving unit 20 receives a change target description document.
(1) In the change target description document, n product names (n is an integer of 2 or more) of product data whose product content is scheduled to be changed are described. FIG. 44 is an example in which two product names “X” and “Y” are described.
(2) On the other hand, the storage unit 30 has _n P _two product name pairs that can be generated from the _n product names described in the change target description document. A pair that is affected by the change of the product content of the original product data, and the accuracy of the dependency set for each pair are stored. For example, in the example of FIG. 44, data “X → Y = 4” and “Y → X = 1” are stored in advance. The file name “X” or the like is a product that is expected to appear in normal program development, and the dependency relationship is stored in the storage unit 30 in advance.
(3) The dependency relationship extraction unit 602 extracts, from the storage unit 30, the accuracy of _n P _two pairs of dependency relationships stored in the storage unit 30. In the example of FIG. 44, the dependency relationship extraction unit 602 extracts information of “X → Y = 4” and “Y → X = 1” from the storage unit 30.
(4) The overall accuracy calculation unit (51-6) selects the name of the received product among the individual accuracy calculated by the accuracy calculation unit 51 and the accuracy recorded in the storage unit 30 by the dependency relationship manual setting unit 601. In addition to the accuracy of the specified pair as the influence source, the overall accuracy for each created pair is recalculated using the accuracy of the dependency relationship extracted by the dependency relationship extraction unit 602. For example, for the created pair “X → Y”, the total accuracy calculation unit (51-6) records “X → Y” recorded as the accuracy of each accuracy calculated from the accuracy calculation programs P1 to Pn and the dependency of the specified pair. The total accuracy is calculated from the accuracy “3” of “= 3” and the accuracy “4” of “X → Y = 4” extracted by the dependency relationship extraction unit 602.

(For dependency description documents)
The case of a dependency description document will be described.
(1) The product receiving unit 20 is a dependency description document in which a pair of an affected product name and an affected product name affected by a change in the product content of the affected product data is described. Is received and stored in the storage unit. For example, a dependency relationship “X → Y” (where X is the name of the affected product and Z is the affected product name) is described.
(2) The storage unit 30 stores a pair described in the dependency relationship description document and the accuracy of the dependency relationship set in the pair. For example, when “X → Y” is described in the dependency relationship description document, the storage unit 30 stores data such as “X → Y = 5”. In this sense, the change target description document and the dependency relationship description document described above set the dependency relationship between deliverables in a so-called “semi-manual” manner.
(3) The dependency relationship extraction unit 602 extracts the accuracy of the pair dependency relationship described in the dependency relationship description document from the storage unit 30. For example, the dependency relationship extraction unit 602 extracts “X → Y = 5” data from the storage unit 30.
(4) The total accuracy calculation unit uses the received product name as an influence source among the accuracy calculated individually by the accuracy calculation unit 51 and the accuracy recorded in the storage unit 30 by the dependency relationship manual setting unit 601. In addition to the accuracy of the specified pair, the overall accuracy for each created pair is recalculated using the accuracy of the dependency relationship extracted by the dependency relationship extraction unit 602.

Next, a specific operation will be described. The processing procedure of the dependency relationship manual setting unit 601 is shown in FIG.
(Step 1.) An input of an influence source product name, an influence target product name, accuracy, and a confirmed dependency relationship is received.
(Step 2.) The dependency is recorded in the storage unit 30.

The processing procedure of the dependency relationship extraction unit 602 is shown in FIG.
(Step 1.) The dependency relationship extraction unit 602 checks the type of the changed document.
(Step 2.) In the case of a document to be changed, the process proceeds to Step 3. In the case of a dependency description document, the process proceeds to Step 4.
(Step 3. Document to be changed)
Extract the target product from the target document. To extract, the program to be extracted is recorded in the storage unit 30 in advance and executed.
(Step 4) The mutual dependency relation is recorded in the storage unit 30 for the extracted change target product. The numerical value of the accuracy to be recorded and whether or not the dependency to be determined is recorded in the storage unit 30 in advance. When the change target description document A includes information that the files X, Y, and Z need to be changed as in the above-described example, the dependency extraction unit 602 determines that “X (influence source) → Y (influence destination)”. , “Y → X”, “Y → Z”, “Z → Y”, “Z → X”, “X → Z”, ( ₃ P ₂ ) accuracy of dependency, and accuracy determined for each Whether or not information is recorded. The dependency between two files and the accuracy thereof are set in the storage unit 30 in advance. That is, when the change target file X, Y, Z is described in the change target description document A, the dependency relationship extraction unit 602 determines the dependency relationship such as “X → Y” already set in the storage unit 30. Search and get the accuracy of. In this sense, dependency is set to “semi-manual”.
(Step 5. Dependency description document)
Extract the affected product and the affected product from the dependency description document. To extract, the program to be extracted is recorded in the storage unit 30 in advance and executed.
(Step 6.) The dependency relationship (accuracy and information on whether or not the dependency relationship should be determined) between the affected source product and the affected product is recorded in the storage unit 30. The numerical value of the accuracy to be recorded and whether or not the dependency to be determined is recorded in the storage unit 30 in advance. When the dependency relationship description document B includes the dependency relationship “X → Y” as in the above example, the dependency relationship extraction unit 602 determines that the dependency relationship “X → Y” is already stored in the storage unit 30. The accuracy of the relationship is acquired, and the accuracy of “X → Y” is recorded in the storage unit 30.

  The processing procedure of the product receiving unit 20 is shown in FIG. Steps 1 to 6 are the same as those in the fifth embodiment. In step 7, among the accuracy calculation programs recorded in the storage unit 30, all the accuracy calculation programs 64 recorded when activated when activated are activated.

  The processing procedure of the product takeout unit 301 is shown in FIG. Steps 1 to 3 and step 5 are the same as steps 1 to 4 in the fifth embodiment. In step 4, among the accuracy calculation programs 64 recorded in the storage unit 30, all the accuracy calculation programs 64 that are recorded when activated when the deliverables are taken out are activated.

The processing procedure of the total accuracy calculation unit (51-6) is shown in FIG. The total accuracy calculation unit (51-6) is activated upon detection that the accuracy of the dependency relationship calculated by the various accuracy calculation programs 64 has been updated.
(Step 1.) The latest dependency relationship is extracted for each accuracy calculation program 64 other than the overall accuracy calculation unit (51-6) for the set of the influence source product and the influence target product.
(Step 2.) When the dependency relationship to be determined is included for each set of the influence source product and the influence target product, the process proceeds to Step 3. If not included, the process proceeds to step 4.
(Step 3.) Since it is clearly stated that the dependency is to be confirmed, it is recorded in the storage unit 30 as the dependency to be confirmed.
(Step 4.) Based on the accuracy calculated by the various accuracy calculation programs 64, the overall accuracy is calculated using the overall accuracy function. Various types of total accuracy functions are conceivable, including “the sum of the accuracy weighted by the elapsed time from the accuracy calculation date and time”.
(Step 5.) The calculated total accuracy is recorded in the storage unit 30 as a dependency by the total accuracy calculation unit (51-6).

  The processing procedure of the affected product detection unit 52 is shown in FIG. Step 1 and steps 3 to 4 are the same as those in the fifth embodiment. Step 2 obtains, from the storage unit 30, a dependency that is affected only by the product included in the set of product names that are input, only for the dependency recorded by the specified accuracy calculation program 64. When displaying the dependence relationship based on the overall accuracy, the overall accuracy calculation unit (51-6) is designated, and when displaying the dependency relationship recorded by the individual accuracy calculation unit 51, the individual accuracy is displayed. The calculation unit 51 is designated. The calculation unit designation method includes a method of recording in the storage unit 30 in advance or inputting from the input unit 10.

  By doing so, the dependency relationship entered by the user or the dependency relationship described in the document data for project management written by the user is used, or there is a dependency relationship between the deliverables that do not have the dependency relationship. Although there is a relationship, the risk of estimating that there is no dependency between deliverables can be reduced.

  In the first to sixth embodiments described above, a series of operations of each component indicated as “-unit” in the inter-product dependency relationship estimation device are related to each other, and these series of operations are: It can be replaced with processing by a program executed by a computer. By replacing the operation of each component with processing by a program, an embodiment of a “dependency estimation program” can be obtained. In addition, by recording the “dependency estimation program” on a computer-readable recording medium, an embodiment of a computer-readable recording medium on which the program is recorded can be obtained. Further, by grasping a series of operations of each component indicated as “˜part” in the inter-product dependency estimation device as “˜step”, the inter-product dependency estimation device is referred to as a “dependency estimation method”. It is also possible to grasp as.

In the first embodiment described above, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for accepting an input file and user name and registering it as a file and change information.
(3) Means for retaining version-managed files, file change information, and organization table data.
(4) Means for designating a file to be changed.
(5) A means for calculating the accuracy of dependency between files based on the change information.
(6) Means for obtaining change information corresponding to the input file name from the storage means, calculating the accuracy using the accuracy calculation means, and passing the affected file and a list of the accuracy to the output means.
(7) Means for displaying a list of affected file names and their accuracy to the user.

In the above-described second embodiment, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for accepting an input file and user name and registering it as a file and change information.
(3) Means for maintaining version-managed files, file change information, organization table data, and dependency relationships between files.
(4) Means for designating a file to be changed.
(5) Means for calculating and recording the accuracy of dependency between files based on the change information.
(6) A means for outputting the affected file and the accuracy based on the recorded accuracy of the dependency relationship.
(7) Means for processing, for example, a list, a chart, a graph, etc., about the accuracy of the affected file and the dependency relationship.
(8) Means for displaying the affected file name and its accuracy to the user.

In the above-described third embodiment, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for accepting an input file and user name and registering it as a file and change information.
(3) Means for taking out a file and recording the taken out file, user name, and taken out date as takeout information.
(4) Means for retaining version-managed files, file change information, file retrieval information, system table data, and dependency relationships between files.
(5) Means for designating a file to be changed.
(6) Means for calculating and recording the accuracy of dependency between files based on the change information and the extraction information.
(7) A means for outputting the affected file and the accuracy based on the recorded accuracy of the dependency relationship.
(8) Means for processing, for example, a list, a chart, or a graph about the accuracy of the affected file and the dependency relationship.
(9) Means for displaying the affected file name and its accuracy to the user.

In the above-described fourth embodiment, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for accepting an input file and user name and registering it as a file and change information.
(3) Means for taking out a file and recording the taken out file, user name, and taken out date as takeout information.
(4) Means for retaining version-managed files, file change information, file retrieval information, system table data, and dependency relationships between files.
(5) Means for designating a file to be changed.
(6) Means for calculating and recording the accuracy of dependency between files based on the change information and the extraction information.
(7) A means for outputting the affected file and the accuracy based on the recorded accuracy of the dependency relationship.
(8) Means for statistically estimating the presence / absence of a dependency relationship from a set of the affected file and its accuracy, and outputting only the affected file and its accuracy estimated to have a dependency relationship.
(9) Means for processing a list, a chart, a graph, and the like for display regarding the accuracy of the affected file and the dependency relationship.
(10) Means for displaying the affected file name and its accuracy to the user.

In the fifth embodiment described above, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for extracting a product from a file.
(3) Means for receiving the input product and user name and registering them as a product and change information.
(4) Means for taking out the deliverable and recording the take-out product, the user name, and the take-out date and time as take-out information.
(5) Means for maintaining version-managed deliverables, deliverable change information, deliverable extraction information, organization chart data, and dependencies between deliverables.
(6) Means for designating the deliverable to be changed.
(7) Means for calculating and recording the accuracy of dependency between deliverables based on change information and retrieval information.
(8) A means for outputting the affected product and its accuracy based on the recorded accuracy of dependency.
(9) Means for statistically estimating the presence / absence of a dependency from a set of affected products and their accuracy, and outputting only the affected product and its accuracy estimated to have a dependency.
(10) Means for processing, for example, a list, a chart, or a graph for the accuracy of the affected product and the dependency relationship.
(11) Means for displaying the affected product name and its accuracy to the user.
(12) A means for shaping and outputting the product so that the user can easily edit it.

In the above-described sixth embodiment, the inter-product dependency relationship estimation apparatus including the following means has been described.
(1) A means for receiving input from the user.
(2) A means for extracting a product from a file.
(3) Means for receiving the input product and user name and registering them as a product and change information.
(4) Means for taking out the deliverable and recording the take-out product, the user name, and the take-out date and time as take-out information.
(5) Version-managed deliverables, change information of deliverables, take-out information of deliverables, organization chart data, dependency relationships between deliverables, accuracy calculation means for calculating the accuracy of dependency relationships, dependency between deliverables Means for holding a dependency relationship description document in which a relationship is described and a change target description document in which a change target product is described.
(6) Means for designating the deliverable to be changed.
(7) Means for calculating and recording the accuracy of dependency between deliverables based on change information and retrieval information.
(8) A means for outputting the affected product and its accuracy based on the recorded accuracy of dependency.
(9) Means for statistically estimating the presence / absence of a dependency from a set of affected products and their accuracy, and outputting only the affected product and its accuracy estimated to have a dependency.
(10) Means for processing, for example, a list, a chart, or a graph for the accuracy of the affected product and the dependency relationship.
(11) Means for displaying the affected product name and its accuracy to the user.
(12) A means for shaping and outputting the product so that the user can easily edit it.
(13) Means for recording in the storage means the affected product, the affected product, and the accuracy between them specified by the user.
(14) Means for extracting dependency relationships from project management document data from which dependency relationships can be extracted.
(15) A means for calculating the overall accuracy based on the accuracy calculated by various accuracy calculation means.

FIG. 3 is a diagram illustrating an example of an appearance of an inter-product dependency relationship estimation apparatus according to Embodiment 1; FIG. 3 is an example of a hardware configuration of the inter-product dependency relationship estimation apparatus according to Embodiment 1. FIG. 2 is a block diagram of an inter-product dependency relationship estimation apparatus 1001 according to Embodiment 1. FIG. 3 is a data structure held in the storage unit 30 according to the first embodiment. 5 is a flowchart showing the operation of the file reception unit 20 in the first embodiment. FIG. 4 shows a state of the storage unit 30 in the first embodiment. The figure which shows the state in which the file was registered with respect to FIG. The figure which shows the state in which the file was further registered with respect to FIG. 5 is a flowchart of the operation of an affected file detection unit 52 in the first embodiment. 6 is a flowchart of the operation of the accuracy calculation unit 51 in the first embodiment. FIG. 4 shows a time series of change information in the first embodiment. The figure which shows pairing of FIG. The figure which shows the content of the change information of each pair of FIG. The figure which extracted the pair of the same changer from FIG. FIG. 4 is a diagram showing the accuracy of dependency relationships in the first embodiment. FIG. 6 is a diagram illustrating pairing of change information in the first embodiment. FIG. 10 is a block diagram of an inter-product dependency relationship estimation apparatus 1002 according to Embodiment 2. The data structure hold | maintained at the storage part 30 in Embodiment 2. FIG. 10 is a flowchart of the operation of an affected file detector 52 in the second embodiment. 10 is a flowchart of the operation of the influence range display unit 201 in the second embodiment. An example of the output of the influence destination file detection part 52 in Embodiment 2. FIG. 10 is an output example of a list form of an influence range display unit 201 according to the second embodiment. FIG. 14 is another output example of a list form of the influence range display unit 201 according to the second embodiment. 10 is an output example of a graph format of the influence range display unit 201 according to the second embodiment. FIG. 11 is another output example of the graph format of the influence range display unit 201 according to the second embodiment. 10 is an output example of a chart format of the influence range display unit 201 according to the second embodiment. FIG. 11 is another output example of a chart format of the influence range display unit 201 according to the second embodiment. FIG. 10 is a block diagram of an inter-product dependency relationship estimation apparatus 1003 according to Embodiment 3. 14 is a data structure held in the storage unit 30 according to the third embodiment. 10 is a flowchart of the operation of a file retrieval unit 301 according to the third embodiment. 10 is a flowchart of the operation of the accuracy calculation unit 51 in the third embodiment. FIG. 10 is a block diagram of an inter-product dependency relationship estimation apparatus 1004 according to Embodiment 4. 10 is a flowchart of the operation of the dependency relationship estimation unit 401 in the fourth embodiment. FIG. 20 is a diagram illustrating an example of division by the dependency relationship estimation unit 401 in the fourth embodiment. FIG. 20 is a diagram illustrating another example of division by the dependency relationship estimation unit 401 in the fourth embodiment. An example of the presence / absence of a dependency relationship by the dependency relationship estimation unit 401 according to the fourth embodiment. FIG. 10 is a block diagram of an inter-product dependency relationship estimation apparatus 1005 according to the fifth embodiment. 6 is a data structure held in the storage unit 30 according to the fifth embodiment. 10 is a flowchart of the operation of a product extraction unit 501 according to the fifth embodiment. 10 is a flowchart of the operation of the shaping unit 502 according to the fifth embodiment. FIG. 20 is a block diagram of an inter-product dependency relationship estimation apparatus 1006 according to Embodiment 6. The data structure hold | maintained at the storage part 30 in Embodiment 6. FIG. FIG. 20 is a block diagram illustrating an outline of main operations in a sixth embodiment. FIG. 25 is another block diagram for explaining an outline of main operations in the sixth embodiment. 18 is a flowchart of the operation of the dependency relationship manual setting unit 601 according to the sixth embodiment. 18 is a flowchart of the operation of the dependency relationship extraction unit 602 according to the sixth embodiment. 18 is a flowchart of the operation of a product receiving unit in the sixth embodiment. 20 is a flowchart of the operation of the file retrieval unit 301 in the sixth embodiment. 18 is a flowchart of the operation of the total accuracy calculation unit in the sixth embodiment. 18 is a flowchart of the operation of the affected file detection unit 52 in the sixth embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Input part, 20 File reception part, 30 Storage part, 40 Change part input part, 50 Influence range detection part, 51 Accuracy calculation part, 51-6 Total accuracy calculation part, 52 Influenced file detection part, 60 Output part, 61 Project Management Document, 62 Deliverables, 63 Dependencies, 64 Accuracy Calculation Program, 65th Edition, 66 Deliverables Contents, 67 Retrieve Information, 68 Change Information, 69 Users, 70 Teams, 111 Files, 111-2 Dependencies, 118- 8 Extraction information, 112 version, 113 File contents, 114 users, 115 teams, 116 Change information, 201 Influence range display unit, 301 File extraction unit, 401 Dependency estimation unit, 501 Product extraction unit, 502 Formatting unit, 601 Dependency Manual relationship setting unit, 602 Dependency extraction unit, 1001, 100 , Between 1003,1004,1005,1006 artifacts dependency estimation device.

Claims (11)

A storage unit for storing data;
Accepts input of product data including the product name that is the name of the product and the product content that is the content of the product, and the user name, and the product that has the same product content as the accepted product content It is determined whether or not the data exists in the storage unit. If it is determined that the data does not exist, a version number that distinguishes the product data having the same product name is given to the accepted product data, and the assigned product data is assigned. A product receiving unit that stores the version number, the received product data, the date information indicating the current date and time, and the change information including the received user name in association with each other;
When the product name is received and the product name is received, the product data having the received product name that is the product name received from the product data stored in the storage unit is specified for each version number. Identify the change information corresponding to each of the deliverable data specified for each version number, and follow the prescribed rules based on the specified change information and other deliverables represented by the accepted deliverable name and other A dependency estimation device characterized by comprising an accuracy calculation unit for calculating the accuracy of the dependency relationship with a product represented by a product name. The dependency relationship estimation device further includes:
The product data search condition and the user name are received, the product data corresponding to the search condition is acquired from the storage unit, and the received user name and the product name included in the acquired product data are acquired. And a retrieval unit including the retrieval time indicating the current time, and the product retrieval unit that stores the generated retrieval information in the storage unit in association with the product name included in the acquired product data When,
An output unit that outputs the product data acquired by the product extraction unit;
The accuracy calculator is
When the product name is received and the product name is received, the product data having the received product name that is the product name received from the product data stored in the storage unit is specified for each version number. In addition, the change information corresponding to each of the deliverable data specified for each version number is specified, and the fetch information corresponding to the deliverable data having the accepted deliverable name from the fetch information stored in the storage unit Dependency between the product represented by the received product name and the product represented by the other product name by following predetermined rules based on the specified change information and retrieval information The dependency estimation apparatus according to claim 1, wherein the accuracy of the relationship is calculated. The dependency relationship estimation device further includes:
By inputting the accuracy of the dependency relationship calculated by the accuracy calculation unit, and using the input dependency accuracy, based on a predetermined statistical method, the product represented by the received product name and other The dependency relationship estimation apparatus according to claim 1, further comprising a dependency relationship estimation unit that estimates the presence or absence of a dependency relationship with a product represented by a product name. The accuracy calculator is
4. The processing is executed by starting when a version number, product data, and change information are associated with each other and stored in the storage unit by the product reception unit. The dependence relationship estimation apparatus in any one of. The accuracy calculator is
5. The dependency estimation apparatus according to claim 2, wherein when the extraction information is stored in the storage unit by the product extraction unit, it is activated to execute processing. A computer equipped with a storage unit for storing data (1) Accepts and accepts input of product data including the product name that is the name of the product and the product content that is the content of the product, and the user name Product data having the same product name as the accepted product data is determined if it is determined whether or not the product data of the same product content exists in the storage unit. In addition to assigning a version number for distinguishing between each other, the assigned version number, the accepted product data, the date information indicating the current date and time, and the change information including the accepted user name are associated with each other. Deliverable reception part to be stored in the storage part,
(2) Accept the deliverable name, and when accepting the deliverable name, the deliverable data having the accepted deliverable name, which is the deliverable name received from the deliverable data stored in the storage unit, for each version number Identify the change information corresponding to each of the deliverable data specified for each version number, and based on the specified change information, follow the prescribed rules to deliver the product represented by the accepted deliverable name An accuracy calculation unit that calculates the accuracy of the dependency between the product and the product represented by other product name,
Dependency estimation program characterized by functioning as   A computer-readable recording medium on which the dependency relationship estimation program according to claim 6 is recorded. A storage unit for storing data;
The input of the product data including the product name that is the name of the product and the product content that is the content of the product is received, and the product data having the same product content as the received product content is stored in the storage unit. If it is determined that it does not exist, a version number that distinguishes product data having the same product name from each other is assigned to the accepted product data, and the assigned version number and acceptance A product receiving unit that stores the stored product data in the storage unit in association with each other,
A product name pair consisting of the product name of the product data of the influence source and the product name of the product data of the affected product data affected by the change of the product content of the product data of the influence source A dependency receiving unit that receives an input of a specified pair specified in advance and the accuracy of the dependency relationship set in advance for the specified pair, and records the input in the storage unit;
The product name is received and the product data of the product data stored in the storage unit is received with the received product name being the received product name among the product data stored in the storage unit. Create a pair of product names that are affected by the change in the product content of the product data of the received product name that is the name of the affected source as a created pair, and the received results of the affected source for each created pair Individually calculating the accuracy of the dependency between product data with product names and product data with affected product names by executing multiple accuracy calculation programs. An accuracy calculator,
Created by using each accuracy calculated individually by the individual accuracy calculation unit and the accuracy of the specified pair whose influence is the received product name among the accuracy recorded in the storage unit by the dependency receiving unit A dependency estimation apparatus comprising: an overall accuracy calculation unit that recalculates the accuracy of dependency for each pair as an overall accuracy. The deliverable reception unit
Accept the input of the change target description document in which the product name of the product data scheduled to change the product content is described (n is an integer of 2 or more), and store it in the storage unit;
The storage unit
_N P ₂ product name pairs that can be generated from the _n product names described in the document to be changed, one of which is the influence source and the other is the change of the product content of the product data of the influence source Stores the affected pair affected by, and the accuracy of the dependency set for each pair.
The dependency relationship estimation device further includes:
A dependency extraction unit for extracting the accuracy of dependency of _n P _two pairs stored in the storage unit from the storage unit;
The total accuracy calculation unit
In addition to each accuracy calculated individually by the individual accuracy calculation unit and the accuracy of the specified pair having the received product name as an influence source among the accuracy recorded in the storage unit by the dependency receiving unit, 9. The dependency relationship estimation apparatus according to claim 8, wherein the total accuracy for each created pair is recalculated using the dependency relationship accuracy extracted by the dependency relationship extraction unit. The deliverable reception unit
Accepts the input of the dependency description document in which the pair of the affected product name and the affected product name affected by the change in the product content of the affected product data is received and stored in the storage unit And
The storage unit
Stores the pair described in the dependency description document and the accuracy of the dependency set for this pair.
The dependency relationship estimation device further includes:
A dependency extraction unit that extracts the accuracy of the dependency relationship of the pair described in the dependency description document from the storage unit;
The total accuracy calculation unit
In addition to each accuracy calculated individually by the individual accuracy calculation unit and the accuracy of the specified pair having the received product name as an influence source among the accuracy recorded in the storage unit by the dependency receiving unit, 9. The dependency relationship estimation apparatus according to claim 8, wherein the total accuracy for each created pair is recalculated using the dependency relationship accuracy extracted by the dependency relationship extraction unit. The dependency receiving unit is
Accepts the input of the specified pair and the dependency confirmation instruction information for instructing the confirmation of the dependency relationship of this specified pair,
The total accuracy calculation unit
The dependency relationship according to any one of claims 8 to 10, wherein the dependency relationship of the specified pair corresponding to the dependency relationship determination instruction information received by the dependency relationship receiving unit is confirmed and recorded in the storage unit. Estimating device.

Images