Programs, methods, information processing devices, and systems

Abstract

To effectively utilize previously created test design documents to reduce the burden of test design while maintaining test quality. [Solution] The program of this disclosure causes the processor to perform the steps of storing test design documents and elements decomposed from test design documents in databases provided for each layer corresponding to the business, and switching and presenting test design documents or elements stored in each database in response to a request from the user.

Description

Technical Field

[0001] This disclosure relates to a program, a method, an information processing apparatus, and a system.

Background Art

[0002] Software is tested for functionality before launch to ensure its quality. The tests are designed based on the content of the software specification so that the desired quality is ensured under the development schedule and budget set by the software development company.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] To design tests according to the intention of the client, advanced knowledge and rich experience are required. 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 conducting tests. Then, test cases are generated from the specification items extracted from the system specification and the test viewpoints stored in the database.

[0005] In Patent Document 1, although test viewpoints are stored in the database, these test viewpoints are not based on test design documents created in the past.

[0006] An object of the present disclosure is to effectively use test design documents created in the past and reduce the burden of test design while maintaining the quality of tests.

Means for Solving the Problems

[0007] To solve the above problems, the program of this disclosure causes the processor to perform the steps of storing test design documents and elements decomposed from test design documents in databases provided for each layer corresponding to the business, and switching and presenting test design documents or elements stored in each database in response to a request from the user. [Effects of the Invention]

[0008] According to this disclosure, it is possible to effectively utilize previously created test design documents and reduce the burden of test design while maintaining test quality. [Brief explanation of the drawing]

[0009] [Figure 1] This diagram shows the overall configuration of the system in this embodiment. [Figure 2] This is a block diagram showing the configuration of the terminal device included in the system of this embodiment. [Figure 3] This block diagram shows the functional configuration of the server included in the system of this embodiment. [Figure 4] This diagram shows a list of verification items included in the test design document. [Figure 5] This diagram represents the pattern table included in the test design document. [Figure 6] This diagram shows the data structure of the project database. [Figure 7] This diagram shows the data structure of the client database. [Figure 8] This diagram shows the data structure of a standard database. [Figure 9] This diagram schematically represents the concept of the system according to this embodiment. [Figure 10] This diagram shows a screen for selecting the desired project. [Figure 11] This diagram shows a screen for displaying test design documents created for a given project. [Figure 12] This diagram shows a screen for displaying test perspectives created in a given project. [Figure 13] It is a diagram showing a screen for displaying a pattern created in a specified project. [Figure 14] It is a diagram showing a screen for displaying a test design document shared within a company. [Figure 15] It is a diagram showing a screen for displaying a pattern shared within a company. [Figure 16] It is a diagram showing a screen for displaying a test perspective shared within a company. [Figure 17] It is a diagram showing a screen for displaying a test design document stored in standard knowledge. [Figure 18] It is a diagram showing a screen for displaying a pattern stored in standard knowledge. [Figure 19] It is a diagram showing a screen for reading out a test perspective stored in standard knowledge. [Figure 20] It is a diagram showing a list display of test design documents. [Figure 21] It is a diagram showing a screen for creating a list of confirmation items. [Figure 22] It is a diagram showing a list display of test perspectives. [Figure 23] It is a diagram showing a creation screen of a list of confirmation items in which "test perspective" and "confirmation item" are input. [Figure 24] It is a diagram showing a management screen of patterns. [Figure 25] It is a diagram showing a list display of patterns. [Figure 26] It is a diagram showing a management screen of patterns. [Figure 27] It is a flowchart showing the processing flow of a control unit when proposing a modification of a test design document or an element in response to a modification of a functional specification document. [Figure 28] It is a diagram showing a screen for displaying a proposed modification of a test design document or an element of a test design document based on a change in a functional specification document.

Mode for Carrying Out the Invention

[0010] The embodiments described below will be explained with reference to the drawings. Note that the embodiments described below are not intended to unduly limit the scope of the claims of this disclosure. Furthermore, not all of the configurations described in these embodiments are necessarily essential components of this disclosure.

[0011] <Overview> In this embodiment, System 1 decomposes the created test design document into elements and stores the test design document and the decomposed elements according to the hierarchy of the business. Then, in response to a request from a test designer or manager, System 1 presents the stored test design document or elements.

[0012] In this embodiment, the test design document is data in which tests are designed to verify the functions of the object under test. The object under test represents the subject of the test, for example, hardware or software developed in a given project. The object under test includes, for example, prototypes, intermediate products, and final products. Functions represent the workings of the various components that make up the object under test.

[0013] <1 Overall Structure> Figure 1 shows the overall configuration of System 1 in this embodiment. As shown in Figure 1, System 1 comprises terminal devices 10 and a server 20. The terminal devices 10 and the server 20 are connected to each other via a network 80 using wired or wireless communication standards. The network 80 is realized, for example, by the Internet and / or a communication network provided by a telecommunications carrier. In the illustrated example, multiple terminal devices 10 are included in System 1.

[0014] Note that while Figure 1 shows a case where server 20 is a single computer, server 20 may be implemented by combining multiple computers. Also, while Figure 1 shows a case where there is a single terminal device 10, the number of terminal devices 10 housed in system 1 may be multiple.

[0015] Terminal device 10 is a terminal used by users who utilize services provided by server 20. For example, terminal device 10 is a terminal used by a test designer who creates test design documents. Terminal device 10 can be implemented as, for example, a stationary PC (Personal Computer), a laptop PC, a head-mounted display, etc. Alternatively, terminal device 10 may be a portable computer such as a smartphone or tablet device.

[0016] As shown in Figure 1, the terminal device 10 includes a communication interface (IF) 12, an input device 13, an output device 14, a memory 15, a storage device 16, and a processor 19. The communication interface 12, the input device 13, the output device 14, the memory 15, the storage device 16, and the processor 19 are connected to each other in a way that allows them to communicate with one another, for example, via a bus.

[0017] The communication interface 12 is an interface for sending and receiving signals so that the terminal device 10 can communicate with an external device. The input device 13 is an input device for receiving input operations from the user (employee). The input device 13 includes, for example, a touch panel, touchpad, a pointing device such as a mouse, a keyboard, etc. 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, etc.

[0018] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is implemented by volatile memory such as DRAM (Dynamic Random Access Memory). Storage 16 is a storage device for saving data, and is implemented by non-volatile memory such as flash memory or HDD (Hard Disk Drive). The processor 19 is hardware for executing the instruction set written in the program, and is composed of an arithmetic unit, registers, peripheral circuits, etc.

[0019] Server 20 is a device that stores the created test design documents and presents the stored test design documents to users in response to requests from users of terminal devices 10. Server 20 is, for example, a computer connected to network 80.

[0020] As shown in Figure 1, the server 20 includes a communication interface 22, an input / output interface 23, memory 25, storage 26, and a processor 29. The communication interface 22, input / output interface 23, memory 25, storage 26, and processor 29 are connected to each other in a way that allows them to communicate with one another, for example, via a bus.

[0021] Communication IF22 is an interface for the server 20 to send and receive signals in order to communicate with external devices. Input / Output IF23 functions as an interface to an input device for receiving input operations from the user and an output device for presenting information to the user. Memory 25 is for temporarily storing programs and data processed by programs, etc., and is implemented by volatile memory such as DRAM.

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

[0023] <1.1 Terminal Device Configuration> Figure 2 is a block diagram showing the configuration of the terminal device 10 included in System 1 of this embodiment. As shown in Figure 2, the terminal device 10 comprises a communication unit 121, an input device 13, an output device 14, a storage unit 170, and a control unit 180.

[0024] The communication unit 121 performs processing for the terminal device 10 to communicate with other devices. The communication unit 121 performs transmission processing on the signals generated by the control unit 180 and sends them to an external source (for example, the server 20). The communication unit 121 performs reception processing on signals received from an external source and outputs them to the control unit 180.

[0025] The input device 13 is a device for a user who owns the terminal device 10 to input instructions. The input device 13 can be implemented by, for example, a mouse 131, a keyboard 132, or a touch-sensitive device 133 on which instructions are input by touching the operating surface. The input device 13 converts the instructions input by the user into electrical signals and outputs the electrical signals to the control unit 180. Note that the input device 13 is not limited to physical operating devices such as a mouse 131 and a keyboard 132. The input device 13 may include, for example, a receiving port that accepts electrical signals input from an external input device.

[0026] The output device 14 is a device for presenting information to the user who owns the terminal device 10. The output device 14 is implemented by, for example, a display 141. The display 141 displays data such as images, videos, and text in accordance with the control of the control unit 180. The display 141 is implemented by, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display.

[0027] The storage unit 170 is implemented by, for example, memory 15 and storage 16, and stores data and programs used by the terminal device 10.

[0028] The control unit 180 is implemented when the processor 19 reads a program stored in the memory unit 170 and executes instructions contained in the program. The control unit 180 controls the operation of the terminal device 10. Specifically, for example, the control unit 180 performs functions as an operation reception unit 181, a transmission / reception unit 182, and a display control unit 183.

[0029] The operation reception unit 181 processes user operations input from the input device 13. The transmission / reception unit 182 processes data for the terminal device 10 to send and receive data with external devices such as the server 20 according to a communication protocol. The display control unit 183 controls the output device 14 to present various information to the user.

[0030] <1.2 Functional Configuration of the Server> Figure 3 is a block diagram showing the functional configuration of the server 20 included in System 1 of this embodiment. As shown in Figure 3, the server 20 performs the functions of a communication unit 201, a storage unit 202, and a control unit 203.

[0031] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

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

[0033] Project DB281 is a database for storing test design documents created for a given project, as well as the elements decomposed from these test design documents. Project DB281 also stores the test design documents currently being created for the given project, as well as the elements decomposed from these test design documents.

[0034] Project DB281 is a database for sharing test design documents or elements created within a project. In other words, it allows everyone involved in the project to share information about what test design documents or elements have been created. Project DB281 is created for each planned project, for example.

[0035] In this embodiment, the test design document includes, for example, information specifying items whose behavior is to be confirmed in the test, and information specifying actual test cases that are set based on the content to be confirmed and the conditions for the behavior to be exhibited. Specifically, the information specifying items whose behavior is to be confirmed in the test is included in the test design document as, for example, a list of confirmation items. The information specifying actual test cases is included in the test design document as, for example, a pattern table.

[0036] Figure 4 is a schematic diagram showing an example of a list of verification items included in a test design document. The example shown in Figure 4 describes a test design document for testing the login function of a given software. The list of verification items shown in Figure 4 includes a first area 31 where metadata of the test design document is stored, and a second area 32 where the contents to be verified by the test are stored.

[0037] The first area 31 includes, for example, the fields "Title," "Project Name," "Product Name," "Management Number," "Version," "Creation Date," "Creator," "Last Updated Date," and "Updater." However, the information included in the first area 31 is not limited to these. Any of this information may be missing, or other information may be included.

[0038] Domain 232 serves as a so-called basic design document, defining the overall framework of the inspection. Domain 232 defines, for example, "test items / functions," "test procedures," "test perspectives," and "expected values." "Test items / functions" represent the items / functions that will be inspected. Figure 4 shows a case where the inspection target is the login function, and the "test items / functions" are defined in the information stored in the items "test category," "major function," "medium function," and "minor function."

[0039] The "test procedure" represents the order in which the tests are performed. In Figure 4, the order in which the "test perspectives" are arranged determines the order in which the tests are performed.

[0040] "Test perspectives" represent the viewpoint (approach) that serves as the basis for testing. "Test perspectives" are defined by the information stored in the item "Test Perspectives" in Figure 4. In addition, the second domain 32 includes the item "Verification Items." The item "Verification Items" represents information used to identify the test to be performed. The information stored in the item "Test Perspectives" and the information stored in the item "Verification Items" are correlated.

[0041] "Expected value" represents the behavior that is expected to occur during verification. "Expected value" is defined by the information stored in the "Expected value" item in Figure 4.

[0042] Note that the information included in the second area 32 is not limited to these. It is possible that any of this information is omitted, or that other types of information are included.

[0043] Figure 5 is a schematic diagram showing an example of a pattern table included in a test design document. The pattern table shown in Figure 5 is included in the same test design document as the list of verification items shown in Figure 4. The pattern table shown in Figure 5 includes a first area 31 where metadata of the test design document is stored, and a third area 33 where patterns are stored. The patterns define the content to be verified, the conditions for the behavior to be expressed by the verification process, and specific test cases that are combinations of the verification content and conditions. The first area 31 is the same as the first area 31 shown in Figure 4.

[0044] In the third area 33, for example, at least one pattern is set according to the function to be tested. In the third area 33 shown in Figure 5, two patterns for testing the login function are stored: a login pattern and a password recovery pattern. The pattern number representing each pattern is stored, for example, in the item "No".

[0045] In the patterns stored in Domain 33, the "content to be confirmed" is defined by the information stored in the items "Factor" and "Level." The "conditions for the behavior expressed by the confirmation process" are defined by the conditions described in the item "Expected Value." The "specific test cases" are defined in each column, starting with "1," "2," "3," etc. The processes actually performed in the test are represented by white circles in the column.

[0046] From the test design document, the above elements can be broken down into, for example, information defining the necessary tests and information setting specific test cases. In other words, the test design document can be broken down into "test perspectives," "verification items," and "patterns."

[0047] Client DB282 is a database for storing test design documents created in projects planned within a company, as well as the elements broken down from these test design documents. For example, Client DB282 is a database for sharing test design documents or elements across projects within the same company. In other words, it allows test designers within the company to share information about what test design documents or elements have been created in other projects within the company. Client DB282 is typically set up for each company.

[0048] Standard DB283 is a database for storing test design documents created within multiple companies, as well as the elements decomposed from these test design documents. Standard DB283 is a database for sharing test design documents or elements as a comprehensive, shared knowledge across companies. In Standard DB283, for example, stored test design documents and elements are assigned identifiers representing attributes. Multiple types of attributes can be set, such as industry / sector, system type, and process type. By using attribute identifiers, it is possible to classify test design documents or elements according to their attributes.

[0049] Functional specification 284 is data that describes the specifications of the functions possessed by the object under test. The test designer creates the test design document while referring to functional specification 284. Functional specification 284 includes, for example, an area where detailed functional specifications are stored and an area where message definitions are stored. If functional specification 284 is created using spreadsheet software, these areas are implemented, for example, on different slides. Note that functional specification 284 does not necessarily have to be stored in the storage unit 202 as data. For example, functional specification 284 may be link information to a functional specification stored on the cloud. Alternatively, functional specification 284 may be link information to a specific relevant section of a functional specification stored on the cloud. For example, on the cloud, the functional specification describes the functional specifications for each predetermined display unit. A predetermined display unit is, for example, a page or a ticket. Functional specification may include, for example, update information, and if there are changes to the specifications, the update information will describe the changes.

[0050] The control unit 203 is implemented by the processor 29 reading a program stored in the memory unit 202 and executing instructions contained in the program. The control unit 203 controls the operation of the server 20. Specifically, for example, the control unit 203 performs functions as a transmit / receive unit 2031, a memory control unit 2032, an acquisition unit 2033, a presentation unit 2034, a detection unit 2035, and a calculation unit 2036.

[0051] The transmitting / receiving unit 2031 controls the process by which the server 20 sends and receives data with external devices such as the terminal device 10 in accordance with the communication protocol.

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

[0053] More specifically, the memory control unit 2032 stores the test design documents created by the user via the terminal device 10, and the elements decomposed from the test design documents, in the project DB 281. Furthermore, if the memory control unit 2032 receives instructions to share the test design documents or elements stored in the project DB 281 within the company, it also stores the test design documents and elements stored in the project DB 281 in the client DB 282. Furthermore, if the memory control unit 2032 receives instructions to share the test design documents or elements stored in the project DB 281 or client DB 282 across the entire company, it also stores the test design documents and elements stored in the project DB 281 or client DB 282 in the standard DB 283.

[0054] The memory control unit 2032 tags, for example, the test design document and the elements decomposed from the test design document, and stores them in the project DB281, client DB282, or standard DB283. The tags are, for example, information that individually represents the characteristics of the test. The tags can be arbitrarily set, for example, by the person who created the test design document.

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

[0056] The acquisition unit 2033 may accept text information input from the user. The acquisition unit 2033 compares the input text information with the names, tags, etc., of test design documents or elements stored in a database specified by the user. The acquisition unit 2033 retrieves test design documents or elements with names or tags that match the input text information. The acquisition unit 2033 may also retrieve test design documents or elements with names or tags that include the input text information. The acquisition unit 2033 may also retrieve test design documents or elements with names or tags that are inferred from the input text information.

[0057] Furthermore, the acquisition unit 2033 acquires the test design document or elements associated with the modified functional specification document 284 from the storage unit 202.

[0058] The presentation unit 2034 presents the acquired information to the user. The detection unit 2035 detects whether or not there have been any changes in the functional specification 284. The calculation unit 2036 calculates index values ​​based on the reuse of accumulated data.

[0059] <2 Data Structure> Figures 6 to 8 show the data structure of the database stored by server 20. Figures 6 to 8 illustrate the example of how "test perspectives," "verification items," and "patterns" are broken down from the test design document. Note that Figures 6 to 8 are examples and do not exclude data not shown.

[0060] Figure 6 shows the data structure of project DB281. As shown in Figure 6, project DB281 stores test design document 2811, pattern 2812, and test perspective 2813. Each record of test design document 2811 includes fields such as "file name", "designer", "reviewer", "status", "link", and "latest update".

[0061] The "File Name" field stores the name of the test design document. The "Designer" field stores the name of the person who created the test design document. Additionally, the "Designer" field stores the name of the person creating the test design document.

[0062] The "Reviewer" field stores the name of the person who reviewed the test design document. The "Status" field records the current state of the test design document. Examples of "Status" fields include "Working" (in progress), "Reviewing" (under review), and "Done" (completed).

[0063] The "Link" item stores the functional specification document associated with the test design document. The "Link" item may associate the functional specification document itself, or it may associate the relevant section of the functional specification document. For example, if the functional specification document is a spreadsheet, the relevant section of the functional specification document may be stored using representations such as slides, rows, or cells. The "Latest Update" item stores the most recent date and time the test design document was updated.

[0064] Each record in pattern 2812 includes fields such as "Pattern Name," "Pattern Number," "File Name," and "Latest Update." The "Pattern Name" field stores the name of the pattern. The "Pattern Number" field stores the unique number assigned to each pattern.

[0065] The "File Name" field stores the name of the original test design document from which the files were disassembled. The "Latest Update" item remembers the most recent date and time the pattern was updated.

[0066] Each record in Test Perspective 2813 includes fields such as "Test Perspective", "Verification Item", "Category 1", "Category 2", and "Latest Update". The "Test Perspectives" item stores the information listed under the "Test Perspectives" item in the list of verification items. The item "Confirmation Items" stores the information listed under the "Confirmation Items" item in the list of confirmation items.

[0067] The "Category 1" field stores information about the first classification assigned to the test perspective. The information stored in "Category 1" is set by the user, for example, when inputting test perspectives during the test design document creation phase. The information stored in "Category 1" is also set by the user, for example, by selecting from several pre-configured fields.

[0068] The "Category 2" field stores information about the second classification assigned to the test perspective. The information stored in "Category 2" is set by the user, for example, when inputting test perspectives during the test design document creation phase. The information stored in "Category 2" is also set by the user, for example, by selecting from several pre-configured fields. The "Latest Update" item remembers the most recent date and time when the test perspective was updated.

[0069] Figure 7 shows the data structure of client DB282. As shown in Figure 7, client DB282 stores test design document 2821, pattern 2822, and test perspective 2823. Each record in test design document 2821 includes fields such as "file name", "tag", "designer", "project", "service", "link", and "latest update". The fields "file name", "designer", "link", and "latest update" are the same fields as those in test design document 2811 shown in Figure 6.

[0070] The "Tags" field stores information that describes the characteristics of a test. This "Tags" information is automatically set, for example, based on information configured for the project, when the test design document stored in Project DB281 is stored in Client DB282. Alternatively, the "Tags" information can be set arbitrarily by the user. The "Project" field stores the name of the project for which the test design document was created. The "Service" item stores the name of the service in which the subject of the test is used.

[0071] Test design document 2821 includes not only the test design documents stored in test design document 2811 shown in Figure 6, but also test design documents created in other projects within the same company.

[0072] Each record in pattern 2822 includes fields such as "Pattern Name," "Pattern Number," "Tags," "File Name," "Project," "Service," and "Latest Update." The fields "Pattern Name," "Pattern Number," "File Name," and "Latest Update" are the same fields as those in pattern 2812 shown in Figure 6.

[0073] The "Tags" field stores the information attached as tags to the original test design document from which the components were disassembled. The "Project" field stores the name of the project in which the original test design document was created. The "Service" item stores the name of the service in which the subject of the test is used.

[0074] Pattern 2822 includes patterns stored in Pattern 2812, as shown in Figure 6, as well as patterns decomposed from test design documents created in other projects within the same company.

[0075] Each record in Test Perspective 2823 includes fields such as "Test Perspective", "Verification Item", "Tags", "Category 1", "Category 2", and "Latest Update". The fields "Test Perspective", "Verification Item", "Category 1", "Category 2", and "Latest Update" are the same fields as those in Test Perspective 2813 shown in Figure 6.

[0076] The "Tags" field stores the information attached as tags to the original test design document from which the components were disassembled. Test perspective 2823 includes test perspectives stored in test perspective 2813, as shown in Figure 6, as well as test perspectives decomposed from test design documents created in other projects within the same company.

[0077] Figure 8 shows the data structure of standard DB283. As shown in Figure 8, standard DB283 stores test design document 2831, pattern 2832, and test perspective 2833. Each record in test design document 2831 includes fields such as "file name", "tag", "designer", "project", "service", "attribute", "link", and "latest update". The fields "file name", "tag", "designer", "project", "service", "link", and "latest update" are the same fields as those in test design document 2821 shown in Figure 7.

[0078] The "Attributes" field stores information representing the type to which the test design document belongs. Multiple types of attributes can be set in the "Attributes" field; for example, one or more attributes can be set from industry / sector, system type, process type, etc. Information related to the "Attributes" field is set, for example, when storing test design documents stored in project DB281 or client DB282 into standard DB283. Information related to the "Attributes" field is also set, for example, based on tags attached to test design documents stored in client DB282.

[0079] Test design document 2831 includes not only the test design documents stored in test design document 2821 shown in Figure 7, but also test design documents created for projects at other companies.

[0080] Each record in pattern 2832 includes fields such as "Pattern Name," "Pattern Number," "Tags," "File Name," "Project," "Service," "Attributes," and "Latest Update." The fields "Pattern Name," "Pattern Number," "Tags," "File Name," "Project," "Service," and "Latest Update" are the same fields as those in pattern 2822 shown in Figure 7.

[0081] The "Attributes" field stores information indicating the type to which the original test design document belongs. Pattern 2832 includes patterns stored in Pattern 2822, as shown in Figure 7, as well as patterns decomposed from test design documents created for projects at other companies.

[0082] Each record in Test Perspective 2833 includes fields such as "Test Perspective", "Verification Item", "Tags", "Category 1", "Category 2", "Attributes", and "Latest Update". The fields "Test Perspective", "Verification Item", "Tags", "Category 1", "Category 2", and "Latest Update" are the same fields as those in Test Perspective 2823 shown in Figure 7.

[0083] The "Attributes" field stores information indicating the type to which the original test design document belongs. Test perspective 2833 includes test perspectives stored in test perspective 2823, as shown in Figure 7, as well as test perspectives decomposed from test design documents created in projects at other companies.

[0084] <3 Summary> Figure 9 is a schematic diagram illustrating the concept of System 1 according to this embodiment. Project DB 281, Client DB 282, and Standard DB 283 are provided for each layer corresponding to the business. By storing the test design documents 2811, patterns 2812, and test perspectives 2813 created within the project in Project DB 281, it becomes possible for those involved in the project to share information about what test design documents, patterns, and test perspectives have been created within the project.

[0085] Furthermore, by storing test design documents 2821, patterns 2822, and test perspectives 2823 created in multiple projects planned within the company in client DB282, it becomes possible for test designers within the company to share information about what test design documents, patterns, and test perspectives have been created in other projects within the company.

[0086] Furthermore, by storing selected test design documents 2831, patterns 2832, and test perspectives 2833 from among the test design documents, patterns, and test perspectives created within multiple companies using the standard DB283, it becomes possible to understand the characteristics of each company's attributes, and to propose the optimal test design when formulating test designs.

[0087] <4 Display screen> Figures 10 to 19 show the display screens shown on the display 141 of the terminal device 10. Note that Figures 10 to 19 are examples and do not limit the display screens of the display 141. Figure 10 is a schematic diagram showing an example of a screen for selecting a desired project. The screen shown in Figure 10 has a first area 41, a second area 42, a third area 43, and a fourth area 44.

[0088] The first area 41 includes field objects 411-415, a search box 416, and a selection object 417. Field object 411 is an object that receives instructions to create a new test design document.

[0089] Field objects 412-415 are objects that accept database specifications from the user. Specifically, field objects 412-415 are objects that accept specifications for My Drive, Project DB281, Client DB282, and Standard DB283, respectively.

[0090] Search box 416 is a box for receiving search keywords from the user. The selection object 417 is an object that represents the user's selection from the field objects 412 to 415. When the user selects one of the field objects 412 to 415, the selection object 417 stops on the selected object.

[0091] In the screen shown in Figure 10, the field object 413, which specifies project DB281, is selected by the selection object 417. The acquisition unit 2033 retrieves data from the selected database. The presentation unit 2034 presents the retrieved data to the user.

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

[0093] Field objects 421-423 are objects for receiving project specifications from the user. Specifically, field objects 421-423 are objects for receiving specifications for projects 1-3, respectively. Although Figure 10 illustrates the case with three projects, there is no limit to the number of projects. Also, project names can be set arbitrarily.

[0094] Field object 424 is an object for receiving instructions to create a new project. When field object 424 is pressed, a new project is created. When a new project is created, information about the project is entered by the user. This information includes, for example, the project process type, system type, development scale, industry, and sector. The memory control unit 2032 stores the project information in, for example, the project DB 281.

[0095] Search box 425 is a box for receiving the project name from the user. The selection object 426 represents the user's selection from the field objects 421 to 423. When the user selects one of the field objects 421 to 423, the selection object 426 stops on the selected object.

[0096] In the screen shown in Figure 10, the field object 421, which specifies Project 1, is selected. The acquisition unit 2033 retrieves data from the project DB 281 corresponding to Project 1. The presentation unit 2034 presents the acquired data to the user.

[0097] The third area 43 is an area for displaying a list of test design documents that are currently being worked on (in progress) from the test design documents of the project selected in the second area 42. The third area 43 displays the test design documents that are currently being worked on in a list format. The third area 43 also includes a search box 431 for accepting search keywords from the user.

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

[0099] When the user confirms their project selection in the second area 42, the presentation unit 2034 presents a screen for displaying information about the selected project.

[0100] Figure 11 is a schematic diagram showing an example of a screen for displaying a test design document created in a given project. The screen shown in Figure 11 has a first area 41, a fifth area 45, and a sixth area 46. The first area 41 is the same as the first area 41 shown in Figure 10.

[0101] Area 5, 45, includes field objects 451-454 and selection object 455. Field objects 451-453 are objects that accept user input to specify the data to be displayed. Specifically, field objects 451-454 are objects that accept specifications for design files, test perspectives, and patterns, respectively.

[0102] Field object 454 is an object that receives instructions to store information (test base) related to the functional specification in project DB281. This information related to the functional specification may be, for example, functional specification data in file format, or a link to a functional specification located in the cloud. The selection object 455 represents the user's selection from the field objects 451 to 454. When the user selects one of the field objects 451 to 454, the selection object 455 stops on the selected object.

[0103] In the screen shown in Figure 11, the field object 451, which 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.

[0104] Area 6, 46, is an area for displaying a list of data (test design documents) selected in Area 5, 45. In Area 6, 46, the test design documents are displayed in list format. The test design documents displayed in Area 6, 46, can be edited from the editing screen that expands when the edit icon 461 located at the left end of the list is pressed.

[0105] The test design document displayed in area 6, 46, can be linked to the functional specification document managed in project DB281 by clicking the link icon 462 located at the far right of the list. Specifically, for example, when a user clicks the link icon 462, a pop-up window 463 is displayed. The user clicks "+Link test base" in the pop-up window 463 and selects the functional specification document referenced when creating the test design document from the functional specification documents managed in project DB281. At this time, the user may also input information about the relevant section of the functional specification document that was actually referenced. If the functional specification document is a spreadsheet file, this information may include information such as slides, rows, and cells. If the functional specification document is data managed on the cloud, this information may include information such as pages and tickets. This links the test design document to the functional specification document. It also links the test design document to the relevant section of the functional specification document.

[0106] The test design documents displayed in area 6, 46, can be shared within the same company by clicking the share icon 4617 located at the far right of the list. In other words, the test design documents are stored in the client DB 282. For example, if a user decides that a test design document should be shared with other projects, they click the share icon 4617. When a user clicks the share icon 4617, the storage control unit 2032 stores the test design document of the record for which the share icon 4617 was clicked in the client DB 282. Note that test design documents stored in the client DB 282 can be deleted from the client DB 282 by, for example, a person with the appropriate authority, such as a project leader. By making it possible for even those without the appropriate authority to store test design documents in the client DB 282, the server 20 can activate the sharing of test design documents within the same company. On the other hand, by allowing a person with the appropriate authority to delete test design documents stored in the client DB 282, it is possible to prevent the accumulation of unnecessary test design documents in the client DB 282. Furthermore, an application icon for requesting registration to the standard knowledge base may be placed at the end of the list displayed in area 6, section 46.

[0107] When the memory control unit 2032 stores a test design document in the client DB282, it creates tag information that includes project information related to the test design document. The memory control unit 2032 then attaches the created tag information to the test design document and stores it in the client DB282.

[0108] Furthermore, the sixth area 46 includes a search box 464 for receiving search keywords from the user. Furthermore, area 6, 46, includes field objects 465-467. Field objects 465-467 are objects that receive instructions from the user.

[0109] Specifically, field object 465 is an object for receiving instructions to copy test design documents stored in My Drive. When field object 465 is pressed, the display control unit 183 displays the test design documents stored in the storage unit 170 on the display 141. When one of the displayed test design documents is selected by the user, the terminal device 10 sends 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 as a new record in the list of area 6 46.

[0110] Field object 466 is an object for receiving instructions to copy a test design document stored in client DB282 or standard DB283. When field object 466 is pressed, the acquisition unit 2033 acquires the test design document stored in client DB282 or standard DB283. The presentation unit 2034 presents the acquired data to the user. When the user selects one of the presented test design documents, the storage control unit 2032 stores the selected test design document in project DB281. The test design document newly stored in project DB281 is displayed as a new record in the list of area 6 46.

[0111] Field object 467 is an object that receives instructions to upload a test design document.

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

[0113] Figure 12 is a schematic diagram showing an example of a screen for displaying test perspectives created in a given project. The screen shown in Figure 12 has a first domain 41, a fifth domain 45, and a sixth domain 46. The first domain 41 is the same as the first domain 41 shown in Figure 10.

[0114] In domain 5 45, the field object 452, which 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.

[0115] Domain 6, 46, is an area for displaying a list of data (test perspectives) selected in Domain 5, 45. The test perspectives are displayed in a list format in Domain 6, 46.

[0116] The test perspectives displayed in Area 6, Section 46 are not limited to test perspectives for test designs already created in the project or test designs currently being created in the project. Users may pre-select and register test perspectives suitable for the project from those stored in the client DB282 or standard DB283. The selected test perspectives are stored in the project DB281.

[0117] Whether a test perspective is related to a test design document created within the project or is a pre-registered test perspective is determined by the description in the "Source" field displayed in Area 6, Section 46. In other words, if the description in the "Source" field is "Project Perspective," it indicates that the test perspective is related to a test design document created within the project. Also, if the description in the "Source" field is "Shared Perspective" or "Standard Perspective," it indicates that the test perspective was selected from Client DB282 or Standard DB283.

[0118] Furthermore, area 6, 46, contains field objects 468-4610. Field objects 468-4610 are objects for receiving instructions from the user.

[0119] Specifically, field object 468 is an object for receiving instructions to add a new test viewpoint. When field object 468 is pressed, the display control unit 183 displays an input form for entering the test viewpoint on the display 141.

[0120] Field object 469 is an object for receiving instructions to request the display of test perspectives stored in standard DB283. When field object 469 is pressed, the acquisition unit 2033 acquires the test perspectives stored in standard DB283. The presentation unit 2034 presents the acquired data to the user. At this time, the presentation unit 2034 may present the test perspectives that the user is expected to desire in an easily visible position. For example, the presentation unit 2034 may present the test perspectives to the user such that test perspectives tagged with the same or similar content as the stored project information appear at the top.

[0121] When the user selects one of the presented test perspectives, the memory control unit 2032 stores the selected test perspective in the project DB 281. The newly stored test perspective in the project DB 281 is displayed as a new record in the list of area 6 46.

[0122] Field object 4610 is an object for receiving instructions to request the display of test perspectives stored in client DB 282. When field object 4610 is pressed, acquisition unit 2033 acquires the test perspectives stored in client DB 282. Presentation unit 2034 presents the acquired data to the user. At this time, presentation unit 2034 may present the test perspectives that the user is expected to desire in an easily visible position. For example, presentation unit 2034 may present test perspectives to the user such that test perspectives tagged with the same or similar content as the stored project information appear at the top.

[0123] When the user selects one of the presented test perspectives, the memory control unit 2032 stores the selected test perspective in the project DB 281. The newly stored test perspective in the project DB 281 is displayed as a new record in the list of area 6 46.

[0124] Although Figure 12 does not explain how to link test perspectives with functional specifications, it is possible to link test perspectives with functional specifications, similar to test design documents. Alternatively, test perspectives may be linked with the corresponding sections of functional specifications. Furthermore, similar to the test design document shown in Figure 11, a sharing icon may be provided to allow sharing of test perspectives within the same company.

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

[0126] Figure 13 is a schematic diagram showing an example of a screen for displaying a pattern created in a given project. The screen shown in Figure 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 Figure 10.

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

[0128] Area 6, 46, is an area for displaying a list of data (patterns) selected in Area 5, 45. The patterns are displayed in list format in Area 6, 46.

[0129] The patterns displayed in Area 6, Section 46 are not limited to patterns for test design documents already created in the project or test design documents currently being created in the project. Users may pre-select and register patterns suitable for their project from patterns stored in Client DB282 or Standard DB283. The selected patterns are stored in Project DB281.

[0130] Whether a pattern is related to a test design document created within a project or is a pre-registered pattern can be determined from the "Source" field displayed in area 6, section 46. In other words, if the "Source" field is set to "Project," it indicates that the pattern is related to a test design document created within the project. Also, if the "Source" field is set to "Shared" or "Standard," it indicates that the pattern was selected from client DB282 or standard DB283.

[0131] Furthermore, area 6, 46, contains field objects 4611-4613. Field objects 4611-4613 are objects for receiving instructions from the user.

[0132] Specifically, field object 4611 is an object for receiving instructions to add a new pattern. When field object 4611 is pressed, the display control unit 183 displays an input form for entering a pattern on the display 141.

[0133] Field object 4612 is an object that receives instructions requesting the display of patterns stored in standard DB283. When field object 4612 is pressed, the acquisition unit 2033 acquires patterns stored in standard DB283. The presentation unit 2034 presents the acquired data to the user. When the user selects one of the presented patterns, the storage control unit 2032 stores the selected pattern in project DB281. The pattern newly stored in project DB281 is displayed as a new record in the list of area 6 46.

[0134] Field object 4613 is an object that receives instructions requesting the display of patterns stored in client DB 282. When field object 4613 is pressed, the acquisition unit 2033 acquires the patterns stored in client DB 282. The presentation unit 2034 presents the acquired data to the user. When the user selects one of the presented patterns, the storage control unit 2032 stores the selected pattern in project DB 281. The pattern newly stored in project DB 281 is displayed as a new record in the list of area 6 46.

[0135] Although Figure 13 does not explain how to associate patterns with functional specifications, it is possible to associate patterns with functional specifications, similar to test design documents. Alternatively, patterns can be associated with the corresponding sections of functional specifications. Furthermore, similar to the test design documents shown in Figure 11, a sharing icon can be provided to allow patterns to be shared within the same company.

[0136] When the user selects a 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.

[0137] Figure 14 is a schematic diagram showing an example of a screen for displaying test design documents shared within a company. The screen shown in Figure 14 has three domains: Domain 1 41, Domain 7 47, and Domain 8 48.

[0138] In the first region 41, the field object 414, which specifies the shared file, is selected by the selection object 417. Area 7, 47, includes field objects 471-475 and selection object 476.

[0139] Field objects 471-473 are objects that accept user input to specify the data to be displayed. Specifically, field objects 471-473 are objects that accept specifications for design files, patterns, and test perspectives, respectively.

[0140] Field object 474 is an object that accepts instructions to search for data based on tags. Field object 475 is an object that represents the currently selected database and data type. In Figure 14, client DB282 is selected and the display of test design documents is selected, so field object 475 is labeled "Shared Design Document".

[0141] The selection object 476 represents the user's selection from the field objects 471 to 474. When the user selects one of the field objects 471 to 474, the selection object 476 stops on the selected object.

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

[0143] Area 8, 48, is an area for displaying a list of data (test design documents) selected in Area 7, 47. In Area 8, 48, the test design documents are displayed in list format.

[0144] The test design document displayed in area 8 48 can be shared in the standard knowledge by clicking the application icon 482 located at the far right of the list. In other words, the test design document is stored in the standard DB 283. For example, a user considers the generality, importance, etc., of the test design document and decides whether or not to share it in the standard knowledge. If it should be shared in the standard knowledge, the user clicks the application icon 482. When the user clicks the application icon 482, the storage control unit 2032 stores the test design document of the record for which the application icon 482 was clicked in the standard DB 283. The test design document of the record for which the application icon 482 was clicked enters an application state and may be stored in the standard DB 283 after permission from a person with the prescribed authority. Note that special privileges may be required to store test design documents accumulated in the shared knowledge (client DB 282) in the standard DB 283. For example, a system administrator has the authority to submit requests, and based on the administrator's judgment, test design documents to be stored in the shared knowledge base are stored in the standard DB283. By establishing such permissions, only truly necessary test design documents are stored in the standard DB283. The fact that a test design document is stored in the standard DB283 indicates that it is a test design document that can be widely used. Therefore, the number of test design documents stored in the standard DB283 can be used as a criterion for evaluating test designers.

[0145] When the memory control unit 2032 stores the test design document in the standard DB283, it sets the attributes of the test design document based on the tags attached to the test design document. The memory control unit 2032 then stores the test design document in the standard DB283 along with the set attributes.

[0146] Furthermore, the eighth area 48 includes a search box 481 for receiving search keywords from the user.

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

[0148] Figure 15 is a schematic diagram illustrating an example of a screen for displaying patterns shared within a company. The screen shown in Figure 15 has a first area 41, a seventh area 47, and an eighth area 48. The first area 41 is the same as the first area 41 shown in Figure 14.

[0149] In area 7 47, the field object 472 that specifies the pattern is selected by the selection object 476. The acquisition unit 2033 retrieves data about the pattern from the client DB 282. The presentation unit 2034 presents the retrieved data to the user.

[0150] Area 8, 48, is an area for displaying a list of data (patterns) selected in Area 7, 47. The patterns are displayed in list format in Area 8, 48.

[0151] Any of the patterns displayed in the list may be selected by the user to be stored in the standard DB283. When the user provides an instruction to store the pattern in the standard DB283, the storage control unit 2032 stores the pattern selected by the user in the standard DB283.

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

[0153] Figure 16 is a schematic diagram illustrating an example of a screen for displaying test perspectives shared within a company. The screen shown in Figure 16 has three domains: Domain 1 41, Domain 7 47, and Domain 8 48. Domain 1 41 is the same as Domain 1 41 shown in Figure 14.

[0154] In area 7 47, the field object 473, which specifies the test viewpoint, is selected by the selection object 476. The acquisition unit 2033 retrieves data about the test viewpoint from the client DB 282. The presentation unit 2034 presents the acquired data to the user.

[0155] Domain 8 (48) is an area for displaying a list of data (test perspectives) selected in Domain 7 (47). The test perspectives are displayed in a list format in Domain 8 (48).

[0156] Any of the test viewpoints displayed in the list may be instructed by the user to be stored in the standard DB283. When the user instructs to store in the standard DB283, the storage control unit 2032 stores the test viewpoint selected by the user in the standard DB283.

[0157] When the user selects a 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.

[0158] Figure 17 is a schematic diagram showing an example of a screen for displaying test design documents stored in standard knowledge. The screen shown in Figure 17 has a first domain 41, a seventh domain 47, and an eighth domain 48.

[0159] In the first area 41, the field object 415 that specifies knowledge is selected by the selection object 417.

[0160] In area 7, 47, the standard DB283 is selected, so the field object 475 is labeled "TD (registered trademark)". Also, the field object 471, which 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 DB283. The presentation unit 2034 presents the acquired data to the user.

[0161] Area 8, 48, is an area for displaying a list of data (test design documents) selected in Area 7, 47. In Area 8, 48, the test design documents are displayed in list format.

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

[0163] Figure 18 is a schematic diagram showing an example of a screen for displaying patterns stored in standard knowledge. The screen shown in Figure 18 has a first area 41, a seventh area 47, and an eighth area 48. The first area 41 is the same as the first area 41 shown in Figure 17.

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

[0165] Area 8, 48, is an area for displaying a list of data (patterns) selected in Area 7, 47. The patterns are displayed in list format in Area 8, 48.

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

[0167] Figure 19 is a schematic diagram showing an example of a screen for retrieving test perspectives stored in standard knowledge. The screen shown in Figure 19 has a first domain 41, a seventh domain 47, and an eighth domain 48. The first domain 41 is the same as the first domain 41 shown in Figure 17.

[0168] In area 7 47, the field object 473, which specifies the test viewpoint, is selected by the selection object 476. The acquisition unit 2033 retrieves data about the test viewpoint from the standard DB 283. The presentation unit 2034 presents the acquired data to the user.

[0169] Domain 8 (48) is an area for displaying a list of data (test perspectives) selected in Domain 7 (47). The test perspectives are displayed in a list format in Domain 8 (48).

[0170] <5 Operations> (Creating test design documents) The process performed by server 20 when a test design document is created will be explained along with the display screen of display 141.

[0171] First, we will explain how to create a test design document by copying a test design document stored in client DB282 or standard DB283. For example, consider a scenario where a user reuses a test design document from their existing collection of test design documents for use in Project 1. The user clicks field object 466, "Copy from Shared Files / Knowledge," on the screen shown in Figure 11.

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

[0173] The display control unit 183 causes the display window 4614, which lists the test design documents read from, for example, the client DB 282 and the standard DB 283, to be displayed on the display 141. Figure 20 is a schematic diagram illustrating an example of a list display of test design documents. The display window 4614 contains a reference icon 4615 and field objects 4616 and 4617. The reference icon 4615 is located at the far left of the list and is an icon for receiving a request to display a test design document.

[0174] Field object 4616 is an object for receiving instructions to create a test design document by reusing a test design document selected by the user. Field object 4617 is an object for receiving instructions to cancel the reuse of the test design document.

[0175] The database from which the test design document displayed in display window 4614 was retrieved can be determined from the entry in the "Source" field. In the example in Figure 20, the test design document with "Shared Knowledge" in the "Source" field was retrieved from client DB282. Similarly, the test design document with "Standard Knowledge" in the "Source" field was retrieved from standard DB283.

[0176] When the user presses the reference icon 4615 located at the left end of the list, the display control unit 183 displays detailed information of the test design document for the record for which the reference icon 4615 was pressed, such as a list of verification items or a pattern table, on the display 141.

[0177] The user reviews the list of items to be checked and the pattern table to determine whether the test design document can be reused in Project 1. If the user determines that the test design document can be reused, they select the test design document that they determined to be reusable and click the field object 4616 displayed in the display window 4614.

[0178] When field object 4616 is pressed, the memory 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 area 46 shown in Figure 11. The created test design document can be edited arbitrarily from the screen shown in Figure 11.

[0179] Figure 20 shows a case where the presentation unit 2034 displays test design documents read from the client DB 282 and the standard DB 283 in a predetermined order. However, the presentation unit 2034 may also display test design documents that the user is expected to want in a position that is easy to see. For example, the presentation unit 2034 may present test design documents to the user such that test design documents tagged with the same or similar content as the stored project information appear at the top of the list.

[0180] Next, we will explain how to create a test design document by reusing test perspectives or patterns stored in Project DB281, Client DB282, or Standard DB283.

[0181] For example, let's assume a user is creating a test design document to be used in Project 1. The user clicks the "New" field object 411 on the screen shown in Figure 11.

[0182] When field object 411 is pressed, the display control unit 183 displays a form for creating a list of confirmation items on the display 141.

[0183] Figure 21 is a schematic diagram showing an example of a screen for creating a list of verification items. The creation screen shown in Figure 21 includes a field object 491. Field object 491 is an object for receiving user input for the list of verification items. When the creation screen is displayed, the user selects, for example, the first cell 4911 of the item "Test Perspectives" to enter test perspectives.

[0184] When cell 4911 is selected, the display control unit 183 displays a confirmation message on the display 141 asking whether or not to display the list of test viewpoints. When the user requests to display 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 viewpoints to the user.

[0185] The display control unit 183, for example, causes the display window 492, which lists the test viewpoints read from the project DB 281, to be displayed on the display 141.

[0186] Figure 22 is a schematic diagram illustrating an example of a list display of test perspectives. The display window 492 contains selection icons 4921 and 4922.

[0187] Selection icons 4921 and 4922 are icons that accept the selection of the database from which to read test perspectives. Specifically, selection icon 4921 accepts the selection of Project DB281. Checking the box on the selection icon selects reading from Project DB281. Selection icon 4922 accepts the selection of Standard DB283. Checking the box on the selection icon selects reading from Standard DB283. Note that display window 492 may also include an icon to accept the selection of reading test perspectives from Client DB282.

[0188] In Figure 22, the selection icon 4921 is checked, and the test perspectives read from Project DB281 are displayed. The "Source" field of the test perspectives read from Project DB281 contains "Project Perspective". When the user checks the selection icon 4922, the test perspectives read from Standard DB283 are displayed (not shown). The "Source" field of the test perspectives read from Standard DB283 contains, for example, "Standard Perspective".

[0189] When a test perspective is selected in display window 492, the selected "test perspective" and the "verification items" included in the selected test perspective are entered into the verification item list.

[0190] Figure 23 is a schematic diagram showing an example of a screen for creating a list of verification items, where "test perspectives" and "verification items" are entered. In Figure 23, "Successful Authentication" is entered in the first cell 4911 of the "Test Perspectives" item, and "Verification Items" is entered in the first cell 4912 of the "Verification Items" item.

[0191] The input screen for the list of confirmation items shown in Figure 23 includes a field object 493 for accepting a transition to the pattern management screen. When the user presses the field object 493, the display control unit 183 displays the pattern management screen on the display 141.

[0192] Figure 24 is a schematic diagram illustrating an example of a pattern management screen. The management screen shown in Figure 24 includes field objects 4101-4104 and a selection object 4105.

[0193] Field object 4101 is an object for receiving instructions to add a new pattern. When field object 4101 is pressed by the user, the display control unit 183 displays field objects 4102 and 4103 on the display 141 for inputting information about the pattern.

[0194] Field object 4102 is an object for accepting selections for managed patterns. If multiple patterns are registered in the confirmation item list, multiple field objects 4102 will be displayed. Field object 4103 is an object for accepting pattern input from the user.

[0195] Field object 4104 is an object that accepts instructions to copy patterns stored in client DB282 or standard DB283.

[0196] The selection object 4105 is an object that represents the user's selection for the field object 4102. When the user selects one of the field objects 4102, the selection object 4105 stops on the selected object.

[0197] When field object 4104 is pressed, acquisition unit 2033 acquires patterns from client DB 282 and standard DB 283. Presentation unit 2034 presents the acquired patterns to terminal device 10.

[0198] The display control unit 183 causes the display window 4106, which lists the patterns read from, for example, the client DB 282 and the standard DB 283, to be displayed on the display 141.

[0199] Figure 25 is a schematic diagram illustrating an example of a pattern list display. The display window 4106 contains a reference icon 4107 and field objects 4108 and 4109. The reference icon 4107 is located at the left end of the list and is the icon that accepts a request to display information about the pattern.

[0200] Field object 4108 is an object for receiving instructions to create a pattern by reusing a pattern selected by the user. Field object 4109 is an object for receiving instructions to cancel the reuse of the pattern.

[0201] The database from which a pattern displayed in display window 4106 was read can be determined from the entry in the "Source" field. In the example in Figure 25, patterns where the "Source" field is "Project" are patterns read from Project DB281. Patterns where the "Source" field is "Client" are test design documents read from Client DB282. Patterns where the "Source" field is "Master" are test design documents read from Standard DB283.

[0202] When the user presses the reference icon 4107 located at the left end of the list, the display control unit 183 displays detailed information about the pattern of the record for which the reference icon 4107 was pressed, such as a pattern table, on the display 141.

[0203] The user checks the pattern table and determines whether the pattern is reusable. If the user determines that the pattern is reusable, they select the pattern they determined to be reusable and press the field object 4108 displayed in the display window 4106.

[0204] When field object 4108 is pressed, the memory 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 Figure 24. Figure 26 is a schematic diagram showing an example of the pattern management screen.

[0205] Figure 25 shows a case where the display unit 2034 displays patterns read from the client DB 282 and the standard DB 283 in a predetermined order. However, the display unit 2034 may also display patterns that are expected to be desired by the user in a position that is easily visible. For example, the display unit 2034 may present patterns to the user such that patterns with tags that are the same as or similar to the stored project information appear at the top.

[0206] (Proposal for revisions based on changes to the functional specification) The process of server 20 when proposing modifications to the test design document or elements in response to revisions to the functional specification document will be explained along with the display screen of display 141.

[0207] Figure 27 is a flowchart showing the processing flow of the control unit 203 when proposing modifications to the test design document or elements in response to revisions to the functional specification document.

[0208] First, the memory control unit 2032 receives information about the functional specifications from the user or a designated site, and stores the received information in the memory unit 202 (step S21).

[0209] The detection unit 2035 determines whether there are any changes to the functional specification 284 linked to the test design document (step S22). For example, the detection unit 2035 obtains information regarding changes to the functional specification 284. Specifically, for example, when changes are made to the functional specification 284, information about the changes is stored in the change information. Based on the change information, the detection unit 2035 identifies the changes in the functional specification 284. Also, for example, if there are changes to the functional specification 284 created using spreadsheet software, the detection unit 2035 detects that there are changes to the functional specification 284 based on the change history, and also detects the changes in the functional specification 284, such as the sheet that was changed, the row that was changed, the cell that was changed, etc.

[0210] The acquisition unit 2033 acquires the test design document associated with the functional specification document 284 in which the change was detected from the project DB 281 (step S23). The acquisition unit 2033 may also acquire elements of the test design document associated with the functional specification document 284 in which the change was detected, such as test perspectives or patterns, from the project DB 281.

[0211] If the test design document is associated with the corresponding section of the functional specification document 284, the acquisition unit 2033 may acquire the test design document, or the elements of the test design document, associated with the changes in the functional specification document 284 from the project DB 281.

[0212] 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, due to changes in the functional specification 284, it may be necessary to modify the acquired test design document or elements of the test design document. The display control unit 183 displays the presented content on the display 141.

[0213] Figure 28 is a schematic diagram illustrating an example of a screen that displays a test design document or a proposed modification of elements of the test design document based on changes to the functional specification document 284. The display control unit 183, for example, displays a display window 4614 on the display 141 in a screen that displays a list of test design documents. The display window 4614 indicates that modifications to the test design document, test perspectives, and patterns may be necessary due to changes in the relevant section of the functional specification document. However, the display in the display window 4614 is not limited to this. Only modifications to the test design document may be proposed, or modifications to the list of verification items and the pattern table of the test design document may also be proposed.

[0214] When a suggested modification is displayed in window 4614, the user checks the relevant functional specification 284 for the modification and considers whether modifications are needed to the test design document or its elements. If modifications are needed, the user modifies the test design document or its elements.

[0215] When a user modifies a test design document or an element of a test design document, the memory control unit 2032 updates the test design document or element of the test design document stored in the project DB281 with the modified data. After updating the data in the project DB281, the memory control unit 2032 determines whether the original test design document or element of the test design document is also stored in the client DB282 or standard DB283. If the original test design document or element of the test design document is also stored in the client DB282 or standard DB283, the memory control unit 2032 updates the data stored in the client DB282 or standard DB283 with the modified data.

[0216] (Generating index values) This section describes the processing performed by Server 20 when test design documents stored in Project DB281, Client DB282, and Standard DB283, or when elements of test design documents are reused to calculate metric values.

[0217] First, the memory control unit 2032 stores in the memory unit 202 the first number of times a test design document or elements of a test design document stored in the project DB 281, client DB 282, or standard DB 283 has been reused. The memory control unit 2032 also stores in the memory unit 202 the second number of times a test designer has reused a test design document or elements of a test design document.

[0218] The calculation unit 2036 calculates a predetermined index value based on the first and second counts stored in the storage unit 202. The index value is, for example, an index value that represents how much the cost of test design has been reduced by reusing test design documents or elements of test design documents stored in the project DB 281, client DB 282, and standard DB 283. For example, the index value includes a reduction value or reduction rate that represents how much the time it took to create one test design document has been reduced by reusing test design documents, etc. The index value also includes a reduction value or reduction rate that represents how much the time spent by a test designer to create one test design document has been reduced by reusing test design documents, etc.

[0219] The display unit 2034 displays the index value calculated by the calculation unit 2036 to the terminal device 10.

[0220] As described above, in the above embodiment, the memory control unit 2032 stores the test design document and the elements decomposed from the test design document in the project DB 281, client DB 282, and standard DB 283, which are provided for each layer corresponding to the business. The presentation unit 2034 then switches and presents the test design document or elements stored in the project DB 281, client DB 282, and standard DB 283 in response to a request from the user. In this way, the server 20 stores the test design document and the elements decomposed from the test design document in the desired database, making it easier for the user to access the desired information.

[0221] Therefore, according to the server 20 described herein, it is possible to effectively utilize previously created test design documents and reduce the burden of test design while maintaining test quality.

[0222] Furthermore, in the above embodiment, the memory control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281, which shares information within the project. This allows the server 20 to store past data created within the project for use within the project.

[0223] Furthermore, in the above embodiment, the memory control unit 2032 stores 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, which shares information across projects. This allows the server 20 to store past data created within a project for use within the company.

[0224] Furthermore, in the above embodiment, the memory control unit 2032 stores either the test design document stored in the project DB 281 or the client DB 282, or one of the elements decomposed from the test design document, in the standard DB 283, which shares information collectively. This allows the server 20 to store past data created within a project or company as standard data for use.

[0225] Furthermore, in the above embodiment, the memory control unit 2032 stores the test design document, or elements decomposed from the test design document, in the standard DB 283 with information indicating the type to which the test design document belongs. As a result, the server 20 classifies the data stored in the standard DB 283 according to the type of company. Therefore, even when a large amount of data is stored in the standard DB 283, the user can efficiently access the desired data.

[0226] Furthermore, in the above embodiment, the memory control unit 2032 ensures that data is stored in a higher-level database in response to instructions from an authorized user. This prevents the amount of data stored in the client DB282 or standard DB283 from becoming excessively large.

[0227] Furthermore, in the above embodiment, the presentation unit 2034 presents the test design document or elements stored in the project DB 281 to users belonging to the project corresponding to the project DB 281. This allows the server 20 to activate information sharing within the project and suppress variations in quality among test designers within the project. In other words, reliance on individual expertise is eliminated, and quality becomes stable.

[0228] Furthermore, in the above embodiment, the presentation unit 2034 presents test design documents or elements stored in the client DB 282 or standard DB 283 to the user. This allows the user to search for desired information from the layer-specific database and quickly access the desired information. In addition, since the quality of tests desired by the client company can be understood in advance, the probability of designing unnecessary tests is reduced, and time loss can be avoided. As a result, it becomes possible to design tests with the optimal cost and optimal quality for the client company throughout the entire project.

[0229] Furthermore, in the above embodiment, the memory control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281, associating them with the functional specification document referenced during creation. The presentation unit 2034 then presents suggested modifications to the test design document or elements associated with the functional specification document if there are any changes to the functional specification document. This allows the user to modify the test design document in real time in conjunction with development. As a result, discrepancies between the actual development target and the tests being designed are minimized. This helps prevent gaps in testing throughout the entire project.

[0230] Furthermore, in the above embodiment, the memory control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281, associating them with the corresponding sections of the functional specification document referenced during creation. The presentation unit 2034 then presents suggested modifications to the test design document or elements associated with the corresponding section if there are any changes to that section. This allows the user to modify the test design document or elements more efficiently in accordance with changes to the functional specification document.

[0231] Furthermore, in the above embodiment, the memory control unit 2032 reflects the changes in the test design document or element that corresponds to the modified test design document or element stored in the higher-level database when the test design document or element associated with the functional specification is modified. As a result, the server 20 can reflect the changes in the functional specification not only in the data stored in the project DB 281, but also in the data stored in the client DB 282 or the standard DB 283.

[0232] Furthermore, in the above embodiment, the memory control unit 2032 stores the test design document and the elements decomposed from the test design document in the project DB 281, client DB 282, and standard DB 283, each tagged with a tag that individually represents the characteristics of the test. The presentation unit 2034 then searches for the test design document or elements stored in each database based on the tags, from the database specified by the user. This allows the user to access the desired data more quickly.

[0233] Furthermore, in the above embodiment, the elements are a test perspective representing the viewpoint on which the test is based, and a pattern table that defines the test cases to be performed. This allows the server 20 to manage data in units of items where the content entered is likely to vary depending on the user's skill level. Therefore, when a user creates a test design document, it is possible to assist in inputting information from the user, thereby reducing the burden of creating the test design document. In addition, variations in the quality of the created test design documents will be suppressed.

[0234] Furthermore, in the above embodiment, the memory control unit 2032 stores the test viewpoints stored in the client DB 282 or standard DB 283 in the project DB 281 before the test design document is created. This allows the server 20 to register the test viewpoints required for the project in advance, thereby reducing the burden on the test designer to set the test viewpoints. It also helps to prevent the omission of necessary test viewpoints.

[0235] Furthermore, in the above embodiment, the calculation unit 2036 calculates an index value representing how much the cost of test design has been reduced, based on the number of times the test design documents or elements stored in the project DB 281, client DB 282, or standard DB 283 have been referenced. This enables the server 20 to quantitatively present the effectiveness of its device to the client company.

[0236] In the above embodiment, the example described was one in which the database is provided in three layers: Project DB281, Client DB282, and Standard DB283. However, the number of layers in which the database according to this embodiment is provided is not limited to three. For example, a layer may be provided above Client DB282 to aggregate information stored in the client layer using predetermined elements. These predetermined elements may be, for example, geographical elements or industry-related elements. Specifically, for example, a database for aggregating information about companies in Eastern Japan and a database for aggregating information about companies in Western Japan may be provided.

[0237] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

[0238] <Note> The details described in each of the above embodiments are noted below.

[0239] (Note 1) A program to be executed on a computer having a processor 29 and memory 25, wherein the program is to be executed on the processor, Step (2032) of storing the test design document and the elements decomposed from the test design document in databases 281, 282, and 283, which are provided for each layer corresponding to the business, Step (2034) to switch and present test design documents or elements stored in each database in response to user requests. A program that executes the command.

[0240] (Note 2) The program described in Appendix 1 stores the created test design document and the elements decomposed from the test design document in a first database 281 for sharing information within the project.

[0241] (Note 3) The program described in Appendix 2 stores, in the memory step, either the test design document stored in the first database or one of the elements decomposed from said test design document, in the second database 282 which shares information across projects.

[0242] (Note 4) The program described in Appendix 3, which, in the memory step, stores either the test design document stored in the first database or the second database, or any of the elements decomposed from said test design document, in the third database 283 which shares information overall.

[0243] (Note 5) The program described in Appendix 4 stores the test design document, or elements decomposed from the test design document, in the storage step, along with information indicating the type to which the test design document belongs, in the third database.

[0244] (Note 6) In the memory step, storing the test design document and the elements decomposed from the test design document in the third database requires the operation of an authorized person, as described in (Appendix 4) or (Appendix 5).

[0245] (Note 7) A program described in any of (Appendix 2) to (Appendix 6) that, in the step of presenting, presents the test design document or elements stored in the first database to the user belonging to the first database and the corresponding project.

[0246] (Note 8) A program described in any of the following (Appendix 3) to (Appendix 7) that presents the test design document or elements stored in the second database to a user belonging to another project within the same client in the step of presentation.

[0247] (Note 9) In the step of presenting, the program described in any of (Appendix 4) to (Appendix 8) presents the test design document or elements stored in the third database to the user.

[0248] (Note 10) In the memory step, the created test design document and the elements decomposed from said test design document are stored in the first database in association with the functional specification document referenced during its creation. A program described in any of the footnotes (2) to (9) that causes the processor to execute a step proposing modifications to the test design document or elements associated with the functional specification document if there are any changes to the functional specification document.

[0249] (Note 11) In the memory step, the created test design document and the elements decomposed from said test design document are stored in the first database, associated with the corresponding sections of the functional specification document referenced during creation. If any changes are made to the relevant section during the proposed steps, the program described in (Appendix 10) proposes modifications to the test design document or elements associated with that section.

[0250] (Note 12) If a test design document or element associated with a functional specification is modified, the program described in (Appendix 10) or (Appendix 11) causes the processor to perform a step to reflect the modification in the modified test design document or element and the corresponding test design document or element stored in the higher-level database.

[0251] (Note 13) In the storing step, store the test design document and the elements decomposed from the test design document in a second database after attaching tags that individually represent the characteristics of the test. In the presenting step, search for the test design document or elements based on the tags using the program described in any one of Appendices 3 to 12.

[0252] (Appendix 14) In the storing step, create attribute information representing the type to which the test design document belongs based on the tag information, and store the test design document or the elements decomposed from the test design document in a third database after attaching the attribute information using the program described in Appendix 13.

[0253] (Appendix 15) The elements are a test perspective that represents a perspective on which the test is based and a pattern table that defines the test cases to be executed using the program described in any one of Appendices 1 to 14.

[0254] (Appendix 16) The elements are a test perspective that represents a perspective on which the test is based and a pattern table that defines the test cases to be executed, In the storing step, store the test perspective stored in the second database or the third database in a first database before the test design document is created using the program described in any one of Appendices 4 to 6.

[0255] (Appendix 17) Cause the processor to execute a step (2036) of calculating an index value based on the number of references to the test design document or elements stored in the first database, the second database, or the third database using the program described in any one of Appendices 4 to 6.

[0256] (Appendix 18) A program for causing a computer including a processor and a memory to execute. The program causes the processor to, The steps include: storing the created test design document in a database, associating it with the functional specification document referenced during its creation; If there are any changes to the functional specification, the step of proposing revisions to the test design document associated with that functional specification is... A program that causes the processor to execute.

[0257] (Note 19) In the memory step, the created test design document is stored in the database, associated with the corresponding section of the functional specification document referenced during its creation. In the proposed steps, if there are any changes to the relevant section, the program described in (Appendix 18) proposes to revise the test design document associated with that section.

[0258] (Note 20) A method performed by a computer having a processor and memory, The steps include storing the test design document and the elements decomposed from the test design document in a database established for each layer corresponding to the business process, In response to user requests, the test design documents stored in each database, or the steps to switch and present the elements, and How to do it.

[0259] (Note 21) An information processing device comprising a processor and memory, The processor, The steps include storing the test design document and the elements decomposed from the test design document in a database established for each layer corresponding to the business process, In response to user requests, the test design documents stored in each database, or the steps to switch and present the elements, and An information processing device that performs the following actions.

[0260] (Note 22) A means for storing test design documents and elements decomposed from said test design documents in databases provided for each layer corresponding to the business, Means for switching and presenting a test design document or elements stored for each database in response to a request from a user A system comprising the above

Explanation of Signs

[0261] 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 / reception unit 183…Display control unit 19…Processor 20…Server 201…Communication unit 202…Storage unit 203…Control unit 2031…Transmission / reception unit 2032…Memory 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 perspective 282…Client DB 2821…Test design document 2822…Pattern 2823…Test perspective 283…Standard DB 2831…Test design document 2832…Pattern 2833…Test perspectives 284... Functional Specifications 29… Processor

Claims

1. A program to be executed by a computer having a processor and memory, wherein the program is to be executed by the processor, The steps include storing the test design document and the elements decomposed from the test design document in a database provided for each layer corresponding to the business process, In response to a user request, the test design document or elements stored in each database are switched and presented. A program that executes the command.

2. The program according to claim 1, wherein in the memory step, 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.

3. The program according to claim 2, wherein in the memory step, either the test design document stored in the first database or the elements decomposed from the test design document is stored in a second database for sharing information across projects.

4. The program according to claim 3, wherein in the storage step, either a test design document stored in the first database or the second database, or any of the elements decomposed from the test design document, is stored in a third database that shares information collectively.

5. The program according to claim 4, wherein in the storage step, the test design document or elements decomposed from the test design document are stored in the third database with information indicating the type to which the test design document belongs.

6. The program according to claim 4 or 5, wherein in the storage step, the operation of an authorized person is required to store the test design document and the elements decomposed from the test design document in the third database.

7. The program according to any one of claims 2 to 6, wherein in the step described above, the test design document or elements stored in the first database are presented to a user belonging to the project corresponding to the first database.

8. The program according to any one of claims 3 to 7, wherein in the step described above, the test design document or elements stored in the second database are presented to a user belonging to another project within the same client.

9. The program according to any one of claims 4 to 8, which in the step described above presents to the user a test design document or elements stored in the third database.

10. In the storage step, 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 specification document referenced during its creation. The program according to any one of claims 2 to 9, which causes the processor to perform a step of proposing a modification to the test design document or elements associated with the functional specification document if there is a change to the functional specification document.

11. In the storage step, 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 sections of the functional specification document referenced during creation. The program according to claim 10, which, in the steps proposed above, proposes to modify the test design document or element associated with the relevant part if there is a change in that part.

12. The program according to claim 10 or 11, which, if a test design document or element associated with the functional specification is modified, causes the processor to perform a step of reflecting the modification in the test design document or element corresponding to the modified test design document or element stored in a higher-level database.

13. In the aforementioned storage step, the test design document and the elements decomposed from the test design document are stored in the second database, each tagged with a tag that individually represents the characteristics of the test. The program according to any one of claims 3 to 12, which searches for the test design document or elements based on the tags in the steps described above.

14. The program according to claim 13, wherein in the storage step, attribute information representing the type to which the test design document belongs is created based on the information of the tag, and the test design document, or elements decomposed from the test design document, are stored in the third database with the attribute information attached.

15. The program according to any one of claims 1 to 14, wherein the aforementioned elements are a test perspective representing the viewpoint on which the test is based, and a pattern table defining the test cases to be performed.

16. The aforementioned elements are a test perspective representing the viewpoint on which the test is based, and a pattern table that defines the test cases to be performed. The program according to any one of claims 4 to 6, wherein in the storage step, the test viewpoints stored in the second database or the third database are stored in the first database before the test design document is created.

17. The program according to any one of claims 4 to 6, which causes the processor to perform the step of calculating an index value based on the number of times a test design document or element is referenced stored in the first database, the second database, or the third database.

18. A program to be executed by a computer having a processor and memory, wherein the program is to be executed by the processor, The steps include: storing the created test design document in a database, associating it with the functional specification document referenced during its creation; If there are any changes to the aforementioned functional specification, the step of proposing revisions to the test design document associated with that functional specification is to be made. A program that causes the aforementioned processor to execute.

19. In the memory step, the created test design document is stored in the database in association with the corresponding section of the functional specification document referenced during its creation. The program according to claim 18, which, in the steps proposed above, proposes to modify the test design document associated with the relevant part if there is a change in that part.

20. A method performed by a computer having a processor and memory, The steps include storing the test design document and the elements decomposed from the test design document in a database provided for each layer corresponding to the business process, In response to a user request, the test design document or elements stored in each database are switched and presented. How to do it.

21. An information processing device comprising a processor and memory, The aforementioned processor, The steps include storing the test design document and the elements decomposed from the test design document in a database provided for each layer corresponding to the business process, In response to a user request, the test design document or elements stored in each database are switched and presented. An information processing device that performs the following actions.

22. A means for storing test design documents and elements decomposed from said test design documents in databases provided for each layer corresponding to the business, In response to user requests, a means for switching and presenting test design documents or elements stored in each of the aforementioned databases. A system that is equipped with [the following].

Images