CN116303000A - A method and device for formally describing test requirements of aerospace equipment software configuration items - Google Patents

Abstract

The invention discloses a formalized description method and a formalized description device for testing requirements of a software configuration item of spaceflight equipment, and relates to the field of testing of the software configuration item of the spaceflight equipment; based on the formalized description tool, selecting basic primitives corresponding to the testing requirements of the software configuration items to establish formalized description graphs; according to the test requirement of the software configuration item, setting the attribute of the basic graphic primitive and the attribute among the basic graphic primitives in the established formal description graphic; and generating an XML description file corresponding to the formal description graph based on the formal description graph with the setting completion. The invention can improve the analysis efficiency of the test requirements and construct favorable conditions for developing formal verification work by adopting an automatic means.

Description

A method and device for formally describing test requirements of aerospace equipment software configuration items

technical field

The invention relates to the field of testing of software configuration items of aerospace equipment, in particular to a method and device for formally describing test requirements of software configuration items of aerospace equipment.

Background technique

In the process of test and verification of aerospace equipment software, the development of test requirements is a crucial link and the basis for all test and verification work. Formal description of test requirements for software configuration items is an important means of test requirements development. Through strict block diagram and attribute definition of arrows, it can ensure that the developed test requirements are accurate, verifiable and transferable, and can avoid requirements Ambiguity and ambiguity of description. By describing test requirements by formal means, testers can find inconsistent, unclear or incomplete requirements, and then communicate with software requirements definition personnel and software developers to effectively avoid deviations in understanding requirements, thereby improving the adequacy of software configuration item testing .

Aerospace equipment software has the characteristics of functional flow, and the functional flow is driven by judging the status of key signs to realize various software functions. Doing a good job in functional testing is the basic requirement to ensure the quality of aerospace equipment software. To carry out the requirements analysis of aerospace equipment software function testing, it is necessary to decompose the software workflow first, identify key flag variables, describe different functional process branches of equipment software according to different values, and ensure the sufficiency of functional test branch coverage. At present, in the functional testing of aerospace equipment software, the testers carry out text-based requirements analysis based on the software design documents. The adequacy of the requirements analysis depends entirely on the granularity and completeness of the software design documents, which is not conducive to giving full play to the testers’ abilities. work experience.

Aerospace equipment software also has the characteristics of high security level and complex interface structure, and its interface relationship is the basic structure for realizing various functions of aerospace equipment software. Doing a good job in interface testing is an important part of improving the quality of aerospace equipment software. To carry out the requirement analysis of aerospace equipment software interface testing, it is necessary to analyze and model the interface relationship of the system where the tested software is located, the interface relationship of the tested software itself, and the messages transmitted between the interfaces. At present, the software interface testing work of aerospace equipment is carried out by testers based on the software design documents to carry out textual requirement analysis work, and most of them are limited to a single software under test, lacking the ability to test the matching of system interfaces and the correctness of interface requirement analysis results .

The aerospace equipment software business workflow also has strict timing characteristics. Different timing instructions correspond to different hardware actions, and then drive the actuator to change the force on the spacecraft to achieve physical motion that meets the requirements of various business processes. In the business workflow of aerospace equipment software, the issuance of timing instructions has strict judgment conditions and interrelationships. Issuing timing instructions when the conditions are not met, or issuing multiple timing instructions out of order may damage the hardware and cause the task to fail. Therefore, carrying out the timing test of aerospace equipment software is the basic requirement to ensure that the aerospace equipment software correctly realizes various established functions and completes business processes. To carry out the analysis of timing test requirements for aerospace equipment software, it is necessary to first clarify the timing instruction requirements of aerospace equipment software, and then identify the judgment conditions for issuing timing instructions, and further describe the judgment conditions for issuing timing instructions under different business processes. Interrelationships between program instructions ensure the adequacy of requirements analysis. At present, the software timing test requirements analysis of aerospace equipment is carried out by the testers according to the software design documents to carry out text itemized requirements analysis work, and the description granularity of the timing test requirements in the software design documents is usually coarse, which may result in insufficient decomposition of test requirements , It is not conducive to give full play to the working experience of the testers.

Space equipment software is usually closely related to hardware. Hardware status, such as switch status, electrical characteristics, etc., as the input data of aerospace equipment software, will affect the decision-making results of software control logic. Among them, the combination of various hardware states related to the software constitutes the software running state profile. In the business process of aerospace equipment software, different decision-making results will be produced based on different operating state profiles. These decision results will usually determine that aerospace equipment software enters a certain major control flow branch, which has the characteristics of top-level decision-making. Therefore, carrying out the software state profile decision-making requirements test of aerospace equipment is the basic requirement to ensure that aerospace equipment correctly realizes various established functions and completes business processes. To carry out the requirement analysis of aerospace equipment software state profiles, it is necessary to first clarify the associated hardware states of aerospace equipment software, and then identify the software characteristics of various hardware states, and further describe the decision results based on state profiles under different business processes , to ensure the adequacy of the requirements analysis. At present, the software state profile decision-making requirements analysis work of aerospace equipment is carried out by testers according to the system design documents to carry out the text-entry requirement analysis work, and the system design documents usually describe the decision-making requirements of the software state profile with coarse granularity, which may cause test requirements. Insufficient decomposition is not conducive to giving full play to the work experience of testers.

Contents of the invention

In view of the defects existing in the prior art, the object of the present invention is to provide a method and device for formally describing test requirements of aerospace equipment software configuration items, which can improve the efficiency of test requirement analysis and construct favorable conditions for the use of automated means to carry out formal verification work .

In order to achieve the above purpose, the present invention provides a method for formally describing test requirements of aerospace equipment software configuration items, which specifically includes the following steps:

Create a formal description tool for formal description of software configuration item test requirements, and select the type of formal description graphics to be established based on the type of software configuration item test requirements;

Based on the formal description tool, select the basic graphic elements corresponding to the test requirements of the software configuration items to establish a formal description graph;

According to the test requirements of software configuration items, set the attributes of the basic primitives in the established formal description graphics and the attributes between basic primitives;

Based on the completed formalized description graph, an XML description file corresponding to the formalized description graph is generated.

On the basis of the above technical solution, the types of test requirements for the software configuration items include software function test requirements, software interface test requirements, software timing test requirements and software state profile decision requirements.

On the basis of the above technical solutions,

When the type of software configuration item test requirement is software function test requirement, the selected formalized description graph to be established is a flow chart;

When the type of software configuration item test requirements is software interface test requirements, the selected formalized description graphics to be established are interface diagrams;

When the type of software configuration item test requirements is software timing test requirements, the selected formal description graph to be established is a fishbone diagram;

When the type of software configuration item test requirements is software state profile decision requirements, the selected formal description graph to be established is a decision matrix.

On the basis of the above technical solutions,

The attributes of the basic primitives themselves include primitive names and descriptive text;

When the type of software configuration item test requirements is software function test requirements, the attributes between the basic graphic elements include flow paths and judgment conditions;

When the type of the software configuration item test requirement is a software interface test requirement, the attributes between the basic graphic elements include interface type and communication protocol;

When the type of software configuration item test requirements is software timing test requirements, the attributes between the basic graphic elements include timing fishbone and timing description conditions;

When the type of the software configuration item test requirement is a software state profile decision requirement, the attributes between the basic graphic elements include a decision condition and a decision result.

On the basis of the above technical solution, the formal description tool is used to select the basic graphic elements corresponding to the test requirements of the software configuration items to establish a formal description graphic, and the specific steps include:

In the formal description tool, drag the basic graphic elements corresponding to the test requirements of the software configuration items from the toolbar to the canvas to create a formal description graph.

On the basis of the above technical solutions, for software function testing requirements, business process description elements include functional modules, data flow direction, control process and judgment structure, and the business process description elements are in the form of dragging and dropping basic graphic elements and configuring basic graphic element attributes described in a manner.

On the basis of the above technical solution, for the software interface testing requirements, the message content transmitted between the interfaces includes message transmission source, message transmission purpose, message name, message ID and message transmission bus attribute information, and the message content can be obtained by dragging the basic diagram A formal way of describing primitives and configuring basic primitive properties.

On the basis of the above technical solutions, for the requirements of software timing testing, timing description elements include business process main axis, timing instruction factors, timing instruction sending judgment conditions, and timing instruction interrelationship description, and timing description elements can be configured by dragging and dropping basic graphics elements and Describe the properties of basic primitives in a formal way.

On the basis of the above technical solutions, for the software state profile decision-making requirements, the state profile decision-making description elements include the decision-making requirement name, software running status, business process and decision results, and the state profile decision-making description elements A formalized way to describe the properties of primitives.

A device for formally describing testing requirements of aerospace equipment software configuration items provided by the present invention includes:

Create a module, which is used to create a formal description tool for formal description of software configuration item test requirements, and select the type of formal description graphics to be established based on the type of software configuration item test requirements;

A selection module, which is used to select the basic graphic elements corresponding to the test requirements of the software configuration item based on the formal description tool, so as to establish a formal description graph;

A setting module, which is used to set the attributes of the basic primitives in the established formal description graphics and the attributes between the basic primitives according to the testing requirements of the software configuration items;

The generating module is used for generating an XML description file corresponding to the formalized description graph based on the completed formalized description graph.

Compared with the prior art, the present invention has the advantages of: by creating a formal description tool for formally describing the test requirements of software configuration items, and based on the created formal description tool, using drag-and-drop graphical modules and configuration Construct the functional process control model of aerospace equipment software in the way of business attributes to ensure the integrity of inspection function test requirements; use drag-and-drop graphical modules and configure business attributes to build the system of aerospace equipment software and its own interface model to ensure the consistency of inspection interface test requirements ;Using drag-and-drop graphical modules and configuring business attributes to build a timing test requirement model for aerospace equipment software, describe the judgment conditions and interrelationships of each timing instruction of aerospace equipment software under different business processes, and verify the integrity of timing testing requirements; use drag-and-drop Graphical modules and configuration business attributes are used to build a state profile decision-making demand model for aerospace equipment software, describe the decision results of aerospace equipment software based on state profiles under different business processes, and verify the completeness of state profile decision requirements. The invention can improve the efficiency of test requirement analysis and construct favorable conditions for adopting automatic means to carry out formalized verification work.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

Fig. 1 is a flow chart of a method for formally describing testing requirements of aerospace equipment software configuration items in an embodiment of the present invention.

Detailed ways

An embodiment of the present invention provides a method for formally describing the test requirements of aerospace equipment software configuration items. By creating a formal description tool for formally describing the test requirements of software configuration items, and based on the created formal description tool, use drag-and-drop Drag and drop graphical modules and configure business attributes to build a functional process control model of aerospace equipment software to ensure the integrity of the inspection function test requirements; use drag and drop graphical modules and configure business attributes to build aerospace equipment software systems and their own interface models to ensure Check the consistency of interface test requirements; use drag-and-drop graphical modules and configure business attributes to build a timing test requirement model for aerospace equipment software, describe the judgment conditions and interrelationships of timing instructions for aerospace equipment software under different business processes, and verify timing test requirements Integrity: Use drag-and-drop graphical modules and configure business attributes to build a decision-making demand model for the state profile of aerospace equipment software, describe the decision-making results of space equipment software based on the state profile under different business processes, and verify the integrity of the decision-making requirements of the state profile. The invention can improve the efficiency of test requirement analysis and construct favorable conditions for adopting automatic means to carry out formalized verification work. Correspondingly, the embodiment of the present invention also provides a device for formally describing test requirements of aerospace equipment software configuration items.

In order to make the purposes, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments It is a part of the embodiments of this application, but not all of them.

Referring to Fig. 1, an embodiment of the present invention provides a method for formally describing test requirements of aerospace equipment software configuration items, which specifically includes the following steps:

S1: Create a formal description tool for formal description of software configuration item test requirements, and select the type of formal description graphics to be established based on the type of software configuration item test requirements;

In the present invention, the types of software configuration item test requirements include software function test requirements, software interface test requirements, software timing test requirements and software state profile decision requirements. When the type of software configuration item test requirement is software function test requirement, the selected formalized description graph to be established is a flow chart; when the type of software configuration item test requirement is software interface test requirement, the selected formalized description graph to be established is is an interface diagram; when the type of software configuration item test requirement is software timing test requirement, the selected formalized description graph to be established is a fishbone diagram; when the type of software configuration item test requirement is software state profile decision requirement, the selected The formal description graph to be established is a decision matrix.

S2: Based on the formal description tool, select the basic graphic elements corresponding to the test requirements of the software configuration items to establish a formal description graph;

In the present invention, based on the formal description tool, select the basic graphic elements corresponding to the test requirements of the software configuration items to establish a formal description graphic. The specific steps include: in the formal description tool, drag the corresponding software from the toolbar to the canvas The basic graphic elements of configuration item test requirements to establish a formal description graph.

S3: According to the test requirements of software configuration items, set the attributes of the basic primitives in the established formal description graphics and the attributes between basic primitives;

In the present invention, the attributes of the basic primitive itself include the name of the primitive and description text;

When the type of software configuration item test requirements is software function test requirements, the attributes between the basic graphic elements include flow paths and judgment conditions; when the type of software configuration item test requirements is software interface test requirements, the basic graphic elements The attributes between the basic graphic elements include interface type and communication protocol; when the type of software configuration item test requirements is software timing test requirements, the attributes between the basic graphic elements include timing fishbone and timing description conditions; when the type of software configuration item test requirements When determining requirements for the software state profile, the attributes between the basic graphic elements include decision conditions and decision results.

S4: Generate an XML (Extensible Markup Language, Extensible Markup Language) description file corresponding to the formalized description graph based on the completed formalized description graph.

In the present invention, for software function testing requirements, the business process description elements include functional modules, data flow direction, control process and judgment structure, and the business process description elements are described by dragging and dragging basic graph elements and configuring basic graph element attributes. .

For software interface testing requirements, the message content transmitted between interfaces includes message transmission source, message transmission purpose, message name, message ID, and message transmission bus attribute information, and the message content can be obtained by dragging the basic primitives and configuring the basic primitive attributes. Described in a formal way.

For software timing test requirements, the timing description elements include the main axis of the business process, timing instruction factors, timing instruction sending judgment conditions, and description of the relationship between timing instructions, and the timing description elements are formalized by dragging the basic primitives and configuring the attributes of the basic primitives to describe.

For software state profile decision-making requirements, the state profile decision-making description elements include the decision-making requirement name, software running status, business process and decision results, and the state profile decision-making description elements are implemented by dragging and dropping basic primitives and configuring basic primitive properties. describe.

The software function test requirements, software interface test requirements, software timing test requirements and software state profile decision-making requirements in the present invention are specifically described below.

1. Requirements for software functional testing

At present, in the functional testing of aerospace equipment software, the testers carry out textual requirement analysis based on the software design documents. If the software design document describes the software function at a coarse granularity, or if the description of the control process branch is incomplete, it will lead to insufficient analysis results of the tested software function test requirements. At the same time, the presentation form of text-based itemized test requirements is not intuitive enough, unable to reflect the logical relationship between test requirements, unable to test the testers' requirements analysis results, and not conducive to carrying out follow-up test verification work. The present invention provides a method for formally describing aerospace equipment software function test requirements based on graphics and structured files, so that the process of testers developing function test requirements can be transformed from invisible thought activities to visible formal description and construction. The modeling process ensures that the functional test requirements developed by testers are accurate, verifiable and transferable, and can avoid ambiguity and ambiguity in requirement descriptions. specific:

(1) The present invention uses a formal method to describe the functional testing requirements of the software under test. The software under test is driven by interface messages and changes in key flag variables as the physical basis, and the software functional process is a business application, wherein the business process description elements mainly include functional modules Attribute information such as data flow direction, control process, key flag judgment structure, etc., the above content is described by formal means such as dragging and dropping graphical modules, configuring business attributes, etc., forming a formal description result of functional test requirements, which includes a graphical description and XML structured documents;

(2) The present invention processes the XML structured files in the formalized description results of functional test requirements by way of encoding, and forms text entry-based aerospace equipment software functional test requirements and automated test scripts, which are used to generate and formalize functional test requirements documents verification work;

(3) The present invention supports the generation of formal description results of functional test requirements by dragging and dropping graphical modules, configuring business attributes, etc., and the graphical description and XML structured files in the results are mutually mapping relationships, which can be described graphically Generate XML structured files, and generate graphical descriptions through translation of XML structured files, and the two can be converted to each other.

Compared with the current equipment software function test requirements analysis method, the present invention has the following advantages:

1. The present invention can transform the process of testers developing functional test requirements from an invisible thought activity into a visible formal description modeling process, ensuring that the functional test requirements developed by testers are accurate, verifiable and transferable , which can avoid the ambiguity and ambiguity of the test requirement description;

2. The present invention can use formal means such as dragging and dropping graphical modules, configuring business attributes, etc. to carry out formal description and modeling of functional test requirements;

3. In the process of formal description and modeling of functional test requirements, testers can find insufficient and incomplete parts in the software design documents, thereby improving the adequacy of equipment software functional test requirements analysis;

4. The present invention can use graphical description and XML structured files to express formalized description results of aerospace equipment software function tests;

5. In the present invention, the graphical description and the XML structured file are mutually mapping relationships and can be converted to each other;

6. The present invention can convert XML structured files into text-based space equipment software function test requirements and automated test scripts, which are used to generate function test requirement documents and formalize verification.

2. Requirements for software interface testing

At present, the software interface testing work of aerospace equipment is carried out by testers according to the software design documents to carry out text entry requirements analysis. If the software design document describes the interface architecture and messages incorrectly, it will directly lead to an error in the analysis of the interface test requirements of the software under test. At the same time, due to the differences in the work experience of the testers, it may also lead to insufficient analysis of the testing requirements of the software interface under test. The presentation form of text-based itemized test requirements is not intuitive enough, unable to reflect the logical relationship between test requirements, unable to test the testers' requirements analysis results, and not conducive to carrying out follow-up test verification work. The present invention provides a method for formally describing aerospace equipment software interface test requirements based on graphical and structured files, so that the process of testers developing interface test requirements is transformed from invisible thought activities into visible formal descriptions The modeling process ensures that the interface test requirements developed by testers are accurate, verifiable and transferable, and can avoid ambiguity and ambiguity in requirement descriptions. specific:

(1) The present invention adopts a formal method to describe the interface relationship of the system where the software under test is located and the messages transmitted between the interfaces, each entity node and the bus structure of the system under test software are the physical basis, and the messages transmitted between the interfaces are business Application, in which the messages transmitted between the interfaces mainly include attribute information such as message transmission source, message transmission destination, message name, message ID, message transmission bus, etc. The above contents are all formalized by dragging and dropping graphical modules, configuring business attributes, etc. Make a description to form a formal description result of the system interface relationship, which includes a graphical description and an XML structured file;

(2) The present invention uses a formal method to describe the interface relationship of the software under test itself and the messages transmitted between the interfaces, by determining the software under test in the results of the formal description of the system interface relationship, according to the configuration in the results of the formal description of the system interface relationship Automatically generate a formalized description result of the configuration item interface relationship of a single software under test based on the business attribute, which includes a graphical description and an XML structured file;

(3) The present invention processes the XML structured files in the formalized description results of the system interface relationship and the formalized description results of the interface relationship of the configuration items in a coding manner, and forms text entry-based aerospace equipment software interface test requirements and automated test scripts for use in Carry out interface test requirement document generation and formal verification;

(4) The present invention supports the generation of formal description results of system interface relations and formal description results of interface relations of configuration items by dragging and dropping graphical modules, configuring business attributes, etc. For the mapping relationship, XML structured files can be generated through graphical descriptions, and graphical descriptions can be generated through translation of XML structured files, which reserves expansion space for the subsequent more intelligent development of aerospace equipment software interface test requirements .

Compared with the current equipment software interface test requirement analysis method, the present invention has the following advantages:

1. The present invention can transform the process of testers developing interface test requirements from an invisible thought activity into a visible formalized description modeling process, ensuring that the interface test requirements developed by testers are accurate, verifiable and transferable , which can avoid the ambiguity and ambiguity of the test requirement description;

2. The present invention can use formal means such as dragging and dropping graphical modules, configuring business attributes, etc. to carry out interface test requirement development work;

3. The present invention can use graphical description and XML structured files to express the formalized description results of aerospace equipment software interface testing;

4. In the present invention, the graphic description and the XML structured file are mutually mapping relations, and can be mutually converted;

5. The present invention can convert XML structured files into text-based space equipment software interface test requirements and automated test scripts, which are used to generate interface test requirement documents and formalize verification.

3. Requirements for software timing testing

At present, the requirement analysis work of aerospace equipment software timing test is carried out, and the testers carry out the requirement analysis work based on the software design documents. However, the description granularity of software timing test requirements in software design documents is usually coarse, which may result in insufficient decomposition of test requirements. At the same time, the presentation form of text-based itemized test requirements is not intuitive enough, unable to reflect the logical relationship between test requirements, unable to test the testers' requirements analysis results, and not conducive to carrying out follow-up test verification work. The present invention provides a method for formally describing aerospace equipment software timing test requirements based on graphics and structured files, enabling testers to change the process of developing software timing testing requirements from invisible thought activities to visible formal descriptions The modeling process ensures that the software timing test requirements developed by testers are accurate, verifiable and transferable, and can avoid ambiguity and ambiguity in requirement descriptions. specific:

(1) The present invention adopts a formal method to describe the timing test requirements of aerospace equipment software, clarify what timing instruction requirements the aerospace equipment software has, and then identify the judgment conditions for issuing each timing instruction, and further describe each timing sequence issued under different business processes The judgment conditions of instructions and the relationship between sequential instructions, the description elements mainly include attribute information such as business process main axis, timing instruction factors, timing instruction sending judgment conditions, and description of the relationship between timing instructions. Configure business attributes and other formal means to describe, and form the formal description results of software timing test requirements, which include graphical descriptions and XML structured files;

(2) The present invention processes the xml structured files in the formalized description results of the software timing test requirements in a coding manner, and forms text entry-based aerospace equipment software timing test requirements and automated test scripts, which are used to generate software timing test requirements documents and Formal verification work;

(3) The present invention supports the generation of formalized description results of software timing test requirements by dragging and dropping graphical modules, configuring business attributes, etc., and the graphical description and XML structured files in the results are mutually mapping relationships, which can be achieved through graphical The description generates an xml structured file, and the graphical description can be generated by translating the xml structured file, and the two can be converted to each other.

Compared with the current aerospace equipment software timing test requirements analysis method, the present invention has the following advantages:

1. The present invention can transform the process of testers developing aerospace equipment software timing test requirements from invisible thought activities into visible formalized description modeling process, ensuring that the state transition test requirements developed by testers are accurate and verifiable and transferable, which can avoid the ambiguity and ambiguity of test requirement description;

2. The present invention can use formal means such as dragging and dropping graphical modules, configuring business attributes, etc. to carry out formal description and modeling of software timing test requirements;

3. During the formal description and modeling process of software timing test requirements, testers can discover the insufficient and incomplete parts of the software design documents that describe the timing test requirements under different business processes, thereby improving the adequacy of software timing test requirements analysis ;

4. The present invention can use graphical description and XML structured files to express formalized description results of aerospace equipment software timing test requirements;

5. In the present invention, the graphical description and the XML structured file are mutually mapping relationships and can be converted to each other;

6. The present invention can convert XML structured files into text-based aerospace equipment software timing test requirements and automated test scripts, which are used to generate software timing test requirement documents and formalize verification.

4. Requirements for Decision-Making of Software State Profiles

At present, the software state profile decision-making requirements analysis of aerospace equipment is carried out, and the testers carry out textual itemized requirements analysis work according to the software design documents. However, software design documents usually describe the decision-making requirements of the software state profile at a relatively coarse granularity, which may result in insufficient decomposition of test requirements. At the same time, the presentation form of text-based itemized test requirements is not intuitive enough, unable to reflect the logical relationship between test requirements, unable to test the testers' requirements analysis results, and not conducive to carrying out follow-up test verification work. The present invention provides a method for formally describing the decision-making requirements of the software state profile of aerospace equipment based on graphics and structured files, so that the process of testers developing the decision-making requirements of the software state profile is changed from an invisible thought activity to a visible form The description modeling process is simplified to ensure that the software state profile decision-making requirements developed by testers are accurate, verifiable and transferable, and can avoid ambiguity and ambiguity in requirements description. specific:

(1) The present invention uses a formal method to describe the decision-making requirements of the state profile of aerospace equipment software, clarify the associated hardware states of the space equipment software, and then identify the software features of various hardware states, and further describe the different business processes based on The decision result of the state profile, its description elements mainly include attribute information such as the name of the decision requirement, the element of the state profile (hardware state), business process and decision result. Describing, forming a formalized description result of software status profile decision requirements, which includes graphical description and XML structured file;

(2) The present invention processes the XML structured files in the formalized description results of the software state profile decision-making requirements by means of coding, and forms text entry-based space equipment software state profile decision-making requirements and automated test scripts, which are used to develop software state profile decision-making requirements Document generation and formal verification work;

(3) The present invention supports the formalized description results of software state profile decision-making requirements generated by dragging and dropping graphical modules and configuring business attributes. The XML structured file can be generated from the simplified description, and the graphical description can be generated through the translation of the XML structured file, and the two can be converted to each other.

Compared with the current aerospace equipment software state profile decision-making requirements analysis method, the present invention has the following advantages:

1. The present invention can transform the process of testers developing aerospace equipment software state profile decision-making requirements from invisible thought activities into a visible formalized description modeling process, ensuring that the state transition test requirements developed by testers are accurate and predictable. Verifiable and transferable, able to avoid ambiguity and ambiguity in test requirement description;

2. The present invention can use formal means such as dragging and dropping graphical modules, configuring business attributes, etc. to carry out the formal description and modeling work of software state profile decision-making requirements;

3. During the formal description modeling process of software state profile decision-making requirements, testers can discover the insufficient and incomplete parts of the software design documents that describe the state profile decision-making requirements under different business processes, thereby improving the analysis of software state profile decision-making requirements sufficiency;

4. The present invention can use graphical descriptions and XML structured files to express formalized description results of aerospace equipment software state profile decision requirements;

5. In the present invention, the graphical description and the XML structured file are mutually mapping relationships and can be converted to each other;

6. The present invention can convert XML structured files into text-based aerospace equipment software state profile decision requirements and automated test scripts, which are used to generate software state profile decision requirements documents and formalize verification.

The invention provides a device for formally describing test requirements of space equipment software configuration items, including a creation module, a selection module, a setting module and a generation module.

The creation module is used to create a formal description tool for formally describing the test requirements of software configuration items, and based on the type of software configuration item test requirements, select the type of formal description graphics to be established; the selection module is used to According to the test requirements of software configuration items, the setting module is used to describe the attributes of the basic primitives in the established formal description graphics and the basic The attributes between the graphic elements are set; the generation module is used to generate an XML description file corresponding to the formalized description graph based on the completed formalized description graph.

The above descriptions are only specific implementation manners of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the application. Therefore, the present application will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Claims (10)

1. A method for formally describing test requirements of aerospace equipment software configuration items, characterized in that, specifically comprising the following steps: Create a formal description tool for formal description of software configuration item test requirements, and select the type of formal description graphics to be established based on the type of software configuration item test requirements; Based on the formal description tool, select the basic graphic elements corresponding to the test requirements of the software configuration items to establish a formal description graph; According to the test requirements of software configuration items, set the attributes of the basic primitives in the established formal description graphics and the attributes between basic primitives; Based on the completed formalized description graph, an XML description file corresponding to the formalized description graph is generated. 2. A method for formally describing test requirements of aerospace equipment software configuration items as claimed in claim 1, characterized in that: the types of said software configuration item test requirements include software function test requirements, software interface test requirements, and software timing tests Requirements and Software State Profile Decision Requirements. 3. a kind of space equipment software configuration item test requirement formal description method as claimed in claim 2, it is characterized in that: When the type of software configuration item test requirement is software function test requirement, the selected formalized description graph to be established is a flow chart; When the type of software configuration item test requirements is software interface test requirements, the selected formalized description graphics to be established are interface diagrams; When the type of software configuration item test requirements is software timing test requirements, the selected formal description graph to be established is a fishbone diagram; When the type of software configuration item test requirements is software state profile decision requirements, the selected formal description graph to be established is a decision matrix. 4. a kind of aerospace equipment software configuration item test requirement formal description method as claimed in claim 3, it is characterized in that: The attributes of the basic primitives themselves include primitive names and descriptive text; When the type of software configuration item test requirements is software function test requirements, the attributes between the basic graphic elements include flow paths and judgment conditions; When the type of the software configuration item test requirement is a software interface test requirement, the attributes between the basic graphic elements include interface type and communication protocol; When the type of software configuration item test requirements is software timing test requirements, the attributes between the basic graphic elements include timing fishbone and timing description conditions; When the type of the software configuration item test requirement is a software state profile decision requirement, the attributes between the basic graphic elements include a decision condition and a decision result. 5. a kind of aerospace equipment software configuration item test requirement formal description method as claimed in claim 4, is characterized in that, described based on formal description tool, selects the basic graphic element of corresponding software configuration item test requirement, to establish form To describe the graph graphically, the specific steps include: In the formal description tool, drag the basic graphic elements corresponding to the test requirements of the software configuration items from the toolbar to the canvas to create a formal description graph. 6. A method for formally describing test requirements of aerospace equipment software configuration items as claimed in claim 5, characterized in that: for software function test requirements, business process description elements include functional modules, data flow direction, control flow and judgment structure, And the business process description elements are described in a formal way by dragging and dropping basic primitives and configuring the properties of basic primitives. 7. A method for formally describing test requirements of aerospace equipment software configuration items as claimed in claim 5, characterized in that: for software interface test requirements, the content of messages transmitted between interfaces includes message transmission source, message transmission purpose, message Name, message ID, and message transmission bus attribute information, and the content of the message is described in a formal way by dragging and dropping basic primitives and configuring basic primitive attributes. 8. A method for formally describing testing requirements of aerospace equipment software configuration items as claimed in claim 5, characterized in that: for software timing testing requirements, timing description elements include business process main axis, timing instruction factors, and timing instruction sending judgment conditions The relationship between timing instructions and timing instructions is described, and the timing description elements are described in a formal way by dragging the basic primitives and configuring the properties of the basic primitives. 9. A method for formally describing test requirements of aerospace equipment software configuration items as claimed in claim 5, characterized in that: for software state profile decision-making requirements, the state-profile decision-making description elements include decision-making requirement name, software running state, business process and decision results, and the state profile decision description elements are described in a formal way by dragging and dropping basic primitives and configuring the properties of basic primitives. 10. A device for formally describing testing requirements of aerospace equipment software configuration items, characterized in that it includes: Create a module, which is used to create a formal description tool for formal description of software configuration item test requirements, and select the type of formal description graphics to be established based on the type of software configuration item test requirements; A selection module, which is used to select the basic graphic elements corresponding to the test requirements of the software configuration item based on the formal description tool, so as to establish a formal description graph; A setting module, which is used to set the attributes of the basic primitives in the established formal description graphics and the attributes between the basic primitives according to the testing requirements of the software configuration items; The generating module is used for generating an XML description file corresponding to the formalized description graph based on the completed formalized description graph.

Images