System stability evaluation method and device and readable storage medium

Abstract

The invention discloses a system stability evaluation method and device and a readable storage medium. The method comprises the following steps: determining components of a to-be-evaluated system; abstract data and stable data of the component are determined, the abstract data are used for indicating the abstract degree of the component, and the stable data are used for indicating the stability degree of the component; the abstract data and the stable data are input into an evaluation model diagram to be analyzed, the stable information of the to-be-evaluated system is determined, the evaluation model diagram is a preset relation model diagram for determining the stable information, and the stable information is used for representing the stability of the system. Through the method and the device, the problem that the system stability cannot be evaluated in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of big data, and in particular, to a system stability assessment method, device and readable storage medium. Background Art

[0002] At present, in the field of software development, software systems are required to be customer-centric, not only to proactively predict business needs and meet the personalized demands of different customers, but also to ensure the stability of business systems while promoting the rapid launch of business. This requires accurate identification of the steady-state and sensitive-state parts of the program, and orderly classification of programs in the middle state of steady-state or sensitive-state.

[0003] In the related technologies, there is no systematic method based on mathematical statistics to identify steady-state and agile programs. It is mainly based on the business experience and inductive summary of R&D personnel to sort out the core branches of the business process, gradually iterate, and form a steady-state service chain. Since the current method of identifying steady-state and agile programs based on inductive summary relies heavily on personal experience and judgment, the results may be subjective, and different people may have different views and understandings. At the same time, experience-based identification methods often lack quantitative analysis and cannot accurately measure and evaluate the degree of steady state and agile state. Since the identification of steady state and agile state is based on personal experience, it is limited by the knowledge and skill level of personal experience and may have limitations. Therefore, there is a problem of being unable to evaluate the stability of the system.

[0004] With regard to the problem that the system stability cannot be evaluated in related technologies, no effective solution has been proposed so far. Summary of the invention

[0005] The main purpose of the present application is to provide a system stability evaluation method, device and readable storage medium to solve the problem that the system stability cannot be evaluated in the related art.

[0006] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for evaluating the stability of a system is provided. The method comprises: determining the components of the system to be evaluated; determining the abstract data and stable data of the components, wherein the abstract data is used to indicate the abstract degree of the components, and the stable data is used to indicate the stability degree of the components; inputting the abstract data and stable data into an evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system.

[0007] Optionally, determining the abstract data of a component includes: obtaining the number of classes and the number of abstract classes of the component, wherein the number of classes is used to indicate the classes with target functions and properties defined in the component, and the number of abstract classes is used to indicate the number of abstract classes and interfaces defined in the component; based on the number of classes and the number of abstract classes, determining the abstract data.

[0008] Optionally, determining the abstract data based on the number of classes and the number of abstract classes includes: converting the number of classes and the number of abstract classes into abstract data.

[0009] Optionally, determining stable data of a component includes: obtaining a frequency of change of the component within a preset time period; and determining stable data based on the frequency of change.

[0010] Optionally, the abstract data and the stable data are input into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, including: determining the position information of the component in the evaluation model diagram based on the abstract data and the stable data; matching the position information with the preset position information to obtain a matching result, wherein the matching result is used to indicate the degree of matching between the position information and the preset position information; determining the stable data of the component based on the matching result; and determining the stability information of the system to be evaluated based on the stable data of the component.

[0011] Optionally, based on the matching result, determining the stable information of the component includes: in response to the matching result being that the position information successfully matches the preset position information, determining the stable information corresponding to the preset position information as the stable information of the component.

[0012] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a stability evaluation device for a system is provided. The device comprises: a first determination unit, used to determine the components of the system to be evaluated; a second determination unit, used to determine the abstract data and stability data of the components, wherein the abstract data is used to indicate the abstract degree of the components, and the stability data is used to indicate the stability degree of the components; a third determination unit, used to input the abstract data and stability data into an evaluation model diagram for analysis, and determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system.

[0013] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein when the program is executed by a processor, the device where the storage medium is located is controlled to execute the system stability assessment method in an embodiment of the present invention.

[0014] To achieve the above object, according to another aspect of the present application, an electronic device is provided. A memory stores an executable program; a processor is used to run the program, wherein the system stability evaluation method in the embodiment of the present invention is executed when the program is run.

[0015] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a computer program product is provided, which includes computer instructions, and when the computer instructions are executed by a processor, the method for evaluating the stability of the system in the embodiment of the present invention is implemented.

[0016] In an embodiment of the present application, by determining the components of the system to be evaluated; determining the abstract data and stable data of the components, wherein the abstract data is used to indicate the degree of abstraction of the components, and the stable data is used to indicate the degree of stability of the components; the abstract data and stable data are input into an evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system. Since the present invention can directly determine the abstract data and stable data of the components through the components of the system to be evaluated, and thus determine the stability information of the system to be evaluated based on the abstract data and stable data, the problem of excessive subjectivity in judging the stability of the system due to reliance on personal experience and judgment is avoided, thereby achieving the technical effect of objectively evaluating the stability of the system, and solving the technical problem of being unable to objectively evaluate the stability of the system due to excessive human subjectivity. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal for implementing a system stability evaluation method provided in an embodiment of the present application;

[0019] Figure 2 is a flow chart of a method for evaluating the stability of a system provided in an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of an evaluation model provided according to an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of an evaluation model interval provided according to an embodiment of the present application;

[0022] Figure 5 is a schematic diagram of an ideal component evaluation model interval provided according to an embodiment of the present application;

[0023] Figure 6 is a schematic diagram of a system stability assessment device provided according to an embodiment of the present application;

[0024] Figure 7 It is a structural block diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0026] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0027] It should be noted that the information and data collected in this application are authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good customs, and provide corresponding operation entrances for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0028] According to an embodiment of the present application, a method embodiment for evaluating the stability of a system is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0029] The system stability evaluation method provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 1 is a hardware structure block diagram of a computer terminal for implementing a method for evaluating system stability according to an embodiment of the present invention. Figure 1 As shown, the computer terminal 10 (or mobile device) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0030] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0031] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the stability evaluation method of the system in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the stability evaluation method of the system described above is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0032] The transmission device 106 can be used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0033] The display may be, for example, a touch screen liquid crystal display (LCD), which enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0034] Under the above operating environment, this application provides Figure 2 The method of evaluating the stability of the system is shown. Figure 2 It is a flow chart of a method for evaluating the stability of a system according to Example 1 of the present application.

[0035] Step S201: determining components of the system to be evaluated.

[0036] In the technical solution provided in the above step S201 of the present invention, the system to be evaluated may at least include a business system.

[0037] In this embodiment, the components of the system to be evaluated are determined. For example, the overall architecture and design of the system are determined according to the functions and objectives of the system to be evaluated, so as to determine the components of the system. This is only an illustrative example and does not limit the specific method of determining the components of the system to be evaluated.

[0038] Optionally, a component is used to indicate a module or part with independent functions in a software system, which can be called or reused by other modules.

[0039] For example, decompose the system to be evaluated into different modules or components, determine the dependencies and interactions between the modules in the system, and identify the key components in the system, which are components that have a significant impact on the system's functions and performance. These components usually need to be evaluated in detail.

[0040] For another example, the data flow and control flow in the system to be evaluated are analyzed to determine the input, output, and processing procedures in the system to be evaluated so as to determine the components of the system.

[0041] Step S202, determining the abstract data and stable data of the component.

[0042] In the technical solution provided in step S202 of the present invention, the abstract data is used to indicate the abstraction level of the component, and the stable data is used to indicate the stability level of the component. The abstract data may also be referred to as an abstract metric (denoted as A), and the stable data may also be referred to as stability or a stable metric (denoted as I).

[0043] In this embodiment, after determining the components of the system to be evaluated in step S201, the abstract data and stable data of the components are determined. For determining the abstract data of the components, for example, the abstract data of the components is determined according to the number of classes, abstract classes, and interfaces in the components. This is only an illustrative example, and the specific method for determining the abstract data of the components is not limited.

[0044] For example, suppose that indicator A is a measure of the degree of abstraction of the components of the system to be evaluated, and its value is the ratio of abstract classes to interfaces in the component. Nc represents the number of classes in the component, and Na represents the number of abstract classes and interfaces in the component. Then the degree of abstraction of the component can be expressed by the following formula:

[0045] A=Na÷Nc (1)

[0046] Among them, the value range of the A indicator is from [0,1]. A value of 0 means that there is no abstract class in the component, and a value of 1 means that there is only abstract class in the component.

[0047] Optionally, with respect to determining the stable data of a component, the stable data of the component may be determined by determining a frequency of program changes in the component within a certain period of time.

[0048] For example, the analysis can be done by monitoring the submission records of the component code repository or version control system. The frequency of program changes can be determined by counting the number of submissions, code changes, code review records, and other indicators over a period of time. Thus, the stable data I can be determined. The value range of the I indicator is from [0,1]. A value of 0 means that the program has no changes and is the most stable. A value of 1 means that the program changes most frequently.

[0049] Step S203: input the abstract data and the stable data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated.

[0050] In the technical solution provided in the above step S203 of the present invention, the evaluation model diagram is a pre-set relationship model diagram for determining stability information, and the stability information is used to characterize the stability of the system. The stability information can also be called stability.

[0051] In this embodiment, after the abstract data and stable data of the component are determined in step S202, the abstract data and stable data are input into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated. For example, according to the relationship between the abstract data and the stable data, the position of the component information in the evaluation model diagram is determined, thereby determining the stability information of the system to be evaluated. This is only an illustrative example, and does not limit the specific method for determining the stability information of the system to be evaluated.

[0052] For example, Figure 3 is a schematic diagram of an evaluation model provided according to an embodiment of the present application, such as Figure 3 As shown in the figure, the most stable component containing infinite abstract classes should be located in the upper left corner (0,1), and the most unstable and most specific component should be located in the lower right corner (1,0). By determining the position of stable data I and abstract data A in the figure, the stability information of the system to be evaluated can be determined.

[0053] It should be noted that the above embodiment can be executed by a stability evaluation device of the system.

[0054] In this embodiment, by determining the components of the system to be evaluated; determining the abstract data and stable data of the components, wherein the abstract data is used to indicate the degree of abstraction of the components, and the stable data is used to indicate the degree of stability of the components; the abstract data and stable data are input into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system. Since the present invention can directly determine the abstract data and stable data of the components through the components of the system to be evaluated, and thus determine the stability information of the system to be evaluated based on the abstract data and stable data, the problem of excessive subjectivity in judging the stability of the system due to reliance on personal experience and judgment is avoided, thereby achieving the technical effect of objectively evaluating the stability of the system, and solving the technical problem of being unable to objectively evaluate the stability of the system due to excessive human subjectivity.

[0055] The above method of this embodiment is further introduced below.

[0056] As an optional implementation method, in the system stability assessment method provided in the embodiment of the present application, determining the abstract data of the component includes: obtaining the number of classes and the number of abstract classes of the component, wherein the number of classes is used to indicate the classes with target functions and attributes defined in the component, and the number of abstract classes is used to indicate the number of abstract classes and interfaces defined in the component; based on the number of classes and the number of abstract classes, determining the abstract data.

[0057] In this embodiment, the number of classes and the number of abstract classes of a component are obtained, for example, by viewing the class structure in the component through an analysis tool, thereby obtaining the number of classes and the number of abstract classes of the component.

[0058] Optionally, the number of classes in a component can be represented as Nc, and the number of abstract classes in a component can be represented as Na.

[0059] For example, use code analysis tools to search and count the number of classes in a project, and then further filter out abstract classes and count the number of abstract classes.

[0060] Optionally, after obtaining the number of classes and the number of abstract classes of the component, the abstract data is determined based on the number of classes and the number of abstract classes. Optionally, the number of classes and the number of abstract classes in the component are calculated to determine the abstract data of the component, thereby achieving the purpose of objectively and accurately calculating the component, thereby improving the accuracy of determining the stability of the system to be evaluated.

[0061] As an optional implementation mode, in the system stability evaluation method provided in the embodiment of the present application, abstract data is determined based on the number of classes and the number of abstract classes, including: converting the number of classes and the number of abstract classes into abstract data.

[0062] In this embodiment, mathematical operations are performed on the number of classes and the number of abstract classes to convert the number of classes and the number of abstract classes into abstract data. For example, the number of classes and the number of abstract classes are divided to determine the abstract data. The number of classes and the number of abstract classes are mathematically operated by the aforementioned formula (1) to obtain the abstract data, which will not be described in detail here.

[0063] Optionally, by performing mathematical operations on the number of classes and the number of abstract classes to determine abstract data, the abstraction level of the component can be accurately determined.

[0064] As an optional implementation mode, in the system stability evaluation method provided in the embodiment of the present application, determining the stability data of the component includes: obtaining the change frequency of the component within a preset time period; and determining the stability data based on the change frequency.

[0065] In this embodiment, the change frequency of the component within a preset time period is obtained, for example, by monitoring the submission record of the component's code repository or version control system for analysis. The frequency of program changes is determined by counting indicators such as the number of submissions, code changes, and code review records within a period of time.

[0066] Optionally, after obtaining the change frequency of the component within a preset time period, the stable data of the component is determined according to the change frequency. For example, the stability of the data is judged according to the change frequency. If the change frequency is low, the data is relatively stable; if the change frequency is high, the data may not be stable enough. According to the judgment result, it is determined which data is stable, and further analysis and processing can be performed.

[0067] Alternatively, if the change frequency of the component is low, that is, the change amplitude is small and the change frequency is small, then the data can be considered to be relatively stable. On the contrary, if the change frequency of the component is high, that is, the change amplitude is large and the change frequency is large, then the data may not be stable enough.

[0068] Alternatively, determining stable data can help make data analysis and decision making more accurate. Stable data can reduce errors and uncertainties, making the results of the analysis more reliable.

[0069] As an optional implementation mode, in the system stability assessment method provided in the embodiment of the present application, abstract data and stable data are input into the assessment model diagram for analysis to determine the stability information of the system to be assessed, including: determining the position information of the component in the assessment model diagram based on the abstract data and the stable data; matching the position information with the preset position information to obtain a matching result, wherein the matching result is used to indicate the degree of matching between the position information and the preset position information; determining the stability data of the component based on the matching result; and determining the stability information of the system to be assessed based on the stability data of the component.

[0070] In this embodiment, the position information of the component in the evaluation model diagram is determined based on the abstract data and the stable data. For example, the position information of the component in the evaluation model diagram is determined based on the abstract data and the stable data. Figure 3 Coordinate positions in the figure shown.

[0071] Optionally, after determining the position information of the component, the position information is matched with preset position information to obtain a matching result. For example, the preset information may be a painful area, a useless area, a main sequence, etc.

[0072] For example, Figure 4 is a schematic diagram of an evaluation model interval provided according to an embodiment of the present application, such as Figure 4 As shown, the pain zone represents the area around (0,0), which indicates that the stability of the component is high, making the component particularly difficult to modify, which means that the component cannot be expanded. Figure 4 The components close to the point (1,1) in the graph are called useless areas. The useless areas indicate that these components are usually infinitely abstract, but are not depended on by other components. Such components are often unusable.

[0073] For another example, the main sequence line is a straight line connecting (1,0) to (0,1). This interval indicates that the component is not designed to be "too abstract" in pursuit of stability, nor is it designed to be "too unstable" in order to avoid abstraction. Such a component is neither particularly difficult to modify nor can it achieve sufficient functionality.

[0074] Optionally, after determining the matching result, the stability data of the component is determined according to the matching result, thereby determining the stability of the system to be evaluated. The specific determination method is as follows.

[0075] Optionally, since the evaluation model diagram is objective and quantitative, its conclusions and results have good generalizability and repeatability and can be applied to different fields and scenarios.

[0076] As an optional implementation method, in the system stability assessment method provided in the embodiment of the present application, the stability information of the component is determined based on the matching result, including: in response to the matching result being that the position information successfully matches the preset position information, the stability information corresponding to the preset position information is determined as the stability information of the component.

[0077] In this embodiment, when the matching result is that the position information matches the preset position information successfully, it means that the preset position information is consistent with the stable information corresponding to the position information. Based on this, the stable information corresponding to the preset position information is determined as the stable information of the component.

[0078] Optionally, by successfully matching the preset location information with the location information, the possibility of system misidentification can be reduced and the stability and accuracy of the system can be improved.

[0079] It should be noted that the above embodiment can be executed by a stability evaluation device of the system.

[0080] The stability evaluation method of a system provided in an embodiment of the present application determines the components of the system to be evaluated; determines the abstract data and stable data of the components, wherein the abstract data is used to indicate the degree of abstraction of the components, and the stable data is used to indicate the degree of stability of the components; inputs the abstract data and stable data into an evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system. Since the present invention can directly determine the abstract data and stable data of the components through the components of the system to be evaluated, and thus determine the stability information of the system to be evaluated based on the abstract data and stable data, the problem of excessive subjectivity in judging system stability due to reliance on personal experience and judgment is avoided, thereby achieving the technical effect of objectively evaluating system stability and solving the technical problem of being unable to objectively evaluate system stability due to excessive human subjectivity.

[0081] The technical solution of the embodiment of the present invention is illustrated below in conjunction with preferred implementation modes.

[0082] At present, in the field of software development, software systems are required to be customer-centric, not only to proactively predict business needs and meet the personalized demands of different customers, but also to ensure the stability of business systems while promoting the rapid launch of business. This requires accurate identification of the steady-state and sensitive-state parts of the program, and orderly classification of programs in the middle state of steady-state or sensitive-state.

[0083] In the related technologies, there is no systematic method based on mathematical statistics to identify steady-state and agile programs. It is mainly based on the business experience and inductive summary of R&D personnel to sort out the core branches of the business process, gradually iterate, and form a steady-state service chain. Since the current method of identifying steady-state and agile programs based on inductive summary relies heavily on personal experience and judgment, the results may be subjective, and different people may have different views and understandings. At the same time, experience-based identification methods often lack quantitative analysis and cannot accurately measure and evaluate the degree of steady state and agility. Since the identification of steady state and agility is based on personal experience, it may be limited by the knowledge and skill level of personal experience. Therefore, there is a problem of being unable to evaluate the stability of the system. For the problem of being unable to evaluate the stability of the system in related technologies, no effective solution has been proposed.

[0084] However, an embodiment of the present invention proposes a stable-sensitive state identification method, which uses an abstract metric A, stability I, in the relevant business system to quantitatively analyze and calculate the system to be identified, and determines the stability of the system to be identified, thereby achieving the technical effect of objectively evaluating the stability of the system and solving the technical problem of being unable to objectively evaluate the stability of the system due to excessive human subjectivity.

[0085] The embodiments of the present invention are further described below.

[0086] In this embodiment, abstraction metric A: Assume that the A index is a measure of the abstraction level of the component, and its value is the ratio of abstract classes to interfaces in the component. Then: Nc represents the number of classes in the component. Na represents the number of abstract classes and interfaces in the component. The abstraction level A can be expressed as: A = Na ÷ Nc.

[0087] Optionally, the value range of the A indicator is from [0,1], a value of 0 means that there is no abstract class in the component, and a value of 1 means that there are only abstract classes in the component.

[0088] Optionally, stability I: Assume that the I index is a measure of the stability of the component, and its value is the frequency of program changes in the component over a certain period of time. The value range of the I index is from [0,1], with a value of 0 indicating the most stable program without changes, and a value of 1 indicating the most frequent program changes.

[0089] Optionally, the main sequence: First define the relationship between stability I and its degree of abstraction A, such as Figure 3 As shown, Figure 3 The most stable component that contains infinite abstract classes should be located at the upper left corner (0,1), and the most unstable and most specific component should be located at the lower right corner (1,0). It is not mandatory to require that all components be located at the two positions (0,1) and (1,0), so we must assume that there is a reasonable component interval in the above figure. This interval should be deduced by the elimination method, that is, we can first find out the positions where the components should not be located.

[0090] Alternatively, if Figure 4 As shown, it is divided into the painful area, the useless area and the main sequence. Assuming that a component is at the (0,0) position, it should be a very stable but also very specific component.

[0091] Alternatively, such a component is poorly designed because it is difficult to modify, which means that the component cannot be extended. In this way, because this component is not abstract, and it becomes particularly difficult to modify for stability reasons, it is not desirable for a well-designed component to be close to this area, so the area around (0,0) is called the pain zone.

[0092] Optionally, components close to the position (1,1) are usually infinitely abstract, but not depended on by other components. Such components are often unusable, so this area is called the useless area.

[0093] Optionally, Figure 5 is a schematic diagram of an ideal component evaluation model interval provided according to an embodiment of the present application, such as Figure 5 As shown, the main sequence line is defined as a straight line connecting (1,0) to (0,1). The stable programs we are looking for are those located on the main sequence line. They will not be designed to be "too abstract" in pursuit of stability, nor will they be designed to be "too unstable" in order to avoid abstraction. Such components will not be particularly difficult to modify, and can achieve sufficient functions. Of course, components in large systems cannot be completely abstract or completely stable. So we only need to strive to make these components located on the main sequence line, or close to this line.

[0094] Optionally, the present invention proposes a stable and sensitive state identification method based on the principle of stable abstraction, which uses a mathematical model to statistically analyze the abstract measurement A and stability I in the business system, thereby performing quantitative analysis and calculation, and can accurately measure and evaluate the degree of stable and sensitive states.

[0095] Optionally, a method for identifying a steady-state and a sensitive state proposed in the present invention has a wide range of applications: the mathematical model can be applied to a variety of different systems and scenarios, and can identify and analyze the steady-state and a sensitive state of the system.

[0096] Optionally, a steady-state identification method proposed in the present invention can take system dynamics into consideration: a mathematical model can describe the dynamic characteristics of the system, thereby better understanding the behavior and changing laws of the system.

[0097] Optionally, a stable-sensitive state identification method proposed in the present invention has strong generalizability: since the mathematical model is objective and quantitative, its conclusions and results have good generalizability and repeatability, and can be applied to different fields and scenarios.

[0098] Alternatively, agile state and steady state are two concepts related to system stability, referring to how the system responds to external changes (including changes in business requirements and changes in technical implementation).

[0099] Optionally, agility definition: Agility refers to the ability of a system to respond and adjust quickly when subjected to external disturbances, that is, the system can adapt and cope with external changes in a short period of time. Agile systems are flexible and adaptable, and can quickly adapt to different working environments and changes. In other words, when external changes occur, the agile part of the system has the ability to respond quickly and can quickly adjust to adapt to new environments or conditions.

[0100] Optionally, steady state definition: Steady state refers to the ability of a system to maintain a stable state for a long time, that is, the system can quickly return to its original state after being disturbed by an external disturbance. A steady-state system has stable performance and reliability and can operate in a certain working state for a long time. In other words, when external changes occur, the steady-state part of the system can maintain a relatively stable state or behavior without major changes or changes.

[0101] Alternatively, in practical applications, the system needs both steady state to maintain long-term stable operation and agile state to cope with emergencies and changes. Steady state and agile state are important indicators of system operation and management, and have a significant impact on the performance and reliability of the system.

[0102] Alternatively, a component refers to an independent module or part of a program, usually used to describe different functions or modules in a system. A component can include one or more classes, interfaces, or other components to implement a specific function or service. Components can be reusable, replaceable, and have independent lifecycles.

[0103] Alternatively, an abstract class is a class used to represent a general concept or template in object-oriented programming. Abstract classes cannot be instantiated and can only be used as base classes or parent classes of other classes. Abstract classes usually contain abstract methods (that is, methods without a specific implementation) that subclasses must implement in order to be instantiated.

[0104] Alternatively, a class is a basic concept in object-oriented programming, used to describe a template for objects with common properties and behaviors. A class can include attributes (fields) and methods (functions) to describe the state and behavior of an object. A class can be instantiated into an object, and an object can perform specific operations by calling methods.

[0105] Alternatively, components, abstract classes, and classes are all concepts used in object-oriented programming to describe different levels and relationships in a program, and they play an important role in program design and development.

[0106] Alternatively, an interface is a specification that defines the interaction between components in a software system. Through interfaces, different components can communicate and interact effectively to achieve the functional requirements of the system. Interfaces can improve the scalability, flexibility, and maintainability of the system, making the system more modular and easy to develop collaboratively. In object-oriented programming, an interface is an abstract concept used to describe the interaction specifications between classes. A class can implement one or more interfaces to implement the methods and properties defined by the interface.

[0107] In this embodiment, the abstract metric A and stability I in the relevant business system are used to quantitatively analyze and calculate the system to be identified, and the stability of the system to be identified is determined, thereby achieving the technical effect of objectively evaluating the stability of the system and solving the technical problem of being unable to objectively evaluate the stability of the system due to excessive human subjectivity.

[0108] The present application also provides a system stability assessment device. It should be noted that the system stability assessment device of the present application can be used to execute the system stability assessment method provided in the present application. The following introduces the system stability assessment device provided in the present application.

[0109] According to an embodiment of the present application, a stability evaluation device for implementing the above system is also provided. Figure 6 As shown, the device includes: a first determining unit 601, a second determining unit 602 and a third determining unit 603.

[0110] The first determining unit 601 is used to determine components of the system to be evaluated.

[0111] The second determining unit 602 is used to determine the abstract data and stable data of the component, wherein the abstract data is used to indicate the abstraction level of the component, and the stable data is used to indicate the stability level of the component.

[0112] The third determination unit 603 is used to input the abstract data and the stable data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stable information, and the stable information is used to reflect the stability of the system.

[0113] The stability evaluation device of the system provided in the embodiment of the present application determines the components of the system to be evaluated; determines the abstract data and stable data of the components, wherein the abstract data is used to indicate the abstract degree of the components, and the stable data is used to indicate the stability degree of the components; inputs the abstract data and stable data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system, thereby solving the problem that the system stability cannot be evaluated in the related art. Thus, the effect of evaluating the stability of the system is achieved.

[0114] Optionally, in the stability assessment device of the system provided in the embodiment of the present application, the second determination unit 602 may include: a first acquisition module, used to acquire the number of classes and the number of abstract classes of a component, wherein the number of classes is used to indicate the classes with target functions and attributes defined in the component, and the number of abstract classes is used to indicate the number of abstract classes and interfaces defined in the component; a first determination module, used to determine abstract data based on the number of classes and the number of abstract classes.

[0115] Optionally, in the system stability assessment device provided in the embodiment of the present application, the first determination module may include: an operator module, configured to convert the number of classes and the number of abstract classes into abstract data.

[0116] Optionally, in the stability evaluation device of the system provided in the embodiment of the present application, the second determination unit 602 may include: a second acquisition module, used to obtain the change frequency of the component within a preset time period; and a second determination module, used to determine stability data based on the change frequency.

[0117] Optionally, in the stability evaluation device of the system provided in the embodiment of the present application, the third determination unit 603 may include: a third determination module, used to determine the position information of the component in the evaluation model diagram based on abstract data and stable data; a matching module, used to match the position information with the preset position information to obtain a matching result, wherein the matching result is used to indicate the degree of matching between the position information and the preset position information; a fourth determination module, used to determine the stable data of the component based on the matching result; and a fifth determination module, used to determine the stable data information of the system to be evaluated based on the stable data of the component.

[0118] Optionally, in the stability evaluation device of the system provided in the embodiment of the present application, the matching module may include: a determination submodule for determining the stability information corresponding to the preset position information as the stability information of the component in response to the matching result that the position information successfully matches the preset position information.

[0119] It should be noted that the first determination unit 601, the second determination unit 602 and the third determination unit 603 correspond to steps S201 to S203 in Example 1, and the three units and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n), and the above-mentioned modules may also be part of the device and may be run in the computer terminal 10 provided in Example 1.

[0120] An embodiment of the present application may provide an electronic device, Figure 7 is a structural block diagram of an electronic device provided according to an embodiment of the present application. Figure 7 As shown, the electronic device may include: one or more ( Figure 7 (only one is shown) processor 1002, memory 1004, storage controller, and peripheral interface, wherein the peripheral interface is connected to the radio frequency module, audio module and display.

[0121] Among them, the memory can be used to store software programs and modules, such as program instructions / modules corresponding to the methods and devices in the embodiments of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned method. The memory may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0122] The processor can call the information and application programs stored in the memory through the transmission device to perform the following steps: determine the components of the system to be evaluated; determine the abstract data and stability data of the components, wherein the abstract data is used to indicate the degree of abstraction of the components, and the stability data is used to indicate the degree of stability of the components; input the abstract data and the stability data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system.

[0123] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: obtain the number of classes and the number of abstract classes of the component, wherein the number of classes is used to indicate the classes with target functions and attributes defined in the component, and the number of abstract classes is used to indicate the number of abstract classes and interfaces defined in the component; based on the number of classes and the number of abstract classes, determine the abstract data.

[0124] The processor may also call the information and application programs stored in the memory through the transmission device to perform the following steps: converting the class quantity and the abstract class quantity into abstract data.

[0125] The processor can also call the information and application programs stored in the memory through the transmission device to perform the following steps: obtaining the change frequency of the component within a preset time period; and determining the stable data based on the change frequency.

[0126] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: based on the abstract data and the stable data, determine the position information of the component in the evaluation model diagram; match the position information with the preset position information to obtain a matching result, wherein the matching result is used to indicate the degree of matching between the position information and the preset position information; based on the matching result, determine the stable data of the component; based on the stable data of the component, determine the stable data information of the system to be evaluated.

[0127] The processor can also call the information and application stored in the memory through the transmission device to perform the following steps: in response to the matching result that the location information successfully matches the preset location information, determine the stability information corresponding to the preset location information as the stability information of the component.

[0128] By adopting the embodiment of the present application, a method for evaluating the stability of a system is provided. By determining the components of the system to be evaluated; determining the abstract data and stable data of the components, wherein the abstract data is used to indicate the abstract degree of the components, and the stable data is used to indicate the stability degree of the components; inputting the abstract data and stable data into the evaluation model diagram for analysis, and determining the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system, since the present invention can directly determine the abstract data and stable data of the components through the components of the system to be evaluated, thereby determining the stability information of the system to be evaluated based on the abstract data and stable data, avoiding the problem of excessive subjectivity in judging the stability of the system due to reliance on personal experience and judgment, thereby achieving the technical effect of objectively evaluating the stability of the system, and solving the technical problem of being unable to objectively evaluate the stability of the system due to excessive human subjectivity.

[0129] Figure 7 is a structural block diagram of an electronic device provided according to an embodiment of the present application. A person skilled in the art can understand that Figure 7 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 7 The structure of the electronic device is not limited. Figure 7 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 7 Different configurations are shown.

[0130] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0131] According to an embodiment of the present invention, a processor is further provided. The processor is used to run a program, wherein the program executes the method for evaluating the stability of the system in the embodiment when the program is run by the processor.

[0132] According to an embodiment of the present invention, there is further provided an electronic device, comprising: a memory storing an executable program; and a processor for running the program, wherein the method for evaluating the stability of the system in the embodiment is executed when the program is running.

[0133] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the method for evaluating the stability of the system in the embodiment.

[0134] According to an embodiment of the present invention, a computer program product is further provided. The computer program product includes a computer program. When the computer program is executed by a processor, the method for evaluating the stability of the system in the embodiment is implemented.

[0135] According to an embodiment of the present invention, a computer program product is also provided, including a non-volatile computer-readable storage medium, the non-volatile computer-readable storage medium is used to store a computer program, and when the computer program is executed by a processor, the method for evaluating the stability of the system in the embodiment is implemented.

[0136] According to an embodiment of the present invention, a computer program is further provided. When the computer program is executed by a processor, the method for evaluating the stability of the system in the embodiment is implemented.

[0137] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0138] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0139] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0140] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0141] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0142] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the relevant technology, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods of various embodiments of the present invention. The aforementioned storage medium includes: U disk, ROM, RAM, mobile hard disk, disk or optical disk and other media that can store program codes.

[0143] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for evaluating the stability of a system, characterized in that: include: Identify the components of the system to be evaluated; Determining abstract data and stable data of the component, wherein the abstract data is used to indicate the abstraction level of the component, and the stable data is used to indicate the stability level of the component; The abstract data and the stability data are input into an evaluation model diagram for analysis to determine stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system.

2. The method according to claim 1, characterized in that Determine the abstract data of the component, including: Obtaining the number of classes and the number of abstract classes of the component, wherein the number of classes is used to indicate the classes with target functions and attributes defined in the component, and the number of abstract classes is used to indicate the number of abstract classes and interfaces defined in the component; Based on the number of classes and the number of abstract classes, the abstract data is determined.

3. The method according to claim 2, characterized in that Determining the abstract data based on the number of classes and the number of abstract classes includes: The class number and the abstract class number are converted into the abstract data.

4. The method according to claim 1, characterized in that: Determine the stability data of the components, including: Obtaining the change frequency of the component within a preset time period; Based on the frequency of variation, the stable data is determined.

5. The method according to claim 1, characterized in that Inputting the abstract data and the stable data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated includes: Determining position information of the component in the evaluation model diagram based on the abstract data and the stable data; Matching the location information with the preset location information to obtain a matching result, wherein the matching result is used to indicate the matching degree between the location information and the preset location information; Based on the matching result, determining stable data of the component; Based on the stability data of the component, the stability information of the system to be evaluated is determined.

6. The method according to claim 5, characterized in that Determining stability information of the component based on the matching result includes: In response to the matching result being that the position information successfully matches the preset position information, the stability information corresponding to the preset position information is determined as the stability information of the component.

7. A system stability assessment device, characterized in that: include: A first determining unit, configured to determine a component of a system to be evaluated; a second determining unit, configured to determine abstract data and stable data of the component, wherein the abstract data is used to indicate a degree of abstraction of the component, and the stable data is used to indicate a degree of stability of the component; The third determination unit is used to input the abstract data and the stability data into the evaluation model diagram for analysis to determine the stability information of the system to be evaluated, wherein the evaluation model diagram is a pre-set relationship model diagram for determining the stability information, and the stability information is used to characterize the stability of the system.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the device where the computer-readable storage medium is located is controlled to execute the method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: include: A memory storing an executable program; A processor, configured to run the program, wherein the program executes the method according to any one of claims 1 to 6 when running.

10. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images