CN111475415A - Method and device for detecting consistency of reliability policy model and codes - Google Patents
Method and device for detecting consistency of reliability policy model and codes Download PDFInfo
- Publication number
- CN111475415A CN111475415A CN202010265739.0A CN202010265739A CN111475415A CN 111475415 A CN111475415 A CN 111475415A CN 202010265739 A CN202010265739 A CN 202010265739A CN 111475415 A CN111475415 A CN 111475415A
- Authority
- CN
- China
- Prior art keywords
- model
- code
- reliability
- reliability policy
- consistency
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention relates to a method and a device for detecting consistency of reliability policy models and codes, belongs to the technical field of software testing, and solves the problem that existing static information extraction is not suitable for detecting the consistency of the models and the codes.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a method and a device for detecting consistency of a reliability policy model and a code.
Background
Software reliability refers to the "ability of software to perform a required function under defined conditions for a given period of time". In the requirement description phase of a software system, system requirements are often described as functional requirements and non-functional requirements. As an important component of the non-functional requirements, the reliability requirements describe the reliability constraints of the system. The reliability design is a decision made according to the reliability requirement and provides a solution, and is a mechanism for ensuring that the system can normally run when encountering faults.
In the design phase, reliability design-based modeling provides guidance and evidence for code developers to implement the desired design. Currently, as the system scale becomes larger and more complex, the model-driven development method has been widely applied to the development process of software systems and provides guidance for developers, but developers need to meet the design of the basic functional requirements and other non-functional requirements of the system while realizing the reliability design; in addition, the updating and patching of the system code version can cause the reliability design to generate corresponding changes, and hidden danger is brought to the complete realization of the reliability design. The test is an effective means of checking whether the tested system completely realizes the expected design, and assists the code developer to confirm the completeness of the reliability design realization.
At present, a reliability test is also required, and the test of a reliability design is difficult to support, only a black box test method for generating a test case through a reliability test model in a design stage is researched for partial research results of the reliability test, and whether the reliability design is completely realized in a code cannot be verified.
Disclosure of Invention
In view of the foregoing analysis, embodiments of the present invention are directed to provide a method and an apparatus for detecting consistency of a reliability policy model and a code, so as to solve the problem that the existing extraction and comparison of pure static information is not suitable for detecting consistency of a reliability policy model and a code.
In one aspect, the embodiment of the invention provides a method for detecting consistency of a reliability policy model and codes, which comprises the steps of formally describing a UM L time sequence diagram and a label migration system L TS respectively, obtaining key information of a reliability policy UM L0 time sequence diagram model based on a reliability policy section model which is extracted from a software system overall design model and is an XMI file of a UM L2 time sequence diagram to construct the reliability policy UM L1 time sequence diagram model, converting the reliability policy UM L time sequence model into a model L TS, tracking the reliability policy model to codes to obtain reliability policy codes, obtaining a L og file based on reliability policy code instrumentation, wherein the L og file comprises execution path information of the reliability policy codes, constructing the codes L TS based on the L og file, extracting all branch paths of the model L TS as model paths and extracting branch paths of the codes L TS as code paths, detecting consistency between the model paths and the code paths, and detecting the number of the minimum code paths, and determining the number of the minimum code paths when the number of the paths is greater than the minimum code path definition accuracy.
The beneficial effects of the above technical scheme are as follows: according to the method for detecting the consistency of the reliability strategy model and the code, the consistency of the reliability strategy model and the code is judged by respectively converting the logic of the reliability strategy design model and the implementation logic of the source code into the same intermediate model, so that the defect of dynamic consistency detection of the model and the code in the current research is made up; the method carries out dynamic consistency detection on the reliability strategy model and the implementation code, meets the requirement of the reliability strategy on the implementation logic correctness, and provides a more efficient detection method and a more accurate detection result.
Based on a further improvement of the above method, detecting the consistency between the model path and the code path further comprises designing a consistency detection rule and detecting the consistency between the model path and the code path according to the consistency detection rule.
Based on a further improvement of the above method, the consistency check rule includes satisfying consistency if and only if one of the interaction messages in the model L TS corresponds to implementing methods of the same class in the implementation code L TS, satisfying consistency if and only if methods implementing the code L0 TS are consecutively invoked and the code L1 TS is in accordance with the order of the model L TS, satisfying consistency if one of the interaction messages in the model L TS corresponds to implementing methods of multiple classes in the implementation code L TS, satisfying consistency if and only if methods of the multiple classes are consecutively invoked and the code L TS is in accordance with the order of the model L TS, if one of the interaction messages in the model L TS is a self-associated message, having two implementations in the code L TS, calling another different method in the same class and calling the same method in the same class, and maintaining consistency of nodes in the mapping path of the starting path in the same class of objects if the object of the starting end of one of the interaction message in the model L TS is different from the object of the starting path of the receiving end.
Based on further improvement of the method, the reliability policy UM L time sequence diagram model is converted into the model L TS based on a conversion principle, wherein the conversion principle comprises that the initial state of the model L TS is marked as 0, one message in the reliability policy UM L time sequence diagram corresponds to one state transition in the model L TS, when a first message and a second message are adjacent on a time axis in the same execution environment, the state of the model L TS after the first message is converted is equivalent to the starting state of the model L TS after the second message is converted, and when the starting information of each sub-segment of a combined segment is converted into the model L TS, a transition state and a transition action are added, wherein the name of the transition state is consistent with the name of a sending end of the starting information, and the type of the transition action is the type of the current combined segment.
Based on the further improvement of the above method, the reliability policy UM L timing diagram model comprises a L T, OPT, L OOP and BREAK combined segment, wherein the conversion rule of the combined segment further comprises adding a transition state node as an end flag when the combined segment is ended, the conversion rule of the a L T combined segment further comprises executing a sub-segment whose guard condition is true, after the a L T combined segment is converted into the model L TS, there are a plurality of branches whose number is consistent with the number of sub-segments in the a L T combined segment, the conversion rule of the OPT combined segment further comprises executing the OPT combined segment when the guard condition is true, otherwise skipping the OPT combined segment, after the OPT combined segment is converted into the model L TS, there are two branches, the conversion rule of the L OOP combined segment further comprises executing the interactive message in the L OOP combined segment when the guard condition is satisfied, otherwise, and the BREAK combined segment further comprises adding another transition state node as a BREAK combined segment after the exchange condition is satisfied, and then the BREAK combined segment is executed when the BREAK combined segment is ended, otherwise, the exchange state node of the BREAK combined segment is added as the BREAK combined segment, and the BREAK combined segment is added after the exchange condition is satisfied.
Based on a further improvement of the above method, the key information includes a lifeline, a combined segment, and a combined segment sub-segment.
Based on further improvement of the method, tracking from the reliability strategy model to the code is carried out by utilizing composite detection to obtain the reliability strategy code, wherein the composite detection is combination of constraint configuration, information retrieval, detection based on a method call graph and manual detection.
Based on a further improvement of the above method, the instrumenting L og file based on the reliability policy code further comprises obtaining the L og file by executing a code segment when the reliability policy code runs to a specified position by inserting the code segment as a probe in the specified position of the reliability policy code, wherein the instrumentation rule comprises inserting the probe and marking Tag as D when direct matching according to name is successful in the result of the tracing, inserting the probe when direct matching according to the name is not successful but there is a direct or indirect dependency with the direct matching marked as D, inserting the probe in all direct matches of a class if the direct matching according to name is not successful inside the class, and inserting the probe in the first and last lines where direct matching of instrumentation is performed.
Based on a further improvement of the above method, constructing code L TS based on L og file includes extracting execution logic information with reliability policy complete at a time from the log file as the log information, and constructing the code L TS based on construction rules, wherein the construction rules include that each piece of log information in the log information is used to construct a start state node and a state transition in the code L TS, that a first piece of log information in the log information constructs a start state node and that subsequent pieces of log information in the log information construct state nodes marked as sequentially increasing numbers, and that a last piece of log information in the log information constructs only state nodes and does not construct state transitions.
On the other hand, the embodiment of the invention provides a consistency detection device of a reliability policy model and codes, which comprises a formal description module, an extraction module, a model L TS construction module, a tracking module, an instrumentation module, a code L TS construction module, an extraction module and a code L detection module, wherein the formal description module is used for formally describing a UM L time sequence diagram and a label migration system L TS respectively, the extraction module is used for acquiring key information of a reliability policy UM L time sequence diagram model based on a reliability policy section model which is extracted separately from a software system overall design model to construct the reliability policy UM L time sequence diagram model, the reliability policy section model is an XMI file of a UM L time sequence diagram, the model L TS construction module is used for converting the reliability policy UM L time sequence diagram model into a model L TS, the tracking module is used for tracking the reliability policy model to obtain reliability policy codes, the instrumentation module is used for instrumentation to obtain L og files based on the reliability policy codes, the L og files comprise execution path information of the reliability policy codes, the code TS construction module is used for constructing code L og 3 based on the reliability policy code files, the extraction module is used for extracting TS models, the TS model and is used for extracting the minimum path code L and determining the consistency between the minimum path codes, and the routing codes used for determining the consistency of paths when the path detection module is used for determining the consistency between the minimum path detection module and the routing detection module, and the routing detection module is used for determining the routing detection module when the routing detection module.
Compared with the prior art, the invention can realize at least one of the following beneficial effects:
1. the technical scheme of the invention is simple and effective, and the consistency of the logic of the reliability strategy design model and the implementation logic in the source code is judged by respectively converting the logic into the same intermediate model, so that the defect of dynamic consistency detection of the model and the code in the current research is made up;
2. the technical scheme of the invention adopts the thought of model-based test, respectively converts the execution sequences of the reliability strategy model and the reliability strategy realized in the source code into the same intermediate model, and judges through comparing and analyzing the intermediate models of the reliability strategy model and the reliability strategy model;
3. the technical scheme of the invention carries out dynamic consistency detection on the reliability strategy model and the implementation code, meets the requirement of the reliability strategy on the implementation logic correctness, and provides a more efficient detection method and a more accurate detection result; and
4. the method for checking the dynamic consistency between the model and the code, which is efficient and accurate, ensures that the reliability design is correctly realized in the development stage, and simultaneously improves the later maintenance efficiency of the system.
In the invention, the technical schemes can be combined with each other to realize more preferable combination schemes. Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and drawings.
Drawings
The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, wherein like reference numerals are used to designate like parts throughout.
FIG. 1 is a flowchart of a method for detecting consistency of a reliability policy model with a code according to an embodiment of the present invention;
FIG. 2 is a schematic overall flow chart of a method for tracking and confirming reliability policy in code according to an embodiment of the present invention;
FIG. 3 is a flow chart of an XMI document parsing a timing diagram of UM L according to an embodiment of the present invention;
FIG. 4 is a class diagram of the timing diagram of the reliability policy UM L and L TS model data structures according to the embodiment of the present invention;
FIG. 5 is a schematic diagram of the conversion rule of A L T combined fragments into model L TS according to the embodiment of the invention;
FIG. 6 is a diagram illustrating the conversion rule of OPT combined fragments into model L TS according to an embodiment of the present invention;
FIG. 7 is a diagram illustrating the conversion rules of L OOP combined fragments into model L TS, according to an embodiment of the present invention;
FIG. 8 is a schematic diagram illustrating conversion rules of BREAK combined fragments into model L TS according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of consistency of model methods corresponding to multiple methods of the same class according to an embodiment of the present invention;
FIG. 10 is a diagram illustrating the consistency of a model method with respect to multiple methods in different classes, according to an embodiment of the present invention;
FIG. 11 is a schematic diagram of the consistency of model self-association messages with implementation methods according to an embodiment of the present invention;
FIG. 12 is a diagram illustrating a search backtracking scenario of a consistency detection algorithm according to an embodiment of the present invention; and
fig. 13 is a block diagram of a device for detecting the consistency of a reliability policy model and a code according to an embodiment of the present invention.
Reference numerals:
1302-formal description module, 1304-extraction module, 1306-model L TS construction module, 1308-tracking module, 1310-instrumentation module, 1312-code L TS construction module, 1314-extraction module, 1316-consistency detection module, and 1318-definition and determination module
Detailed Description
The accompanying drawings, which are incorporated in and constitute a part of this application, illustrate preferred embodiments of the invention and together with the description, serve to explain the principles of the invention and not to limit the scope of the invention.
As shown in FIG. 1, the method for detecting consistency of the reliability policy model and the code comprises the steps of formally describing a UM L time sequence diagram and a label migration system L TS in step S102, obtaining key information of a reliability policy UM L time sequence diagram model based on the reliability policy section model which is extracted from a software system overall design model in step S104 to construct a reliability policy UM L time sequence diagram model, wherein the reliability policy section model is an XMI file of a UM L2 time sequence diagram, converting the reliability policy UM L time sequence diagram model into a model L TS in step S106, tracking the reliability policy model to the code to obtain the reliability policy code in step S108, performing instrumentation to obtain a L og file based on the reliability policy code in step S110, wherein the L og file comprises execution path information of the reliability policy code, constructing a code L og file based on the reliability policy code to obtain a reliability policy code, extracting a minimum code TS 13 code number as a minimum code path number in step S114, and determining the minimum code path number of a minimum code branch number in step S865 118 when the reliability policy section model is extracted as a minimum code number in step S865 24.
Compared with the prior art, the method for detecting the consistency of the reliability policy model and the code provided by the embodiment judges that the reliability policy model and the source code meet the consistency by respectively converting the logic of the reliability policy design model and the implementation logic of the source code into the same intermediate model, and makes up for the deficiency of dynamic consistency detection of the model and the code in the current research; the method carries out dynamic consistency detection on the reliability strategy model and the implementation code, meets the requirement of the reliability strategy on the implementation logic correctness, and provides a more efficient detection method and a more accurate detection result.
Hereinafter, a method of detecting the consistency of the reliability policy model with the code will be described in detail with reference to fig. 1.
The consistency detection method of the reliability policy model and the code comprises the steps of formally describing (i.e. formally defining) a UM L timing diagram and a label migration system L TS respectively in step S102. formally describing a UM L0 timing diagram and a label migration system L1 TS respectively comprises describing a UM L2 timing diagram as an octave, SD { Obj, M, E, →, CF, OP, O, C }, wherein Obj represents a set of all objects in a UM L timing diagram, M represents a set of all messages in a UM L timing diagram, E represents a set of all events in a UM L timing diagram, → represents a global ordering relation on a message set M of the UM L timing diagram, CF represents a set of all combined segments in the UM L, OP represents a set of all sub-segments belonging to the combined segments in a UM L timing diagram, O represents a functional relation from E to OP, C represents a functional relation from E to CF, and describing a label migration system TS L, TS 35A, S35q, T35q, T L, T35q, T L, and S30S represents a finite non-empty set of label migration system states; a represents a limited, non-empty set of label migration system behavior activity labels; t represents a set of system state transitions; q. q.s0The UM L timing diagram and the formalized description of the label migration system L TS can guide what information needs to be extracted from the UM L timing diagram model subsequently and the formulation of conversion rules.
The method for detecting the consistency of the reliability policy model and the codes further comprises the step of acquiring key information of a reliability policy UM L time sequence diagram model based on the reliability policy section model which is separated and extracted from the software system overall design model in step S104 to construct a reliability policy UM L time sequence diagram model, wherein the reliability policy section model is an XMI file of a UM L time sequence diagram, and specifically, the key information comprises a life line, a combined segment and a combined segment sub-segment.
The method for detecting consistency between the reliability policy model and the code further includes, in step S106, converting the reliability policy UM L time-series graph model into the model L TS. based on the conversion rule to convert the reliability policy UM L time-series graph model into the model L1 TS. based on the conversion rule, since the formalized definitions of the reliability policy UM L time-series graph model and the model L TS are different, the conversion rule needs to be defined, the conversion rule includes that the initial state of the model L TS is marked as 0, a message in the reliability policy UM L time-series graph corresponds to a state transition in the model L TS, when the first message and the second message are adjacent on the time axis in the same execution environment, the state of the model L TS after the first message conversion is equivalent to the start state of the model L TS after the second message conversion, and when the start message of each sub-segment of the combined segment is converted into the model L TS, a transition state and a transition action are added, wherein the name of the transition state is consistent with the name of the sender of the start message, and the type of the transition action is the type of the.
The reliability policy UM L timing graph model includes A L1T, OPT, L OOP and BREAK combined segments, wherein the conversion rules of the combined segments further include adding a transition state node as an end flag when the combined segment ends, the conversion rules of the A L T combined segment further include executing a sub-segment whose guard condition is true, after the A L T combined segment is converted into the model L TS, there are a number of branches that is consistent with the number of sub-segments in the A L T combined segment, the conversion rules of the OPT combined segment further include executing the OPT combined segment when the guard condition is true, otherwise skipping the OPT combined segment, after the OPT combined segment is converted into the model L TS, there are two branches, the conversion rules of the L OOP combined segment further include executing the intra-loop combined segment when the loop execution condition is satisfied, executing the intra-loop combined segment, otherwise, converting the intra-loop combined segment into the BREAK combined segment, and then executing the another branch combined segment as an end flag, otherwise, and when the BREAK combined segment is converted into the another loop execution rules include adding the intra-loop combined segment, otherwise, and when the loop execution rules of the BREAK combined segment are completed, and the BREAK combined segment, otherwise, the combined segment is added, the end flag.
The consistency detection method of the reliability policy model and the code further comprises the following steps: in step S108, tracking the reliability policy model to the code is performed to obtain the reliability policy code, where tracking includes two links of positioning and mapping. And tracking the reliability strategy model to the code by utilizing composite detection to obtain the reliability strategy code, wherein the composite detection is the combination of constraint configuration, information retrieval, detection based on a method call graph and manual detection. The search range can be greatly reduced through three steps of constraint configuration, information retrieval and detection based on the method call graph, and not only can a large amount of manpower and time be avoided being consumed by using manual detection at last, but also the accuracy rate of tracking can be effectively improved.
The method for detecting consistency of the reliability policy model and the code further includes obtaining L g files based on reliability policy code instrumentation, wherein L g files include execution path information of the reliability policy code, obtaining L g files by executing code fragments when the reliability policy code is run to a specified position by inserting the code fragments as probes in the specified position of the reliability policy code, wherein the instrumentation rules include inserting probes and marking Tag as D when direct matching according to the name is successful in a result of tracing, inserting probes when direct matching according to the name is not successful but direct or indirect dependency relationship exists with the direct matching marked as D, inserting probes in all direct matching of the class if direct matching according to the name is not successful, and inserting probes in a first line and a last line of the direct matching of the instrumentation, in step S110.
The method for detecting the consistency of the reliability policy model and the code further comprises the steps that in step S112, the code L TS is built on the basis of the L og file based building code L TS. and the L og file based building code 3632, the execution logic information with the reliability policy complete at a time is extracted from a log file to serve as log information, the building rule based building code L TS. comprises the steps that each piece of log information in the log information is used for building a starting state node and a state transition in the code L TS, the first piece of log information in the log information builds the starting state node, the state nodes built by the subsequent pieces of log information in the log information are marked as sequentially increasing numbers, the last piece of log information in the log information only builds the state node and does not build the state transition, and the code L TS of the reliability policy execution path can be obtained through the building rule.
The method for detecting consistency of the reliability policy model and the code further includes extracting all branch paths of the model L TS as model paths and extracting a branch path of the code L TS as a code path in step S114.
The consistency detection method of the reliability policy model and the code further comprises the steps of detecting consistency between a model path and a code path in step S116, designing a consistency detection rule and detecting consistency between the model path and the code path according to the consistency detection rule, wherein a one-to-one correspondence between the model L TS and the code L TS is almost nonexistent and is basically a one-to-many correspondence, and therefore the consistency detection rule needs to be defined.
The consistency detection method of the reliability policy model and the code further comprises the following steps: in step S118, the number of minimum code paths is defined, and when the number of code paths is equal to or greater than the number of minimum code paths, it is determined that the detection result of the consistency is accurate.
Hereinafter, referring to fig. 2 to 12, a method of detecting the consistency of the reliability policy model with the code is described in detail by way of specific examples.
The reliability policy is not completely realized according to the design model in the system implementation process or code change is generated in the later code upgrading maintenance process, and the implementation of the reliability policy is damaged, so that whether the reliability policy in the system code is correctly realized according to the design model needs to be detected, fig. 2 shows the overall flow of the reliability policy tracking and confirming method in the code of the invention, a reliability policy section model (UM L timing diagram) in fig. 2 is obtained based on a system overall architecture model, a system reliability requirement, a reliability policy library and the like, and is a document which is existed by default, therefore, formal definitions of a UM L timing diagram and a L TS model are defined first, key information is extracted from a description file of a UM 631 model, conversion rules of a UM 4834 TS model to a UM 363 TS model are defined, the reliability policy section model is extracted based on a TS 466 timing diagram model and a TS 0TS model is defined, the reliability policy section model is extracted from a TS 631 model description file of the policy section model, and the reliability policy section model is extracted from a TS 464 TS 463 TS model, and a reliability policy section model is obtained by combining with a reliability policy section model translation policy section model calculation algorithm calculation chart, reliability calculation chart is carried out, and calculation chart calculation.
FIG. 2 is a flow chart showing the steps of implementing the method of the present invention, and the specific steps are described in detail as follows:
step one, defining the formalized description of the UM L timing diagram and the label migration System (L absolute Transition System, L TS).
In order to complete the conversion from the UM L timing diagram to the L TS model, the formal definitions of the UM L timing diagram and L TS are first needed, and the formal definitions can also guide which information needs to be extracted from the UM L timing diagram and the establishment of conversion rules.
The UM L timing graph may be represented as an octave, SD ═ Obj, M, E, →, CF, OP, O, C, where Obj represents the set of all objects in the timing graph, M represents the set of all messages in the timing graph, E represents the set of all events in the timing graph, → represents a global ordering relationship on the message set M of UM L timing graph, which represents the precedence of all messages in the timing graph on the longitudinal time axis, CF represents the set of all composition segments in the timing graph, OP represents the set of all sub-segments in the timing graph that belong to the composition segment, O represents a functional relationship from E to OP for O (E) ∈ OP, the sub-segment to which event E belongs, C represents a functional relationship from OP to CF, and C (OP) ∈ CF represents the composition segment to which sub-segment belongs to OP.
The label migration system can be represented as a quadruplet L ═ S, a, T, q0}. where S represents a finite non-empty set of system states, A represents a finite non-empty set of system behavior activity labels, T represents a set of system state transitions that is a subset of S × A × S, q represents a set of system state transitions that is a subset of S × A × S0Because the L TS translated from the UM L timing diagram herein has only one initial state, determined by the entry message of the UM L timing diagram.
And secondly, acquiring key information of the UM L time sequence diagram model based on a reliability strategy section model (UM L time sequence diagram) which is separated and extracted from the overall design model of the software system.
By parsing the XMI file derived from the UM L timing graph with the file as input, all key information in the timing graph is extracted and saved as in the data structure instance of the UM L timing graph.
Fig. 3 is a flow chart for parsing an UM L time sequence diagram XMI file, in which an example of key information such as a lifeline, a combined fragment sub-fragment, and the like, which needs to be extracted from the XMI file of the UM L time sequence diagram, and then a UM L time sequence diagram data structure is constructed by using the extracted information is shown, fig. 4 is a data structure of reliability policy UM L time sequence diagram (hereinafter, abbreviated as UM L time sequence diagram) and L TS, which shows data information that should be saved by the UM L time sequence diagram and L TS models in detail.
And step three, defining the conversion principle from the UM L time sequence diagram to the L TS model, and realizing the conversion algorithm from the UM L time sequence diagram to the L TS model.
Because the UM L timing diagram and L TS model are different in formalized definition, the related conversion principle needs to be defined for guiding the implementation of the conversion algorithm, wherein the conversion principle includes (1) an initial state node of L0 TS system is marked as 0, (2) a message in UM L1 timing diagram (i.e., reliability policy UM L timing diagram) corresponds to a state transition in L TS (i.e., model L TS), (3) after two pieces of information adjacent on the time axis in the same execution environment are converted into L TS, the destination state of L TS after the conversion of the first message is equivalent to the starting state of L TS after the conversion of the second message, and (4) when the first message of each sub-segment in the combined segment of a L T, OPT and the like is converted into corresponding L TS, a transition state and a transition action need to be added, the name of the transition state is consistent with the name of the object of the first message, and the type of the transition action is the type of the current combined segment.
In addition to the need to implement the conversion algorithm from the UM L timing diagram as a whole to L TS (as shown in table 2), the conversion algorithm from the four types of combined fragments of a L T, OPT, L OOP and BREAK to L TS (as shown in fig. 5, 6, 7 and 8) needs to be considered separately.
FIG. 5 is a schematic diagram of a conversion rule from the A L T combined fragment to the model L TS according to the embodiment of the present invention, for the A L T fragment, there are multiple guard conditions, and the guard condition is true sub-fragment is executed first, therefore, for the A L T combined fragment, there are several branches after the A L T combined fragment is converted to L TS, the number of branches is consistent with the number of sub-fragments in the combined fragment, each branch uses [ cfName, A L T, Ci ] as a transition migration index, where Ci is the guard condition of each sub-fragment itself, since the receiving END of the last message of each sub-fragment is not necessarily the same object, and therefore, a transition state node named A L T _ CF _ END needs to be added after the combined fragment is finished, as shown in FIG. 6.
FIG. 6 is a diagram illustrating the conversion rule from the OPT composite fragment to the model L TS according to the embodiment of the invention, for the OPT composite fragment, when the guard condition is true, the interactive message in the fragment will not be executed, otherwise the composite fragment will be skipped, therefore, when the OPT composite fragment is converted to L TS, two branches will appear, with [ cfName, OPT, Ci ] and [ cfName, OPT, | Ci as transition migration labels, wherein Ci and | Ci respectively indicate that the guard condition is true and the guard condition is false, when the composite fragment ENDs, a transition state node named OPT _ CF _ END will be used as the END mark of the composite fragment, as shown in FIG. 6.
FIG. 7 is a schematic diagram of a conversion rule from L OOP combined fragment to model L TS according to an embodiment of the present invention, for L OOP combined fragment, there is a loop execution condition, which includes an initial value, a limit value and an execution action, a variable to be judged is set as the initial value, and then it is judged whether the value of the variable does not exceed the limit value, if so, the [ cfName, L OOP, Ci ] is used as a transition migration flag to start executing the interactive message in the combined fragment, and then the execution action is used to modify the value of the variable, otherwise, the [ cfName, L OOP, Ci ] is used as the transition migration flag to END the loop, after the last message in the fragment is executed, the last operation is repeated, and it is judged whether the value of the variable satisfies the condition, and then the next operation is performed according to the judgment result.
FIG. 8 is a diagram illustrating the conversion rule from the BREAK combined fragment to model L TS according to the embodiment of the invention, so that when the guard condition is true for the BREAK combined fragment, the interactive message in the fragment is executed, therefore, when the BREAK combined fragment is converted to L TS, two branches will appear, with [ cfName, OPT, Ci ] and [ cfName, OPT, | Ci ] as transition migration labels, if the BREAK combined fragment belongs to another combined fragment (assumed to be CFb), then after the BREAK fragment is executed, the BREAK _ CF _ END status node is the adjacent status node of the CFb END node of the combined fragment, and if the BREAK combined fragment does not belong to any combined fragment, the BREAK _ CF _ END status node is the global END status node, as shown in FIG. 8.
TABLE 1 transition Algorithm from UM L timing diagram to L TS
Step four: and (4) providing a composite detection algorithm to complete the tracking from the reliability strategy design model to the code.
The tracking between the model and the code is mainly divided into two links, namely positioning and mapping. Positioning means finding an implementation code of a reliability policy in a system source code; mapping refers to designing a model based on a reliability strategy, and mapping elements in the model to code classes obtained by positioning. The composite detection method provided by the invention is simultaneously suitable for the two links, and the composite detection method improves the efficiency and the accuracy of tracking the code from the model by combining constraint configuration, information retrieval, detection based on a method call graph and manual detection.
(1) Constraint configuration: the main configuration constraints comprise reliability strategy keywords, system module names based on requirements, system source code file formats and the like;
(2) and (3) information retrieval: the process mainly comprises the steps of extracting, retrieving and matching the model and the code information. The model information to be extracted comprises a reliability strategy keyword list, a strategy model all-object name list and a strategy model all-message name list; the code information that needs to be extracted includes a list of all module names, all packages under each module, all classes under each package, all methods in each class, and all internal classes in each class. And the retrieval matching is completed by adopting a fuzzy matching principle, and the relevant matching of the model information and the code information is completed.
(3) Detection based on the method call graph: the method call graph can completely reflect the method call relation among various classes in the code and describe the dynamic interactive behavior of the code. In order to avoid information omission caused by simple information retrieval, the 'calling distance' between related classes is used as a judgment criterion, if the calling distance is not more than N (default is 5), the currently judged class is considered to be linked with the initial reference class, and the currently judged class is stored as a matching result.
(4) Manual detection: through the three steps, the searching range can be greatly reduced, the problem of large consumption of manpower and time can be avoided by using manual detection at last, and the tracking accuracy can be effectively improved.
Table 2 and table 3 represent the effectiveness of the composite detection method proposed in step four of the present invention for the positioning and mapping process, respectively. In these two tables, we list the precision and the recall of the two detection methods: IR, a method of simply using information retrieval; constraint & IR & Call Graph, namely three methods of combining Constraint configuration, information retrieval and detection based on a method Call Graph.
Table 2: validity verification of composite detection in positioning process
Table 3: validity verification of composite detection in mapping process
And fifthly, based on the mapping relation between the model elements and the code implementation obtained in the fourth step, based on source code instrumentation, running to obtain the execution path L og information of the reliability policy implementation code.
Step four, the implementation code of the reliability strategy is acquired, so that instrumentation rules need to be defined, and after the system program runs to a specified position by inserting a code segment ("probe") at the position, L og information such as control flow and the like can be acquired by executing the probe, wherein the instrumentation rules comprise:
(1) in the tracking result obtained in the fourth step, for the method which depends on the name to be successfully matched directly, a probe is inserted, and Tag is marked as D;
(2) inserting a probe into the tracking result obtained in the fourth step, wherein the method which does not depend on name matching success exists in a direct or indirect dependence relationship with the method marked as 'D';
(3) in the tracking result obtained in the fourth step, for the class which is successfully matched directly by virtue of the name, if a method marked as 'D' does not exist in the class, inserting a 'probe' into all the methods in the class; and
(4) a "probe" is inserted in the first row (ensuring that the program will execute the statement first to the method) and the last row (ensuring that the program will execute the statement before leaving the method) of each instrumented method.
And sixthly, realizing an algorithm for constructing a corresponding L TS model based on L og information.
The L og obtained in the step five stores the execution path information of the reliability policy implementation code, so that the L TS model of the reliability policy implementation code execution path can be constructed based on the L og.
The L TS model obtained by converting the reliability strategy timing diagram model is a one-time complete flow of the reliability strategy, for a system program, as long as the program does not interrupt the operation, the information in a L og file is continuously increased, and the implementation logic of the reliability strategy code can be repeatedly executed for multiple times, so that the L TS model of the code execution path is conveniently constructed by extracting the one-time complete execution logic information of the reliability strategy from L og, and the invention finds the 'entries' of two adjacent complete flows by Hash on the information of each line in a L og file, obtains the total line number output by the one-time complete flow by using the line number difference corresponding to the 'entries', and obtains the L og information of the one-time complete flow.
The method comprises the steps of defining a construction rule and guiding to realize a related construction algorithm (shown in a table 4), wherein the construction rule comprises L og information (namely content triggering one-time 'probe' output) of each line, which can be used for constructing a starting state node and a state transition in L TS, L og information, wherein the starting state node constructed by the first message is marked as 0, the state nodes constructed subsequently are marked by sequentially increasing numbers, L og information is the last message, only the state node needs to be constructed, and the state transition does not need to be constructed.
TABLE 4 Algorithm for building L TS based on L og
And seventhly, extracting all branch paths of the L TS models obtained in the third step and the sixth step respectively, wherein the branch path obtained from the model L TS is called a model path, and the branch path obtained from the code L TS is called a code path.
L TS of the reliability policy design model and L TS. of the reliability policy implementation code obtained in the third step and the sixth step respectively have branches such as selection and circulation in the reliability policy design model, so that the converted L TS also has branches, and all branch paths need to be extracted, and L TS of the reliability policy implementation code represents a complete path of code operation because the L TS is constructed based on L og of code operation, and no additional branch path exists.
Step eight: and designing a consistency detection rule, realizing a consistency detection algorithm, and judging whether the code path can be successfully matched with the model path.
Therefore, in order to detect consistency between the branch path of the reliability policy design model L TS and the branch path of the reliability policy implementation code L TS, consistency rules need to be defined:
(1) if one interactive message in the policy model corresponds to a plurality of implementation methods in the same class in the implementation code, if and only if the plurality of methods in the implementation code are continuously called and the code class sequence and the model object sequence are kept consistent, the consistency is satisfied, as shown in fig. 9;
(2) if an interactive message in the policy model corresponds to multiple implementation methods in multiple classes in the policy implementation code, if and only if the multiple methods in the multiple corresponding implementation classes are continuously called and the code class order (the order between classes mapped to the same model object is not limited) is consistent with the model object order, the consistency is satisfied, as shown in fig. 10;
(3) if an interactive message in the policy model is a self-association message, i.e. the model object sends the interactive message to itself, there are two possible implementations in the code: the method calls a different method in the same class (i.e., a regular call), the method calls the same method in the same class (i.e., a recursive call), as shown in FIG. 11;
(4) if the object of the starting end of an interactive message in the policy model is different from the object of the receiving end, in order to meet the consistency between the policy model and the code, the model object of the class mapping of the starting node of the code path is required to be the same as the object of the starting node in the model path, otherwise, an inconsistent detection result is immediately returned.
According to the fourth rule of consistency, when the matching detection is performed between the model path and the code path, the model path and the code path may need to be continuously executed later to determine whether the current states are consistent. The invention therefore uses the search and backtracking concept (as shown in fig. 12) to design and implement a consistency detection algorithm.
Table 5: consistency detection algorithm of model path and code path
Step nine: defining a consistency detection coverage standard, and improving the reliability of a detection result; and analyzing and obtaining a final result.
Because L TS of the reliability policy model often has a plurality of branch paths, and L TS of the Code execution path only has one path under a certain determined operating condition, in order to improve the reliability of the consistency detection and avoid the situation of misjudgment, L0 TS of a new Code execution path can be generated by changing the Code operating condition, and multiple times of consistency detection are performed, when L1 TS of the reliability policy model has a large Number of branch paths, too much time cost is consumed by changing the operating condition to regenerate L TS of the Code execution path, and the situation that the Code operation cannot be completely covered by the path may exist, so that the invention defines a Minimum Number of Code execution paths L TS (Minimum Code L TS Number, MC L N), the generated Number of Code execution paths L TS is only not less than MC L N, and the requirement of the reliability of the consistency detection is met, and the result of the consistency detection between the reliability policy model L TS and the Code L TS is considered to be accurate.
This example proposes a calculation of MC L N based on a specified confidence level and an expected confidence level of consistency check assuming that in the current consistency check flow, the number of branch paths generated by the reliability policy model L TS is MN, the probability of false positives is k, α is the significance level, the lowest confidence requirement that the consistency check result can be received is R, and the estimated confidence level is R
Then the confidence level
Can be calculated to obtain:
the method is simple and effective, judges that the logic of the reliability strategy design model and the implementation logic in the source code meet the consistency by respectively converting the logic of the reliability strategy design model and the implementation logic in the source code into the same intermediate model, makes up the defect of detecting the dynamic consistency of the model and the code in the current research, detects the dynamic consistency of the reliability strategy model and the implementation code by the method, accords with the requirement of the reliability strategy on the correctness of the implementation logic, and provides a more efficient detection method and a more accurate detection result for the reliability strategy.
Hereinafter, the reliability policy model and code consistency detection apparatus will be described with reference to fig. 13.
The invention further discloses a device for detecting consistency of reliability policy models and codes, which comprises a formal description module 1302, an extraction module 1304, a model L TS construction module 1306, a tracking module 1308, a instrumentation module 1310, a code L TS construction module 1312, a code construction module 1314, a code extraction module 1314 and a code branch detection module 1316, wherein the formal description module 1302 is used for formally describing UM L time sequence diagrams and label migration systems L TS respectively, the extraction module is used for obtaining key information of reliability policy UM L0 time sequence diagram models based on reliability policy UM 631 time sequence diagram models which are XMI files of UM L time sequence diagrams and are extracted from a software system overall design model, the model L TS construction module 1306 is used for converting the reliability policy UM L time sequence diagram models into L TS, the tracking module 1308 is used for tracking the reliability policy models to obtain the reliability policy codes, the instrumentation module 1310 is used for obtaining the reliability policy codes based on reliability policy code instrumentation, the reliability policy code instrumentation module 1310 files which comprise execution path information of the reliability policy codes, the execution path models, the TS construction module 1312 2TS construction module is used for extracting codes 1314, the TS detection module is used for determining the number of paths which is greater than the minimum path number of the minimum path model 468, and is used for determining the path detection module when the path detection module 468 and the path detection module is used for determining the minimum path number of the minimum path detection module.
The consistency detection device of the reliability strategy model and the code also comprises a plurality of other modules, and the other modules correspond to the consistency detection method of the reliability strategy model and the code. Since the consistency detection device of the reliability policy model and the code corresponds to the consistency detection method of the reliability policy model and the code, detailed description of a plurality of other modules is omitted in order to avoid redundancy.
Compared with the prior art, the method and the device for detecting the consistency between the reliability policy model and the code have the following technical effects:
1. the technical scheme of the invention is simple and effective, and the consistency of the logic of the reliability strategy design model and the implementation logic in the source code is judged by respectively converting the logic into the same intermediate model, so that the defect of dynamic consistency detection of the model and the code in the current research is made up;
2. the technical scheme of the invention adopts the thought of model-based test, respectively converts the execution sequences of the reliability strategy model and the reliability strategy realized in the source code into the same intermediate model, and judges through comparing and analyzing the intermediate models of the reliability strategy model and the reliability strategy model;
3. the technical scheme of the invention carries out dynamic consistency detection on the reliability strategy model and the implementation code, meets the requirement of the reliability strategy on the implementation logic correctness, and provides a more efficient detection method and a more accurate detection result; and
4. the method for checking the dynamic consistency between the model and the code, which is efficient and accurate, ensures that the reliability design is correctly realized in the development stage, and simultaneously improves the later maintenance efficiency of the system.
Those skilled in the art will appreciate that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program, which is stored in a computer readable storage medium, to instruct related hardware. The computer readable storage medium is a magnetic disk, an optical disk, a read-only memory or a random access memory.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention.
Claims (10)
1. A method for detecting consistency of a reliability policy model and a code is characterized by comprising the following steps:
the UM L timing diagram and the label migration system L TS are formally described separately;
acquiring key information of a reliability policy UM L time sequence chart model based on a reliability policy section model which is separated and extracted from a software system overall design model to construct the reliability policy UM L time sequence chart model, wherein the reliability policy section model is an XMI file of a UM L time sequence chart;
converting the reliability policy UM L timing diagram model into a model L TS;
tracking the reliability policy model to the code to obtain a reliability policy code;
obtaining L og files based on the reliability policy code instrumentation, wherein the L og files include execution path information of the reliability policy code;
building code L TS based on the L og file;
extracting all branch paths of the model L TS as model paths and a branch path of the code L TS as code paths, and
detecting a correspondence between the model path and the code path;
defining the number of minimum code paths, and determining that the detection result of the consistency is accurate when the number of code paths is greater than or equal to the number of minimum code paths.
2. The method of claim 1, wherein detecting the correspondence between the model path and the code path further comprises designing a correspondence detection rule and detecting the correspondence between the model path and the code path according to the correspondence detection rule.
3. The method for detecting the consistency of the reliability policy model and the code according to claim 2, wherein the consistency detection rule comprises:
if an interaction message in the model L TS corresponds to implementing methods of the same class in the implementation code L TS, consistency is satisfied if and only if methods implementing the code L TS are called consecutively and the code L TS is in accordance with the order of the model L TS;
if an interaction message in the model L TS corresponds to multiple implementation methods that implement multiple classes in the code L TS, consistency is satisfied if and only if the multiple implementation methods of the multiple classes are called consecutively and the code L TS is in accordance with the order of the model L TS;
if an interaction message in the model L TS is a self-associated message, then there are two implementations in the code L TS that call a different method in the same class and call the same method in the same class, and
if the object of the start end of an interactive message in the model L TS is different from the object of the receiving end, consistency is maintained when the object of the class mapping of the start node in the code path is the same as the object of the start node in the model path.
4. The method of claim 1, wherein the reliability policy UM L timing graph model is transformed into model L TS based on transformation rules, the transformation rules comprising:
the initial state of the model L TS is labeled 0;
a message in the reliability policy UM L timing diagram corresponds to a state transition in the model L TS;
when a first piece of information and a second piece of information are adjacent on a time axis in the same execution environment, the target state of the first information converted model L TS is equivalent to the starting state of the second information converted model L TS, and
when the initial information of each sub-segment of the combined segment is converted into the model L TS, a transition state and a transition migration action are added, wherein the name of the transition state is consistent with the name of the sending end of the initial information, and the type of the transition migration action is the type of the current combined segment.
5. The reliability policy model and code consistency detection method according to claim 4,
the reliability policy UM L timing diagram model includes a combination of a L T, OPT, L OOP and BREAK segments, wherein,
the conversion principle of the combined segment further comprises: when the combined segment is ended, adding a transition state node as an end mark;
the conversion principle of the A L T combined segment also comprises the steps of executing sub-segments with true guard conditions, wherein after the A L T combined segment is converted into the model L TS, a plurality of branches exist, and the number of the branches is consistent with that of the sub-segments in the A L T combined segment;
the principle of converting the OPT combined segment also comprises the steps of executing the OPT combined segment when the guard condition is true, and skipping the OPT combined segment if the guard condition is not true;
the L OOP combined segment conversion principle further comprises executing the interactive message in the L OOP combined segment when the loop execution condition is satisfied, otherwise ending the loop, and
the conversion principle of the BREAK combined segment also comprises the steps of executing interactive information in the BREAK combined segment when the guard condition is true, wherein two branches exist when the BREAK combined segment is converted into the model L TS, when the BREAK combined segment belongs to another combined segment, adding the ending mark after the BREAK combined segment is executed, then executing the other combined segment, and if not, taking the added ending mark as a global ending state node.
6. The method according to claim 1, wherein the key information comprises a life line, a combined segment, and a combined segment sub-segment.
7. The method of claim 1, wherein the reliability policy model is tracked to the code to obtain the reliability policy code by using a composite detection, wherein the composite detection is a combination of constraint configuration, information retrieval, detection based on a method call graph, and manual detection.
8. The method for detecting the consistency of the reliability policy model and the code according to claim 1, wherein the obtaining L og files based on the reliability policy code instrumentation further comprises obtaining L og files by inserting code fragments as probes in specified positions of the reliability policy code so that the reliability policy code runs to the specified positions, wherein the instrumentation rules comprise, in the result of the tracking,
when direct matching by name is successful, the probe is inserted and Tag is marked as D;
inserting a probe when no match is successful according to the name but there is a direct or indirect dependency with the direct match labeled D;
when a class succeeds in direct matching by name, if the direct match marked as D does not exist inside the class, inserting probes in all the direct matches of the class; and
the probes are inserted in the first and last rows where the direct matching of the stake is performed.
9. The method for detecting the consistency of the reliability policy model and the code according to claim 1, wherein the constructing the code L TS based on the L og file comprises:
extracting execution logic information with a reliability strategy complete once from the log file as the log information; and
constructing the code L TS based on construction rules, wherein the construction rules include:
each of the log information is used to construct a start state node and a state transition in the code L TS;
a first one of the log information constructs a starting state node, and subsequent ones of the log information construct state nodes labeled as sequentially increasing numbers; and
the last log information in the log information only constructs state nodes and does not construct state transitions.
10. An apparatus for detecting consistency of a reliability policy model with a code, comprising:
a formal description module, configured to perform formal description on the UM L timing diagram and the label migration system L TS, respectively;
the extraction module is used for acquiring key information of a reliability policy UM L time sequence diagram model based on a reliability policy section model which is separated and extracted from a software system overall design model so as to construct the reliability policy UM L time sequence diagram model, wherein the reliability policy section model is an XMI file of a UM L time sequence diagram;
a model L TS construction module, configured to convert the reliability policy UM L timing graph model into a model L TS;
the tracking module is used for tracking the reliability strategy model to the code to obtain the reliability strategy code;
a instrumentation module for instrumenting the reliability policy code to obtain L og files, wherein the L og files include execution path information of the reliability policy code;
code L TS construction module for constructing code L TS based on the L og file;
an extraction module, configured to extract all branch paths of the model L TS as model paths, and extract a branch path of the code L TS as a code path;
a consistency detection module for detecting consistency between the model path and the code path; and
and the defining and determining module is used for defining the number of the minimum code paths and determining that the detection result of the consistency is accurate when the number of the code paths is greater than or equal to the number of the minimum code paths.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010265739.0A CN111475415B (en) | 2020-04-07 | 2020-04-07 | Method and device for detecting consistency of reliability policy model and codes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010265739.0A CN111475415B (en) | 2020-04-07 | 2020-04-07 | Method and device for detecting consistency of reliability policy model and codes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111475415A true CN111475415A (en) | 2020-07-31 |
| CN111475415B CN111475415B (en) | 2021-07-27 |
Family
ID=71750636
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010265739.0A Active CN111475415B (en) | 2020-04-07 | 2020-04-07 | Method and device for detecting consistency of reliability policy model and codes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111475415B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651241B1 (en) * | 1999-09-29 | 2003-11-18 | Lucent Technologies Inc. | Scriptor and interpreter |
| CN101571828A (en) * | 2009-06-11 | 2009-11-04 | 北京航空航天大学 | Method for detecting code security hole based on constraint analysis and model checking |
| CN101872322A (en) * | 2009-04-27 | 2010-10-27 | 武汉大学 | Method for detecting software features on basis of system requirement model |
| CN101894068A (en) * | 2010-05-31 | 2010-11-24 | 北京航空航天大学 | Embedded software reliability accelerated test method |
| CN102629232A (en) * | 2012-01-09 | 2012-08-08 | 北京航空航天大学 | Software reliability verifying and testing method with test validity introduced |
| CN102768642A (en) * | 2012-06-25 | 2012-11-07 | 浪潮电子信息产业股份有限公司 | LINUX kernel reliability evaluating system and LINUX kernel reliability evaluating method based on source code analysis |
| CN103268279A (en) * | 2013-02-27 | 2013-08-28 | 中国信息安全测评中心 | Compound poisson process-based software reliability prediction method |
| CN103530228A (en) * | 2013-09-27 | 2014-01-22 | 西安电子科技大学 | Software testing method based on model |
| US20140122028A1 (en) * | 2012-10-28 | 2014-05-01 | The Mathworks, Inc | Self-testing graphical component algorithm specification |
| CN105868106A (en) * | 2016-03-24 | 2016-08-17 | 飞依诺科技(苏州)有限公司 | An ultrasonic apparatus reliability testing method and testing system |
| CN110851546A (en) * | 2019-09-23 | 2020-02-28 | 京东数字科技控股有限公司 | Verification method, model training method, model sharing method, system and medium |
-
2020
- 2020-04-07 CN CN202010265739.0A patent/CN111475415B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6651241B1 (en) * | 1999-09-29 | 2003-11-18 | Lucent Technologies Inc. | Scriptor and interpreter |
| CN101872322A (en) * | 2009-04-27 | 2010-10-27 | 武汉大学 | Method for detecting software features on basis of system requirement model |
| CN101571828A (en) * | 2009-06-11 | 2009-11-04 | 北京航空航天大学 | Method for detecting code security hole based on constraint analysis and model checking |
| CN101894068A (en) * | 2010-05-31 | 2010-11-24 | 北京航空航天大学 | Embedded software reliability accelerated test method |
| CN102629232A (en) * | 2012-01-09 | 2012-08-08 | 北京航空航天大学 | Software reliability verifying and testing method with test validity introduced |
| CN102768642A (en) * | 2012-06-25 | 2012-11-07 | 浪潮电子信息产业股份有限公司 | LINUX kernel reliability evaluating system and LINUX kernel reliability evaluating method based on source code analysis |
| US20140122028A1 (en) * | 2012-10-28 | 2014-05-01 | The Mathworks, Inc | Self-testing graphical component algorithm specification |
| CN103268279A (en) * | 2013-02-27 | 2013-08-28 | 中国信息安全测评中心 | Compound poisson process-based software reliability prediction method |
| CN103530228A (en) * | 2013-09-27 | 2014-01-22 | 西安电子科技大学 | Software testing method based on model |
| CN105868106A (en) * | 2016-03-24 | 2016-08-17 | 飞依诺科技(苏州)有限公司 | An ultrasonic apparatus reliability testing method and testing system |
| CN110851546A (en) * | 2019-09-23 | 2020-02-28 | 京东数字科技控股有限公司 | Verification method, model training method, model sharing method, system and medium |
Non-Patent Citations (2)
| Title |
|---|
| FERRA YANUAR等: "Consistency Test of Reliability Index in SEM Model", 《HTTPS://WWW.SEMANTICSCHOLAR.ORG/PAPER/CONSISTENCY-TEST-OF-RELIABILITY-INDEX-IN-SEM-MODEL-YANUAR-》 * |
| 靖天才: "基于UML的可靠性测试模型研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111475415B (en) | 2021-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111382070B (en) | Compatibility testing method and device, storage medium and computer equipment | |
| US20090249308A1 (en) | Efficient Encoding of Instrumented Data in Real-Time Concurrent Systems | |
| CN102339252A (en) | Static state detecting system based on XML (Extensive Makeup Language) middle model and defect mode matching | |
| US20090307654A1 (en) | System, method and computer program for generating sequence diagram | |
| CN109871319A (en) | Item code scan method, device, computer equipment and storage medium | |
| CN108694320B (en) | Method and system for measuring sensitive application dynamic under multiple security environments | |
| CN110704063A (en) | Method and device for compiling and executing intelligent contract | |
| CN111488276B (en) | Software reliability testing method and device based on code tracking | |
| CN110704064A (en) | Method and device for compiling and executing intelligent contract | |
| JP4951416B2 (en) | Program verification method and program verification apparatus | |
| CN112199115A (en) | Cross-Java byte code and source code line association method based on feature similarity matching | |
| CN116383833A (en) | Method and device for testing software program code, electronic equipment and storage medium | |
| Zhang et al. | Understanding large language model based fuzz driver generation | |
| US6516306B1 (en) | Model checking of message flow diagrams | |
| CN114661290A (en) | Script error processing method, device, equipment and storage medium | |
| CN113868136A (en) | Program vulnerability analysis method based on Go language executable formal semantics | |
| CN114547318A (en) | Fault information acquisition method, device, equipment and computer storage medium | |
| CN111475415B (en) | Method and device for detecting consistency of reliability policy model and codes | |
| US20090064092A1 (en) | Visual programming language optimization | |
| CN115373737B (en) | Code clone detection method based on feature fusion | |
| CN115310095A (en) | Block chain intelligent contract mixed formal verification method and system | |
| CN115828264A (en) | Intelligent contract vulnerability detection method and system and electronic equipment | |
| CN112925874B (en) | Similar code searching method and system based on case marks | |
| US9354870B2 (en) | Maintaining integrity of output of code generators | |
| CN116893963A (en) | Fuzz driver generation method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220120 Address after: 215488 No. 301, building 11, phase II, Taicang University Science Park, No. 27, Zigang Road, science and education new town, Taicang City, Suzhou City, Jiangsu Province Patentee after: Tianhang Changying (Jiangsu) Technology Co.,Ltd. Address before: 100191 No. 37, Haidian District, Beijing, Xueyuan Road Patentee before: BEIHANG University |
|
| TR01 | Transfer of patent right |