Aeroengine software traceability and inspection method and system

Abstract

The application discloses an aero-engine software tracing and checking method and system, realizes full-process automatic tracing from requirement definition to final verification, shows the tracing relationship in an intuitive mode, improves the efficiency and quality of software development, and provides support for aero-engine software development and maintenance. The technical scheme is as follows: a link relationship is established: a plurality of requirement files and traced files are linked through different tools or methods, and the link relationship between high and low layer requirements and data is verified; after each source file with the link relationship is acquired, the source file is converted into an intermediate file through a converter, the intermediate file contains format information, the tracing relationship in the intermediate file is extracted by analyzing a keyword, and a coverage range is acquired; based on the tracing rule checking, the wrong tracing relationship is located and modified; and a visual view is formed according to the tracing relationship.

Description

Technical Field

[0001] This invention relates to the field of aero-engine control, and in particular to a method and system for tracing and inspecting aero-engine software data. Background Technology

[0002] In the field of aero-engine software development, software traceability, as a crucial link in software lifecycle management, is of great significance for ensuring software quality, meeting stakeholder needs, and effectively managing changes. The core of traceability lies in establishing a comprehensive linking system that allows each requirement to be precisely associated with its original source, design details, test cases, and experimental verification results. This system aims to achieve full-chain traceability from high-level requirements to low-level requirements, models, code, and even verification steps, thereby greatly improving the transparency and controllability of the software development process.

[0003] Specifically, through software traceability, project teams can quickly trace the source of any validation requirement and identify which stakeholder's requirement it belongs to. This is crucial for understanding the background of the requirement and assessing the impact of changes. When stakeholder requirements change, an efficient traceability mechanism can quickly locate the affected model parts, guide the development team to make necessary adjustments, and effectively reduce the propagation of errors and increased costs caused by requirement changes.

[0004] However, a significant challenge in current aero-engine software development practices is the proliferation and incompatibility of development tools and document types across different stages. The lack of unified interfaces or standards between requirements development tools, model development tools, and software verification tools makes it difficult to effectively integrate and trace various requirements documents, code files, model files, test cases, test procedures, and test results. This diversity of tools and document types not only increases the complexity of traceability but also limits the development team's overall control over the entire software lifecycle.

[0005] To address this challenge, while some solutions have been developed in the market that attempt to achieve data exchange between different tools through middleware or data conversion tools, these methods often suffer from limited compatibility, high operational complexity, and incomplete traceability chains, failing to fully meet the needs of aero-engine software development for efficient and accurate traceability. Summary of the Invention

[0006] The following provides a brief overview of one or more aspects to offer a basic understanding of them. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify key or decisive elements of all aspects, nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form to prepare for the more detailed descriptions that follow.

[0007] The purpose of this invention is to solve the above-mentioned technical problems and proposes a method and system for tracing and inspecting aero-engine software. By integrating multiple development tools, it aims to build a unified and efficient tracing platform, which can not only realize the full-process automated tracing from requirement definition to final verification, but also display the tracing relationship in an intuitive way, greatly improving the efficiency and quality of software development and providing strong support for the development and maintenance of aero-engine software.

[0008] The technical solution of this invention is as follows: This invention discloses a method for tracing and inspecting aircraft engine software, the method comprising:

[0009] Step 1: Establish links: Use different tools or methods to establish links between multiple requirement documents and traceable documents, and verify the links between high- and low-level requirements and data;

[0010] Step 2: After obtaining the source files with link relationships, the source files are converted into intermediate files using a converter. The intermediate files contain format information. By analyzing keywords, the traceability relationships in the intermediate files are extracted, and the coverage is obtained.

[0011] Step 3: Based on the traceability rules, locate the erroneous traceability relationships and correct them;

[0012] Step 4: Based on the traceability relationship, a visual view is generated.

[0013] According to an embodiment of the aero-engine software traceability and inspection method of the present invention, the link relationships in step 1 include: the link relationship between high-level requirements and low-level requirements, the link relationship between models and requirements, and the link relationship between code and low-level requirements.

[0014] According to an embodiment of the aero-engine software traceability and inspection method of the present invention, in step 2, the traceability includes requirement test traceability and model simulation traceability, which is further divided into test case and requirement traceability, test case and test procedure traceability, and test case and test result traceability.

[0015] According to an embodiment of the aircraft engine software tracing and inspection method of the present invention, in step 2, the tracing relationship in the intermediate file is extracted by parsing an expression.

[0016] According to an embodiment of the aircraft engine software traceability and inspection method of the present invention, in step 3, the traceability rule inspection includes determining whether the coverage has reached the expected level.

[0017] According to an embodiment of the aero-engine software traceability and inspection method of the present invention, step 4 further includes filtering the traceability results, extracting relevant information, and supporting one-click export.

[0018] This invention also discloses an aircraft engine software traceability and inspection system, the system comprising:

[0019] The traceability relationship establishment module is configured to establish links between multiple requirement documents and traceable documents through different tools or methods, and to verify the link relationships between high- and low-level requirements and data.

[0020] The traceability extraction module is configured to obtain source files with link relationships, convert the source files into intermediate files using a converter, and extract traceability relationships from the intermediate files by analyzing keywords, and obtain the coverage range.

[0021] The traceability relationship correction module is configured to check for errors in traceability relationships based on traceability rules and then modify them.

[0022] The traceability export module is configured to generate a visual view based on traceability relationships.

[0023] The present invention also discloses a computer system for tracing and inspecting aircraft engine software, including a memory, a processor, and program instructions stored in the memory that can be executed by the processor, wherein the processor executes the program instructions to implement the steps of the aircraft engine software tracing and inspecting method described above.

[0024] The present invention also discloses a computer-readable storage medium for tracing and inspecting aircraft engine software, which stores program instructions executable by a processor to implement the steps of the aircraft engine software tracing and inspecting method described above.

[0025] The present invention also discloses a computer program product, including a computer program that, when executed by a processor, implements the steps of the aircraft engine software traceability and inspection method as described above.

[0026] Compared with the prior art, the present invention has the following advantages: The present invention aims to solve the following problems in the prior art:

[0027] (1) Existing software traceability methods are limited to the traceability of single preceding and following data (i.e., simply realizing the traceability from requirements to design and from design to implementation). How to realize the traceability of the entire process from requirements to design to implementation to verification is the problem to be solved by this invention.

[0028] (2) How to design concise parsing expressions to extract text from documents of different formats;

[0029] (3) How to check the correctness of the requirement link and provide a reference for the modification of the requirement link.

[0030] To address the above problems, this invention determines the method for capturing key information in intermediate files by analyzing the type, and designs appropriate parsing expressions to capture links of requirements, text, and coverage. Specifically, it includes the following technical innovations:

[0031] a) The present invention provides a solution for full-process software traceability based on intermediate files;

[0032] b) This invention designs a traceability inspection tool to facilitate users in checking links.

[0033] Compared with the prior art, the present invention has the following advantages:

[0034] (1) It supports full-process traceability from requirements to design to implementation to verification, realizing a leap from point to surface;

[0035] (2) It supports tracing multiple input file formats and has a wide range of applications;

[0036] (3) It supports the correctness detection of demand traceability links, effectively saving the waste of manpower caused by traceability errors. Attached Figure Description

[0037] The above-described features and advantages of the present invention will be better understood after reading the following detailed description of embodiments of the present disclosure in conjunction with the accompanying drawings. In the drawings, components are not necessarily drawn to scale, and components having similar related characteristics or features may have the same or similar reference numerals.

[0038] Figure 1 A schematic diagram of the software traceability relationship of the present invention is shown.

[0039] Figure 2 A flowchart of an embodiment of the aircraft engine software tracing and inspection method of the present invention is shown.

[0040] Figure 3 A schematic diagram of the data traceability middleware of the present invention is shown.

[0041] Figure 4 The traceability topology diagram of the present invention is shown.

[0042] Figure 5 A schematic diagram of an embodiment of the aircraft engine software traceability and inspection system of the present invention is shown. Detailed Implementation

[0043] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be noted that the aspects described below with reference to the accompanying drawings and specific embodiments are merely exemplary and should not be construed as limiting the scope of protection of the present invention in any way.

[0044] Figure 2The flowchart of an embodiment of the aircraft engine software tracing and inspection method of the present invention is shown. Please refer to... Figure 2 As shown, the implementation steps of the method in this embodiment are described in detail below.

[0045] Step 1: Establish links: Using different tools or methods, establish links between multiple requirement documents and traceable documents, including links between high-level and low-level requirements, between models and requirements, and between code and low-level requirements, and verify the links between high-level and low-level requirements and data.

[0046] Specific traceability relationships are as follows: Figure 1 As shown.

[0047] In detail, step 1 further includes:

[0048] In the requirements editor, establish the traceability relationship between high-level requirements (HLR) and low-level requirements (LLR). According to the requirements design standards (requirements, category attributes, etc.), the currently defined requirements item attributes include traceable requirements (R), derived requirements (D), requirement continuation (C), and description (I). It is necessary to link traceable requirements.

[0049] The traceability of code and low-level requirements is achieved by inserting traceable information directly into functions using a pre-defined comment format (Implement LLR_XXX, where XXX is the requirement number), thereby creating a traceability relationship.

[0050] The model traceability relationship is established only for independent model units, and each model unit must be traced back to high-level software requirements. Models that cannot be traced must be marked as derived designs, and corresponding annotations must be added to explain the reasons for the derivation. The model modeling standard imposes certain constraints on model traceability: derived models do not need to be linked; architectural design models are not allowed to be linked, etc. Therefore, the following rules are implemented to check model traceability, supporting the viewing of rule violations and detailed information on illegal links, and enabling quick location of illegal links, as shown in Table 1 below (Model Traceability Check Function).

[0051] Table 1 Model Traceability Check Function

[0052]

[0053]

[0054] After completing the above processing, the software traceability scheme is determined.

[0055] Step 2: After obtaining the source files with link relationships, convert the source files into intermediate files using a suitable converter. The intermediate files contain format information that can be analyzed. By analyzing keywords, the traceability relationship (i.e., link relationship) in the intermediate files is extracted, and the coverage is obtained.

[0056] Test traceability includes requirement test traceability and model simulation traceability, further divided into test case and requirement traceability, test case and test procedure traceability, and test case and test result traceability. First, the design format of test cases, test procedures, and test results needs to be determined, incorporating traceability information, as shown in Table 2-4. One requirement can be traced back to multiple test cases. A test procedure is a document describing the test case design method, testing method, testing tools, and testing environment. Each test case corresponds to one test procedure; therefore, the test procedure design must include a test case identifier and name. Test results are the conclusion regarding whether a test case passes or fails; therefore, the test results must include the test case identifier and name. In model simulation traceability, the simulation design test cases and simulation result design are also shown in Tables 2 and 4. The model simulation procedure is a simulation executable file generated using a model simulation tool, and its name includes the phrase "simulation test case identifier."

[0057] Table 2 Test Case Format

[0058]

[0059] Table 3 Test Procedure Format

[0060]

[0061] Table 4 Test Result Format

[0062] In step 2, based on the input file attribute categories (requirements, models, code, test files), key information is extracted from each input file and converted into intermediate files. The file attributes are then indicated in the intermediate files, such as... Figure 3 As shown, the traceability information is then extracted through parsing the expression.

[0063] The requirement documents are converted into intermediate XML format using a converter. The contents of each requirement are shown in Table 5. Based on the requirement field type, appropriate expressions are designed to extract coverage information and traceable information from the lower-level requirement documents. The traceable information refers to the traceable requirement identifier and text content, while the coverage information refers to the link relationship to the higher-level requirements. The traceable requirement identifier and text content are captured in the higher-level requirement documents.

[0064] Table 5 Explanation of Requirement Fields

[0065]

[0066] The model file is converted into an intermediate file in XML format using a converter. The contents of each entry are shown in Table 6. Based on the model field type, an appropriate parsing expression is designed to capture the model diagram name, model annotation, and corresponding coverage information in the model file. The coverage information refers to the link relationship pointing to higher-level requirements.

[0067] Table 6 Explanation of Model Fields

[0068]

[0069] The key data in the source code file is converted into an intermediate file in XML format by a converter. The contents of each source code field are shown in Table 7. The function name and coverage information are extracted from it. The coverage information refers to the link relationship pointing to the lower-level requirements.

[0070] Table 7 Explanation of Source Code Fields

[0071]

[0072] For Excel files containing test cases, test procedures, and test results, key information is extracted in a column-based manner to generate intermediate files. By configuring appropriate regular expressions, coverage information and traceability information are extracted. In test cases, the test case identifier, test name, and other traceability information are extracted; the coverage information is also the requirement identifier and requirement content. In test procedures, the corresponding traceability information is extracted; the coverage information is also the test case identifier and test case name. In test results, the corresponding traceability information is extracted; the coverage information is also the requirement identifier and requirement content.

[0073] Table 8 Explanation of Test Case Fields

[0074] Serial Number Composition and structure illustrate 1 Use Case Identifier = T_FUNC01_001 Information to be traced 2 Demand identifier = [HLR-1] Coverage information 3 Required text content = "xxxxx" Coverage information

[0075] Table 9 Explanation of Test Procedure Fields

[0076] Serial Number Composition and structure illustrate 1 Procedure identifier = T_FUNC01_001_TESTPROC Information to be traced 2 Use Case Identifier = T_FUNC01_001 Coverage information 3 Use case content = "xxxxx" Coverage information

[0077] Table 10 Explanation of Test Result Fields

[0078] Serial Number Composition and structure illustrate 1 Test result = "xxxxx" Information to be traced 2 Use Case Identifier = T_FUNC01_001 Coverage information 3 Use case content = "xxxxx" Coverage information

[0079] For the Excel files containing model simulation test cases and model simulation results, similar to the test case and test result traceability scheme described above, the simulation procedures are named with corresponding "simulation test case identifiers." By extracting the names of each test procedure, the corresponding simulation test cases can be found within the simulation test cases, thus extracting the corresponding traceability relationships.

[0080] Step 3: Based on the traceability rules, locate the erroneous traceability relationships and correct them.

[0081] If the coverage does not meet expectations, a software traceability check should be performed to confirm the correctness of the traceability. Consider developing the following rules to filter the correctness of the traceability, which can quickly locate the error based on the error message and make the necessary changes to the requirements. Here, "requirements" refers to the input files mentioned in the main text, including requirements, models, code, and test files.

[0082] Table 11 Traceability Inspection Function

[0083]

[0084]

[0085] Step 4: Based on the traceability relationship, a visual view is generated, and the traceability results are filtered to extract relevant information, supporting one-click export.

[0086] By extracting key information and coverage details, and considering tracking visualization, a software data traceability topology diagram is generated. Each traceability document is displayed as a directory structure object, and solid lines in the topology diagram represent links between elements in one document and elements in another. When an element is selected, its corresponding coverage relationship is highlighted, including its forward coverage information (previous level requirements) and backward coverage information (next level requirements), such as... Figure 4 As shown, it can intuitively reflect the data traceability relationship of software from requirements to design and development to verification.

[0087] The extracted key information and coverage information also support the export of a two-way traceability matrix for the software, that is, the covered file tracks the covered file, and the covered file tracks the covered file. The specific content is defined in the form of the table below.

[0088] Table 12 Format of Two-Way Traceability Matrix

[0089]

[0090] Figure 5 The principle of an embodiment of the aircraft engine software traceability and inspection system of the present invention is illustrated. Please refer to [link / reference]. Figure 5 The system in this embodiment includes: a traceability relationship establishment module, a traceability relationship extraction module, a traceability relationship correction module, and a traceability relationship export module.

[0091] The traceability relationship establishment module is configured to establish links between multiple requirement documents and traceable documents using different tools or methods, verifying the link relationships between high- and low-level requirements and data. The specific processing of this module is the same as... Figure 2 Step 1 of the method embodiment shown will not be repeated here.

[0092] The traceability extraction module is configured to acquire source files with linked relationships, convert them into intermediate files using a converter, and extract traceability relationships from these intermediate files by analyzing keywords, thus obtaining the coverage scope. The specific processing of this module is the same as... Figure 2 Step 2 of the method embodiment shown will not be repeated here.

[0093] The traceability relationship correction module is configured to check for erroneous traceability relationships based on traceability rules and then correct them. The specific processing of this module is the same as... Figure 2 Step 3 of the method embodiment shown will not be repeated here.

[0094] The traceability export module is configured to generate a visual view based on traceability relationships. The specific processing of this module is the same as... Figure 2 Step 4 of the method embodiment shown will not be repeated here.

[0095] Furthermore, the present invention also discloses a computer system for tracing and inspecting aircraft engine software, including a memory, a processor, and program instructions stored in the memory that can be executed by the processor, wherein the processor executes the program instructions to implement the steps of the aircraft engine software tracing and inspecting method embodiment described above.

[0096] Furthermore, the present invention also discloses a computer-readable storage medium for tracing and inspecting aircraft engine software, which stores program instructions executable by a processor to implement the steps of the aircraft engine software tracing and inspecting method embodiment described above.

[0097] Furthermore, the present invention also discloses a computer program product, including a computer program that, when executed by a processor, implements the steps of the embodiment of the aero-engine software traceability and inspection method described above.

[0098] Although the methods described above are illustrated and depicted as a series of actions for the sake of simplicity, it should be understood and appreciated that these methods are not limited by the order of the actions, as some actions may occur in a different order and / or concurrently with other actions from the illustrations and descriptions herein or not illustrated and described herein but which may be understood by those skilled in the art, according to one or more embodiments.

[0099] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized manner in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of the invention.

[0100] The various illustrative logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein can be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, it may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0101] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read and write information to / from the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0102] In one or more exemplary embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functionality may be stored or transmitted as one or more instructions or code on or through a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Any connection is also legitimately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of a medium. As used in this article, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0103] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for tracing and inspecting aircraft engine software, characterized in that, The methods include: Step 1: Establish links: Use different tools or methods to establish links between multiple requirement documents and traceable documents, and verify the links between high- and low-level requirements and data; Step 2: After obtaining the source files with link relationships, the source files are converted into intermediate files using a converter. The intermediate files contain format information. By analyzing keywords, the traceability relationships in the intermediate files are extracted, and the coverage is obtained. Step 3: Based on the traceability rules, locate the erroneous traceability relationships and correct them; Step 4: Based on the traceability relationship, a visual view is generated.

2. The method for tracing and inspecting aircraft engine software according to claim 1, characterized in that, The links in step 1 include: the links between high-level requirements and low-level requirements, the links between models and requirements, and the links between code and low-level requirements.

3. The method for tracing and inspecting aircraft engine software according to claim 1, characterized in that, In step 2, traceability includes requirement test traceability and model simulation traceability, which is further divided into test case and requirement traceability, test case and test procedure traceability, and test case and test result traceability.

4. The method for tracing and inspecting aircraft engine software according to claim 1, characterized in that, In step 2, the traceability relationships in the intermediate files are extracted using parsed expressions.

5. The method for tracing and inspecting aircraft engine software according to claim 1, characterized in that, In step 3, the traceability rule check includes determining whether the coverage has met expectations.

6. The method for tracing and inspecting aircraft engine software according to claim 1, characterized in that, Step 4 also includes filtering the traceability results, extracting relevant information, and supporting one-click export.

7. An aircraft engine software traceability and inspection system, characterized in that, The system includes: The traceability relationship establishment module is configured to establish links between multiple requirement documents and traceable documents through different tools or methods, and to verify the link relationships between high- and low-level requirements and data. The traceability extraction module is configured to obtain source files with link relationships, convert the source files into intermediate files using a converter, and extract traceability relationships from the intermediate files by analyzing keywords, and obtain the coverage range. The traceability relationship correction module is configured to check for errors in traceability relationships based on traceability rules and then modify them. The traceability export module is configured to generate a visual view based on traceability relationships.

8. A computer system for tracing and inspecting aircraft engine software, characterized in that, The system includes a memory, a processor, and program instructions stored in the memory that can be executed by the processor, wherein the processor executes the program instructions to implement the steps of the aircraft engine software traceability and inspection method as described in any one of claims 1 to 6.

9. A computer-readable storage medium for tracing and inspecting aircraft engine software, characterized in that, It stores program instructions that can be executed by a processor to implement the steps of the aircraft engine software traceability and inspection method as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the aircraft engine software tracing and inspection method as described in any one of claims 1 to 6.

Images