JPH0855041A - System test specification generator - Google Patents

Abstract

PURPOSE:To execute the preparation of a system test specification or its support by utilizing the specification descriptions of a system, to perform its execution support and to reduce labor for developing the system. CONSTITUTION:This device is provided with a specification input means 101 for inputting specification data, specification description storage means 102 for storing the inputted specification data, test item deciding means 103 for deciding a test item based on the stored specification data, specification description retrieving means 104 for retrieving the reaction of the system corresponding to the test item decided by the test item deciding means 103 from the specification data stored in the specification description storage means 102, and test result output means 105 for outputting the test item and the retrieved result.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a test of a system developed by using a specification description which is specification data,
The present invention relates to a system test specification generation device that creates a system test specification document using a specification description.

[0002]

2. Description of the Related Art Currently, in system development, in order to improve development efficiency, support tools in each process of system development and support tools integrating each process are becoming popular. They aim to generate the data required to implement the system based on the system specifications defined at the beginning. However, in actual system development, the realized system is
System test). Until now, the system test was conducted manually by considering the test method from the information from the person who developed the system and the development document for each person who performs the system test.

[0003]

However, in the above-mentioned conventional system development support system, it takes time and manpower to create the system test specification at the system test stage, and the test procedure may be omitted. there were. In addition, there may be a delay in determining how the test results violate the system specifications.

The present invention solves the above-mentioned problems of the prior art by creating a system test specification using a system specification description or supporting the system test execution, and by supporting the system test execution, the system development effort is reduced. It is an object of the present invention to provide a system test specification generation device that can be used.

[0005]

In order to achieve the above object, the first configuration of the system test specification generation device of the present invention is to input the specification data as data of a sentence or a drawing or to convert the existing specification data. Specification input means for reading from the specification description storage means for reuse and input, specification description storage means for storing the specification data input by the specification input means, and test items based on the specification data stored in the specification description storage means A test item determining means for determining, a specification description searching means for searching the reaction of the system to the test item determined by the test item determining means from the specification data stored in the specification description storing means, a test item and a search result are output. And a test result output means.

A second configuration of the present invention is a specification document input means for inputting a system specification by a tagged document in which specification data such as a text or a drawing is tagged, and a specification document for storing the document as a specification document. A storage unit, a specification description search unit that searches the specification document for specification data from the specification document storage unit based on tags, a test item determination unit that determines a test item based on the specification document stored in the specification document storage unit, and a test A specification description search means for searching the specification document stored in the specification document storage means for the system reaction to the test item determined by the item determination means, and a test result output means for outputting the test item and the search result Is.

A third structure of the present invention is, in addition to the above-mentioned second structure, provided with a specification item storage means for storing, for each document, description item tags required for a specification document system required in system development. .

A fourth structure of the present invention is the above first to third structures.
In the above configuration, the test item determining means is provided in place of the test item deciding means so that the test item can be input by a sentence or the like so that the test item can be added or modified.

According to a fifth aspect of the present invention, the specification input means for inputting the specification data, the specification description storage means for storing the specification data input by the specification input means, and the specification data input by the specification input means Specification item storage means for storing the specification items required for description for each specification data, specification item input means for inputting the specification items, and specification description storage means for storing the insufficient items based on the specification items input by the specification item input means. A specification description search means for searching from the specification data stored in and a specification item inspection result output means for outputting a search result.

According to a sixth aspect of the present invention, the specification input means for inputting the specification data, the specification description storage means for storing the specification data input by the specification input means, and the specification data stored in the specification description storage means. The specification name input means for inputting the specification name for the purpose of collating with each other, the pre-stage specification input means for obtaining the specification data of the previous stage of the input specification name from the specification description storage means, and the obtained previous stage The specification description retrieving means for retrieving the specification data of the subsequent stage from the specification description storing means on the basis of the specification data and collating the specification data, and the collation result outputting means for outputting the collation result.

According to a seventh aspect of the present invention, the specification input means for inputting the specification data, the specification description storage means for storing the specification data input by the specification input means, and the existing existing when the specification data is input by the specification input means. Search item input means for inputting search items for searching the specification data of, and specification description search means for searching the specification data of the part requested by the search items from the specification description storage means based on the input search items, The specification description output means for outputting the retrieved specification data to the specification input means is provided.

[0012]

According to the first aspect of the present invention, when the system specification is input by the specification input means, the existing system specifications or the specification data before the current development stage is used from the specification description storage means. Development is possible and development effort can be reduced. In addition, the test item determining means selects all or part of the operation of the system from the specification data, which is the system specification stored in the specification description storing means, and the reaction to the system and the reaction thereof, and then selects the system according to the rule. Make a combination about the order in which the operations to
By making it a test item, it is possible to eliminate leakage of the test item.

According to the second structure of the present invention, the specification data with tag is input as specification document by the specification document input means, and the document itself is held in the specification document storage means. Then you can directly use it to create a system test specification. Furthermore, by removing the tag from the specification document, a specification document in natural language can be obtained.

According to the third configuration, the present invention further comprises specification item storage means for storing description item tags required for a specification document system required in system development for each document, and based on this, input up to now. In addition to the specifications
By presenting the lacking specification item as a description item tag, it is possible to reduce the development labor for creating the specification document of the system.

According to the fourth aspect of the present invention, the test item is input by the test item inputting means, and the specification description storing means and the specification document storing means store the respective specification descriptions and the respective specification documents by the specification description searching means. It is possible to confirm the system specifications at each stage by searching and obtaining the reaction of the system as the test result with the test result output device.

According to the fifth aspect of the present invention, the description of each specification data is obtained by inspecting the specification data stored in the specification description storage means based on each specification item stored in the specification item storage means. You can inspect for leaks.

According to the sixth aspect of the present invention, based on the specification name input from the specification name input means, the previous-stage specification search means searches for the previous-stage specification data, and the specification description search means searches for the previous data. By matching the specification data of the stage with the specification data of the specification name, the consistency between the specification data can be maintained.

According to the seventh aspect of the present invention, when the specification data is input by the specification input means, necessary specification data is input as search items by the search item input means, and is searched from the specification description storage means. By outputting the description output means to the specification input means, the input of the specification data can be reduced and the existing specification data can be reused.

[0019]

【Example】

(Embodiment 1) A first embodiment of the present invention will be described with reference to FIG. FIG. 1 is a block diagram showing the arrangement of a system test specification generation device according to this embodiment. In FIG. 1, 101 is a system for inputting system specifications, or an existing specification description, that is, specification data, for the specification description storage means 1.
A specification input means for reading and using from 02 to input new specifications, 102 a specification description storage means for storing system specifications as specification data, and 103 a test item based on the specification data stored in the specification description storage means 102. Which is determined and input to the specification description retrieving means 104. Reference numeral 104 retrieves each specification data in the specification description storing means 102 based on the test item input from the test item deciding means 103, and the system for the test item. Is a specification description retrieving means, and 105 is a test result output means for outputting the test result obtained by the specification description retrieving means 104.

The operation of the system test specification generating apparatus configured as described above will be described below. FIG. 2 shows the procedure of the system test specification generation device of this embodiment. In FIG. 2, the specification input means 101 first checks whether or not there is a usable specification description in the specification description storage means 102 (step 201). If not, enter system specifications (step 202). If yes,
The specification description data to be used is read and a new system specification is added (step 203). Next, the specification description storage means 102 stores each system specification as each specification description (step 204). Next, the test item determination means 103
Searches the description of the test item from the specification description storage unit 102, prioritizes the description of the searched test item, determines the order of execution of the test item according to the priority, and converts the test item into the format of the test item ( Step 205).
Next, the specification description search means 104 is the test item determination means 1
In response to the search request from 03, the reaction of the system according to each specification description in the specification description storage unit 102 is obtained as a test prediction result (step 206). Finally, the test result output means 105 outputs the test prediction result obtained by the specification description search means 104 (step 207).

Next, the specific operation of the system test specification generating apparatus will be described by taking the slide presentation system shown in FIG. 3 as an example. This slide presentation system has a front button for sending the page of the slide forward and a rear button for sending the page of the slide forward to each slide projected on the screen, and the display of ACTIVE indicates a state where the button can be pressed, and INACTIVE. Indicates that the button cannot be pressed. The system requirement specification of this slide presentation system is to display a page and send the page forward and backward. As a UI (user interface) specification, when the user executes a start command, the system displays 1 It is defined that when the page is displayed and the user presses the back button, the system displays the back page and when the user presses the front button, the system displays the front page. However, if the current display is the first page, the previous button is INAC
It is stipulated that the rear button should be INACTIVE if it is the last page, and that each button should be ACTIVE if it is the last page.

4 and 5 show examples of the grammar of the specification description of the above embodiment. In this embodiment, each specification is described as a specification description. For example, when "% system: system name" is described in the requirement specification description, it means that the system name is defined, and "% action:
When it is described as "system function", it means that the system function is defined. Also, in the grammar of the UI specification description, "% structure {system name}" is followed by "% structure {component name {Part name, {Part name, ..
} ...}} ”can be used to hierarchically describe the system and component configurations. Also, any number of such descriptions can be described, and the description order of% structure is system or component. Indicates the priority order for executing the function, and the description order in {} indicates the component configuration of the system.In addition, when "% operation: instruction" is described, the operation instruction of the user to the system or its component is given. , "% State: variable name = value" means that the state variable of the system or component and its value are defined, and "% action: system function (state variable name op Value) ”describes the function of the system, but the value of the state variable is op (+ and-)
It means that the function of the system is executed after the change according to the following. When "% action: Function of the system (A)" is described, the function of the system is defined. Means that the function is performed. If "% component: component name" is described, it means a component that makes up the system. If "% when: state variable name comp state variable name" is described,
If the condition indicated by comp is applied to the state variable of the system and the condition is satisfied, it means that the contents described thereafter are executed. Here comp is =, <,
>, And the values of variables on both sides of comp are equal, less than, and greater than in this order.

Next, the operation of this embodiment will be described with reference to FIGS. 6 to 9 based on the above specific example. First, the specification input means 1
01 checks whether the available system specifications exist in the specification description storage means 102 (step 601). That is, it is checked whether or not some system specifications are already stored. If this is not the case, for example, the content of the system requirement specification is input with such a description (step 6).
02), the specification description storage means 102 stores this specification description (step 603).

If there is a usable specification description (step 601), for example, in the above example, the specification description storing means 102 has the specification description of the system requirement specification.
It is read from the specification description storage means 102, and a new specification (UI user interface specification) is input and added to it from the specification input means 101 (circle part). In addition, the description method is changed (the part of Δ) (step 604,
701). The created specification description is stored in the specification description storage means 102 (step 702). In this way, system specifications and specification descriptions have a level of specification refinement,
The specification input means 101 obtains a required level of specification description from the specification description storage means 102 according to the level.

Subsequently, the test item determining means 103 retrieves the test item from the specification description storing means 102 according to the rule. In this example, the part that is the test item (% componen
Search for t,% system,% operation) (step 8)
01). From the description of% structure, step 802
It is converted to a tree structure like. The tree structure is first traced counterclockwise from the slide presentation system, which is the root of the tree structure, and the priority is set to 1 for the slide presentation system, 2 for the rear button, and 3 for the front button. Further, by tracing clockwise from the slide presentation system, which is the root of the tree structure, the priority order is set such that the slide presentation system is 1, the front button is 2, and the back button is 3. Finally, the information obtained from the set of the test item part% component and its% operation or% system and its% operation, that is, the description after ":" is arranged according to the two priorities just obtained. At this time, the description format of the test item is corrected, for example, as in step 803.

Next, by inputting the test item created by the test item determining means 103, the specification description searching means 104
Obtains the system reaction to each test item from the specification description as follows (step 901). For example, in the case of the test item "start (slide presentation system)", from the UI specification description in step 701,% component,% sy
Stem,% operation and the corresponding description part (parts separated by blank lines) with "start" and "slide presentation system" of the test item "start (slide presentation system)" as marks
Find out. Therefore,% operation: The next line after activation,% action: display (page), is obtained as the reaction of the system. Get the "display (page)" part from here.

Further, from "page", the current value of the state variable page is obtained. At this time, if the part in () includes + and-, the value of the state variable is changed according to each.
Currently, the value of the state variable is 1 because% state: page = 1 is set. The "display (page, 1)" is obtained from the 1 and the "display (page)". Furthermore, the part of% when is searched from all the descriptions of the UI specification description. Then, the current value of the state variable page is 1, so you can find the line% when: page = 1. If the condition shown after% when: is met, you will see this next line, so you can find% action: INACTIVE (previous button) here. Similarly, "ACTIVE (back button)" can be obtained.

Therefore, the test result "display (page 1)", "INACTIVE (front button)" and "ACTIVE (rear button)" can be obtained from the test item "start (slide presentation system)". Other test items also obtain test results in the same manner. Then, the test result output means 105 outputs these (steps 902 and 903).

Although the specification input means 101 inputs the specification description, a method of inputting the specification description, converting it into the specification description format, and inputting it to the specification description storage means 102 is also conceivable. Further, in the test item determining means 103, the order of the test items is determined here by the priority, but the method of determining the test items is held as data, and the test item determining means 103 stores the test items in the specification description based on the method. A method of determining from the means 102 is also conceivable.

As described above, according to the first embodiment, the system specification description is used to describe only the difference in specifications at each stage of system development, and the items to be system tested are comprehensively complied with the rules. Since the system test specifications are generated after selecting the above, there are advantages that the consistency of the specifications can be maintained, the understanding of the system can be assisted, and the effort for system test preparation can be reduced.

(Second Embodiment) A second embodiment of the present invention will be described with reference to FIG. FIG. 10 is a block diagram showing the configuration of the system test specification generation device in this embodiment. In FIG. 10, reference numeral 1001 is a specification document input means for inputting specification data in which texts and drawings are tagged as a specification document, 1002 is a specification document storage means for storing the specification document, and 1003 is a specification document storage means 1
A test item determining means for determining a test item based on the specification document stored in 002, a specification 1004 searches each specification document in the specification document storing means 1002 based on the tag, and obtains a system reaction to the test item as a test result. Description search means 1005 is specification description search means 1004
Is a test result output means for outputting the obtained test result.

The operation of the system test specification generating device configured as described above will be described below. Figure 11
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 11, first, the specification document input means 100
1 inputs a system specification document (step 11)
01). Next, the specification document storage means 1002 stores each system specification document as each tagged document (step 1
102). Next, the test item determination means 1003 retrieves the description serving as the test item from the specification document storage means 1002, prioritizes the retrieved test item descriptions,
The execution order of the test items is determined according to the priority order and converted into the test item format (step 1103). Next, the specification description search means 1004 is the test item determination means 100.
In response to the retrieval request from 3, the tag portion is extracted from the specification document storage means 1002, and the reaction of the system is obtained as the test prediction result (step 1104). Finally, the test result output means 1005 is the specification description search means 100.
4 outputs the test prediction result obtained (step 110).
5).

Next, a specific operation of the system test specification generation apparatus will be described using the slide presentation system shown in FIG. 3 as an example and using the description method shown in FIGS. 12 and 13. 12 and 13 show grammatical examples of the specification document in this embodiment, and each specification is described as a specification document. The specification document is a document or a figure with a tag attached, and the tag is a mark, which is indicated by "\, .. {}" here. Further, the specification document exists according to the level of detailing of the specification. In the case of the tag of the requirement specification document, the description of "\ system {}" indicates the system name, and the description of "\ action {}" indicates the system function. Also, in the case of the tag of the UI specification document, "\ structure {component name {component name, {component name, ...
} ...}} ”can be used to hierarchically describe the system and component configurations. Also, any number of such descriptions can be described, and the description order of% structure is system or component. The order of execution of the functions is shown, and the description order in {} shows the system component structure.In addition, "\ state {name = value + value -value}"
Is a system or component state variable, the variable name is name and the value is its value, where = means the assignment of the value to the variable, and + means the current value of the variable. The value of value is added to, and-means that the value of value is subtracted from the current value of the variable. Also, "\ component
When it is described as {part name}, it means a part that makes up the system, and when it is described as "\ operation {}", it means an operation command of the user to the system or the part, When "\ when {name comp name}" is described, the condition indicated by comp is applied to the system state variable name, and if the condition is satisfied, the contents described after that are executed. Here, comp is =, <,>, and in this order, the values of variables on both sides of comp are equal, less than, and greater than.

Next, the operation of this embodiment will be described with reference to FIGS. 14 to 17 based on the above specific example. First, the specification document input means 1001 inputs a system specification document (step 1401). For example, here, the system requirement specification in FIG. 3 is described in the format shown in step 1401 and thereafter. Here, the specification document includes tags and documents. The specification document is stored in the specification document storage means 1
002 (step 1402).

If there is a specification document that can be used (step 1403), for example, in the above example, the specification document storage means 1002 has the specification document of the system requirement specification. Therefore, it is read from the specification document storage means 1002. ,
A new specification document (UI specification) is input from the specification document input means 1001 and added or changed (steps 1404 and 1501), and the resulting specification document is stored in the specification document storage means 1002 (step 1502). As described above, the system specification and the specification document have a level of detailing the specification, and the specification document input unit 1001 obtains a required level specification document from the specification document storage unit 1002 according to the level.

Then, the test item determining means 1003 fetches the test items from the specification document storing means 1002 according to the rule (step 1601). In this example, the part that is the test item (\ component, \ system, \ operation
) Is searched. Further, the description of \ structure is converted into a tree structure as in step 1602. Then, the tree structure is first traced counterclockwise from the slide presentation system, which is the root of the tree structure, and the priority is set to the slide presentation system 1,
Attach the back button as 2, the front button as 3. Further, by tracing clockwise from the slide presentation system, which is the root of the tree structure, the priority order is set such that the slide presentation system is 1, the front button is 2, and the rear button is 3. The last part to be tested is \ component and its \ operation or \ syst
The information obtained from the combination of em and its \ operation is arranged according to the two priorities just obtained. At this time, the description format of the test item is corrected, for example, as in step 1603.

Next, by inputting the test item created by the test item determining means 1003, the specification description searching means 100
4 obtains the reaction of the system to each test item from the specification document as follows (step 1701). For example, in the case of the test item "start (slide presentation system)", from the UI specification document in step 1601, the tags \ component, \ system, and \ operation and the test item "start (slide presentation system)""start", Use the "slide presentation system" as a marker to find the corresponding description part (part delimited by a blank line). So, \ operatio
n The "display (page)" portion is obtained as the system reaction from the tag \ state {page} next to {start} and the next tag \ action {display}.

Further, the current value of the state variable page is obtained from "page". At this time, if the part in () includes + and-, the value of the state variable is changed according to each.
At present, the value of the state variable is 1 because \ state {page = 1} is set, and "display (page, 1)" is obtained from this 1 and "display (page)".

Further, the portion of \ when is searched from all the descriptions of the UI specification document. Then, since the current value of the state variable page is 1, the line \ when {page = 1} can be found. If the condition shown after \ when: is satisfied, the next line is viewed, so here, the following two tags \ component {previous button} and \ action {INACTIVE} to "INACTIVE (previous button)" Is obtained. The same can be obtained for "ACTIVE (back button)".

Therefore, from the test item "start (slide presentation system)" to the test result "display (page,
1) ”,“ INACTIVE (front button) ”and“ ACTIVE (back button) ”are obtained. The test results are obtained in the same manner for other test items.
5 outputs (steps 1702 and 1703).

As described above, according to the second embodiment, a system specification document is saved as a document by adding a tag to the system specification document, and the system specification is directly used to specify the specification at each stage of system development. The system test specifications are generated after describing only the differences in the above and comprehensively selecting the items to be system tested according to the rules, so that the consistency of the specifications can be maintained and the labor for the system test preparation can be reduced. In addition, by removing the tag from the specification document, it is possible to create a specification document consisting only of natural language, which has an advantage of helping understanding of the specification.

(Embodiment 3) A third embodiment of the present invention will be described with reference to FIG. FIG. 18 is a block diagram showing the configuration of the system test specification generation device in this embodiment. In FIG. 18, reference numeral 1801 is a specification document input means for inputting specification data in which documents such as sentences and drawings are tagged as a specification document, 1802 is a specification document storage means for storing the specification document, and 1803 is a specification document input means. When inputting a specification document in 1901, the specification item storage means stores the description items necessary to describe the specification document as tags for each document. Reference numeral 1804 is a test item determining means for determining a test item based on the specification document, 180
Reference numeral 5 is a specification description search means for searching each specification document in the specification document storage means 1802 based on the tag and obtaining a system reaction as a test result. Reference numeral 1806 is a specification description search means 180.
5 is a test result output means for outputting the obtained test result.

The operation of the system test specification generating device configured as described above will be described below. FIG. 19
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 19, first, the specification item storage means 180
3 stores the description items necessary for describing the specification document as tags (step 1901). Next, the specification document input means 1801 inputs the description item tag necessary for creating the specification document from the specification item storage means 1803 and inputs the system specification document (step 1902). Next, the specification document storage unit 1802 stores each system specification document as each tagged document (step 1903). Next, the test item determining unit 1804 retrieves the description serving as the test item from the specification document storage unit 1802 (step 190).
4), prioritize from the description of the retrieved test items, determine the order of execution of the test items according to the priority,
Convert to test item format. Next, the specification description search means 1
In response to the search request from the test item determination unit 1804, the unit 805 extracts the tag portion from the specification document storage unit 1802, and then obtains the system reaction as a test prediction result (step 1905). Finally, the test result output means 1806 outputs the test prediction result obtained by the specification description search means 1805 (step 1906).

Next, regarding the specific operation of the system test specification generating apparatus, using the slide presentation system shown in FIG. 3 as an example, using the description method of FIGS. 12 and 13,
This will be described with reference to FIGS. 20 to 22. First, description item tags necessary for describing a specification document are stored in the specification item storage unit 1803 (step 2001). Then, the specification document input means 1801 is used for the specification item storage means 180.
The description items necessary for describing the specification document are obtained from 3 as tags, and the system specification document is input by the specification document input means 1801 (step 2002). For example, here, the system requirement specification in FIG. 3 is described in the format of the tag and the document as shown in step 2002, and this specification document is stored in the specification document storage unit 1802 (step 2
003).

If there is a specification document that can be used (step 2101), for example, in the above example, the specification document storage means 1802 has the specification document of the system requirement specification, so it is read from the specification document storage means 1802 ( Step 2102). Further, the UI specification required items necessary for describing the UI specifications are read from the specification item storage unit 1803 (step 2103). A new specification document (UI specification) is input and added to the specification document input means 1801 (step 2201). The created specification document is stored in the specification document storage means 1802 (step 220).
2). As described above, the system specification, the specification document, and the specification item have a level of detailing of the specification.
Reference numeral 01 designates a required level of specification document from the specification document storage means 1802 according to the level,
From 3 get the required level of specification items.

The subsequent processing is shown in FIG.
Same as 17. Also, the same effect can be obtained by replacing the data to be handled from the specification document with the specification description and adding the specification item storage means 1803 to the configuration of FIG. 1 of the first embodiment.

As described above, according to the third embodiment, the specification item necessary for describing the specification is saved as a tag and is used at the time of inputting the specification document, thereby reducing the effort for creating the specification document. , Clarify the necessary description items in each specification document. Also, by tagging the system specification document, the system specification is saved as a document, and by using this directly, only the differences in specifications are described at each stage of system development, and the items that should be system tested are comprehensive according to the rules. Since the system test specifications are generated after selecting, the consistency of the specifications can be maintained and the effort for system test preparation can be reduced.

Further, by removing the tag from the specification document, a specification in natural language can be obtained.

(Fourth Embodiment) Next, a fourth embodiment of the present invention will be described with reference to FIG. FIG. 23 is a block diagram showing the arrangement of the system test specification generating apparatus according to this embodiment. In FIG. 23, reference numeral 2301 is used to input system specifications, or to read and use an existing specification description, that is, specification data from the specification description storage means 2302, and input new specifications. Specification description storage means 2303 for storing the specification data, test item input means 2303 for inputting a test item, 2304 search each specification data of the specification description storage means 2302 from the test items input by the test item input means 2303, and the system 2305 is a test result output unit for outputting the test result obtained by the specification description search unit 2304.

The operation of the system test specification generating apparatus configured as described above will be described below. FIG.
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 24, first, the specification input means 2301
Checks whether there is a usable specification description in the specification description storage unit 2302 (step 2401). If not, enter system specifications (step 240).
2) If there is, read the specification description data to be used and add a new system specification (step 240).
3). Next, the specification description storage unit 2302 stores each system specification as each specification description (step 2404).
Next, the test item input means 2303 inputs the item to be tested (step 2405). Next, the specification description retrieving unit 2304 obtains the reaction of the system corresponding to each specification description in the specification description storing unit 2302 as a test prediction result in response to the retrieval request from the test item inputting unit 2303 (step 2406). Finally, the test result output means 2305
Outputs the test prediction result obtained by the specification description searching means 2304 (step 2407).

Next, regarding the specific operation of the system test specification generation apparatus, the slide presentation system shown in FIG. 3 is taken as an example and the description method shown in FIGS.
5 and FIG. 26. First, each system specification is stored in the specification description storage unit 2302 as each specification description. For example, it is assumed here that the specification description of the UI specification is stored (step 2501).

Subsequently, when a test item is input from the test item input unit 2303 (step 2601), the specification description search unit 2304 responds to each specification description in the specification description storage unit 2302 by a search request from the test item input unit 2303. The system response is obtained as a test result (step 2602). For example, when the test item is "start (slide presentation system)", from the UI specification description in step 2501,% component,% system,% operat
Find the corresponding description part (part delimited by a blank line) with “start” and “slide presentation system” in the test item “start (slide presentation system)” as the marks. Therefore,% operation: The next line after activation,% action: display (page), is obtained as the reaction of the system. Get the "display (page)" part from here.

Further, the current value of the state variable page is obtained from "page". At this time, if the part in () includes + and-, the value of the state variable is changed according to each.
Currently, the value of the state variable is 1 because% system: page = 1 is set. The "display (page, 1)" is obtained from the 1 and the "display (page)".

Further, the% when portion is searched from all the descriptions in the UI specification description. Then, the current value of the state variable page is 1, so you can find the line% when: page = 1. % When: The next line will be seen if the condition shown after: is satisfied, so here is% action: INAC.
You can find TIVE (front button). Similarly, ACTIVE (back button) is obtained.

Therefore, the test result “display (page, 1)”, “INACTIVE (front button)” and “ACTIVE (rear button)” can be obtained from the test item “start (slide presentation system)”. Other test items also obtain test results in the same manner. Then, the test result output means 2305 outputs these (step 2603).

The same effect can be obtained even if the data to be handled is replaced from the specification description to the specification document, and the specification input means 2301 is replaced with the specification document input means and the specification description storage means 2302 is replaced with the specification document storage means.

As described above, according to the fourth embodiment, the test item is input by the test item input means,
By searching the test results from the specification description storage means or the specification document storage means by the specification description search means, the system specifications can be confirmed at each stage of the specifications.

(Embodiment 5) A fifth embodiment of the present invention will be described with reference to FIG. FIG. 27 is a block diagram showing the arrangement of the system specification inspection apparatus according to this embodiment. In FIG. 27, 2701 is specification input means, 2
Reference numeral 702 is a specification description storage unit, 2703 is a specification item storage unit, 2704 is a specification item input unit for inputting a specification item from the specification item storage unit 2703, 2705 is a specification description search unit, and 2706 is insufficient based on the input specification item. It is a specification item inspection result output unit that outputs a result of searching an item from the specification data stored in the specification description storage unit 2702.

The operation of the system test specification generating apparatus configured as described above will be described below. FIG.
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 28, the specification input means 2701 first inputs each system specification (step 2801).
Next, the specification description storage means 2702 stores each system specification as each specification description (step 2802). Next, it is assumed that each specification item is stored in the specification item storage means 2703 (step 2703). Next, the specification item input means 2704 inputs the specification item (step 280).
4). Next, the specification description search means 2705 compares the input specification item with the specification description of the inspection target to search for an insufficient item (step 2805). Finally, the specification item inspection result output means 2706 outputs the lacking part of the specification item (step 2806).

Next, regarding the specific operation of the system test specification generation apparatus, the slide presentation system shown in FIG. 3 will be used as an example and the description method shown in FIGS.
9 and FIG. 30. First, each system specification is input. For example, the required specifications of the slide presentation system of FIG. 3 are input in the specification description format. However, it is assumed that one item required for description is insufficient (step 2
901). Then, the system description is stored in the specification description storage means 2
It is stored in 702 (step 2902).

The specification item storage means 2703 stores each specification item. For example, it is assumed here that the specification items necessary for the required specification description are stored (step 2903). Then, the required specification items are input by the specification item input means 2704 (step 290).
4). Based on the input specification item, the specification description searching means 2705 compares the specification description in the specification description storing means 2702 to search for an insufficient item or an undescribed portion (step 3001). Finally, the specification item inspection result output means 2706 outputs the deficient portion or undescribed portion retrieved (step 3002).

In the specification item storage means 2703, the items necessary for describing the actual system are held and used as tags here. However, for the purpose of facilitating the description of the specifications, for example, "Part 1 System Function" It is also possible to store "", "Part 2 data specification", etc., and describe the specification document in a format closer to the specification.

Similar effects can be obtained by replacing the specification description with the specification document.

As described above, according to the fifth embodiment, the necessary items that the specification description and the specification document must meet at each specification stage are stored in the specification item storage means, and the existing items are stored based on the necessary items. By checking the specification data of, it is possible to find any omissions in the description of the specification data.

(Embodiment 6) A sixth embodiment of the present invention will be described with reference to FIG. FIG. 31 is a block diagram showing the arrangement of the system specification inspection apparatus according to this embodiment. In FIG. 31, 3101 is specification input means, 3
Reference numeral 102 is a specification description storage means, 3103 is a specification name input means for inputting a specification name to be collated, and 3104 is specification description storage means 31 for the specification data at a stage before the input specification name.
02, the specification description search means 3105 and the specification description search means 3105.
Reference numeral 106 is a collation result output means for outputting the collation result.

The operation of the system test specification generating apparatus configured as described above will be described below. FIG.
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 32, the specification input means 3101 first inputs each system specification (step 3201).
Next, the specification description storage means 3102 stores each system specification as each specification description (step 3202). Next, the specification name input means 3103 inputs the specification name to be collated (step 3203), and collates whether or not there is specification data at the previous stage of the input specification name (step 3204). If there is not, the process ends, and if there is, the previous stage specification input means 310
4 obtains the previous specification data of the specification name to be collated from the specification description storage means 3102 and inputs it to the specification description search means 3105 (step 3205). Next, the specification description search means 3
Based on the input specification data 105, the specification data of the subsequent stage is retrieved from the specification description storage means 3102 and collated (step 3206). Finally, the collation result output means 3106 outputs the collation result (step 3).
207).

Next, regarding the specific operation of the system test specification generation apparatus, the slide presentation system shown in FIG. 3 will be taken as an example and the description method shown in FIGS.
3 and FIG. 34. First, each system specification is input. For example, the required specifications and UI specifications of the slide presentation system in FIG. 3 are input in the specification description format. However, the description method will be partially changed for the UI specification description. That is, a description method is adopted such that the specification description of the previous stage (required specification description) is included in the specification description of the subsequent stage (UI specification description) (step 3301).

Then, the above-mentioned system requirement specification description and UI
The specification description is stored in the specification description storage means 3102 (step 3401). Here, the specification name of the latter stage of the specification data to be collated between the specification data is the specification name input means 3
Input from 103 (step 3402). For example, if the system requirement specifications and UI specifications are checked here, U
Enter I specification. Next, it is checked whether or not there is specification data at the previous stage of the input specification name (step 340).
3).

If there is pre-stage specification data, the pre-stage specification data of the UI specifications and the system requirement specification description are stored in the specification description storing means 3102. The system requirement specification description is obtained from the description storage means 3102 and input to the specification description search means 3105 (step 3404). If there is no previous specification data of the input specification name, the process ends.

From the system requirement specification description, the specification description retrieving means 3105 checks whether or not each line of the system requirement specification description is included in the UI specification description stored in the specification description storing means 3102 (step 3405).

The collation result output means 3106 outputs the collation result. Here, since the system requirement specification description is all included in the UI specification description, for example, the verification result is OK.
Is output (step 3406).

If the output result from the collation result output means 3106 is OK, the specification name at the next stage is input to the specification name input means 310.
It is also possible to automatically inspect all the stages of specifications, such as input from 3.

The same effect can be obtained by replacing the specification description with the specification document.

As described above, according to the sixth embodiment, it is possible to check the consistency between the specification data according to each specification stage.

(Embodiment 7) A seventh embodiment of the present invention will be described with reference to FIG. FIG. 35 is a block diagram showing the configuration of the system specification input support device in this embodiment. In FIG. 35, reference numeral 3501 is specification input means, 3502 is specification description storage means, 3503 is search item input means for inputting search items to search for specification data required when inputting the specification data in the specification input means 3501, and 3504 is A specification description search unit 3505 is a specification description output unit that outputs the specification data searched from the specification description storage unit 3502 by the specification description search unit 3504 based on the search item.

The operation of the system test specification generating apparatus configured as described above will be described below. Fig. 36
Shows the procedure of the system test specification generation device of this embodiment. In FIG. 36, the specification input means 3501 first inputs search items to the search item input means 3503 for the specification data required by the existing specification data stored in the specification description storage means 3502 (step 3601).
Next, the search item input means 3503 inputs the search items to the specification description search means (step 3602). Next, the specification description search means 3504 obtains the specification description of the part required by the search items from the specification description storage means 3502 based on the input search items (step 3603). Next, the specification description output means 3505 outputs the desired specification description to the specification input means (step 3604). And specification input means 3
501 obtains the intended specification description (step 360).
5).

Next, regarding the specific operation of the system test specification generation device, the slide presentation system shown in FIG. 3 will be used as an example and the description method shown in FIGS.
5, FIG. 37, and FIG. 38. First, as existing specification data in the specification description storage unit 3502,
It is assumed that the UI specification description as shown in FIG. 25 is stored. Then, the specification input means 3501 is used for the specification description storage means 3
In order to use the existing specification data stored in 502, necessary search items are input to the search item input means 3503. For example, if specification data about a button is required, since the button is a component, the component is indicated by% component: and the button is input as "% component: button" (step 3701).

Then, the search item input means 3503 inputs the input search items to the specification description search means 3504 (step 3702), and the specification description search means 3504
Search item "% component: Button""%component"
From the UI specification description stored in the specification description storage unit 3502, and the “button” are searched for a part that matches these keywords. % Component retrieves a block separated by a blank line (step 3703).

When the specification description output means 3505 outputs the retrieved specification data to the specification input means 3501 (step 3801), the specification input means 3501 uses the specification data to input the specification data (step 3).
802).

Although the components are reused by% component here, the system is reused, the function is reused, and the data is reused for% system, a pair of% operation and% action, and% state. Reuse is possible as well.

Similar effects can be obtained by replacing the specification description with the specification document.

As described above, according to the seventh embodiment, when the specification data is input by the specification input means, the existing specification data is used to reduce the input of the specification data and re-use the specification data. Available.

[0083]

As is apparent from the first embodiment of the present invention, when the system specification is input by the specification input means, the existing system specification or the specification description before the current development stage is stored in the specification description storage means. It is possible to use and develop from, and the development labor can be reduced. In addition, the test item determining means selects all or a part of the operation of the system, which is the specification data in the specification description storing means, and the operation of the system according to the rule, and the combination in the order of execution. Based on this test item, the specification description retrieval means retrieves the test result from the specification description storage means in which the specifications of the operation to the system and its operation are registered, and the test item and the test result are created. It is possible to create a system test specification with less leakage in the test procedure.

As is apparent from the second embodiment, the present invention inputs the specification document tagged with the specification data by the specification document input means, and holds the document itself as the specification document in the specification document storage means. By doing so, it is possible to create a system test specification by using it directly as a tag, and by removing the tag from the specification document, it becomes a specification consisting only of natural language, which helps understanding of the specification.

As is apparent from the third embodiment, the present invention further comprises specification item storage means for storing the description items necessary for the specification document system required in system development as tags for each document. Based on the specifications input up to the present and its lacking part, by presenting the description items as the contents of the specifications, it is possible to reduce the development effort for creating the specification data of the system.

Further, as is apparent from the fourth embodiment, the present invention inputs the test item by the test item input means and retrieves the test result from the specification description storage means or the specification document storage means by the specification description retrieval means. By doing so, the system specification can be confirmed at each stage of the specification.

As is clear from the fifth embodiment, the present invention stores the necessary items that the specification description and the specification document must satisfy at each specification stage in the specification item storage means, and based on that, By checking the existing specification data by using the above, it is possible to find the description omission of the specification data.

Further, as is apparent from the sixth embodiment, the present invention prepares the specifications by aligning the descriptions between the specification data and matching the specification data with each other by the previous-stage specification input means and the specification description search means. It is possible to check the consistency between the specification data according to each stage.

As is apparent from the seventh embodiment, according to the present invention, when the specification data is input by the specification input means, necessary specification data is input by the search item input means as a search item and the specification description is stored. By retrieving from the means and outputting to the specification input means by the specification description output means, the input of the specification data can be reduced and the existing specification data can be reused.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a system test specification generation device according to a first embodiment.

FIG. 2 is a flowchart showing a procedure of system test specification generation in the first embodiment.

FIG. 3 is a list diagram showing a specific example of system specifications in each embodiment.

FIG. 4 is a list diagram showing a grammar example of a specification description in the first embodiment.

FIG. 5 is a list diagram showing a grammar example of a specification description in the first embodiment (continued)

FIG. 6 is a flowchart showing a specific processing example of the system test specification generation device in the first embodiment.

FIG. 7 is a flowchart showing a specific processing example of the system test specification generation device in the first embodiment (continued)

FIG. 8 is a flowchart showing a specific processing example of the system test specification generation device in the first embodiment (continued)

FIG. 9 is a flowchart showing a specific processing example of the system test specification generation device in the first embodiment (continued)

FIG. 10 is a block diagram showing a configuration of a system test specification generation device according to a second embodiment.

FIG. 11 is a flowchart showing the procedure of system test specification generation in the second embodiment.

FIG. 12 is a list diagram showing a grammar example of a specification document in the second embodiment.

FIG. 13 is a list view showing a grammar example of a specification document in the second embodiment (continued)

FIG. 14 is a flowchart showing a specific processing example of the system test specification generation device in the second embodiment.

FIG. 15 is a flowchart showing a specific processing example of the system test specification generation device in the second embodiment (continued)

FIG. 16 is a flowchart showing a specific processing example of the system test specification generation device in the second embodiment (continued)

FIG. 17 is a flowchart showing a specific processing example of the system test specification generation device in the second embodiment (continued)

FIG. 18 is a block diagram showing a configuration of a system test specification generation device according to a third embodiment.

FIG. 19 is a flowchart showing the procedure of system test specification generation in the third embodiment.

FIG. 20 is a flowchart showing a specific processing example of the system test specification generation device in the third embodiment.

FIG. 21 is a flowchart showing a specific processing example of the system test specification generation device in the third embodiment (continued)

FIG. 22 is a flowchart showing a concrete processing example of the system test specification generation device according to the third embodiment (continued).

FIG. 23 is a block diagram showing the configuration of a system test specification generation device according to a fourth embodiment.

FIG. 24 is a flowchart showing the procedure of system test specification generation in the fourth embodiment.

FIG. 25 is a flowchart showing a specific processing example of the system test specification generation device in the fourth embodiment.

FIG. 26 is a flowchart showing a specific processing example of the system test specification generation device in the fourth embodiment (continued)

FIG. 27 is a block diagram showing the configuration of a system specification inspection device according to a fifth embodiment.

FIG. 28 is a flowchart showing the procedure of system specification inspection in the fifth embodiment.

FIG. 29 is a flowchart showing a specific processing example of the system specification inspection device in the fifth embodiment.

FIG. 30 is a flow chart (continuation) showing a specific processing example of the system specification inspection apparatus in the fifth embodiment.

FIG. 31 is a block diagram showing the configuration of a system specification inspection device according to a sixth embodiment.

FIG. 32 is a flowchart showing the procedure of system specification inspection in the sixth embodiment.

FIG. 33 is a flowchart showing a specific processing example of the system specification inspection device in the sixth embodiment.

FIG. 34 is a flowchart showing a concrete processing example of the system-specification inspection apparatus in the sixth embodiment (continuation).

FIG. 35 is a block diagram showing the configuration of a system specification input support device in a seventh embodiment.

FIG. 36 is a flowchart showing the procedure of system specification input support in the seventh embodiment.

FIG. 37 is a flowchart showing a specific processing example of the system specification input support device in the seventh embodiment.

FIG. 38 is a flowchart showing a specific processing example of the system specification input support device according to the seventh embodiment (continued).

[Description of sign]

 101 specification input means 102 specification description storage means 103 test item determination means 104 specification description search means 105 test result output means 1001 specification document input means 1002 specification document storage means 1003 test item determination means 1004 specification description search means 1005 test result output means 1801 Specification document input means 1802 Specification document storage means 1803 Specification item storage means 1804 Test item determination means 1805 Specification description search means 1806 Test result output means 2301 Specification input means 2302 Specification description storage means 2303 Test result output means 2304 Specification description search means 2305 Test Item input means 2701 Specification input means 2702 Specification description storage means 2703 Specification item storage means 2704 Specification item input means 2705 Specification description search means 2706 Specifications Eye inspection result output means 3101 Specification input means 3102 Specification description storage means 3103 Specification name input means 3104 Pre-stage specification input means 3105 Specification description search means 3106 Matching result output means 3501 Specification input means 3502 Specification description storage means 3504 Specification description search means 3503 Search item input means 3505 Specification description output means

Claims (7)

[Claims] 1. Specification input means for inputting specification data,
Specification description storage means for storing the specification data input by the specification input means, test item determination means for determining a test item based on the specification data stored in the specification description storage means, and determination by the test item determination means A system test specification including a specification description search means for searching the specification data stored in the specification description storage means for the reaction of the system to the specified test item, and a test result output means for outputting the test item and the search result. Generator. 2. A specification document input means for inputting data to which specification data is tagged as a specification document, a specification document storage means for storing the specification document input by the specification document input means, and the specification document storage means. A test item determining means for determining a test item based on the specification document stored in the specification document, and a specification for retrieving the system reaction to the test item determined by the test item determining means from the specification document stored in the specification document storing means A system test specification generation device comprising a description search means and a test result output means for outputting the test item and the search result. 3. The system test specification generation device according to claim 2, further comprising specification item storage means for storing, as tags, items required for description for each specification document when the specification document input means inputs the specification document. 4. A test item inputting means for inputting a test item instead of the test item deciding means for deciding the test item based on the specification description or the specification document stored in the specification description storing means or the specification document storing means. Item 1, 2
Alternatively, the system test specification generation device described in 3. 5. Specification input means for inputting specification data,
Specification description storage means for storing the specification data input by the specification input means, specification item storage means for storing the specification items necessary for description for each specification data when the specification data is input by the specification input means, A specification item input means for inputting a specification item; a specification description search means for searching a specification data stored in the specification description storage means for a missing item based on the specification item input by the specification item input means; A system test specification generation device comprising: a specification item inspection result output means for outputting a result. 6. Specification input means for inputting specification data,
A specification description storage unit for storing the specification data input by the specification input unit; a specification name input unit for inputting a specification name for matching the specification data stored in the specification description storage unit; The specification data of the previous stage of the specified specification name obtained from the specification description storage unit, and the specification data of the subsequent stage based on the obtained specification data of the previous stage are stored in the specification description. A system test specification generation device comprising specification description search means for searching and collating by means and collation result output means for outputting the collation result. 7. Specification input means for inputting specification data,
A specification description storage unit for storing the specification data input by the specification input unit; a search item input unit for inputting search items for searching existing specification data when the specification data is input by the specification input unit; Specification description search means for searching the specification description storage means for specification data of a part required by the search items based on the input search items, and specification description output for outputting the searched specification data to the specification input means And a system test specification generating device.