JP2003108405A - Device and program for supporting preparation of test specification - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device and a program for supporting to rapidly and easily prepare the test case group of a test specification providing a low working load to a test case preparing person and capable of increasing a coverage. SOLUTION: To support the preparation of the test specification of an objective system, this device comprises an input means for inputting user pattern information indicating representative operation patterns when a user operates a system and system behavior analysis information indication the behavior of the system analyzed in detail on an operation pattern basis, a system behavior hierarchical analysis means for analyzing the user operation pattern information and system behavior analysis information and tabulating a system behavior hierarchical table obtained by hierarchically combining both information with each other, an operation item extraction means for comprehensively extracting operation items from the system behavior hierarchical table, and a test specification item preparing means for preparing test specification items along specified view points and references for the extracted operation items.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a test technique for improving reliability in software development, and supports creation of a test case used in software test from the viewpoint of functional operation specifications. The present invention relates to a test specification creation support device and program.

[0002]

2. Description of the Related Art In modern society, there are various devices ranging from daily-use home appliances to social infrastructure such as information and communication devices, power plants, and transportation facilities. These devices are indispensable for our daily lives, and their malfunction can have a great impact on society. Therefore, there is an ever increasing demand for reliability of software incorporated for controlling / managing devices.

In general, a testing process is important to evaluate and guarantee the reliability of developed software. It is necessary to guarantee the correct operation of the software under any circumstances by actually checking the operation of all items such as functional specifications and performance specifications that the software should satisfy and correcting any problems. I won't.

In particular, in a system involving human life or a system in which the occurrence of a failure has a great influence on society, it is necessary to comprehensively test all possible behaviors and combinations thereof. With the sophistication and complexity of the software system, it has become extremely difficult to create such comprehensive test cases.

Usually, in the test work, a checklist listing the functions and performances that the product should satisfy is used as a test case, and the sufficiency of the test is determined by the test case described in the checklist. And the degree of coverage.

However, conventionally, it has been very troublesome to create a test case by manually referring to a product specification or the like. Also, with the current specifications using natural language, due to its ambiguity, it is difficult to create test cases that are highly comprehensive and sufficiently reliable, and the product knowledge and experience of engineers who are familiar with the software concerned are difficult to create. Will depend heavily on.

In order to solve the above problems, a technique of describing the operation specifications of the target software using a formal specification description expression such as a state transition diagram and mechanically generating a test case from the information. Alternatively, a technique has been proposed in which verification of a logical operation is attempted on these formal specification descriptions (for example, Japanese Patent Laid-Open Nos. 5-119987 and
6-110734, etc.).

However, in these prior arts, all specifications of software must be described as strict and formal specifications using a defined format such as a state transition diagram, which requires a great deal of labor. Need.

Further, as a matter of course, it cannot be applied to ordinary software in which the specification is described in natural language, and in this case, the burden of rewriting the specification into a formal description is very heavy. is there.

[0010]

Under the circumstances as described above, it is necessary to quickly and easily design a highly comprehensive test case group for a software system that is becoming more complicated and bloated in recent years. Is extremely difficult and requires a great deal of time and cost.

On the other hand, with the rapid progress of software technology, the life cycle of a software system and the period given to development are becoming shorter and shorter. Therefore, in actual development, there is a demand for a simple and efficient test method capable of ensuring the required reliability within the limited time allocated to the test process.

The present invention has been made in consideration of such circumstances, and a creator can quickly and easily create a highly comprehensive test case (test specification item) group that constitutes a test specification for target software. It is an object to provide a device and a program that support the ability.

[0013]

In order to solve the above problems and achieve the object, the present invention is constructed as follows.

A test specification creation support apparatus according to the present invention is a test specification creation support apparatus that supports creation of test specifications of a target system, and a user who represents a typical operation pattern when the user operates the system. Operation pattern information, and input means for inputting system behavior analysis information indicating the behavior of the system analyzed with a degree of detail based on the operation pattern, and analyzing the user operation pattern information and the system behavior analysis information. , System behavior hierarchy analysis means for creating a system behavior hierarchy table in which both are hierarchically combined, operation item extraction means for comprehensively extracting operation items from the system behavior hierarchy table, and the extracted operation For items, a test specification item creating means for creating a test specification item in accordance with a predetermined viewpoint and standard is provided. It is characterized in.

[0015]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of the present invention relates to a test specification creation support device that supports a work for a creator to create a test case (test specification item) group constituting a test specification for target software. The apparatus is configured by using a general-purpose computer, and the test specification creation support according to the present invention is realized by, for example, a software program.

In the test specification creation support according to the present invention, based on the software specification written in natural language, the external behavior of the software is viewed from two viewpoints, that is, "user operation pattern" and its contents. It is analyzed according to the expressed "system behavior". The analysis result is hierarchically described by using a tabular expression or a graphic expression, and the operation that can be performed in the software is extracted using this. Further, the test items are derived by adding information from a predetermined viewpoint / reference to each of the extracted operations.

<Overall Configuration> FIG. 1 is a block diagram showing a schematic configuration of a test specification creation support apparatus according to an embodiment of the present invention. This test specification creation support device is a product specification 1
A device that supports the work of creating a test specification 10 based on 3 and (a) a product specification 13 written in natural language.
, A user operation pattern evaluation unit 1 for evaluating three typical patterns of how the software is used by the user (user operation patterns), users who use the system, and their relationships, and (b ) Product specification 1
3 and the user operation pattern list 2, the system behavior analysis unit 3 for graphically expressing the procedure of the user using the software and the behavior of the system along with it, and (c) the user operation pattern list 2 and system behavior analysis System behavior hierarchy that extracts the hierarchical structure shown in Fig. 4 or defines the hierarchical structure in the information based on figures and tables that have information equivalent to them, and expresses this in tabular form. System behavior hierarchy analysis unit 5 for conversion into Table 6
And (d) an operation extraction unit 7 for analyzing the system behavior hierarchy table 6 and extracting an operation possible in the software.
And (e) Test specification items (test cases) to cover prerequisites / expected results from the defined viewpoints / standards for each extracted operation based on the information in product specification 13
A creation unit and (f) a term dictionary management unit 11 that organizes terms used between them and creates and manages a term dictionary 12.

Product specifications written in natural language 1
The operation that should be listed as a test item by gradually creating from 3 the user operation pattern list 2, the system behavior analysis diagram 4, and the system behavior hierarchy table 6 Is extracted with a high degree of coverage, and the test specification 10 is created.

The operation procedure of the test specification creation support apparatus of this embodiment will be described.

First, a user operation pattern list 2 is created by using the user operation pattern evaluation unit 1 with the product specification 13 of the software system to be tested as an input.

Next, based on the created user operation pattern list 2 and the product specification 13, the system behavior analysis section 3 is used to allow the user to identify the scenario in which the software is used and the behavior of the software system in accordance with the scenario. System behavior analysis Created as Figure 4. At that time, the user operation pattern evaluation unit 1 and the system behavior analysis unit 3
Uses the term dictionary management unit 11 to register and manage the names of the user operation patterns / system behavior elements appearing in these figures / tables, along with their position in the hierarchical structure. This makes it possible to detect the same user operation pattern or system behavior element used by different user operation patterns or system behavior elements, and by referring to them, it is possible to efficiently and systematically avoid duplication as much as possible. It is possible to create a list of user operation patterns and a system behavior analysis diagram.

Next, the created user operation pattern list 2
And the system behavior analysis FIG. 4 is input to the system behavior hierarchy analysis unit 5 to convert the hierarchical structure formed by the user operation pattern list 2 and the system behavior analysis FIG. 4 into the system behavior hierarchy table 6 for visualization.

Next, based on the system behavior hierarchy table 6 and the product specification 13 of the software system, the operation extraction unit 7 is used to comprehensively extract the software operations,
An operation item list 8 is created.

Finally, the created operation item list 8
And the test specification item creation unit 9 based on the product specification 13
Perform analysis from the specified criteria / viewpoints using, and list the preconditions and expected results (test acceptance criteria) for each operation. As a result, the operations extracted in the previous process are expanded to the test case group, and the test specification 10 which is a set of them is obtained.

Each component of the test specification creation support device shown in FIG. 1 will be described below individually.

<User Operation Pattern Evaluation Unit 1> The “user operation pattern” in the present invention means “what kind of position or role of user exists” and “what those users are with respect to the target system”. How do you use the target system? " For example, in the case of a copying machine, "general office users", "sales shop maintenance personnel", etc. can be considered as the breakdown of users. Also,
As a method of using the system, different usage scenarios are conceivable depending on the user's standpoint, such as “copy (general office user)” and “perform regular inspection (maintenance staff of store)”.

When the target software system is large-scale and complicated, the variation of the function provided by the software system is rich and complicated. Along with this, there are many variations in the “user operation pattern” that represents a typical pattern of how the user uses the system. In addition, there are complicated dependencies among these variations.

Therefore, in the user operation pattern evaluation unit 1, "users of the target system" and "user operation patterns considered when those users use the system".
Is extracted from the functional operation specifications of the system. The relationship between these is output as a user operation pattern list 2 in the form of a diagram or a table to describe the outline of the system.

User Operation Pattern List 2 and System Behavior Analysis By hierarchically associating the respective diagrams / tables and elements in FIG. 4, extraction of possible operations in the software system is realized. When the user operation pattern that is an element of the user operation pattern list 2 is made up of a plurality of detailed user operation patterns, or when a specific scenario of the user operation pattern is expressed as the system behavior analysis diagram 4, those user operations are performed. It is necessary to maintain the relationship between the table / diagram that describes the details of the pattern and the user operation pattern to be refined.

The user operation pattern list 2 is based on the premise that the hierarchical relationship between figures / tables / elements as described above can be held as information, and UML (Unified Modeling Language).
It may be implemented using the use case diagram defined in.

Example of User Operation Pattern FIG. 2 shows a display example of the user operation pattern relating to the hospital information management system on the display. In this example,
A doctor is assumed as a user (user) of the system, and is represented by a face-shaped icon (symbol) in the figure. As a user operation pattern that can be directly activated by a doctor who is a user, "1. carry out treatment and register the execution result", "2. delete treatment order". ． ．
There is a series of user operation patterns arranged vertically in the center, etc., but each of these is connected to the user's icon by a straight line, and it is clearly indicated that it is directly activated by the doctor. In addition, “6. Search for treatment order”. ． ． A user operation pattern pointed to by an arrow from another user operation pattern such as “change order information” is referred to by the user operation pattern connected to the start point of the arrow, and the user operation pattern of the reference source. It is used in.

In this way, the outline of the system can be grasped by making a group of user operations included in a plurality of user operation patterns or a series of user operations that make sense as one group independent as one user operation pattern. It is easy to do and it is possible to avoid duplication of description.

<System Behavior Analysis Unit 3> The system behavior analysis unit 3 receives the function operation specifications 13 of the software system and the user operation pattern list 2 created by the user operation pattern evaluation unit 1 described above, and inputs them to them. It corresponds to a means for creating the system behavior analysis diagram 4 by analyzing the described individual user operation patterns in detail from the viewpoint of the system behavior associated with a series of user operations.

Normally, when a user uses a software system, desired operations and outputs are realized by continuously performing a plurality of operations. The above-described user operation pattern list 2 is a collection of a series of these user operations as one unit, and an outline of the system is expressed by this.
Here, the user creates the user operation that constitutes each user operation pattern described in the user operation pattern list 2 and the flow of the system behavior accompanying it as a system behavior analysis diagram 4 by the user.

System Behavior Analysis FIG. 4 has a system behavior element, which is a unit of a scenario when a software is used, in which a series of actions caused by a user and the reaction of the system to them are integrated into a certain size. , The behavior of the system is expressed by describing together with the transitions between them.

From the above properties of the system behavior elements, each element in the system behavior analysis diagram 4 is
The flow can be expressed by still another system behavior analysis FIG. Therefore, by combining the system behavior analysis chart 4 with the user operation pattern list 2 described above, the behavior of the system can be expressed hierarchically.
It should be noted that by adjusting the abstraction level of the description by the user so that each figure does not become overly detailed, the description of the system behavior becomes easy and the completed system behavior analysis diagram 4 is easy to understand. become.

The system behavior analysis unit 3 satisfies the system behavior analysis format shown in FIG. 4 as described above, and shows the hierarchical structure of the system behavior associated with the user operation combined with the user operation pattern list 2 in the user operation pattern list. 2. System behavior analysis Includes a graphic editor (graphic editing means) for describing FIG. 4 and their elements, and relationships such as references / dependencies between these figures / tables / elements. Such a graphic editor allows the user to read the product specification 13 and describe the system behavior analysis diagram 4.
And allows to express a hierarchical structure.

In this embodiment, the detailing / hierarchical process is repeated until all system behavior elements of the system behavior analysis diagram 4 are described as actions that cannot be further divided. As a result, all the system behavior elements have a level of detail that can be realized by a single primitive operation for the system, and it is possible to extract operation items without omissions and omissions and to derive test specification items by subsequent operations.

System Behavior Analysis In FIG. 4, when a system behavior element name that is the same as or similar to the input system behavior element name has been previously input, the term dictionary management unit 11 points this out. This makes it possible to suppress redundant expressions including duplication in the system behavior analysis diagram 4.

System Behavior Analysis Example of Creation of FIG. 4 FIG. 3 is a system behavior analysis diagram of the user operation pattern “2. Delete the treatment order” in the same system as FIG.
Is shown. In this system behavior analysis Figure 4,
System behavior elements such as “2-1. Search for treatment order” related to deletion of treatment order are arranged according to the procedure of the deletion process, and the transition is represented by an arrow. What kind of system behavior the operation pattern specifically follows is executed.

Here, as described above, the "system behavior element" means "a series of user operations" on the system.
And "the behavior of the system" against it in a certain size. For example, the system behavior element “2-3. Delete an order” in the example of FIG. 3 combines the operation of the user who instructs the order deletion and the behavior of the system that executes the order deletion process in accordance with the operation. It is a representation.

The user operation pattern as shown in FIG. 2 is described by focusing on how to use the system, but by considering the processing realized by the operation pattern as well, It is also possible to interpret this as a system behavior element. In this case,
System behavior analysis of elements "2-1" and "2" in Figure 4
-2 ", it is possible to refer to the user operation pattern in the system behavior analysis FIG.

<System Behavior Hierarchical Analysis Unit 5> When actually testing the software system, each of the primitive levels such as “press button”, “select menu item”, and “enter character string”. Regarding the operation of, the behavior that the system behaves must be explicitly described as a test specification. However, in a large-scale and complicated software system targeted by the present invention, the number of operations at the primitive level is huge, and one function is realized from a large number of operations. , It becomes difficult to understand the relationship between the semantic structure of the software system and individual operations, and the dependency relationship between each operation. Therefore, it is not realistic to directly express the behavior of the system at such a primitive level of operation, because there is a high possibility that the operation may be missed / missed.

Therefore, the behavior of the entire target system described by the above-described user operation pattern evaluation unit 1 and the system behavior analysis unit 3 that analyzes the system behavior in each user operation pattern extracted therein is described as the system behavior hierarchy. The analysis unit 5 analyzes and creates, for example, a hierarchical table (system behavior hierarchy analysis table) from a rough level starting from a user operation pattern to a detailed level. This makes it easier to understand the behavior of the target system. Then, by extracting operation items based on this system behavior hierarchy analysis table, it is possible to suppress omission or omission of operations.

The system behavior hierarchy analysis unit 5 uses the term dictionary management unit 11 to duplicate the user operation pattern list 2 described in the form of a diagram or a table and the system behavior analysis diagram 4 corresponding to each user operation pattern. Check the dependency relationship and the hierarchical structure of the two while extracting the same or similar description, define (reconfigure) again if necessary, and analyze the hierarchical structure. Export to.

FIG. 4 is a diagram showing a process and data flow for creating the system behavior hierarchy table 6 in the system behavior hierarchy analysis unit 5. In the system behavior hierarchy analysis unit 5, first, the system behavior analysis diagram 4 itself or a description equivalent thereto is analyzed using the term dictionary management unit 11 to extract a duplicate or similar portion in the flow of the system behavior. Present to the user. The user determines whether or not these overlapping or similar portions presented by the system behavior hierarchy analysis unit 5 are the same as the flow of the system behavior, and inputs the determination result. The system behavior hierarchy analysis unit 5 receives the input from the user, collects the overlapping / similar portions, makes them independent as user operation patterns, and defines the dependency relationship with other user operation patterns and the system behavior analysis reference from FIG. .

When the described flow of system behavior is so long as to hinder understanding or there are many branches, these are presented / pointed out to the user to prompt correction. Here, the user specifies a set of system behavior elements that can have one meaning as a group and gives them names, thereby making a system behavior element composed of a plurality of small unit system behavior elements. Can be defined. For details, prepare a description consisting of small units of system behavior elements as a sub-figure, and form a hierarchical structure by referring to the newly summarized system behavior elements.

By repeating the above operation, the user operation pattern list 2 and the system behavior analysis diagram 4 are hierarchically
And can be described without duplication. FIG. 5 shows the hierarchical relationship formed by the finally created diagrams.

Next, the system behavior hierarchy analysis unit 5 converts the hierarchy structure of the user operation pattern list 2 and the system behavior analysis diagram 4 into a table format and writes it out.

With this, it is possible to list the system behaviors that can be realized by the primitive operation, and it becomes easy to extract the operation using the operation extracting unit 7 described below.

Example of Creating System Behavior Hierarchy Table 6 FIG. 6 shows an example (excerpt) of the system behavior hierarchy table 6 in the hospital information management system. The leftmost column shows the user operation pattern located at the top of the hierarchical structure, and the right side shows the user operation pattern / system behavior that is the element of the sub-drawing of the corresponding left element. In this example, for a user operation pattern "2. delete a treatment order", a sequence of system behavior that realizes the pattern "2-1. Search for treatment order",
"2-2. Confirm order information" and "2-3. Delete order" are arranged on the right side, and "2-3. Delete order" is a system behavior element that is an element of the sub-diagram. The sequences are listed on the right.

FIG. 7 shows the flow of creating the system behavior hierarchy analysis table. In this example, the system behavior hierarchy analysis unit 5 first describes, in the leftmost column of the table, the highest-level user operation pattern, “2. Delete inspection order”. Next, the links in the hierarchical structure are followed to find the corresponding sub-diagram, and the system behavior that is the element is sequentially described in the right column. Here, "2-1. Search for treatment order"
For example, the elements described in the second column correspond to this. At this time, when the system behavior further refers to the sub-diagram, the link is followed, and the system behavior element is further described in the right column in the same way as the system behavior of the sub-diagram is described for the user operation pattern. Will be described in. When the user operation pattern or the system behavior refers to another user operation pattern in the middle, the reference destination user operation pattern is recorded in the rightmost column. The system behavior hierarchy analysis unit 5 is a unit that automatically repeats these operations to create a table as shown in FIG.

These elements in the system behavior hierarchy table 6 form a tree structure with the user operation patterns listed in the leftmost column as the root, and the element corresponding to that leaf (on the right side of itself in a certain row). (There is no element in) is a system behavior element that can be realized by a single primitive operation. As will be described later, the operation extracting unit 7 extracts operations for realizing each of these leaf elements of the tree structure.

The above-mentioned function can also be realized by converting the information of the user operation pattern list 2 / system behavior analysis FIG. 4 into a structured text-based general-purpose data format such as XML. in this case,
The system behavior hierarchy analysis unit 5 performs an operation of once converting the user operation pattern list 2 / system behavior analysis FIG. 4 into a data format structured as an intermediate expression format, and further writing it out in a table format. become.
By adopting such a format, the management and processing of the functional specification data described by the use case diagram / operation flow diagram are facilitated, and the use of these data for other purposes is promoted.

<Operation Extraction Unit 7> The operation extraction unit 7 is a system that can be realized by a single operation using the operation extraction unit 7 based on the created system behavior hierarchy table 6 and the product specifications 13 of the software. A behavior element is extracted and a list of operation items for realizing the element is created.

Usually, in a software system,
There are multiple user operations that achieve equivalent system behavior. For example, taking the print function of a general word processor as an example, "Select" Print "from the menu", "Click the" Print "button on the toolbar",
User operations such as "use shortcut keys"
Realizes the equivalent system behavior of "printing." In software system testing, it is necessary to ensure that the software operates correctly according to specifications at the level of primitive operation that realizes a certain system behavior element.

As described above, conventionally, in a large-scale / complex system, it is very difficult to extract a primitive level operation that is to be extracted here.・ Clipping is easy to occur, and preventing it is an urgent issue.

In the present embodiment, since the system behavior hierarchy table 6 created by the system behavior hierarchy analysis unit 5 described above is used, in the functional structure of the system of the system behavior elements that can be realized by a single primitive operation extracted. It is easy to understand the positioning. Therefore, it becomes possible to easily find the omission or omission of the system behavior element required when extracting the operation item, and it is possible to create a highly reliable and comprehensive operation item list.

The operation extracting unit 7 extracts the system behavior elements that can be realized by the primitive operation from the system behavior hierarchy table 6 described above, and displays the list together with the system behavior hierarchy table 6. This allows the user to easily understand the positioning of the listed system behavior elements in the functional structure of the entire system. Therefore, the omission / leakage of the system behavior elements can be suppressed, and the omission / leakage of the test specification items resulting from these can also be suppressed. Also,
Even when operations that realize the same system behavior elements are described in multiple locations in the functional operation specifications, it is easy to understand the system functional structure, so the system behavior elements that realize those operations are specified. The work to do is easy.

Next, based on the information in the function operation specification 13,
Expand these system behavior element lists into individual operations,
I will describe it. When the same or similar operation has been input in the past with respect to the input operation, the term dictionary management unit 11
Points out this. The user who has been pointed out determines whether these operations are completely different, the same or similar, inputs them to the term dictionary 12, and then adds them to the operation item list. When the same is input, the test item of the same operation item can be reused in the test specification item creating unit 9 described below.

The operation extraction unit 7 displays the system behavior hierarchy table 6 to realize the above procedure, extracts system behavior elements that can be realized by a primitive operation from the system behavior hierarchy table 6, and extracts the list of those elements into individual primitives. It is possible to develop and describe it in a manual operation and manage the terms of the operation items to be added.

Example of Creating Operation Item List FIG. 8 shows an example (excerpt) of an operation item list created using the system behavior hierarchy table of FIG. The operation extracting unit 7 first displays the system behavior hierarchy table 6 as in columns 1 to 3 in the table shown in FIG. Next, the system behavior element in which the right side of itself is blank, that is, the leaf element of the tree structure is extracted from that and listed in the rightmost column (column 4) of the table. Some of the extracted system behavior elements refer to other user operation patterns.
In that case, the reference user operation pattern is further described in the right column.

Next, based on the functional operation specification, the operation for realizing each system behavior is entered as shown in column 5. Here, when the same or similar operation item is input, the term dictionary management unit 11 points out, so it is determined whether the operation is the same as or similar to the previously input operation, or a completely different operation. And term dictionary 1
Enter 2. FIG. 9 shows the flow of processing by the operation extracting unit 7 described above.

<Test Specification Item Creation Unit 9> In the present embodiment, as the final step, the test specification item creation unit 9 is used to analyze each operation item in the operation item list (list), and the test case (test specification) is analyzed. Item). In the analysis of operation items, the viewpoints for deriving test cases and their criteria are set focusing on "(1) State that can be acquired for system" and "(2) Value / state of data used / defined by operation" To do. An example of viewpoints / criteria is shown in FIG. In this way, the above (1) and (2) are embodied according to the screen configuration and the structure of data to be handled based on the functional operation specifications of the target software system (in FIG. 10, some standards are taken as examples). Then, the prerequisites and expected results for each operation item extracted by the operation extracting unit 7 are covered accordingly.

FIG. 11 shows an example of a test case created by analyzing the operation items using the operation item analysis viewpoints / criteria shown in FIG. For example, considering the operation of "selecting" order-delete order "from the menu", first, from the viewpoint of [Window], the window name "treatment work main screen" is specified as the window on which this operation is performed. Also, from the perspective of [screen state],
Conditions such as "list display mode" and "order information display mode" are derived as those that affect the operation result. The test specification item creation unit 9 supports the derivation of test cases and their description by comparing the above-mentioned viewpoints / criteria, which serve as a guide for precondition coverage, with each operation item.

According to the test specification creation support apparatus of this embodiment described above, the following operational effects can be obtained.

First, in the test specification creation support apparatus of this embodiment, the software specification is briefly described by a diagram group having a hierarchical structure. Therefore, regardless of the scale and complexity of the target software, the abstraction level that is easy to understand is uniformly described for each layer. Therefore, it is possible to facilitate the description of the behavior of the system according to the operation pattern of the user, and it is easy to understand. In the present embodiment, the restrictions on the description method and the format are very relaxed as compared with the conventional formal specification description, and the work load at the time of creating the chart group is relatively small.

Then, the behavior of the software to be tested can be automatically analyzed based on the user operation pattern list 2 forming the tree structure and the system behavior analysis FIG.
This makes it possible to comprehensively extract system behavior elements that can be executed by a single operation that can be realized by the software. Therefore, it is possible to significantly speed up and facilitate the subsequent work of detecting operation items and creating test specification items, compared to manual work, and creating test specifications with few omissions and high comprehensiveness. It will be possible.
It should be noted that the present invention is not limited to the above-described embodiment, and can be variously modified and implemented.

[0069]

According to the present invention described above, the creator can quickly and easily create a highly comprehensive test case (test specification item) group that constitutes a test specification for the target software. Moreover, it is possible to flexibly respond to a request accompanying a specification change of the target software.

[Brief description of drawings]

FIG. 1 is a block diagram showing a schematic configuration of a test specification creation support device according to an embodiment of the present invention.

FIG. 2 is a diagram showing an example of a user operation pattern list (graphic format).

FIG. 3 is a diagram showing an example of a system behavior analysis diagram.

FIG. 4 is a block diagram showing the flow of processing in a system behavior hierarchy analysis diagram.

FIG. 5 is a diagram conceptually showing a hierarchical structure of a system specification including a user operation pattern list and a system behavior analysis diagram.

FIG. 6 is a diagram showing an example of a system behavior hierarchy analysis table.

FIG. 7 is a block diagram showing a process of creating a system behavior hierarchy analysis diagram using the system behavior analysis diagram.

FIG. 8 is a diagram showing an example of an operation item list.

FIG. 9 is a block diagram showing a process of creating an operation item list using a system behavior hierarchy analysis table.

FIG. 10 is a diagram showing an example of viewpoints for extracting test specification items and their criteria.

FIG. 11 is a diagram showing an example of a test specification (test specification item list).

[Explanation of symbols]

1 ... User operation pattern evaluation unit 2 ... User operation pattern list 3 ... System behavior analysis unit 4: System behavior analysis diagram 5 ... System behavior hierarchy analysis diagram 6 ... System behavior hierarchy table 7 ... Operation extraction unit 8 ... Operation item list 9 ... Test specification item creation section 10 ... Test specifications 11 ... Term dictionary management unit 12 ... Term dictionary 13 ... Product specifications

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Masayuki Hirayama             1st Komukai Toshiba-cho, Sachi-ku, Kawasaki-shi, Kanagawa             Inside the Toshiba Research and Development Center F-term (reference) 5B042 HH19

Claims (7)

[Claims] 1. A test specification creation support device for supporting creation of test specifications of a target system, user operation pattern information representing a typical operation pattern when a user operates the system, and the operation pattern. An input means for inputting system behavior analysis information indicating the behavior of the system analyzed with a degree of detail based on, a system in which the user operation pattern information and the system behavior analysis information are analyzed, and both are hierarchically combined. System behavior hierarchy analysis means for creating a behavior hierarchy table, operation item extraction means for comprehensively extracting operation items from the system behavior hierarchy table, and a predetermined viewpoint and standard for the extracted operation items. And a test specification item creating means for creating a test specification item in accordance with Apparatus. 2. The system further comprises a term dictionary composed of terms for identifying the user operation pattern or the behavior of the system, and the system behavior hierarchy analysis unit refers to the term dictionary to describe the user operation pattern information and the system. The test specification creation support apparatus according to claim 1, wherein dependency relationships between elements in the behavior analysis information are analyzed. 3. The system behavior hierarchy analysis means comprises means for modifying and reconstructing the hierarchy structure of the system behavior hierarchy table according to a designation from the user. The test specification creation support device described in. 4. The test specification creation support apparatus according to claim 1, wherein the test specification item includes a precondition and a result of the operation when the user gives the operation. . 5. A test specification creation support device for supporting creation of a test specification of a target system, wherein a user operation pattern information representing a typical operation pattern when a user operates the system is used to generate the operation pattern. The behavior of the system is identified from a user operation pattern evaluation unit that extracts a term to be identified and registers the term in a term dictionary, and system behavior analysis information that represents the behavior of the system analyzed with a degree of detail based on the operation pattern. A system behavior analysis means for extracting a term and registering it in the term dictionary, and analyzing a dependency relationship between each component of the user operation pattern information and the system behavior analysis information with reference to the term dictionary, System behavior hierarchy analysis means for creating a system behavior hierarchy table that is hierarchically combined; An operation item extracting means for comprehensively extracting the operation items, and a test specification item creating means for creating a test specification item according to a predetermined viewpoint and a standard for the extracted operation items. A test specification creation support device characterized in that 6. A test specification creation support program for supporting creation of a test specification of a target system, the user operation pattern information indicating a typical operation pattern when a user operates the system, and A function of storing in the storage means system behavior analysis information indicating the behavior of the system analyzed with a degree of detail based on an operation pattern, analyzing the user operation pattern information and the system behavior analysis information, and hierarchically analyzing both. A system behavior hierarchy analysis function for creating a combined system behavior hierarchy table, an operation item extraction function for comprehensively extracting operation items from the system behavior hierarchy table, a predetermined viewpoint and criteria for the extracted operation items Test specification item creation function for creating test specification items according to Like creation support program. 7. A test specification creation support program for supporting creation of a test specification of a target system, wherein a user operation pattern information representing a typical operation pattern when a user operates the system is used to generate the operation pattern. A user operation pattern evaluation function for extracting a term to be identified and registering it in a term dictionary, a term for identifying the behavior of the system from system behavior analysis information indicating the behavior of the system analyzed by the degree of detail based on the operation pattern System behavior analysis function for extracting and registering in the term dictionary, analyzing the dependency relationship between each component of the user operation pattern information and the system behavior analysis information with reference to the term dictionary, and hierarchically analyzing both. A system behavior hierarchy analysis function for creating a system behavior hierarchy table combined with A computer implements an operation item extraction function for comprehensively extracting operation items, and a test specification item creation function for creating test specification items according to a predetermined viewpoint and criteria for the extracted operation items. A test specification creation support program for.