Computer system and support method of architecture design of it system

The system addresses the inefficiencies in IT system architecture design by using databases to rank and generate cost-effective alternatives for non-functional requirements, ensuring that user requirements are met through a systematic and informed approach.

JP2024163490APending Publication Date: 2024-11-22HITACHI LTD

Patent Information

Application Number
JP2023079130
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

Existing IT system architecture design methods struggle to efficiently satisfy user requirements, particularly non-functional requirements, due to the lack of cost consideration and unclear criteria for altering design alternatives, especially when sufficient development ability is lacking.

Method used

A computer system that supports IT system architecture design by utilizing an element database and historical database to generate and rank combinations of elements based on non-functional requirements, calculating evaluation indices, and generating alternatives when necessary, while considering cost constraints.

Benefits of technology

Enables the creation of appropriate IT system architectures that meet user requirements by prioritizing cost-effective combinations and providing rationale for design changes, enhancing the efficiency and effectiveness of architectural design processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024163490000001_ABST
    Figure 2024163490000001_ABST
Patent Text Reader

Abstract

To support architecture design of an IT system.SOLUTION: A computer system holds an element database which manages an element which is design information for mounting a non-functional requirement, and a history database which stores a mounting history of the past non-functional requirement. The computer system acquires information on the non-functional requirement mounted in an IT system realized by architecture as a base, generates a plurality of combinations of elements by referring to the element database, and assigns a priority showing recommendation order of the plurality of combinations of elements, to the plurality of combinations of elements. When the combination of the element satisfying a constraint condition does not exist, an alternative is generated by using the mounting history. The computer system outputs at least one of the combination of elements sorted on the basis of the priority and the alternative.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a system for supporting architecture design. [Background technology]

[0002] In the development of an IT system, the design of the IT system architecture plays an important role in converting the requirements that users expect from the IT system into the structure and format of a computer and forming the foundation of the IT system. In this specification, the architecture of an IT system means information that expresses the components of the IT system and the connections between the components in a concrete format.

[0003] 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 laborious. In response to this, cloud vendors provide reference architectures that correspond to the domain and purpose of the IT system.

[0004] A reference architecture is created based on frequently occurring configurations in a domain or best practices in architecture design, and is composed of general services and minimum functions to achieve the purpose of an IT system.

[0005] Designers can efficiently design the architecture of an IT system by modifying a reference architecture corresponding to a similar domain or purpose in response to a user request of the IT system.

[0006] User requirements are generally classified into functional requirements 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 the architecture to satisfy user requirements while considering the relationships and influences between non-functional requirements. Therefore, a wide range of knowledge and experience is also required when designing the architecture of an IT system using a reference architecture.

[0007] Therefore, in the conventional technology, if a designer does not have sufficient development capabilities, it is difficult to design an IT system architecture that satisfies user requirements. [Prior art documents] [Patent documents]

[0008] [Patent Document 1] JP 2016-110325 A [Non-patent literature]

[0009] [Non-Patent Document 1] Information-technology Promotion Agency, "Non-functional requirement grade," [online], April 2018, [Retrieved December 27, 2022], Internet<URL:https: / / www.ipa.go.jp / sec / softwareengineering / std / ent03-b.html> Summary of the Invention [Problem to be solved by the invention]

[0010] To solve 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 specified in a first table, and if a plurality of design information is specified for any of the requirements as a result of the specification, a suitability ranking of a combination of each of the plurality of design information and the design information specified for the other requirements is referenced in a second table to specify design information that results in a combination with a higher suitability ranking, and the design information specified for each of the plurality of requirements is output to a specified device."

[0011] 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 issues. One issue is that the ranking does not take into consideration the cost of implementing the IT system architecture. Another issue is that the change criteria for the generated alternative plan when there is no appropriate combination of design information is not clear.

[0012] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a system and method for prioritizing 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. [Means for solving the problem]

[0013] A representative example of the invention disclosed in the present application is as follows: That is, a computer system for supporting the design of an IT system architecture 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 implementation of the non-functional requirements in the past, acquires information on the non-functional requirements to be implemented in an IT system realized by a base architecture, generates a plurality of combinations of the elements for implementing the non-functional requirements by referring to the element database, calculates an evaluation index used to determine a recommendation order for the plurality of combinations of the elements, assigns a priority indicating a recommendation order for the plurality of combinations of the elements based on the evaluation index, determines whether or not there is a combination of the elements that satisfies a constraint condition, and if there is no combination of the elements that satisfies the constraint condition, identifies a method of changing at least one of the elements included in the combination of the elements by analyzing the implementation history, generates an alternative by modifying the combination of the elements based on the identified change method, and outputs at least one of the combination of the elements and the alternative sorted based on the priority. Effect of the Invention

[0014] 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. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 illustrates an example of a configuration of an architecture design support system according to a first embodiment. [Figure 2A] FIG. 2 is a diagram illustrating an example of a data structure of an element DB according to the first embodiment. [Figure 2B] FIG. 2 is a diagram illustrating an example of a data structure of an element DB according to the first embodiment. [Figure 3A] FIG. 2 is a diagram illustrating an example of a data structure of a history DB according to the first embodiment. [Figure 3B]FIG. 2 is a diagram illustrating an example of a data structure of a history DB according to the first embodiment. [Figure 4] 1 is a flowchart illustrating an example of a process executed by the architecture design support system according to the first embodiment. [Diagram 5] 1 is a diagram for explaining 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 of the first embodiment. FIG. [Figure 6] FIG. 2 is a diagram for explaining an example of a cost calculation method by the architecture design support system of the first embodiment. [Figure 7] 11 is a flowchart illustrating an example of a priority determination process executed by the architecture design support system according to the first embodiment. [Figure 8] 11 is a flowchart illustrating an example of a priority determination process executed by the architecture design support system according to the first embodiment. [Figure 9] 11 is a flowchart illustrating an example of a priority determination process executed by the architecture design support system according to the first embodiment. [Figure 10] FIG. 11 is a diagram illustrating a specific method for determining a priority in the first embodiment. [Figure 11A] 11 is a flowchart illustrating an example of an alternative generation process executed by the architecture design support system according to the first embodiment. [Figure 11B] 11 is a flowchart illustrating an example of an alternative generation process executed by the architecture design support system according to the first embodiment. [Figure 12A] 11 is a flowchart illustrating an example of an alternative generation process executed by the architecture design support system according to the first embodiment. [Figure 12B] 11 is a flowchart illustrating an example of an alternative generation process executed by the architecture design support system according to the first embodiment. [Figure 13] 13 is a flowchart illustrating an example of an alternative plan generation process executed by the architecture design support system according to the third embodiment. [Figure 14]13 is a flowchart illustrating an example of a process executed by the architecture design support system according to the third embodiment. [Figure 15] FIG. 13 illustrates an example of a configuration of an architecture design support system according to a fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] Hereinafter, an embodiment of the present invention will be described with reference to the accompanying drawings. However, the present invention should not be interpreted as being limited to the description of the embodiment shown below. It will be easily understood by those skilled in the art that the specific configuration can be changed without departing from the concept or purpose of the present invention.

[0017] In the configurations of the invention described below, the same or similar configurations or functions are given the same reference numerals, and duplicated explanations are omitted.

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

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

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

[0021] In this specification, the architecture of an IT system is considered to be information composed of elements that define the type of service, the connection between services, the connection of 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, etc.

[0022] The architecture design support system 100 includes a combination determination unit 111, a verification unit 112, and an alternative plan generation unit 113, and also holds 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.

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

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

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

[0026] The verification unit 112 calculates the cost, which is an evaluation index based on the viewpoints of development, implementation, operation, etc., for the combination of elements determined by the combination determination unit 111, and determines the priority for determining the recommendation order (application order) of the combination of elements based on the cost. The cost is, for example, the cost required for introducing and maintaining the IT system, the man-hours required for implementation, the management level of the service in the IT system, etc.

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

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

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

[0030] 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 items and targets of the non-functional requirements shown in the non-functional requirement grade table in Non-Patent Document 1. In addition, the requirement level is defined as a numerical value that relatively indicates the range of non-functional requirements that each element can handle. The table 200 stores entries each consisting of an ID 201, an item 202, a target 203, a requirement level 204, and an element 205.

[0031] For example, it shows that the element that realizes the "non-functional requirement related to fault tolerance of requirement level 3 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 are in a one-to-one relationship.

[0032] The element 205 stores data 250 having a data structure as shown in FIG. 2B, for example. The data 250 includes information required to realize the non-functional requirements. For example, the data 250 includes names 251 of resources that realize the non-functional requirements, codes 252 that represent the structures, parameters, and settings of the resources, and variables 253 related to costs. Note that the data 250 shown in FIG. 2B is an example and is not limited thereto. For example, the data may include a detailed structure between resources as a main resource and a sub-resource, and may include the importance and setting method of parameters.

[0033] 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.

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

[0035] The history DB 115 stores the implementation history of the 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 the non-functional requirements.

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

[0037] The elements are managed in association with the non-functional requirements in the element DB 114. Therefore, it is possible to know which elements of the non-functional requirements 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 elements of the non-functional requirements are implemented.

[0038] The adoption / rejection result table 310 stores entries (implementation decision history) for managing the results of a user's decision on whether to adopt 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 focused on in deciding whether to implement an element. For example, a 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 selected in a pull-down format, or may be freely written by the user.

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

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

[0041] 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 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 by a numerical value or a range.

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

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

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

[0045] 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, combinations of elements 1 and 3, and combinations 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.

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

[0047] (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. The cost may also be calculated based on the difference in basic information before and after the implementation of the combination of elements.

[0048] (Pattern 2) When calculating the man-hours required for implementation as the cost, 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.

[0049] (Pattern 3) When calculating the effort required to operate the implemented IT system as the cost, 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.

[0050] The verification unit 112 calculates the total, maximum, minimum, and average cost of each element included in the element combination as the cost of the element combination. Note that the cost may be calculated taking into account overlapping contents of the elements.

[0051] 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.

[0052] In addition, when multiple types of costs are calculated, the priority may be determined based on the total value of each type of cost or an arbitrary cost. Also, the verification unit 112 may specify a cost to be focused on based on the history DB 115. The method of determining the priority will be described in detail later.

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

[0054] The user checks the combinations of elements, determines the cost constraint conditions, and inputs them to the architecture design support system 100. The cost constraint conditions include a conditional expression related to cost or priority, and the number of combinations of elements to be selected.

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

[0056] 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.

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

[0058] 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, etc. of the element. At this time, the alternative generator 113 calculates the cost of the alternative and determines whether or not it satisfies the cost constraint condition.

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

[0060] 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.

[0061] Each process will be specifically described below with reference to FIG. 5 to FIG.

[0062] First, a method for generating a combination of elements will be described with reference to Fig. 5. Fig. 5 is a diagram for explaining 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 of the first embodiment.

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

[0064] (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

[0065] In step S101, as shown in FIG. 5(B), the combination determination unit 111 refers to 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.

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

[0067] The target of "RDS for Aurora" and "RDS(Multi)" is RDS, but the target of "Lifecycle Manager" is EC2, and so the targets 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.

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

[0069] Here, we will explain how to calculate the cost of the element combination "RDS(Multi) and RDS(backup)".

[0070] 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 is set in advance for the element. 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).

[0071]

number

[0072]

number

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

[0074] 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 both of the two elements have the same characteristics, the management level is managed, the service type is standalone, and there are four sub-resources. In addition, it can be seen that the element RDS(Multi) includes two variables, a variable 1 and a variable 2, as variables necessary for implementation, and the element RDS(backup) includes three variables, a variable 1 and a variable 2, as variables necessary for implementation.

[0075] The verification unit 112 compares the information acquired from the elements and calculates the cost of implementing them simultaneously. For example, the verification unit 112 calculates the management level, the service type, the number of configurations, and the number of variables as the implementation / operation cost. In the example shown in FIG. 6, the service type is a single unit, the number of variables 1 is 3, the number of variables 2 is 1 because the variables are common between the elements, and the number of variables 3 is 0. The number of sub-resources is four because they are common between the configurations, and five is the number of configurations including RDS, which is a common main resource. 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 levels of all elements are self-managed, the cost is small, if self-managed and managed are mixed, the cost is medium, and if the management levels of all elements are managed, the cost is large.

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

[0077] 7, 8, and 9 are flowcharts illustrating an example of a priority determination process executed by the architecture design support system 100 of the embodiment 1. Fig. 10 is a diagram showing a specific method of determining the priority in the embodiment 1.

[0078] 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 rank, and also converts the implementation / operation cost into a numerical value representing the rank (step S201). The method of converting the numerical values ​​is preset. For example, the verification unit 112 outputs smaller numerical values ​​in ascending order of cost.

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

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

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

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

[0083] For example, the priority is given so that a combination of elements with a small overall cost is preferentially displayed. The same priority may be given to combinations of elements with the same overall cost, or a unique priority may be given based on a comparison of the individual costs.

[0084] 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 of 3 and 4 in Fig. 5(D), and a low priority is assigned to the combination of elements with IDs of 1 and 2 in Fig. 5(D). The combination of elements with a high priority assigned is presented to the user preferentially.

[0085] Next, the method of determining the priority in Fig. 8 will be described. The verification unit 112 determines the priority of the combination of elements based on the reference cost of each combination of elements (step S301). 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.

[0086] 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.

[0087] When the number of configurations is the reference cost, the elements with the highest priority in FIG. 5(D) are the elements with the ID of 4, the elements with the ID of 2, the elements with the ID of 3, and the elements with the ID of 1.

[0088] Next, a description will be given of a method of determining the priority in Fig. 9. The verification unit 112 refers to the adoption / rejection result table 310 and specifies the reference cost (step S401).

[0089] 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.

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

[0091] The verification unit 112 determines the priority of the combination of elements based on the reference cost of each combination of elements (step S402). 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.

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

[0093] Next, a method for generating alternatives will be described with reference to FIGS.

[0094] If there is no combination of elements that satisfies the cost constraint conditions, a combination of elements that satisfies the cost constraint conditions can be generated 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 non-functional requirements in the past, and generates alternatives.

[0095] 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.

[0096] In the method of generating alternatives shown in Figures 11A and 11B, elements are changed based on implementation frequency. First, the alternative generating unit 113 selects a base combination of elements based on the priority of the element combinations output by the verifying 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 multiple base combinations of elements are selected, the process described below is executed for each combination of elements.

[0097] 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 indicates the number of times an element for realizing the non-functional requirement has been implemented.

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

[0099] Note that only entries with similar basic configurations may be searched for. Also, the user may specify a non-functional requirement for which the execution frequency is to be calculated.

[0100] 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).

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

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

[0103] 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 records are selected as the non-functional requirements to be changed.

[0104] The alternative generator 113 determines whether the element corresponding to the selected non-functional requirement is changeable (step S504).

[0105] 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 selected element is determined to be not changeable, because the cost constraint condition is not satisfied even if the element is changed.

[0106] 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). This is to determine whether the non-functional requirement is unlikely to be implemented in the architecture of the IT system.

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

[0108] 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). After that, the alternative generator 113 proceeds to step S507. The Remove flag is a flag indicating a deletion operation of an element.

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

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

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

[0112] It is not necessary to execute the processes of steps S505 and S506. If the determination result of step S504 is NO, the alternative generator 113 proceeds to step S507.

[0113] 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).

[0114] Specifically, the alternative generator 113 extracts modification methods that change the cost. The modification methods include modifying variables or parameters of the element or changing the element. When multiple modification methods are extracted, the alternative generator 113 may select one or any number of modification methods.

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

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

[0117] As explained in step S103, the change to an element may have an impact such as making it impossible to coexist with other elements. Therefore, the presence or absence of 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 the other elements also require change. Note that the presence or absence of an impact on the basic configuration may also be taken into consideration.

[0118] 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). After that, the alternative generator 113 proceeds to step S512. The Change flag is a flag that indicates the implementation of a change to the element to be changed.

[0119] When the change to an element affects other elements, the alternative generator 113 identifies the change method for 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 it 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 are affected.

[0120] If there is no method of changing other elements, 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.

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

[0122] 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).

[0123] Specifically, a high priority is assigned to operation data that realizes a combination of elements that satisfies the cost constraint conditions and also satisfies the non-functional requirements. The priority is assigned taking into consideration the cost difference associated with the change, the level of the requirements, the degree of impact on other elements, etc. The priority may be determined based on one or more factors.

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

[0125] For example, the alternative generator 113 generates an alternative by modifying elements included in a combination of elements that is 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 generate an alternative by combining the selected multiple operation data.

[0126] If the alternative candidate stack is empty, the alternative generator 113 outputs a message notifying the effect that an alternative could not be generated (step S515), after which the alternative generator 113 ends the process.

[0127] The alternative plan generating unit 113 may output a message suggesting a possibility of generating an alternative plan by adding information on the basic configuration, changing a selection condition of a non-functional requirement to be changed, etc. The alternative plan generating unit 113 may also output a message suggesting a possibility of generating an alternative plan by referring to an implementation history.

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

[0129] (Case 1) Assume that the combination of elements with ID 3 in FIG. 5(D) is the base, "non-functional requirement 1" is selected in step S503, and it is found in step S504 that the monetary cost of the element "RDS(Multi)" can be reduced by lowering the requirement level. In step S508, the alternative generator 113 identifies a change method for changing the element to "MySQL-MultiAz". This change method does not affect the other element "AWS Backup" in the base element combination. Therefore, in step S510, the alternative generator 113 assigns a Change flag to the operation data that associates the element "RDS(Multi)" with the above-mentioned change method, and adds it to the alternative candidate stack.

[0130] (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 found in step S504 that the monetary cost of the element "RDS(Multi)" can be reduced by lowering the requirement level. In step S508, the alternative generator 113 identifies a change method for changing the element to "MySQL-MultiAz". This change method affects another element "RDS(backup)" in the combination of elements that is the base, so the element "RDS(backup)" needs to be changed. Here, it is assumed that a change method for changing the element "RDS(backup)" to "Lifecycle Manager" is identified. In this case, in step S510, the alternative generator 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.

[0131] When prioritizing based on requirement level, 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.

[0132] Here, an example of a method for generating an alternative when constraint conditions based on implementation / operation costs are not satisfied will be described. Assume that the combination of elements with ID 1 in FIG. 5(D) is the base, and "non-functional requirement 1" is selected in step S503. In order to reduce the operation cost of the element "RDS for Aurora", it is necessary to raise the sub-requirement level or management level. Assume that it is found that the implementation / operation cost can be reduced by changing the element to "Aurora Serverless". In step S508, the alternative generation unit 113 identifies a change method for changing the element to "Aurora Serverless". The change method does not affect the other element "AWS Backup" of the base element combination. Therefore, in step S510, the alternative generation unit 113 assigns a Change flag to the operation data associated with the element "RDS for Aurora" and the above-mentioned change method, and adds it to the alternative candidate stack.

[0133] 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.

[0134] In the method of generating alternatives shown in Figures 12A and 12B, elements are changed based on the level of non-functional requirements. First, the alternative generating unit 113 selects a base combination of elements based on the priority of the combination of elements output by the verifying 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 process described below is executed for each combination of elements.

[0135] 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.

[0136] Specifically, the alternative generator 113 refers to the history table 300 and acquires the level of each component. The alternative generator 113 refers to the element DB 114 and calculates 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.

[0137] Note that only entries with similar basic configurations may be searched for. Also, the user may specify a non-functional requirement for which the performance level is to be calculated.

[0138] 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).

[0139] 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.

[0140] For example, when generating alternatives that satisfy cost constraints related to monetary costs, 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.

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

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

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

[0144] The alternative generator 113 determines whether the element corresponding to the selected non-functional requirement is changeable (step S604).

[0145] For example, if the cost does not change with the modification of the variables or parameters of the element, or if the cost does not change with the change 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 the cost constraint condition is not satisfied even if the element is changed.

[0146] 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).

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

[0148] When the determination of all elements to be changed is completed, the alternative generator 113 proceeds to step S610.

[0149] 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.

[0150] 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.

[0151] 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). After that, the alternative generator 113 proceeds to step S610. The process of step S608 is the same as the process of step S510.

[0152] If the change of an element affects other elements, the alternative generator 113 identifies the change method of 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 it to the alternative candidate stack (step S609). After that, the alternative generator 113 proceeds to step S610. The process of step S609 is the same as the process of step S511.

[0153] 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.

[0154] 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.

[0155] 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 S612). After that, the alternative generator 113 ends the process. The process of step S612 is the same as the process of step S514.

[0156] In step S610, if the alternative candidate stack is empty, the alternative generator 113 outputs a message notifying that an alternative could not be generated (step S613). After that, the alternative generator 113 ends the process. The process of step S613 is the same as the process of step S515.

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

[0158] (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 judgment result in step S604 will be NO.

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

[0160] The architecture design support system 100 of the first embodiment determines a recommendation order for element combinations based on cost and presents it to the user. This allows the user to understand the element combinations that should be adopted with priority. Furthermore, when there is no element combination that satisfies the cost constraint condition, 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 in the architecture design. Since element changes are identified based on the history, the history can be presented as evidence data. EXAMPLES

[0161] 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 together with non-functional requirements. In this case, the architecture design support system 100 omits the process of step S106. The other processes are the same as those of the first embodiment.

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

[0163] 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 constraint conditions and generate alternatives. EXAMPLES

[0164] 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.

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

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

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

[0168] 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.

[0169] 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.

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

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

[0172] Furthermore, the implementation constraint may be a constraint on 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.

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

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

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

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

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

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

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

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

[0181] 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.

[0182] The process described below is performed on any combination of elements that does not satisfy the implementation constraints.

[0183] 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 constraint conditions (step S801). The implementation tendency of the non-functional requirements is, for example, the elements to be adopted or the requirement level to be adopted.

[0184] If the implementation constraint condition regarding the association of multiple non-functional requirements is 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.

[0185] The alternative generator 113 identifies a change method based on the analysis result (step S802). For example, a change method for changing the requirement level of the non-functional requirement to the same level as the previous requirement level may be considered.

[0186] The process from step S803 to step S809 is the same as the process from step S509 to step S515.

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

[0188] Assume that the following non-functional requirement 2' and non-functional requirement 3 are specified. In addition, 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 if the scope of application of backup is not wider than the scope of application of data recovery during operation, the requirements for data recovery related to operation will not be met.

[0189] (Non-functional requirement 2') Item is backup, target is database, requirement level is 1 (Non-functional requirement 3) The item is data recovery related to operations, the target is database, and the requirement level is 2 or higher

[0190] 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:

[0191] 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.

[0192] The architecture design support system 100 of the third embodiment determines a recommendation order for element combinations based on the degree of match with implementation / operation constraints, and presents the recommendation order to the user. This allows the user to easily understand the element combinations that should be adopted with priority. Furthermore, when there is no element combination that satisfies the implementation constraint conditions, the architecture design support system 100 of the third embodiment generates an alternative proposal 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.

[0193] It is also possible to combine the embodiment 1 and the embodiment 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 constraint conditions and the implementation constraint conditions in step S104. EXAMPLES

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

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

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

[0197] The feedback acquisition unit 151 acquires the implementation result using the output combination of elements and the alternative plan as feedback. The feedback is accumulated in the history DB 115.

[0198] 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, it is possible to generate alternatives with higher accuracy.

[0199] The present invention is not limited to the above-mentioned embodiment, but includes various modified examples. For example, the above-mentioned embodiment describes the configuration in detail to easily explain the present invention, and the present invention is not necessarily limited to the configuration including all the described configurations. Also, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0200] In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that realizes 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 realizes the functions of the above-mentioned embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, ROMs, etc.

[0201] Furthermore, the program code for realizing the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, Java (registered trademark), etc.

[0202] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed over 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 out and execute the program code stored in the storage means or storage medium.

[0203] In the above-mentioned embodiment, the control lines and information lines are shown as those considered necessary for the explanation, and not all the control lines and information lines are shown in the product. All the components may be connected to each other. [Explanation of symbols]

[0204] 100 Architecture Design Support System 111 Combination decision unit 112 Verification Department 113 Alternative plan generation part 114 Element DB 115 History DB 151 Feedback Acquisition Department 200 Tables 250 Data 300 History Table 310 Adoption / rejection result table

Claims

1. A computer system for supporting the design of an IT system architecture, comprising: The method includes: maintaining an element database for storing data associating non-functional requirements with elements that are design information for implementing the non-functional requirements; and a history database for storing a history of implementation of the non-functional requirements in the past; Obtaining information on the non-functional requirements to be implemented in an IT system realized by the base architecture; generating a plurality of combinations of the elements for implementing the non-functional requirements by referring to the element database; Calculating an evaluation index for determining a recommendation order for each combination of the plurality of elements; assigning a priority indicating a recommendation order of the combination of the plurality of elements based on the evaluation index; determining whether there exists a combination of said elements that satisfies a constraint condition; if there is no combination of the elements that satisfies the constraint condition, identifying a method of changing at least one of the elements included in the combination of the elements by analyzing the implementation history; generating alternatives by modifying the combination of elements based on the identified modification methods; A computer system which outputs at least one of the combinations of the elements sorted based on the priority and the alternatives.

2. 2. The computer system of claim 1, By analyzing the implementation history, the element that has a low implementation record or the element that satisfies an excess or deficiency of requirements compared to the past implementation history is identified as the element that can be changed; A computer system for identifying a method for modifying the modifiable element.

3. 3. The computer system of claim 2, Identifying implementation trends of the non-functional requirements by analyzing the implementation history; A computer system comprising: a processor that identifies a method for changing an element included in the combination of elements based on an implementation trend of the non-functional requirements.

4. 3. The computer system of claim 2, The evaluation index is at least one of a monetary cost, an implementation cost, and an operation cost; A computer system, wherein the constraint condition is a constraint condition related to at least one of the monetary cost, the implementation cost, and the operation cost.

5. 3. The computer system of claim 2, The constraints include implementation constraints, A computer system, wherein the evaluation index is a numerical value representing a degree of conformance with the constraint condition.

6. 3. The computer system of claim 2, The history database stores a history of implementation decisions made by users regarding whether or not the non-functional requirements were adopted in the past; the implementation decision history includes the element, whether or not the element can be implemented, and the type of the evaluation index that is a criterion for determining whether or not the element can be implemented; The computer system comprises: Calculating a plurality of types of the evaluation indexes; Identifying the type of evaluation index used to determine the implementation of the non-functional requirement based on the implementation determination history; A computer system comprising: a computer that assigns the priority based on the evaluation index of the identified type.

7. 7. The computer system of claim 6, Obtaining, as feedback, an implementation result using the output combination of the elements and the alternative; The computer system is characterized in that the acquired feedback is accumulated as the implementation history or the implementation judgment history.

8. A method for supporting architecture design of an IT system executed by a computer system, comprising: the computer system holds an element database that stores data associating non-functional requirements with elements that are design information for implementing the non-functional requirements, and a history database that stores a history of past implementations of the non-functional requirements; The method for supporting architecture design of an IT system includes: 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 of the computer system generating a plurality of combinations of the elements for implementing the non-functional requirements by referring to the element database; a third step of the computer system calculating an evaluation index used to determine a recommendation order for each combination of the plurality of elements; a fourth step of the computer system assigning priorities representing recommendation rankings of the combinations of the plurality of elements based on the evaluation index; 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 sixth step of the computer system identifying a method of changing at least one of the elements included in the combination of elements by analyzing the implementation history when the combination of elements that satisfies the constraint condition does not exist; a seventh step in which the computer system generates an alternative by modifying the combination of the elements based on the identified modification method; and an eighth step in which the computer system outputs at least one of the combinations of the elements sorted based on the priority and the alternatives.

9. 9. A method for supporting architecture design of an IT system according to claim 8, comprising: The sixth step includes: a step of the computer system analyzing the implementation history to identify, as a modifiable element, an element that has been implemented in a small number of cases or an element that satisfies an excess or deficiency of requirements compared with a past implementation history; a step of the computer system specifying a method of changing the changeable element.

10. 10. A method for supporting IT system architecture design according to claim 9, comprising: The sixth step includes: The computer system analyzes the implementation history to identify an implementation trend of the non-functional requirements; A method for supporting the architecture design of an IT system, comprising a step in which the computer system identifies a method for changing the elements included in the combination of elements based on the implementation tendency of the non-functional requirements.

11. 10. A method for supporting IT system architecture design according to claim 9, comprising: The evaluation index is at least one of a monetary cost, an implementation cost, and an operation cost; A method for supporting architecture design of an IT system, wherein the constraint is a constraint related to at least one of the monetary cost, the cost required for implementation, and the cost required for operation.

12. 10. A method for supporting IT system architecture design according to claim 9, comprising: The constraints include implementation constraints, A method for supporting architecture design of an IT system, wherein the evaluation index is a numerical value that indicates a degree of conformance with the constraint conditions.

13. 10. A method for supporting IT system architecture design according to claim 9, comprising: The history database stores a history of implementation decisions made by users regarding whether or not the non-functional requirements were adopted in the past; the implementation decision history includes the element, whether or not the element can be implemented, and the type of the evaluation index that is a criterion for determining whether or not the element can be implemented; The third step includes: The computer system includes a step of calculating a plurality of types of the evaluation indexes, The fourth step includes: a step of the computer system identifying a type of the evaluation index used for determining whether or not to implement the non-functional requirement based on the implementation determination history; a step of the computer system assigning the priority based on the evaluation index of the specified type.

14. A method for supporting IT system architecture design according to claim 13, comprising: The computer system acquires, as feedback, an implementation result using the output combination of the elements and the alternative plan; A method for supporting architecture design of an IT system, comprising a step of storing the acquired feedback by the computer system as the implementation history or the implementation decision history.

Citation Information

Patent Citations

  • System design support device and method for system design support

    JP2016110325A

Cited By

  • Architecture proposed device, information processing method and program

    JP2026119962A

  • ARCHITECTURE PROPOSAL DEVICE, INFORMATION PROCESSING METHOD, AND PROGRAM

    JP7678947B1