JP2022041197A - Program, method, information processing apparatus, and system - Google Patents

Abstract

To reduce the burden of test design while maintaining test quality by effectively using test design documents created in the past.SOLUTION: A program causes a processor to execute the steps of: storing test design documents and elements dissolved from the test design documents in databases prepared for each of layers corresponding to applications; and selectively presenting the test design documents or elements stored in each database in accordance with a request from a user.SELECTED DRAWING: Figure 9

Description

The present disclosure relates to programs, methods, information processing devices, and systems.

The software is functionally tested prior to launch to ensure its quality. The test is designed based on the contents of the software specifications so that the desired quality is guaranteed under the development schedule and budget set by the software development company.

JP-A-2020-98413

Advanced knowledge and abundant experience are required to design a test according to the client's intention. In order to reduce the burden of creating a test design document, Patent Document 1 provides a database that stores a plurality of test viewpoints indicating viewpoints when performing a test. Then, test cases are generated from the specification items extracted from the system specifications and the test viewpoints stored in the database.

In Patent Document 1, the test viewpoint is stored in the database, but this test viewpoint is not based on the test design document created in the past.

The purpose of this disclosure is to effectively use the test design documents created in the past and reduce the burden of test design while maintaining the quality of the test.

In order to solve the above problems, the program of the present disclosure includes a step of storing a test design document and elements decomposed from the test design document in a database provided for each layer corresponding to the business, and a user. In response to the request from, the test design document stored in each database or the step of switching and presenting the elements is executed.

According to the present disclosure, it is possible to effectively use the test design document prepared in the past and reduce the burden of the test design while maintaining the quality of the test.

It is a figure which shows the whole structure of the system of this embodiment. It is a block diagram which shows the structure of the terminal apparatus included in the system of this embodiment. It is a block diagram which shows the functional configuration of the server included in the system of this embodiment. It is a figure which shows the list of confirmation items included in the test design document. It is a figure which shows the pattern table included in a test design document. It is a figure which shows the data structure of a project DB. It is a figure which shows the data structure of a client DB. It is a figure which shows the data structure of a standard DB. It is a figure which shows typically the concept of the system which concerns on this embodiment. It is a figure which shows the screen for selecting a desired project. It is a figure which shows the screen for displaying the test design document created in a predetermined project. It is a figure which shows the screen for displaying the test viewpoint created in a predetermined project. It is a figure which shows the screen for displaying the pattern created in a predetermined project. It is a figure which shows the screen for displaying the test design document shared in a company. It is a figure showing the screen for displaying the pattern shared in a company. It is a figure showing the screen for displaying the test viewpoint shared in a company. It is a figure which shows the screen for displaying the test design document which is stored in the standard knowledge. It is a figure which shows the screen for displaying the pattern which is stored in the standard knowledge. It is a figure which shows the screen for reading the test viewpoint stored in the standard knowledge. It is a figure which shows the list display of a test design document. It is a figure which shows the screen for creating the confirmation item list. It is a figure which shows the list display of the test viewpoint. It is a figure showing the creation screen of the confirmation item list in which "test viewpoint" and "confirmation item" are input. It is a figure which shows the management screen of a pattern. It is a figure which shows the list display of a pattern. It is a figure which shows the management screen of a pattern. It is a flowchart which shows the process flow of the control part at the time of proposing the modification of a test design document or an element according to the modification of a functional specification. It is a figure showing the screen which displays the test design document based on the change of the functional specification, or the correction proposal of the element of the test design document.

Hereinafter, embodiments will be described with reference to the drawings. It should be noted that the present embodiment described below does not unreasonably limit the content of the present disclosure described in the claims. Further, not all of the configurations described in the present embodiment are essential constituent requirements of the present disclosure.

<Overview>
The system 1 according to the present embodiment decomposes the created test design document into elements, and stores the test design document and the decomposed elements for each layer related to the business. Then, the system 1 presents a stored test design document or element in response to a request from the test designer, the administrator, or the like.

In this embodiment, the test design document is data for which a test for inspecting the function of the inspection target is designed. The inspection target represents an inspection target, and is, for example, hardware or software developed in a predetermined project. Inspection targets include, for example, prototypes, intermediate products, and final products. The function represents the function of various components constituting the inspection target.

<1 Overall configuration>
FIG. 1 is a diagram showing an overall configuration of the system 1 of the present embodiment. As shown in FIG. 1, the system 1 includes a terminal device 10 and a server 20. The terminal device 10 and the server 20 are connected to each other so as to be able to communicate with each other via the network 80 by using a wired or wireless communication standard. The network 80 is realized by, for example, the Internet and / or a communication network provided by a communication carrier. In the illustrated example, a plurality of terminal devices 10 are included in the system 1.

Although FIG. 1 shows a case where the server 20 is one computer, the server 20 may be realized by combining a plurality of computers. Further, although FIG. 1 shows a case where the number of terminal devices 10 is one, the number of terminal devices 10 accommodated in the system 1 may be a plurality of devices.

The terminal device 10 is a terminal used by a user who uses the service provided by the server 20. For example, the terminal device 10 is a terminal used by a test designer who creates a test design document. The terminal device 10 is realized by, for example, a stationary PC (Personal Computer), a laptop PC, a head-mounted display, or the like. Further, the terminal device 10 may be a portable computer such as a smartphone or a tablet terminal.

As shown in FIG. 1, the terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 15, a storage 16, and a processor 19. The communication IF 12, the input device 13, the output device 14, the memory 15, the storage 16, and the processor 19 are connected to each other so as to be communicable with each other via, for example, a bus.

The communication IF 12 is an interface for transmitting and receiving signals because the terminal device 10 communicates with an external device. The input device 13 is an input device for receiving an input operation from a user (employee). The input device 13 includes, for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, and the like. The output device 14 is an output device for presenting information to the user. The output device 14 includes, for example, a display, a speaker, and the like.

The memory 15 is for temporarily storing a program, data processed by the program or the like, and is realized by, for example, a volatile memory such as a DRAM (Dynamic Random Access Memory). The storage 16 is a storage device for storing data, and is realized by, for example, a non-volatile memory such as a flash memory or an HDD (Hard Disc Drive). The processor 19 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

The server 20 is a device that stores the created test design documents and presents the stored test design documents to the user in response to a request from the user of the terminal device 10. The server 20 is, for example, a computer connected to the network 80.

As shown in FIG. 1, the server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29. The communication IF 22, the input / output IF 23, the memory 25, the storage 26, and the processor 29 are connected to each other so as to be communicable with each other via, for example, a bus.

The communication IF 22 is an interface for transmitting and receiving signals because the server 20 communicates with an external device. The input / output IF 23 functions as an interface with an input device for receiving an input operation from the user and an output device for presenting information to the user. The memory 25 is for temporarily storing a program, data processed by the program, or the like, and is realized by, for example, a volatile memory such as a DRAM.

The storage 26 is a storage device for storing data, and is realized by, for example, a non-volatile memory such as a flash memory or an HDD. The storage 26 does not necessarily have to be realized by a single circuit. The storage 26 may be realized by, for example, a plurality of storage circuits. The processor 29 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

<1.1 Configuration of terminal equipment>
FIG. 2 is a block diagram showing a configuration of a terminal device 10 included in the system 1 of the present embodiment. As shown in FIG. 2, the terminal device 10 includes a communication unit 121, an input device 13, an output device 14, a storage unit 170, and a control unit 180.

The communication unit 121 performs a process for the terminal device 10 to communicate with another device. The communication unit 121 performs transmission processing on the signal generated by the control unit 180, and transmits the signal to the outside (for example, the server 20). The communication unit 121 performs reception processing on the signal received from the outside and outputs the signal to the control unit 180.

The input device 13 is a device for a user who owns the terminal device 10 to input an instruction. The input device 13 is realized by, for example, a mouse 131, a keyboard 132, a touch-sensitive device 133 to which an instruction is input by touching an operation surface, and the like. The input device 13 converts an instruction input from the user into an electric signal, and outputs the electric signal to the control unit 180. The input device 13 is not limited to a physical operation device such as a mouse 131 and a keyboard 132. The input device 13 may include, for example, a receiving port that receives an electric signal input from an external input device.

The output device 14 is a device for presenting information to the user who owns the terminal device 10. The output device 14 is realized by, for example, a display 141 or the like. The display 141 displays data such as images, moving images, and texts according to the control of the control unit 180. The display 141 is realized by, for example, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like.

The storage unit 170 is realized by, for example, a memory 15 and a storage 16, and stores data and a program used by the terminal device 10.

The control unit 180 is realized by the processor 19 reading a program stored in the storage unit 170 and executing an instruction included in the program. The control unit 180 controls the operation of the terminal device 10. Specifically, for example, the control unit 180 exerts functions as an operation reception unit 181, a transmission / reception unit 182, and a display control unit 183.

The operation receiving unit 181 performs a process for receiving the user's operation input from the input device 13. The transmission / reception unit 182 performs a process for the terminal device 10 to transmit / receive data to / from an external device such as a server 20 according to a communication protocol. The display control unit 183 controls the output device 14 in order to present various information to the user.

<1.2 Server functional configuration>
FIG. 3 is a block diagram showing a functional configuration of the server 20 included in the system 1 of the present embodiment. As shown in FIG. 3, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

The communication unit 201 performs a process for the server 20 to communicate with an external device.

The storage unit 202 stores data and programs used by the server 20. For example, the storage unit 202 stores a project database (DB) 281, a client database (DB) 282, a standard database (DB) 283, and a functional specification 284.

The project DB 281 is a database for storing the test design document created in a predetermined project and the elements decomposed from this test design document. Further, the project DB 281 also stores the test design document currently created in the predetermined project and the elements decomposed from this test design document.

The project DB 281 is, for example, a test design document created in the project or a database for sharing elements. In other words, it is possible to share what kind of test design document or element was created in this project among the people involved in the project. The project DB 281 is provided for each planned project, for example.

In the present embodiment, the test design document defines, for example, the information in which the items for which the behavior is confirmed in the test is defined, and the actual test case which is set based on the contents to be confirmed and the conditions of the expressed behavior. Includes information that has been made. Specifically, the information in which the items for which the behavior is confirmed in the test is specified is included in the test design document as, for example, a list of confirmation items. The information in which the actual test cases are specified is included in the test design document as, for example, a pattern table.

FIG. 4 is a schematic diagram showing an example of a list of confirmation items included in the test design document. In the example shown in FIG. 4, a test design document for inspecting the login function in a predetermined software will be described. The list of confirmation items shown in FIG. 4 includes a first area 31 in which the meta information of the test design document is stored, and a second area 32 in which the contents confirmed in the test are stored.

In the first area 31, for example, the item "title", the item "project name", the item "product name", the item "management number", the item "version", the item "creation date", the item "creator", and the item "Last updated date" and item "Updated by" are included. The information contained in the first region 31 is not limited to these. Information on any of these may not be present, or information other than these may be included.

The second area 32 serves, for example, as a so-called basic design document in which the outline of the inspection is defined. In the second area 32, for example, "test target item / target function", "test procedure", "test viewpoint", "expected value" and the like are defined. "Test target item / target function" represents an item / function to be inspected. In FIG. 4, the case where the inspection target is the login function is shown, and the information stored in the item "test category", the item "major function", the item "medium function", and the item "small function" includes " "Test target item / target function" is specified.

The "test procedure" represents the order in which the tests are performed. In FIG. 4, the order in which the tests are performed is defined by the order in which the "test viewpoints" are arranged.

The "test viewpoint" represents the viewpoint (idea) on which the test is based. The "test viewpoint" is defined by the information stored in the item "test viewpoint" in FIG. Further, the second area 32 includes an item "confirmation item". The item "confirmation item" represents information for identifying the test to be performed. The information stored in the item "test viewpoint" and the information stored in the item "confirmation item" are associated with each other.

The "expected value" represents the behavior expected to be expressed at the time of confirmation. The "expected value" is defined by the information stored in the item "expected value" in FIG.

The information contained in the second region 32 is not limited to these. Information on any of these may not be present, or information other than these may be included.

FIG. 5 is a schematic diagram showing an example of a pattern table included in the test design document. The pattern table shown in FIG. 5 is included in the same test design document as the list of confirmation items shown in FIG. The pattern table shown in FIG. 5 includes a first area 31 in which the meta information of the test design document is stored and a third area 33 in which the pattern is stored. The pattern defines the content to be confirmed, the condition of the behavior expressed by the confirmation process, and the specific test case in which the confirmation content and the condition are combined. The first region 31 is the same as the first region 31 shown in FIG.

In the third region 33, for example, at least one pattern is set according to the function to be inspected. In the third area 33 shown in FIG. 5, two patterns for inspecting the login function, that is, a login pattern and a password forgotten correspondence pattern are stored. The pattern number representing each pattern is stored in, for example, the item “No”.

In the pattern stored in the third region 33, the "content to be confirmed" is defined by, for example, the information stored in the item "factor" and the item "level". The "condition of behavior expressed by the confirmation process" is defined by, for example, the condition described in the item "expected value". The "specific test case" is defined by, for example, each column starting with "1", "2", "3", and so on. The processing actually performed in the test is represented by a white circle in the column.

From the test design document, as the above elements, for example, information for defining a necessary test and information in which a specific test case is set are decomposed. That is, the "test viewpoint", "confirmation item", and "pattern" are decomposed from the test design document.

The client DB 282 is a database for storing the test design document created in the project planned in the company and the elements decomposed from this test design document. The client DB 282 is, for example, a database for sharing test design documents or elements across projects within the same company. In other words, it is possible for in-house test designers to share what kind of test design document or element was created in another project in the company. The client DB 282 is provided for each company, for example.

The standard DB 283 is a database for storing test design documents created in a plurality of companies and elements decomposed from the test design documents. The standard DB 283 is a database for sharing test design documents or elements as an overall shared knowledge across companies. In the standard DB 283, for example, a stored test design document and an element are given an identifier representing an attribute. A plurality of types of attributes can be set, and for example, there are types of industry / industry, system type, and process type. By using an identifier representing an attribute, it is possible to classify a test design document or an element according to the attribute.

The functional specification 284 is data in which specifications for the functions of the inspection target are described. The test designer creates a test design document with reference to the functional specification document 284. The functional specification 284 includes, for example, an area in which detailed specifications of functions are stored and an area in which message definitions are stored. When the functional specification 284 is created by spreadsheet software, these areas are realized, for example, in different slides. In the functional specification 284, the data itself may not be stored in the storage unit 202. For example, the functional specification 284 may be link information to the functional specification stored on the cloud. Further, the functional specification 284 may be link information to a predetermined corresponding portion of the functional specification stored on the cloud. For example, on the cloud, the functional specifications describe the functional specifications for each predetermined display unit. The predetermined display unit is, for example, a page, a ticket, or the like. For example, update information is attached to the functional specification, and when a change occurs in the specification, information about the change is described in the update information.

The control unit 203 is realized by the processor 29 reading the program stored in the storage unit 202 and executing the instruction included in the program. The control unit 203 controls the operation of the server 20. Specifically, for example, the control unit 203 functions as a transmission / reception unit 2031, a storage control unit 2032, an acquisition unit 2033, a presentation unit 2034, a detection unit 2035, and a calculation unit 2036.

The transmission / reception unit 2031 controls a process in which the server 20 transmits / receives data to / from an external device such as a terminal device 10 according to a communication protocol.

The storage control unit 2032 controls the storage of information in the storage unit 202. Specifically, the storage control unit 2032 stores the test design document and the elements decomposed from the test design document in the project DB 281, the client DB 282, or the standard DB 283.

More specifically, the storage control unit 2032 stores the test design document created by the user via the terminal device 10 and the elements decomposed from the test design document in the project DB 281. Further, when receiving an instruction to share the test design document or element stored in the project DB 281 within the company, the storage control unit 2032 transfers the test design document and element stored in the project DB 281 to the client DB 282. Also remember. Further, when the test design document or the element to be stored in the project DB 281 or the client DB 282 is instructed to be shared by the entire company, the storage control unit 2032 stores the test design document or the element in the project DB 281 or the client DB 282. The test design document and elements are also stored in the standard DB 283.

The storage control unit 2032 attaches a tag to the test design document and the elements decomposed from the test design document, and stores the test design document in the project DB 281, the client DB 282, or the standard DB 283. The tag is, for example, information that individually represents the characteristics of the test. The tag can be arbitrarily set by, for example, the person who created the test design document.

The acquisition unit 2033 acquires information from the storage unit 202. Specifically, the acquisition unit 2033 acquires predetermined information from the database designated by the user among the project DB 281, the client DB 282, and the standard DB 283.

The acquisition unit 2033 may accept the input of text information from the user. The acquisition unit 2033 collates the input text information with the test design document stored in the database designated by the user, the name of the element, the tag, and the like. The acquisition unit 2033 acquires a test design document or an element having a name or a tag that matches the input text information. Further, the acquisition unit 2033 may acquire a name including the input text information, a test design document with a tag, or an element. Further, the acquisition unit 2033 may acquire a test design document or an element with a name or a tag estimated from the input text information.

Further, the acquisition unit 2033 acquires the test design document or the element associated with the changed functional specification document 284 from the storage unit 202.

The presentation unit 2034 presents the acquired information to the user.
The detection unit 2035 detects whether or not there is a change in the functional specification 284.
The calculation unit 2036 calculates an index value based on the diversion of the accumulated data.

<2 data structure>
6 to 8 are diagrams showing the data structure of the database stored in the server 20. In FIGS. 6 to 8, a case where the “test viewpoint”, the “confirmation item”, and the “pattern” are decomposed from the test design document will be described as an example. It should be noted that FIGS. 6 to 8 are examples, and data not described is not excluded.

FIG. 6 is a diagram showing a data structure of the project DB 281. As shown in FIG. 6, the test design document 2811, the pattern 2812, and the test viewpoint 2813 are stored in the project DB 281. Each of the records of the test design document 2811 includes an item "file name", an item "designer", an item "reviewer", an item "status", an item "link", an item "latest update" and the like.

The item "file name" stores the name of the test design document.
The item "designer" remembers the name of the person who created the test design document. In addition, the item "designer" stores the name of the person who creates the test designer.

The item "reviewer" stores the name of the person who reviewed the test design document.
The item "status" stores the current state of the test design document. In the item "status", for example, "Working" indicating that the work is underway, "Reviewing" indicating that the work is being confirmed, and "Done" indicating that the product has been completed are described.

The item "link" stores the functional specification associated with the test design document. In the item "link", the functional specification itself may be associated, but the corresponding part of the functional specification may be associated. The relevant part of the functional specification may be stored, for example, as a slide, a row, a cell, or the like when the functional specification is spreadsheet software.
The item "Latest update" stores the latest date and time when the test design document was updated.

Each of the records of the pattern 2812 includes an item "pattern name", an item "pattern number", an item "file name", an item "latest update", and the like.
The item "pattern name" stores the name of the pattern.
The item "pattern number" stores a unique number assigned to the pattern.

The item "file name" stores the name of the test design document of the disassembly source.
The item "latest update" stores the latest date and time when the pattern was updated.

Each of the records of the test viewpoint 2813 includes the item "test viewpoint", the item "confirmation item", the item "classification 1", the item "classification 2", the item "latest update" and the like.
The item "test viewpoint" stores the information described in the item "test viewpoint" of the confirmation item list.
The item "confirmation item" stores the information described in the item "confirmation item" of the confirmation item list.

The item "Category 1" stores information about the first classification attached to the test viewpoint. The information stored in the item "Category 1" is set by the user when inputting the test viewpoint, for example, in the stage of creating the test design document. The information stored in the item "classification 1" is, for example, selected and set by the user from a plurality of preset items.

The item "Category 2" stores information about the second classification attached to the test viewpoint. The information stored in the item "classification 2" is set by the user when inputting the test viewpoint, for example, in the stage of creating the test design document. The information stored in the item "classification 2" is, for example, selected and set by the user from a plurality of preset items.
The item "Latest update" stores the latest date and time when the test viewpoint was updated.

FIG. 7 is a diagram showing a data structure of the client DB 282. As shown in FIG. 7, the client DB 282 stores the test design document 2821, the pattern 2822, and the test viewpoint 2823. Each of the records of the test design document 2821 includes the item "file name", the item "tag", the item "designer", the item "project", the item "service", the item "link", the item "latest update", etc. .. The item "file name", the item "designer", the item "link", and the item "latest update" are the same items as each item of the test design document 2811 shown in FIG.

The item "tag" stores information that represents the characteristics of the test. The information of the item "tag" is automatically set when the test design document stored in the project DB 281 is stored in the client DB 282, for example, based on the information set for the project. Further, the information of the item "tag" may be arbitrarily set by the user.
The item "project" stores the name of the project in which the test design document was created.
The item "service" stores the name of the service used by the inspection target.

In addition to the test design document stored in the test design document 2811 shown in FIG. 6, the test design document 2821 includes a test design document created by another project in the same company.

Each of the records of pattern 2822 includes an item "pattern name", an item "pattern number", an item "tag", an item "file name", an item "project", an item "service", an item "latest update", and the like. The item "pattern name", the item "pattern number", the item "file name", and the item "latest update" are the same items as each item of the pattern 2812 shown in FIG.

The item "tag" stores the information attached as a tag to the test design document of the disassembly source.
The item "project" stores the name of the project in which the test design document of the division source was created.
The item "service" stores the name of the service used by the inspection target.

In addition to the pattern stored in the pattern 2812 shown in FIG. 6, the pattern 2822 includes a pattern decomposed from a test design document created by another project in the same company.

Each of the records of the test viewpoint 2823 includes the item "test viewpoint", the item "confirmation item", the item "tag", the item "classification 1", the item "classification 2", the item "latest update" and the like. The item "test viewpoint", item "confirmation item", item "classification 1", item "classification 2", and item "latest update" are the same items as each item of the test viewpoint 2813 shown in FIG.

The item "tag" stores the information attached as a tag to the test design document of the disassembly source.
In addition to the test viewpoint stored in the test viewpoint 2813 shown in FIG. 6, the test viewpoint 2823 includes a test viewpoint decomposed from a test design document created by another project in the same company.

FIG. 8 is a diagram showing a data structure of the standard DB 283. As shown in FIG. 8, the standard DB 283 stores the test design document 2831, the pattern 2832, and the test viewpoint 2833. Each of the records of the test design document 2831 is an item "file name", an item "tag", an item "designer", an item "project", an item "service", an item "attribute", an item "link", and an item "latest". "Update" etc. are included. The item "file name", item "tag", item "designer", item "project", item "service", item "link", and item "latest update" are each item of the test design document 2821 shown in FIG. It is the same item as.

The item "attribute" stores information indicating the type to which the test design document belongs. A plurality of types of attributes can be set in the item "attribute", and for example, one or more attributes can be set from the industry / industry, system type, process type, and the like. The information related to the item "attribute" is set, for example, when the test design document stored in the project DB 281 or the client DB 282 is stored in the standard DB 283. The information related to the item "attribute" is set, for example, based on the tag attached to the test design document stored in the client DB 282.

In addition to the test design document stored in the test design document 2821 shown in FIG. 7, the test design document 2831 includes a test design document created by a project of another company.

Each of the records of pattern 2832 has an item "pattern name", an item "pattern number", an item "tag", an item "file name", an item "project", an item "service", an item "attribute", and an item "latest update". ”, Etc. are included. The item "pattern name", item "pattern number", item "tag", item "file name", item "project", item "service", and item "latest update" are the items of pattern 2822 shown in FIG. It is the same item.

The item "attribute" stores information indicating the type to which the test design document of the decomposition source belongs.
In addition to the pattern stored in the pattern 2822 shown in FIG. 7, the pattern 2832 includes a pattern decomposed from a test design document created by a project of another company.

Each of the records of the test viewpoint 2833 has the item "test viewpoint", the item "confirmation item", the item "tag", the item "classification 1", the item "classification 2", the item "attribute", the item "latest update", etc. include. The item "test viewpoint", item "confirmation item", item "tag", item "classification 1", item "classification 2", and item "latest update" are the same items as each item of test viewpoint 2823 shown in FIG. be.

The item "attribute" stores information indicating the type to which the test design document of the decomposition source belongs.
The test viewpoint 2833 includes the test viewpoint stored in the test viewpoint 2823 shown in FIG. 7, as well as the test viewpoint decomposed from the test design document created by the project of another company.

<3 Summary>
FIG. 9 is a diagram schematically showing the concept of the system 1 according to the present embodiment. The project DB 281, the client DB 282, and the standard DB 283 are provided for each layer corresponding to the business. By storing the test design document 2811, pattern 2812, and test viewpoint 2813 created in the project in the project DB 281, the person involved in the project can know what kind of test design document, pattern, and test viewpoint were created in the project. It will be possible to share with each other.

In addition, by storing the test design document 2821, pattern 2822, and test viewpoint 2823 created in multiple projects planned in the company in the client DB 282, what kind of test design document, in other projects in the company, can be stored. It will be possible for in-house test designers to share whether patterns and test viewpoints have been created.

Further, by storing, for example, the selected test design document 2831, pattern 2832, and test viewpoint 2833 among the test design documents, patterns, and test viewpoints created in a plurality of companies in the standard DB 283, the attributes of the company are stored. It is possible to grasp the characteristics of each, and to propose the optimum test design when formulating the test design.

<4 Display screen>
10 to 19 are views showing a display screen displayed on the display 141 of the terminal device 10. It should be noted that FIGS. 10 to 19 are examples, and the display screen of the display 141 is not limited.
FIG. 10 is a schematic diagram showing an example of a screen for selecting a desired project. The screen shown in FIG. 10 has a first region 41, a second region 42, a third region 43, and a fourth region 44.

The first region 41 includes field objects 411 to 415, a search box 416, and a selection object 417.
The field object 411 is an object for receiving an instruction to create a new test design document.

The field objects 412 to 415 are objects for receiving the database designation from the user. Specifically, the field objects 412 to 415 are objects for accepting the designations of My Drive, project DB281, client DB282, and standard DB283, respectively.

The search box 416 is a box for accepting input of a search keyword from a user.
The selection object 417 is an object representing a user's selection with respect to the field objects 412 to 415. The selection object 417 stops on the selected object when the user selects any of the field objects 412 to 415.

In the screen shown in FIG. 10, the field object 413 that specifies the project DB 281 is selected by the selection object 417. The acquisition unit 2033 acquires data from the selected database. The presentation unit 2034 presents the acquired data to the user.

The second area 42 is an area for displaying a list of projects stored in the project DB 281. The second region 42 includes field objects 421 to 424, a search box 425, and a selection object 426.

The field objects 421 to 423 are objects for receiving the project designation from the user. Specifically, the field objects 421 to 423 are objects for accepting the designations of the projects 1 to 3, respectively. Although FIG. 10 describes the case where there are three projects as an example, there is no limit to the number of projects. The project name can be set arbitrarily.

The field object 424 is an object for receiving an instruction to create a new project. When the field object 424 is pressed, a new project is created. When creating a new project, the user enters information about the project. Information about the project includes, for example, information on the process type, system type, development scale, industry, industry, etc. of the project. The storage control unit 2032 stores, for example, information about the project in the project DB 281.

The search box 425 is a box for accepting input of the project name from the user.
The selection object 426 is an object representing the user's selection for the field objects 421 to 423. The selection object 426 stops on the selected object when the user selects any of the field objects 421 to 423.

In the screen shown in FIG. 10, the field object 421 that specifies the project 1 is selected. The acquisition unit 2033 acquires data from the project DB 281 corresponding to the project 1. The presentation unit 2034 presents the acquired data to the user.

The third area 43 is an area for displaying a list of test design documents being worked on (beginning) among the test design documents of the project selected in the second area 42. In the third area 43, the test design document being worked on is displayed in a list format. Further, the third area 43 includes a search box 431 for accepting input of a search keyword from the user.

The fourth area 44 is an area for displaying a list of test design documents that are frequently used when creating a test design document. The test design document displayed in the fourth area 44 is read from, for example, the client DB 282 or the standard DB 283. Specifically, for example, the acquisition unit 2033 is frequently used among the test design documents used in the selected project 1 and similar projects based on the information about the project stored in the project DB 281. Obtain a test design document. The presentation unit 2034 presents the acquired information to the terminal device 10. Further, the fourth area 44 includes a search box 441 for accepting input of a search keyword from the user.

When the user confirms the selection of the project in the second area 42, the presentation unit 2034 presents a screen for displaying information about the project for which the selection is confirmed.

FIG. 11 is a schematic diagram showing an example of a screen for displaying a test design document created in a predetermined project. The screen shown in FIG. 11 has a first region 41, a fifth region 45, and a sixth region 46. The first region 41 is the same as the first region 41 shown in FIG.

The fifth area 45 includes field objects 451 to 454 and selection objects 455.
The field objects 451 to 453 are objects for accepting the designation of the data to be displayed from the user. Specifically, the field objects 451 to 454 are objects for accepting the design file, the test viewpoint, and the designation of the pattern, respectively.

The field object 454 is an object for receiving an instruction to store information (test base) related to the functional specifications in the project DB 281. The information about the functional specifications is, for example, the functional specification data in a file format or the link information to the functional specifications existing on the cloud.
The selection object 455 is an object representing a user's selection with respect to the field objects 451 to 454. The selection object 455 stops on the selected object when the user selects any of the field objects 451 to 454.

In the screen shown in FIG. 11, the field object 451 that specifies the design file is selected by the selection object 455. The acquisition unit 2033 acquires data about the test design document from the project DB 281. The presentation unit 2034 presents the acquired data to the user.

The sixth area 46 is an area for displaying a list of data (test design documents) selected in the fifth area 45. In the sixth area 46, the test design document is displayed in a list format. The test design document displayed in the sixth area 46 is edited from the edit screen expanded by pressing the edit icon 461 arranged at the left end of the list.

The test design document displayed in the sixth area 46 is associated with the functional specification document managed by the project DB 281 by pressing the link icon 462 arranged at the right end of the list. Specifically, for example, when the user presses the link icon 462, the pop-up window 463 is displayed. The user presses "+ Associate test base" in the pop-up window 463, and selects the functional specification referred to when creating the test design document from the functional specifications managed in the project DB 281. At this time, the user may also input information about the relevant portion actually referred to in the functional specification. The information about the relevant part includes, for example, information such as slides, rows, cells, etc. when the functional specification is a file by spreadsheet software. Further, the information about the relevant part includes, for example, information such as a page and a ticket when the functional specification is data managed on the cloud. As a result, the test design document and the functional specification document are associated with each other. In addition, the test design document and the relevant part of the functional specification document are associated with each other.

The test design document displayed in the sixth area 46 is shared within the same company by pressing the shared icon 4617 arranged at the right end of the list. That is, the test design document is stored in the client DB 282. For example, when the user determines that the test design document should be shared with other projects, he / she presses the sharing icon 4617. When the user presses the shared icon 4617, the storage control unit 2032 stores the test design document of the record in which the shared icon 4617 is pressed in the client DB 282. The test design document stored in the client DB 282 may be deleted from the client DB 282 by, for example, a person having a predetermined authority, for example, a project leader. In this way, by making it possible to store the test design document in the client DB 282 even by an unauthorized person, the server 20 can activate the sharing of the test design document within the same company. Become. On the other hand, by making it possible for a person having a predetermined authority to delete the test design document stored in the client DB 282, it is possible to suppress an increase in unnecessary test design documents in the client DB 282. An application icon for applying for registration to the standard knowledge may be arranged at the end of the list displayed in the sixth area 46.

When the storage control unit 2032 stores the test design document in the client DB 282, the storage control unit 2032 creates tag information including information about the project of the test design document. The storage control unit 2032 attaches the created tag information to the test design document and stores it in the client DB 282.

Further, the sixth area 46 includes a search box 464 for accepting input of a search keyword from the user.
Further, the sixth region 46 includes field objects 465 to 467. The field objects 465 to 467 are objects for receiving instructions from the user.

Specifically, the field object 465 is an object for receiving an instruction to copy the test design document stored in My Drive. When the field object 465 is pressed, the display control unit 183 causes the display 141 to display the test design document stored in the storage unit 170. When any of the displayed test design documents is selected by the user, the terminal device 10 transmits the selected test design document to the server 20 and stores it in the project DB 281. The test design document newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

The field object 466 is an object for receiving an instruction to copy the test design document stored in the client DB 282 or the standard DB 283. When the field object 466 is pressed, the acquisition unit 2033 acquires the test design document stored in the client DB 282 or the standard DB 283. The presentation unit 2034 presents the acquired data to the user. When any of the presented test design documents is selected by the user, the storage control unit 2032 stores the selected test design document in the project DB 281. The test design document newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

The field object 467 is an object for receiving an instruction to upload the test design document.

When the user selects the field object 452 in the fifth area 45, the presentation unit 2034 presents a screen for displaying the data viewpoint.

FIG. 12 is a schematic diagram showing an example of a screen for displaying a test viewpoint created in a predetermined project. The screen shown in FIG. 12 has a first region 41, a fifth region 45, and a sixth region 46. The first region 41 is the same as the first region 41 shown in FIG.

In the fifth region 45, the field object 452 that specifies the test viewpoint is selected by the selection object 455. The acquisition unit 2033 acquires data about the test viewpoint from the project DB 281. The presentation unit 2034 presents the acquired data to the user.

The sixth area 46 is an area for displaying a list of data (test viewpoints) selected in the fifth area 45. In the sixth area 46, the test viewpoints are displayed in a list format.

The test viewpoint displayed in the sixth area 46 is not limited to the test viewpoint already created in the project and the test viewpoint for the test design document being created in the project. The user may select and register a test viewpoint suitable for the project in advance from the test viewpoint stored in the client DB 282 or the standard DB 283. The selected test viewpoint is stored in the project DB 281.

Whether it is a test viewpoint or a pre-registered test viewpoint for the test design document created in the project is determined from the description of the item "source" displayed in the sixth area 46. In other words, when the description of the item "source" is "project viewpoint", it means that the test viewpoint is for the test design document created in the project. Further, when the description of the item "source" is "shared viewpoint" or "standard viewpoint", it means that the test viewpoint is selected from the client DB 282 or the standard DB 283.

Further, the sixth region 46 includes field objects 468 to 4610. The field objects 468 to 4610 are objects for receiving instructions from the user.

Specifically, the field object 468 is an object for receiving an instruction to newly add a test viewpoint. When the field object 468 is pressed, the display control unit 183 causes the display 141 to display an input form for inputting a test viewpoint.

The field object 469 is an object for receiving an instruction to request the display of the test viewpoint stored in the standard DB 283. When the field object 469 is pressed, the acquisition unit 2033 acquires the test viewpoint stored in the standard DB 283. The presentation unit 2034 presents the acquired data to the user. At this time, the presentation unit 2034 may present the test viewpoint expected to be desired by the user at a position where it is easy to see. For example, the presentation unit 2034 presents the test viewpoint to the user so that the stored test viewpoint with the same or similar content as the information about the project is ranked higher.

When any of the presented test viewpoints is selected by the user, the storage control unit 2032 stores the selected test viewpoint in the project DB 281. The test viewpoint newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

The field object 4610 is an object for receiving an instruction to request the display of the test viewpoint stored in the client DB 282. When the field object 4610 is pressed, the acquisition unit 2033 acquires the test viewpoint stored in the client DB 282. The presentation unit 2034 presents the acquired data to the user. At this time, the presentation unit 2034 may present the test viewpoint expected to be desired by the user at a position where it is easy to see. For example, the presentation unit 2034 presents the test viewpoint to the user so that the stored test viewpoint with the same or similar content as the information about the project is ranked higher.

When any of the presented test viewpoints is selected by the user, the storage control unit 2032 stores the selected test viewpoint in the project DB 281. The test viewpoint newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

Although it is not described in FIG. 12 that the test viewpoint is associated with the functional specification, the test viewpoint and the functional specification may be associated with each other as in the test design document. In addition, the test viewpoint may be associated with the relevant part of the functional specification. Further, as in the test design document shown in FIG. 11, a shared icon may be provided so that the test viewpoint can be shared within the same company.

When the user selects the field object 453 in the fifth area 45, the presentation unit 2034 presents a screen for displaying the pattern.

FIG. 13 is a schematic diagram showing an example of a screen for displaying a pattern created in a predetermined project. The screen shown in FIG. 13 has a first region 41, a fifth region 45, and a sixth region 46. The first region 41 is the same as the first region 41 shown in FIG.

In the fifth area 45, the field object 453 that specifies the pattern is selected by the selection object 455. The acquisition unit 2033 acquires data about the pattern from the project DB 281. The presentation unit 2034 presents the acquired data to the user.

The sixth area 46 is an area for displaying a list of data (patterns) selected in the fifth area 45. The pattern is displayed in a list format in the sixth area 46.

The pattern displayed in the sixth area 46 is not limited to the test design document already created in the project and the pattern for the test design document being created in the project. The user may select and register a pattern suitable for the project from the patterns stored in the client DB 282 or the standard DB 283 in advance. The selected pattern is stored in the project DB 281.

Whether the pattern is for the test design document created in the project or the pattern is registered in advance is determined from the description of the item "source" displayed in the sixth area 46. In other words, when the description of the item "source" is "project", it means that the pattern is for the test design document created in the project. Further, when the description of the item "source" is "shared" or "standard", it means that the pattern is selected from the client DB 282 or the standard DB 283.

Further, the sixth region 46 includes the field objects 4611 to 4613. The field objects 4611 to 4613 are objects for receiving instructions from the user.

Specifically, the field object 4611 is an object for receiving an instruction to newly add a pattern. When the field object 4611 is pressed, the display control unit 183 causes the display 141 to display an input form for inputting a pattern.

The field object 4612 is an object for receiving an instruction to request the display of the pattern stored in the standard DB 283. When the field object 4612 is pressed, the acquisition unit 2033 acquires the pattern stored in the standard DB 283. The presentation unit 2034 presents the acquired data to the user. When any of the presented patterns is selected by the user, the storage control unit 2032 stores the selected pattern in the project DB 281. The pattern newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

The field object 4613 is an object for receiving an instruction to request the display of the pattern stored in the client DB 282. When the field object 4613 is pressed, the acquisition unit 2033 acquires the pattern stored in the client DB 282. The presentation unit 2034 presents the acquired data to the user. When any of the presented patterns is selected by the user, the storage control unit 2032 stores the selected pattern in the project DB 281. The pattern newly stored in the project DB 281 is displayed in a new record in the list of the sixth area 46.

Although the association between the pattern and the functional specification is not described in FIG. 13, the pattern and the functional specification may be associated with each other as in the test design document. In addition, the pattern may be associated with the relevant part of the functional specification. Further, as in the test design document shown in FIG. 11, a sharing icon may be provided so that the pattern can be shared within the same company.

When the user selects the field object 414 in the first area 41, the presentation unit 2034 presents a screen for displaying the data stored in the client DB 282.

FIG. 14 is a schematic diagram showing an example of a screen for displaying a test design document shared within a company. The screen shown in FIG. 14 has a first region 41, a seventh region 47, and an eighth region 48.

In the first area 41, the field object 414 that specifies the shared file is selected by the selection object 417.
The seventh region 47 includes field objects 471 to 475 and selection objects 476.

The field objects 471 to 473 are objects for accepting the designation of the data to be displayed from the user. Specifically, the field objects 471 to 473 are objects for accepting the designation of the design file, the pattern, and the test viewpoint, respectively.

The field object 474 is an object for receiving an instruction to search data based on the tag.
Field object 475 is an object that represents the currently selected database and data type. In FIG. 14, since the client DB 282 is selected and the display of the test design document is selected, the field object 475 is described as “shared design document”.

The selection object 476 is an object representing the user's selection for the field objects 471 to 474. The selection object 476 stops on the selected object when the user selects any of the field objects 471 to 474.

In the screen shown in FIG. 14, the field object 471 that specifies the design document is selected by the selection object 476. The acquisition unit 2033 acquires data about the test design document from the client DB 282. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (test design documents) selected in the seventh area 47. In the eighth area 48, the test design document is displayed in a list format.

The test design document displayed in the eighth area 48 is shared by the standard knowledge by pressing the application icon 482 arranged at the right end of the list. That is, the test design document is stored in the standard DB 283. For example, the user considers the generality, importance, etc. of the test design document and determines whether or not the test design document should be shared in the standard knowledge. If it should be shared with standard knowledge, the user presses the application icon 482. When the user presses the application icon 482, the storage control unit 2032 stores the test design document of the record in which the application icon 482 is pressed in the standard DB 283. The test design document of the record in which the application icon 482 is pressed may be in the application state and may be stored in the standard DB 283 with permission from a person having a predetermined authority. It should be noted that special authority may be required to store the test design document accumulated in the shared knowledge (client DB 282) in the standard DB 283. For example, the system administrator has the application authority, and the test design document accumulated in the shared knowledge is stored in the standard DB 283 based on the judgment of the administrator. By providing the authority in this way, only the test design documents that are really necessary are accumulated in the standard DB 283. The fact that the test design document is stored in the standard DB 283 means that the test design document can be widely and generally used. Therefore, it can be a material for evaluating the test designer based on the number of test design documents stored in the standard DB 283.

When the test design document is stored in the standard DB 283, the storage control unit 2032 sets the attributes of the test design document based on the tags attached to the test design document. The storage control unit 2032 stores the test design document in the standard DB 283 together with the set attributes.

Further, the eighth area 48 includes a search box 481 for accepting input of a search keyword from the user.

When the user selects the field object 472 in the seventh area 47, the presentation unit 2034 presents a screen for displaying the pattern.

FIG. 15 is a schematic diagram showing an example of a screen for displaying a pattern shared within a company. The screen shown in FIG. 15 has a first region 41, a seventh region 47, and an eighth region 48. The first region 41 is the same as the first region 41 shown in FIG.

In the seventh area 47, the field object 472 that specifies the pattern is selected by the selection object 476. The acquisition unit 2033 acquires data about the pattern from the client DB 282. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (patterns) selected in the seventh area 47. The pattern is displayed in a list format in the eighth area 48.

Any of the patterns displayed in the list may receive an instruction from the user to store in the standard DB 283. When the user inputs an instruction to store in the standard DB 283, the storage control unit 2032 stores the pattern selected by the user in the standard DB 283.

When the user selects the field object 473 in the seventh area 47, the presentation unit 2034 presents a screen for displaying the data viewpoint.

FIG. 16 is a schematic diagram showing an example of a screen for displaying a test viewpoint shared within a company. The screen shown in FIG. 16 has a first region 41, a seventh region 47, and an eighth region 48. The first region 41 is the same as the first region 41 shown in FIG.

In the seventh region 47, the field object 473 that specifies the test viewpoint is selected by the selection object 476. The acquisition unit 2033 acquires data about the test viewpoint from the client DB 282. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (test viewpoints) selected in the seventh area 47. In the eighth area 48, the test viewpoints are displayed in a list format.

Any of the test viewpoints displayed in the list may receive an instruction from the user to store in the standard DB 283. When the user inputs an instruction to store in the standard DB 283, the storage control unit 2032 stores the test viewpoint selected by the user in the standard DB 283.

When the user selects the field object 415 in the first area 41, the presentation unit 2034 presents a screen for displaying the data stored in the standard DB 283.

FIG. 17 is a schematic diagram showing an example of a screen for displaying a test design document stored in standard knowledge. The screen shown in FIG. 17 has a first region 41, a seventh region 47, and an eighth region 48.

In the first region 41, the field object 415 that specifies the knowledge is selected by the selection object 417.

In the seventh area 47, since the standard DB 283 is selected, the field object 475 is described as "TD (registered trademark)". Further, the field object 471 that specifies the design document is selected by the selection object 476. The acquisition unit 2033 acquires data about the test design document from the standard DB 283. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (test design documents) selected in the seventh area 47. In the eighth area 48, the test design document is displayed in a list format.

When the user selects the field object 472 in the seventh area 47, the presentation unit 2034 presents a screen for displaying the pattern.

FIG. 18 is a schematic diagram showing an example of a screen for displaying a pattern stored in standard knowledge. The screen shown in FIG. 18 has a first region 41, a seventh region 47, and an eighth region 48. The first region 41 is the same as the first region 41 shown in FIG.

In the seventh area 47, the field object 472 that specifies the pattern is selected by the selection object 476. The acquisition unit 2033 acquires data about the pattern from the standard DB 283. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (patterns) selected in the seventh area 47. The pattern is displayed in a list format in the eighth area 48.

When the user selects the field object 473 in the seventh area 47, the presentation unit 2034 presents a screen for displaying the data viewpoint.

FIG. 19 is a schematic diagram showing an example of a screen for reading out the test viewpoint stored in the standard knowledge. The screen shown in FIG. 19 has a first region 41, a seventh region 47, and an eighth region 48. The first region 41 is the same as the first region 41 shown in FIG.

In the seventh region 47, the field object 473 that specifies the test viewpoint is selected by the selection object 476. The acquisition unit 2033 acquires data about the test viewpoint from the standard DB 283. The presentation unit 2034 presents the acquired data to the user.

The eighth area 48 is an area for displaying a list of data (test viewpoints) selected in the seventh area 47. In the eighth area 48, the test viewpoints are displayed in a list format.

<5 operation>
(Creation of test design document)
The process of the server 20 when the test design document is created will be described together with the display screen of the display 141.

First, a case where the test design document stored in the client DB 282 or the standard DB 283 is copied to create the test design document will be described.
For example, it is assumed that the user diverts the test design document used in the project 1 from the accumulated test design document. The user presses the field object 466 of "Copy from shared file knowledge" on the screen shown in FIG.

When the field object 466 is pressed, the acquisition unit 2033 acquires the test design document from the client DB 282 and the standard DB 283. The presentation unit 2034 presents the acquired test design document to the terminal device 10.

The display control unit 183 causes the display 141 to display, for example, a display window 4614 in which the client DB 282 and the test design document read from the standard DB 283 are listed.
FIG. 20 is a schematic diagram showing an example of a list display of a test design document. The display window 4614 includes a reference icon 4615 and field objects 4616, 4617. The reference icon 4615 is arranged at the left end of the list and is an icon for accepting a display request for a test design document.

The field object 4616 is an object for receiving an instruction to create a test design document by diverting the test design document selected by the user. The field object 4617 is an object for receiving an instruction to cancel the diversion of the test design document.

From which database the test design document displayed in the display window 4614 is read can be determined from the description of the item "source". In the example of FIG. 20, the test design document in which the description of the item “source” is “shared knowledge” is the test design document read from the client DB 282. Further, the test design document in which the description of the item "source" is "standard knowledge" is a test design document read from the standard DB 283.

When the reference icon 4615 arranged at the left end of the list is pressed by the user, the display control unit 183 displays detailed information of the test design document of the record to which the reference icon 4615 is pressed, for example, a confirmation item list or a pattern table. It is displayed on the display 141.

The user confirms the confirmation item list and the pattern table, and determines whether or not the test design document can be diverted in project 1. When it is determined that the test design document can be diverted, the user selects the test design document determined to be divertable and presses the field object 4616 displayed in the display window 4614.

When the field object 4616 is pressed, the storage control unit 2032 stores the test design document selected by the user in the project DB 281. When the test design document is stored in the project DB 281, the acquisition unit 2033 acquires the stored test design document. The presentation unit 2034 presents the acquired test design document to the terminal device 10. As a result, a new test design document is created in the list of the sixth region 46 shown in FIG. The created test design document can be arbitrarily edited from the screen shown in FIG.

Note that FIG. 20 shows a case where the presentation unit 2034 displays the test design documents read from the client DB 282 and the standard DB 283 in a predetermined order. However, the presentation unit 2034 may present the test design document expected to be desired by the user in a position where it is easy to see. For example, the presentation unit 2034 presents the test design document to the user so that the stored test design document with the same or similar content as the information about the project is ranked higher.

Next, a case where a test design document is created while diverting the test viewpoint or pattern stored in the project DB 281, the client DB 282, or the standard DB 283 will be described.

For example, assume that the user creates a test design document used in project 1. The user presses the "newly created" field object 411 on the screen shown in FIG.

When the field object 411 is pressed, the display control unit 183 causes the display 141 to display a form for creating a confirmation item list.

FIG. 21 is a schematic diagram showing an example of a screen for creating a list of confirmation items. The creation screen shown in FIG. 21 includes a field object 491. The field object 491 is an object for accepting input from the user for the confirmation item list. When the creation screen is displayed, the user selects, for example, the first cell 4911 of the item "test viewpoint" in order to input the test viewpoint.

When cell 4911 is selected, the display control unit 183 causes the display 141 to confirm whether or not to display the list of test viewpoints. When the user requests the display of the list of test viewpoints, the acquisition unit 2033 acquires the test viewpoints from the project DB 281. The presentation unit 2034 presents the acquired test viewpoint to the user.

The display control unit 183 causes the display 141 to display, for example, a display window 492 in which the test viewpoints read from the project DB 281 are displayed in a list.

FIG. 22 is a schematic diagram showing an example of a list display of test viewpoints. The display window 492 includes selection icons 4921, 4922.

The selection icons 4921 and 4922 are icons for accepting the selection of the database for reading the test viewpoint. Specifically, the selection icon 4921 is an icon for accepting the selection of the project DB 281. If you check the box of the selection icon, reading from the project DB 281 is selected. The selection icon 4922 is an icon for accepting the selection of the standard DB 283. If you check the box of the selection icon, reading from the standard DB283 is selected. The display window 492 may include an icon for accepting the selection of reading the test viewpoint from the client DB 282.

In FIG. 22, the selection icon 4921 is checked, and the test viewpoint read from the project DB 281 is displayed. In the item "source" of the test viewpoint read from the project DB 281, the "project viewpoint" is described. When the selection icon 4922 is checked by the user, the test viewpoint read from the standard DB 283 is displayed (not shown). In the item "source" of the test viewpoint read from the standard DB 283, for example, "standard viewpoint" is described.

When the test viewpoint displayed in the display window 492 is selected, the selected "test viewpoint" and the "confirmation item" included in the selected test viewpoint are input to the confirmation item list.

FIG. 23 is a schematic diagram showing an example of a confirmation item list creation screen in which a “test viewpoint” and a “confirmation item” are input. In FIG. 23, “normal authentication” is described in the first cell 4911 of the item “test viewpoint”, and the “confirmation item” is described in the first cell 4912 of the item “confirmation item”.

The input screen of the confirmation item list shown in FIG. 23 includes a field object 493 for accepting a transition to the pattern management screen. When the field object 493 is pressed by the user, the display control unit 183 displays the pattern management screen on the display 141.

FIG. 24 is a schematic diagram showing an example of a pattern management screen. The management screen shown in FIG. 24 includes field objects 4101 to 4104 and selection objects 4105.

The field object 4101 is an object for receiving an instruction to newly add a pattern. When the field object 4101 is pressed by the user, the display control unit 183 causes the display 141 to display the field objects 4102 and 4103 for inputting information about the pattern.

The field object 4102 is an object for accepting selections for the managed pattern. When a plurality of patterns are registered in the confirmation item list, a plurality of field objects 4102 are displayed. The field object 4103 is an object for receiving a pattern input from the user.

The field object 4104 is an object for receiving an instruction to copy a pattern stored in the client DB 282 or the standard DB 283.

The selection object 4105 is an object that represents the user's selection with respect to the field object 4102. The selection object 4105 stops on the selected object when the user selects any of the field objects 4102.

When the field object 4104 is pressed, the acquisition unit 2033 acquires a pattern from the client DB 282 and the standard DB 283. The presentation unit 2034 presents the acquired pattern to the terminal device 10.

The display control unit 183 causes the display 141 to display, for example, the client DB 282 and the display window 4106 in which the patterns read from the standard DB 283 are displayed in a list.

FIG. 25 is a schematic diagram showing an example of a list display of patterns. The display window 4106 includes a reference icon 4107 and field objects 4108, 4109. The reference icon 4107 is arranged at the left end of the list and is an icon for accepting a display request for a pattern.

The field object 4108 is an object for receiving an instruction to create a pattern by diverting the pattern selected by the user. The field object 4109 is an object for receiving an instruction to cancel the diversion of the pattern.

From which database the pattern displayed in the display window 4106 is read can be determined from the description of the item "source". In the example of FIG. 25, the pattern in which the description of the item “source” is “project” is a pattern read from the project DB 281. Further, the pattern in which the description of the item "source" is "client" is a test design document read from the client DB 282. Further, the pattern in which the description of the item "source" is "master" is a test design document read from the standard DB 283.

When the reference icon 4107 arranged at the left end of the list is pressed by the user, the display control unit 183 displays the detailed information of the pattern of the record on which the reference icon 4107 is pressed, for example, the pattern table on the display 141.

The user checks the pattern table and determines whether or not the pattern can be diverted. When it is determined that the pattern can be diverted, the user selects the pattern determined to be divertable and presses the field object 4108 displayed in the display window 4106.

When the field object 4108 is pressed, the storage control unit 2032 stores the pattern selected by the user in the project DB 281. When the pattern is stored in the project DB 281, the acquisition unit 2033 acquires the stored pattern. The presentation unit 2034 presents the acquired pattern to the terminal device 10. As a result, a new field object 4102 is added to the management screen shown in FIG. 24. FIG. 26 is a schematic diagram showing an example of a pattern management screen.

Note that FIG. 25 shows a case where the presentation unit 2034 displays the patterns read from the client DB 282 and the standard DB 283 in a predetermined order. However, the presentation unit 2034 may present the pattern expected to be desired by the user at a position where it is easy to see. For example, the presentation unit 2034 presents the pattern to the user so that the stored pattern tagged with the same or similar content as the information about the project goes up.

(Proposal of revision according to revision of functional specifications)
The processing of the server 20 when proposing the modification of the test design document or the element according to the modification of the functional specification will be described together with the display screen of the display 141.

FIG. 27 is a flowchart showing the processing flow of the control unit 203 when proposing the modification of the test design document or the element according to the modification of the functional specification.

First, the storage control unit 2032 receives information about the functional specifications from the user or a predetermined site, and stores the received information in the storage unit 202 (step S21).

The detection unit 2035 determines whether or not there is a change in the functional specification 284 associated with the test design document (step S22). For example, the detection unit 2035 acquires information regarding changes in the functional specification 284. Specifically, for example, when a change is made to the functional specification 284, information about the change is stored in the change information. The detection unit 2035 grasps the changed part in the functional specification 284 based on the change information. Further, for example, when there is a change in the functional specification 284 created by the spreadsheet software, the detection unit 2035 detects that the functional specification 284 has been changed based on the change history, and also detects the change in the functional specification 284. Detects changed parts in, for example, changed sheets, changed rows, changed cells, and the like.

The acquisition unit 2033 acquires the test design document associated with the functional specification document 284 in which the change is detected from the project DB 281 (step S23). The acquisition unit 2033 may acquire the elements of the test design document associated with the functional specification 284 in which the change is detected, for example, the test viewpoint or the pattern from the project DB 281.

When the test design document and the corresponding part of the functional specification document 284 are associated with each other, the acquisition unit 2033 sets the test design document or the element of the test design document associated with the changed part of the functional specification document 284 into the project DB 281. May be obtained from.

The presentation unit 2034 presents the acquired information to the terminal device 10 (step S24). Specifically, for example, the presentation unit 2034 presents to the terminal device 10 that it may be necessary to modify the acquired test design document or the element of the test design document due to the change of the functional specification document 284. do. The display control unit 183 causes the display 141 to display the presented contents.

FIG. 28 is a schematic diagram showing an example of a screen for displaying a test design document based on a change in the functional specification document 284 or a correction proposal for an element of the test design document. The display control unit 183 causes the display 141 to display the display window 4614 on the screen for displaying the list of the test design documents, for example. The display window 4614 indicates that the test design document, the test viewpoint, and the pattern may need to be modified due to the change of the relevant part of the functional specification. The display of the display window 4614 is not limited to this. Only the modification of the test design document may be proposed, or the modification of the confirmation item list and the pattern table of the test design document may be proposed.

When the proposal for modification is displayed in the display window 4614, the user confirms the modification part of the corresponding functional specification 284 and examines whether or not the test design document or the element of the test design document needs modification. When modification is necessary, the user modifies the test design document or the element of the test design document.

When the test design document or the element of the test design document is modified by the user, the storage control unit 2032 updates the element of the test design document or the test design document stored in the project DB 281 with the modified data. When the data of the project DB 281 is updated, the storage control unit 2032 determines whether or not the test design document before modification or the element of the test design document is also stored in the client DB 282 or the standard DB 283. When the test design document before modification or the element of the test design document is also stored in the client DB 282 or the standard DB 283, the storage control unit 2032 corrects the data stored in the client DB 282 or the standard DB 283 after modification. Update with the data of.

(Generation of index value)
The process of the server 20 when the index value is calculated by diverting the elements of the test design document or the test design document stored in the project DB 281, the client DB 282, and the standard DB 283 will be described.

First, the storage control unit 2032 stores in the storage unit 202 the first number of times that the project DB 281, the client DB 282, the test design document stored in the standard DB 283, or the elements of the test design document are diverted. Further, the storage control unit 2032 stores in the storage unit 202 the second number of times that the test designer diverted the test design document or the element of the test design document.

The calculation unit 2036 calculates a predetermined index value based on the first number of times and the second number of times stored in the storage unit 202. The index value is an index value indicating how much the cost of the test design is suppressed by diverting the elements of the test design document or the test design document stored in the project DB 281, the client DB 282, and the standard DB 283, for example. .. For example, the index value includes a shortened value, a shortened rate, or the like, which indicates how much the time for creating one test design document has been shortened by diverting the test design document or the like. In addition, by diverting a test design document or the like as an index value, a shortened value or a shortening rate indicating how much time the test designer took to create one test design document was shortened. Etc. are included.

The presentation unit 2034 presents the index value calculated by the calculation unit 2036 to the terminal device 10.

As described above, in the above embodiment, the memory control unit 2032 has the test design document and the elements decomposed from the test design document in the project DB 281, the client DB 282, and the standard DB 283 provided for each layer corresponding to the business. Remember in. Then, the presentation unit 2034 switches and presents the test design document or the element stored in the project DB 281, the client DB 282, and the standard DB 283 in response to a request from the user. As a result, the server 20 stores the test design document and the elements decomposed from the test design document in the desired database, so that the user can easily reach the desired information.

Therefore, according to the server 20 according to the present disclosure, it is possible to effectively use the test design document created in the past and reduce the burden of the test design while maintaining the quality of the test.

Further, in the above embodiment, the storage control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281 that shares information within the project. As a result, the server 20 can store the past data created in the project so that it can be used in the project.

Further, in the above embodiment, the storage control unit 2032 shares either the test design document stored in the project DB 281 or the elements decomposed from the test design document in the client DB 282 that shares information across the project. I try to remember it. As a result, the server 20 can store the past data created in the project so that it can be used in the company.

Further, in the above embodiment, the storage control unit 2032 shares information on any one of the test design document stored in the project DB 281 or the client DB 282 and the elements decomposed from the test design document as a whole. It is stored in the standard DB 283. As a result, the server 20 can usely store the past data created in the project or the company as standard data.

Further, in the above embodiment, the storage control unit 2032 attaches information indicating the type to which the test design document belongs to the test design document or the element decomposed from the test design document and stores it in the standard DB 283. There is. As a result, the server 20 classifies the data stored in the standard DB 283 according to the type of the company. Therefore, the user can efficiently reach the desired data even when a large amount of data is accumulated in the standard DB 283.

Further, in the above embodiment, the storage control unit 2032 is configured to store the data in the database of the upper layer in response to the instruction of the authorized user. As a result, it is possible to prevent the number of data stored in the client DB 282 or the standard DB 283 from becoming enormous.

Further, in the above embodiment, the presentation unit 2034 presents the test design document or the element stored in the project DB 281 to the user belonging to the project corresponding to the project DB 281. As a result, the server 20 can activate information sharing within the project and suppress quality fluctuations for each test designer within the project. In other words, personalization is eliminated and quality is stable.

Further, in the above embodiment, the presentation unit 2034 presents the test design document or the element stored in the client DB 282 or the standard DB 283 to the user. As a result, the user can search for the desired information from the database for each layer, and can quickly reach the desired information. In addition, since the quality test desired by the client company can be grasped in advance planning, the probability of designing a useless test is reduced, and it is possible to avoid time loss. Therefore, it is possible to design a test of optimum cost and optimum quality for the client company in the entire project.

Further, in the above embodiment, the storage control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281 in association with the functional specifications referred to at the time of creation. .. Then, when the functional specification is changed, the presentation unit 2034 presents a test design document or an element modification proposal associated with the functional specification. As a result, the user can modify the test design document in real time in conjunction with the development. Therefore, the discrepancy between the actual developed target and the test being designed can be suppressed. This helps prevent test omissions throughout the project.

Further, in the above embodiment, the memory control unit 2032 associates the created test design document and the elements decomposed from the test design document with the corresponding parts of the functional specifications referred to at the time of creation, and the project DB 281. Remember in. Then, when there is a change in the relevant part, the presentation unit 2034 presents a test design document or an element modification proposal associated with the relevant part. As a result, the user can more efficiently modify the test design document or the element according to the change of the functional specification.

Further, in the above embodiment, the storage control unit 2032 has a test design document associated with the functional specification, or a modified test design document stored in a database of a higher layer when an element is modified. Or, the correction is reflected in the test design document or element corresponding to the element. As a result, the server 20 can reflect the changes in the functional specifications not only to the data stored in the project DB 281 but also to the data stored in the client DB 282 or the standard DB 283.

Further, in the above embodiment, the memory control unit 2032 attaches the test design document and the elements decomposed from the test design document to the project DB 281, the client DB 282, and the standard DB 283 with tags that individually represent the characteristics of the test. Remember. Then, the presentation unit 2034 searches the database designated by the user for the test design document or the element stored in each database based on the tag. This allows the user to reach the desired data more quickly.

Further, in the above embodiment, the element is a pattern table in which a test viewpoint representing a viewpoint on which the test is based and a test case to be executed are defined. As a result, the server 20 can manage the data in units of items in which the input contents are likely to vary depending on the skill of the user. Therefore, when the user creates the test design document, it is possible to support the input of information from the user, and it is possible to reduce the burden of creating the test design document. In addition, variations in the quality of the created test design documents will be suppressed.

Further, in the above embodiment, the storage control unit 2032 stores the test viewpoint stored in the client DB 282 or the standard DB 283 in the project DB 281 before the test design document is created. As a result, the server 20 can register the test viewpoint required for the project in advance, so that the burden on the test designer to set the test viewpoint can be reduced. In addition, it is possible to prevent the necessary test viewpoints from being leaked.

Further, in the above embodiment, the calculation unit 2036 indicates how much the cost of the test design is suppressed based on the number of reference times of the test design document or the element stored in the project DB 281, the client DB 282, or the standard DB 283. I try to calculate the index value. As a result, the server 20 can quantitatively present the effectiveness of its own device to the client company.

In the above embodiment, the case where the database is provided in the three layers of the project DB 281, the client DB 282, and the standard DB 283 has been described as an example. However, the number of layers in which the database according to this embodiment is provided is not limited to three layers. For example, a layer for collecting information stored in the client layer by a predetermined element may be provided above the client DB 282. Predetermined elements are, for example, geographical elements, industry-related elements, and the like. Specifically, for example, a database that summarizes information about companies in eastern Japan and a database that summarizes information about companies in western Japan may be provided.

Although some embodiments of the present disclosure have been described above, these embodiments can be implemented in various other embodiments, and various omissions, replacements, and modifications are made without departing from the gist of the invention. It can be performed. These embodiments and variations thereof shall be included in the scope of the invention described in the claims and the equivalent scope thereof, as well as in the scope and gist of the invention.

<Additional Notes>
The matters described in each of the above embodiments are added below.

(Appendix 1)
A program for causing a computer having a processor 29 and a memory 25 to execute the program.
A step (2032) of storing the test design document and the elements decomposed from the test design document in the databases 281,282,283 provided for each layer corresponding to the business, and
A program that executes a test design document stored in each database or a step (2034) of switching and presenting elements in response to a request from a user.

(Appendix 2)
The program according to (Appendix 1), which stores the created test design document and the elements decomposed from the test design document in the first database 281 that shares information within the project.

(Appendix 3)
In the step of storing, either the test design document stored in the first database or the elements decomposed from the test design document is stored in the second database 282 that shares information across the project (Appendix 2). ).

(Appendix 4)
In the step of storing, either the test design document stored in the first database or the second database, or the elements decomposed from the test design document are stored in the third database 283 that shares information as a whole. The program described in (Appendix 3).

(Appendix 5)
The program described in (Appendix 4), in which information indicating the type to which the test design document belongs is attached to the test design document or the element decomposed from the test design document and stored in the third database in the step of storing.

(Appendix 6)
In the step of memorizing, in order to memorize the test design document and the elements decomposed from the test design document in the third database, the operation of an authorized person is required (Appendix 4) or (Appendix 5). The program described in.

(Appendix 7)
The program according to any one of (Appendix 2) to (Appendix 6) that presents a test design document or an element stored in the first database to a user belonging to a project corresponding to the first database in the presented step.

(Appendix 8)
The program according to any one of (Appendix 3) to (Appendix 7) that presents a test design document or an element stored in a second database to a user belonging to another project in the same client in the presented step.

(Appendix 9)
The program according to any one of (Appendix 4) to (Appendix 8) that presents a test design document or an element stored in a third database to a user in the presented step.

(Appendix 10)
In the step of memorizing, the created test design document and the elements decomposed from the test design document are stored in the first database in association with the functional specifications referred to at the time of creation.
When there is a change in the functional specification, the test design document associated with the functional specification or the step of proposing the modification of the element is described in any one of (Appendix 2) to (Appendix 9). Program.

(Appendix 11)
In the step of memorizing, the created test design document and the elements decomposed from the test design document are stored in the first database in association with the relevant part of the functional specification referenced at the time of creation.
The program described in (Appendix 10) that proposes modification of the test design document or element associated with the relevant part when there is a change in the relevant part in the proposed step.

(Appendix 12)
If the test design document or element associated with the functional specification is modified, the modified test design document or test design document or element corresponding to the element is stored in the database of the upper layer. The program according to (Appendix 10) or (Appendix 11), which causes the processor to execute a step for reflecting the modification.

(Appendix 13)
In the step of memorizing, the test design document and the elements decomposed from the test design document are stored in the second database with tags that individually represent the characteristics of the test.
The program described in any of (Appendix 3) to (Appendix 12) for searching a test design document or an element based on a tag in the presented step.

(Appendix 14)
In the step to memorize, attribute information indicating the type to which the test design document belongs is created based on the tag information, and the test design document or the element decomposed from the test design document is attached with the attribute information to the third database. The program described in (Appendix 13).

(Appendix 15)
The program according to any one of (Appendix 1) to (Appendix 14), wherein the element is a pattern table in which a test viewpoint representing a viewpoint on which the test is based and a test case to be performed are defined.

(Appendix 16)
The elements are a pattern table that defines the test viewpoints that represent the viewpoints on which the tests are based and the test cases that are performed.
In the step of storing, the test viewpoint stored in the second database or the third database is stored in the first database before the test design document is created (Appendix 4) to (Appendix 6). The program described in.

(Appendix 17)
Have the processor execute the step (2036) of calculating the index value based on the number of reference times of the test design document or the element stored in the first database, the second database, or the third database (Appendix 4) to (Appendix 4). The program described in any of 6).

(Appendix 18)
A program to be executed by a computer equipped with a processor and a memory, and the program is a program to be executed by the processor.
Steps to store the created test design document in the database in association with the functional specifications referenced at the time of creation, and
A program that causes the processor to execute a step that proposes a modification of the test design document associated with the functional specification when there is a change in the functional specification.

(Appendix 19)
In the step to memorize, the created test design document is stored in the database in association with the relevant part of the functional specification referenced at the time of creation.
The program described in (Appendix 18) that proposes the modification of the test design document associated with the relevant part when there is a change in the relevant part in the proposed step.

(Appendix 20)
It's a way a computer with a processor and memory does it.
A step to store the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business.
A method of executing a test design document stored in each database or a step of switching and presenting elements according to a request from a user.

(Appendix 21)
An information processing device equipped with a processor and a memory.
The processor,
A step to store the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business.
An information processing device that executes a test design document stored in each database or a step of switching and presenting elements in response to a request from a user.

(Appendix 22)
A means for storing the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business.
A system provided with a test design document stored in each database or a means for switching and presenting elements in response to a request from a user.

1 ... System 10 ... Terminal device 121 ... Communication unit 13 ... Input device 131 ... Mouse 132 ... Keyboard 133 ... Touch sensitive device 14 ... Output device 141 ... Display 15 ... Memory 16 ... Storage 170 ... Storage unit 180 ... Control unit 181 ... Operation reception unit 182 ... Transmission / output unit 183 ... Display control unit 19 ... Processor 20 ... Server 201 ... Communication unit 202 ... Storage unit 203 ... Control unit 2031 ... Transmission / output unit 2032 ... Storage control unit 2033 ... Acquisition unit 2034 ... Presentation unit 2035 ... Detection unit 2036 ... Calculation unit 25 ... Memory 26 ... Storage 281 ... Project DB
2811 ... Test design document 2812 ... Pattern 2813 ... Test viewpoint 282 ... Client DB
2821 ... Test design document 2822 ... Pattern 2823 ... Test viewpoint 283 ... Standard DB
2831 ... Test design document 2832 ... Pattern 2833 ... Test viewpoint 284 ... Functional specification 29 ... Processor

Claims (22)

A program for causing a computer having a processor and a memory to execute the program, wherein the program causes the processor to execute the program.
A step of storing the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business, and
A program that executes a test design document stored in each database or a step of switching and presenting elements in response to a request from a user. The program according to claim 1, wherein the created test design document and the elements decomposed from the test design document are stored in a first database for sharing information within the project. A claim that stores one of the test design document stored in the first database and the elements decomposed from the test design document in the second database that shares information across the project in the storage step. 2 The program described. In the step of storing, a third database that shares information as a whole with either the test design document stored in the first database or the second database, or the elements decomposed from the test design document. The program according to claim 3 to be stored in. The program according to claim 4, wherein in the step of storing, information indicating the type to which the test design document belongs is attached to the test design document or an element decomposed from the test design document and stored in the third database. .. 4. program. The program according to any one of claims 2 to 6, which presents a test design document or an element stored in the first database to a user belonging to a project corresponding to the first database in the presented step. The program according to any one of claims 3 to 7, which presents a test design document or an element stored in the second database to a user belonging to another project in the same client in the presented step. The program according to any one of claims 4 to 8 in which the test design document stored in the third database or the elements are presented to the user in the presented step. In the step of storing, the created test design document and the elements decomposed from the test design document are stored in the first database in association with the functional specifications referred to at the time of creation.
The program according to any one of claims 2 to 9, wherein when the functional specification is changed, the test design document associated with the functional specification or the step of proposing the modification of the element is executed by the processor. .. In the step of storing, the created test design document and the elements decomposed from the test design document are stored in the first database in association with the corresponding part of the functional specification referred to at the time of creation.
The program according to claim 10, which proposes modification of a test design document or an element associated with the relevant part when the relevant part is changed in the proposed step. When the test design document or element associated with the functional specification is modified, the modified test design document or the test design document or element corresponding to the element is stored in the database of the upper layer. The program according to claim 10 or 11, wherein the processor executes a step for reflecting the modification. In the step of storing, the test design document and the elements decomposed from the test design document are stored in the second database with tags that individually represent the characteristics of the test.
The program according to any one of claims 3 to 12, which searches for the test design document or the element based on the tag in the presented step. In the step to be stored, attribute information indicating the type to which the test design document belongs is created based on the information of the tag, and the test design document or an element decomposed from the test design document is attached with the attribute information. The program according to claim 13, which is stored in the third database. The program according to any one of claims 1 to 14, wherein the element is a test viewpoint representing a viewpoint on which the test is based, and a pattern table in which test cases to be performed are defined. The above-mentioned elements are a pattern table in which test viewpoints representing the viewpoints on which the tests are based and test cases to be carried out are defined.
Any of claims 4 to 6 in which the test viewpoint stored in the second database or the third database is stored in the first database before the test design document is created in the storage step. The program described in Crab. Claims 4 to 6 for causing the processor to perform a step of calculating an index value based on the number of references to a test design document or an element stored in the first database, the second database, or the third database. The program described in either. A program for causing a computer having a processor and a memory to execute the program, wherein the program causes the processor to execute the program.
Steps to store the created test design document in the database in association with the functional specifications referenced at the time of creation, and
A program that causes the processor to execute a step of proposing a modification of the test design document associated with the functional specification when the functional specification is changed. In the step of storing, the created test design document is stored in the database in association with the corresponding part of the functional specification referenced at the time of creation.
The program according to claim 18, which proposes modification of the test design document associated with the relevant part when the relevant part is changed in the proposed step. It's a way a computer with a processor and memory does it.
A step of storing the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business, and
A method of executing a test design document stored in each database or a step of switching and presenting elements in response to a request from a user. An information processing device equipped with a processor and a memory.
The processor
A step of storing the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business, and
An information processing device that executes a test design document stored in each database or a step of switching and presenting elements in response to a request from a user. A means for storing the test design document and the elements decomposed from the test design document in the database provided for each layer corresponding to the business.
A system provided with a test design document stored in each database or a means for switching and presenting elements in response to a request from a user.

Images