Computer system and support method for architecture design of it system

The system addresses the challenge of designing IT system architectures by using an element database and historical data to rank and generate cost-effective architecture combinations, ensuring suitable and cost-conscious design solutions.

WO2024236958A1PCT designated stage expired Publication Date: 2024-11-21HITACHI LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/014536
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-04-10
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Conventional systems for designing IT system architectures lack consideration of implementation costs and provide unclear criteria for altering design information combinations, making it difficult for designers to generate suitable architectures that meet user requirements.

Method used

A computer system that supports IT system architecture design by using an element database to associate non-functional requirements with design elements, maintaining a historical database for implementation history, and generating combinations of elements to determine recommendation rankings based on evaluation indices, with alternative generation methods when constraints are not met.

Benefits of technology

Enables the design of appropriate IT system architectures that consider cost constraints and provides clear rationale for architectural changes, ensuring efficient and effective design decisions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024014536_21112024_PF_FP_ABST
    Figure JP2024014536_21112024_PF_FP_ABST
Patent Text Reader

Abstract

A computer system according to the present invention holds an element database that manages elements that are design information for implementing non-functional requirements, and a history database that stores an implementation history of past non-functional requirements. The computer system acquires information on non-functional requirements to be implemented in an IT system achieved by a base architecture, generates multiple combinations of elements by referring to the element database, and assigns priorities to the multiple combinations of elements that indicate a recommended order for the multiple combinations of elements. If there is no combination of elements satisfying constraint conditions, an alternative is generated using the implementation history. The computer system outputs at least any of combinations of elements and alternatives sorted on the basis of priority.
Need to check novelty before this filing date? Find Prior Art

Description

Support method for architecture design of computer systems and IT systems Incorporation by Reference

[0001] This application claims priority from Japanese Patent Application No. 2023-79130, filed May 12, 2023, the contents of which are incorporated herein by reference.

[0002] The present invention relates to a system for supporting architecture design.

[0003] In the development of IT systems, the design of IT system architecture plays an important role in converting the requirements that users have for the IT system into the structure and format of a computer, thereby forming the foundation of the IT system. In this specification, the architecture of an IT system refers to information that expresses in a concrete format the components of the IT system and the connections between the components.

[0004] Designing an IT system architecture requires extensive knowledge of IT systems in general, as well as in-depth knowledge of the relationships between the components of the architecture and implementation methods. Therefore, designing an IT system architecture from scratch is time-consuming and labor-intensive. In response to this, cloud vendors and others provide reference architectures that correspond to the domain and purpose of the IT system.

[0005] A reference architecture is created based on configurations that frequently occur in a domain or best practices in architecture design, and is composed of general services and minimum functions for achieving the purpose of an IT system.

[0006] Designers can efficiently design the architecture of an IT system by modifying a reference architecture corresponding to a similar domain or purpose in accordance with the user requirements of the IT system.

[0007] User requirements are generally classified into functional and non-functional requirements. Functional requirements are requirements related to the functions and behavior provided by an IT system, while non-functional requirements are requirements related to the quality of the IT system, such as performance, security, and availability. Since non-functional requirements are often realized by combining elements that make up the architecture, designers must design an architecture that satisfies user requirements while taking into account the relationships and impacts between non-functional requirements. Therefore, extensive knowledge and experience are also required when designing the architecture of an IT system using a reference architecture.

[0008] Therefore, with conventional technology, if a designer does not have sufficient development capabilities, it is difficult to design an IT system architecture that satisfies user requirements.

[0009] JP 2016-110325 A

[0010] Information-technology Promotion Agency, Japan, "Non-functional Requirement Grade," [online], April 2018, [Retrieved December 27, 2022], Internet <URL: https: / / www.ipa.go.jp / sec / softwareengineering / std / ent03-b.html>

[0011] To address the above-mentioned problem, a technology described in Patent Document 1 is known. Patent Document 1 describes that "in a system design support device 180, design information that realizes each of a plurality of requirements related to a system to be newly designed is identified in a first table, and if multiple pieces of design information are identified for any of the requirements as a result of the identification, a suitability ranking of combinations of each of the multiple pieces of design information with the design information identified for the other requirements is referenced in a second table to identify design information that results in a combination with a higher suitability ranking, and the design information identified for each of the multiple requirements is output to a predetermined device."

[0012] By using the technology described in Patent Document 1, it is possible to output design information that satisfies multiple requirements and has a high suitability ranking. However, Patent Document 1 has the following problems. One problem is that the ranking does not take into account the cost of implementing the IT system architecture. Another problem is that when there is no appropriate combination of design information, the change criteria for the generated alternative plan are not clear.

[0013] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a system and method for ranking IT system architectures taking cost into consideration, and for generating alternatives based on change criteria that can provide the user with reasons if an appropriate architecture cannot be generated.

[0014] A representative example of the invention disclosed in the present application is as follows: A computer system for supporting the design of an IT system architecture maintains an element database storing data associating non-functional requirements with elements that are design information for implementing the non-functional requirements, and a history database storing past implementation histories of the non-functional requirements, acquires information on the non-functional requirements to be implemented in an IT system realized by a base architecture, refers to the element database to generate multiple combinations of elements for implementing the non-functional requirements, calculates evaluation indices used to determine a recommendation order for the multiple combinations of elements, assigns priorities representing the recommendation order for the multiple combinations of elements based on the evaluation indices, determines whether or not a combination of elements that satisfies a constraint exists, and if no combination of elements that satisfies the constraint exists, analyzes the implementation history to identify a method for changing at least one of the elements included in the combination of elements, generates alternatives by modifying the combination of elements based on the identified change method, and outputs at least one of the combinations of elements and the alternatives sorted based on the priority.

[0015] According to one aspect of the present invention, a computer system can support the design of an appropriate IT system architecture. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiment.

[0016] 1 is a diagram illustrating an example of a configuration of an architecture design support system according to a first embodiment. FIG. 1 is a diagram illustrating an example of a data structure of an element DB according to the first embodiment. FIG. 2 is a diagram illustrating an example of a data structure of an element DB according to the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of a history DB according to the first embodiment. FIG. 4 is a flowchart illustrating an example of a process executed by the architecture design support system according to the first embodiment. FIG. 5 is a diagram illustrating an example of a method for identifying elements of non-functional requirements and a method for generating combinations of elements by the architecture design support system according to the first embodiment. FIG. 6 is a diagram illustrating an example of a cost calculation method by the architecture design support system according to the first embodiment. FIG. 7 is a flowchart illustrating an example of a priority determination process executed by the architecture design support system according to the first embodiment. FIG. 8 is a flowchart illustrating an example of a priority determination process executed by the architecture design support system according to the first embodiment. FIG. 9 is a diagram illustrating a specific method for determining priorities according to the first embodiment. FIG. 10 is a flowchart illustrating an example of an alternative plan generation process executed by the architecture design support system according to the first embodiment. FIG. 11 is a flowchart illustrating an example of an alternative plan generation process executed by the architecture design support system according to the first embodiment. Fig. 10 is a flowchart for explaining an example of an alternative generation process executed by the architecture design support system of Example 1. Fig. 11 is a flowchart for explaining an example of an alternative generation process executed by the architecture design support system of Example 3. Fig. 12 is a flowchart for explaining an example of a process executed by the architecture design support system of Example 3. Fig. 13 is a diagram illustrating an example of the configuration of an architecture design support system of Example 4.

[0017] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be modified within the scope of the concept and spirit of the present invention.

[0018] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0019] In this specification, the terms "first," "second," "third," etc. are used to identify components and do not necessarily limit the number or order.

[0020] FIG. 1 is a diagram illustrating an example of the configuration of an architecture design support system 100 according to a first embodiment.

[0021] The architecture design support system 100 of the first embodiment supports the design of an IT system architecture. As will be described later, the architecture design support system 100 generates an IT system architecture that realizes non-functional requirements while taking into account cost constraints.

[0022] In this specification, the architecture of an IT system is defined as information composed of elements that define the type of service, the connections between services, the connections between physical devices, parameters, etc. Also, in this specification, a use case is assumed in which a user adds non-functional requirements to the reference architecture (basic configuration) of an IT system provided by a cloud vendor or the like.

[0023] The architecture design support system 100 includes a combination determination unit 111, a verification unit 112, and an alternative generation unit 113, and also stores an element DB 114 and a history DB 115. The architecture design support system 100 may exchange information directly with a user, or may exchange information with an external system.

[0024] The element DB 114 is a database that stores elements, which are setting information for implementing non-functional requirements. The element DB 114 may be held by an external server different from the architecture design support system 100. Details of the element DB 114 will be described using FIGS. 2A and 2B.

[0025] The history DB 115 is a database that stores the implementation history of the architecture of the IT system. Details of the history DB 115 will be described with reference to FIGS. 3A and 3B.

[0026] The combination determination unit 111 refers to the element DB 114, extracts elements for realizing the specified non-functional requirements, and determines a combination of elements.

[0027] The verification unit 112 calculates costs, which are evaluation indices based on the perspectives of development, implementation, operation, etc., for the combinations of elements determined by the combination determination unit 111, and determines priorities for determining the recommendation order (application order) of the combinations of elements based on the costs. The costs include, for example, the cost required for introducing and maintaining the IT system, the man-hours required for implementation, the service management level in the IT system, etc.

[0028] The alternative generator 113 generates an alternative by referring to the history DB 115 to identify a method for changing an element and modifying the element of the combination of elements based on the identified method for changing the element. Here, the change of an element is a concept that includes the modification of variables and parameters of the element, and the change of the element itself.

[0029] The architecture design support system 100 is realized using a computer having a processor, a memory, and a network interface.

[0030] 2A and 2B are diagrams illustrating an example of a data structure of the element DB 114 according to the first embodiment.

[0031] The element DB 114 stores, for example, a table 200 as shown in FIG. 2A as information for managing elements for realizing non-functional requirements. In this embodiment, the non-functional requirements are classified based on the non-functional requirement items and targets shown in the non-functional requirement grade table in Non-Patent Document 1. Furthermore, the requirement level is defined as a numerical value that relatively indicates the range of non-functional requirements that each element can support. Table 200 stores entries each consisting of an ID 201, an item 202, a target 203, a requirement level 204, and an element 205.

[0032] For example, it shows that the element that realizes the "non-functional requirement related to level 3 fault tolerance for databases" is "RDS for Aurora." Note that there may be multiple elements that realize non-functional requirements with the same item, target, and requirement level, and a new field may be added to table 200 so that elements corresponding to non-functional requirement information have a one-to-one correspondence.

[0033] Element 205 stores data 250 having a data structure such as that shown in FIG. 2B . Data 250 includes information necessary to realize non-functional requirements. For example, data 250 includes names 251 of resources that realize non-functional requirements, codes 252 that represent the structure, parameters, and settings of the resources, and cost-related variables 253. Note that data 250 shown in FIG. 2B is merely an example and is not limiting. For example, data 250 may include a detailed structure between resources as main resources and sub-resources, or may include the importance and setting method of parameters.

[0034] The data 250 may be written in, for example, an IaC (Infrastructure as Code) format provided by a cloud vendor, or may be itemized text.

[0035] 3A and 3B are diagrams illustrating an example of a data structure of the history DB 115 according to the first embodiment.

[0036] The history DB 115 stores the implementation history of non-functional requirements. The history DB 115 stores, for example, a history table 300 as shown in Fig. 3A and an adoption result table 310 as shown in Fig. 3B. The history DB 115 may also include a table for managing the implementation status of non-functional requirements.

[0037] The history table 300 stores entries (implementation history) for managing elements implemented in an IT system to realize non-functional requirements. The entries include an ID 301, an element list 302, and a basic configuration 303. The element list 302 is a field for storing a list of IDs (ID 201) of elements implemented in the IT system. The basic configuration 303 is a field for storing the reference architecture of the IT system. Note that the basic configuration 303 may also store the main purpose, domain, configuration diagram, etc. of the IT system.

[0038] The elements are managed in association with the non-functional requirements in the element DB 114. Therefore, it is possible to know which non-functional requirement elements are implemented in the IT system from the history table 300. It is also possible to know the details of the architecture of the IT system in which the non-functional requirement elements are implemented.

[0039] The adoption / rejection result table 310 stores entries (implementation decision history) for managing the results of a user's decision on whether to adopt or reject the implementation of an element. The entries include an ID 311, a history ID 312, an element ID 313, an adoption type 314, cost information 315, and a reason 316. The cost information 315 is a field for storing information related to the cost that was focused on when deciding whether to implement an element. For example, the cost type and a judgment formula are stored. The reason 316 is a field for storing the reason why the user did not adopt the implementation of an element. The reason may be selectable in a pull-down menu, or may be freely written by the user.

[0040] The criteria for determining whether or not to adopt an element can be understood from the adoption result table 310. By managing the implementation decision history in association with the implementation history, the priority of implementation of non-functional requirements in any IT system can be understood.

[0041] FIG. 4 is a flowchart illustrating an example of processing executed by the architecture design support system 100 according to the first embodiment.

[0042] When the architecture design support system 100 receives a design request including non-functional requirements from a user, it starts the process described below. The user simply inputs the items and targets as information specifying the non-functional requirements. The requirement level may also be included. The requirement level may be specified as a numerical value or a range.

[0043] The combination determination unit 111 refers to the element DB 114 and identifies an element that corresponds to the specified non-functional requirement (step S101).

[0044] The combination determination unit 111 generates combinations of all the specified non-functional requirement elements (step S102).

[0045] The combination determination unit 111 checks the consistency of each combination of elements and identifies combinations of elements that can be implemented (step S103).

[0046] For example, assume that there are elements 1 and 2 corresponding to non-functional requirement α, and element 3 corresponding to non-functional requirement β. Element 1 targets service A, and elements 2 and 3 target service B. In this case, the combinations of elements 1 and 3, and the combination of elements 2 and 3, are possible combinations that simultaneously satisfy non-functional requirements α and β. However, combining element 1, which targets service A, with element 3, which targets service B, is not suitable for implementation in an IT system. Therefore, the combination determination unit 111 deletes the combination of element 1 and element 3. The basic configuration of the IT system may be used as information for identifying combinations of elements that can be implemented.

[0047] The verification unit 112 calculates the cost of each combination of elements (step S104). For example, the following costs may be considered:

[0048] (Pattern 1) When calculating the cost based on the amount required for implementation, the verification unit 112 calculates the cost based on fee information provided by the cloud vendor. Alternatively, the cost may be calculated based on the difference between the basic information before and after the implementation of the combination of elements.

[0049] (Pattern 2) When calculating the cost based on the man-hours required for implementation, the verification unit 112 calculates the cost based on the number of resources included in the element, the number of variables that need to be defined, etc. The cost can be calculated based on the element or the implementation history of the element.

[0050] (Pattern 3) When calculating the cost of the operation of an implemented IT system, the verification unit 112 calculates the cost based on the management level and service type of the elements, etc. The cost can be calculated based on the elements or the implementation history of the elements.

[0051] The verification unit 112 calculates the cost of the combination of elements by taking into account the total, maximum, minimum, and average costs of the elements included in the combination of elements. Note that the cost may be calculated by taking into account overlapping content of the elements.

[0052] The verification unit 112 determines the priority of the combination of elements based on the cost (step S105). For example, a method of setting the priority in ascending order of cost is conceivable.

[0053] If multiple types of costs are calculated, the priority may be determined based on the total value of the various costs or on an arbitrary cost. The verification unit 112 may also identify a cost of interest based on the history DB 115. The method for determining the priority will be described in detail later.

[0054] The architecture design support system 100 sorts the combinations of elements based on the priority and presents them to the user (step S106).

[0055] The user checks the combinations of elements, determines the cost constraints, and inputs them into the architecture design support system 100. The cost constraints include conditional expressions related to cost or priority, and the number of combinations of elements to be selected.

[0056] When the verification unit 112 acquires the cost constraint condition from the user, it determines whether or not there is a combination of elements that satisfies the cost constraint condition (step S107).

[0057] If there is a combination of elements that satisfies the cost constraint condition, the verification unit 112 outputs the combination of elements (step S108), and then ends the process.

[0058] If there is no combination of elements that satisfies the cost constraint condition, the alternative generator 113 generates a combination of elements that will serve as an alternative (step S109). The number of alternatives may be one or more.

[0059] For example, the alternative generator 113 identifies an element that is implemented less frequently in a certain combination of elements based on the history DB 115, and generates an alternative by changing the requirement level of the element, etc. At this time, the alternative generator 113 calculates the cost of the alternative and determines whether or not the alternative satisfies the cost constraint condition.

[0060] The alternative generator 113 outputs an alternative that satisfies the cost constraint conditions (step S110), and then ends the process.

[0061] In step S107, if there is a combination of elements that satisfies the cost constraint condition and a combination of elements that does not satisfy the cost constraint condition, the alternative generator 113 may proceed to step S109.

[0062] Each process will be specifically described below with reference to FIGS. 5 to 12.

[0063] First, a method for generating a combination of elements will be described with reference to Fig. 5. Fig. 5 is a diagram illustrating an example of a method for identifying elements of non-functional requirements and a method for generating a combination of elements by the architecture design support system 100 according to the first embodiment.

[0064] It is assumed that the architecture design support system 100 has received information specifying the following non-functional requirements (see FIG. 5A).

[0065] (Non-functional requirement 1) Item is fault tolerance, target is database, requirement level is 2 or higher. (Non-functional requirement 2) Item is backup, target is database, requirement level is 2 or higher.

[0066] In step S101, as shown in FIG. 5(B), the combination determination unit 111 refers to the table 200 shown in FIG. 2A and identifies “RDS for Aurora” and “RDS (Multi)” as elements for realizing non-functional requirement 1, and identifies “AWS Backup,” “Lifecycle Manager,” and “RDS (Backup)” as elements for realizing non-functional requirement 2.

[0067] In step S102, the combination determination unit 111 generates combinations of six elements, as shown in FIG. 5(C).

[0068] The target of "RDS for Aurora" and "RDS (Multi)" is RDS, but the target of "Lifecycle Manager" is EC2, and therefore they are different. Therefore, they cannot be implemented simultaneously as elements applied to the same database. Therefore, in step S103, as shown in FIG. 5(D), the combination determination unit 111 deletes combinations of elements including "RDS for Aurora, Lifecycle Manager" and "RDS (Multi), Lifecycle Manager," and outputs combinations of four elements.

[0069] Next, a cost calculation method will be described with reference to Fig. 6. Fig. 6 is a diagram illustrating an example of a cost calculation method by the architecture design support system 100 according to the first embodiment.

[0070] Here, a method for calculating the cost of the element combination "RDS (Multi), RDS (backup)" will be described.

[0071] First, the calculation method of the monetary cost will be described. In this embodiment, it is assumed that the calculation method of the monetary cost for each element is set in advance. For example, the calculation method shown in formula (1) is set for the element RDS(Multi), and the calculation method shown in formula (2) is set for the element RDS(backup).

[0072]

[0073]

[0074] Since the variables in the above cost calculation formulas are different, the verification unit 112 calculates the monetary cost as the sum of the values ​​obtained from formula (1) and formula (2).

[0075] Next, a method for calculating implementation / operation costs will be described. The verification unit 112 can obtain information such as that shown in FIG. 6 from the element RDS(Multi) and element RDS(backup). The verification unit 112 can see that the two elements have the same characteristics, a managed management level, a single service type, and four sub-resources. It can also be seen that the element RDS(Multi) includes two variables, variable 1 and variable 2, as variables necessary for implementation, and that the element RDS(backup) includes three variables, variable 1 and variable 2, as variables necessary for implementation.

[0076] The verification unit 112 compares information obtained from the elements and calculates the cost of simultaneously implementing them. For example, the verification unit 112 calculates the implementation / operation cost based on the management level, service type, number of configurations, and number of variables. In the example shown in FIG. 6 , the service type is single, the number of variable 1 is 3, the number of variable 2 is 1 because the variable is common between the elements, and the number of variable 3 is 0. The number of sub-resources is four because they are common between the configurations, and adding the RDS, which is the common main resource, makes five, making the number of configurations. In addition, the verification unit 112 converts the combination of management levels in the combination of elements into a cost. For example, if the management level of all elements is self-managed, the cost is considered low; if self-managed and managed are mixed, the cost is considered medium; and if the management level of all elements is managed, the cost is considered high.

[0077] Next, a method for determining the priority will be described with reference to FIGS.

[0078] 7, 8, and 9 are flowcharts illustrating an example of a priority determination process executed by the architecture design support system 100 according to the first embodiment. Fig. 10 is a diagram illustrating a specific method for determining priority according to the first embodiment.

[0079] First, the priority determination process of Fig. 7 will be described. For each combination of elements, the verification unit 112 converts the monetary cost into a numerical value representing the ranking, and also converts the implementation / operation cost into a numerical value representing the ranking (step S201). The numerical value conversion method is set in advance. For example, the verification unit 112 outputs the smaller numerical values ​​in ascending order of cost.

[0080] For example, when the costs shown in FIG. 10A are calculated for the combinations of elements shown in FIG. 5, the verification unit 112 converts them into numerical values ​​as shown in FIG. 10B.

[0081] The verification unit 112 calculates a total cost for each combination of elements based on the values ​​calculated from the individual costs (step S202).

[0082] For example, the verification unit 112 may calculate the total cost by adding up the values ​​calculated from the individual costs. Alternatively, the total cost may be calculated as a weighted sum of the values.

[0083] The verification unit 112 determines the priority of the combination of elements based on the total cost (step S203).

[0084] For example, priorities are assigned so that combinations of elements with a small overall cost are displayed preferentially. Note that combinations of elements with the same overall cost may be assigned the same priority, or unique priorities may be assigned based on the results of comparing the individual costs.

[0085] When the total cost is the sum of the numerical values ​​of each cost, in the determination method of Fig. 7, a high priority is assigned to the combination of elements with IDs 3 and 4 in Fig. 5(D), and a low priority is assigned to the combination of elements with IDs 1 and 2 in Fig. 5(D). The combination of elements with a high priority is preferentially presented to the user.

[0086] Next, the method of determining the priority of Fig. 8 will be described. The verification unit 112 determines the priority of a combination of elements based on the reference cost of each combination of elements (step S301). Note that the same priority may be assigned to combinations of elements with the same reference cost, or a unique priority may be assigned based on the comparison result of other costs.

[0087] The reference cost is a cost used to determine the priority, and may be set in advance or may be selectable by the user. Note that there may be multiple reference costs.

[0088] When the number of components is the reference cost, the elements with ID 4, 2, 3, and 1 in FIG. 5D are given higher priority in this order.

[0089] Next, a method for determining the priority will be described with reference to Fig. 9. The verification unit 112 refers to the adoption / rejection result table 310 and identifies the reference cost (step S401).

[0090] For example, the verification unit 112 calculates the frequency of use of various costs based on the cost information 315 of each entry in the adoption / rejection result table 310. The verification unit 112 identifies the most frequently used type of cost as the reference cost.

[0091] The frequency of use may be calculated using only entries with similar elements or basic configurations. Also, there may be multiple reference costs.

[0092] The verification unit 112 determines the priority of the combination of elements based on the reference cost of each combination of elements (step S402). Note that the same priority may be assigned to combinations of elements with the same reference cost, or a unique priority may be assigned based on the comparison result of other costs.

[0093] When the service type is identified as the reference cost, a high priority is assigned to the combination of elements with IDs 1 and 3 in FIG. 5(D), and a low priority is assigned to the combination of elements with IDs 2 and 4 in FIG. 5(D).

[0094] Next, a method for generating an alternative plan will be described with reference to FIGS.

[0095] If a combination of elements that satisfies the cost constraints does not exist, it is possible to generate a combination of elements that satisfies the cost constraints by changing some of the elements in the combination. However, changing non-functional requirements requires knowledge and experience. The architecture design support system 100 of the first embodiment identifies how to change elements using the implementation history of past non-functional requirements and generates alternatives.

[0096] 11A and 11B are flowcharts illustrating an example of a process for generating an alternative plan executed by the architecture design support system 100 according to the first embodiment.

[0097] 11A and 11B, elements are changed based on implementation frequency. First, the alternative generation unit 113 selects a base element combination based on the priority of the element combinations output by the verification unit 112. There may be one or more base element combinations. Here, it is assumed that one base element combination is selected. If multiple base element combinations are selected, the processing described below is executed for each element combination.

[0098] The alternative generator 113 refers to the history table 300 and calculates the implementation frequency of each non-functional requirement corresponding to the combination of base elements (step S501). Here, the implementation frequency of a non-functional requirement represents the number of times an element for realizing the non-functional requirement has been implemented.

[0099] Specifically, the alternative generator 113 identifies elements for realizing the non-functional requirements. The alternative generator 113 calculates the number of entries storing the IDs of the identified elements in the element list 302 as the implementation frequency of the non-functional requirements.

[0100] Alternatively, only entries with similar basic configurations may be searched for. Also, the user may specify non-functional requirements for which the execution frequency is to be calculated.

[0101] The alternative generator 113 determines whether or not there is a non-functional requirement that can be changed, based on the implementation frequency of each non-functional requirement (step S502).

[0102] Specifically, the alternative generator 113 calculates the difference in implementation frequency between the non-functional requirements corresponding to the combination of base elements. If there is a difference in implementation frequency between the non-functional requirements, the alternative generator 113 determines that there is a non-functional requirement that can be changed.

[0103] If there is no changeable non-functional requirement, the alternative generator 113 proceeds to step S512.

[0104] If there are any non-functional requirements that can be changed, the alternative generator 113 selects the non-functional requirements to be changed (step S503). Here, the non-functional requirements are selected in ascending order of implementation frequency. In other words, the non-functional requirements with the lowest implementation record are selected as the non-functional requirements to be changed.

[0105] The alternative generator 113 determines whether the element corresponding to the selected non-functional requirement can be changed (step S504).

[0106] For example, if the cost does not change when the variables or parameters of the element are modified, or if the cost does not change when the element is changed to another element having the same level as the current non-functional requirement or another element having a different level, the selected element is determined to be non-changeable, because changing the element will not satisfy the cost constraint.

[0107] If the element corresponding to the selected non-functional requirement is not changeable, the alternative generator 113 determines whether the implementation frequency of the non-functional requirement is less than a predetermined threshold (step S505), which determines whether the non-functional requirement is rarely implemented in the architecture of the IT system.

[0108] If the implementation frequency of the non-functional requirement is equal to or greater than the predetermined threshold, the alternative generator 113 proceeds to step S507.

[0109] If the implementation frequency of the non-functional requirement is less than a predetermined threshold, the alternative generator 113 assigns a Remove flag to the operation data including the element corresponding to the non-functional requirement and adds it to the alternative candidate stack (step S506).The alternative generator 113 then proceeds to step S507.The Remove flag is a flag indicating an element deletion operation.

[0110] In step S507, the alternative generator 113 determines whether or not there is a selectable element to be changed (step S507).

[0111] If there is no selectable element to be changed, the alternative generator 113 proceeds to step S512.

[0112] If there is a selectable element to be changed, the alternative generator 113 returns to step S503.

[0113] It is to be noted that the processes of steps S505 and S506 do not have to be executed. If the determination result of step S504 is NO, the alternative generator 113 proceeds to step S507.

[0114] In step S504, if the element corresponding to the selected non-functional requirement is changeable, the alternative generator 113 identifies a method for changing the element (step S508).

[0115] Specifically, the alternatives generator 113 extracts modification methods that change costs. The modification methods include modifying variables or parameters of elements or changing elements. If multiple modification methods are extracted, the alternatives generator 113 may select one or any number of modification methods.

[0116] The alternative generator 113 may refer to the implementation history of the selected non-functional requirement and compare the current element with the element in the implementation history to identify a change method.

[0117] The alternative generator 113 determines whether or not the change to the element made by the specified change method will have an effect on other elements (step S509).

[0118] As explained in step S103, changing an element may have an impact, such as making it unable to coexist with other elements. Therefore, the presence or absence of such an impact is confirmed. For example, the alternative generator 113 changes the element according to the identified change method, compares the changed element with other elements, and determines whether or not changes are also required for the other elements. Note that the presence or absence of an impact on the basic configuration may also be taken into consideration.

[0119] If the change to the element does not affect other elements, the alternative generator 113 assigns a Change flag to the operation data that associates the current element with the change method, and adds it to the alternative candidate stack (step S510). The alternative generator 113 then proceeds to step S512. The Change flag is a flag that indicates that the change to the element to be changed has been implemented.

[0120] If the change to an element affects other elements, the alternative generator 113 identifies a change method for the other elements, assigns a Link-Change flag to operation data associating the current element, the other elements, and the change method, and adds the operation data to the alternative candidate stack (step S511). The alternative generator 113 then proceeds to step S512. The Link-Change flag is a flag that indicates the change to the element to be changed and the other elements that will be affected.

[0121] If there is no other method of changing the element, the alternative generator 113 proceeds to step S512. Also, the process of step S511 may be omitted. If step S509 is YES, the alternative generator 113 proceeds to step S512.

[0122] In step S512, the alternative generator 113 determines whether the alternative candidate stack is empty (step S512).

[0123] If the alternative candidate stack is not empty, the alternative generator 113 determines the priority of the operation data to be stored in the alternative candidate stack (step S513).

[0124] Specifically, a high priority is assigned to operation data that realizes a combination of elements that satisfies both cost constraints and non-functional requirements. The prioritization takes into consideration factors such as the cost difference associated with the change, the level of the requirements, and the degree of impact on other elements. The priority may be determined based on one or more factors.

[0125] The alternative generator 113 generates an alternative based on the operation data to which the priority has been assigned and the combination of the base elements (step S514), and then the alternative generator 113 ends the process.

[0126] For example, the alternative generator 113 generates an alternative by modifying elements included in a combination of elements that serves as a base, based on the operation data with the highest priority. Note that the alternative generator 113 may select multiple operation data with higher priority based on the priority, and combine the selected multiple operation data to generate an alternative.

[0127] If the alternative candidate stack is empty, the alternative generator 113 outputs a message notifying the user that an alternative could not be generated (step S515), and then ends the process.

[0128] The alternative generation unit 113 may output a message suggesting the possibility of generating an alternative by adding information about the basic configuration, changing the selection conditions of the non-functional requirements to be changed, etc. The alternative generation unit 113 may also output a message suggesting the possibility of generating an alternative by referring to the implementation history.

[0129] Here, a specific generation of alternatives will be described.

[0130] (Case 1) Assume that the combination of elements with ID 3 in FIG. 5D is the base, "Non-functional Requirement 1" is selected in step S503, and it is determined in step S504 that lowering the requirement level for the element "RDS (Multi)" will reduce the monetary cost. In step S508, the alternative generation unit 113 identifies a modification method for changing the element to "MySQL-MultiAz." This modification method does not affect the other element "AWS Backup" in the base element combination. Therefore, in step S510, the alternative generation unit 113 assigns a "Change" flag to the operation data that associates the element "RDS (Multi)" with the aforementioned modification method, and adds it to the alternative candidate stack.

[0131] (Case 2) Assume that the combination of elements with ID 4 in FIG. 5(D) is the base, "Non-functional Requirement 1" is selected in step S503, and it is determined in step S504 that lowering the requirement level for the element "RDS (Multi)" will reduce the monetary cost. In step S508, the alternative generator 113 identifies a modification method for changing the element to "MySQL-MultiAz." This modification method affects another element, "RDS (backup)," in the base element combination, so a modification to the element "RDS (backup)" is required. In this case, it is assumed that a modification method for changing the element "RDS (backup)" to "Lifecycle Manager" is identified. In this case, in step S510, the alternative generation unit 113 assigns a Link-Change flag to the operation data associated with the element "RDS (Multi)", the element "RDS (backup)", and the above-mentioned change method, and adds them to the alternative candidate stack.

[0132] When priorities are assigned based on requirement levels, a high priority is assigned to the operation data of case 1, and a low priority is assigned to the operation data of case 2.

[0133] Here, an example of a method for generating an alternative when constraints based on implementation / operation costs are not satisfied will be described. Assume that the combination of elements with ID 1 in FIG. 5D is the base, and "non-functional requirement 1" was selected in step S503. To reduce the operational cost of the element "RDS for Aurora," the sub-requirement level or management level must be increased. Assume that it has been determined that changing the element to "Aurora Serverless" will reduce the implementation / operation costs. In step S508, the alternative generation unit 113 identifies a change method for changing the element to "Aurora Serverless." This change method does not affect the other element, "AWS Backup," in the base element combination. Therefore, in step S510, the alternative generation unit 113 assigns a "Change" flag to the operation data that associates the element "RDS for Aurora" with the aforementioned change method, and adds it to the alternative candidate stack.

[0134] 12A and 12B are flowcharts illustrating an example of a process for generating an alternative plan executed by the architecture design support system 100 according to the first embodiment.

[0135] 12A and 12B, elements are changed based on the level of the non-functional requirements. First, the alternative generation unit 113 selects a base combination of elements based on the priority of the element combinations output by the verification unit 112. There may be one or more base combinations of elements. Here, it is assumed that one base combination of elements is selected. When a base combination of elements is selected, the processing described below is executed for each base combination of elements.

[0136] The alternative generator 113 refers to the history table 300 and calculates the level at which the non-functional requirement corresponding to the combination of base elements was implemented in the past (step S601). Here, the level of the non-functional requirement is the requirement level or the management level.

[0137] Specifically, the alternative generator 113 refers to the history table 300 to obtain the level of each component. The alternative generator 113 refers to the component DB 114 to calculate the level of a non-functional requirement using the levels of elements that realize the same non-functional requirement. The level of a non-functional requirement may be the most frequently occurring level or a range of levels.

[0138] Alternatively, only entries with similar basic configurations may be searched for. Also, the user may specify non-functional requirements for which the performance level is to be calculated.

[0139] The alternative generator 113 determines whether or not there is a non-functional requirement that can be changed, based on the level of each non-functional requirement (step S602).

[0140] Specifically, the alternative generator 113 determines whether the level of the non-functional requirement specified by the user is different from the calculated level of the non-functional requirement. If the two levels are different, the non-functional requirement is determined to be a changeable non-functional requirement.

[0141] For example, when generating alternatives that satisfy cost constraints related to monetary cost, if the level specified by the user is higher than the calculated level, changing the level may reduce the monetary cost. Therefore, non-functional requirements with different levels as described above are mutable non-functional requirements.

[0142] For example, when generating alternatives that satisfy cost constraints related to implementation / operation costs, if the level specified by the user is lower than the calculated level, changing the level may reduce the implementation / operation costs. Therefore, non-functional requirements with different levels as described above are mutable non-functional requirements.

[0143] If there is no changeable non-functional requirement, the alternative generator 113 proceeds to step S610.

[0144] If there are any non-functional requirements that can be changed, the alternative generator 113 selects the non-functional requirements to be changed (step S603). Here, the non-functional requirements are selected in descending order of level difference. That is, the non-functional requirements whose level specified by the user is excessive or insufficient compared to the past implementation history are selected as the non-functional requirements to be changed.

[0145] The alternative generator 113 determines whether the element corresponding to the selected non-functional requirement can be changed (step S604).

[0146] For example, if the cost does not change when the variable or parameter of the element is modified, or if the cost does not change when the element is changed to another element having the same level as the current non-functional requirement or another element having a different level, the alternative generator 113 determines that the selected element is not changeable, because changing the element will not satisfy the cost constraint.

[0147] If the element corresponding to the selected non-functional requirement is not changeable, the alternative generator 113 determines whether or not the determination of all elements to be changed has been completed (step S605).

[0148] If the determination of all elements to be changed has not been completed, the alternative generator 113 returns to step S603.

[0149] If the determination of all elements to be changed has been completed, the alternative generator 113 proceeds to step S610.

[0150] In step S604, if the element corresponding to the selected non-functional requirement is changeable, the alternative generator 113 identifies a method for changing the element (step S606). The process of step S606 is the same as the process of step S508.

[0151] The alternative generator 113 determines whether or not the change to the element by the specified change method will have an effect on other elements (step S607). The process of step S607 is the same as the process of step S509.

[0152] If the change to the element does not affect other elements, the alternative generator 113 assigns a Change flag to the operation data that associates the current element with the change method, and adds it to the alternative candidate stack (step S608). The alternative generator 113 then proceeds to step S610. The process of step S608 is the same as the process of step S510.

[0153] If the change to an element affects other elements, the alternative generator 113 identifies a method for changing the other elements, assigns a Link-Change flag to the operation data that associates the current element, the other elements, and the change method, and adds the operation data to the alternative candidate stack (step S609).Then, the alternative generator 113 proceeds to step S610. The processing in step S609 is the same as the processing in step S511.

[0154] In step S610, the alternative generator 113 determines whether the alternative candidate stack is empty (step S610). The process of step S610 is the same as the process of step S512.

[0155] If the alternative candidate stack is not empty, the alternative generator 113 determines the priority of the operation data to be stored in the alternative candidate stack (step S611). The process of step S611 is the same as the process of step S513.

[0156] The alternative generator 113 generates an alternative based on the prioritized operation data and the combination of base elements (step S612). The alternative generator 113 then terminates the process. The process of step S612 is the same as the process of step S514.

[0157] If the alternative candidate stack is empty in step S610, the alternative generator 113 outputs a message notifying that an alternative could not be generated (step S613). The alternative generator 113 then terminates the process. The process in step S613 is the same as the process in step S515.

[0158] Here, a specific generation of alternatives will be described.

[0159] (Case 1) Assume that the combination of elements with ID 3 in Figure 5(D) is the base, and "non-functional requirement 2" is selected in step S603. If the element is changed to "AWS Backup" in step S604, the combination of elements after the change will be the same as the combination of elements with ID 4 in Figure 5(D). Therefore, the determination result in step S604 will be NO.

[0160] (Case 2) Assume that the combination of elements with ID 4 in FIG. 5(D) is the base, and that "non-functional requirement 2" was selected in step S603. Assume that it was determined in step S604 that modifying the parameters of the element "RDS (backup)" would reduce the monetary cost. In step S606, the alternative generator 113 identifies a modification method for modifying the parameters of the element "RDS (backup)." Modifying the parameters of the element "RDS (backup)" does not affect other elements. Therefore, the alternative generator 113 assigns a Change flag to the operation data that associates the element "RDS (backup)" with the aforementioned modification method, and adds it to the alternative candidate stack.

[0161] The architecture design support system 100 of the first embodiment determines a recommended order of element combinations based on cost and presents the order to the user. This allows the user to understand which element combinations should be adopted with priority. Furthermore, if there is no element combination that satisfies the cost constraint conditions, the architecture design support system 100 of the first embodiment generates an alternative based on the history. This makes it possible to efficiently support changes and decisions on the architecture design. Since element changes are identified based on the history, the history can be presented as evidence data.

[0162] The configuration of the architecture design support system 100 of the second embodiment is the same as that of the first embodiment. The architecture design support system 100 of the second embodiment accepts input of cost constraint conditions along with non-functional requirements. In this case, the architecture design support system 100 omits the processing of step S106. The other processing is the same as that of the first embodiment.

[0163] By accepting the cost constraint conditions in advance, the combination of elements and verification of the cost constraint conditions can be performed automatically.

[0164] The architecture design support system 100 of the second embodiment can obtain the same effects as those of the first embodiment. Furthermore, the architecture design support system 100 of the second embodiment can quickly verify cost constraints and generate alternatives.

[0165] The third embodiment differs from the first embodiment in that it presents a combination of elements that satisfy implementation constraints. The third embodiment will be described below, focusing on the differences from the first embodiment.

[0166] The configuration of the architecture design support system 100 of the third embodiment is the same as that of the first embodiment. The processing executed by the architecture design support system 100 of the third embodiment is partially different from that of the first embodiment.

[0167] FIG. 13 is a flowchart illustrating an example of processing executed by the architecture design support system 100 according to the third embodiment.

[0168] When the architecture design support system 100 receives a design request including non-functional requirements from a user, it starts the process described below.

[0169] The combination determination unit 111 refers to the element DB 114 to identify an element that corresponds to the specified non-functional requirement (step S701). The process of step S701 is the same as the process of step S101.

[0170] The combination determination unit 111 generates combinations of all the specified non-functional requirement elements (step S702). The process of step S702 is the same as the process of step S102.

[0171] The verification unit 112 determines whether or not each combination of elements satisfies the implementation constraints (step S703).

[0172] The implementation constraints include constraints on the relevance of non-functional requirements, and constraints on the parameters and structural information of elements. For example, they include conditions on the magnitude relationship of the requirement levels of non-functional requirements. Constraints on the basic configuration may also be included.

[0173] Furthermore, the implementation constraint may be a constraint regarding a data storage location, etc. If such a constraint is set, it is determined that a combination of elements including RDS(Multi) does not satisfy the implementation constraint.

[0174] The verification unit 112 determines the priority of the combination of elements based on the determination result (step S704).

[0175] For example, the verification unit 112 assigns a high priority to a combination of elements that satisfies the implementation constraints, and assigns a low priority to a combination of elements that does not satisfy the implementation constraints.

[0176] The verification unit 112 determines whether or not there is a combination of elements that satisfies the implementation constraints (step S705).

[0177] If there is a combination of elements that satisfies the implementation constraints, the verification unit 112 outputs the combination of elements (step S706), and then ends the process.

[0178] If there is no combination of elements that satisfies the implementation constraints, the alternative generator 113 generates an alternative (step S707).

[0179] The alternative generator 113 outputs the alternative (step S708), and then ends the process.

[0180] If it is determined in step S705 that there is a combination of elements that satisfies the implementation constraints and an element that does not satisfy the implementation constraints, the verifying unit 112 may proceed to step S707.

[0181] The architecture design support system 100 may present the determination result of step S703 to the user. At this time, it may present the parts that do not satisfy the implementation constraints, etc. It may also present the possibility of satisfying the implementation constraints by changing elements.

[0182] FIG. 14 is a flowchart illustrating an example of a process for generating an alternative plan executed by the architecture design support system 100 according to the third embodiment.

[0183] The following process is performed on combinations of elements that do not satisfy the implementation constraints.

[0184] The alternative generator 113 refers to the history table 300 and analyzes the implementation tendency of the non-functional requirements corresponding to the elements that do not satisfy the implementation constraints (step S801). The implementation tendency of the non-functional requirements is, for example, the elements that are adopted or the requirement level that is adopted.

[0185] If the implementation constraints regarding the relationships between multiple non-functional requirements are not satisfied, the alternative generator 113 may analyze the implementation tendency of one non-functional requirement or may analyze the implementation tendency of multiple non-functional requirements. If the implementation tendency is unknown, the alternative generator 113 proceeds to step S806.

[0186] The alternative generator 113 identifies a change method based on the analysis result (step S802). For example, a change method that makes the requirement level of the non-functional requirement the same as the previous requirement level can be considered.

[0187] The processing from step S803 to step S809 is the same as the processing from step S509 to step S515.

[0188] Here, a specific generation of alternatives will be described.

[0189] Assume that the following non-functional requirement 2' and the following non-functional requirement 3 are specified. In addition, the implementation constraint is that the requirement level of the non-functional requirement related to data recovery must be equal to or lower than the requirement level of the non-functional requirement related to backup. This indicates that the requirements for data recovery related to operations will not be met unless the scope of application of backup is wider than the scope of application of data recovery during operations.

[0190] (Non-functional requirement 2') Item is backup, target is database, requirement level is 1. (Non-functional requirement 3) Item is data recovery related to operations, target is database, requirement level is 2 or higher.

[0191] For a combination of requirements where non-functional requirement 2 has a requirement level of 1 and non-functional requirement 3 has a requirement level of 2, the following alternatives are generated:

[0192] In step S801, it is assumed that an implementation tendency in which the requirement levels of non-functional requirement 2 and non-functional requirement 3 are the same is identified. In this case, in step S802, the alternative generator 113 identifies a change method for changing the requirement level of non-functional requirement 2 to 2. If it does not affect other elements, the alternative generator 113 adds the operation data with a Change flag attached to the alternative candidate stack.

[0193] The architecture design support system 100 of the third embodiment determines a recommended order of element combinations based on the degree of conformance with implementation / operation constraints and presents the order to the user. This allows the user to easily understand the element combinations that should be adopted with priority. Furthermore, if there is no element combination that satisfies the implementation constraints, the architecture design support system 100 of the third embodiment generates an alternative based on the history. This makes it possible to efficiently support changes and decisions in the architecture design. Since element changes are identified based on the history, the history can be presented as evidence data.

[0194] It is also possible to combine Example 1 and Example 3. For example, the architecture design support system 100 executes the process of step S703 after step S103, and calculates the cost based on the cost constraints and the implementation constraints in step S104.

[0195] The architecture design support system 100 of the fourth embodiment differs from that of the first embodiment in that it accumulates feedback on the presented architecture. The fourth embodiment will be described below, focusing on the differences from the first embodiment.

[0196] FIG. 15 is a diagram illustrating an example of the configuration of an architecture design support system 100 according to the fourth embodiment.

[0197] The architecture design support system 100 of the fourth embodiment differs from the first embodiment in that it includes a feedback acquisition unit 151 .

[0198] The feedback acquisition unit 151 acquires, as feedback, the implementation results using the output element combinations and alternatives. The feedback is accumulated in the history DB 115.

[0199] The architecture design support system 100 of the fourth embodiment has the same effects as those of the first embodiment. Furthermore, by accumulating feedback on the output element combinations and alternatives, alternatives can be generated with higher accuracy.

[0200] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments are provided to explain the present invention in detail, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

[0201] Furthermore, some or all of the above-described configurations, functions, processing units, processing means, etc. may be implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, solid-state drives (SSDs), optical disks, magneto-optical disks, CD-Rs, magnetic tape, non-volatile memory cards, and ROMs.

[0202] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of programming or scripting languages, such as assembler, C / C++, perl, Shell, PHP, Python, and Java.

[0203] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or the storage medium.

[0204] In the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All components may be interconnected.

Claims

1. A computer system for supporting the design of IT system architecture, comprising: an element database storing data associating non-functional requirements with elements that are design information for implementing the non-functional requirements; and a history database storing the implementation history of the non-functional requirements in the past; obtaining information on the non-functional requirements to be implemented in an IT system realized by a base architecture; generating multiple combinations of the elements for implementing the non-functional requirements by referring to the element database; calculating an evaluation index used to determine a recommendation order for the multiple combinations of elements; assigning a priority representing a recommendation order for the multiple combinations of elements based on the evaluation index; determining whether or not there is a combination of elements that satisfies a constraint condition; if there is no combination of elements that satisfies the constraint condition, analyzing the implementation history to identify a method of changing at least one of the elements included in the combination of elements; generating an alternative by modifying the combination of elements based on the identified change method; and outputting at least one of the combinations of elements sorted based on the priority and the alternatives.

2. A computer system as described in claim 1, characterized in that by analyzing the implementation history, elements that have little implementation history or elements that satisfy excess or deficiency of requirements compared to past implementation history are identified as modifiable elements, and a method for changing the modifiable elements is identified.

3. A computer system as described in claim 2, characterized in that by analyzing the implementation history, an implementation trend of the non-functional requirements is identified, and a method of changing the elements included in the combination of elements is identified based on the implementation trend of the non-functional requirements.

4. A computer system as described in claim 2, characterized in that the evaluation index is at least one of monetary cost, implementation cost, and operation cost, and the constraint is a constraint related to at least one of the monetary cost, implementation cost, and operation cost.

5. A computer system according to claim 2, wherein the constraints include implementation-related constraints, and the evaluation index is a numerical value representing the degree of conformance of the constraints.

6. A computer system as described in claim 2, wherein the history database stores implementation decision history regarding whether or not the user has adopted the non-functional requirements in the past, and the implementation decision history includes the elements, whether or not the elements can be implemented, and the type of evaluation index that serves as a criterion for deciding whether or not to implement the elements, and the computer system calculates multiple types of the evaluation index, identifies the type of evaluation index to be used for deciding whether or not to implement the non-functional requirements based on the implementation decision history, and assigns the priority based on the identified type of evaluation index.

7. A computer system according to claim 6, characterized in that the implementation results using the output combination of elements and the alternatives are obtained as feedback, and the obtained feedback is stored as the implementation history or the implementation decision history.

8. A method for supporting the architecture design of an IT system executed by a computer system, wherein the computer system holds an element database storing data associating non-functional requirements with elements that are design information for implementing the non-functional requirements, and a history database storing a history of past implementations of the non-functional requirements, the method for supporting the architecture design of an IT system comprising: a first step in which the computer system acquires information on the non-functional requirements to be implemented in an IT system realized by a base architecture; a second step in which the computer system refers to the element database to generate a plurality of combinations of the elements for implementing the non-functional requirements; a third step in which the computer system calculates an evaluation index used to determine a recommendation order for the combinations of the plurality of elements; a fourth step in which the computer system assigns priorities representing the recommendation order for the combinations of the plurality of elements based on the evaluation index; and a fifth step in which the computer system determines whether or not there is a combination of the elements that satisfies a constraint condition. A method for supporting architecture design of an IT system, comprising: a sixth step in which, if there is no combination of elements that satisfies the constraints, the computer system identifies a method of changing at least one of the elements included in the combination of elements by analyzing the implementation history; a seventh step in which the computer system generates an alternative by modifying the combination of elements based on the identified method of changing; and an eighth step in which the computer system outputs at least one of the combination of elements and the alternatives sorted based on the priority.

9. A method for supporting architecture design of an IT system as described in claim 8, wherein the sixth step includes: a step in which the computer system analyzes the implementation history to identify, as modifiable elements, elements that have been implemented in little time or elements that satisfy an excess or deficiency of requirements compared to past implementation history; and a step in which the computer system identifies a method of changing the modifiable elements.

10. A method for supporting IT system architecture design as described in claim 9, wherein the sixth step includes: a step in which the computer system identifies an implementation trend of the non-functional requirements by analyzing the implementation history; and a step in which the computer system identifies a method of changing the elements included in the combination of elements based on the implementation trend of the non-functional requirements.

11. A method for supporting architecture design of an IT system as described in claim 9, characterized in that the evaluation index is at least one of monetary cost, implementation cost, and operation cost, and the constraint is a constraint related to at least one of the monetary cost, implementation cost, and operation cost.

12. A method for supporting architecture design of an IT system as described in claim 9, characterized in that the constraints include implementation-related constraints, and the evaluation index is a numerical value representing the degree of conformity with the constraints.

13. A method for supporting architecture design of an IT system as described in claim 9, wherein the history database stores implementation decision history regarding whether or not a user has adopted the non-functional requirements in the past, the implementation decision history including the elements, whether or not the elements can be implemented, and the type of evaluation index that serves as a criterion for determining whether or not to implement the elements, the third step including a step in which the computer system calculates multiple types of the evaluation index, and the fourth step including a step in which the computer system identifies the type of evaluation index to be used for determining whether or not to implement the non-functional requirements based on the implementation decision history, and a step in which the computer system assigns the priority based on the identified type of evaluation index.

14. A method for supporting the architecture design of an IT system as described in claim 13, comprising the steps of: said computer system acquiring, as feedback, implementation results utilizing the output combination of elements and said alternative plans; and said computer system accumulating the acquired feedback as said implementation history or said implementation decision history.

Citation Information

Patent Citations

  • System development support device and system development support method

    JP2014071775A

  • Constructing and enhancing a deployment pattern

    US20180165385A1

  • Software selection system and method therefor

    WO2016151865A1