Embedded software testing method based on AADL (Architecture Analysis and Design Language) mode transformation relationship

Abstract

The invention relates to an embedded software testing method based on AADL (Architecture Analysis and Design Language) mode transformation relationship, which has the following steps of: constructing a mode transition diagram on the basis of mode information in an AADL model, and converting the diagram into a mode relationship tree required by a transformation test according to the improved depth-first traversing algorithm; constructing a source test case in the mode transformation relationship by traversing the mode relationship tree, generating a subsequent test case by means of the mode transformation relationship in the AADL model, and verifying the mode transformation relationship to obtain the conclusion of the transformation test. The embedded software testing method based on AADL mode transformation relationship solves the 'Oracle' problem existing in the embedded software test, is convenient for a user to test the embedded software at an early stage of software design and ensures the reliability of software at a system architecture level. If the model architecture can not meet corresponding requirements, the architecture of the software can be modified at an early stage of development, thus the development cost is saved, and meanwhile, the development cycle can also be shortened.

Description

technical field [0001] The invention relates to an embedded software testing method based on AADL modal metamorphosis relationship, and relates to a metamorphic testing technology in software testing. Background technique [0002] With the development of computer technology, embedded systems play an increasingly important role in the industrial field. The task of early embedded software is simple and clear, and the scale of the software is relatively small. Therefore, in the process of software design and implementation, the focus is on how to effectively meet the functional and non-functional requirements of the software, basically ignoring the requirements of software engineering. Methods and techniques for controlling and managing system size and complexity. With the continuous expansion of the complexity of embedded software systems, the early embedded software development methods can no longer fully meet the requirements of embedded software design. Both bring challen...

AI Technical Summary

Problems solved by technology

However, these models have less support for AADL-based model testing. In addition, it is worth noting that in the process of embedded software testing, due to the diversity of the actual operating environment of components and the complexity of the interaction between components, program execution results often appear. It cannot be predicted in advance, or the phenomenon of using artificial methods to predict the result requires a large cost. The phenomenon that the execution result of this program cannot be predicted is called "Oracle problem" in test theory.

However, the existing component software testing models and methods compare the running results of the program under specific test cases with the expected running results to judge whether there are errors in the program design and implementation, which leads testers to only choose some simple test cases that can predict the results. testing, but not fully and effectively revealing the bugs in the program

Images