JP2012084030A - Software development support system, software development support program and software development support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system which allows a person in charge of development or trouble correction of a software to efficiently identify correction places and contents when testing the software.SOLUTION: The software development support system includes a registration part, an association part and a display part. The registration part registers deliverbles generated in processes of software development, information on troubles, and information on tests in which a trouble/troubles occurred. The association part identifies a place in a deliverble corresponding to a test in which a trouble/troubles occurred based on the information on tests in which a trouble/troubles occurred and generates association information associating the information on tests in which a trouble/troubles occurred, information on the identified place and the information on troubles. The display part displays the information on troubles, the information on tests in which a trouble/troubles occurred, and the information on the identified place as display items by associating among one another.

Description

  Embodiments described herein relate generally to a technique for supporting software development.

  The software is developed first by defining requirements, and then in the order of design, manufacturing, and testing, and documents and source codes are created in each process. In addition, the larger the development scale, the greater the number of persons in charge of development.

  The following documents are disclosed as related techniques.

JP 2004-252719 A JP 2009-53778 A

  When shortening the development period, the ratio of the defect correction man-hours of the development target software becomes a problem. In addition, when developing using existing software, if a problem occurs with a function outside the scope of development, there are many cases where a person who is not familiar with the function corrects it. Similarly, in large-scale development and short delivery development, the person in charge of developing the function (designer / coding person) and the person in charge of correcting the defect (defect person in charge of the test process) are often different.

  In addition, there may be cases where a document related to a defect is not provided to a defect correction person who is not in charge of development. In this case, the person in charge of defect correction searches for a corresponding part in the corresponding document or source code, and it takes time to correct it. In addition, if there is a discrepancy in the content of the defect or the recognition of the latest specifications between the person in charge of the test and the person in charge of defect correction, the number of defect correction man-hours will increase.

  Also involved in development in the later stages of software development, such as duplication time for multiple people to correct the same problem reported in different expressions, back work time, time for matching between each person in charge, etc. The number of man-hours due to the increase in members increases.

  The embodiments of the present invention have been made to solve the above-described problems, so that when a defect is corrected, a developer or a defect corrector can efficiently specify a correction location and correct correction contents. The purpose is to provide technology that supports the above.

  In order to solve the above-described problem, the software development support system according to the present embodiment includes a registration unit, an association unit, and a display unit. The registration unit registers a product created in the process of developing software, information on a defect, and information on a test in which the defect has occurred. The associating unit identifies the location corresponding to the test in which the failure occurred in the deliverable based on the information on the test in which the failure occurred, information on the test on which the failure occurred, information on the specific location, information on the failure, Create association information that associates. Based on the association information, the display unit displays information relating to the defect, information relating to the test in which the defect has occurred, and information relating to the specific location as display items in association with each other.

It is a functional block diagram showing an example of composition of a software development support system concerning an embodiment. It is a figure which shows an example of the requirement definition document used by embodiment, a design document, and a source code. It is a figure which shows an example of the test specification used by embodiment, and test data. It is a figure which shows an example of the malfunction information used by embodiment. It is a flowchart which shows an example of operation | movement of the correlation information preparation part which concerns on embodiment. It is a figure which shows an example of the association information which the association information creation part which concerns on embodiment produces. It is a figure showing an example of a display of a software development support system concerning an embodiment, and an example of screen transition. It is a figure which shows an example when a disclosed user ID is linked | related with the example of a correspondence between charge and user ID based on embodiment, and correlation information. It is a flowchart which shows the example of a process of the correction | amendment of a source code, and a retest using the edit part which concerns on embodiment, a verification part, and a malfunction information update part. It is a figure which shows an example at the time of a related test item being linked | related with the correlation information which concerns on embodiment.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 shows an example of functional blocks of the software development support system according to the present embodiment. A software development support system 100 includes a keyboard and a mouse that receive information input from a user, a monitor that displays information to the user, and each hardware of a computer having a CPU (Central Processing Unit), a memory, and an HDD (Hard disk drive) The hardware units and the programs installed in advance in the HDD cooperate to implement the functional units shown in FIG.

  The registration unit 1 is an actual file group A (required definition document, design document, test specification document file, source code, and test code) that is a product created in each process in accordance with a user instruction. Test data) and defect information B, which is information related to a defect that occurred during the test, is stored in the storage unit 9. The registration unit 1 includes a defect registration unit 11 that stores the defect information B in the storage unit 9 and a related file registration unit 12 that stores the actual file group A in the storage unit 9. In addition, the registration unit 1 includes an operation unit 13 that supports a user's selection operation such as which file to register in the registration process of the defect registration unit 11 and the related file registration unit 12.

  The association information creation unit 2 includes a requirement definition document, a design document, a test specification, a section number (chapter number, section number), a page number and an identification code stored in the storage unit 9, a step number of the source code, Association information 8 that is information in which the function name is associated with the data in defect information B (for example, test identification code, defect identification code) is created in storage unit 9. The association information creation unit 2 includes an automatic association unit 21 that the software development support system 100 itself associates, a manual association unit 22 that performs association by a manual operation by a user, and a manual association operation unit 23.

  Based on the information associated with the association information 8, the display unit 3 displays, for each defect item, the section number of the document associated with the defect item and the corresponding part of the source code (specifically, the source code file name and function name). However, it may be a step number) in association with each other. The defect-related information list display creation unit 32 of the display unit 3 creates a screen image in which information (for example, a section number and a function name) that can identify a corresponding part such as a document and each source code is associated. The list display screen 31 of the display unit 3 displays the created screen images as a list.

  The actual state display unit 4 displays actual data such as a section of the document selected by the user from the display list displayed by the display unit 3, a corresponding portion of the source code, test data, and defect information B. The actual state display unit 4 includes a case where only the means for starting an existing application is provided. The actual state display unit 4 includes an actual state selection operation unit 42 that assists the user in selecting data, acquires items selected from the list display screen, and acquires the corresponding entities from the storage unit 9. A data display screen 41 for displaying the actual data.

  The editing unit 5 has an editing function that assists the user in correcting the source code and the document, and a function of saving the edited data. The editing unit 5 includes a source correction operation unit 51 and a document correction operation unit 52 that support correction of actual data displayed on the actual display screen 41, and an editing result for updating the corrected data into a file. A storage unit 53 is included. These functions may be provided by existing applications.

  The verification unit 6 is a functional unit that performs a test using test data. The verification unit 6 includes an execution module creation unit 61 that compiles and builds a new or modified source code and creates a module file in an executable format, and executes a script in which a manual or execution procedure is defined. A test execution unit 62 that automatically performs a test is included. The verification unit 6 has a user operation unit 63 that inquires of the user which test the failure is to be executed for, acquires permission to execute the test, and displays the test result by the test execution unit 62.

  The defect information update unit 7 updates the defect information B based on the result of the verification performed by the verification unit 6.

  Next, examples of various data used in the present embodiment are shown in FIGS. In the following example, the “information distribution system” is a development target system, and in particular, the “mail transmission function” of the “information distribution system” is described as an example.

  2A shows an example of a requirement definition document, FIG. 2B shows a design document, and FIG. 2C shows an example of source code. An identification code (hereinafter referred to as “ID”) is attached to each of the requirement definition section and the design document section by using a manual or traceability technique. For example, in the case of the “notification function” of the chapter item, IDs of RD0001 and SD01_RD0001 are attached to the requirement definition document and the design document, respectively. Attached to each design document. As shown in FIGS. 2A and 2B, for example, the ID of the chapter “notification function” of the requirement definition document is RD0001, and the ID of the chapter “notification function” of the design document is a code including RD0001. That is, the ID attached to the design document includes the ID attached to the requirement definition document, such as SD01_RD0001.

  In the design document of this embodiment, the actual function name for implementing the function is described after “function name:” (see FIG. 2B). In FIG. 2C, the source code file is not originally assigned a step number, but in FIG. 2C, a step number is assigned for convenience.

  FIG. 3A shows an example of a test specification, and FIG. 3B shows an example of data used when a test is performed. In this example, in the test specification, a new ID: 0009 is assigned to the “mail transmission function”, and the ID “0009-1” is assigned to “send at a predetermined time” of the test item. Yes. Also, in the test specification, for each test, the relevant section number of the requirement definition document, the relevant section number of the design document, and the ID assigned thereto are recorded as information of the related book.

  Further, as shown in FIG. 3B, a folder is created in the storage unit 9 so as to have the same folder name and folder structure as the ID assigned to each item of the test specification, and the test data is stored therein. Stored.

  2 and 3 are information stored in advance in the storage unit 9 by the registration unit 1 before the test is performed, while the defect information illustrated in FIG. 4 is information on a result of the test. The defect information indicates a defect ID, a “defect item” indicating the content of the defect in a short sentence, a “test ID” that is the same ID as the ID described in the test specification, and a simple description of the function name and function. It consists of “Related Item Key”, test results, and details of the test.

  Next, an operation example of the process of associating each document and source code with the software development support system 100 will be described with reference to the flowchart of FIG.

  First, the registration unit 1 acquires defect information B input by the user, and stores this information in the storage unit 9 (S1). The user may manually input the information shown in FIG. 4 from an input form displayed on the monitor, or may create a file in a predetermined format and store it in a predetermined folder. In addition, the registration of the defect information may be automatically generated and registered based on a test result document (a test specification in which pass / fail results are described).

  The association information creation unit 2 acquires a test ID from the defect information B, and based on the test ID, related information (required specification related location, design description location, location of function name of source code, test data, test procedure) And the like, and the association information 8 in which these are associated with the defect ID is created (S2).

  S2 will be described using the data shown in FIGS. 2 to 4 as an example. The association information creation unit 2 searches the test specification with the test ID: 0009-1 in the defect information B, and finds the corresponding section (“ Specify the section and section of “Mail Notification Function”. In addition, the association information creation unit 2 identifies the relevant section number (6.1) and ID (RD000101) in the requirement definition document by referring to the “related books” written in the relevant part of the test specification. Then, the relevant section number (10.1) and ID (SD01_RD000101) in the design document are specified. The association information creation unit 2 further searches the corresponding section in the design document for the characters “function name:”, and the source code file name in which the function is defined, and the corresponding location in the source code file ( Step number) is specified. The test data is specified by the folder name and folder structure in which the test data is stored.

  Next, the association information creating unit 2 associates various information with the related item key in the defect information B (S3). The association information creation unit 2 acquires a related item key from the defect information B, and based on the related item key, related information (requirement specification related location, design document description location, source function name location, test data, test procedure) And the like, and the association information 8 in which these are associated with the defect ID is created.

  S3 will be described using the data shown in FIGS. 2 to 4 as an example. The association information creation unit 2 searches the test specification for a character string of “related item key in the defect information B:“ send at a predetermined time ”from the test specification, and selects the corresponding section (chapter, section of“ email notification function ”). ). In addition, the association information creation unit 2 acquires a character string of “mail transmission function” that is a section name of the section identified from the test specification, and designs the character string of “mail transmission function” in the requirement definition document. Search the book and specify the corresponding section number. The association information creation unit 2 further searches the corresponding section in the design document for the characters “function name:”, and the source code file name in which the function is defined, and the corresponding location in the source code file ( Step number) is specified. The test data is specified by the folder name and folder structure in which the test data is stored.

  The association information creation unit 2 may perform association by both the processes of S2 and S3, or only one of them. Whether to perform both or only one of them can be selected by setting.

  The association information creation unit 2 creates the association information 8 that associates the locations specified by S2 and S3 (S4). FIG. 6 shows an example of the association information. In the association information, for each defect ID, a corresponding part of each document such as a test ID and a corresponding part of the source code are defined. In the present embodiment, the document file name, page number, chapter number (section number), source code file name, and step number are registered in the association information 8 as corresponding portions.

  As described above, the association information creating unit 2 uses the information when the requirement definition document, the design document, the test specification, and the source code are associated with each other manually or by traceability technology. In addition, the association information creation unit 2 detects a related part by performing a full text (all data) search, a chapter search, a key search, etc., from various specifications or specification data for related item keys. The association information creation unit 2 extracts a function name, a class name, and a method name from the design document detected from the related item key, and further associates it with the source code.

  FIG. 7 is an example of a screen displayed by the list display unit 3 and the actual status display unit 4. With reference to FIG. 7, screen transition and display contents by the display unit 3 and the actual state display unit 4 will be described. On the main screen (MG), a plurality of screens such as all project trees (G1) are displayed by the list display unit 3. When the “defect related information list display function” is selected by the user from a menu (not shown) on the main screen (MG), the list display unit 3 displays a defect item list (G2). The defect item list is a list of “defect item” and “defect ID” of defect information B registered in the storage unit 9. When one item in the defect item list (G2) is selected (for example, clicked with the mouse), the list display unit 3 and the entity display unit 4 are selected as G3 based on the association in the association information 8. Display related information corresponding to the defective item. For example, the function name “S_mail ()” is not associated with the association information 8, but can be identified from the file name and step number of the source code, or can be identified from the design document. In addition, all the display items to be listed may be associated in advance. Further, the display format is a hierarchical diagram in the present embodiment, but may be a table format.

  When one of the list information (G3), for example, “S_mail ()” is selected, the actual condition display unit 4 displays the actual condition (G4). The same applies to the document. For example, when “requirement definition location: 6.1” is selected, the actual state display unit 4 identifies the corresponding section from the document file and displays the actual state (G5).

  In addition, before the list display, the list display unit 3 may perform the user authentication and select an item to be displayed according to the user. For example, as shown in FIG. 8A, when a user ID is defined for each person in charge, for example, the association information creating unit 2 states that “the person in charge of the test cannot modify the requirement definition document and view / modify the design document. The disclosed user ID may be associated with the association information 8 as shown in FIG. 8B based on a predefined browsing policy such as “Yes”. That is, the list display unit 3 selects items to be displayed or not to be displayed according to the logged-in user, and displays only a list of items that can be displayed as a selection result. In the example of FIG. 8, the manager, the developer, and the person in charge of the test are divided into users, but the user may be divided according to the function to be developed. Similarly, when a user who is not registered in the “editing user ID” of the association information 8 in FIG. 8B logs in, the editing unit 5 rejects editing for the user. In the example of FIG. 8, the person in charge of the test can view the requirement definition document but cannot edit it. As described above, the editing unit 5 determines whether or not the correction can be made according to the logged-in user based on the correspondence relationship of the association information 8 as shown in FIG. Deny access (edit).

  Next, operations from correction of source code and document to retest will be described with reference to the flowchart of FIG.

  First, the source code or document displayed by the actual status display unit 4 is corrected by the user via the editing unit 5 (S11). When the source code is corrected, the verification unit 6 creates an execution format module of the corrected source code by compiling and building (S12). In the present embodiment, a module can be created from the software development support system 100. In addition, it is possible to select whether to build only the corrected part for the defect or to include the other corrections.

Next, the verification unit 6 sets a test target (test range) according to the user's selection (S13). The verification unit 6 causes the user to select one of the following two items.
1. Test only the modified test items.
2. Test the modified test item and the test items related to the test item.

  Above 1. For example, if the source code is modified, only the source code is tested, and if the design document is modified, the operation is performed according to the modified part, or if the requirement definition document is modified, A test is performed to see if the requirements are met.

  2. The method for identifying the related test items will be described. The verification unit 6 (which may be the association information creation unit 2) specifies a section in the design document corresponding to the test item to be tested (in the example of FIG. 2B, “10.1 Mail transmission function”). ), The higher chapter is specified ("10 notification function" in FIG. 2B). The verifying unit 6 identifies all sections included in the identified higher chapter (in the example of FIG. 2B, “10.2 non-delivery mail check function”), and the corresponding relationship with all the identified sections. A test item is a related test item. As another method, the verification unit 6 may specify other class names, function names, and related keys in the same source code file. The process of specifying the related test item may be performed when the association information creating unit 2 performs the association process. In this case, for example, as shown in FIG. 10, the test ID corresponding to the related test item is held in the association information 8, and the list display unit 3 also displays the related test item in the list (displays it in association). . Moreover, you may make a user designate what kind of related test item is specified.

  The verification unit 6 executes a test for confirming whether the corrected module has a desired operation (S14). While the user confirms the related test specifications, the user may perform the test manually, or if a script with a predefined test procedure is prepared, the test is automatically performed according to the test procedure. May be performed. In addition, when the ID of the test related to the test to be performed is registered in the association information 8 as described above, the verification unit 6 performs the test related to the test to be performed based on the association information 8. Can be implemented by setting.

  When the test is automatically performed, the defect information update unit 7 updates the pass / fail result in the defect information B (S15). The defect information may be manually updated. In addition, when the test is executed manually, the defect information is updated manually.

  The deliverable is created in each step of software development, and is at least one, a part, or all of a requirement definition document, a design document, a source code, a test specification, and test data. Also, in the above description, it is assumed that information related to a defect (failure ID and defect item), information related to a test in which a defect has occurred (test ID), and all deliverables created in each process are associated and displayed as a list. However, for example, the implementation may be such that only the source code or only the design document is displayed in a list.

  In the present embodiment, the association information 8 has been described in which the defect ID and the test ID are registered as information related to the defect and information related to the test in which the defect has occurred. Any information may be used as long as the content of the test is unique. In addition, in the association information 8, the document name (file name), session number, page number, source code file name, and step number of each document are registered as locations corresponding to the test in which the defect occurred in the deliverable. However, any information may be used as long as the information can be specified.

  As described above, in this embodiment, the corresponding part of the deliverable can be displayed in a list in association with the defect item or defect ID, so that the developer or defect corrector can efficiently identify the correction part and the correction content. it can.

  A software development support program that realizes the above-described functions in cooperation with hardware may be stored in a computer-readable recording medium. The computer-readable recording medium includes a disk and a semiconductor memory. The form includes a storage device provided inside the software development support system 100, a storage device provided outside the software development support system 100, a portable recording medium, and a storage device of another computer. For example, when the portable recording medium stores a software development support program and the software development support system 100 has a reader for the portable recording medium, the software development support system 100 reads the software development support program from the recording medium. Also good. Alternatively, when another computer stores the software development support program, the software development support system 100 has a communication interface, and the communication interface is connected to the other computer, the software development support system 100 receives the software from the other computer. You may receive a development support program.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 Registration part, 2 Association information creation part, 3 List display part, 4 Actual condition display part, 5 Editing part, 6 Verification part, 7 Defect information update part, 8 Association information, 9 Storage part, 100 Software development support system.

Claims (10)

A registration unit for registering a product created in the process of developing software, information on a defect, and information on a test in which the defect has occurred;
Based on the information on the test in which the defect has occurred, the location corresponding to the test in which the defect has occurred in the deliverable is identified, information on the test in which the defect has occurred, information on the specific location, and the defect An association unit for creating association information in association with information;
Based on the association information, information relating to the defect, information relating to the test in which the defect has occurred, and information relating to the specific location as display items, respectively, a display unit that displays the associated information,
A software development support system. The software development support system according to claim 1,
The deliverable is one or both of a document and source code created in each process of developing software,
The associating unit is software for creating the associating information by using a session number in the document when the deliverable is a document, and a step number of the source code when the deliverable is source code as information on the specific location. Development support system. The software development support system according to claim 1, further comprising:
An actual display unit that displays actual data corresponding to an item selected from the items displayed by the display unit;
A correction unit that accepts corrections to the actual data displayed by the actual display unit, and stores the actual data after correction;
A software development support system. The software development support system according to claim 3, further comprising:
A software development support system including a verification unit that performs a test in which the defect occurs using the corrected actual data. In the software development support system according to any one of claims 1 to 4,
The association unit further creates association information by associating information about the user,
The display unit further selects, based on the association information, an item to be displayed or not to be displayed according to a user who uses the display unit, and displays the selected item as a list when the item is displayed. In the software development support system according to claim 3 or 4,
The association unit further creates association information by associating information about the user,
The display unit further selects an item to be displayed or not to be displayed according to a user using the display unit based on the association information, and displays only the selected item as a list when displayed.
The actual status display unit displays actual data corresponding to an item selected from the items displayed by the display unit,
The correction unit further determines whether to permit correction of the actual data displayed by the actual display unit according to a user based on the association information. The software development support system according to any one of claims 1 to 6,
The associating unit further specifies information related to the test related to information related to the test in which the defect has occurred, creates information related to the information related to the specified test,
The display unit is a software development support system that further displays, as an item, information related to a test related to information related to the test in which the defect has occurred. In the software development support system according to claim 4,
The associating unit further specifies information related to the test related to information related to the test in which the defect has occurred, creates information related to the information related to the specified test,
The verification unit is a software development support system that further performs a test related to the test in which the defect occurs based on the association information. Store the product created in the process of developing the software, information on the defect, and information on the test in which the defect occurred, in the storage unit,
Based on the information on the test in which the defect has occurred, the location corresponding to the test in which the defect has occurred in the deliverable is identified, information on the test in which the defect has occurred, information on the specific location, and the defect Create association information that associates with information, store it in the storage unit,
Based on the association information, software development for causing a computer to execute a process of displaying information relating to the defect, information relating to the test in which the defect has occurred, and information relating to the specific location as display items in association with each other Support program. Computer
Store the product created in the process of developing the software, information on the defect, and information on the test in which the defect occurred, in the storage unit,
Based on the information on the test in which the defect has occurred, the location corresponding to the test in which the defect has occurred in the deliverable is identified, information on the test in which the defect has occurred, information on the specific location, and the defect Create association information that associates with information, store it in the storage unit,
A software development support method that displays information relating to the defect, information relating to the test in which the defect has occurred, and information relating to the specific location as display items in association with each other based on the association information.

Images