Program, method, information processing device, and system

Abstract

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

Description

[Technical Field]

[0001] The present disclosure relates to a program, a method, an information processing device, and a system. [Background technology]

[0002] To ensure the quality of software, its functionality is tested before it is released. Tests are designed based on the software specifications to ensure the desired quality is achieved within the development schedule and budget set by the software development company. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2020-98413 Summary of the Invention [Problem to be solved by the invention]

[0004] Designing tests that meet the client's intentions requires advanced knowledge and extensive experience. To reduce the burden of creating a test design document, Patent Document 1 provides a database that stores multiple test perspectives that indicate the perspectives to be used when conducting tests. Test cases are then generated from specification items extracted from the system specifications and the test perspectives stored in the database.

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

[0006] The present disclosure aims to reduce the burden of test design while maintaining test quality by effectively using test design documents created in the past. [Means for solving the problem]

[0007] In order to solve the above problem, the program disclosed herein causes a processor to execute the steps of storing a test design document and elements decomposed from the test design document in a database provided for each layer corresponding to the business, and switching and presenting the test design document or elements stored in each database in response to a request from a user. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to effectively use test design documents created in the past, thereby reducing the burden of test design while maintaining the quality of the tests. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram showing the overall configuration of a system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a block diagram showing the configuration of a terminal device included in the system of the present embodiment. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a server included in the system of the present embodiment. [Figure 4] FIG. 10 is a diagram showing a list of check items included in a test design document. [Figure 5] FIG. 10 is a diagram illustrating a pattern table included in a test design document. [Figure 6] FIG. 2 is a diagram illustrating a data structure of a project DB. [Figure 7] FIG. 10 is a diagram illustrating a data structure of a client DB. [Figure 8] FIG. 10 is a diagram illustrating the data structure of a standard DB. [Figure 9] FIG. 1 is a diagram schematically illustrating the concept of a system according to an embodiment of the present invention. [Figure 10] FIG. 10 is a diagram illustrating a screen for selecting a desired project. [Figure 11] FIG. 10 is a diagram illustrating a screen for displaying a test design document created in a predetermined project. [Figure 12] FIG. 10 is a diagram illustrating a screen for displaying test viewpoints created in a specific project. [Figure 13] FIG. 10 is a diagram illustrating a screen for displaying a pattern created in a predetermined project. [Figure 14] FIG. 10 is a diagram illustrating a screen for displaying a test design document shared within a company. [Figure 15] FIG. 10 is a diagram illustrating a screen for displaying patterns shared within a company. [Figure 16] FIG. 10 is a diagram illustrating a screen for displaying test viewpoints shared within a company. [Figure 17] FIG. 10 is a diagram illustrating a screen for displaying a test design document stored in standard knowledge. [Figure 18] FIG. 10 is a diagram showing a screen for displaying patterns stored in standard knowledge. [Figure 19] FIG. 10 is a diagram showing a screen for reading out test viewpoints stored in standard knowledge. [Figure 20] FIG. 10 is a diagram illustrating a list display of a test design document. [Figure 21] FIG. 10 is a diagram illustrating a screen for creating a list of confirmation items. [Figure 22] FIG. 10 is a diagram illustrating a list display of test viewpoints. [Figure 23] FIG. 10 is a diagram illustrating a creation screen for a check item list on which "test viewpoints" and "check items" have been input. [Figure 24] FIG. 10 is a diagram illustrating a pattern management screen. [Figure 25] FIG. 10 is a diagram showing a list display of patterns. [Figure 26] FIG. 10 is a diagram illustrating a pattern management screen. [Figure 27] 10 is a flowchart showing the flow of processing by the control unit when proposing a test design document or an element modification in response to a modification of a functional specification document. [Figure 28] 10 is a diagram showing a screen displaying a test design document based on a change in a functional specification document or a modification proposal for an element of the test design document. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments will be described with reference to the drawings. Note that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all of the configurations described in the embodiments are necessarily essential components of the present disclosure.

[0011] <Summary> The system 1 according to this embodiment decomposes a created test design document into elements, and stores the test design document and the decomposed elements for each business hierarchy.The system 1 then presents the stored test design document or elements in response to a request from a test designer or a manager.

[0012] In this embodiment, the test design document is data in which tests are designed to test the functions of the test object. The test object represents the object of the test, such as hardware or software developed in a specific project. The test object includes, for example, a prototype, an intermediate product, and a final product. The function represents the function of the various components that make up the test object.

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

[0014] 1 shows a case where the server 20 is one computer, but the server 20 may be realized by combining multiple computers. Also, while FIG. 1 shows a case where there is one terminal device 10, the number of terminal devices 10 accommodated in the system 1 may be multiple.

[0015] The terminal device 10 is a terminal used by a user who uses the services provided by the server 20. For example, the terminal device 10 is a terminal used by a test designer who creates a test design document. The terminal device 10 is realized by, for example, a desktop personal computer (PC), a laptop PC, a head-mounted display, or the like. The terminal device 10 may also be a portable computer such as a smartphone or a tablet terminal.

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

[0017] The communication IF 12 is an interface for transmitting and receiving signals so that the terminal device 10 can communicate with external devices. The input device 13 is an input device for receiving input operations from a user (employee). The input device 13 includes, for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc. The output device 14 is an output device for presenting information to a user. The output device 14 includes, for example, a display, a speaker, etc.

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

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

[0020] 1, the server 20 includes a communication IF 22, an input / output IF 23, a memory 25, a storage 26, and a processor 29. The communication IF 22, the input / output IF 23, the memory 25, the storage 26, and the processor 29 are connected to each other so as to be able to communicate with each other, for example, via a bus.

[0021] The communication IF 22 is an interface for transmitting and receiving signals so that the server 20 can communicate with external devices. The input / output IF 23 functions as an interface with an input device for receiving input operations from a user and an output device for presenting information to the user. The memory 25 is for temporarily storing programs and data processed by the programs, etc., and is realized by a volatile memory such as a DRAM.

[0022] The storage 26 is a storage device for saving data, and is realized by a non-volatile memory such as a flash memory or a HDD. The storage 26 does not necessarily have to be realized by a single circuit. For example, the storage 26 may be realized by a plurality of storage circuits. The processor 29 is hardware for executing an instruction set written in a program, and is made up of an arithmetic unit, registers, peripheral circuits, etc.

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

[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 a signal generated by the control unit 180 and transmits the signal to the outside (for example, the server 20). The communication unit 121 performs reception processing on a signal received from the outside and outputs the signal 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 is realized by, for example, a mouse 131, a keyboard 132, and a touch-sensitive device 133 in which instructions are input by touching the operation surface. The input device 13 converts 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 operation devices such as the mouse 131 and the keyboard 132. The input device 13 may include, for example, a receiving port that receives electrical signals input from an external input device.

[0026] The output device 14 is a device for presenting information to a user who owns the terminal device 10. The output device 14 is realized, for example, by a display 141 or the like. 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 realized, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display or the like.

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

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

[0029] The operation receiving unit 181 performs processing for receiving user operations input from the input device 13. The transmitting / receiving unit 182 performs processing for the terminal device 10 to transmit and receive data to and from external devices such as the server 20 in accordance with a communication protocol. The display control unit 183 controls the output device 14 to present various information to the user.

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

[0031] The communication unit 201 performs processing for 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 a project database (DB) 281, a client database (DB) 282, a standard database (DB) 283, and a function specification 284.

[0033] The project DB 281 is a database for storing test design documents created in a specific project and elements decomposed from the test design documents. The project DB 281 also stores the test design documents currently being created in a specific project and the elements decomposed from the test design documents.

[0034] The project DB 281 is a database for sharing test design documents or elements created within a project. That is, it is possible for those involved in the project to share information about the test design documents or elements created in the project. The project DB 281 is provided, for example, for each planned project.

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

[0036] Fig. 4 is a schematic diagram showing an example of a list of check items included in a test design document. The example shown in Fig. 4 explains a test design document for inspecting the login function of a specific software. The check item list shown in Fig. 4 includes a first area 31 in which meta-information of the test design document is stored, and a second area 32 in which the contents to be checked in the test are stored.

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

[0038] The second area 32 plays the role of a so-called basic design document, which defines the general framework of the test, for example. In the second area 32, for example, "test target items / target functions," "test procedure," "test viewpoint," "expected values," etc. are defined. "Test target items / target functions" represent the items / functions that are the subject of the test. Figure 4 shows a case where the subject of the test is the login function, and the "test target items / target functions" are defined in the information stored in the item "test category," item "major function," item "medium function," and item "minor function."

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

[0040] The "test perspective" represents the viewpoint (way of thinking) that the test is based on. The "test perspective" is defined by the information stored in the "test perspective" item in FIG. 4. The second area 32 also includes the item "check items." The item "check items" represents information for specifying the test to be conducted. The information stored in the "test perspective" item and the information stored in the "check items" item are associated with each other.

[0041] The "expected value" represents the behavior that is expected to occur during confirmation. The "expected value" is defined by the information stored in the "expected value" item in FIG.

[0042] It should be noted that the information included in the second area 32 is not limited to these, and any of these pieces of information may be absent, or information other than these may be included.

[0043] FIG. 5 is a schematic diagram showing an example of a pattern table included in a test design document. The pattern table shown in FIG. 5 is included in the same test design document as the list of check items shown in FIG. 4. The pattern table shown in FIG. 5 includes a first area 31 in which meta information of the test design document is stored, and a third area 33 in which patterns are stored. The patterns specify the content to be checked, the conditions for the behavior that will be exhibited by the check process, and specific test cases that are combinations of the check content and conditions. The first area 31 is the same as the first area 31 shown in FIG. 4.

[0044] In the third area 33, for example, at least one pattern corresponding to the function to be tested is set. Two patterns for testing the login function, namely, a login pattern and a forgotten password pattern, are stored in the third area 33 shown in Fig. 5. A pattern number representing each pattern is stored in, for example, the item "No."

[0045] In the patterns stored in the third area 33, the "contents to be confirmed" are specified, for example, by the information stored in the "factor" and "level" items. The "conditions for the behavior manifested by the confirmation process" are specified, for example, by the conditions written in the "expected value" item. The "specific test cases" are specified in each column, starting with, for example, "1," "2," "3," etc. The processes actually performed in the test are represented by white circles in the columns.

[0046] The test design document is broken down into the above elements, such as information for specifying the necessary tests and information on which specific test cases are set. In other words, the test design document is broken down into "test perspectives," "check items," and "patterns."

[0047] The client DB 282 is a database for storing test design documents created in projects planned within a company and elements broken down from these test design documents. The client DB 282 is a database for sharing test design documents or elements across projects within the same company, for example. In other words, it allows test designers within the company to share information about test design documents or elements created in other projects within the company. A client DB 282 is provided, for example, for each company.

[0048] The standard DB 283 is a database for storing test designs created within multiple companies and elements decomposed from these test designs. The standard DB 283 is a database for sharing test designs or elements as overall shared knowledge across companies. In the standard DB 283, for example, identifiers representing attributes are assigned to the stored test designs and elements. Multiple types of attributes can be set, such as business type / industry, system type, and process type. By using identifiers representing attributes, it is possible to classify test designs or elements according to the attributes.

[0049] The functional specification 284 is data describing specifications for the functions of the test target. A test designer creates a test design document while referring to the functional specification 284. The functional specification 284 includes, for example, an area for storing detailed functional specifications and an area for storing message definitions. If the functional specification 284 is created using spreadsheet software, these areas are realized, for example, by different slides. Note that the functional specification 284 data itself does not need to be stored in the storage unit 202. For example, the functional specification 284 may be link information to a functional specification stored on the cloud. Alternatively, the functional specification 284 may be link information to a predetermined corresponding section of the functional specification stored on the cloud. For example, on the cloud, the functional specification describes the specifications of the function for each predetermined display unit. The predetermined display unit may be, for example, a page or a ticket. The functional specification may include, for example, update information. If a change occurs in the specifications, the information about the change is described in the update information.

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

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

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

[0053] More specifically, the storage control unit 2032 stores a test design document created by a user via the terminal device 10 and elements decomposed from the test design document in the project DB 281. Furthermore, when an instruction is received to share the test design document or elements stored in the project DB 281 within a company, the storage control unit 2032 also stores the test design document and elements stored in the project DB 281 in the client DB 282. Furthermore, when an instruction is received to share the test design document or elements stored in the project DB 281 or the client DB 282 across an entire company, the storage control unit 2032 also stores the test design document and elements stored in the project DB 281 or the client DB 282 in the standard DB 283.

[0054] The storage control unit 2032, for example, attaches tags to the test design document and elements decomposed from the test design document, and stores them in the project DB 281, the client DB 282, or the standard DB 283. The tags are, for example, information that individually represents the characteristics of the test. The tags can be set arbitrarily by, for example, 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 one of the project DB 281, the client DB 282, and the standard DB 283, whichever database the user specifies.

[0056] The acquiring unit 2033 may accept input of text information from a user. The acquiring unit 2033 compares the input text information with names, tags, etc. of test designs or elements stored in a database specified by the user. The acquiring unit 2033 acquires test designs or elements with names or tags that match the input text information. The acquiring unit 2033 may also acquire test designs or elements with names or tags that include the input text information. The acquiring unit 2033 may also acquire test designs or elements with names or tags that are estimated from the input text information.

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

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

[0059] <2 Data Structure> 6 to 8 are diagrams showing the data structure of the database stored in the server 20. In Fig. 6 to Fig. 8, an example is explained in which a test design document is broken down into "test viewpoints," "check items," and "patterns." Note that Fig. 6 to Fig. 8 are merely examples and do not exclude data that is not listed.

[0060] Fig. 6 is a diagram showing the data structure of the project DB 281. As shown in Fig. 6, the project DB 281 stores a test design document 2811, a pattern 2812, and a test viewpoint 2813. Each record of the test design document 2811 includes an item "file name," an item "designer," an item "reviewer," an item "status," an item "link," an item "latest update," etc.

[0061] The item "file name" stores the name of the test design document. The item "designer" stores the name of the person who created the test design document. The item "designer" stores the name of the person who created the test designer.

[0062] The item "reviewer" stores the name of the person who reviewed the test design document. The item "Status" stores the current status of the test design document. For example, the item "Status" may be "Working" indicating that work is underway, "Reviewing" indicating that work is being reviewed, or "Done" indicating that work is completed.

[0063] The "Link" item stores the functional specification associated with the test design document. The "Link" item may be associated with the functional specification itself, or with a corresponding section of the functional specification. For example, if the functional specification is a spreadsheet, the corresponding section of the functional specification may be stored as an expression such as a slide, row, or cell. The item "Latest Update" stores the latest date and time when the test design document was updated.

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

[0065] The item "file name" stores the name of the test design document from which the test was decomposed. The item "Latest Update" stores the date and time when the pattern was last updated.

[0066] Each record of the test viewpoint 2813 includes an item "test viewpoint", an item "check item", an item "category 1", an item "category 2", an item "latest update", and the like. The item "test viewpoint" stores information that is written in the item "test viewpoint" of the confirmation item list. The item "check item" stores information that is written in the item "check item" of the check item list.

[0067] The item "Classification 1" stores information about the first classification assigned to a test viewpoint. The information stored in the item "Classification 1" is set by the user when inputting a test viewpoint, for example, at the stage of creating a test design document. The information stored in the item "Classification 1" is set by the user by selecting from a plurality of items set in advance, for example.

[0068] The item "Classification 2" stores information about the second classification assigned to the test viewpoint. The information stored in the item "Classification 2" is set by the user when inputting the test viewpoint during the test design document creation stage. The information stored in the item "Classification 2" is set by the user by selecting from a plurality of pre-set items, for example. The item "Latest Update" stores the latest date and time when the test viewpoint was updated.

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

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

[0071] The test design document 2821 includes test design documents created in other projects within the same company in addition to the test design documents stored in the test design document 2811 shown in FIG.

[0072] Each record of pattern 2822 includes an item "pattern name," an item "pattern number," an item "tag," an item "file name," an item "project," an item "service," an item "latest update," etc. The items "pattern name," "pattern number," "file name," and "latest update" are the same as the respective items of pattern 2812 shown in FIG. 6.

[0073] The item "tag" stores information attached as a tag to the test design document from which the test was decomposed. The item "project" stores the name of the project in which the test design document to be divided was created. The item "service" stores the name of the service in which the test target is used.

[0074] The patterns 2822 include patterns decomposed from test design documents created in other projects within the same company, in addition to the patterns stored in the patterns 2812 shown in FIG.

[0075] Each record of the test viewpoint 2823 includes an item "test viewpoint", an item "check item", an item "tag", an item "category 1", an item "category 2", an item "latest update", etc. The items "test viewpoint", "check item", "category 1", "category 2", and "latest update" are the same items as the respective items of the test viewpoint 2813 shown in FIG. 6.

[0076] The item "tag" stores information attached as a tag to the test design document from which the test was decomposed. The test perspective 2823 includes test perspectives that are decomposed from test design documents created in other projects within the same company, in addition to the test perspectives stored in the test perspective 2813 shown in FIG.

[0077] Fig. 8 is a diagram showing the data structure of the standard DB 283. As shown in Fig. 8, the standard DB 283 stores a test design document 2831, a pattern 2832, and a test viewpoint 2833. Each record of the test design document 2831 includes an item "file name", an item "tag", an item "designer", an item "project", an item "service", an item "attribute", an item "link", an item "latest update", etc. The items "file name", "tag", "designer", "project", "service", "link", and "latest update" are the same as the items in the test design document 2821 shown in Fig. 7.

[0078] The "attribute" item stores information indicating the type to which the test design document belongs. Multiple types of attributes can be set in the "attribute" item, and for example, one or more attributes can be set from business type / industry, system type, process type, etc. Information related to the "attribute" item is set, for example, when a test design document stored in the project DB281 or client DB282 is stored in the standard DB283. Information related to the "attribute" item is set, for example, based on a tag attached to the test design document stored in the client DB282.

[0079] The test design document 2831 includes test design documents created in projects of other companies in addition to the test design documents stored in the test design document 2821 shown in FIG.

[0080] Each record of pattern 2832 includes an item "pattern name", an item "pattern number", an item "tag", an item "file name", an item "project", an item "service", an item "attribute", an item "latest update", etc. The item "pattern name", the item "pattern number", the item "tag", the item "file name", the item "project", the item "service", and the item "latest update" are the same items as the respective items of pattern 2822 shown in FIG. 7.

[0081] The item "attribute" stores information indicating the type to which the test design document from which the decomposition originates belongs. The patterns 2832 include patterns decomposed from test design documents created in projects of other companies, in addition to the patterns stored in the patterns 2822 shown in FIG.

[0082] Each record of the test viewpoint 2833 includes an item "test viewpoint", an item "check item", an item "tag", an item "category 1", an item "category 2", an item "attribute", an item "latest update", etc. The item "test viewpoint", the item "check item", the item "tag", the item "category 1", the item "category 2", and the item "latest update" are the same items as the respective items of the test viewpoint 2823 shown in FIG. 7.

[0083] The item "attribute" stores information indicating the type to which the test design document from which the decomposition originates belongs. The test perspective 2833 includes test perspectives that are decomposed from test design documents created in projects of other companies, in addition to the test perspectives stored in the test perspective 2823 shown in FIG.

[0084] <3 Summary> 9 is a diagram schematically illustrating the concept of the system 1 according to this embodiment. A project DB 281, a client DB 282, and a standard DB 283 are provided for each layer corresponding to a business. By storing a test design document 2811, patterns 2812, and test viewpoints 2813 created within a project in the project DB 281, it becomes possible for those involved in the project to share information about the test design documents, patterns, and test viewpoints created in the project.

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

[0086] Furthermore, by storing, for example, selected test design documents 2831, patterns 2832, and test viewpoints 2833 from among the test design documents, patterns, and test viewpoints created within multiple companies in the standard DB 283, it becomes possible to grasp the characteristics of each company's attributes, and to propose the optimal test design when formulating the test design.

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

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

[0089] The field objects 412 to 415 are objects for receiving database designations from the user. Specifically, the field objects 412 to 415 are objects for receiving designations of My Drive, the project DB 281, the client DB 282, and the standard DB 283, respectively.

[0090] The search box 416 is a box for accepting search keywords input from the user. The selection object 417 is an object that represents a user's selection of 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] 10, a field object 413 that specifies the project DB 281 is selected by a selection object 417. An acquisition unit 2033 acquires data from the selected database. A presentation unit 2034 presents the acquired 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 to 424, a search box 425, and a selection object 426.

[0093] Field objects 421 to 423 are objects for receiving a project designation from the user. Specifically, field objects 421 to 423 are objects for receiving designations of projects 1 to 3, respectively. Note that although FIG. 10 illustrates an example in which there are three projects, there is no limit to the number of projects. Furthermore, project names can be set arbitrarily.

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

[0095] The search box 425 is a box for receiving input of a project name from the user. The selection object 426 is an object that represents a user's selection of 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] 10, a field object 421 specifying project 1 is selected. The acquisition unit 2033 acquires 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 (started) among 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 receiving search keyword input from the user.

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

[0099] When the user confirms the selection of a project in the second area 42, the presentation unit 2034 presents a screen for displaying information about the project whose selection has been confirmed.

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

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

[0102] The field object 454 is an object for receiving an instruction to store information (test basis) related to the functional specification in the project DB 281. The information related to the functional specification is, for example, functional specification data in a file format or link information to the functional specification existing on the cloud. The selection object 455 is an object that represents a user's selection of 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] 11, a field object 451 that specifies a design file is selected by a selection object 455. An acquisition unit 2033 acquires data about the test design document from the project DB 281. A presentation unit 2034 presents the acquired data to the user.

[0104] The sixth area 46 is an area for displaying a list of the data (test design documents) selected in the fifth area 45. The test design documents are displayed in a list format in the sixth area 46. The test design documents displayed in the sixth area 46 are edited from an edit screen that is opened by pressing an edit icon 461 located at the left end of the list.

[0105] The test design document displayed in the sixth area 46 can be associated with a functional specification document managed in the project DB 281 by pressing a link icon 462 located at the right end of the list. Specifically, for example, when the user presses the link icon 462, a pop-up window 463 is displayed. The user presses “+ Link Test Base” in the pop-up window 463 and selects a functional specification document referenced when creating the test design document from among the functional specifications managed in the project DB 281. At this time, the user may also enter information about the relevant section of the functional specification document that was actually referenced. If the functional specification document is a spreadsheet file, the information about the relevant section includes, for example, information about the slide, row, cell, etc. Furthermore, if the functional specification document is data managed on the cloud, the information about the relevant section includes, for example, information about the page, ticket, etc. This associates the test design document with the functional specification. Furthermore, the test design document and the relevant section of the functional specification document are associated.

[0106] The test design document displayed in the sixth area 46 can be shared within the same company by pressing the share icon 4617 located at the right end of the list. That is, the test design document is stored in the client DB 282. For example, if a user determines that the test design document should be shared with other projects, the user presses the share icon 4617. When the user presses the share icon 4617, the storage control unit 2032 stores the test design document of the record for which the share icon 4617 was pressed in the client DB 282. Note that the test design document stored in the client DB 282 can be deleted from the client DB 282 by, for example, a person with predetermined authority, such as a project leader. By enabling even unauthorized persons to store test design documents in the client DB 282 in this way, the server 20 can promote the sharing of test design documents within the same company. On the other hand, by enabling authorized persons to delete test design documents stored in the client DB 282, it is possible to prevent unnecessary test design documents from increasing in the client DB 282. An application icon for applying for registration in standard knowledge may be placed at the end of the list displayed in the sixth area 46.

[0107] The storage control unit 2032 creates tag information including information about the project of the test design document when storing the test design document in the client DB 282. The storage control unit 2032 attaches the created tag information to the test design document and stores it in the client DB 282.

[0108] The sixth area 46 also includes a search box 464 for receiving search keywords input from the user. The sixth area 46 also includes field objects 465 to 467. The field objects 465 to 467 are objects for receiving instructions from the user.

[0109] Specifically, the field object 465 is an object for receiving an instruction to copy a test design document stored in My Drive. When the 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 the user selects one of the displayed test design documents, the terminal device 10 transmits the selected test design document to the server 20 and stores it in the project DB 281. The test design document newly stored in the project DB 281 is displayed in a new record in the list in the sixth area 46.

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

[0111] The field object 467 is an object for receiving an instruction to upload a test design document.

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

[0113] Fig. 12 is a schematic diagram showing an example of a screen for displaying test perspectives created in a specific project. The screen shown in Fig. 12 has a first area 41, a fifth area 45, and a sixth area 46. The first area 41 is similar to the first area 41 shown in Fig. 10.

[0114] In the fifth area 45, a field object 452 that specifies a test viewpoint is selected by a 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] The sixth area 46 is an area for displaying a list of the data (test viewpoints) selected in the fifth area 45. In the sixth area 46, the test viewpoints are displayed in a list format.

[0116] The test perspectives displayed in the sixth area 46 are not limited to test perspectives for test designs already created in the project and test designs being created in the project. The user may preselect and register a test perspective suitable for the project from the test perspectives stored in the client DB 282 or the standard DB 283. The selected test perspective is stored in the project DB 281.

[0117] Whether the test perspective is for a test design document created within a project or a pre-registered test perspective can be determined from the description of the item "Source" displayed in the sixth area 46. In other words, if the description of the item "Source" is "Project Perspective," it indicates that the test perspective is for a test design document created within a project. Also, if the description of the item "Source" is "Shared Perspective" or "Standard Perspective," it indicates that the test perspective is selected from the client DB 282 or standard DB 283.

[0118] The sixth area 46 also includes field objects 468 to 4610. The field objects 468 to 4610 are objects for receiving instructions from the user.

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

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

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

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

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

[0124] Although Fig. 12 does not explain how to associate a test perspective with a functional specification, similar to the test design document, a test perspective may be associated with a functional specification. Also, a test perspective may be associated with a corresponding section of the functional specification. Furthermore, similar to the test design document shown in Fig. 11, a share icon may be provided so that test perspectives can be shared within the same company.

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

[0126] Fig. 13 is a schematic diagram showing an example of a screen for displaying patterns created in a specific project. The screen shown in Fig. 13 has a first area 41, a fifth area 45, and a sixth area 46. The first area 41 is similar to the first area 41 shown in Fig. 10.

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

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

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

[0130] Whether a pattern is for a test design document created within a project or a pre-registered pattern can be determined from the description of the "Source" item displayed in the sixth area 46. That is, if the description of the "Source" item is "Project", it indicates that the pattern is for a test design document created within a project. Also, if the description of the "Source" item is "Shared" or "Standard", it indicates that the pattern was selected from the client DB 282 or the standard DB 283.

[0131] The sixth area 46 also includes field objects 4611 to 4613. The field objects 4611 to 4613 are objects for receiving instructions from the user.

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

[0133] The field object 4612 is an object for receiving an instruction to request the display of patterns stored in the standard DB 283. When the field object 4612 is pressed, the acquisition unit 2033 acquires the patterns stored in the standard DB 283. 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 the project DB 281. The pattern newly stored in the project DB 281 is displayed in a new record in the list in the sixth area 46.

[0134] The field object 4613 is an object for receiving an instruction to request the display of patterns stored in the client DB 282. When the field object 4613 is pressed, the acquisition unit 2033 acquires the patterns stored in the 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 the project DB 281. The pattern newly stored in the project DB 281 is displayed in a new record in the list in the sixth area 46.

[0135] Although Fig. 13 does not explain how to associate a pattern with a functional specification, a pattern may be associated with a functional specification, as in the case of a test design document. A pattern may also be associated with a corresponding section of the functional specification. Furthermore, as in the case of the test design document shown in Fig. 11, a share icon may be provided so that patterns can be shared within the same company.

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

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

[0138] In the first area 41, a selection object 417 selects a field object 414 that specifies a shared file. The seventh area 47 includes field objects 471 to 475 and a selection object 476 .

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

[0140] The field object 474 is an object for receiving an instruction to search for data based on a tag. The field object 475 is an object that represents the currently selected database and data type. In Fig. 14, the client DB 282 is selected and the display of the test design document is selected, so the field object 475 is written as "shared design document."

[0141] The selection object 476 is an object that represents a user's selection of 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] 14, a field object 471 that specifies a design document is selected by a selection object 476. The acquisition unit 2033 acquires data about the test design document from the client DB 282. The presentation unit 2034 presents the acquired data to the user.

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

[0144] The test design document displayed in the eighth area 48 is shared as standard knowledge by pressing the request icon 482 located at the right end of the list. In other words, the test design document is stored in the standard DB 283. For example, the user determines whether the test design document should be shared as standard knowledge, taking into consideration the generality, importance, etc. of the test design document. If it should be shared as standard knowledge, the user presses the request icon 482. When the user presses the request icon 482, the storage control unit 2032 stores the test design document of the record for which the request icon 482 was pressed in the standard DB 283. The test design document of the record for which the request icon 482 was pressed enters a request state and may be stored in the standard DB 283 with permission from a person with predetermined authority. Note that special authority may be required to store the test design document accumulated in the shared knowledge (client DB 282) in the standard DB 283. For example, a system administrator has the authority to apply, and based on the administrator's judgment, test design documents accumulated in the shared knowledge are stored in the standard DB 283. By providing such authority, only truly necessary test design documents are stored in the standard DB 283. Storing a test design document in the standard DB 283 means that the test design document can be widely and generally used. For this reason, the number of test design documents stored in the standard DB 283 can be used as a basis for evaluating a test designer.

[0145] The storage control unit 2032 sets attributes of the test design document based on the tags attached to the test design document when storing the test design document in the standard DB 283. The storage control unit 2032 stores the test design document together with the set attributes in the standard DB 283.

[0146] The eighth area 48 also includes a search box 481 for receiving search keywords input from the user.

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

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

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

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

[0151] An instruction to store any of the patterns displayed in the list in the standard DB 283 may be received from the user. When an instruction to store in the standard DB 283 is input from the user, the storage control unit 2032 stores the pattern selected by the user in the standard DB 283.

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

[0153] Fig. 16 is a schematic diagram showing an example of a screen for displaying test viewpoints shared within a company. The screen shown in Fig. 16 has a first area 41, a seventh area 47, and an eighth area 48. The first area 41 is similar to the first area 41 shown in Fig. 14.

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

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

[0156] An instruction to store any of the listed test perspectives in the standard DB 283 may be received from the user. When the instruction to store in the standard DB 283 is input from the user, the storage control unit 2032 stores in the standard DB 283 the test perspective selected by the user.

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

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

[0159] In the first area 41, a selection object 417 selects a field object 415 that specifies knowledge.

[0160] In the seventh area 47, the standard DB 283 is selected, and therefore the field object 475 is written as "TD (registered trademark)." Also, a selection object 476 selects a field object 471 that specifies a design document. The acquisition unit 2033 acquires data about the test design document from the standard DB 283. The presentation unit 2034 presents the acquired data to the user.

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

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

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

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

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

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

[0167] Fig. 19 is a schematic diagram showing an example of a screen for reading out test viewpoints stored in standard knowledge. The screen shown in Fig. 19 has a first area 41, a seventh area 47, and an eighth area 48. The first area 41 is similar to the first area 41 shown in Fig. 17.

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

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

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

[0171] First, a case where a test design document is created by copying a test design document stored in the client DB 282 or the standard DB 283 will be described. For example, assume that a user wants to reuse a test design document used in Project 1 from the accumulated test design documents. The user presses the field object 466 for “Copy from shared file / knowledge” on the screen shown in FIG.

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

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

[0174] The field object 4616 is an object for receiving an instruction to create a test design document by reusing a test design document selected by the user. The field object 4617 is an object for receiving an instruction to cancel reusing a test design document.

[0175] The database from which the test design document displayed in the display window 4614 has been read can be determined from the description of the "Source" item. In the example of Fig. 20, a test design document whose "Source" item is described as "Shared Knowledge" is a test design document read from the client DB 282. Also, a test design document whose "Source" item is described as "Standard Knowledge" is a test design document read from the standard DB 283.

[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 confirmation items or a pattern table, on the display 141.

[0177] The user checks the confirmation item list and the pattern table and determines whether the test design document can be reused in project 1. If the user determines that the test design document can be reused, the user selects the test design document that the user determines can be reused and presses the field object 4616 displayed in the display window 4614.

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

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

[0180] Next, a case where a test design document is created while reusing test viewpoints or patterns stored in the project DB 281, the client DB 282, or the standard DB 283 will be described.

[0181] For example, assume that the user is creating a test design document to be used in Project 1. The user presses the "Create New" field object 411 on the screen shown in FIG.

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

[0183] Fig. 21 is a schematic diagram showing an example of a screen for creating a list of check items. The creation screen shown in Fig. 21 includes a field object 491. The field object 491 is an object for receiving input from the user for the list of check items. When the creation screen is displayed, the user selects the first cell 4911 of the item "Test Perspective" to input, for example, a test perspective.

[0184] When cell 4911 is selected, the display control unit 183 displays a message on the display 141 to confirm whether or not to display a list of test perspectives. When the user requests display of a list of test perspectives, the acquisition unit 2033 acquires the test perspectives from the project DB 281. The presentation unit 2034 presents the acquired test perspectives to the user.

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

[0186] 22 is a schematic diagram showing an example of a list display of test viewpoints. A display window 492 includes selection icons 4921 and 4922.

[0187] The selection icons 4921 and 4922 are icons for accepting the selection of a database from which a test perspective is to be read. Specifically, the selection icon 4921 is an icon for accepting the selection of the project DB 281. Checking the box of the selection icon selects reading from the project DB 281. The selection icon 4922 is an icon for accepting the selection of the standard DB 283. Checking the box of the selection icon selects reading from the standard DB 283. Note that the display window 492 may include an icon for accepting the selection of reading a test perspective from the client DB 282.

[0188] 22, the selection icon 4921 is checked, and the test perspective read from the project DB 281 is displayed. The "project perspective" is entered in the "source" item of the test perspective read from the project DB 281. When the user checks the selection icon 4922, the test perspective read from the standard DB 283 is displayed (not shown). The "source" item of the test perspective read from the standard DB 283 is entered, for example, as the "standard perspective."

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

[0190] Fig. 23 is a schematic diagram showing an example of a creation screen for a list of confirmation items on which a "test viewpoint" and a "confirmation item" are entered. In Fig. 23, "successful authentication" is entered in the first cell 4911 of the item "test viewpoint," and a "confirmation item" is entered in the first cell 4912 of the item "confirmation item."

[0191] 23 includes a field object 493 for accepting a transition to a pattern management screen. When the user presses the field object 493, the display control unit 183 causes the display 141 to display the pattern management screen.

[0192] 24 is a schematic diagram showing an example of a pattern management screen. The management screen shown in FIG.

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

[0194] A field object 4102 is an object for accepting selection of a managed pattern. If multiple patterns are registered in the confirmation item list, multiple field objects 4102 are displayed. A field object 4103 is an object for accepting pattern input from the user.

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

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

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

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

[0199] 25 is a schematic diagram showing an example of a list display of patterns. A display window 4106 includes 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 an icon for receiving a display request for a pattern.

[0200] The field object 4108 is an object for receiving an instruction to create a pattern by reusing a pattern selected by the user. The field object 4109 is an object for receiving an instruction to cancel the reusing of a pattern.

[0201] The database from which the pattern displayed in the display window 4106 has been read can be determined from the description of the item "Source." In the example of Fig. 25, a pattern in which the description of the item "Source" is "Project" is a pattern read from the project DB 281. A pattern in which the description of the item "Source" is "Client" is a test design document read from the client DB 282. A pattern in which the description of the item "Source" is "Master" is a test design document read from the standard DB 283.

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

[0203] The user checks the pattern table and determines whether the pattern can be reused. If the user determines that the pattern can be reused, the user selects the pattern that the user has determined to be usable and presses the field object 4108 displayed in the display window 4106.

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

[0205] 25 shows a case where the presentation unit 2034 displays patterns read from the client DB 282 and the standard DB 283 in a predetermined order. However, the presentation unit 2034 may present patterns that are expected to be desired by the user in a position that is easy to see. For example, the presentation unit 2034 presents patterns to the user so that patterns tagged with tags that are the same as or similar to stored project-related information are ranked higher.

[0206] (Proposal of modifications in response to modifications to the functional specifications) The processing of the server 20 when proposing a test design document or an element modification in response to a modification of the functional specification document will be described below with reference to the display screen of the display 141.

[0207] FIG. 27 is a flowchart showing the flow of processing performed by the control unit 203 when proposing a test design document or an element modification in response to a modification of the functional specification document.

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

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

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

[0211] When the test design document and the corresponding part of the functional specification 284 are associated with each other, the acquisition unit 2033 may acquire the test design document or the element of the test design document associated with the changed part of the functional specification 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 the acquired test design document or elements of the test design document may need to be modified in accordance with a change in the functional specification 284. The display control unit 183 causes the display 141 to display the presented content.

[0213] 28 is a schematic diagram showing an example of a screen displaying a test design document or a proposed modification of elements of the test design document based on a change to the functional specification 284. The display control unit 183 displays a display window 4614 on the display 141, for example, on a screen displaying a list of test design documents. The display window 4614 displays information that the test design document, test perspectives, and patterns may need to be modified due to changes to the relevant parts of the functional specification. Note that 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 check item list and pattern table of the test design document may be proposed.

[0214] When the suggested corrections are displayed in the display window 4614, the user checks the corresponding corrections in the functional specification 284 and considers whether the test design document or the elements of the test design document need to be corrected. If corrections are necessary, the user corrects the test design document or the elements of the test design document.

[0215] When a test design document or an element of the test design document is modified by the user, the storage control unit 2032 updates the test design document or the element of the test design document stored in the project DB 281 with the modified data. After updating the data in the project DB 281, the storage control unit 2032 determines whether the test design document or the element of the test design document before modification is also stored in the client DB 282 or the standard DB 283. If the test design document or the element of the test design document before modification is also stored in the client DB 282 or the standard DB 283, the storage control unit 2032 updates the data stored in the client DB 282 or the standard DB 283 with the modified data.

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

[0217] First, the storage control unit 2032 stores in the storage unit 202 the first number of times that a test design document or an element of a test design document stored in the project DB 281, the client DB 282, or the standard DB 283 has been reused. In addition, the storage control unit 2032 stores in the storage unit 202 the second number of times that a test designer has reused a test design document or an element 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 an index value that indicates, for example, 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, the client DB 282, and the standard DB 283. For example, the index value includes a reduction value or a reduction rate that indicates how much the time taken to create one test design document has been reduced by reusing the test design document, etc. The index value also includes a reduction value or a reduction rate that indicates how much the time taken by a test designer to create one test design document has been reduced by reusing the test design document, etc.

[0219] The presenting unit 2034 presents the index value calculated by the calculating unit 2036 to the terminal device 10.

[0220] As described above, in the above embodiment, the storage 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. Then, in response to a request from the user, the presentation unit 2034 switches and presents the test design document or the elements stored in the project DB 281, client DB 282, and standard DB 283. In this way, the server 20 accumulates the test design document and the elements decomposed from the test design document in the desired database, making it easier for the user to reach the desired information.

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

[0222] In the above embodiment, the storage control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281, which shares information within the project. This enables the server 20 to accumulate past data created within the project so that it can be used within the project.

[0223] In the above embodiment, the storage 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 enables the server 20 to accumulate past data created within a project so that it can be used within the company.

[0224] In the above embodiment, the storage control unit 2032 stores either the test design document stored in the project DB 281 or the client DB 282, or the elements decomposed from the test design document, in the standard DB 283, which shares information with the entire system. This enables the server 20 to accumulate past data created within a project or company as usable standard data.

[0225] Furthermore, in the above embodiment, the storage control unit 2032 stores the test design document or the elements decomposed from the test design document in the standard DB 283 by adding information indicating the type to which the test design document belongs. This allows the server 20 to classify the data stored in the standard DB 283 according to the type of company. This allows the user to efficiently access desired data even when a large amount of data is stored in the standard DB 283.

[0226] In the above embodiment, the storage control unit 2032 stores data in a higher-level database in response to an instruction from an authorized user, thereby preventing the amount of data stored in the client DB 282 or the standard DB 283 from becoming too large.

[0227] In the above embodiment, the presentation unit 2034 presents the test design documents or elements stored in the project DB 281 to users who belong to the project corresponding to the project DB 281. This allows the server 20 to promote information sharing within the project and reduce variations in quality among test designers within the project. In other words, personalization is eliminated, stabilizing quality.

[0228] In the above embodiment, the presentation unit 2034 presents the test design documents or elements stored in the client DB 282 or the standard DB 283 to the user. This allows the user to search for desired information from the database for each layer, enabling the user to quickly access the desired information. Furthermore, because the client company can understand the desired quality of tests in advance, the probability of designing unnecessary tests is reduced, making it possible to avoid time loss. This makes it possible to design optimally cost-optimized and optimally quality tests for the client company throughout the entire project.

[0229] In the above embodiment, the storage control unit 2032 stores the created test design document and the elements decomposed from the test design document in the project DB 281 in association with the functional specification referenced during creation. When a change is made to the functional specification, the presentation unit 2034 presents a proposal to modify the test design document or elements associated with the functional specification. This allows the user to modify the test design document in real time in conjunction with development. This reduces discrepancies between the target being actually developed and the test being designed. This helps prevent missing tests throughout the entire project.

[0230] In the above embodiment, the storage control unit 2032 associates the created test design document and the elements decomposed from the test design document with the corresponding part of the functional specification referenced during the creation of the test design document, and stores them in the project DB 281. If a change is made to the corresponding part, the presentation unit 2034 presents a proposal to modify the test design document or the element associated with the corresponding part. This allows the user to more efficiently modify the test design document or the element in accordance with the change to the functional specification.

[0231] In the above embodiment, when a test design document or an element associated with a functional specification is modified, the storage control unit 2032 reflects the modification in a test design document or an element corresponding to the modified test design document or element, which is stored in a database of a higher layer. This enables the server 20 to reflect the modification of 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] In the above embodiment, the storage control unit 2032 stores the test design document and the elements decomposed from the test design document in the project DB 281, the client DB 282, and the standard DB 283, with tags that individually represent the characteristics of the test. The presentation unit 2034 then searches the database specified by the user for the test design document or element stored in each database based on the tag. This allows the user to reach the desired data more quickly.

[0233] In the above embodiment, the elements are test perspectives, which represent the perspectives on which testing is based, and pattern tables, which specify the test cases to be performed. This allows the server 20 to manage data by item, where the content entered is likely to vary depending on the user's skill. Therefore, when a user creates a test design document, it is possible to support the user in entering information, thereby reducing the burden of creating the test design document. Furthermore, this reduces the variation in the quality of the created test design documents.

[0234] Furthermore, in the above embodiment, the storage control unit 2032 stores the test perspectives stored in the client DB 282 or the standard DB 283 in the project DB 281 before the test design document is created. This allows the server 20 to register test perspectives required for the project in advance, thereby reducing the burden on the test designer to set test perspectives. It also makes it possible to prevent necessary test perspectives from being omitted.

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

[0236] In the above embodiment, an example has been described in which databases are provided in three hierarchical levels: a project DB 281, a client DB 282, and a standard DB 283. However, the number of hierarchical levels in which databases according to this embodiment are provided is not limited to three hierarchical levels. For example, a hierarchical level may be provided above the client DB 282, which compiles information stored in the client hierarchical level by a predetermined element. The predetermined element may be, for example, a geographical element, an element related to an industry, or the like. Specifically, for example, a database that compiles information about companies in eastern Japan and a database that compiles information about companies in western Japan may be provided.

[0237] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0238] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0239] (Appendix 1) A program to be executed by a computer including a processor 29 and a memory 25, the program causing the processor to: a step (2032) of storing the test design document and the elements decomposed from the test design document in databases 281, 282, and 283 provided for each layer corresponding to the business; a step (2034) of switching and presenting test design documents or elements stored in each database in response to a request from a user; A program that executes the following.

[0240] (Appendix 2) The program according to claim 1, wherein the storing step stores the created test design document and the elements decomposed from the test design document in a first database 281 that shares information within the project.

[0241] (Appendix 3) A program described in Appendix 2, in which, in the storing step, the test design document stored in the first database and any of the elements decomposed from the test design document are stored in a second database 282 that shares information across projects.

[0242] (Appendix 4) A program described in Appendix 3, in which, in the storing step, the test design document stored in the first database or the second database, and any of the elements decomposed from the test design document, are stored in a third database 283 that shares information with the entire system.

[0243] (Appendix 5) The program according to claim 4, wherein in the storing step, information indicating the type to which the test design document belongs is attached to the test design document or an element decomposed from the test design document, and the information is stored in the third database.

[0244] (Appendix 6) A program described in (Appendix 4) or (Appendix 5), wherein in the storing step, operation by an authorized person is required to store the test design document and the elements decomposed from the test design document in the third database.

[0245] (Appendix 7) The program according to any one of (Supplementary Note 2) to (Supplementary Note 6), wherein in the presenting step, the test design document or the element stored in the first database is presented to a user who belongs to a project corresponding to the first database.

[0246] (Appendix 8) The program according to any one of (Supplementary Note 3) to (Supplementary Note 7), wherein in the presenting step, the test design document or the element stored in the second database is presented to a user belonging to another project within the same client.

[0247] (Appendix 9) The program according to any one of (Supplementary Note 4) to (Supplementary Note 8), wherein in the presenting step, the test design document or the element stored in the third database is presented to the user.

[0248] (Appendix 10) In the storing step, the created test design document and the elements decomposed from the test design document are stored in a first database in association with the functional specification referred to when the test design document was created; A program described in any one of (Appendix 2) to (Appendix 9) that causes a processor to execute a step of proposing modifications to a test design document or element associated with a functional specification when a change is made to the functional specification.

[0249] (Appendix 11) In the storing 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 parts of the functional specification document referred to when the test design document was created; A program according to claim 10, which, in the proposing step, proposes modification of a test design document or element associated with the relevant part if there is a change in the relevant part.

[0250] (Appendix 12) A program as described in (Appendix 10) or (Appendix 11), which causes a processor to execute a step of reflecting the modifications in a test design document or element corresponding to the modified test design document or element stored in a database at a higher layer when the test design document or element associated with the functional specification is modified.

[0251] (Appendix 13) In the storing step, the test design document and the elements decomposed from the test design document are stored in a second database with tags individually representing the characteristics of the test; The program according to any one of (Supplementary Note 3) to (Supplementary Note 12), wherein in the presenting step, a test design document or an element is searched for based on the tag.

[0252] (Appendix 14) A program described in Appendix 13, in which, in the storing step, attribute information indicating the type to which the test design document belongs is created based on tag information, and the test design document or elements decomposed from the test design document are stored in a third database with the attribute information attached.

[0253] (Appendix 15) A program described in any one of (Appendix 1) to (Appendix 14), wherein the elements are a test viewpoint that represents the viewpoint on which the test is based, and a pattern table that specifies the test cases to be executed.

[0254] (Appendix 16) The elements are test viewpoints that represent the viewpoints on which the test is based, and pattern tables that specify test cases to be executed. A program described in any one of (Appendix 4) to (Appendix 6), wherein in the storing 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.

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

[0256] (Appendix 18) A program to be executed by a computer having a processor and a memory, the program causing the processor to: a step of storing the created test design document in a database in association with the functional specification document referred to when the test design document was created; When there is a change in the functional specification, a step of proposing a modification of the test design document associated with the functional specification; A program that causes a processor to execute the following.

[0257] (Appendix 19) In the storing step, the created test design document is stored in a database in association with a corresponding portion of the functional specification document referred to when the test design document was created; A program according to claim 18, which, in the proposing step, proposes a modification to the test design document associated with the relevant part if there is a change in the relevant part.

[0258] (Appendix 20) 1. A computer-implemented method comprising a processor and a memory, the method comprising: 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; a step of switching and presenting test design documents or elements stored in each database in response to a request from a user; How to do it.

[0259] (Appendix 21) An information processing device including a processor and a memory, The processor: 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; a step of switching and presenting test design documents or elements stored in each database in response to a request from a user; An information processing device that executes the above.

[0260] (Appendix 22) a means for storing a test design document and elements decomposed from the test design document in a database provided for each layer corresponding to a business; A means for switching and presenting test design documents or elements stored in each database in response to a user request. A system comprising: [Explanation of symbols]

[0261] 1. System 10...Terminal device 121…Communications Department 13...Input device 131...Mouse 132...Keyboard 133...Touch-sensitive devices 14...Output device 141...Display 15...Memory 16…Storage 170...Storage section 180...Control unit 181...Operation reception section 182...Transmitter / receiver 183...Display control unit 19...Processor 20...Server 201…Communications Department 202...Storage section 203...Control unit 2031...Transmitter / receiver 2032...Memory control unit 2033…Acquisition Department 2034…Presentation part 2035…Detection unit 2036…Calculation section 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 perspective 284...Functional Specifications 29...Processor

Claims

1. A program to be executed by a computer including a processor and a memory, the program causing the processor to: a step of storing a test design document in which tests for testing functions of a test target are designed, and at least one of a first element that specifies a test and a second element in which a specific test case is set, which are extracted from the test design document, in a database provided for each layer where information sharing is required; a step of managing that the elements stored in the database have been reused in creating a test design document; A program that executes the following.

2. A program as described in claim 1, which causes the processor to execute a step of understanding a test design document created by reusing specified elements based on the managed information.

3. 1. A computer-implemented method comprising a processor and a memory, the method comprising: a step of storing a test design document in which tests for testing functions of a test target are designed, and at least one of a first element that specifies a test and a second element in which a specific test case is set, which are extracted from the test design document, in a database provided for each layer where information sharing is required; a step of managing that the elements stored in the database have been reused in creating a test design document; How to do it.

4. An information processing device including a processor and a memory, the processor: a step of storing a test design document in which tests for testing functions of a test target are designed, and at least one of a first element that specifies a test and a second element in which a specific test case is set, which are extracted from the test design document, in a database provided for each layer where information sharing is required; a step of managing that the elements stored in the database have been reused in creating a test design document; An information processing device that executes the above.

5. A means for storing a test design document in which tests are designed to test the functions of the test subject, and at least one of elements included in said test design document, which are extracted from said test design document and are a first element that specifies the test and a second element in which a specific test case is set, in a database provided for each layer where information sharing is required; a means for managing that the elements stored in the database have been reused in the creation of a test design document; A system comprising:

Images