JPH10228396A - Data processor for software inspection - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generate, actually inspect, and manage inspection specifications automatically by generating inspection specification data wherein detailed information regarding the inspection specifications of inspection of software is itemized by functions of the software. SOLUTION: A data processor 1A for software inspection is equipped with an inspection specification data generation part 2 so as to perform data processing for inspecting some software. Then its inspection specification data generation part 2 edits inspection item data by the functions of the software to generate inspection matrix data and also generates inspection specification data on the basis of the generated inspection matrix data. Consequently, the generation of the inspection specifications, actual inspecting process, and management of the inspection specifications can automatically be performed and the burden of the inspection specification data generating operation on an inspecting operator can greatly be reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION

(Table of Contents) Technical Field to which the Invention pertains Prior Art (FIGS. 17 and 18) Problems to be Solved by the Invention Means for Solving the Problems (FIGS. 1 to 3) Embodiments of the Invention (FIG. 4) ~ FIG. 16) Effects of the Invention

[0002]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software inspection data processing apparatus for performing inspection data processing on various software such as computer programs.

[0003]

2. Description of the Related Art Generally, software (computer,
The inspection of the program) is performed based on the inspection specification by creating what is called an inspection specification defining detailed information such as inspection items and inspection contents. Here, this inspection specification is usually created by an inspection operator using a software inspection data processing device such as a personal computer. For example, as shown in FIG. 17, the inspection operator refers to an operation manual 101 (or a function specification) relating to software (system) to be inspected, which is created in advance, and the like, and checks all functions (programs) of the software. Then, identify the commands included in the program)
Inspection specifications (manual) 102 are created by inputting detailed information such as inspection items and inspection contents to the data processing device for each function and associating them (step A1).

[0004] For example, certain software (here, C
Considering a wiring program in an AD system), as shown in FIG. 18, “Edit” (drawing), “Rout”
e "(automatic line drawing)," Add "(line addition)," Info "
"Mation" (drawing assist), "Net" (planned drawing), "Hit" (planned line / check line extraction), "Ch"
In the case where the inspection operator is configured to have commands (functions) such as “eck” (scheduled check) and “List” (list of check lines), the inspection operator sets inspection items (inspection contents) for each of these functions. After defining, an inspection specification as shown in the following Table 1 is finally created.

[0005]

[Table 1]

[0006] Then, the inspection operator refers to the inspection specification document 102 prepared as described above, and inputs the data necessary for actual execution of the inspection to the data processing device (file specification, etc.) to perform the inspection operation. The processing is performed by the processing device (step A2), and the data processing device performs the inspection to generate the inspection log data 103 (step A3). The inspection operator manages the inspection log data 103 for each inspected software (member name management) (step A4), and reuses it for inspection of other software as needed (step A5).

The inspection operator displays on a screen or prints out an inspection execution record (inspection execution status such as completion / incompleteness of inspection for each function) 104 obtained by executing the inspection work in the data processing apparatus. It is also possible to confirm. In other words, in the conventional software inspection work, check management of inspection results and handling of processing results are also required.
As with the preparation of the inspection specifications, each is handled by manual intervention.

[0008]

However, in such a conventional data processing apparatus for software inspection, it is necessary to manually create an inspection specification document defining inspection items and inspection contents and an inspection procedure manual defining inspection methods. Inspection worker), the inspection worker
A great deal of time and effort is required for confirming the contents of inspection items and man-hours for preparing inspection specifications. In addition, such manual intervention greatly increases the possibility of lowering the reliability (inspection quality) of inspection work such as omission of confirmation of inspection items.

Further, in the actual inspection work, the inspection operator manages the inspection specification document 102, the inspection log data 103, the inspection execution record 104 (or the test data) and the like individually using a processing device (for example, a file). management)
Data management becomes very complicated,
This will reduce the efficiency and reliability of the next inspection work.

The present invention has been made in view of such a problem, and can automatically create an inspection specification for a certain software, perform an actual inspection process, and manage the inspection specification without manual operation. It is an object of the present invention to provide a data processing device for software inspection as described above.

[0011]

FIG. 1 is a block diagram showing the principle of the present invention. FIG. 1 shows a software inspection data processing apparatus (hereinafter sometimes simply referred to as "data processing apparatus") 1A according to the present invention. The present invention is configured to perform data processing for inspecting a certain software. In the present invention, an inspection specification data creating unit 2 is provided.

Here, the inspection specification data creating section 2
Based on the inspection item data of the software described above, inspection specification data in which detailed information on an inspection specification when performing an inspection on the software is itemized for each function of the software is created. As a result, the data processing apparatus 1A can automatically generate inspection specification data in which detailed information on the inspection specification is itemized for each function of the software to be inspected without manual operation. ).

The inspection specification data creation unit 2 edits the inspection item data for each function of software to generate inspection matrix data, and an inspection matrix generation processing unit that generates the inspection matrix data. An inspection specification data generation processing unit that generates inspection specification data based on inspection matrix data may be provided.

Thus, in the inspection specification data data creating section 2, the inspection matrix generation processing section generates inspection matrix data in which the above inspection item data is edited for each function of the software. Items can be converted into data without omission, and the inspection specification data generation processing section can reliably generate desired inspection specification data (claim 2).

Further, the above-described inspection specification data creating unit 2
The above-mentioned software may be configured to include an inspection item data extraction unit that extracts inspection item data described in advance as comment data. As a result, the inspection specification data creation unit 2 creates inspection specification data based on the inspection item data described in advance as comment data in the above software, so that the inspection item data for creating the inspection specification data is manually input. Even if not
Inspection specification data can be created automatically (claim 3).

FIG. 2 is a block diagram showing the principle of the present invention. The data processing apparatus 1B for software inspection shown in FIG. 2 comprises an inspection command data creation unit 3 and an inspection execution processing unit 4. Have been. Here, the inspection command data creation unit 3 creates inspection command data for actually performing an inspection on the software based on the inspection item data on the software, and the inspection execution processing unit 4 The above-described software inspection is executed based on the inspection command data created by the inspection command data creation unit 3.

In the data processing apparatus 1B of the present invention configured as described above, the inspection command data creating unit 3 creates inspection command data for actually performing the inspection on the software to be inspected, and based on the inspection command data. Since the inspection execution processing unit 4 actually executes the inspection of the software, the software inspection can be automatically executed even if no inspection execution command is input from the outside (claim 4).

The above-described inspection command data creation unit 3
Is configured to create the inspection command data according to the type of software based on the inspection item data and the inspection command generation data prepared for each type of software. The creation unit 3 can create inspection command data that is optimal for the inspection of the software regardless of the type of the software to be inspected (claim 5).

The inspection command data creating unit 3
Is configured to include an inspection item data extraction unit that extracts inspection item data described in advance as comment data in software, so that inspection command data is generated based on the inspection item data described in advance as comment data in the software. Therefore, the inspection command data can be automatically created even if the inspection item data for creating the inspection command data is not manually input (claim 6).

FIG. 3 is a block diagram showing the principle of the present invention. The data processing device 1C for software inspection according to the present invention shown in FIG. It has a specification data editing / updating unit 7. Here, the inspection specification data creation unit 5
Is to create inspection specification data in which detailed information on inspection specifications when performing inspection on a certain software is itemized for each function of the software. Inspection specification data editing / updating unit 7
The above-described inspection specification data is edited and updated based on information on the inspection result obtained by performing the inspection in the inspection execution processing unit 6.

In the data processing apparatus 1C of the present invention configured as described above, the inspection specification data editing / updating unit 7 is created by the inspection specification data creating unit 5 with the execution of the inspection by the inspection execution processing unit 6. Since the edited inspection specification data is edited and updated based on the information on the inspection result, the information on the inspection result can be reflected on the inspection specification data (claim 7).

For example, if the inspection specification data editing / updating unit 7 is configured to add the information on the above inspection result to the inspection specification data for each function of the software to be inspected, the inspection specification data is referred to. It is possible to easily grasp the information on the inspection result alone (claim 8), acquire the inspection execution information on the execution status of the inspection based on the information on the inspection result, and If the inspection execution information is added to the inspection specification data for each function of the software, the implementation status of the inspection can be easily grasped only by referring to the inspection specification data. 9).

If the data processing apparatus 1C has an inspection specification data management unit for managing inspection specification data edited and updated by the inspection specification data editing / updating unit 7, reference and use of inspection specification data are possible. And the like can be automated (claim 10).

[0024]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 4 is a block diagram showing a configuration of a software inspection data processing apparatus according to an embodiment of the present invention. As shown in FIG. 4, as shown in FIG. 1) an inspection specification / command data creating unit 11, a storage unit 16, an inspection execution processing unit 17, an inspection specification database (DB) editing / updating unit 18; Inspection specification DB management unit 1
9.

Here, the inspection specification / command data creating unit 11 performs the inspection based on the inspection item data of a software to be inspected (hereinafter referred to as “inspected software”).
The inspection specification 23 (inspection specification data: see FIG. 9) and the inspection command data 26 (see FIG. 12) are created. The “inspection specification” is a list of detailed information on the inspection specification when performing an inspection on the software to be inspected, for each function of the software to be inspected. Assume that a wiring program in a CAD system is assumed and detailed inspection specification information is itemized for each function command in the wiring program. “Inspection command data” is command data used during actual inspection work.

For this reason, as shown in FIG. 4, the inspection specification / command data generation unit 11 includes a comment data extraction unit 12, an inspection matrix generation processing unit 13, an inspection specification generation processing unit 14, and an inspection command data generation unit. 15. Here, the comment data extraction unit (inspection item data extraction unit) 12 extracts inspection item data described in advance as comment data in the software to be inspected, and generates inspection matrix generation data 21 (function command data) as shown in FIG. Data list data).

In this embodiment, the following Tables 2 and 3
As shown in the above, the inspection item of each function command is represented by a common word (inspection behavior) as much as possible, and its expression is simplified to define the expression method of the inspection item. Comment data is defined using the defined expression method. It is written in advance on the software to be inspected.

[0028]

[Table 2]

[0029]

[Table 3]

Specifically, for example, as shown in FIG.
Inspection items of “Edit” command = confirmation / execution / method, data in which inspection items are associated with each function command are represented by comment symbols (/ *, * /), data identifiers [two at marks (in FIG. 5, Are written on the software to be inspected as comment data. Therefore, if the comment data extraction unit 12 reads only the data part between the data identifiers in the comment data (data enclosed by the comment symbols), the above-described check matrix generation unit 12 generates the above-described check matrix in a format as shown in FIG. The data 21 can be automatically generated.

The check matrix generation data 2
1 can also be created in the same manner by the inspection operator directly inputting necessary inspection items for each function command while referring to the operation manual of the software to be inspected, the function specification, and the like. Check matrix generation processing unit 1
Numeral 3 edits inspection item data for each function command based on the above-described inspection matrix generation data 21 and generates inspection matrix data 22 (see FIG. 8).
Here, for example, as shown in FIG. 7, a flag ("1") is set in a corresponding item column of the test matrix data 22 'having a tabular format for each function command and test item included in the test matrix generation data 21. By setting “0” in the remaining item columns (undefined inspection items and inspection items not to be inspected), the inspection matrix data 22 as shown in FIG. 8 is finally generated. ing.

It should be noted that the number of inspection item columns in the inspection matrix data 22 can be arbitrarily changed after generation as needed. In addition, the inspection specification generation processing unit 14
Generates the inspection specification 23 as shown in FIG. 9, for example, by totalizing the inspection item data for each function command based on the inspection matrix data 22 generated by the inspection matrix generation processing unit 13. The storage unit 16 stores the inspection specification 23 created by the inspection specification generation processing unit 14 as described above and constructs an inspection specification database (DB).

In addition, the inspection command data creation unit 15
In this embodiment, inspection command data for actually performing the inspection on the software to be inspected is created. In the present embodiment, the inspection matrix data 22 created by the inspection matrix generation processing unit 13 and the control data 24 shown in FIG.
And command data generation data 25 specified by the control data 24 as shown in FIG.
The inspection command data 26 as shown in FIG. 12 is automatically created.

Here, specifically, the control data 24
For example, as shown in FIG. 10, a flag (data indicating the type of software to be inspected) indicating whether the software to be inspected (program) is a batch program or a conversational program, A reference key for designating the command data generation data 25 to be executed is stored.

On the other hand, as shown in FIG. 11, the command data generation data 25 includes software to be inspected (program).
Is a fixed format data necessary for command generation when is a batch program [numerical data (coordinate data)
Data whose data contents are fixed in advance) and coordinate data necessary for command generation in the case of a conversational program.
Generates inspection command data 26 required for actual inspection execution of the software to be inspected from these data. The above coordinate data is a numerical value indicating a wiring position and the like, and uses a data value for a test debug or the like specified in an operation manual or the like or inspection log data obtained by actually performing an inspection work. Created.

Here, specifically, for example, when the software to be inspected is a batch program, a batch program flag is set to ON in the control data 24, and the fixed format data for the batch program is designated. A reference key for setting (for example, file designation) is set, and the inspection command data creation unit 15 selects a necessary data file based on the reference key set in the control data 24, and executes a batch-based process. The inspection command data 26 suitable for executing the inspection of the program is created.

On the other hand, when the software to be inspected is a conversational program, the conversational program flag is set to ON in the control data 24, and a reference key or the like for designating coordinate data for the conversational program is set. The inspection command data creation unit 15 selects the required data file based on the reference key set in the control data 24, and is set interactively (interactively) in the data file. By sequentially inputting data contents such as numerical data, inspection command data 26 suitable for executing an interactive program inspection is created.

That is, the inspection command data creation unit 15
Is to create inspection command data 26 according to the type of software to be inspected, based on the inspection item data and the command data generation data 25 prepared for each type of software to be inspected. . Next, the inspection execution processing unit 17 actually executes the inspection of the software to be inspected based on the inspection command data 26 created by the inspection command data creating unit 15, and the inspection specification DB editing / updating unit. Numeral 18 edits and updates the inspection specification 23 stored in the DB in the storage unit 16 based on information (inspection log data) on the inspection result obtained by performing the inspection in the inspection execution processing unit 17. is there.

Specifically, the inspection specification DB editing / updating unit 18 checks the inspection log data as the inspection result and the inspection specification 2
3 as input, the contents of the items of the inspection specification 23 are checked from the inspection log data, and the editing / updating process of the inspection specification 23 is performed by inputting data for editing / updating control. For example, in the present embodiment, as shown in FIG. 13, the number of inspection log data (processing order: L
01, L02,...) And inspection execution flag data (inspection execution information) indicating inspection execution status such as inspection end / unprocessed / not applicable obtained from inspection log data By inputting the obtained control data 27 and adding the log version number management data as a reference key to the corresponding item of the inspection specification 23, the inspection specification 23 and the actual inspection log data can function as shown in FIG. A new inspection specification 23A linked for each command is created, and inspection execution information is further added to the corresponding item of the inspection specification 23A to finally create an inspection specification 23B as shown in FIG. It has become.

That is, the inspection specification DB editing / updating unit 1
8 adds inspection log data to the inspection specification 23 for each function command of the software to be inspected, acquires inspection execution information on the status of the inspection based on the inspection log data, and The inspection execution information is added to the inspection specification 23.

The inspection specification DB management unit 19 manages the inspection specification 23B newly created by the inspection specification DB editing / updating unit 18. The inspection specification 23B
Various functions such as reference of inspection execution status, management of version numbers of inspection log data, creation of new inspection items, and index (reference) of test data / inspection log data based on the above are realized.

Hereinafter, the operation of the data processing apparatus 1 of the present embodiment configured as described above will be described with reference to FIG. First, as described above with reference to Tables 2 and 3 and FIG. 5, the inspection operator writes the inspection item data for the software to be inspected on the source program 28 of the software to be inspected as comment data together with a data identifier in advance as comment data. (Enclosed by symbols (/ *, * /)) (step S1).

When preparing the inspection specification 23 for the source program 28, the data processing device 1
Then, the comment data extraction unit 12 of the inspection specification / command data creation unit 11 identifies the comment symbol (/ *, * /) and the data identifier in the source program 28, and the part enclosed by the data identifier. The inspection item data is extracted by extracting only the data of (1), and inspection matrix generation data 21 (see FIG. 6) is created (step S2).

The check matrix generation data 2
1 can be created by the inspection operator directly inputting necessary inspection item data for each function command while referring to the operation manual 30 and the like (step S5). Next, the inspection item data 21 extracted by the comment data extraction unit 12 is stored in the inspection matrix generation processing unit 13.
The check matrix generation processing unit 13 sets a flag (see FIG. 7) in a corresponding item column of the check matrix data 22 '(see FIG. 7) having a tabular format for each function command and test item included in the check matrix generation data 21. By setting "1") and setting "0" in the remaining item columns, the inspection matrix data 22 (FIG. 8)
(See step S3), and all inspection items for all function commands are converted into data without omission (step S3).

The check matrix data 22
, The inspection specification generation processing unit 14 automatically creates the inspection specification 23 (see FIG. 9) by totalizing the inspection item data for each function command (step S).
4). Note that the inspection specification 23 created in this way is stored in the storage unit 16 as a DB. As described above, according to the data processing device 1 of the present embodiment, the inspection specification / command data creation unit 11 performs an inspection specification by itemizing detailed information on the inspection specification for each function command in the source program 28. 23 can be automatically created without manual work, so that the burden on the inspection operator of creating the inspection specifications 23 can be greatly reduced.
Can be created very quickly.

At this time, the inspection specification / command data creating section 11 creates the inspection specification 23 based on the inspection item data described in the source program 28 as comment data in advance. Even if the inspection item data for the inspection is not manually input, the inspection specification 23 can be automatically created, and the burden of the operation of creating the inspection specification 23 can be reduced.

Further, the inspection specification / command data creating unit 11 generates inspection matrix data 22 by editing the inspection item data for each function command, thereby converting the inspection items of the source program 28 into data without omission. Since the desired inspection specification 23 is reliably generated, the reliability of the automatically generated inspection specification 23 is greatly improved.

By the way, in the above-described check matrix generation processing unit 13, as described above, the check matrix data 2
2 is generated, the inspection matrix generation data 21 and
The control data 24 (see FIG. 10) and the operation manual 30
Command data generation data 25 created by using a test debug data value specified by the user or the inspection log data obtained by actually performing the inspection work.
(See FIG. 11), the inspection command data 26 (see FIG. 12) necessary for the actual inspection is created according to the type (batch type, conversation type, etc.) of the source program 28 (step S6).

When the inspection command data 26 is given to the inspection execution processing unit 17, the inspection execution processing unit 17
Automatically performs an inspection on the source program 28 based on the inspection command data 26, and generates inspection log data 29 that is information on the inspection result (step S7). Note that this inspection process can also be performed manually by an inspection operator inputting an inspection command while referring to the inspection specification 23, as indicated by the broken line in FIG. 16 (step S7 '). However,
Inspection items that cannot be automatically inspected are handled by this manual inspection.

As described above, according to the data processing device 1 of the present embodiment, the inspection command data creation unit 15 creates the inspection command data 26 for actually performing the inspection on the source program 28, and the inspection command data 2
6 is executed by the inspection execution processing unit 17 based on the source program 2
Since the inspection of Step 8 is actually executed, the inspection can be automatically executed even if no command for executing the inspection is input from the outside. Therefore, the work load at the time of the actual inspection work can be significantly reduced.

In this embodiment, the inspection command data 26 is created according to the type of the source program 28 (batch type, conversation type, etc.).
Inspection command data 26 optimal for the inspection of the source program 28 can be created irrespective of the type of 8. Therefore, even during such an automatic inspection, a correct inspection operation can always be performed.
It has greatly contributed to the improvement of reliability and versatility.

In this case, the inspection command data 26
Similarly to the inspection matrix data 22, the inspection item data for creating the inspection command data 26 is manually input because the inspection item data is created based on the inspection item data described in the source program 28 as comment data in advance. Inspection command data 2 automatically
6 can be created, thereby greatly reducing the work load of the inspection worker during the automatic inspection work.

Next, the inspection log data 29 obtained as described above is used together with the inspection specification 23 to edit and edit the inspection specification DB.
The inspection specification DB editing / updating unit 18 is provided to the updating unit 18.
Then, based on the inspection specification 23, the inspection log data 29, and the control data 27 (see FIG. 13), the editing / updating process of the inspection specification 23 in the DB as described above is performed.

That is, the log version number management data as a reference key set in the control data 27 is stored in the inspection specification 23.
The inspection specification 23A is linked to the actual inspection log data for each function command to create an inspection specification 23A (see FIG. 14). By adding the inspection execution information in the control data 27, the latest inspection specification 23B
(FIG. 15) is created (step S8).

The inspection specification 23B created by the inspection specification DB editing / updating unit 18 is subjected to an editing process (step S9) such as combining the same inspection log data into one. The inspection specification DB management unit 19 manages the inspection specification 23 together with the log data 29 '.
The inspection result data including B is unified, reference of the inspection execution status based on the inspection specification 23B, version management of inspection log data, creation of a new inspection item, index of test data / inspection log data ( (See step S10).

As described above, according to the data processing device 1 of the present embodiment, the inspection specification DB editing / updating unit 18 causes the inspection specification document generation processing unit 14 to execute the inspection by the inspection execution processing unit 17. Since the created inspection specification 23 is edited and updated based on the inspection log data, information on the inspection result can be reflected in the inspection specification 23. Therefore, the inspection specification 23 and the information on the inspection result can be collectively managed, and the inspection operator can obtain necessary information extremely quickly and easily.

More specifically, as shown in FIGS. 14 and 15, log version number management data and inspection execution information are added to the inspection specification 23 for each function command in the source program 28. Can easily ascertain inspection log data, inspection execution status, and the like simply by referring to the inspection specification 23B. In other words, inspection processing, such as confirmation of inspection execution status (inspection progress status), management of inspection log data, management of inspection log data trace (selection of optimal inspection log data at the time of reuse), using inspection specification 23 as a core. Centralized management over all functions is realized.

Therefore, it is possible to easily grasp information on the optimum reusable inspection result,
Efficiency and high reliability at the time of later inspection work can be reliably achieved. In the present embodiment, the inspection specification DB management unit 1
9 automatically automates the management of reference and use of the inspection specification 23B, so that the burden on the inspection operator can be greatly reduced in terms of management of the inspection specification 23B.

In the present embodiment, both the log version number management data and the inspection execution information are added to the inspection specification 23, but only one of them may be added. Further, the data processing device 1 of the present embodiment
Has a storage unit 16 for converting the inspection specification 23 into a DB, but this storage unit 16 is not an essential requirement of the present invention, and the storage unit 16 may be provided externally, for example. Further, the above-described check matrix generation data 21,
When the inspection command data 26 is directly created by the data input by the inspection operator, the comment data extraction unit 12 is not particularly necessary.

Further, the data processing device 1 of the present embodiment
Although the configuration has all of the inspection specification automatic creation function, the automatic inspection execution function, and the inspection specification DB management function, the present invention is not limited to this, and for example, the configuration having only one of the above functions Or a combination of any two of the above functions.

[0061]

As described in detail above, according to the data processing device for software inspection of the present invention, detailed information on the inspection specification is itemized for each function of the software to be inspected by the inspection specification data creating unit. The inspection specification data can be automatically created without manual operation, so that the burden of the inspection worker on the inspection specification data creation work can be significantly reduced, and the inspection specification data can be created very quickly ( Claim 1).

In the above-described inspection specification data creating section,
By generating inspection matrix data in which the above inspection item data is edited for each software function, the inspection items for the software to be inspected can be completely converted into data, and the desired inspection specification data can be reliably generated. In addition, the reliability of the automatically generated inspection specification data can be greatly improved (claim 2).

In the inspection specification data creating section,
Since the inspection specification data can be created based on the inspection item data described in advance as comment data in the above software, even if the inspection item data for creating the inspection specification data is not manually input, the inspection specification data is automatically generated. In addition, the inspection specification data can be created, and the burden of the inspection worker on the inspection specification data creation operation can be reduced.

According to the data processing device for software inspection of the present invention, the inspection command data for actually performing the inspection on the software to be inspected is created by the inspection command data creating section, and based on the inspection command data. Since the inspection execution processing unit actually executes the inspection of the software, the software inspection can be automatically executed even if no command for executing the inspection is input from the outside. Can significantly reduce the work load (claim 4).

The above-described inspection command data generating unit is configured to convert the above-mentioned inspection command data according to the type of software based on the above-mentioned inspection item data and inspection command generation data prepared for each type of software. With such a configuration, the inspection command data creation unit can create the inspection command data most suitable for the inspection of the software regardless of the type of the software to be inspected. At
It is possible to always perform the correct inspection work, which greatly contributes to the improvement of the reliability and versatility of the data processing apparatus.

Further, the inspection command data creating section includes:
Since the inspection command data can be created based on the inspection item data described in advance as comment data in the software to be inspected, even if the inspection item data for creating the inspection command data is not manually input, the inspection command data can be automatically generated. In addition, the inspection command data can be created, whereby the workload of the inspection operator during the automatic inspection operation can be significantly reduced (claim 6).

Further, according to the data processing device for software inspection of the present invention, the inspection specification data editing / updating unit is configured to execute the inspection specification data created by the inspection specification data creating unit in accordance with the execution of the inspection by the inspection execution processing unit. Since the data is edited and updated based on the information on the inspection result, the information on the inspection result can be reflected on the inspection specification data. Therefore, the inspection specification data and the information on the inspection result can be collectively managed, and the inspection operator can obtain necessary information extremely quickly and easily (claim 7). For example, if the above-described inspection specification data editing / updating unit is configured to add information on the above-described inspection result to the inspection specification data for each function of the software to be inspected, the inspection can be performed simply by referring to the inspection specification data. Since information on results can be easily grasped, it is also possible to easily grasp information on optimal reusable test results, thereby improving efficiency in later inspection work. Can be reliably achieved (claim 8).

The inspection specification data editing / updating unit obtains inspection execution information on the execution status of the inspection based on the information on the inspection result, and outputs the inspection execution information for each function of the software to be inspected. Is added to the inspection specification data, the inspection execution status can be easily grasped only by referring to the inspection specification data, so that the inspection work (progress) status can be easily confirmed. Therefore, the efficiency of the inspection work and the high reliability of the inspection work quality can be surely attained (claim 9).

It should be noted that if the data processing apparatus described above has an inspection specification data management unit that manages inspection specification data edited and updated by the inspection specification data editing and updating unit,
Since the management of reference and use of the inspection specification data can be automated, the burden on the inspection worker can be significantly reduced also in the management of the inspection specification data.
0).

[Brief description of the drawings]

FIG. 1 is a principle block diagram of the present invention.

FIG. 2 is a principle block diagram of the present invention.

FIG. 3 is a principle block diagram of the present invention.

FIG. 4 is a block diagram showing a configuration of a data processing device for software inspection as one embodiment of the present invention.

FIG. 5 is a diagram showing an example of inspection item data described in advance in a source program according to the embodiment;

FIG. 6 is a diagram showing an example of test matrix generation data generated by the software test data processing device of the present embodiment.

FIG. 7 is a diagram showing an example of inspection matrix data generated by the software inspection data processing device of the present embodiment.

FIG. 8 is a diagram showing an example of inspection matrix data generated by the software inspection data processing device of the present embodiment.

FIG. 9 is a diagram illustrating an example of an inspection specification generated by the software inspection data processing apparatus according to the embodiment;

FIG. 10 is a diagram illustrating an example of control data (for generating inspection command data) used in the software inspection data processing device of the present embodiment.

FIG. 11 is a diagram showing an example of inspection command data generation data used in the software inspection data processing device of the present embodiment.

FIG. 12 is a diagram illustrating an example of inspection command data generated by the software inspection data processing device of the present embodiment.

FIG. 13 is a diagram illustrating an example of control data (for editing / updating) used in the data processing device for software inspection according to the present embodiment.

FIG. 14 is a diagram illustrating an example of an edited / updated inspection specification generated by the software inspection data processing apparatus according to the embodiment;

FIG. 15 is a diagram illustrating an example of an edited / updated inspection specification generated by the software inspection data processing apparatus according to the embodiment;

FIG. 16 is a diagram for explaining the operation of the data processing device for software inspection of the present embodiment.

FIG. 17 is a diagram for explaining an inspection operation performed by a conventional software inspection data processing device.

FIG. 18: Software to be inspected (wiring program)
It is a figure showing an example of.

[Explanation of symbols]

 1, 1A to 1C Software inspection data processing device 2, 5 Inspection specification data creation unit 3, 15 Inspection command data creation unit 4, 6 Inspection execution processing unit 7 Inspection specification data editing / updating unit 11 Inspection specification / command data creation Unit 12 comment data extraction unit (inspection item data extraction unit) 13 inspection matrix generation processing unit 14 inspection specification document generation processing unit 16 storage unit 17 inspection execution processing unit 18 inspection specification DB editing / updating unit 19 inspection specification DB management unit 21 inspection Matrix generation data 22, 22 'Inspection matrix data 23, 23A, 23B Inspection specification (inspection specification data) 24, 27 Control data 25 Data for command data generation 26 Inspection command data 28 Source program 29 Inspection log data 30 Operation manual

Claims (10)

[Claims] 1. A software inspection data processing device for performing data processing for inspecting certain software, comprising:
Software inspection data, comprising: an inspection specification data creating unit that creates inspection specification data in which detailed information about an inspection specification for performing an inspection on the software is itemized for each function of the software. Processing equipment. 2. An inspection matrix generation processing unit that edits the inspection item data for each function of the software to generate inspection matrix data, and the inspection specification data generation unit generates the inspection matrix data. 2. The software inspection data processing device according to claim 1, further comprising an inspection specification data generation processing unit that generates the inspection specification data based on the inspection matrix data. 3. The inspection specification data creating unit has an inspection item data extracting unit that extracts the inspection item data described in advance as comment data in the software. The data processing device for software inspection according to claim 2. 4. A data processing device for software inspection for performing data processing for inspecting a certain software, comprising:
An inspection command data generating unit for generating inspection command data for actually performing an inspection on the software, and an inspection execution for executing an inspection of the software based on the inspection command data generated by the inspection command data generating unit A data processing device for software inspection, comprising a processing unit. 5. The test command data generating unit, based on the test item data and test command generation data prepared for each type of software, converts the test command data according to the type of software. The data processing device for software inspection according to claim 4, wherein the data processing device is configured to generate the data. 6. The inspection command data creation unit according to claim 4, further comprising an inspection item data extraction unit configured to extract the inspection item data described in the software as comment data in advance. A data processing device for software inspection according to claim 5. 7. A software inspection data processing apparatus for performing data processing for inspecting a certain software, wherein detailed information about an inspection specification at the time of inspecting the software is provided for each function of the software. An inspection specification data creating unit for creating itemized inspection specification data, an inspection execution processing unit for actually performing an inspection on the software, and information on an inspection result obtained by executing the inspection in the inspection execution processing unit Edit the inspection specification data
A data processing device for software inspection, comprising an inspection specification data editing / updating unit to be updated. 8. The inspection specification data editing / updating unit is configured to add information on the inspection result to the inspection specification data for each function of the software. The data processing device for software inspection according to the above. 9. The inspection specification data editing / updating unit acquires inspection execution information on the execution status of the inspection based on the information on the inspection result, and stores the inspection execution information for each function of the software. 8. The apparatus according to claim 7, wherein the apparatus is configured to be added to the inspection specification data.
Or a data processing device for software inspection according to claim 8. 10. An inspection specification data management unit for managing the inspection specification data edited / updated by the inspection specification data editing / updating unit.
The data processing device for software inspection according to claim 9.