Design system, search device, design method, search method, and program

Abstract

We provide a design system that allows users to track system requirements against the completed system configuration. [Solution] The design system includes a configuration design means that receives system requirements as input and designs a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that make up the system; a differential configuration extraction means that extracts system components that have been added or changed in one stage of concretization during the design process; an analysis means that determines whether or not the system components that have been added or changed in one stage of concretization are related to the system requirements; and a requirements tracking configuration generation means that generates requirements tracking configuration information showing the relationship between the system requirements and the system configuration using the determination result.

Description

Technical Field

[0001] The present invention relates to a design system, a search device, a design method, a search method, and a program.

Background Art

[0002] In some cases, an apparatus or a system performs system design. For example, the system design apparatus described in Patent Document 1 repeatedly applies an embodiment rule to a system configuration including abstract components. Then, the embodied system configuration is output.

Prior Art Literature

Patent Literature

[0003]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0004] When an apparatus or a system performs system design, it is preferable that a user can track system requirements with respect to a completed system configuration.

[0005] An example of an object of the present invention is to provide a design system, a search device, a design method, a search method, and a program that can solve the above-described problem.

Means for Solving the Problem

[0006] According to a first aspect of the present invention, the design system includes: a configuration design means that receives system requirements as input and designs a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that constitute the system; a differential configuration extraction means that extracts system components that have been added or changed in one stage of concretization during the design process; an analysis means that determines whether or not the system components that have been added or changed in one stage of concretization are related to the system requirements; and a requirements tracking configuration generation means that generates requirements tracking configuration information showing the relationship between the system requirements and the system configuration using the determination result.

[0007] According to a second aspect of the present invention, the search device includes a requirement tracking information search means that receives input information identifying a system configuration and specific system requirement items, and searches for requirement tracking configuration information for the system requirement items with respect to the system configuration, and a requirement tracking information synthesis means that, when multiple pieces of requirement tracking configuration information are received for a single system requirement item, combines these multiple pieces of requirement tracking configuration information into a single piece of requirement tracking configuration information.

[0008] According to a third aspect of the present invention, the design method includes the steps of: a computer receiving system requirements as input and designing a specific system configuration that satisfies the input system requirements by repeatedly concretizing system components that constitute the system; extracting system components that have been added or modified in one stage of concretization during the design process; determining whether the components that have been added or modified in one stage of concretization are related to the system requirements; and generating requirements tracking configuration information that shows the relationship between the system requirements and the system configuration using the determination result.

[0009] According to a fourth aspect of the present invention, the search method includes the steps of: a computer receiving input of information identifying a system configuration and a specific system requirement item, and searching for requirement tracking configuration information for the system requirement item for the system configuration; and, if multiple requirement tracking configuration pieces are detected for a single system requirement item, consolidating those multiple requirement tracking configuration pieces into a single requirement tracking configuration piece.

[0010] According to a fifth aspect of the present invention, the program causes the computer to perform the following processes: receiving system requirements as input and designing a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that constitute the system; extracting system components that have been added or modified in one stage of concretization during the design process; determining whether the system components that have been added or modified in one stage of concretization are related to the system requirements; and using the determination result, generating requirements tracking configuration information that shows the relationship between the system requirements and the system configuration.

[0011] According to a sixth aspect of the present invention, the program causes a computer to receive input of information identifying a system configuration and specific system requirement items, to perform a process of searching for requirement tracking configuration information for the system requirement items for the system configuration, and, if multiple requirement tracking configuration information entries are found for a single system requirement item, to consolidate those multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. [Effects of the Invention]

[0012] According to the present invention, users can track system requirements for the completed system configuration. [Brief explanation of the drawing]

[0013] [Figure 1] This is a block diagram showing an example configuration of a design system according to at least one embodiment. [Figure 2]FIG. 1 is a diagram showing an example of a system configuration according to at least one embodiment. [Figure 3] FIG. 1 is a diagram showing an example of an implementation pattern according to at least one embodiment. [Figure 4] FIG. 1 is a diagram showing an example of an implementation pattern according to at least one embodiment. [Figure 5] FIG. 1 is a diagram showing an example of a system configuration according to at least one embodiment. [Figure 6] FIG. 1 is a diagram showing an example of updating requirement tracing configuration information according to at least one embodiment. [Figure 7] FIG. 1 is a flowchart showing an operation example of a design system according to at least one embodiment. [Figure 8] FIG. 1 is a diagram showing an example of difference configuration information according to at least one embodiment. [Figure 9] FIG. 1 is a diagram showing an example of difference configuration information according to at least one embodiment. [Figure 10] FIG. 1 is a block diagram showing a configuration example of a design system according to at least one embodiment. [Figure 11] FIG. 1 is a diagram showing an example of a requirement tracing configuration display screen displayed by an output device according to at least one embodiment. [Figure 12] FIG. 1 is a flowchart showing an operation example of a search device according to at least one embodiment. [Figure 13] FIG. 1 is a block diagram showing a configuration example of a design system according to at least one embodiment. [Figure 14] FIG. 1 is a diagram showing another example of a requirement tracing configuration display screen displayed by an output device according to at least one embodiment. [Figure 15] FIG. 1 is a flowchart showing an operation example of a design system according to at least one embodiment. [Figure 16] FIG. 1 is a diagram showing a configuration example of a design system according to at least one embodiment. [Figure 17] FIG. 1 is a diagram showing a configuration example of a search device according to at least one embodiment. [Figure 18]It is a diagram illustrating an example of a processing procedure in a design method according to at least one embodiment. [Figure 19] It is a diagram illustrating an example of a processing procedure in a search method according to at least one embodiment. [Figure 20] It is a diagram illustrating the hardware configuration of a computer functioning as a design apparatus and a search apparatus according to at least one embodiment. DETAILED DESCRIPTION OF EMBODIMENTS

[0014] Hereinafter, embodiments of the present invention will be exemplified. However, the present invention is not limited to the embodiments exemplified below, and various modifications can be made within the scope defined in the claims. For example, embodiments obtained by appropriately combining techniques (part or all of an article or a method) employed in the embodiments exemplified below are also included within the scope of the present invention. In addition, embodiments obtained by appropriately omitting part of the techniques employed in the embodiments exemplified below are also included within the scope of the present invention. Furthermore, the effects mentioned in the embodiments exemplified below are examples of effects expected in the respective embodiments, and do not define the scope of the present invention. That is, embodiments that do not achieve the effects mentioned in the embodiments exemplified below are also included within the scope of the present invention.

[0015] [FIRST EMBODIMENT] A first embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. The present embodiment is a basic form that serves as a foundation for each of the embodiments described later. Note that the application scope of each technique employed in the present embodiment is not limited to the present embodiment. That is, each technique employed in the present embodiment can also be employed in other embodiments included in the present disclosure, as long as no particular technical impediment arises. In addition, each technique shown in the drawings referred to for describing the present embodiment can also be employed in other embodiments included in the present disclosure, as long as no particular technical impediment arises.

[0016] (Description of Configuration) Figure 1 is a block diagram showing an example of the configuration of a design system according to at least one embodiment.

[0017] As shown in Figure 1, the design system 1 comprises a design device 11, a storage device 12, an input device 13, and an output device 14. The design device 11 and the storage device 12 are connected in a communicative manner. For example, the configuration design unit 111, the differential configuration extraction unit 112, the analysis unit 113, and the requirements tracking configuration generation unit 114 may each have access to the storage device 12. The design device 11 and the input device 13 are also connected in a communicative manner. The design device 11 and the output device 14 are also connected in a communicative manner. The design device 11 comprises a configuration design unit 111, a differential configuration extraction unit 112, an analysis unit 113, and a requirements tracking configuration generation unit 114.

[0018] The design device 11 performs system design. The design device 11 or a part thereof may be configured using a computer such as a workstation (WS) or personal computer (PC). Alternatively, the design device 11 or a part thereof may be configured using an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

[0019] The storage device 12 stores various data for processing by the design device 11. The input device 13 acquires input data. In particular, the input device 13 acquires information indicating the system requirements (system requirements) that the design device 11 should design. The input device 13 may be equipped with input devices such as a keyboard and mouse to accept user input for data. Alternatively, the input device 13 may communicate with an external device of the design system 1 to receive input data. The input device 13 outputs the acquired input data to the design device 11. The output device 14 outputs data. The method by which the output device 14 outputs data is not limited to a specific method. For example, the output device 14 may be configured using a display device to display various images according to the control of the design device 11.

[0020] The design device 11, the storage device 12, the input device 13, and the output device 14, or a part of these, may be configured as a single device. For example, the design device 11, the storage device 12, the input device 13, and the output device 14 may be incorporated into an all-in-one computer system such as a laptop computer. Furthermore, the input device 13 or the output device 14, or both, may be external components of the design system 1.

[0021] The configuration design unit 111 receives system requirements from the input device 13 and automatically designs a specific system configuration that satisfies the input system requirements. The configuration design unit 111 designs a system that includes the components that make up the system. The configuration design unit 111 is an example of a configuration design means.

[0022] System requirements are the requirements that the designed system must satisfy. Here, system requirements include an abstract system configuration. In addition to the abstract system configuration, system requirements may also include one or more constraints that the designed system must satisfy.

[0023] Components that are associated with a specific device or system and do not need to be further specified are also called specified components or concrete components. Components other than specified components, that is, components that need to be further specified in system design, are also called abstract components.

[0024] The configuration design unit 111 assumes that it is known whether a given component is an abstract component or a concrete component. For example, the concrete pattern used by the configuration design unit 111 in system design may include information that distinguishes between abstract components and concrete components. Alternatively, the storage device 12 may store information indicating whether each component is an abstract component or a concrete component.

[0025] When all components included in a system configuration are concrete components, that system configuration is also called a concrete system configuration. A system configuration that includes abstract components is also called an abstract system configuration.

[0026] Figure 2 shows an example of a system configuration. The system configuration shown in Figure 2 includes multiple components indicated by circles, and these components have relationships indicated by arrows. Note that Figure 2 is intended to illustrate the system configuration, and therefore, explanations of each component and its relationships are omitted.

[0027] The configuration design unit 111 designs the system by adding or replacing components according to a concretization pattern. A concretization pattern defines components that can be added to or replaced by a specific component. The concretization pattern may also include relationships between components.

[0028] Figure 3 shows an example of a concretization pattern. For example, the concretization pattern shown in Figure 3 represents a pattern in which the components of "OS" (Operating System) are replaced with components of "Win" or "Linux" (Linux is a registered trademark).

[0029] Figure 4 shows another example of the concretization pattern. The concretization pattern shown in Figure 4 involves adding the "Machine" component to the "OS" component and adding the relationship "Hosted_on". The specific pattern may be stored in the memory device 12.

[0030] The configuration design unit 111 performs the above-described system design in stages. That is, it repeats the process of materializing specific components that have not yet been materialized among the components included in the initial or intermediate stage of the system configuration, until the materialization of all components is completed. In this context, the materialization of a component is completed when that component has become a concrete component.

[0031] The configuration design unit 111 stores the system configuration in the storage device 12 at each stage of system design. For example, the storage device 12 may store the input system requirements. Furthermore, the configuration design unit 111 may store the obtained system configuration in the storage device 12 each time it performs a stage of system design, that is, each time it applies a concretization pattern to the components included in the system configuration.

[0032] The configuration design unit 111 determines whether the system configuration to which the concretized pattern is applied satisfies the constraints imposed on the system configuration. The number of constraints imposed on the system configuration is not limited to a specific number. If there is one or more constraints that are not satisfied, the configuration design unit 111 rejects the system configuration to which the concretized pattern is applied and applies another concretized pattern. The constraints are conditions that the system configuration must satisfy and may be stored in the storage device 12.

[0033] Figure 5 shows an example of a system configuration. The system configuration shown in Figure 5 includes components such as "WebSystem", "AppServer", "Database", "Web App", "OS", "ExpressR120" (physical server ExpressR120), "DBS" (database system), and "Data". Furthermore, these components have relationships such as "Include", "Conn_to", and "Hosted_on". The configuration design unit 111 stores configuration information indicating the system configuration in the storage device 12 and also outputs it to the differential configuration extraction unit 112.

[0034] The differential configuration extraction unit 112 extracts system components that have been specified one step further by the configuration design unit 111. The differential configuration extraction unit 112 obtains the system configuration from the storage device 12 before the system configuration input from the configuration design unit 111 is specified one step further, and compares the components between the system configurations before and after the specification. The difference configuration extraction unit 112 is an example of a difference configuration extraction means.

[0035] The difference configuration extraction unit 112 compares the components of the system configurations to extract the components that constitute the differences between the system configurations, the components that have relationships with those components, and information about those relationships. This extracted information indicates that, in the system configurations being compared, the configuration design unit 111 applied concretization patterns to the components that have relationships with the components extracted as differences to perform the design. Hereinafter, the components extracted as differences will be referred to as "additional components," and the components that have relationships with the additional components will be referred to as "concretization target components."

[0036] The difference configuration extraction unit 112 outputs difference configuration information, which consists of the specific component to be specified, the additional component, and the relationships between the components, to the analysis unit 113.

[0037] The analysis unit 113 analyzes whether the additional component is related to the system requirements. In other words, the analysis unit 113 determines whether the additional component is related to the system requirements. The specific analysis details will be described later. For each single requirement item included in the system requirements, the analysis unit 113 analyzes whether the additional component is related to the system requirements. The analysis unit 113 is an example of an analysis tool.

[0038] The requirements referred to here are the characteristics required of a system, a subset system, or a component. A subset system, in this context, is a part of a system. For example, "minimum throughput" or "maximum number of users" are examples of requirement items. However, "minimum throughput" and "maximum number of users" are just examples, and requirement items are not limited to specific items.

[0039] Furthermore, the characteristics of a system, a subsystem, or a component are also referred to as the attributes of that system, subsystem, or component. For example, the minimum throughput of a component, or the maximum number of users of a component (the maximum number of users that the component can handle), are examples of attributes of a component. However, minimum throughput and maximum number of users are just examples, and the items that can be considered attributes are not limited to specific items.

[0040] Furthermore, the characteristics required of a system, a subset of a system, or a component are also referred to as the attributes required of that system, its subset, or its component. The attributes required of a system, a subset of a system, or a component may be characteristics specified in the system requirements, or characteristics calculated from the characteristics specified in the system requirements. For example, if the maximum number of users required in the system requirements is 100, and this maximum number of users is to be equally shared between two components, the maximum number of users required for one component is calculated to be 50.

[0041] The attributes possessed by a system, a subset, or a component, and the attributes required of a system, a subset, or a component, are collectively referred to as the attributes of that system, its subset, or its component. The items that are subject to attributes are also called attribute items or attribute fields. Attribute items required for a system, a subset of a system, or a component may also be called requirements for that system, its subset, or its component. Information that indicates attributes is also called attribute information.

[0042] The analysis unit 113 acquires requirement tracking configuration information stored by the requirement tracking configuration generation unit 114, which will be described later, from the storage device 12. The requirement tracking configuration referred to here is the configuration of the part of the system (which may be a system under design) that relates to a certain requirement item (for example, a requirement item specified by the user). The requirement tracking configuration can be considered as a partial configuration extracted from the system configuration, consisting only of the components related to a certain requirement item and the relationships (relationships between components) related to that requirement item. Requirements tracking configuration information is information that describes the requirements tracking configuration. Requirements tracking configuration information shows the configuration of the requirements tracking configuration and the attributes of the components of the requirements tracking configuration.

[0043] The analysis unit 113 extracts the attributes of the component to be materialized (in this case, the attributes possessed by the component to be materialized) that are related to the requirement items included in the system requirements from the requirements tracking configuration information or differential configuration information. The requirement items included in the system requirements are also called system requirement items. A single requirement item may have multiple related attributes.

[0044] The analysis unit 113 determines whether the constraints using the extracted attributes are included in the constraints of the additional components. In other words, the analysis unit 113 determines whether the extracted attributes are used in the constraints of the additional components. For example, if the analysis unit 113 extracts throughput as an attribute, it determines whether the constraint condition using the throughput (attribute information) of the additional component is included in the constraint condition of the additional component. If the analysis unit 113 determines that a constraint condition using the attribute in question is included, it generates analysis result information for each single requirement item, consisting of extracted differential configuration information and attribute information of the attribute of the additional component.

[0045] Furthermore, the analysis unit 113 determines whether the constraints using the extracted attributes are included in the constraints of the component to be materialized. In other words, the analysis unit 113 determines whether the extracted attributes are used in the constraints of the component to be materialized. If the analysis unit 113 determines that constraints using the attribute in question are included, it generates analysis result information for each single requirement item, which consists of extracted differential configuration information and attribute information of the attribute of the component to be materialized.

[0046] Furthermore, the analysis unit 113 determines whether the constraints using the extracted attributes are included in the constraints of the relationship between the additional component and the component to be materialized. In other words, the analysis unit 113 determines whether the extracted attributes are used in the constraints of the above-mentioned relationship. If the analysis unit 113 determines that a constraint condition using the attribute in question is included, it generates analysis result information for each single requirement item, consisting of extracted differential configuration information and attribute information of the attribute in question in the above-mentioned relationship.

[0047] The analysis unit 113 outputs the generated analysis result information to the requirements tracking configuration generation unit 114.

[0048] The requirements tracking configuration generation unit 114 generates requirements tracking configuration information for each system requirement item using the analysis result information (determination result by the analysis unit 113). The requirements tracking configuration generation unit 114 generates a requirements tracking configuration for each single requirement item included in the system requirements. The requirements tracking configuration generation unit 114 is an example of requirements tracking configuration generation means.

[0049] The requirements tracking configuration generation unit 114 acquires, for each single requirement item included in the system requirements, the requirements tracking configuration information before it is further refined from the storage device 12, and the analysis result information input by the analysis unit 113.

[0050] Figure 6 shows an example of updating requirements tracking configuration information. The requirements tracking configuration generation unit 114 updates the requirements tracking configuration information by integrating the requirements tracking configuration information and the analysis result information for each single requirement item, as shown in Figure 6, and stores it in the storage device 12. In the example in Figure 6, the "Web App" (web application), which is a component of system configuration D11 included in the requirements tracking configuration information from the previous stage, matches the "Web App" (web application), which is a component of system configuration D12 included in the analysis result information. Therefore, the requirements tracking configuration generation unit 114 combines system configuration D11 included in the requirements tracking configuration information from the previous stage and system configuration D12 included in the analysis result information so as to connect the "Web App" component. As a result, the requirements tracking configuration generation unit 114 generates system configuration D13 included in the updated requirements tracking configuration information.

[0051] The requirements tracking configuration generation unit 114 generates requirements tracking configuration information as shown in the example in Figure 6, allowing the user to easily understand the related components for each single requirement item included in the system requirements.

[0052] (Operation description) Figure 7 is a flowchart showing an example of the operation of design system 1.

[0053] (Step S1) The configuration design unit 111 receives system requirements input from the input device 13. After step S1, the process proceeds to step S2.

[0054] (Step S2) The configuration design unit 111 designs a specific system configuration that satisfies the input system requirements and constraints in one step by adding or replacing components according to the concretization pattern. The configuration design unit 111 stores the designed system configuration in the storage device 12 and also outputs it to the differential configuration extraction unit 112. After step S2, the process proceeds to step S3.

[0055] (Step S3) When the differential configuration extraction unit 112 receives the system configuration input from the configuration design unit 111, it generates differential configuration information consisting of the differences in components between that system configuration and the system configuration obtained from the storage device 12 one step prior to design. The differential configuration extraction unit 112 outputs the generated differential configuration information to the analysis unit 113. After step S3, the process proceeds to step S4.

[0056] (Step S4) When the analysis unit 113 receives differential configuration information from the differential configuration extraction unit 112, it determines whether requirement tracking configuration information exists in the storage device 12. If the analysis unit 113 determines that requirements tracking configuration information exists (step S4: YES), the process proceeds to step S5. On the other hand, if the analysis unit 113 determines that no requirements tracking configuration information exists (step S4: NO), the process proceeds to step S6.

[0057] (Step S5) The analysis unit 113 obtains requirements tracking configuration information from the storage device 12. After step S5, the process proceeds to step S6.

[0058] (Step S6) The analysis unit 113 obtains the attributes of the component to be materialized that are related to the requirement items included in the system requirements, from the requirements tracking configuration information or differential configuration information. After step S6, the process proceeds to step S7.

[0059] (Step S7) The analysis unit 113 determines whether the constraints using the extracted attributes are included in the constraints of the additional components, the constraints of the components to be materialized, and the constraints of the relationship between the additional components and the components to be materialized (step S7). If the analysis unit 113 determines that constraints using the extracted attributes are included (step S7: YES), it outputs the extracted differential configuration information and the attribute information included in the constraint (attribute information of the extracted attribute) for each single requirement item to the requirements tracking configuration generation unit 114 as analysis result information. The process then proceeds to step S8. On the other hand, if the analysis unit 113 determines that the extracted attributes do not constitute constraints (step S7: NO), the process proceeds to step S9.

[0060] Figures 8 and 9 illustrate an example of differential configuration information. Figure 8 shows an example of differential configuration information. In the differential configuration information shown in Figure 8, the specific component to be implemented, "WS" (Web System), and the additional components, "AP" (Web Application) and "DBS" (Database System), have the relationships indicated by arrows, and the components "WS" (Web System) and "AP" (Web Application) have the attributes and constraints indicated by callouts. In the example shown in Figure 8, the analysis unit 113 extracts the "maximum number of users" of the specified component "WS" (web system) as an attribute related to the requirement item included in the system requirements in step S6. Next, in step S7, the analysis unit 113 determines that the constraint condition using the attribute "maximum number of users" of the specified component "WS" (web system) is included in the constraint condition of "WS" (web system) ("maximum number of users of AP = maximum number of users of WS"), and adds the attribute "maximum number of users" of the additional component "AP" (web application) to the analysis result information.

[0061] Figure 9 shows another example of differential configuration information. In the differential configuration information shown in Figure 9, the component to be materialized, "AP" (Web Application), and the additional component, "OS" (OS), have a relationship indicated by arrows, and the components "AP" (Web Application) and "OS" (OS) have attributes and constraints indicated by callouts. In the example shown in Figure 9, in step S6, the analysis unit 113 extracts the "maximum number of users" of the specified component "AP" (web application) as an attribute related to the requirement item included in the system requirements. Next, in step S7, the analysis unit 113 determines that the constraint condition using the attribute "maximum number of users" of the specified component "AP" (web application) is included in the constraint condition of "AP" (web application) ("number of users that the OS can accommodate ≥ maximum number of users of AP"), and adds the attribute "number of users that can be accommodated" of the additional component "OS" (OS) to the analysis result information.

[0062] (Step S8) When the requirements tracking configuration generation unit 114 receives analysis result information from the analysis unit 113, it retrieves the requirements tracking configuration information from the storage device 12 before it is further refined, and generates the requirements tracking configuration information by integrating the requirements tracking configuration information with the analysis result information, and stores it in the storage device 12. The requirements tracking configuration generation unit 114 also notifies the analysis unit 113 that the requirements tracking configuration generation step has been completed. After step S8, the process proceeds to step S9.

[0063] (Step S9) The analysis unit 113 determines whether the analysis of all attributes obtained in step S6 has been completed. If the analysis unit 113 determines that there are attributes whose analysis is not yet complete (step S9: NO), the process returns to step S6. In this case, the analysis unit 113 executes the process in step S6 for the incomplete attributes. On the other hand, if it is determined that the analysis for all attributes is complete (step S9: YES), the analysis unit 113 notifies the configuration design unit 111 that the analysis step is complete. The process then proceeds to step S10.

[0064] (Step S10) The configuration design unit 111 determines whether or not the specification of all components has been completed. (Step S10: NO), the process returns to step S. In this case, the configuration design unit 111, If the configuration design unit 111 determines that there are components that have not been fully materialized (step S10: NO), the process returns to step S2. In this case, the configuration design unit 111 executes the process in step S2 for the incomplete components. On the other hand, if the configuration design unit 111 determines that the specification of all components has been completed, the design system 1 terminates the process shown in Figure 7.

[0065] (Explanation of effects) As described above, the configuration design unit 111 receives system requirements and designs a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that make up the system. The differential configuration extraction unit 112 extracts system components that have been added or modified in one stage of the design process. The analysis unit 113 determines whether the system components added or modified in the first stage of concretization are related to the system requirements. The requirements tracking configuration generation unit 114 uses the determination result to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration.

[0066] Design system 1 outputs requirements tracking configuration information that shows the relationship between system requirements and the system configuration, which is the design result. By referring to this requirements tracking configuration information, users of design system 1 can understand the relationship between system requirements and the system configuration, which is the design result.

[0067] [Second Embodiment] (Structure description) Figure 10 is a block diagram showing another example of the configuration of a design system according to at least one embodiment. As shown in Figure 10, the design system 6 in the second embodiment for carrying out the present invention further includes a search device 65 in addition to the parts of the design system 1. Otherwise, the design system 6 is the same as the design system 1. The parts of Figure 10 that have the same function as the parts of Figure 1 are denoted by the same reference numerals (1, 11, 12, 13, 14, 111, 112, 113, 114), and a detailed description is omitted here. The search device 65 and the storage device 12 are connected in a communication manner. For example, the requirements tracking information search unit 651 may be able to access the storage device 12.

[0068] Furthermore, the scope of application of each technology adopted in this embodiment is not limited to this embodiment. That is, each technology adopted in this embodiment can also be adopted in other embodiments included in this disclosure, to the extent that no particular technical problems arise. In addition, each technology shown in the drawings referenced to explain this embodiment can also be adopted in other embodiments included in this disclosure, to the extent that no particular technical problems arise.

[0069] The search device 65 comprises a requirements tracking information search unit 651 and a requirements tracking information synthesis unit 652. The requirements tracking information search unit 651 is connected to the storage device 12.

[0070] The requirements tracking information retrieval unit 651 receives information identifying the system configuration and system requirement items from the input device 13, and searches for requirements tracking configuration information for the input requirement items for the identified system configuration. The requirements tracking information retrieval unit 651 is an example of a requirements tracking information retrieval means.

[0071] Here, the storage device 12 stores multiple system requirements and system configurations for each system requirement. The requirements tracking information retrieval unit 651 extracts requirements tracking configuration information from among the multiple system configurations stored in the storage device 12, specifically from the system configuration identified by the information that identifies the system configuration. Alternatively, the requirements tracking information retrieval unit 651 may receive system requirement items from the input device 13 and retrieve requirements tracking configuration information for the input requirement items from the entire system configuration stored in the storage device 12. Multiple system requirement items may be entered. The requirements tracking information search unit 651 retrieves requirements tracking configuration information corresponding to the received system configuration and requirement items from the storage device 12 using the search described above, and outputs it to the requirements tracking information synthesis unit 652.

[0072] The requirements tracking information synthesis unit 652 synthesizes multiple requirements tracking configuration information when it receives multiple requirements tracking configuration information from the requirements tracking information search unit 651. Specifically, the requirements tracking information synthesis unit 652 compares the system configuration components and the attributes of those components for each of the multiple requirements tracking configuration information. The requirements tracking information synthesis unit 652 then generates a single requirements tracking configuration information that includes all the components and attributes included in the multiple requirements tracking configuration information and outputs it to the output device 14. The synthesis of requirements tracking configuration information performed by the requirements tracking information synthesis unit 652 can be understood as combining multiple requirements tracking configuration information into a single requirements tracking configuration information. The requirements tracking information synthesis unit 652 is an example of a requirements tracking information synthesis means.

[0073] Figure 11 shows an example of the requirements tracking configuration display screen displayed by the output device 14. The output device 14 can output (display) a requirements tracking configuration display screen as shown in Figure 11. In the example in Figure 11, the requirements tracking configuration screen includes a display area A11 for system requirements information and a display area A12 for the requirements tracking configuration diagram. The system requirements information shown in display area A11 shows the requirement items and their specific values ​​that are included in the system requirements input from the input device 13. The requirements tracking configuration diagram shown in display area A12 shows the requirements tracking configuration information for the requirement item selected in the system requirements information display area A11. In the example in Figure 11, the requirement item "Maximum number of users" included in the system requirements information is selected, and the requirements tracking configuration information for the requirement item "Maximum number of users" is displayed in display area A12 of the requirements tracking configuration diagram.

[0074] As described above, the input device 13 may receive information identifying the system configuration and system requirement items. In this case, the requirements tracking configuration display screen displayed by the output device 14 may have a display area for information identifying the system configuration (for example, the system configuration name or the system configuration identification number) in addition to the display area A11 for the system requirement information.

[0075] The output device 14 may display, side by side, in display area A12 a system configuration diagram showing specific system configuration information that satisfies the system requirements input from the input device 13, and a requirements tracking configuration diagram showing requirements tracking configuration information. Alternatively, the output device 14 may overlay the system configuration diagram showing specific system configuration information that satisfies the system requirements input from the input device 13 and the requirements tracking configuration diagram showing requirements tracking configuration information in display area A12. When the output device 14 overlays the system configuration information and the requirements tracking configuration information, it may highlight the requirements tracking configuration information. This makes it easier for the user to confirm the requirements tracking configuration information.

[0076] (Operation description) Figure 12 is a flowchart showing an example of the operation of the search device 65.

[0077] In the process shown in Figure 12, the requirements tracking information retrieval unit 651 receives input from the input device 13, which includes information identifying the system configuration and specific system requirement items (step S21).

[0078] Next, the requirements tracking information retrieval unit 651 retrieves requirements tracking configuration information for the input system requirement items for the system configuration identified by the information from the input device 13 from the storage device 12 and outputs it to the requirements tracking information synthesis unit 652 (step S22).

[0079] Next, the requirements tracking information synthesis unit 652 synthesizes one or more requirements tracking configuration information input from the requirements tracking information search unit 651 to generate a single requirements tracking configuration information (step S23).

[0080] Next, the requirements tracking information synthesis unit 652 outputs the generated single requirements tracking configuration information via the output device 14 (step S24). After step S24, the search device 65 completes the process shown in Figure 12.

[0081] (Explanation of effects) As described above, the requirements tracking information retrieval unit 651 receives input of information that identifies the system configuration and specific system requirement items, and searches for requirements tracking configuration information for the system requirement items in relation to the system configuration. The requirements tracking information synthesis unit 652 synthesizes the requirements tracking configuration information when it receives multiple sets of requirements tracking configuration information.

[0082] According to design system 6, users of this design system 6 can search for specific requirement tracking configuration information by specifying the system configuration and requirement items. The requirement items can be single or multiple, enabling users to understand the relationship between the system requirements they want to check and the resulting system configuration.

[0083] [Third Embodiment] (Structure description) Figure 13 is another block diagram showing the configuration of the design system according to at least one embodiment. As shown in Figure 13, in the design system 8 in the third embodiment for carrying out the present invention, the design device 81 differs from the design device 11 of the design system 1. In addition to the parts provided by the design device 11, the design device 81 further includes a design basis recording unit 815. In other respects, the design system 8 is the same as the design system 1. Among the parts in Figure 13, parts that have the same function as the parts in Figure 1 are denoted by the same reference numerals, and detailed descriptions are omitted here.

[0084] The design device 81 and the storage device 12 are connected in a communication manner. For example, the configuration design unit 111, the differential configuration extraction unit 112, the analysis unit 113, the design basis recording unit 815, and the requirements tracking configuration generation unit 114 may each have access to the storage device 12. The design device 81 is also connected in a communication manner to the input device 13. The design device 81 is also connected in a communication manner to the output device 14.

[0085] Furthermore, the scope of application of each technology adopted in this embodiment is not limited to this embodiment. That is, each technology adopted in this embodiment can also be adopted in other embodiments included in this disclosure, to the extent that no particular technical problems arise. In addition, each technology shown in the drawings referenced to explain this embodiment can also be adopted in other embodiments included in this disclosure, to the extent that no particular technical problems arise.

[0086] The design device 81 comprises a configuration design unit 111, a differential configuration extraction unit 112, an analysis unit 113, a design basis recording unit 815, and a requirements tracking configuration generation unit 114. The design basis recording unit 815 is connected to the storage device 12.

[0087] The design rationale recording unit 815 adds design rationale information to the analysis result information generated by the analysis unit 113. Design rationale information is information that shows that the designed system satisfies the required constraints. As design rationale information, for example, evaluation content using the identification name, characteristics, and attributes of components such as the component to be materialized, additional components, or the configuration selected as a result of materialization can be used. Here, the identification name is a name used to identify the component. Constraints may be expressed using mathematical formulas. That is, evaluation content using attributes may be expressed as an equation or inequality using attributes, or a combination thereof. This design rationale information is information that shows what constraints exist between components with respect to a specific attribute and what configuration was selected as a result of materialization, and is information that allows the user to understand the design rationale. The design basis recording unit 815 is an example of a design basis recording means.

[0088] The design rationale recording unit 815 receives analysis result information from the analysis unit 113 and extracts design rationale information from the constraints of the additional components, the constraints of the components to be materialized, and the constraints of the relationship between the additional components and the components to be materialized.

[0089] The design basis recording unit 815 may extract specific attribute values ​​from one or more of the additional components, the components to be materialized, and the attributes of the relationship between the additional components and the components to be materialized, and add them to the design basis information.

[0090] The design rationale recording unit 815 adds the design rationale information to the analysis result information and outputs it to the analysis unit 113.

[0091] The design rationale recording unit 815 may determine whether or not to add the design rationale information to the analysis result information depending on the type of evaluation content using attributes. For example, the design rationale recording unit 815 may not add the evaluation content using attributes to the analysis result information if it is an equation, but may add it to the analysis result information if it is an inequality.

[0092] Figure 14 shows another example of the requirements tracking configuration display screen displayed by the output device 14. The output device 14 can output (display) a requirements tracking configuration screen as shown in Figure 14. The requirements tracking configuration screen in the example of Figure 14 differs from that in Figure 11 in that the display area A23 for design rationale information is included in the display area A22 of the requirements tracking configuration diagram. In all other respects, the requirements tracking configuration screen in the example of Figure 14 is the same as that in Figure 11. In the requirements tracking configuration display screen in the example of Figure 14, the display area for system requirements information is the same as in Figure 11, and the same reference numeral (A11) is used as in Figure 11, so a detailed explanation is omitted here.

[0093] The output device 14 displays, overlaid on the display area A22 of the requirements tracking configuration diagram, a system configuration diagram showing specific system configuration information that satisfies the system requirements input from the input device 13, a requirements tracking configuration diagram showing the requirements tracking configuration information for the requirement items selected in the display area A11 of the system requirements information, and the design rationale information in area 23. The design rationale information in area A23 is the design rationale information added by the design rationale recording unit 815. In the example in Figure 14, the requirement item "maximum number of users" included in the system requirements information is selected, and in display area A22, the requirements tracking configuration diagram showing the requirements tracking configuration information for the requirement item "maximum number of users" is highlighted and displayed on top of the system configuration diagram showing specific system configuration information.

[0094] The output device 14 may be configured to display only the requirements tracking configuration diagram among the requirements tracking configuration diagram and the system configuration diagram in display area A22. Alternatively, the output device 14 may be configured to display the requirements tracking configuration diagram and the system configuration diagram side by side in display area A22.

[0095] In the example in Figure 14, the component "Web App" (web application) included in the requirements tracking configuration diagram is selected. Output device 14 displays the attributes related to the requirements items of the selected component "Web App" (web application), the identification name of the selected configuration, and the evaluation content using the attributes in display area A23, for each item of "Attributes," "Selected Configuration," and "Constraints." Output device 14 may be configured to display only the design rationale information related to the selected component, as shown in the example in Figure 14. Alternatively, output device 14 may be configured to display the design rationale information related to all components included in the requirements tracking configuration diagram.

[0096] (Operation description) Figure 15 is a flowchart illustrating an example of the operation of the design system 8. Among the processing steps shown in Figure 15, those that are the same as those shown in Figure 7 are denoted with the same reference numerals (S1, S2, S3, S4, S5, S6, S7, S8, S9, S10) as in Figure 7, and detailed explanations are omitted here.

[0097] The process in Figure 15 differs from the process in Figure 7 in the following respects. The first point is that if the analysis unit 113 determines that there are constraints using the attributes extracted in step S6 (step S7: YES), it outputs the analysis result information to the design basis recording unit 815. After that, the process proceeds to step S31. The second point is that the design rationale recording unit 815 extracts design rationale information from the constraints of the additional components, the constraints of the components to be materialized, and the constraints of the relationship between the additional components and the components to be materialized, and adds it to the analysis result information (step S31). After step S31, the process proceeds to step S8. In all other respects, the process in Figure 15 is the same as the process in Figure 7.

[0098] (Explanation of effects) As described above, the design basis recording unit 815 adds information that serves as the basis for the design to the requirements tracking configuration information. Design system 8 outputs requirements tracking configuration information, which includes information showing the relationship between system requirements and the resulting system configuration, as well as information showing the rationale behind the design. By referring to this requirements tracking configuration information, users of design system 8 can understand the detailed rationale behind how the system requirements were specifically evaluated and how the resulting system configuration was selected.

[0099] [Fourth Embodiment] Figure 16 shows another example of the configuration of a design system according to at least one embodiment. As shown in Figure 16, the design system 910 comprises a configuration design unit 911, a difference configuration extraction unit 912, an analysis unit 913, and a requirements tracking configuration generation unit 914.

[0100] In this configuration, the configuration design unit 911 receives system requirements as input and designs a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that make up the system. The differential configuration extraction unit 912 extracts system components that have been added or changed in one stage of concretization during the design process. The analysis unit 913 determines whether the system components that have been added or changed in one stage of concretization are related to the system requirements. The requirements tracking configuration generation unit 914 uses the determination result to generate requirements tracking configuration information that shows the relationship between the system requirements and the system configuration. The configuration design unit 911 is an example of a configuration design means. The differential configuration extraction unit 912 is an example of a differential configuration extraction means. The analysis unit 913 is an example of an analysis means. The requirements tracking configuration generation unit 914 is an example of a requirements tracking configuration generation means.

[0101] The design system 910 outputs requirements tracking configuration information that shows the relationship between system requirements and the system configuration, which is the design result. By referring to this requirements tracking configuration information, users of the design system 910 can understand the relationship between system requirements and the system configuration, which is the design result.

[0102] [Fifth Embodiment] Figure 17 shows another example of the configuration of a search device according to at least one embodiment. As shown in Figure 17, the search device 920 comprises a requirements tracking information search unit 921 and a requirements tracking information synthesis unit 922.

[0103] In this configuration, the requirements tracking information retrieval unit 921 receives input of information identifying the system configuration and specific system requirement items, and searches for requirements tracking configuration information for the system requirement items in relation to the system configuration. When the requirements tracking information synthesis unit 922 receives multiple requirements tracking configuration information for a single system requirement item, it combines these multiple requirements tracking configuration information into a single requirement tracking configuration information. The requirements tracking information retrieval unit 921 is an example of requirements tracking information retrieval means. The requirements tracking information synthesis unit 922 is an example of requirements tracking information synthesis means.

[0104] According to the search device 920, a user of this search device 920 can search for specific requirement tracking configuration information by specifying the system configuration and requirement items. The requirement items can be single or multiple, enabling the user to understand the relationship between the system requirements they want to check and the system configuration, which is the result of the design.

[0105] [Sixth Embodiment] Figure 18 shows an example of the processing steps in a design method according to at least one embodiment. The design method shown in Figure 18 includes designing a system configuration (step S911), extracting system components (step S912), making a determination (step S913), and generating requirements tracking configuration information (step S914).

[0106] In designing the system configuration (step S911), the computer receives system requirements as input and designs a specific system configuration that satisfies those input requirements by repeatedly concretizing the system components that make up the system. In extracting system components (step S912), the computer extracts system components that have been added or modified in a stage of realization during the design process. In making a determination (step S913), the computer determines whether the components added or modified in one step of the embodiment are related to the system requirements. In generating requirements tracking configuration information (step S914), the computer uses the determination results to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration.

[0107] According to the design method shown in Figure 18, the computer outputs requirements tracking configuration information that shows the relationship between system requirements and the system configuration, which is the design result. According to the design method shown in Figure 18, the user of this computer can understand the relationship between system requirements and the system configuration, which is the design result, by referring to the requirements tracking configuration information.

[0108] [Seventh Embodiment] Figure 19 is a diagram showing an example of the processing steps in a search method according to at least one embodiment. The search method shown in Figure 19 includes searching for requirements tracking configuration information (step S921) and summarizing the requirements tracking configuration information (step S922).

[0109] In retrieving requirements tracking configuration information (step S921), the computer receives input of information identifying the system configuration and specific system requirement items, and retrieves requirements tracking configuration information for the system requirement items for the said system configuration. In the process of consolidating requirements tracking configuration information (step S922), if the computer detects multiple requirements tracking configuration information entries for a single system requirement item, it consolidates these multiple requirements tracking configuration information entries into a single requirement tracking configuration information entry.

[0110] According to the search method shown in Figure 19, the user of the computer executing this search method can search for specific requirement tracking configuration information by specifying the system configuration and requirement items. The requirement items can be single or multiple, enabling the user to understand the relationship between the system requirements they wish to verify and the resulting system configuration.

[0111] [Examples of implementation using software] Some or all of the functions of design systems 1, 6, 8 and 910 and search device 920 (hereinafter also referred to as "the aforementioned systems or devices") may be implemented by hardware such as integrated circuits (IC chips) or by software.

[0112] In the latter case, each of the aforementioned systems or devices is implemented, for example, by a computer that executes instructions for a program, which is software that implements each function. An example of such a computer (hereinafter referred to as Computer C) is shown in Figure 20. Figure 20 is a block diagram showing the hardware configuration of Computer C, which functions as each of the aforementioned devices.

[0113] Computer C comprises at least one processor C1 and at least one memory C2. Memory C2 stores a program P that causes computer C to operate as each of the aforementioned devices. In computer C, processor C1 reads program P from memory C2 and executes it, thereby realizing each of the aforementioned devices.

[0114] For processor C1, for example, a CPU (Central Processing Unit), GPU (Graphic Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating Point Number Processing Unit), PPU (Physics Processing Unit), TPU (Tensor Processing Unit), quantum processor, microcontroller, or a combination thereof can be used. For memory C2, for example, flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or a combination thereof can be used.

[0115] Computer C may also be equipped with RAM (Random Access Memory) for loading program P at runtime and for temporarily storing various data. Furthermore, computer C may be equipped with communication interfaces for sending and receiving data with other devices. Additionally, computer C may be equipped with input / output interfaces for connecting input / output devices such as keyboards, mice, displays, and printers.

[0116] Furthermore, program P can be recorded on a non-temporary, tangible recording medium M that is readable by computer C. Such a recording medium M could be, for example, tape, disk, card, semiconductor memory, or programmable logic circuitry. Computer C can acquire program P via such a recording medium M. Program P can also be transmitted via a transmission medium. Such a transmission medium could be, for example, a communication network or broadcast waves. Computer C can also acquire program P via such a transmission medium.

[0117] Furthermore, each of the aforementioned functions of each of the aforementioned systems or devices may be implemented by a single processor in a single computer, by multiple processors in a single computer working together, or by multiple processors in each of multiple computers working together. In addition, the programs for implementing each of the aforementioned functions of each of the aforementioned systems or devices may be stored in a single memory in a single computer, distributed and stored in multiple memories in a single computer, or distributed and stored in multiple memories in each of multiple computers.

[0118] Some or all of the above embodiments may also be described as follows, but are not limited to these.

[0119] (Note 1) A configuration design method that receives system requirements as input and designs a specific system configuration that satisfies those input system requirements by repeatedly concretizing the system components that make up the system, A differential configuration extraction means for extracting system components that have been added or modified in one stage of concretization during the design process, An analytical means for determining whether system components added or modified in a first stage of concretization are related to system requirements, A requirements tracking configuration generation means that generates requirements tracking configuration information showing the relationship between system requirements and system configuration using the determination result, A design system equipped with the following features.

[0120] (Note 2) A requirements tracking information search means that receives information identifying the system configuration and specific system requirement items as input, and searches for requirements tracking configuration information for the system requirement items for the said system configuration, A requirements tracking information synthesis means that, when multiple requirements tracking configuration information is received for a single system requirement item, combines these multiple requirements tracking configuration information into a single requirements tracking configuration information, The design system described in Appendix 1, comprising the features described above.

[0121] (Note 3) The design system according to Appendix 1 or 2, further comprising a design basis recording means for adding information that serves as the basis for the design to the requirements tracking configuration information.

[0122] (Note 4) A requirements tracking information search means that receives information identifying the system configuration and specific system requirement items as input, and searches for requirements tracking configuration information for the system requirement items for the said system configuration, A requirements tracking information synthesis means that, when multiple requirements tracking configuration information is received for a single system requirement item, combines these multiple requirements tracking configuration information into a single requirements tracking configuration information, A search device equipped with the following features.

[0123] (Note 5) Computers The process involves receiving system requirements and designing a specific system configuration that satisfies those requirements, which is done by repeatedly concretizing the system components that make up the system. A step of extracting system components that have been added or modified in one stage of concretization during the design process, A step of determining whether any components added or modified in a first stage of concretization are relevant to the system requirements, Using the judgment results, a step is to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration, A design method that includes this.

[0124] (Note 6) The aforementioned computer, The steps include receiving information that identifies the system configuration and specific system requirement items as input, and searching for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are received for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. The design method described in Appendix 5, including the method described in Appendix 5.

[0125] (Note 7) The aforementioned computer, Steps to add information that forms the basis of the design to the requirements tracking configuration information. The design method described in Appendix 5 or Appendix 6, including the following.

[0126] (Note 8) Computers The steps include receiving information that identifies the system configuration and specific system requirement items as input, and searching for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are detected for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. Search methods that include this.

[0127] (Note 9) On the computer, The process of receiving system requirements and designing a specific system configuration that satisfies those requirements involves repeatedly concretizing the system components that make up the system. A process for extracting system components that have been added or modified in one stage of concretization during the design process, A process to determine whether system components added or modified in a first stage of concretization are related to system requirements, Using the judgment results, a process is performed to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration, A program that executes the command.

[0128] (Note 10) To the aforementioned computer, A process that receives information identifying the system configuration and specific system requirement items as input, and searches for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are received for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. The program described in Appendix 9 that executes this program.

[0129] (Note 11) To the aforementioned computer, Process to add information that forms the basis of the design to the aforementioned requirements tracking configuration information. The program described in Appendix 9 or Appendix 10 that causes the execution of the above.

[0130] (Note 12) On the computer, A process that receives information identifying the system configuration and specific system requirement items as input, and searches for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are detected for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. A program that executes the command. [Explanation of Symbols]

[0131] 1, 6, 8, 910 Design System 11, 81 Design equipment 12 Storage device 65,920 Search Devices 111, 911 Configuration Design Department 112, 912 Difference configuration extraction part 113, 913 Analysis Department 114, 914 Requirements tracking configuration generation unit 651, 921 Requirements Tracking Information Retrieval Department 652, 922 Requirements Tracking Information Synthesis Unit 815 Design Basis Record Section

Claims

1. A configuration design method that receives system requirements as input and designs a specific system configuration that satisfies the input system requirements by repeatedly concretizing the system components that make up the system, A differential configuration extraction means for extracting system components that have been added or modified in one stage of concretization during the design process, An analytical means for determining whether system components added or modified in a first stage of concretization are related to system requirements, A requirements tracking configuration generation means that generates requirements tracking configuration information showing the relationship between system requirements and system configuration using the judgment result, A design system equipped with the following features.

2. A requirements tracking information search means that receives information identifying the system configuration and specific system requirement items as input, and searches for requirements tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration pieces are received for a single system requirement item, a requirement tracking information synthesis means is provided to combine these multiple requirement tracking configuration pieces into a single requirement tracking configuration piece. The design system according to claim 1, comprising:

3. The design system according to claim 1 or 2, further comprising design basis recording means for adding information that serves as the basis for the design to the requirements tracking configuration information.

4. A requirements tracking information search means that receives information identifying the system configuration and specific system requirement items as input, and searches for requirements tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration pieces are received for a single system requirement item, a requirement tracking information synthesis means is provided to combine these multiple requirement tracking configuration pieces into a single requirement tracking configuration piece. A search device equipped with the following features.

5. Computers The process involves receiving system requirements and designing a specific system configuration that satisfies those requirements, which is done by repeatedly concretizing the system components that make up the system. A step of extracting system components that have been added or modified in one stage of concretization during the design process, A step of determining whether any components added or modified in a first stage of concretization are relevant to the system requirements, Using the judgment results, a step is to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration, A design method that includes this.

6. The aforementioned computer, Steps to add information that forms the basis of the design to the requirements tracking configuration information. The design method according to claim 5, including the following:

7. Computers The steps include receiving information that identifies the system configuration and specific system requirement items as input, and searching for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are detected for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. Search methods that include this.

8. On the computer, The process of receiving system requirements and designing a specific system configuration that satisfies those requirements involves repeatedly concretizing the system components that make up the system. A process for extracting system components that have been added or modified in one stage of concretization during the design process, A process to determine whether system components added or modified in a first stage of concretization are related to system requirements, Using the judgment results, a process is performed to generate requirements tracking configuration information that shows the relationship between system requirements and system configuration, A program that executes the command.

9. To the aforementioned computer, Process to add information that forms the basis of the design to the aforementioned requirements tracking configuration information. The program according to claim 8, which causes the execution of the program.

10. On the computer, A process that receives information identifying the system configuration and specific system requirement items as input, and searches for requirement tracking configuration information for the system requirement items for the said system configuration, When multiple requirement tracking configuration information entries are detected for a single system requirement item, the process involves consolidating these multiple requirement tracking configuration information entries into a single requirement tracking configuration information entry. A program that executes the command.

Images