JP6482997B2 - Software development support device - Google Patents

Description

  The present invention relates to a technology for supporting software development in a business system or the like. Especially, it is related with the technique for grasping the influence spread of the change of a design document.

In software development, especially large-scale software development such as business systems, a large number of design documents are created. Since complicated dependencies exist between design documents, a change in one design document affects a plurality of design documents. In response to the change, the designer needs to monitor the progress of the design document modification work including the influence on other design documents.
In general, in software development, holding tracking information about the relationship between deliverables and deliverables and using it for grasping and checking the influence spread range is called traceability management.

As an example of a technique related to this traceability management, Patent Literature 1 and Patent Literature 2 are shown.
Patent Document 1 uses a management table for tracking specifications and source codes from requirements and functions, and automatically generates a correction report including correction targets and correction statuses. While maintaining the relationship between the document and the source code, proceed with the correction work without excess or deficiency.
In Patent Document 2, the relationship between design deliverables is managed in units of fine-grained design elements, and additions, deletions, and changes to design elements are monitored and detected, and notification is made to related parties.

JP 2010-266934 A Japanese Patent Application Laid-Open No. 2007-172223

However, with the technique described in the above-mentioned patent document, it is not possible to mechanically make a determination that the modification of another design document that affects the modification is completed with respect to the modification of the design document to be changed.
In addition, only other design documents that have an influence at the time (or immediately before) the design document to be changed are corrected are monitored. The effect of addition / deletion / change to other design documents implemented by a third party after modifying the design document to be changed cannot be considered.

  In order to solve the above-described problem, in the present invention, the design item position and the relationship between design items are used as the starting point for the design item position of the design item to be corrected, and the dependency destination indicated by the relationship between the design items is successively By specifying, the spread range is specified in a chain. At this time, the route may also be specified. More specifically, as the design document format definition information, the design item position and the relationship between the design items are defined, and the influence propagation tracking route is periodically calculated using the design item position and the relationship between the design items. Keep it. When there is a change in the position of a specific design item, the modification status of the design document in the influence spread range is determined based on the change in the tracking path.

  According to the present invention, it is possible to easily and accurately identify the influence spread of the design document change as compared with the conventional case.

The block diagram which shows the example of a software structure in one Embodiment of this invention. The block diagram which shows the hardware structural example in one Embodiment of this invention. The example of the design document (design document storage part) used by one Embodiment of this invention. The example of the design document format definition (design document format definition storage part) used by one Embodiment of this invention. The example of the design information storage part used by one Embodiment of this invention. The example of the trace path | route storage part used by one Embodiment of this invention. The example of the trace path | route analysis result storage part used by one Embodiment of this invention. The example of the processing flow of the design information extraction part in one Embodiment of this invention. The example of the processing flow of the trace path | route acquisition part in one Embodiment of this invention. The example of the processing flow of the trace path | route analysis part in one Embodiment of this invention. The example of the conceptual diagram (before correction) of the trace path | route in one Embodiment of this invention. The example of the conceptual diagram (after correction 1) of the trace path | route in one Embodiment of this invention. The example of the conceptual diagram (after correction 2) of the trace path | route in one Embodiment of this invention. The example of the screen (design document change) of the traceability management support tool in one Embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a block diagram illustrating an example of a software configuration in a system that performs processing according to the present embodiment.
The user of the software development support apparatus 101 (system) stores the created design document in the design document storage unit 111 at an arbitrary timing. Here, the design document follows a design document format defined for each type of design document, and the design document format definition is held in the design document format definition storage unit 112.
The design information extraction unit 121 uses the design document format definition stored in the design document format definition storage unit 112 to extract design information from the design document stored in the design document storage unit 111 using an arbitrary body mig. Store in the storage unit 113.
The trace path acquisition unit uses the design information (113) and the design document format definition (112) to generate a trace path and store it in the trace path storage unit at an arbitrary timing.
The trace path analysis unit detects a difference between trace paths (114) having different storage timings, considers that the design information has changed, and starts monitoring using the design information as a trace base point. When a notification to the designer or a response request occurs during the monitoring process, the notification information is stored in the trace path analysis result notification storage unit 116. In the present embodiment, it is assumed that the trace path analysis result notification storage unit 116 is a database or a file that temporarily stores data. However, direct notification means to an email or a user interface as shown in FIG. You may take it.

FIG. 2 is a block diagram illustrating an example of a hardware configuration in the system of the present embodiment. In other words, various processes described later are executed by calculating with this hardware according to the software shown in FIG.
The software development support environment 201 is installed in a computer including a CPU 202, a memory 203, an external storage device 204, a display device 205, an input device 206, an external medium input / output device 207, a network communication device 208, and the like.
The CPU 202 executes various processes by executing programs stored in the memory 203. The memory 203 functions as a work area for the CPU 202 and stores programs and data necessary for executing the programs.
Here, the program specifically corresponds to the design information extraction unit 121, the trace path acquisition unit 122, and the trace path analysis unit 123, which are element processes of the software development support environment 101.
Specifically, the data includes the design document storage unit 111, the design document format definition storage unit 112, the design information storage unit 113, the trace path storage unit 114, the trace path analysis result storage unit 115, and the trace path analysis. This corresponds to each piece of information stored in the result notification storage unit 116.

The external storage device 204 is a device that permanently stores various data such as a hard disk device, for example. Here, the data stored in the memory 203 may be stored in the external storage device 204, or the data stored in the external storage device 204 may be stored in the memory 203. Each program may be stored in the memory 203 or the external storage device 204 in advance, or may be introduced from another device into the memory 203 or the external storage device 204 via an available medium as necessary. Also good. The medium refers to, for example, a storage medium that can be attached to and detached from the external medium input / output device 207 or a network communication device 208.
The display device 205 is a user interface that displays a processing result of the program such as a display.
The input device 206 is a user interface for inputting processing execution instructions and information necessary for processing, such as a keyboard and a mouse.

The external medium input / output device 207 inputs / outputs data stored in the memory 203 or the external storage device 204 to / from the external medium input / output device 207 that is removable and portable.
The network communication device 208 is an external interface that enables transmission of information to / from the outside by wired / wireless.

FIG. 3 is an example of a design document (code list 301, code specification 302) handled in the present embodiment.
The code list 301 has a single table, and has an item number 311, a code name 312, a code ID 313, a description 314, and the like as columns. The design document type name is included in the header section 321. In the present embodiment, a “single” table is used, but it is only necessary to register the various data described above.

  The code specification 302 is a format having two tables. The upper table (the left column is the header) has the code name 321 and the code ID as rows, and the lower table (the upper row is the header) is the item number 331. , Code value 332, meaning 333, description 334, and the like as columns. Further, the design document type name is included in the header section 322.

  Here, in addition to the table as described above, the design document format can take a single character string, a matrix format table, a tree format table, a tree or graph combining figures, etc. as components. And

FIG. 4 is a “design document format definition” 401 that defines the format of the design document shown in FIG. Here, the code list 301 is the target, and the design document format is defined by the target 411, the design item 412, and the design item link 413.
The target 411 has a design document type name 421 as a name that uniquely represents the type of design document, and “code list” is described in this example.

  The design item 412 is a table that represents a list of design items on the design document format. The table includes a design item 431 that is the name of the design item, a position 432 that indicates a description position (base point) of the design item, and a design item. 431, a configuration pattern 433 indicating a pattern configuring the position 432, and the like.

The design item link 413 is a table that defines a design document (in this example, a code list) that is the target of the design document format definition and a design document (in this example, a code specification) that has a link in traceability. Design item 441 (one of design items 431 of design item 412), link destination design document type 442, link destination design item 443, rule 444 for determining the establishment of a link, and the like. Here, the rule includes conditions for establishing a link with respect to the value A of the link source design item 441 and the value B of the link destination design item 443 (“match” A = B, “mismatch” A ≠ B, “large” FIG. 5 shows an example in which the design information generated by the design information extraction unit 121 and stored in the design information storage unit 113 is expressed in a table format 511. . In this example, it has a design item 501 corresponding to the design item 431 in FIG. 4, a position 502 corresponding to the position 432 in FIG. 4, a value 503 that is a character string that can be acquired from the position 502 of the design document, and the like.

  FIG. 6 is an example 611 in which the trace path generated by the trace path acquisition unit 122 and stored in the trace path storage unit 114 is expressed in a table format. In this example, a route ID 601 that uniquely identifies a trace route, a route 602 that is a list of design documents / design items (in this example, “a1”, “b1”, “c1”... And the like, the date and time 603 that is the date and time when the data is acquired.

FIG. 7 illustrates an example 711 of the trace path analysis result generated by the trace path analysis unit 123 and stored in the trace path analysis result storage unit 115 in a table format. In the present embodiment, a route ID 701 corresponding to the route ID in FIG. 6, a route (1) 702, a date and time (1) 703 corresponding to the route 602 and the date 603 in FIG. (2) 704, date and time (2) 705, status 706 indicating the start status of the route, and the like.
Here, it is possible to have a plurality of sets of routes (N) and dates / times (N) corresponding to the management history. The status indicates the monitoring status of the trace path 701 to be monitored. For example, if the date and time (1) and the date and time (N: latest) are the same, “invariant”, if there is a difference, “difference”, Once the difference occurs in the route, it is “recovered” when it returns to the original state. When the difference is being confirmed for the user via the trace route analysis result notification storage unit 116, “under confirmation”. If you have already obtained an answer, say “Yes”.

FIG. 8 is a processing flow of the design information extraction unit.
First, the system acquires a design document from the design information storage unit 111 (801).
Next, the system acquires the design document format definition 401 corresponding to the design document acquired in the previous step from the design document format definition storage unit 112 (802). Here, the design document type name 421 in the design document format definition storage unit 401 matches the design document names 321 and 322 of the design document.

Next, using the definition of the design item format definition design item 412 acquired in the previous step, the system acquires the design information 501, position 502, and value 503 of the design information stored in the design information storage unit from the design document. (803).
In this process, the design document format definition storage unit 112 may be searched with the design information storage unit 121 as an axis. Conversely, the design information storage unit 121 is searched with the design document format definition storage unit 112 as an axis. May be.

FIG. 9 is a processing flow of the trace route acquisition unit.
First, the system selects a design document format definition 401 from the design document format definition storage unit 112 (901).

  Next, the system acquires design information corresponding to the design document format definition acquired in the previous step from the design information storage unit 113 (902).

Next, the system acquires a row corresponding to the link source design item 441 of the design item link 413 of the design document format definition from the design information acquired in the previous step (903).
Next, the system uses the design information row (design item 501 and value 502) acquired in the previous step as a link source, and the design information corresponding to the link destination design document type 442 and link destination design item 443 of the design item link 413. Is retrieved from the design information storage unit (904).

  Next, the system determines that the link has been established when the design document format definition rule 444 is established for the link destination design information value 502 and the link source design information value 502 that were hit in the previous step search. (905).

Next, the system assigns a route ID 601 to the link established in the previous step, and adds link source design information and link destination design information to the trace route 602. (906)
The steps are repeated until no new link destination is hit, and a trace route 602 is created, and the created date and time 603 is stored (907).
In this process, the design document format definition storage unit 112 may be searched with the design information storage unit 121 as an axis. Conversely, the design information storage unit 121 is searched with the design document format definition storage unit 112 as an axis. May I.

FIG. 10 is a processing flow of the trace path analysis unit in the present embodiment.
First, the system stores the trace path to be monitored in the path ID 701, path (previous) 702, and date (previous) 703 of the trace path analysis result 711 (1001).
Next, the system updates the trace path to be monitored at an arbitrary timing, and stores it in the path (after) 704 and the date and time (after) 705 of the trace path analysis result 711 (1002).

Next, the system updates the status 706 of the trace path analysis result 711 from the change status of the trace path to be monitored (1003).
Here, in the case of a change situation determined to require user confirmation in step 1003, notification information is output to the trace path analysis result notification storage unit 116 (1004).
If the current status is determined to be waiting for a notification response in step 1003, the notification response is acquired from the trace path analysis result notification storage unit 116, and the status is updated based on the notification response (1004).

  FIG. 11 is a conceptual explanatory diagram of the trace path stored in the trace path storage unit 114. Here, there are design document types A to D, and a1, b1,... Indicate units of the design document. Similarly to the trace path 602, the arrow line connecting the units of the design document includes the description of the design item link 413 in the design document format definition, and the values of the design items of the link source 441 and the link destination 443 indicate the rule 444. Indicates that it is satisfied. Here, (1) a1⇒b1⇒c1⇒d1, (2) a1⇒b1⇒c1⇒d2, (3) a1⇒b1⇒c3⇒d3, (4) a1⇒b3 Is established.

FIG. 12 is a conceptual explanatory diagram of a case where the trace path is changed by changing a1 in the monitoring of the design document / design item corresponding to a1 with respect to FIG. Here, the link to the design document / design item b1 is changed to b2 due to the change of a1 (corresponding to the trace paths 1, 2, and 3 described above).
The change from the state of FIG. 11 to the state of FIG. 12 can be monitored from the trace path analysis result storage unit 115, and the status 706 of the trace path analysis result can be mechanically updated by continuing the subsequent audit. .

  FIG. 13 is a conceptual explanation of a case where a new route a1⇒b4⇒c2 occurs after the start of monitoring due to the addition / correction of the design document / design item b4 other than the monitoring target a1 to FIG. FIG. A change from the state of FIG. 11 to the state of FIG. 12 can be monitored from the trace path analysis result storage unit 115. In the monitoring of a1, since the new generation of the path may affect other design documents, the system notifies the user via the trace path analysis result notification storage unit 116.

  FIG. 14 is a screen example of a software development support environment that supports monitoring of the status of response to a design document change in this embodiment. The trace starting point 1411 corresponds to the trace starting point (a1 in FIG. 7) of the path 702 of the trace path analysis result storage unit 115, and the user may specify it using any means, and the system stores design information. The change in the design information stored in the unit 113 or the change in the trace path stored in the trace path storage unit 114 may be detected and mechanically designated. The status 1412 corresponds to the status 706 of the trace path analysis result storage unit 115. A detail 1413 is an operation trigger for the user to confirm the details of the monitoring status of the trace starting point 1411. The design information stored in the design information storage unit 113, the trace path stored in the trace path storage unit 114, and the trace path analysis A user interface that calls the trace path analysis result stored in the result storage unit 115 and the trace path analysis result notification stored in the trace path analysis result notification storage unit 116 in an arbitrary format is called. The answer 1414 is an operation trigger for the user to respond / instruct to a warning via the trace path analysis result notification stored in the trace path analysis result notification storage unit 116, as in the detail 1413.

DESCRIPTION OF SYMBOLS 101 Software development support apparatus 111 Design document storage part 112 Design document format definition storage part 113 Design information storage part 114 Trace path storage part 115 Trace path analysis result storage part 116 Trace path analysis result notification storage part 121 Design information processing part 122 Trace path Acquisition unit 123 Trace path analysis unit

Claims (4)

A software development support device that identifies the modification support status of another design document affected by the change of the design document based on the relationship between the design documents,
Means for associating and holding a position on the design document and a design item;
Means for maintaining the relationship between the design items;
Means for receiving an instruction for one of the design items held in the holding means;
About the designated design item, the design item related to the design item is specified using the relationship held in the holding means, and the design item is further chained using the relationship from the specified design item. Means for obtaining the influence spread range for the designed item as a path that is a sequence of relations between the design items ,
The acquisition means calculates a route before and after the change when the design document is changed, and further compares the route before and after the change with a difference as a result of the comparison. A software development support apparatus comprising: means for specifying an update status of a path; and means for determining a correction response status of another design document that has received a change in the design document based on the update status. The software development support apparatus according to claim 1,
The software development support apparatus further comprises means for recording the update status in time series. In the software development support apparatus according to claim 1 or 2 ,
further,
A means for identifying the route to be monitored;
A software development support apparatus comprising means for acquiring a change made by a third party with respect to a design document related to the identified route to be monitored, and grasping an influence on the route . In the software development support device according to claim 3 ,
further,
Means for sending an inquiry to the user using the software development support device according to the status of the route to be monitored;
A software development support apparatus comprising means for accepting an answer of the user to the inquiry and updating a status of the route to be monitored.

Images