System engineering design and verification method and system based on fishbone model
Through the system engineering design and verification method based on fish bone model, the problems of high learning threshold and difficult data consistency in complex system design are solved, simplified representation of system functions and early problem exposure are realized, and system reliability and consistency are improved. .
Patent Information
- Application Number
- CN202210318439.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-29
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-03-29
AI Technical Summary
The existing system engineering methods have problems such as high learning threshold, complex design process, and difficulty in ensuring data consistency and integrity in complex system design. The existing methods cannot effectively replace the real situation during the verification stage, resulting in the loss of meaning of auxiliary design.
Using the system engineering design and verification method based on the fish bone model, by obtaining system-level static information and dynamic data flow, the system static composition structure diagram and functional point dynamic data flow chart are constructed, and consistent adjustments are made to ensure the system functions and tasks. Integrity and consistency to improve system reliability.
It lowers the threshold for engineering personnel to learn and use, simplifies system structure representation, can virtualize actual systems, simulate usage scenarios, expose design problems early, improve system reliability and consistency, and simplifies the verification process.
Smart Images

Figure CN114638042B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of system engineering, and in particular to a system engineering design and verification method and system based on a fishbone model. Background Art
[0002] As the engineering systems developed by people become more and more complex, traditional systems engineering (TSE) is becoming increasingly difficult to cope with. In traditional systems engineering, the output of systems engineering activities is a series of documents based on natural language, such as user requirements and design plans. This document is in "text format", so it can also be said that traditional systems engineering is "text-based systems engineering". In this model, it is time-consuming, labor-intensive and error-prone to integrate and link the information of engineering systems scattered in various demonstration reports, design reports, analysis reports, and test reports. Moreover, with the development of information technology, the complexity and scale of modern systems are constantly increasing. Traditional document-centric systems engineering has become increasingly unable to meet the needs of engineering due to many defects such as the inability to ensure data consistency, difficulty in making changes, and difficulty in describing activities.
[0003] At the same time, information technology represented by modeling is also developing rapidly. Therefore, driven by demand and technology, Model-Based Systems Engineering (MBSE) came into being. It puts the model at the center of the entire engineering process, and realizes the system design of the product through the continuous evolution and iterative increase of the model from the demand stage. Compared with traditional document-centric systems engineering, MBSE has many advantages, mainly including strengthening communication between investors and team members, improving the ability to acquire knowledge, having better information traceability, enhancing artifact reuse, and reducing development risks. The International Society for Systems Engineering pointed out that the model-driven system design method "is expected to replace the document-centric method used by system engineers for many years, and will eventually be fully integrated into the system engineering process."
[0004] The model-based system engineering method simplifies complex problems and achieves dimensionality reduction by describing one aspect of the problem; the model-based system engineering method gives a clear and comprehensive description of complex problems through the "connection" of multi-perspective models; the model-based system engineering method ignores unimportant details to reveal the essence of the problem; the model-based system engineering method expresses the problem in a form that is easier to observe and understand, enhancing knowledge acquisition, analysis intensity and completeness; the model-based system engineering method achieves the capture of knowledge and the maintenance of contact information through the establishment of multi-perspective models. This solves the problem of insufficient knowledge management capabilities and insufficient decision-making support of document-based requirements engineering methods.
[0005] At present, there are 6 mainstream MBSE methods, namely Harmony, RUP, OOSEM, MagicGrid, OPM, Arcadia and Vitech. These methods use UML, SysML, OPL, Arcadia and SDL system modeling languages for modeling. However, practice has proved that for complex system design, due to the overly complex syntax of UML, SysML, OPL, Arcadia and SDL, professional designers are required to have a high level of proficiency in methodology and tools, and designers need to spend a long time to learn and understand. Moreover, the modeling tools that implement the system engineering method have limited customization capabilities, a variety of graphics, and a relatively flexible modeling process, which often leads to confusion and confusion among engineers during architecture design.
[0006] In the related art, the invention patent application with publication number CN 101847170 A discloses an auxiliary design or verification method for system engineering, including: decomposing the system into smaller subsystems layer by layer according to the system specification or requirement description; decomposing the elements of the smallest functional unit; analyzing the attributes contained in the elements and the corresponding attribute values, and then counting the labels, resources, resource characteristics and structural information between the system or subsystem, elements and attributes; pairing all elements in pairs and defining the relationship between the paired elements and describing the various aspects of the relationship, and then counting the labels, resources, resource characteristics and structural information between the pairings, relationships, aspects; integrating the pairings and their relationships into components, selectively reorganizing and packaging them into combined flows, and counting the components, constraints as selection conditions, combined flows and their internal components, labels, resources, resource characteristics and structural information between each other. In this way, a comprehensive and complete analysis of the system is achieved. This method decomposes smaller subsystems and smallest functional unit elements according to the system specification or requirement description, and the textual expression content may be ambiguous, so the correctness of the decomposed smallest functional unit elements cannot be guaranteed. Secondly, for the system design stage, whether the method is implemented automatically or requires manual participation of designers, the decomposition, analysis and statistics process is too complicated. The abstract level of functions that can be achieved in the system design stage, the rationality of the attributes contained in the analyzed elements and the corresponding attribute values will be greatly reduced. Moreover, such complex and frequent decomposition, analysis, statistics, one-dimensional analysis and comparison, and two-dimensional analysis and comparison are also a great test for the operating efficiency of the system. Finally, for the instantiation process verification of this method, the instantiation simulation execution of the design factors from the beginning to the end not only increases the burden of system operation, but also no matter how complex the simulation is, it cannot replace and reproduce the real situation. However, the auxiliary design is so complicated that it loses its meaning.
[0007] The invention patent application with the publication number of CN 112560213 A discloses a system modeling method and system based on model system engineering and hypernetwork theory. The system modeling system based on model system engineering and hypernetwork theory includes: an application scenario determination module, an architecture determination module, an architecture verification module, an index determination module, a weight determination module, a central control module, an architecture model correction module, a data acquisition module, a data processing module, a data reference module, a system model output module, and a model conversion output module. By converting the constructed system model group into a hypernetwork model, analyzing the system model mapping relationship between each perspective, combining the generated system hypernetwork model group, and finally generating a multi-layer hypernetwork model of the architecture, it is convenient to use mathematical tools to quantify and analyze the indicators of the architecture. Through top-to-bottom combing and bottom-to-top integration, the integrity and validity of the combed data can be guaranteed. This method is targeted at specific fields. When used, the input of the system is to establish an application scenario. However, the form of establishing the application scenario and what elements need to be given are not specifically defined, which is not easy for implementers and users to understand and use, resulting in confusion and errors in operation information. Secondly, it is necessary to establish a scenario library and an architecture model library, and it is necessary to understand the properties and quantity of the corresponding architecture models. Therefore, establishing the two libraries requires a lot of specialized work and is not very universal. Summary of the invention
[0008] The technical problem to be solved by the present invention is how to provide a simple and accurate system engineering design and verification method and system based on the fishbone model.
[0009] The present invention solves the above technical problems through the following technical means:
[0010] On the one hand, the present invention proposes a system engineering design and verification method based on a fishbone model, the method comprising:
[0011] Acquiring modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow;
[0012] Based on the fishbone diagram, the system-level static information and the system task-level static information are represented as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram;
[0013] Based on the fishbone diagram, the system task-level dynamic data flow is represented as a system function point dynamic data flow diagram;
[0014] Based on the system task composition structure diagram, a static set of each software function module of the system is established, and based on the system function point dynamic data flow diagram, a dynamic set of each software function module of the system is established;
[0015] The software function modules in the static set and the software function modules in the dynamic set are adjusted for consistency until the software function modules in the static set and the software function modules in the dynamic set are consistent.
[0016] The present invention adopts a system engineering method based on the fishbone model, which is easier for engineers to get started, understand and use than the problem of the learning threshold of the existing MBSE method. Moreover, the static composition diagram of the system function based on the fishbone model, the static composition diagram of each system function and the dynamic data flow diagram of the system function point based on the fishbone model can make the structure of the system simple and clear, and can virtualize the actual system, simulate the use scenario, and the design of the system and its implementation software is effectively verified, which is conducive to exposing and discovering the design problems of the system as soon as possible. By comparing the dynamic data flow of each system function based on the fishbone model with the static composition structure diagram of each system function, the integrity, consistency and traceability between the system function and the software that realizes the system task are guaranteed, and the verification of the system data flow is strengthened, which is conducive to the early discovery of software problems and can effectively improve the reliability of the system.
[0017] Furthermore, the system-level static information includes a system name graphic element and a system task graphic element;
[0018] The system task level static information includes the name element of the system task and the name element of the software function module;
[0019] The system task level dynamic data flow includes the name element of the system task, the name element of the software and the name element of the software function module.
[0020] Further, based on the fishbone diagram, the system-level static information and the system task-level static information are represented as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram, including:
[0021] Placing the name graphic element of the system at the end point of a horizontal straight line in a fishbone diagram as the head of the fishbone, and listing the name graphic elements of the system tasks on the oblique line segment of the fishbone diagram to form a static composition structure diagram of the system;
[0022] For each system task in the system static composition structure diagram, the name graphic element of the system task is placed at the end point of a horizontal straight line in a fishbone diagram as the fishbone head, and the name graphic elements of the software function modules used to implement the system task are listed on the oblique line segment of the fishbone diagram to form the system task composition structure diagram.
[0023] Furthermore, based on the fishbone diagram, the system task-level dynamic data flow is represented as a system function point dynamic data flow diagram, including:
[0024] The system task is represented by a horizontal straight line with an arrow, and the name graphic element of the system task is placed at the end point of the horizontal straight line in a fishbone diagram as the fishbone head;
[0025] List the software name graphic element on the oblique line segment in the corresponding fishbone diagram, wherein the corresponding fishbone diagram is a fishbone diagram with the corresponding system task name graphic element as the fishbone head;
[0026] The name graphic elements of the software function modules are listed on the oblique line segments in the corresponding fishbone diagram, and the corresponding fishbone diagram is a fishbone diagram with the name graphic elements of the corresponding software as the fishbone head.
[0027] Furthermore, the order of the name element of the system task, the name element of the software and the name element of the software function module is consistent with the execution order of the system;
[0028] When the software or the software functional modules are in a parallel relationship in terms of time sequence, the horizontal straight line with an arrow connecting the software or the software functional modules is represented by a dotted line.
[0029] Furthermore, the static set of each software function module of the system is established based on the system task composition structure diagram, and the dynamic set of each software function module of the system is established based on the system function point dynamic data flow diagram, including:
[0030] Based on the system task composition structure diagram, a static set A of each software function module of the system is established. k , k represents the total number of software functional modules in the static set;
[0031] Based on the dynamic data flow diagram of the system function points, a dynamic set A of each software function module of the system is established. n , n represents the total number of software functional modules in the dynamic set.
[0032] Further, the adjusting the consistency of the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent includes:
[0033] According to the priority ranking of each software function module in the static set, a weight determination model is adopted to determine the weight of each software function module, wherein the formula of the weight determination model is expressed as:
[0034]
[0035] m i ∈A k, and m1>m2>…>m k
[0036] Among them, A k Represents a static set, m1, m2, ..., m k Respectively represent the weight of each software function module in the static set, and k represents the total number of software function modules in the static set;
[0037] According to the consistency determination model, the software function modules in the static set and the software function modules in the dynamic set are adjusted for consistency. The formula of the consistency determination model is expressed as:
[0038]
[0039]
[0040]
[0041] Wherein, n and k are both positive integers, n represents the total number of software function modules in the dynamic set, Indicates the weight of each corresponding software function module in the static set;
[0042] When Z=1 is satisfied, it is determined that the software function modules in the static set are consistent with the software function modules in the dynamic set, and a system engineering level review is performed.
[0043] Furthermore, the step of determining the weight of each software function module by using a weight determination model according to the priority ranking of each software function module in the static set includes:
[0044] Based on the convergence concept, the software function modules in the static set are ranked in descending order of priority in a ratio of 1 / k, and the weights of the software function modules are determined as follows:
[0045] m1=(k-1)*k k-1 / k k -1, i=1
[0046] m i =m1*1 / k i-1 , i≠1, and i≤k.
[0047] Furthermore, the method further comprises:
[0048] When Z>1, changing the functional modules in the static set or the functional modules in the dynamic set until Z≤1 is satisfied;
[0049] When Z<1, the functional modules in the static set or the functional modules in the dynamic set are changed until Z=1 is satisfied.
[0050] In addition, the present invention also proposes a system engineering design and verification system based on the fishbone model, the system comprising:
[0051] An information acquisition module, used to acquire modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow;
[0052] A first information representation module is used to represent the system-level static information and the system task-level static information as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram based on a fishbone diagram;
[0053] A second information representation module is used to represent the system task-level dynamic data flow as a system function point dynamic data flow diagram based on a fishbone diagram;
[0054] A set determination module, used to establish a static set of each software function module of the system based on the system task composition structure diagram, and to establish a dynamic set of each software function module of the system based on the system function point dynamic data flow diagram;
[0055] The consistency determination module is used to adjust the consistency of the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent.
[0056] The advantages of the present invention are:
[0057] (1) The present invention adopts a system engineering method based on the fishbone model. Compared with the learning threshold of the existing MBSE method, it is easier for engineers to get started, understand and use it. In addition, the static composition diagram of system functions based on the fishbone model, the static composition diagram of each system function and the dynamic data flow diagram of system function points based on the fishbone model can make the structure of the system simple and clear, and can virtualize the actual system, simulate the usage scenario, and effectively verify the design of the system and its implementation software, which is conducive to exposing and discovering the design problems of the system as early as possible. By comparing the dynamic data flow of each system function based on the fishbone model with the static composition structure diagram of each system function, the integrity, consistency and traceability between the system function and the software that realizes the system task are guaranteed, and the verification of the system data flow is strengthened, which is conducive to the early discovery of software problems and can effectively improve the reliability of the system.
[0058] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0059] Figure 1 It is a flow chart of the system engineering design and verification method based on the fishbone model in the present invention;
[0060] Figure 2 It is a schematic diagram of the static composition structure of the system function based on the model in the present invention;
[0061] Figure 3 It is a schematic diagram of the static composition structure of each system function in the present invention;
[0062] Figure 4 It is a schematic diagram of a dynamic data flow based on system function points in the present invention;
[0063] Figure 5 It is a schematic diagram of the set of definitions of the icons in the present invention;
[0064] Figure 6 It is a schematic diagram of the static composition structure of the link communication system level in the present invention;
[0065] Figure 7 It is a schematic diagram of the static composition structure of the link communication system task in the present invention;
[0066] Figure 8 It is a dynamic data flow diagram of the link communication system task in the present invention;
[0067] Fig. 9 It is a schematic diagram of the static composition of the parking access control system in the present invention;
[0068] Fig.10 It is a schematic diagram of the static composition structure of the parking access control system task in the present invention;
[0069] Fig.11 It is a dynamic data flow diagram of the parking access control system task in the present invention;
[0070] Fig.12 It is a structural schematic diagram of the system engineering design and verification system based on the fishbone model in the present invention. DETAILED DESCRIPTION
[0071] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in combination with the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0072] Reference Figure 1An embodiment of the present invention provides a system engineering design and verification method based on a fishbone model, the method comprising the following steps:
[0073] S10, acquiring modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow;
[0074] S20, based on the fishbone diagram, representing the system-level static information and the system task-level static information as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram;
[0075] S30, based on the fishbone diagram, representing the system task-level dynamic data flow as a system function point dynamic data flow diagram;
[0076] S40, establishing a static set of each software function module of the system based on the system task composition structure diagram, and establishing a dynamic set of each software function module of the system based on the system function point dynamic data flow diagram;
[0077] S50: Perform consistency adjustment on the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set are consistent with the software function modules in the dynamic set.
[0078] It should be noted that the present invention adopts a system engineering method based on the fishbone model, which is easier for engineers to get started, understand and use than the problem of the learning threshold of the existing MBSE method. Moreover, the static composition diagram of the system function based on the fishbone model, the static composition diagram of each system function and the dynamic data flow diagram of the system function point based on the fishbone model can make the structure of the system simple and clear, and can virtualize the actual system, simulate the use scenario, and the design of the system and its implementation software is effectively verified, which is conducive to exposing and discovering the design problems of the system as soon as possible. By comparing the dynamic data flow of each system function based on the fishbone model with the static composition structure diagram of each system function, the integrity, consistency and traceability between the system function and the various software that realizes the system task are guaranteed, and the verification of the system data flow is strengthened, which is conducive to the early discovery of software problems and can effectively improve the reliability of the system.
[0079] In one embodiment, in step S10, the system-level static information includes a system name graphic element and a system task graphic element;
[0080] The system task level static information includes the name element of the system task and the name element of the software function module;
[0081] The system task level dynamic data flow includes the name element of the system task, the name element of the software and the name element of the software function module.
[0082] It should be noted that the modeling information in this embodiment can be the primitives in the self-developed tool. The Qt GraphicsView framework structure is used to provide primitive-based model view programming. The framework includes three main classes, namely, QGraphicsScene scene class, QGraphicsView view class and QGraphItem primitive class. A scene can be represented by multiple views, and a scene includes multiple geometric figures. The Qt GraphicsView framework structure is used to define and generate the primitives of the system.
[0083] In one embodiment, the step S20 includes the following steps:
[0084] S21, placing the name graphic element of the system at the end point of a horizontal straight line in a fishbone diagram as the head of the fishbone, and listing the name graphic elements of the system tasks on the oblique line segment of the fishbone diagram to form a static composition structure diagram of the system;
[0085] S22. For each system task in the system static composition structure diagram, place the name graphic element of the system task at the end point of a horizontal straight line in a fishbone diagram as the fishbone head, and list the name graphic elements of the software function modules used to implement the system task on the oblique line segment of the fishbone diagram to form the system task composition structure diagram.
[0086] It should be noted that, based on the fishbone model, the information data of various elements of system functions and their software components are established. Its unified architecture can be expressed as follows: the software name element is represented by a horizontal straight line, and the name element of the software function module is represented by a slash segment connected to the horizontal straight line of the software name element. The specific modeling is as follows:
[0087] Reference Figure 2 The system-level static information consists of the system and the tasks that the system needs to complete. The name graphic element of the system is placed at the head of the fishbone as the end point of the horizontal line, and the name graphic elements of the system tasks that the system needs to complete are listed on the fishbone represented by the oblique line segment.
[0088] Reference Figure 3 The system task-level static information consists of the system tasks that the system needs to complete and the various software and their functions that make up the system. The name graphic element of the system task is placed at the head of the fishbone as the end point of the horizontal line, and the software required for the task and the name graphic elements of certain aspects of its implementation are listed on the fishbone represented by the slash segment.
[0089] In one embodiment, the step S30 includes the following steps:
[0090] S31, using a horizontal straight line with an arrow to represent the system task, and placing the name graphic element of the system task at the end point of the horizontal straight line in a fishbone diagram as the fishbone head;
[0091] S32, listing the name graphic element of the software on the oblique line segment in the corresponding fishbone diagram, where the corresponding fishbone diagram is a fishbone diagram with the name graphic element of the corresponding system task as the fishbone head;
[0092] S33, listing the name graphic elements of the software function modules on the oblique line segments in the corresponding fishbone diagram, wherein the corresponding fishbone diagram is a fishbone diagram with the name graphic elements of the corresponding software as the fishbone head.
[0093] It should be noted that, refer to Figure 4 Based on the fishbone model, the system task-level dynamic data flow is represented as a system function point dynamic data flow chart. Its unified architecture can be represented as follows: the tasks that the system needs to complete are represented by a horizontal straight line with an arrow pointing from left to right; the various software that constitute the system are represented by arrowed line segments that are diagonally directed from points on the horizontal straight line with an arrow; the various functional modules that implement the software are represented by arrowed line segments that are diagonally directed from a point outside the software line segment that constitutes the system. The name primitive of the system task is placed at the head of the fishbone as the end point of the horizontal straight line; the name primitives of the required software are listed on the fishbone represented by the diagonal line segment with the name primitive of the system task as the head; the name primitives of the software functional modules are listed on the fishbone represented by the diagonal line segment with the name primitive of the software as the head.
[0094] In one embodiment, the order of the name element of the system task, the name element of the software and the name element of the software function module is consistent with the execution order of the system;
[0095] When the software or the software functional modules are in a parallel relationship in terms of time sequence, the horizontal straight line with an arrow connecting the software or the software functional modules is represented by a dotted line.
[0096] It should be noted that the name elements of each software or the name elements of each functional module of the software connected by the dotted line represent a parallel relationship in time sequence, that is, there is no order of input and output of its functional points. For the input and output messages between the functional modules of each software in the dynamic data flow diagram of the system task, the output messages between each software are represented by digital codes, and the final output of the system task is identified by the output message name. The input messages between each software are identified by "the digital code of the associated output message + the input message name", and the initial input of the system task is identified by the input message name.
[0097] In one embodiment, the step S40 includes the following steps:
[0098] Based on the system task composition structure diagram, a static set A of each software function module of the system is established. k , k represents the total number of software functional modules in the static set;
[0099] Based on the dynamic data flow diagram of the system function points, a dynamic set A of each software function module of the system is established. n , n represents the total number of software functional modules in the dynamic set.
[0100] It should be noted that k and n here both represent positive integers.
[0101] In one embodiment, the step S50 includes the following steps:
[0102] S51, according to the priority ranking of each software function module in the static set, using a weight determination model to determine the weight of each software function module, wherein the formula of the weight determination model is expressed as:
[0103]
[0104] m i ∈A k , and m1>m2>…>m k
[0105] Among them, A k Represents a static set, m1, m2, ..., m k Respectively represent the weight of each software function module in the static set, and k represents the total number of software function modules in the static set;
[0106] It should be noted that the priority of the software function modules here is automatically or manually sorted. The automatic priority sorting can be understood as the process of constructing the system task composition structure diagram, which is composed according to the priority of the software function modules, with the high priority placed in the front and the low priority placed in the back; the manual priority sorting can be determined by expert evaluation methods, such as determining the priority of the software function module according to the number of times the software function module appears in each system task, the more times it appears, the higher its priority; secondly, for software function modules with the same number of appearances, their priority is determined according to the order of appearance of the software function modules. Specifically, if the software function modules appear in different system task fishbone diagrams, the system task fishbone diagram that appears first is considered to have a higher priority; if the software function modules appear in the same system task fishbone diagram, the software function module in the front of the time sequence is considered to have a higher priority.
[0107] S52: According to a consistency determination model, consistency adjustment is performed on the software function modules in the static set and the software function modules in the dynamic set. The formula of the consistency determination model is expressed as:
[0108]
[0109]
[0110]
[0111] Wherein, n and k are both positive integers, n represents the total number of software function modules in the dynamic set, Indicates the weight of each corresponding software function module in the static set;
[0112] It should be noted that for software function modules in the dynamic set that exist in the static set, that is, m i ∈A k and i≤n, then the weight values m1, m2, ..., m of each software implementation module set in the static composition information are assigned k , here we use Indicates. For software function modules in the dynamic set that do not exist in the static set, the total number of software function modules k in the static set is directly used as a penalty factor and assigned to the software function modules that exist in the dynamic set but not in the static set. The penalty factor is set to the total number of software function modules. The purpose is that when the weighted sum is greater than 1, it means that there must be functions in the dynamic design that are not in the static design function set. The extra functions may bring greater risks to the system, such as failures and crashes, and will inevitably bring redundancy to the system. Therefore, the handling of the extra functions must be taken seriously and carefully, and the extra functions in the dynamic design need to be analyzed to ensure the consistency of the system design.
[0113] S53: When Z=1 is satisfied, determine that the software function modules in the static set are consistent with the software function modules in the dynamic set, and perform a system engineering level review.
[0114] It should be noted that when Z=1, it indicates that the system functional logic design is complete and consistent, and a system engineering-level review can be conducted. After the review is passed, the system detailed design and implementation work can be carried out.
[0115] In this embodiment, after setting a weight value for each functional module in the static set, it is compared with each functional module in the dynamic set to determine the consistency of each functional module of the static design and each functional module of the dynamic design. If a functional module in the dynamic set already exists in a static functional module set with a weight value, the dynamic functional module is calibrated to the weight value assigned in the static set; if it does not exist in the static functional module set with a weight value, it is calibrated to the total number of software functional modules in the static set.
[0116] In this way, the consistency and completeness of the two sets can be determined by weighted sum. If it is 1, it can be determined that the functions of the dynamic design are consistent and complete with the static design functions, and there are no redundant functions or missing functions; if it is greater than 1, it can be concluded that there must be redundant functions in the dynamic design functions, and it is necessary to go back to the static design process, analyze and find the cause of the problem, and modify the static design drawing or the dynamic design drawing until it is 1; if it is less than 1, it can be concluded that there must be missing functions in the dynamic design functions, and it is necessary to go back to the static design process, analyze and find the cause of the problem, and modify the static design drawing or the dynamic design drawing until it is 1.
[0117] In one embodiment, the step S51 is specifically as follows:
[0118] Based on the convergence normalization concept, the software function modules in the static set are ranked in descending order of priority in a ratio of 1 / k, and the weights of the software function modules are determined as follows:
[0119] m1=(k-1)*k k-1 / k k -1, i=1
[0120] m i =m1*1 / k i-1 , i≠1, and i≤k.
[0121] It should be noted that according to the convergence idea, the criticality can be reduced in the order of priority by a ratio of 1 / k, that is, m1 has the highest weight, and its criticality factor value is (k-1)*k k-1 / k k -1, m k The weight is the lowest, and its criticality factor value is m1*1 / k k-1 , other i ∈A i The weight calculation formula is m1*1 / k i-1 ; When k=1, then m1=1.
[0122] It should be noted that the current common consistency and integrity verification is judged by observing whether the dynamic execution of all state diagrams can reach the end. This dynamic verification method increases the complexity of the operation when used, and a lot of work needs to be done to achieve the dynamic verification effect. Once there is a problem in the operation process, rather than a design problem, it will also cause all state diagrams to fail to execute to the end, which brings difficulties to the location and troubleshooting of the problem. The advantage of adopting the convergence normalization idea is that, first of all, the consistency of the dynamic design process set and the static design process set elements can be accurately determined. And the additional operations to be performed to build dynamic execution are omitted, avoiding the problems and impacts caused by building dynamic execution operations. It greatly reduces the workload of designers and improves work efficiency.
[0123] In one embodiment, the method further comprises the following steps:
[0124] When Z>1, changing the functional modules in the static set or the functional modules in the dynamic set until Z≤1 is satisfied;
[0125] When Z<1, the functional modules in the static set or the functional modules in the dynamic set are changed until Z=1 is satisfied.
[0126] It should be noted that when Z>1, it means that the system function logic design is unreasonable, that is, the software function in the dynamic data flow information of each system function, and gives the possible error point elements, that is, A n -{A n ∩A k} elements in the set, that is, the elements in the information element that only appear in the dynamic data flow information of each system function, but not in the static composition information of each system task. Manual processing is performed according to the dispute point, and the dynamic data flow information of each system function or the dynamic data flow information of each system function is changed until Z≤1; when Z<1, it means that the logical design of the system function is unreasonable, that is, the software function in the dynamic data flow information of each system function, and the missing information elements in the dynamic data flow information of each system function are given, that is, A k -A n The elements in the set, that is, the elements in the information elements, which only appear in the static composition information of each system task, but not in the dynamic data flow information of each system function. Manual processing is performed according to the dispute points, and the dynamic data flow information of each system function or the dynamic data flow information of each system function is changed until Z=1.
[0127] The present embodiment designs a lightweight and universal system engineering design method. System designers only need to follow the method of the present patent to sequentially establish a schematic diagram of the static composition structure of the system based on the fishbone model, a static composition structure diagram of the system function to realize the system, and a dynamic data flow diagram based on the system function point, which is in line with the development process and design ideas, and does not add extra work. In view of this problem, by combining the fishbone diagram frequently used in engineering as a carrier, the application meaning is adaptively transformed, and its specific form of expression and meaning are strictly defined, thereby realizing a model set based on fishbones suitable for various situations of system engineering design. The concept and understanding are unified, which facilitates the realization of subsequent data processing. The present patent uses a static analysis method to sequentially establish a schematic diagram of the static composition structure of the system based on the fishbone model, a static composition structure diagram of the system function to realize the system, and a dynamic data flow diagram based on the system function point, without adding extra work, to analyze the inconsistency and incompleteness problems, thereby reducing the workload. And the method proposed in the present embodiment can be used and implemented in the system engineering design process stage.
[0128] It should be understood that the system engineering design and verification method based on the fishbone model proposed in this implementation is the same as the application scenario of MBSE. The following two specific examples are used to illustrate the design of the link communication system engineering and the design of the parking access control system. The design and verification steps include:
[0129] Embodiment 1:
[0130] (1) On the self-developed tool, construct a link communication system-level static composition structure diagram, such as Figure 6 As shown, the meaning of the icons is specified in the schematic diagram as follows Figure 5 As shown. The link communication system is composed of link communication tasks, and its system name (i.e., link communication system) is placed at the head of the fishbone as the end point of the horizontal straight line, and the system task name (link communication function) is listed on the fishbone represented by the slash segment; the system name icon is represented by a horizontal straight line, and the system task name icon is represented by a slash segment connected to the horizontal straight line of the system name icon;
[0131] (2) On the self-developed tool, a static structure diagram of the link communication system task is constructed, such as Figure 7As shown. The link communication system task diagram is composed of various software and software functions that realize the system task. The link communication system task name is placed at the head of the fishbone as the end point of the horizontal straight line, and the software names and software function names that realize the system task are listed on the fishbone represented by the slash segment. The link communication system task composition structure diagram is composed of various software names (monitoring software, data management software, control software and data processing software) and software function point names (link function of monitoring software, link function of data management software, link function of control software and link function of data processing software). The link communication system task name is placed at the head of the fishbone as the end point of the horizontal straight line, and the software function point names are listed on the fishbone represented by the slash segment;
[0132] (3) On the self-developed tool, construct a dynamic data flow diagram of the link communication system task, such as Figure 8 As shown. The dynamic data flow icon of the link communication system task includes the system task name (link communication system task), the names of various software (monitoring sub-software, data management software, control software and data processing software), the names of software function points (link function of monitoring software, link function of data management software, link function of control software and link function of data processing software) and software function point input and output (monitoring software input: link inquiry; data management software input: link inquiry; control software input: link inquiry and signal processing software input: link inquiry; and monitoring software output: link response; data management software output: link response; control software output: link response and signal processing software output: link response). Among them, the system task name (link communication system task) icon is represented by a horizontal straight line with an arrow pointing from left to right. The icons of each software name (monitoring software, data management software, control software and data processing software) are represented by a line segment that leads obliquely from a point on the straight line to the straight line, and the icons of software function point names (link function of monitoring software, link function of data management software, link function of control software and link function of data processing software) are represented by arrow line segments that lead from points on the arrow line segments of each software name icon to each software name icon. The icons of each software function point input (monitoring software link function input: link inquiry; data management software link function input: link inquiry; control software link function input: link inquiry and signal processing software link function input: link inquiry) are represented by arrow line segments that lead to the software function point name icons. The software function point output icons (monitoring software link function output: link response; data management software link function output: link response; control software link function output: link response and signal processing software link function output: link response) are represented by arrow line segments that lead out of the software function point name icons. In addition, the dotted line portion in the straight line of the system task name icon indicates that the software function points connected on the dotted line are in a parallel relationship in terms of time sequence, that is, there is no order of priority between the input and output of the function points.
[0133] (4) According to the extracted static composition information of the system tasks, automatically complete the priority sorting of each software implementation module, and establish the weight setting of each software implementation module according to the priority order. Among them, the automatic priority sorting implementation method of each software module is to establish a static set of each software function module of the system A4 = {link function of monitoring software, link function of control software, link function of data management software, link function of data processing software} according to the established static composition information of each system task. Because each software function point appears the same number of times in the fishbone model, its priority is determined according to the order of appearance of the software function, and the weight of each software function point is obtained: m 监控软件的链路功能 =192 / 255, m 控制软件的链路功能 =48 / 255, m 数据管理软件的链路功能 =12 / 255, m 数据处理软件的链路功能 =3 / 255.
[0134] (5) Make a logical correctness judgment based on the extracted dynamic data flow information of each system function.
[0135] according to and principle, The system function weights in the dynamic data flow information of each system function are accumulated, and the value is Z=1. Therefore, the system functions and the various software that implement the system tasks meet the integrity and consistency requirements, the system design logic is reasonable, and the impact range is controllable.
[0136] Example 2
[0137] The following is a specific example of the design of a parking access control system. The design and verification steps include:
[0138] (1) On the self-developed tool, a static structure diagram of the parking access control system is constructed, such as Fig. 9 As shown. The parking access control system consists of entry control and exit control, and its system name (i.e., parking access control system) is placed at the head of the fishbone as the end point of the horizontal straight line, and the system task names (entry control function and exit control function) are listed on the fishbone represented by the oblique line segment; the system name icon is represented by a horizontal straight line, and the system task name icon is represented by an oblique line segment connected to the horizontal straight line of the system name icon;
[0139] (2) On the self-developed tool, a static structure diagram of the parking access control system task is constructed, such as Fig.10As shown. The entry control system task diagram consists of various software and software functions that realize the system task, and the name of the entry control system task is placed at the head of the fishbone as the end point of the horizontal straight line, and the names of various software and software functions that realize the system task are listed on the fishbone represented by the slash segment. The entry control system task composition structure diagram consists of various software names (monitoring software and control software) and software function point names (visitor arrival identification function, door access opening function and parking space full prompt function), and the name of the entry control system task is placed at the head of the fishbone as the end point of the horizontal straight line, and the software function point names are listed on the fishbone represented by the slash segment; the departure control system task composition structure diagram consists of various software names (monitoring software and control software) and software function point names (visitor arrival identification function and door access opening function), and the name of the departure control system task is placed at the head of the fishbone as the end point of the horizontal straight line, and the software function point names are listed on the fishbone represented by the slash segment;
[0140] (3) On the self-developed tool, a dynamic data flow diagram of the parking access control system task is constructed, such as Fig.10 As shown. The dynamic data flow icon of the parking access control system task includes the system task name (enter control system task and exit control system), the software name (monitoring software and control software), the software function point name (visitor arrival recognition function, door opening function and parking space full prompt function) and software function point input and output (monitoring software input: scan visitor arrival; control software input: visitor arrival information; and monitoring software output: visitor arrival information; control software output: door opening or full prompt). Among them, the system task name (enter control system task and exit control system) icon is represented by a horizontal straight line with an arrow pointing from left to right. The icons of each software name (monitoring software and control software) are represented by a line segment diagonally leading from a point on the straight line to the straight line, and the software function point name (visitor arrival recognition function, door opening function and parking space full prompt function) icons are represented by arrow line segments leading from points on the arrow line segments of each software name icon to each software name icon. The input icons of each software function point (monitoring software input: scan visitor arrival; control software input: visitor arrival information) are represented by arrow line segments leading to the software function point name icons. The output icon of the software function point (monitoring software output: visitor arrival information; control software output: open the door or prompt that it is full) is represented by an arrow line segment leading to the software function point name icon. In addition, the dotted line in the straight line of the system task name icon indicates that the software function points connected on the dotted line are in a parallel relationship in time sequence, that is, the input and output of the function point have no order.
[0141] (4) According to the extracted static composition information of the system tasks, the priority of each software implementation module is automatically sorted, and the weight setting of each software implementation module is established according to the priority order. Among them, the automatic priority sorting implementation method of each software module is to establish a static set of each software function module of the system A4 = {visitor arrival recognition function of the monitoring software, remaining position recognition function of the control software, door access opening function when there is a remaining position of the control software, full prompt function when there is no remaining position of the control software, door access opening function of the control software} according to the established static composition information of each system task. Because each software function point appears the same number of times in the fishbone model, the priority of the software functions is determined according to the order of appearance, and the weight of each software function point is obtained: the visitor arrival recognition function of the m monitoring software = 2500 / 3124, the remaining position recognition function of the m control software = 500 / 3124, the door access opening function when there are remaining positions of the m control software = 100 / 3124, the full prompt function when there are no remaining positions of the m control software = 20 / 3124, and the door access opening function of the m control software = 4 / 3124.
[0142] (5) According to the extracted dynamic data flow information of each system function, make a logical correctness judgment. and principle, The system function weights in the dynamic data flow information of each system function are accumulated, and the value is Z=1. Therefore, the system functions and the various software that implement the system tasks meet the integrity and consistency requirements, the system design logic is reasonable, and the impact range is controllable.
[0143] This embodiment solves the arbitrariness of the traceability relationship between the system and the software that implements the system tasks through dynamic data flow analysis based on system tasks, static composition structure analysis of system tasks and static composition structure analysis of the system, and ensures the integrity and consistency between the system functions and the software that implements the system tasks; by comparing the dynamic data flow of each system function based on the fishbone model with the static composition structure diagram of each system function, the design of the system and its implementation software can be effectively verified, ensuring the rigor and non-ambiguity of the design, reasonable structure, and easy maintenance and upgrading in the future.
[0144] Moreover, the system engineering method based on the fishbone model solves the learning threshold of the existing MBSE method, making it easier for engineers to get started, understand and use it. The static composition diagram of system functions based on the fishbone model, the static composition diagram of each system function and the dynamic data flow diagram of system function points based on the fishbone model can make the system structure simple and clear, and can simulate the actual system, simulate the usage scenario, and verify the system design logic and impact, which is conducive to exposing and discovering system design problems as early as possible.
[0145] In addition, refer to Fig.12Another embodiment of the present invention further proposes a system engineering design and verification system based on the fishbone model, the system comprising:
[0146] An information acquisition module 10, used to acquire modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow;
[0147] A first information representation module 20, for representing the system-level static information and the system-task-level static information as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram based on a fishbone diagram;
[0148] A second information representation module 30 is used to represent the system task-level dynamic data flow as a system function point dynamic data flow diagram based on a fishbone diagram;
[0149] A set determination module 40, used to establish a static set of each software function module of the system based on the system task composition structure diagram, and to establish a dynamic set of each software function module of the system based on the system function point dynamic data flow diagram;
[0150] The consistency determination module 50 is used to adjust the consistency of the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent.
[0151] In one embodiment, the modeling information acquired by the information acquisition module 10 is specifically as follows: the system-level static information includes the name element of the system and the element of the system task;
[0152] The system task level static information includes the name element of the system task and the name element of the software function module;
[0153] The system task level dynamic data flow includes the name element of the system task, the name element of the software and the name element of the software function module.
[0154] In one embodiment, the first information representation module 20 specifically includes:
[0155] The system static composition representation unit is used to place the name element of the system at the end point of a horizontal straight line in a fishbone diagram as the fishbone head, and list the name elements of the system tasks on the oblique line segment of the fishbone diagram to form the system static composition structure diagram;
[0156] The system task composition representation unit is used to place the name graphic element of each system task in the system static composition structure diagram at the end point of a horizontal line in a fishbone diagram as the fishbone head, and to list the name graphic elements of the software function modules used to implement the system task on the oblique line segment of the fishbone diagram to form the system task composition structure diagram.
[0157] In one embodiment, the second information representation module 30 specifically includes:
[0158] A first representation unit is used to represent the system task with a horizontal straight line with an arrow, and to place the name graphic element of the system task at the end point of the horizontal straight line in a fishbone diagram as the fishbone head;
[0159] A second representation unit is used to list the name graphic element of the software on the oblique line segment in the corresponding fishbone diagram, where the corresponding fishbone diagram is a fishbone diagram with the name graphic element of the corresponding system task as the fishbone head;
[0160] The third representation unit is used to list the name graphic element of the software function module on the oblique line segment in the corresponding fishbone diagram, and the corresponding fishbone diagram is a fishbone diagram with the name graphic element of the corresponding software as the fishbone head.
[0161] In one embodiment, the order of the name element of the system task, the name element of the software and the name element of the software function module is consistent with the execution order of the system;
[0162] When the software or the software functional modules are in a parallel relationship in terms of time sequence, the horizontal straight line with an arrow connecting the software or the software functional modules is represented by a dotted line.
[0163] It should be noted that the name elements of each software or the name elements of each functional module of the software connected by the dotted line represent a parallel relationship in time sequence, that is, there is no order of input and output of its functional points. For the input and output messages between the functional modules of each software in the dynamic data flow diagram of the system task, the output messages between each software are represented by digital codes, and the final output of the system task is identified by the output message name. The input messages between each software are identified by "the digital code of the associated output message + the input message name", and the initial input of the system task is identified by the input message name.
[0164] In one embodiment, the set determination module 40 specifically includes:
[0165] A static set determination unit is used to establish a static set A of each software function module of the system based on the system task composition structure diagram. k , k represents the total number of software functional modules in the static set;
[0166] A dynamic set determination unit is used to establish a dynamic set A of each software function module of the system based on the dynamic data flow diagram of the system function point. n , n represents the total number of software functional modules in the dynamic set.
[0167] In one embodiment, the consistency determination module 50 specifically includes:
[0168] The weight assignment module is used to determine the weight of each software function module according to the priority ranking of each software function module in the static set, using a weight determination model, wherein the formula of the weight determination model is expressed as:
[0169]
[0170] m i ∈A k , and m1>m2>…>m k
[0171] Among them, A k Represents a static set, m1, m2, ..., m k Respectively represent the weight of each software function module in the static set, and k represents the total number of software function modules in the static set;
[0172] After setting weight values for each functional module in the static set, the function modules in the dynamic set are compared to determine the consistency between the functional modules of the static design and the functional modules of the dynamic design. If a functional module in the dynamic set already exists in a static functional module set with a weight value, the dynamic functional module is calibrated to the weight value assigned in the static set. If it does not exist in a static functional module set with a weight value, it is calibrated to the total number of software functional modules in the static set.
[0173] In this way, the consistency and completeness of the two sets can be determined by weighted sum. If it is 1, it can be determined that the functions of the dynamic design are consistent and complete with the static design functions, and there are no redundant functions or missing functions; if it is greater than 1, it can be concluded that there must be redundant functions in the dynamic design functions, and it is necessary to go back to the static design process, analyze and find the cause of the problem, and modify the static design drawing or the dynamic design drawing until it is 1; if it is less than 1, it can be concluded that there must be missing functions in the dynamic design functions, and it is necessary to go back to the static design process, analyze and find the cause of the problem, and modify the static design drawing or the dynamic design drawing until it is 1.
[0174] It should be noted that the priority of the software function modules here is automatically or manually sorted. The automatic priority sorting can be understood as the process of constructing the system task composition structure diagram, which is composed according to the priority of the software function modules, with the high priority placed in the front and the low priority placed in the back; the manual priority sorting can be determined by expert evaluation methods, such as determining the priority of the software function module according to the number of times the software function module appears in each system task, the more times it appears, the higher its priority; secondly, for software function modules with the same number of appearances, their priority is determined according to the order of appearance of the software function modules. Specifically, if the software function modules appear in different system task fishbone diagrams, the system task fishbone diagram that appears first is considered to have a higher priority; if the software function modules appear in the same system task fishbone diagram, the software function module in the front of the time sequence is considered to have a higher priority.
[0175] The consistency determination unit is used to perform consistency adjustment on the software function modules in the static set and the software function modules in the dynamic set according to the consistency determination model, wherein the formula of the consistency determination model is expressed as:
[0176]
[0177]
[0178]
[0179] Wherein, n and k are both positive integers, n represents the total number of software function modules in the dynamic set, Indicates the weight of each corresponding software function module in the static set;
[0180] It should be noted that for software function modules in the dynamic set that exist in the static set, that is, m i ∈A k and i≤n, then the weight values m1, m2, ..., m of each software implementation module set in the static composition information are assigned k , here we use Indicates. For software function modules in the dynamic set that do not exist in the static set, the total number of software function modules k in the static set is directly used as a penalty factor and assigned to the software function modules that exist in the dynamic set but not in the static set. The penalty factor is set to the total number of software function modules. The purpose is that when the weighted sum is greater than 1, it means that there must be functions in the dynamic design that are not in the static design function set. The extra functions may bring greater risks to the system, such as failures and crashes, and will inevitably bring redundancy to the system. Therefore, the handling of the extra functions must be taken seriously and carefully, and the extra functions in the dynamic design need to be analyzed to ensure the consistency of the system design.
[0181] The determination unit is used to determine that the software function modules in the static set are consistent with the software function modules in the dynamic set when Z=1 is satisfied, and perform a system engineering level review.
[0182] It should be noted that when Z=1, it indicates that the system functional logic design is complete and consistent, and a system engineering-level review can be conducted. After the review is passed, the system detailed design and implementation work can be carried out.
[0183] In one embodiment, the weight assignment unit is specifically used to:
[0184] At present, the usual consistency and integrity verification is judged by observing whether the dynamic execution of all state diagrams can reach the end. This dynamic verification method increases the complexity of operation when used, and a lot of work needs to be done to achieve the dynamic verification effect. Once there is a problem in the operation process, rather than a design problem, it will also cause all state diagrams to fail to execute to the end, which brings difficulties to the location and troubleshooting of the problem. The advantage of adopting the convergence normalization idea is that, first of all, the consistency of the dynamic design process set and the static design process set elements can be accurately determined. And the additional operations to be performed to build dynamic execution are omitted, avoiding the problems and impacts caused by building dynamic execution operations. It greatly reduces the workload of designers and improves work efficiency.
[0185] Based on the convergence concept, the software function modules in the static set are ranked in descending order of priority in a ratio of 1 / k, and the weights of the software function modules are determined as follows:
[0186] m1=(k-1)*k k-1 / k k -1, i=1
[0187] m i =m1*1 / k i-1 , i≠1, and i≤k.
[0188] It should be noted that according to the convergence idea, the criticality can be reduced in the order of priority by a ratio of 1 / k, that is, m1 has the highest weight, and its criticality factor value is (k-1)*k k-1 / k k -1, m k The weight is the lowest, and its criticality factor value is m1*1 / k k-1 , other i ∈A i The weight calculation formula is m1*1 / k i-1 ; When k=1, then m1=1.
[0189] In one embodiment, the system further includes an adjustment module, specifically configured to:
[0190] When Z>1, changing the functional modules in the static set or the functional modules in the dynamic set until Z≤1 is satisfied;
[0191] When Z<1, the functional modules in the static set or the functional modules in the dynamic set are changed until Z=1 is satisfied.
[0192] It should be noted that when Z>1, it means that the system function logic design is unreasonable, that is, the software function in the dynamic data flow information of each system function, and gives the possible error point elements, that is, A n -{A n ∩A k} elements in the set, that is, the elements in the information element that only appear in the dynamic data flow information of each system function, but not in the static composition information of each system task. Manual processing is performed according to the dispute point, and the dynamic data flow information of each system function or the dynamic data flow information of each system function is changed until Z≤1; when Z<1, it means that the logical design of the system function is unreasonable, that is, the software function in the dynamic data flow information of each system function, and the missing information elements in the dynamic data flow information of each system function are given, that is, A k -A n The elements in the set, that is, the elements in the information elements, which only appear in the static composition information of each system task, but not in the dynamic data flow information of each system function. Manual processing is performed according to the dispute points, and the dynamic data flow information of each system function or the dynamic data flow information of each system function is changed until Z=1.
[0193] It should be noted that other embodiments or implementation methods of the system engineering design and verification system based on the fishbone model of the present invention can refer to the above-mentioned method embodiments, which will not be repeated here.
[0194] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0195] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.
[0196] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.
Claims
1. A system engineering design and verification method based on fishbone model, characterized in that: The method comprises: Acquiring modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow; Based on the fishbone diagram, the system-level static information and the system task-level static information are represented as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram; Based on the fishbone diagram, the system task-level dynamic data flow is represented as a system function point dynamic data flow diagram; Based on the system task composition structure diagram, a static set of each software function module of the system is established, and based on the system function point dynamic data flow diagram, a dynamic set of each software function module of the system is established; Performing consistency adjustment on the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent; in, The system-level static information includes a system name element and a system task name element; The system task level static information includes the name element of the system task and the name element of the software function module; The system task level dynamic data flow includes the name primitive of the system task, the name primitive of the software and the name primitive of the software function module; Based on the fishbone diagram, the system-level static information and the system task-level static information are represented as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram, including: Placing the name graphic element of the system at the end point of a horizontal straight line in a fishbone diagram as the head of the fishbone, and listing the name graphic elements of the system tasks on the oblique line segment of the fishbone diagram to form a static composition structure diagram of the system; For each system task in the system static composition structure diagram, the name graphic element of the system task is placed at the end point of a horizontal straight line in a fishbone diagram as the fishbone head, and the name graphic element of the software function module used to implement the system task is listed on the oblique line segment of the fishbone diagram to form the system task composition structure diagram; Based on the fishbone diagram, the system task-level dynamic data flow is represented as a system function point dynamic data flow diagram, including: The system task is represented by a horizontal straight line with an arrow, and the name graphic element of the system task is placed at the end point of the horizontal straight line in a fishbone diagram as the fishbone head; List the software name graphic element on the oblique line segment in the corresponding fishbone diagram, wherein the corresponding fishbone diagram is a fishbone diagram with the corresponding system task name graphic element as the fishbone head; The name graphic elements of the software function modules are listed on the oblique line segments in the corresponding fishbone diagram, and the corresponding fishbone diagram is a fishbone diagram with the name graphic elements of the corresponding software as the fishbone head.
2. The system engineering design and verification method based on the fishbone model according to claim 1, characterized in that: The order of the name element of the system task, the name element of the software and the name element of the software function module is consistent with the execution order of the system; When the software or the software functional modules are in a parallel relationship in terms of time sequence, the horizontal straight line with an arrow connecting the software or the software functional modules is represented by a dotted line.
3. The system engineering design and verification method based on the fishbone model according to claim 1, characterized in that: The static set of each software function module of the system is established based on the system task composition structure diagram, and the dynamic set of each software function module of the system is established based on the system function point dynamic data flow diagram, including: Based on the system task composition structure diagram, a static set A of each software function module of the system is established. k , k represents the total number of software functional modules in the static set; Based on the dynamic data flow diagram of the system function points, a dynamic set A of each software function module of the system is established. n , n represents the total number of software functional modules in the dynamic set.
4. The system engineering design and verification method based on the fishbone model according to claim 1, characterized in that: The step of adjusting the consistency of the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent includes: According to the priority ranking of each software function module in the static set, a weight determination model is adopted to determine the weight of each software function module, wherein the formula of the weight determination model is expressed as: m i ∈A k , and m1>m2>…>m k Among them, A k Represents a static set, m1, m2, ..., m k Respectively represent the weight of each software function module in the static set, and k represents the total number of software function modules in the static set; According to the consistency determination model, the software function modules in the static set and the software function modules in the dynamic set are adjusted for consistency. The formula of the consistency determination model is expressed as: Wherein, n and k are both positive integers, n represents the total number of software function modules in the dynamic set, Indicates the weight of each corresponding software function module in the static set; When Z=1 is satisfied, it is determined that the software function modules in the static set are consistent with the software function modules in the dynamic set, and a system engineering level review is performed.
5. The system engineering design and verification method based on the fishbone model as claimed in claim 4, characterized in that: The step of determining the weight of each software function module by using a weight determination model according to the priority ranking of each software function module in the static set includes: Based on the convergence concept, the software function modules in the static set are ranked in descending order of priority in a ratio of 1 / k, and the weights of the software function modules are determined as follows: m1=(k-1)*k k-1 / k k -1,c=1 m c =m1*1 / k c-1 , c≠1, and c≤k.
6. The system engineering design and verification method based on the fishbone model according to claim 4, characterized in that: The method further comprises: When Z>1, changing the functional modules in the static set or the functional modules in the dynamic set until Z≤1 is satisfied; When Z<1, the functional modules in the static set or the functional modules in the dynamic set are changed until Z=1 is satisfied.
7. A system engineering design and verification system based on fishbone model, characterized in that: The system comprises: An information acquisition module, used to acquire modeling information, wherein the modeling information includes system-level static information, system-task-level static information, and system-task-level dynamic data flow; A first information representation module is used to represent the system-level static information and the system task-level static information as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram based on a fishbone diagram; A second information representation module is used to represent the system task-level dynamic data flow as a system function point dynamic data flow diagram based on a fishbone diagram; A set determination module, used to establish a static set of each software function module of the system based on the system task composition structure diagram, and to establish a dynamic set of each software function module of the system based on the system function point dynamic data flow diagram; A consistency determination module, used for adjusting the consistency of the software function modules in the static set and the software function modules in the dynamic set until the software function modules in the static set and the software function modules in the dynamic set are consistent; in, The system-level static information includes a system name element and a system task name element; The system task level static information includes the name element of the system task and the name element of the software function module; The system task level dynamic data flow includes the name primitive of the system task, the name primitive of the software and the name primitive of the software function module; Based on the fishbone diagram, the system-level static information and the system task-level static information are represented as a system static composition structure diagram and a system task composition structure diagram corresponding to each system task in the system static composition structure diagram, including: Placing the name graphic element of the system at the end point of a horizontal straight line in a fishbone diagram as the head of the fishbone, and listing the name graphic elements of the system tasks on the oblique line segment of the fishbone diagram to form a static composition structure diagram of the system; For each system task in the system static composition structure diagram, the name graphic element of the system task is placed at the end point of a horizontal straight line in a fishbone diagram as the fishbone head, and the name graphic element of the software function module used to implement the system task is listed on the oblique line segment of the fishbone diagram to form the system task composition structure diagram; Based on the fishbone diagram, the system task-level dynamic data flow is represented as a system function point dynamic data flow diagram, including: The system task is represented by a horizontal straight line with an arrow, and the name graphic element of the system task is placed at the end point of the horizontal straight line in a fishbone diagram as the fishbone head; List the software name graphic element on the oblique line segment in the corresponding fishbone diagram, wherein the corresponding fishbone diagram is a fishbone diagram with the corresponding system task name graphic element as the fishbone head; The name graphic elements of the software function modules are listed on the oblique line segments in the corresponding fishbone diagram, and the corresponding fishbone diagram is a fishbone diagram with the name graphic elements of the corresponding software as the fishbone head.
