JPH03260725A - Check system for soft development execution plan - Google Patents

Abstract

PURPOSE:To check the developed soft with high efficiency by displaying the check list data and the failed instance data corresponding to the items to be checked related with each other on a keyboard display terminal. CONSTITUTION:When a keyboard 5 is operated, a CPU 1 retrieves the check list data corresponding to the check items and the comment data out of a disk file part 2. Then the CPU 1 retrieves the failed instance data corresponding to the check items out of an external image storage medium part 3 and displays it at a display part 6. Thus both data can be displayed related with each other on a keyboard display terminal. Then a check list user can check the developed soft while understanding well the meanings of produced check items. Thus no mischeck is caused at all.

Description

[Detailed Description of the Invention] [Industrial Application Field 1] The present invention relates to an execution plan for a software development project.
In particular, it relates to a software development execution plan checking system that improves the effectiveness of using checklists during execution planning.

[Prior Art] Conventionally, a checklist used for checking this type of software development execution plan uses paper such as a notebook, and check items are manually entered on the paper. Then, software developed by a third party, that is, by a person other than the creator of the check item, is checked in accordance with this check item.

[Problem to be solved by the invention] In the conventional software development execution plan checklist described above, the contents of the check items are usually such that only the creator himself/herself can understand them, and therefore it is difficult for a third party to understand the contents of the check items. The problem is that users have to proceed with checking without understanding the true meaning of these contents, resulting in many missing checks, and as a result, it is not possible to check the developed software efficiently.

[Means for Solving the Problems] In order to solve such problems, the software development execution plan checking system according to the present invention has a system for checking check items by transmitting check item request data from a keyboard/display terminal to a large general-purpose computer. , checklist data corresponding to this check item and failure case data are displayed in association with each other on a keyboard/display terminal.

[When the action check item request data is sent, the checklist data corresponding to this check item and the failure case data are displayed in association with each other on the keyboard/display terminal, and as a result, when checking the developed software, the checklist user can check the created check items with a thorough understanding of their meaning.

[Example] Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram of a software development execution plan checking system according to the present invention. In the figure, 1 is a CPI (large general purpose computer), 2 is a disk file unit (disk file device), 3 is an image external storage medium unit, 4 is a keyboard/display terminal, 5 is a keyboard unit, and 6 is a display unit. .

Next, FIG. 2 is a flowchart explaining the operation of the CPU i of this software development execution plan checking system.

Moreover, FIGS. 3 to 5 are explanatory diagrams for explaining the screens displayed on the display unit 6 when checking this software development execution plan.

The detailed operation of this software development execution plan checking system will be explained based on the flowchart 1 in FIG. 2 and the explanatory diagrams in FIGS. 3 to 5.

First, when the keyboard 5 is operated and check item request data is transmitted, this check item request data is input in step 10. Then, in step 11, a corresponding check item stored in the disk file section 2, that is, check item data (check list data) corresponding to the check item request data, is searched, and then in step 12, this searched check item data is searched. It is displayed on the display unit 6 in the form shown on the display screen of FIG.

Subsequently, in step 13, by operating the keyboard 5, it is determined whether the explanation request key has been pressed. This explanation request key is pressed when the user wants to know the specific reason for checking this check item after the above-mentioned check item data is displayed. And this is "Y"
In this case, in step 14, the disk file section 2
Search for explanatory data corresponding to this check item from
Next, in step 15, this searched explanation data is used as the fourth
It is displayed on the display section 6 in the form shown on the display screen in the figure.

Subsequently, in step 16, by operating the keyboard 5, it is determined whether the failure case request key has been pressed. This failure case request key is pressed when the user wants to know the failure case on which the above check item is based, or the failure case related to this check item. And this is "
If "Y", failure case data corresponding to this check item is searched from the image external storage medium section 3 in step 17, and then in step 18, this searched failure case data is displayed on the display screen of FIG. The information is displayed on the display unit 6 in such a manner that the

Further, when "N" is determined in step 13, that is, when the explanation request key is not pressed, it is determined in step 16 whether the failure case request key is pressed, and in step 16, "
If the answer is "N", the process returns to step 10 and the next check item request data is input.

As explained above, this software development execution plan checking system can display the check items, check reasons, and failure cases in association with each other on the display section 6, so that the checklist user can check the checklist creator when checking the developed software. This has the effect of being able to fully understand the meaning of the check items created by the user and checking them, thereby reducing the number of omissions.

[Effects of the Invention] As explained above, the software development execution plan checking system of the present invention, when check item request data is transmitted, associates the checklist data corresponding to this check item with the failure case data and uses the keyboard. Since it is configured to be displayed on a display terminal, when checking the developed software, the checklist user can fully understand the meaning of the created check items and proceed with the check. This has the effect of contributing to improving the quality of the software that is created.

[Brief explanation of drawings]

Figure 1 is a block diagram showing an embodiment of the software development execution plan checking system of the present invention, Figure 2 is a flowchart explaining the operation of this system, and Figures 3 to 5 explain the display state of this system. FIG. 1...CPU, 2...Disk file section, 3
... Image external storage medium section, 4. Keyboard display terminal, 5.. Keyboard section, 6..
Display section.

Claims (1)

[Claims] In a system comprising a disk file device connected to a large general-purpose computer in which checklist data as character information is stored, and an image external storage medium in which failure case data is stored as image information. , By transmitting check item request data from the keyboard/display terminal to the large-scale general-purpose computer, the checklist data corresponding to the check item and failure case data are displayed in association with each other on the keyboard/display terminal. A software development execution plan checking system characterized by the following.