Demand architecture analysis methods, apparatus, equipment, media, and program products

Abstract

This disclosure provides a requirement architecture analysis method applicable to the field of artificial intelligence technology. The method includes: obtaining the requirement use cases to be analyzed and their corresponding business architectures, the business architectures comprising multiple business modules; calculating the correlation between each pair of business modules to obtain a first correlation coefficient set, the first correlation coefficient set comprising multiple first correlation coefficients; calculating the correlation between the requirement use cases and the business architecture to obtain a second correlation coefficient set, the second correlation coefficient set comprising multiple second correlation coefficients; comparing the first correlation coefficient set with a corresponding first threshold set, and comparing the second correlation coefficient set with a corresponding second threshold set, to identify the business modules exhibiting anomalies in the business architecture. This method can improve the quality of requirement use cases and business architecture models. This disclosure also provides a requirement architecture analysis apparatus, device, medium, and program product.

Description

Technical Field

[0001] This disclosure relates to the field of artificial intelligence, and more specifically to a requirement architecture analysis method, apparatus, device, medium, and program product. Background Technology

[0002] With intensifying market competition, higher demands are being placed on the quality and efficiency of business development. Requirements analysis is a crucial prerequisite for business development, while business architecture is its key support, providing a unified logical language system for both business and development personnel. Business architecture efficiently and intelligently supports requirements analysis, while requirements analysis, in turn, feeds back into the improvement of business architecture—a sequential improvement process. How to leverage technology to collaboratively enhance the efficiency of both is a technical problem that those skilled in the art need to solve. Summary of the Invention

[0003] In view of the above problems, this disclosure provides a method, apparatus, device, medium and program product for improving the efficiency of requirements analysis.

[0004] According to a first aspect of this disclosure, a requirement architecture analysis method is provided, comprising: obtaining requirement use cases to be analyzed and corresponding business architectures, the business architectures including multiple business modules; calculating the correlation between each pair of the multiple business modules to obtain a first correlation coefficient set, wherein the first correlation coefficient set includes multiple first correlation coefficients; calculating the correlation between requirement use cases and business architectures to obtain a second correlation coefficient set, the second correlation coefficient set including multiple second correlation coefficients; comparing the size of the first correlation coefficient set with the corresponding first threshold set, and comparing the size of the second correlation coefficient set with the corresponding second threshold set, to determine the business modules in the business architecture that exhibit anomalies.

[0005] According to embodiments of this disclosure, the method further includes: obtaining a historical requirement use case library; comparing the requirement use cases with the historical requirement use case library to obtain a requirement use case set and a business architecture set, wherein the requirement use case set includes at least one historical requirement use case with a similarity higher than a predetermined threshold, and the business architecture set includes the historical business architecture corresponding to each of the at least one historical requirement use case.

[0006] According to embodiments of this disclosure, calculating the correlation between multiple business modules to obtain a first correlation coefficient set includes: calculating the correlation between multiple business modules and a business architecture set to obtain multiple first sequences, wherein the multiple first sequences correspond one-to-one with the multiple business modules; and calculating the first correlation coefficients between multiple business modules based on the multiple first sequences to obtain a first correlation coefficient set.

[0007] According to embodiments of this disclosure, calculating the correlation between requirement use cases and business architecture to obtain a second set of correlation coefficients includes: extracting the top N keywords by frequency of use in the text content of the requirement use cases, where N is an integer greater than or equal to 1; performing text matching between the top N keywords by frequency of use and the requirement use case set to obtain N second sequences; calculating the correlation between multiple business modules and the requirement use case set to obtain multiple third sequences; and calculating the correlation between each keyword and each business module based on the N second sequences and the multiple third sequences to obtain the second set of correlation coefficients.

[0008] According to embodiments of this disclosure, calculating the correlation between each keyword and each business module based on N second sequences and multiple third sequences to obtain a second set of correlation coefficients includes: calculating the second correlation coefficient between each of the N second sequences and each of the multiple third sequences to obtain a second set of correlation coefficients.

[0009] According to embodiments of this disclosure, comparing the size between a first set of correlation coefficients and a corresponding first set of thresholds, and comparing the size between a second set of correlation coefficients and a corresponding second set of thresholds, to determine the business modules in the business architecture that are abnormal includes: when a first correlation coefficient in the first set of correlation coefficients is less than a corresponding threshold in the first set of thresholds, indicating that the two business modules corresponding to the first correlation coefficient are abnormal; when a second correlation coefficient in the second set of correlation coefficients is less than a corresponding threshold in the second set of thresholds, indicating that the correspondence between the business module corresponding to the second correlation coefficient and the requirement use case is abnormal.

[0010] According to embodiments of this disclosure, the number of requirement use cases to be analyzed is multiple, and the requirement architecture method further includes: performing requirement architecture analysis on multiple requirement use cases respectively to obtain the requirement architecture analysis results of each requirement use case; when the architecture analysis results of multiple requirement use cases are all normal, it is indicated that multiple requirement use cases need to be integrated.

[0011] According to embodiments of this disclosure, it further includes: extracting some business modules from multiple business modules to perform requirement architecture analysis on the some business modules.

[0012] A second aspect of this disclosure provides a requirement architecture analysis apparatus, comprising: an acquisition module for acquiring requirement use cases to be analyzed and the corresponding business architecture of the requirement use cases, the business architecture including multiple business modules; a first calculation module for calculating the correlation between each pair of the multiple business modules to obtain a first correlation coefficient set, wherein the first correlation coefficient set includes multiple first correlation coefficients; a second calculation module for calculating the correlation between the requirement use cases and the business architecture to obtain a second correlation coefficient set, the second correlation coefficient set including multiple second correlation coefficients; and a comparison module for comparing the size of the first correlation coefficient set with the corresponding first threshold set, and comparing the size of the second correlation coefficient set with the corresponding second threshold set, to determine the business modules in the business architecture that exhibit anomalies.

[0013] A third aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the aforementioned requirements architecture analysis method.

[0014] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the aforementioned requirements architecture analysis method.

[0015] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned requirements architecture analysis method. Attached Figure Description

[0016] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 This schematically illustrates a module hierarchy diagram of a business model in a business architecture according to an embodiment of the present disclosure;

[0018] Figure 2 This diagram illustrates an application scenario of the requirements architecture analysis method according to embodiments of the present disclosure.

[0019] Figure 3 A flowchart illustrating a requirement architecture analysis method according to an embodiment of the present disclosure is shown schematically;

[0020] Figure 4 A second flowchart illustrating a requirement architecture analysis method according to an embodiment of the present disclosure is shown schematically.

[0021] Figure 5 A schematic diagram illustrating the structural block diagram of a requirements architecture analysis apparatus according to embodiments of the present disclosure; and

[0022] Figure 6 A block diagram of an electronic device suitable for implementing a requirements architecture analysis method according to an embodiment of the present disclosure is shown schematically. Detailed Implementation

[0023] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0025] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0026] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0027] In the process of enterprise digitalization, business departments typically write requirement use cases based on market demands or business scenarios. A "use case" is a requirement modeling language, or a requirement modeling method, used to specifically describe the basic information, complete process, and business rules of a use case. The main structure of a requirement use case includes the following:

[0028] (1) Business Process. A business process describes the workflow of the content carried by a use case, with the goal of defining coherent behavior without revealing the internal structure of the system. From a traditional textual perspective, it includes preconditions, process description, error handling, and postconditions.

[0029] (2) Business Rules. Business rules are descriptions of the business logic and constraints of a use case. They are behaviors used to maintain the business structure or control and influence the business. The business rules of a use case should include the business logic and constraints corresponding to all business processes of the current use case. That is, the logical operations that must be performed to implement the business processes are the business rules.

[0030] Business architecture guides the selection of business models needed to fulfill a business requirement, the services provided by each model, and the collaborative relationships between different models, including data transfer and invocation. The business architecture is written or adjusted based on the requirement's use cases.

[0031] Figure 1 A schematic diagram illustrating the module hierarchy of a business model in a business architecture according to an embodiment of this disclosure is provided. Figure 1 As shown, for example, the business architecture includes the following:

[0032] (1) Process Model. The process model uses a standardized, structured modeling language to describe the execution of banking business, reflecting how the bank processes and delivers value according to certain processes and rules to meet internal and external needs. Business domains are the first level of the process model, reflecting the overall value creation process of the enterprise and representing the bank's service capabilities. They are divided into product domains and management domains. Value streams are the second level of the process model, providing a relatively high-level description of how a business domain creates value, facilitating a quick understanding of the business domain's operational process. Activities are the third level of the process model, triggered by events, and describe the end-to-end complete business process of interactions with stakeholders to meet stakeholder needs or specific business objectives. Tasks are the fourth level of the process model, the main components of the three levels of activities, and a set of steps executed by a role within a certain timeframe, with a clear business objective.

[0033] (2) Product Model. The product model uses a standardized, structured modeling language to describe the classification structure and constituent elements of bank products, thereby enabling product innovation or rapid launch. A product line, from the bank's perspective, aggregates products that generate similar revenue streams. A product group is the next level of classification after a product line, grouping essentially similar marketable products together. A basic product is a cluster of marketable products with similar service functions and business processing rules, encompassing all characteristics of the clustered marketable products and serving as a template for product configuration. Marketable products are financial products or services that generate revenue, configured based on basic products, and sold and operated independently by the bank.

[0034] Based on the above business architecture structure and requirement use case structure, a data storage relationship with the same granularity is established between the two. Each requirement use case corresponds to a business architecture. This disclosure realizes the architecture analysis of the business architecture corresponding to the requirement use case, thereby improving the efficiency of requirement analysis.

[0035] This disclosure provides a requirement architecture analysis method, comprising: obtaining requirement use cases to be analyzed and corresponding business architectures, the business architecture including multiple business modules; calculating the correlation between each pair of the multiple business modules to obtain a first correlation coefficient set, wherein the first correlation coefficient set includes multiple first correlation coefficients; calculating the correlation between requirement use cases and the business architecture to obtain a second correlation coefficient set, the second correlation coefficient set including multiple second correlation coefficients; comparing the first correlation coefficient set with the corresponding first threshold set, and comparing the second correlation coefficient set with the corresponding second threshold set, to determine the business modules in the business architecture that exhibit anomalies. By calculating the correlation between each business module within the business architecture, and the correlation between requirement use cases and the business architecture, the method analyzes the correspondence between requirement use cases and the business architecture, as well as the coupling degree within the business architecture, to identify the business modules within the business architecture that exhibit anomalies, thereby improving the quality of the business architecture model.

[0036] Figure 2 The diagram illustrates an application scenario of the requirements architecture analysis method according to an embodiment of the present disclosure.

[0037] like Figure 2 As shown, application scenario 200 according to this embodiment may include terminal devices 201, 202, and 203, a network 204, and a server 205. Network 204 serves as a medium for providing a communication link between terminal devices 201, 202, and 203 and server 205. Network 204 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0038] Users can use terminal devices 201, 202, and 203 to interact with server 205 via network 204 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 201, 202, and 203, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0039] Terminal devices 201, 202, and 203 can be various electronic devices with displays that support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0040] Server 205 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 201, 202, and 203 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0041] It should be noted that the demand architecture analysis method provided in this embodiment can generally be executed by server 205. Correspondingly, the demand architecture analysis device provided in this embodiment can generally be located in server 205. The demand architecture analysis method provided in this embodiment can also be executed by a server or server cluster that is different from server 205 and capable of communicating with terminal devices 201, 202, 203 and / or server 205. Correspondingly, the demand architecture analysis device provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 201, 202, 203 and / or server 205.

[0042] It should be understood that Figure 2 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0043] The following will be based on Figure 1 as well as Figure 2 The described scene, through Figure 3 and Figure 4 The requirement architecture analysis method of the disclosed embodiments is described in detail.

[0044] Figure 3 A flowchart illustrating a requirement architecture analysis method according to an embodiment of the present disclosure is shown schematically.

[0045] like Figure 3 As shown, the requirement architecture analysis method of this embodiment includes operations S310 to S330, and the requirement architecture analysis method can be executed by server 205.

[0046] When operating S310, obtain the requirement use cases to be analyzed and the corresponding business architecture. The business architecture includes multiple business modules.

[0047] Each requirement use case has a corresponding business architecture, each business architecture includes at least one business model, and each business model includes multiple business modules. For example... Figure 1In the business models shown, activities, tasks, product lines, and customers are all business module levels. The activity level can include activity A, activity B, and activity C, and the basic product level includes basic product A, basic product B, and basic product C. There is no specific limit to the number of business modules at each level in the business architecture.

[0048] In operation S320, the correlation between multiple business modules is calculated to obtain a first set of correlation coefficients, wherein the first set of correlation coefficients includes multiple first correlation coefficients.

[0049] Figure 4 A second flowchart illustrating a requirement architecture analysis method according to an embodiment of the present disclosure is shown schematically.

[0050] like Figure 4 As shown, according to an embodiment of this disclosure, before performing operation S320, operation S350 also needs to be performed.

[0051] In operation S350, a historical requirement use case library is obtained; the requirement use case to be analyzed is compared with the historical requirement use case library to obtain a set of requirement use cases and a set of business architectures. The set of requirement use cases includes at least one historical requirement use case with a similarity higher than a predetermined threshold, and the set of business architectures includes the historical business architectures corresponding to at least one historical requirement use case.

[0052] The requirement use cases include the use case name, overview, scope, level, main actors, project stakeholders and interests, preconditions, minimum guarantees, success guarantees, triggering events, main success scenarios, extended scenarios and related information, etc., including a certain amount of textual description.

[0053] The NLP (Natural Language Processing) program processes the requirement use cases to be analyzed and each requirement use case in the historical requirement use case library. From the historical requirement use case library, all historical requirement use cases with a similarity higher than a predetermined threshold to the requirement use cases to be analyzed are selected. These historical requirement use cases constitute a requirement use case set. The business architecture corresponding to each requirement use case in the requirement use case set is obtained, and these business architectures constitute a business architecture set. The cohesion of the business architecture is determined by calculating the correlation between the various business modules within each business architecture.

[0054] According to embodiments of this disclosure, calculating the correlation between multiple business modules to obtain a first correlation coefficient set includes: calculating the correlation between multiple business modules and a business architecture set to obtain multiple first sequences, wherein the multiple first sequences correspond one-to-one with the multiple business modules; and calculating the first correlation coefficients between multiple business modules based on the multiple first sequences to obtain a first correlation coefficient set.

[0055] The following analysis provides an example of how to calculate the correlation between each pair of business modules within the business structure.

[0056] For example, a specific analysis of the correlation between two business modules, activities and basic products, in the business model is performed. The Pearson correlation coefficient between the activity and the basic product is calculated based on their frequency of co-occurrence. The names of activities in the business architecture corresponding to the demand use cases to be analyzed are compared with the historical business architectures in the business architecture set. Assuming that in operation S350, the selected demand use case set includes N historical demand use cases, the corresponding business architecture set includes N historical business architectures. Dummy variables are set: 1 is recorded as an association between an activity and a historical business architecture in the business architecture, and 0 is recorded as no association. The same applies to basic products. For example, if the activity name in the business architecture is "Open a Three-Pillar Special Account," then the occurrence of the activity "Open a Three-Pillar Special Account" in the historical business architecture is recorded as 1, and its absence as 0. This process is repeated for each historical business architecture, resulting in a correlation between the activity and the business architecture set represented by a sequence of N 0-1 numbers, i.e., the first sequence corresponding to the activity. The same applies to basic products, yielding their corresponding first sequence. Finally, the Pearson correlation coefficient between these two first sequences is calculated, representing the first correlation coefficient between the two business modules.

[0057] By integrating the first correlation coefficients between each pair of business modules in the business architecture, we can obtain a set of first correlation coefficients. For example, this set of first correlation coefficients can be represented by a matrix ρ1.

[0058]

[0059] Each element in matrix ρ1 represents the first correlation coefficient between any two business modules in the business architecture.

[0060] In operation S330, the correlation between the requirement use case and the business architecture is calculated to obtain a second set of correlation coefficients, which includes multiple second correlation coefficients.

[0061] According to embodiments of this disclosure, calculating the correlation between requirement use cases and business architecture to obtain a second set of correlation coefficients includes: extracting the top N keywords by frequency of use in the text content of the requirement use cases, where N is an integer greater than or equal to 1; performing text matching between the top N keywords by frequency of use and the requirement use case set to obtain N second sequences; calculating the correlation between multiple business modules and the requirement use case set to obtain multiple third sequences; and calculating the correlation between each keyword and each business module based on the N second sequences and the multiple third sequences to obtain the second set of correlation coefficients.

[0062] According to embodiments of this disclosure, calculating the correlation between each keyword and each business module based on N second sequences and multiple third sequences to obtain a second set of correlation coefficients includes: calculating the second correlation coefficient between each of the N second sequences and each of the multiple third sequences to obtain a second set of correlation coefficients.

[0063] The following is an example analysis of the correlation calculation between requirement use cases and business architecture.

[0064] In the textual content of the requirement use cases, such as the use case name and brief description, keywords are extracted from the text using NLP decomposition. The top N keywords with the highest frequency are selected as KW1, KW2, ..., KWn. Let's take calculating the correlation between keyword KW1 and activity A in the business module as an example.

[0065] First, set up a dummy variable to perform text matching between the keyword KW1 and the set of requirement use cases. If KW1 appears in the historical requirement use cases, it is recorded as 1; otherwise, it is recorded as 0. In this way, KW1 is matched with N historical requirement use cases respectively, resulting in a sequence of N 0-1 numbers, which is the second sequence.

[0066] Then, the association degree of activity A with the set of requirement use cases is calculated. If activity A appears in the historical requirement use cases, it is recorded as 1, and if it does not appear, it is recorded as 0. Thus, activity A is matched with N historical requirement use cases respectively, resulting in a sequence of N 0-1 numbers, which is the third sequence.

[0067] Finally, using the Pearson correlation coefficient calculation method, the second correlation coefficient between the second sequence corresponding to keyword KW1 and the third sequence corresponding to activity A is calculated.

[0068] By integrating the keywords of each requirement use case with the second correlation coefficients between each business module in the business architecture, a second correlation coefficient set is obtained. For example, the first correlation coefficient set can be represented by a matrix ρ2.

[0069]

[0070] Each element in matrix ρ2 is denoted as A. i，j , where i represents the i-th business module, j represents the j-th keyword, and each row is the second correlation coefficient between the i-th business module and each keyword.

[0071] In operation S340, the size of the first correlation coefficient set is compared with the size of the corresponding first threshold set, and the size of the second correlation coefficient set is compared with the size of the corresponding second threshold set, in order to identify the business modules in the business architecture that are abnormal.

[0072] According to embodiments of this disclosure, comparing the size between a first set of correlation coefficients and a corresponding first set of thresholds, and comparing the size between a second set of correlation coefficients and a corresponding second set of thresholds, to determine the business modules in the business architecture that are abnormal includes: when a first correlation coefficient in the first set of correlation coefficients is less than a corresponding threshold in the first set of thresholds, indicating that the two business modules corresponding to the first correlation coefficient are abnormal; when a second correlation coefficient in the second set of correlation coefficients is less than a corresponding threshold in the second set of thresholds, indicating that the correspondence between the business module corresponding to the second correlation coefficient and the requirement use case is abnormal.

[0073] For example, the first threshold set can be set in matrix form.

[0074]

[0075] By comparing the values ​​of the corresponding elements in ρ1 and the threshold matrix T1, it can be seen that all elements except the first correlation coefficient of 0.05 meet the threshold. For the business architecture corresponding to this requirement use case, there is only a problem of low correlation between the two business modules corresponding to the first correlation coefficient of 0.05. Through the requirement architecture analysis method disclosed in this paper, the business modules that do not meet the threshold can be intuitively identified. Then, the business architecture can be quickly adjusted based on the architecture analysis results, thereby improving the efficiency of requirement analysis.

[0076] Similarly, the second threshold set is set in matrix form.

[0077]

[0078] The value of each element in T2 is determined based on the historical average quantile level. Each element in each row of matrix ρ2 is compared with each element in each row of T2. For example, the values ​​0.78, 0.05, ..., 0.65 in the first row of matrix ρ2 are compared with 0.68. If more than m values ​​in the first row of matrix ρ2 are greater than 0.68, it indicates that the correspondence between the keywords and the business architecture for that row is correct. Conversely, if more than m values ​​are greater than 0.68, it indicates that the correspondence between the keywords and the business architecture for that row is incorrect. This disclosed requirement architecture analysis method allows for the intuitive identification of business modules with abnormal correspondences to requirement use cases. Based on the architecture analysis results, the business architecture can be quickly adjusted, improving the efficiency of requirement analysis.

[0079] By combining the comparison results of the first correlation coefficient and the second correlation coefficient, it can be further determined that when the first correlation coefficient in the first correlation coefficient set is less than the corresponding threshold in the first threshold set, and the second correlation coefficient in the second correlation coefficient set is greater than the corresponding threshold in the second threshold set, it indicates that the correlation between the two business modules corresponding to the first correlation coefficient is small, and the correspondence between the two business modules and the requirement use cases is normal. This can prompt the user to judge whether there is a possibility of integration between the two tasks and whether there is a problem of low cohesion and high coupling in the modeling.

[0080] According to embodiments of this disclosure, the number of requirement use cases to be analyzed is multiple, and the requirement architecture method further includes: performing requirement architecture analysis on multiple requirement use cases respectively to obtain the requirement architecture analysis results of each requirement use case; when the architecture analysis results of multiple requirement use cases are all normal, it is indicated that multiple requirement use cases need to be integrated.

[0081] If two use cases, Use Case A and Use Case B, are input and the business architecture analysis results for both use cases are consistent, it indicates that the architecture analysis results for both use cases are normal. Since both use cases use the same set of business architecture assets, it is necessary to consider whether there is a need to integrate requirements, merging the rules and processes of the two use cases into a single complete use case. Using the requirement architecture analysis method disclosed herein, requirement analysts can further analyze the possibility of requirement integration based on the architecture analysis results. When multiple requirements are highly correlated with the same set of architecture analysis, the system uses digital calculations to indicate the need for requirement integration, thereby improving the model quality of the requirement use cases.

[0082] According to embodiments of this disclosure, it further includes: extracting some business modules from multiple business modules to perform requirement architecture analysis on the some business modules.

[0083] When there are many business modules in the business architecture, the amount of computation can be reduced and the efficiency of requirement architecture analysis can be improved by extracting some business modules and operating only on those parts of the business modules (S310-S340).

[0084] The requirement architecture analysis method disclosed herein enables accurate and comprehensive judgment and recommendations on the business architecture analysis of requirements. When the correlation between requirements and architecture analysis is low, intelligent computing provides architecture analysis suggestions. It also enables requirement analysts to integrate requirements. When multiple requirements are highly correlated with the same set of architecture analyses, digital calculations indicate the need for requirement integration. Furthermore, it enables business architects to judge the quality of business models, combining qualitative and quantitative analysis to indicate whether the business architecture model achieves high cohesion and low coupling.

[0085] Based on the above-described requirement architecture analysis method, this disclosure also provides a requirement architecture analysis apparatus. The following will combine... Figure 5 The device is described in detail.

[0086] Figure 5 A schematic block diagram of a requirements architecture analysis apparatus according to an embodiment of the present disclosure is shown.

[0087] like Figure 5 As shown, the demand architecture analysis device 500 of this embodiment includes an acquisition module 510, a first calculation module 520, a second calculation module 530, and a comparison module 540.

[0088] The acquisition module 510 is used to acquire the requirement use cases to be analyzed and the corresponding business architecture, which includes multiple business modules. In one embodiment, the acquisition module 510 can be used to execute the operation S310 described above, which will not be repeated here.

[0089] The first calculation module 520 is used to calculate the correlation between each pair of multiple business modules to obtain a first correlation coefficient set, wherein the first correlation coefficient set includes multiple first correlation coefficients. In one embodiment, the first calculation module 520 can be used to perform the operation S320 described above, which will not be repeated here.

[0090] The second calculation module 530 is used to calculate the correlation between the requirement use case and the business architecture to obtain a second correlation coefficient set, which includes multiple second correlation coefficients. In one embodiment, the second calculation module 530 can be used to perform the operation S330 described above, which will not be repeated here.

[0091] The comparison module 540 is used to compare the size between the first correlation coefficient set and the corresponding first threshold set, and to compare the size between the second correlation coefficient set and the corresponding second threshold set, in order to determine the business modules in the business architecture that are abnormal. In one embodiment, the comparison module 540 can be used to perform the operation S340 described above, which will not be repeated here.

[0092] According to embodiments of this disclosure, any plurality of modules among the acquisition module 510, the first calculation module 520, the second calculation module 530, and the comparison module 540 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the acquisition module 510, the first calculation module 520, the second calculation module 530, and the comparison module 540 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these methods. Alternatively, at least one of the acquisition module 510, the first calculation module 520, the second calculation module 530, and the comparison module 540 may be implemented at least partially as a computer program module, which can perform corresponding functions when the computer program module is run.

[0093] Figure 6 A block diagram of an electronic device suitable for implementing a requirements architecture analysis method according to an embodiment of the present disclosure is shown schematically.

[0094] like Figure 6 As shown, an electronic device 600 according to an embodiment of this disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this disclosure.

[0095] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0096] According to embodiments of this disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0097] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0098] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0099] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to enable the computer system to implement the requirements architecture analysis method provided in the embodiments of this disclosure.

[0100] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0101] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0102] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0103] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0104] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0105] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0106] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A requirement architecture analysis method, characterized in that, include: Obtain the requirement use cases to be analyzed and the corresponding business architecture, wherein the business architecture includes multiple business modules; Calculate the correlation degree between each pair of the multiple business modules to obtain a first correlation coefficient set, wherein the first correlation coefficient set includes multiple first correlation coefficients; Calculate the correlation between the requirement use case and the business architecture to obtain a second set of correlation coefficients, which includes multiple second correlation coefficients; The first set of correlation coefficients is compared with the corresponding first set of thresholds, and the second set of correlation coefficients is compared with the corresponding second set of thresholds to determine the business modules in the business architecture that are abnormal; wherein, the first set of thresholds is a set composed of thresholds corresponding to each first correlation coefficient, and the second set of thresholds is a set composed of thresholds corresponding to each second correlation coefficient. The method further includes: Obtain the historical requirement use case library; The requirement use case is compared with the historical requirement use case library to obtain a set of requirement use cases and a set of business architectures. The set of requirement use cases includes at least one historical requirement use case with a similarity higher than a predetermined threshold, and the set of business architectures includes the historical business architectures corresponding to each of the at least one historical requirement use case. The calculation of the correlation between each pair of the multiple business modules to obtain the first set of correlation coefficients includes: The correlation degree between the plurality of business modules and the business architecture set is calculated respectively to obtain a plurality of first sequences, wherein the plurality of first sequences correspond one-to-one with the plurality of business modules; Based on the plurality of first data sequences, calculate the first correlation coefficients between each pair of the plurality of business modules to obtain a set of first correlation coefficients; The calculation of the correlation between the requirement use case and the business architecture to obtain the second set of correlation coefficients includes: In the text content of the requirement use case, extract the top N keywords with the highest frequency of use in the requirement use case, where N is an integer greater than or equal to 1; The top N most frequently used keywords are matched with the set of requirement use cases to obtain N second sequences. Calculate the correlation degree between the multiple business modules and the set of requirement use cases to obtain multiple third sequences; Based on the N second sequences and the multiple third sequences, the correlation between each keyword and each business module is calculated to obtain a second set of correlation coefficients.

2. The requirement architecture analysis method according to claim 1, characterized in that, The process of calculating the correlation between each keyword and each business module based on the N second sequences and the plurality of third sequences to obtain the second set of correlation coefficients includes: Calculate the second correlation coefficient between each of the N second sequences and each of the plurality of third sequences to obtain a set of second correlation coefficients.

3. The requirement architecture analysis method according to claim 1, characterized in that, The step of comparing the first set of correlation coefficients with the corresponding first set of thresholds, and comparing the second set of correlation coefficients with the corresponding second set of thresholds, to determine the business modules in the business architecture that are experiencing anomalies includes: When the first correlation coefficient in the first correlation coefficient set is less than the corresponding threshold in the first threshold set, it indicates that the two business modules corresponding to the first correlation coefficient are abnormal. When the second correlation coefficient in the second correlation coefficient set is less than the corresponding threshold in the second threshold set, an error is indicated that the correspondence between the business module corresponding to the second correlation coefficient and the requirement use case is abnormal.

4. The requirement architecture analysis method according to claim 1, characterized in that, The number of requirement use cases to be analyzed is multiple, and the requirement architecture analysis method also includes: Perform requirement architecture analysis on multiple requirement use cases to obtain the requirement architecture analysis results for each requirement use case; If the architecture analysis results of the multiple requirement use cases are all normal, then it will be indicated that the multiple requirement use cases need to be integrated.

5. The requirement architecture analysis method according to claim 1, characterized in that, Also includes: Extract some business modules from the multiple business modules to perform requirement architecture analysis on the selected business modules.

6. A demand architecture analysis apparatus for implementing the method according to any one of claims 1 to 5, comprising: The acquisition module is used to acquire the requirement use case to be analyzed and the business architecture corresponding to the requirement use case, wherein the business architecture includes multiple business modules; The first calculation module is used to calculate the correlation between each pair of the plurality of business modules to obtain a first set of correlation coefficients, wherein the first set of correlation coefficients includes a plurality of first correlation coefficients; The second calculation module is used to calculate the correlation between the requirement use case and the business architecture to obtain a second set of correlation coefficients, which includes multiple second correlation coefficients; and The comparison module is used to compare the size between the first set of correlation coefficients and the corresponding first set of thresholds, and to compare the size between the second set of correlation coefficients and the corresponding second set of thresholds, so as to determine the business modules that have an anomaly in the business architecture; wherein, the first set of thresholds is a set composed of thresholds corresponding to each first correlation coefficient, and the second set of thresholds is a set composed of thresholds corresponding to each second correlation coefficient.

7. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 5.

9. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images