JP6300710B2 - Change impact analysis apparatus, change impact analysis method and program - Google Patents

Description

  The present invention relates to a technique for extracting elements and functions that may need to be changed in accordance with changes that occur in software development.

A method of supporting the change impact analysis function for analyzing the effect of the change when a part of the software development product is changed is devised by a computer or the like, and is disclosed in Patent Literature 1 and Patent Literature 2.
In Patent Document 1, a method of analyzing change effects based on traceability between software development products is disclosed. In Patent Document 2, dependency relationships in source code are extracted, and change effects are analyzed based on the information. A method is disclosed.

JP 2006-178511 A JP 2013-003715 A

The method disclosed in Patent Document 1 manages the traceability between software components created from the upstream process to the downstream process of development, and analyzes the change effect of other software components when the software component is changed. It was.
However, the dependency relationships in the source code are not managed, and the software created in the upstream process of development starting from the source code that has a change effect on the other source code due to the source code change and the source code that has the change effect The effect of changes on the components could not be analyzed.
Therefore, when changing software components, it is difficult to extract other software components that may have to be changed under the influence of the change.

In the method disclosed in Patent Document 2, a requirement specification created in an upstream process of development, a test specification created in a downstream process, traceability between source programs, and dependency relationships between call relationships between source programs And analyzed the impact of changes to the requirements specification or test specification, other specifications and the source program when the source program was changed.
However, it was not possible to analyze the impact of changes on the requirement specifications created in the upstream process of development and the test specifications created in the downstream process, starting from the source program that has a change effect.
Therefore, when changing requirement specifications, test specifications, and source programs, extract other requirement specifications, test specifications, and source programs that may have to be changed under the influence. It was difficult.

  The present invention has been made in view of the above, and when there is a change in any of the specification elements constituting the software specification, other specification elements and functions that are affected by the change to the specification element are surely confirmed. The main purpose is to obtain a configuration to be extracted.

The change impact analysis apparatus according to the present invention is:
Specification elements in mutual correspondence between source code including a plurality of specification element information in which a plurality of specification elements constituting a software specification are respectively described and a plurality of functions for realizing the plurality of specification elements And a traceability information storage unit for storing traceability information for associating a specification element and a function corresponding to each other, and
A dependency information storage unit that stores dependency information that associates functions that are in a dependency relationship among the plurality of functions included in the source code;
A change source element receiving unit for receiving a change source element notification for notifying, as a change source element, a specification element to be changed among the plurality of specification elements described in the plurality of specification element information;
The specification element and the function associated with the change source element notified by the change source element notification and the traceability information are extracted, and the function associated with the extracted function and the dependency relationship information is extracted as a dependency function. And a change impact analysis unit that extracts specification elements associated with the extracted dependency function and the traceability information.

  According to this invention, it is possible to analyze the traceability information and the dependency relationship information, and to reliably extract the specification elements and functions that are affected by the change to the change source element. Can be used to improve software quality and improve development efficiency.

2 is a diagram illustrating a configuration example of a change impact analysis apparatus according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a requirement specification in Embodiment 1. FIG. 5 is a diagram illustrating an example of a software design document in Embodiment 1. FIG. 3 is a diagram illustrating an example of source code in Embodiment 1. FIG. 6 is a diagram illustrating an example of a traceability matrix between requirement specifications and software design documents according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a traceability matrix between functions in a software design document and source code in Embodiment 1. FIG. 6 is a diagram illustrating an example of a dependency relationship matrix between functions in source code according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a change impact priority matrix that is input to the change impact analysis apparatus according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a change source element notification input to the change impact analysis apparatus according to Embodiment 1. FIG. FIG. 3 is a diagram showing an algorithm of the change impact analysis apparatus in the first embodiment. FIG. 3 is a diagram showing an algorithm of the change impact analysis apparatus in the first embodiment. It is a figure which shows the Example of the change influence analysis using the change influence analysis apparatus in Embodiment 1. FIG. It is a figure which shows the Example of the change influence analysis using the change influence analysis apparatus in Embodiment 1. FIG. It is a figure which shows the Example of the change influence analysis using the change influence analysis apparatus in Embodiment 1. FIG. It is a figure which shows the Example of the change influence analysis using the change influence analysis apparatus in Embodiment 1. FIG. It is a figure which shows the Example of the change influence analysis using the change influence analysis apparatus in Embodiment 1. FIG. FIG. 3 is a diagram showing an algorithm for change impact analysis calculation in the first embodiment. 6 is a diagram illustrating an example of a change influence destination element output by a change influence analysis apparatus according to Embodiment 1. FIG. 3 is a diagram illustrating a hardware configuration example of a change impact analysis device according to Embodiment 1. FIG.

Embodiments of a change impact analysis apparatus according to the present invention will be described below in detail with reference to the drawings.
Note that the present invention is not limited to the embodiments.

Embodiment 1 FIG.
In the present embodiment, in software development, specification / design changes occur using traceability between software development products such as requirement specifications or software design documents, source code, and function call relationships in the source code. Next, a change impact analysis apparatus will be described in which other required items and design items that may have to be changed along with the change and functions in the source code are extracted and shown to the user.

*** Explanation of configuration ***
FIG. 1 is a block diagram illustrating a configuration example of a change impact analysis apparatus.

  Referring to FIG. 1, a change impact analysis apparatus 100 according to the present exemplary embodiment includes a traceability extraction unit 101, a dependency relationship extraction unit 102, a change impact analysis unit 103, a change impact display unit 104, a change source element notification reception unit 105, and traceability. An information storage unit 301 and a dependency relationship information storage unit 302 are provided.

The traceability extraction unit 101 extracts traceability information between the requirement specification 201, the software design document 202, and the source code 203.
In the requirement specification 201 and the software design document 202, a plurality of specification elements constituting the software specifications are described respectively, and each corresponds to specification element information.
The source code 203 includes a plurality of functions that realize a plurality of specification elements.
The traceability information is information that associates specification elements that are in a mutually corresponding relationship between the requirement specification 201 and software design document 202 that are specification element information and the source code 203, and a specification element and a function that have a corresponding relationship with each other. It is.
The traceability extraction unit 101 extracts the correspondence relationship between the plurality of specification elements of the requirement specification 201 and the software design document 202 and the function of the source code, and generates traceability information.
The generated traceability information is stored in the traceability information storage unit 301.

The dependency relationship extraction unit 102 extracts dependency relationship information between functions in the source code 203.
The dependency relationship information is information for associating functions having a dependency relationship among a plurality of functions included in the source code.
The dependency relationship extraction unit 102 extracts dependency relationships between a plurality of functions in the source code and generates dependency relationship information.
The generated dependency relationship information is stored in the dependency information storage unit 302.

The change source element notification receiving unit 105 receives a change source element notification 401 that notifies a change source element that is a request item or a design item to be changed.
The change source element notification 401 is information for notifying, as a change source element, a specification element to be changed among a plurality of specification elements described in the required specification document 201 and the software design document 202.

The change impact analysis unit 103 extracts the change impact destination element 402 with reference to the change source element notification 401, traceability information, and dependency relationship information.
More specifically, the change impact analysis unit 103 extracts specification elements and functions associated with the change source element notified by the change source element notification 401 and the traceability information.
In addition, the change impact analysis unit 103 extracts a function associated with the extracted function and dependency relationship information as a dependency function, and extracts specification elements associated with the extracted dependency function and traceability information.
The extracted specification element and function become the change influence destination element 402.
Furthermore, the change impact analysis unit 103 determines the priority (change) of the extracted function based on the addition value of the number of times the extracted function is called from another function and the number of times the extracted function refers to the global variable. And the change influence priority of the extracted specification element corresponding to the extracted function.

The change influence display unit 104 displays the change influence destination element 402 extracted by the change influence analysis unit 103 on the display device 501.
That is, the change impact display unit 104 displays the specification elements and functions extracted by the change impact analysis unit 103 on the display device 501.
The change influence display unit 104 displays the specification elements and functions extracted by the change influence analysis unit 103 on the display device 501 together with the change influence priority.

FIG. 2 shows an example of the requirement specification 201.
The request specification 201 has a request ID tag ([R0001] to [R004]) composed of R and a three-digit numerical value for each request item.
In FIG. 2, the request item is a description following the request ID tag, and each request item corresponds to a specification element.
For example, “one LED can be turned on / off” following “[R001]” is a required item (specification element).

FIG. 3 shows an example of the software design document 202.
The software design document 202 has a design ID tag ([D001] to [D004]) composed of D and a three-digit numerical value for each design item.
In FIG. 3, the design item is a description following the design ID tag, and each design item corresponds to a specification element.
For example, “[D001]” followed by “LED lighting process / output 0x01 to LED port” is a design item (specification element).

FIG. 4 shows an example of the source code 203.
The source code 203 has a function ID tag ([C001] to [C007]) composed of C and a three-digit numerical value for each function in the source code.

  The traceability information includes a traceability matrix illustrated in FIG. 5 and a traceability matrix illustrated in FIG.

FIG. 5 shows an example of a traceability matrix between the request ID and the design ID.
The traceability matrix between the request ID and the design ID has the request ID as a row and the design ID as a column. When traceability exists between the request ID and the design ID, the location where the request ID row and the design ID column intersect Is circled.
That is, the traceability matrix of FIG. 5 associates the requirement items and the design items that are in a correspondence relationship by associating the requirement IDs with the design IDs.

FIG. 6 shows an example of a traceability matrix between the design ID and the function ID.
The traceability matrix between a design ID and a function ID has a design ID as a row and a function ID as a column. When traceability exists between a design ID and a function ID, the place where the row of the design ID and the column of the function ID intersect Is circled.
That is, the traceability matrix in FIG. 6 associates design items and functions in a corresponding relationship by associating design IDs with function IDs.

  The dependency relationship information includes a dependency relationship matrix illustrated in FIG. 7 and a change impact priority matrix illustrated in FIG.

FIG. 7 shows an example of a dependency matrix between function IDs.
In the dependency matrix, the function ID of the call destination is a row and the function ID of the call source is a column. When traceability exists between the function IDs, the function ID row of the call destination and the column of the function ID of the call source are Circles at the intersections.
That is, the dependency relationship matrix in FIG. 7 associates functions having dependency relationships by associating function IDs.

FIG. 8 shows an example of a function ID change influence priority matrix.
In the change impact priority matrix, the function ID is a row, and the number of global variables referenced by the function corresponding to the function ID and the number of caller functions of the function are columns.
The change impact priority is the total value of the value described in the caller function column and the value described in the global variable column.

FIG. 9 shows an example of the change source element notification 401.
The change source element notification 401 has all the request IDs and design IDs on the left row. When there is a request ID or design ID to be changed, the right row of the column of the request ID or design ID is circled.

*** Explanation of operation ***
10 and 11 show the change impact analysis algorithm of the change impact analysis unit 103. FIG.
Note that a described in steps S101, S102, and S103, b described in steps S201, S202, and S203, c described in steps S301, S302, and S303, and d described in steps S401, S402, and S403 are ID ( Request ID, design ID, function ID).

In step S101, the change source element notification reception unit 105 receives the change source element notification 401 (change source element reception step), and the change impact analysis unit 103 inputs the change source element notification 401 from the change source element notification reception unit 105. .
As described above, the change source element notification 401 is information indicating a request item or design item to be changed.
Through the processing after step S102, the change impact analysis unit 103 extracts the requirement items, design items, and functions that are affected by the change to the change source element by analyzing traceability information and dependency relationship information (change impact analysis step). .

In steps S102, S103, S104, and S106, the change impact analysis unit 103 sequentially selects a request ID and a design ID with a circle in the right column from the list of change source element notifications 401 input in step S101.
For example, when the change source element notification 401 in FIG. 9 is input, the request ID to be selected is R002.

When the ID selected in step S105 is a request ID, the change impact analysis unit 103 circles the column of the selected request ID from the traceability matrix (FIG. 5) between the request ID and the design ID in step S106. The design ID group of the current row is extracted.
For example, when the selected request ID is R002, design IDs extracted from the traceability matrix of FIG. 5 are D003 and D004 circled in the row of R002 as shown in FIG.

  When the ID selected in step S105 is a design ID, the change impact analysis unit 103 circles the line of the design ID selected in step S202 from the traceability matrix (FIG. 6) between the design ID and the function ID in step S204. The function ID group of the column marked with is extracted.

  In steps S201, S202, S203, and S205, the change impact analysis unit 103 sequentially selects the design ID group extracted in step S106.

In step S204, the change impact analysis unit 103 extracts the function ID of the column in which the row of the selected design ID is circled from the traceability matrix (FIG. 6) between the design ID and the function ID.
For example, when the selected design IDs are D003 and D004, the function IDs extracted from the traceability matrix in FIG. 6 are C003 and C004 in columns with circles in the rows of D003 and D004 as shown in FIG. .

  In steps S301, S302, S303, and S306, the change impact analysis unit 103 sequentially selects all the function ID groups extracted in step S204.

In step S304, the change impact analysis unit 103 extracts a function ID group in a column with a circle in the row of the function ID selected in step S302 from the dependency matrix (FIG. 7) between the function IDs.
For example, when the selected function IDs are C003 and C004, the function IDs to be selected are C003 and C004, and the function IDs extracted from the dependency matrix in FIG. 7 are the rows of C003 and C004 as shown in FIG. Are C005 and C006 in rows with circles.

  In steps S401, S402, S403, and S406, the change impact analysis unit 103 sequentially selects all the function ID groups extracted in step S304.

In step S404, the change impact analysis unit 103 extracts the design ID of the row in which the function ID column selected in step S402 is circled from the traceability matrix between the design ID and the function ID (FIG. 6).
For example, when the selected function IDs are C005 and C006, the design IDs extracted from the traceability matrix of FIG. 6 are D005 and D006 in the rows with circles in the columns of C005 and C006 as shown in FIG. is there.

In step S405, the change impact analysis unit 103 extracts a request ID group in a row with a circle in the design ID column extracted in step S404 from the traceability matrix between the request ID and the design ID.
For example, when the extracted design IDs are D005 and D006, the request ID extracted from the traceability matrix in FIG. 5 is R003 in a row with circles in the columns D005 and D006 as shown in FIG.

In step S501, the change impact analysis unit 103 calculates the change impact priority of the design ID and the request ID from the change impact priority matrix of the function ID.
FIG. 17 shows a change impact priority calculation algorithm.
Note that a described in steps S503, S504, and S505 and b described in steps S510, S511, and S512 are variables for selecting an ID (required ID, design ID, and function ID), respectively.

  The change impact analysis unit 103 inputs the design ID group extracted in step S502, and sequentially selects the input design ID group in steps S503, S504, S505, and S508.

In step S506, the change impact analysis unit 103 extracts the function ID of the column in which the row of the design ID selected in step S504 is circled from the traceability matrix between the design ID and the function ID.
For example, when the selected design ID is D003, the function ID extracted from the traceability matrix of FIG. 6 is C003 in a column circled in the row of D003.

In step S507, the change impact analysis unit 103 sets the change impact priority of the function ID extracted in the change impact priority matrix of the function ID as the change impact priority of the selected design ID, and outputs the change impact priority to the change impact destination element 402. .
For example, if the selected design ID is D003 and the extracted function ID is C003, the change impact priority of C003 is 3 in the change impact priority matrix of FIG. 8, so that the change impact of D003 is as shown in FIG. The priority is 3, which is the same as C003.

  The change impact analysis unit 103 inputs the request ID group extracted in step S509, and sequentially selects the input design ID group in steps S510, S511, S512, and S515.

In step S513, the change impact analysis unit 103 extracts the design ID of the column with a circle in the row of the request ID selected in step S511 from the traceability matrix between the request ID and the design ID.
For example, when the selected request ID is R003, the design ID groups extracted from the traceability matrix in FIG. 5 are D005 and D006 in columns with circles in the row of R003.

In step S514, the change impact analysis unit 103 sets the change impact priority of the design ID group extracted in step 513 as the change impact priority of the selected request ID, and outputs the change impact destination element 402.
For example, when the selected request ID is R003 and the extracted design ID groups are D003 and D004, as shown in FIG. 18, the change impact priority 0 of D005 and the change impact priority 0 of D006 are 0, which is 0 in total. Therefore, the change impact priority of R003 is 0.

In step S601, the change influence destination element 402 in which all request IDs, design IDs, and function ID groups extracted in steps S106, S204, S304, S404, and S405 are arranged in descending order of change influence priority is output.
FIG. 18 shows an example of the change influence destination element 402 to be output. The extracted R003, D003, D004, D005, D006, C003, C004, C005, and C006 are arranged in order of change influence priority.

As a result, when there is a change in the requirement item or design item, other requirement items and design items that may need to be changed due to the change, functions in the source code can be changed. It becomes possible to extract without omission in order.
For example, when the change influence destination element 402 to be output is FIG. 18, IDs of other required items and design items that may need to be changed, and functions in the source code are R003, D003, D004, D005, D006, C003, C004, C005, and C006, and those having a particularly high possibility of change are D003 for a design ID and C003 for a function ID.

*** Explanation of effects ***
As described above, according to the present embodiment, at the stage where a required item or design item is changed, other required items and design items that may have to be changed along with the change can be extracted without omission. Accordingly, it is possible to prevent omissions in changes in software development products such as requirement specifications, software design documents, and source code, which can be used for improving software quality and improving development efficiency.
For this reason, the change impact analysis apparatus according to the present embodiment is useful for the change impact analysis of software development products.

  In the above, the change impact priority is determined based on the addition value of the number of times the extracted function is called from another function and the number of times the extracted function refers to the global variable. The change impact priority may be determined based only on the number of times called from other functions, or the change impact priority may be determined based only on the number of times the function references the global function.

Finally, a hardware configuration example of the change impact analysis apparatus 100 shown in the present embodiment will be described with reference to FIG.
The change impact analysis apparatus 100 is a computer, and each element of the change impact analysis apparatus 100 can be realized by a program.
As a hardware configuration of the change impact analysis apparatus 100, an arithmetic device 901, an external storage device 902, a main storage device 903, a communication device 904, and an input / output device 905 are connected to a bus.

The arithmetic device 901 is a CPU (Central Processing Unit) that executes a program.
The external storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or a hard disk device.
The main storage device 903 is a RAM (Random Access Memory).
The communication device 904 is, for example, a NIC (Network Interface Card).
The input / output device 905 is, for example, a mouse, a keyboard, a display device, or the like.
The display device 501 illustrated in FIG. 1 is a part of the input / output device 905.

The program is normally stored in the external storage device 902, and is loaded into the main storage device 903 and sequentially read into the arithmetic device 901 and executed.
The program is a program that realizes a function described as “unit” shown in FIG.
Further, an operating system (OS) is also stored in the external storage device 902. At least a part of the OS is loaded into the main storage device 903. ”Is executed.
In the description of the present embodiment, “determine”, “determine”, “extract”, “analyze”, “decide”, “select”, “generate”, “calculate”, Information, data, signal values, and variable values indicating the results of the processes described as “set”, “register”, “input”, “output”, etc. are stored in the main storage device 903 as files. Yes.

  Note that the configuration in FIG. 19 is merely an example of the hardware configuration of the change impact analysis apparatus 100, and the hardware configuration of the change impact analysis apparatus 100 is not limited to the configuration illustrated in FIG. There may be.

  Further, the change impact analysis method according to the present invention can be realized by the procedure shown in the present embodiment.

  DESCRIPTION OF SYMBOLS 100 Change impact analysis apparatus, 101 Traceability extraction part, 102 Dependency extraction part, 103 Change impact analysis part, 104 Change impact display part, 105 Change source element notification reception part, 201 Requirements specification, 202 Software design document, 203 Source code , 301 Traceability information storage unit, 302 Dependency information storage unit, 401 Change source element notification, 402 Change influence destination element, 501 Display device.

Claims (10)

Specification elements in mutual correspondence between source code including a plurality of specification element information in which a plurality of specification elements constituting a software specification are respectively described and a plurality of functions for realizing the plurality of specification elements And a traceability information storage unit for storing traceability information for associating a specification element and a function corresponding to each other, and
A dependency information storage unit that stores dependency information that associates functions that are in a dependency relationship among the plurality of functions included in the source code;
A change source element receiving unit for receiving a change source element notification for notifying, as a change source element, a specification element to be changed among the plurality of specification elements described in the plurality of specification element information;
The specification element and the function associated with the change source element notified by the change source element notification and the traceability information are extracted, and the function associated with the extracted function and the dependency relationship information is extracted as a dependency function. And a change impact analysis unit that extracts a specification element associated with the extracted dependency relationship function and the traceability information. The change impact analysis apparatus further includes:
The change impact analysis apparatus according to claim 1, further comprising a change impact display unit that displays specification elements and functions extracted by the change impact analysis unit. The change impact analysis unit
The priority of the extracted function and the priority of the extracted specification element corresponding to the extracted function are determined based on the number of times the extracted function is called from another function. Change impact analysis equipment. The change impact analysis unit
The priority of the extracted function and the priority of the extracted specification element corresponding to the extracted function are determined based on the number of times the extracted function refers to the global variable. Change impact analysis device. The change impact analysis unit
Based on the sum of the number of times the extracted function is called from other functions and the number of times the extracted function references a global variable, the priority of the extracted function is in a correspondence relationship with the extracted function The change impact analysis apparatus according to claim 1, wherein the priority of the extracted specification element is determined. The change impact analysis apparatus further includes:
The change impact analysis apparatus according to claim 3, further comprising a change impact display unit that displays the specification element and the function extracted by the change impact analysis unit together with a priority. The change impact analysis device includes:
A traceability extraction unit that extracts correspondence between the plurality of specification elements of the plurality of specification element information and the plurality of functions of the source code to generate the traceability information;
A dependency extraction unit that extracts dependency relationships between the plurality of functions of the source code and generates the dependency relationship information;
The traceability information storage unit
Storing the traceability information generated by the traceability extraction unit;
The dependency relationship information storage unit
The change impact analysis device according to claim 1, wherein the dependency relationship information generated by the dependency relationship extraction unit is stored. The traceability information storage unit
The plurality of specification element information as a requirement specification and a software design document,
Storing traceability information for associating specification elements and functions corresponding to each other, and specification elements and functions corresponding to each other between the requirement specification and the software design document and the source code;
The change impact analysis unit
The change impact analysis apparatus according to claim 1, wherein at least one of a specification element of the requirement specification and a specification element of the software design document is extracted as a specification element affected by the change to the change source element. Specification elements in mutual correspondence between source code including a plurality of specification element information in which a plurality of specification elements constituting a software specification are respectively described and a plurality of functions for realizing the plurality of specification elements And a traceability information storage unit for storing traceability information for associating a specification element and a function corresponding to each other, and
A change impact analysis method performed by a computer having a dependency relationship information storage unit that stores dependency relationship information that associates functions having a dependency relationship among the plurality of functions included in the source code,
A change source element receiving step for receiving a change source element notification for notifying, as a change source element, a specification element to be changed among the plurality of specification elements described in the plurality of specification element information;
The computer extracts the specification element and the function associated with the traceability information and the change source element notified by the change source element notification, and depends on the function associated with the extracted function and the dependency relationship information. A change impact analysis method comprising: a change impact analysis step for extracting a specification element associated with the extracted dependency relationship function and the traceability information, extracted as a relation function. Specification elements in mutual correspondence between source code including a plurality of specification element information in which a plurality of specification elements constituting a software specification are respectively described and a plurality of functions for realizing the plurality of specification elements And a traceability information storage unit for storing traceability information for associating a specification element and a function corresponding to each other, and
A computer having a dependency relationship information storage unit that stores dependency relationship information for associating functions having a dependency relationship among the plurality of functions included in the source code,
A change source element reception step for receiving a change source element notification for notifying a specification element to be changed among the plurality of specification elements described in the plurality of specification element information as a change source element;
The specification element and the function associated with the change source element notified by the change source element notification and the traceability information are extracted, and the function associated with the extracted function and the dependency relationship information is extracted as a dependency function. And a change impact analysis step of extracting a specification element associated with the extracted dependency function and the traceability information.

Images