Embedded Software Functional Module Design Method Based on Software Product Line Variability

Abstract

The present invention provides a design method for an embedded software function module based on software product line variability. The design method for the embedded software function module based on software product line variability includes: sorting out and designing the overall functional requirements of the embedded software function module; sorting out and designing a plurality of basic modules required to meet the overall functional requirements; sorting out the variability parameter requirements in the overall functional requirements, and designing the form and transmission method of the variability parameters according to the variability parameter requirements; designing a plurality of combined function architectures for guiding the basic modules according to the variability parameters; and assembling the plurality of combined function architectures to form a complete embedded software function module. By applying the technical solution of the present invention, the technical problems of low software development reliability and low reuse degree in software function modules can be solved.

Description

Technical Field

[0001] The present invention relates to the technical field of aircraft embedded software design and development, and particularly relates to a design method for embedded software function modules based on the variability of software product lines. Background Art

[0002] Aircraft embedded software refers to an embedded software system installed in the aircraft's computer, which has complex functions and numerous interfaces. To improve software development efficiency and design quality, software has gradually shifted from independent project development to software reuse development. Currently, the commonly used software reuse development method is to modularize and encapsulate software, and the software calls the encapsulated modules to improve software efficiency. However, since the granularity of the encapsulated software modules is small, the reused modules need to be called multiple times or frequently, resulting in low usage efficiency and reliability of the encapsulated software modules. Summary of the Invention

[0003] The present invention aims to solve at least one of the technical problems existing in the prior art.

[0004] The present invention provides a design method for embedded software function modules based on the variability of software product lines. The design method for embedded software function modules based on the variability of software product lines includes: sorting out and designing the overall function requirements of the embedded software function modules; sorting out and designing multiple basic modules required to meet the overall function requirements; sorting out the variability parameter requirements in the overall function requirements, and designing the form and transmission method of the variability parameters according to the variability parameter requirements; designing multiple combined function architectures for guiding the basic modules according to the variability parameters; and assembling multiple combined function architectures to form a complete embedded software function module.

[0005] Further, the embedded software function module is a filtering function module.

[0006] Further, the filtering function module includes a basic first-order filtering module, a basic second-order filtering module, and a basic third-order filtering module.

[0007] Further, the variability parameters of the filtering function module include the data body, whether to filter multiple times, the required filtering order, and the corresponding filtering coefficients.

[0008] Further, the form of the variability parameters of the filtering function module is a filtering parsing word.

[0009] Furthermore, the multiple combined functional architectures of the filtering function module include: judging the parameter validity according to each parameter limit in the variability parameter requirements, and returning a fault flag if the parameter is invalid; assigning parameters and performing filtering processing according to different orders for data that only requires single filtering; for data that requires multiple filterings, assigning parameters and performing filtering processing when the multiple filterings have the same order; for data that requires multiple filterings, assigning parameters and performing combined filtering processing when the order is different for each of the multiple filterings; and returning the final filtering result.

[0010] Applying the technical solution of the present invention, a design method for an embedded software functional module based on the variability of a software product line is provided. This design method for the embedded software functional module designs multiple basic modules according to the overall functional requirements, which are used as the smallest granularity of the functional module, and designs a combined functional architecture adapted to the basic modules according to the variability parameter requirements to form a complete embedded software functional module. The functional module design method of the present invention can improve the software reuse rate, more conveniently use mature software functional modules, and omit the secondary development process of the reused modules. Compared with the prior art, the technical solution of the present invention can solve the technical problems of low software development reliability and low reuse degree in software functional modules. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings included are used to provide a further understanding of the embodiments of the present invention, which form a part of the specification, are used to illustrate the embodiments of the present invention, and are used to explain the principles of the present invention together with the text description. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0012] Figure 1 Shows a schematic diagram of the architecture of an embedded software functional module based on the variability of a software product line provided according to a specific embodiment of the present invention;

[0013] Figure 2 Shows a schematic diagram of the architecture of a filtering function module provided according to a specific embodiment of the present invention;

[0014] Figure 3 Shows a schematic diagram of variability parameters provided according to a specific embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0015] It should be noted that, without conflict, the embodiments in the present application and the features in the embodiments may be combined with each other. The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and in no way limits the present invention and its application or use. Based on the embodiments in the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present invention.

[0016] It should be noted that the terms used herein are only for describing specific embodiments and are not intended to limit the exemplary embodiments according to the present application. As used herein, unless the context clearly indicates otherwise, the singular form is also intended to include the plural form. In addition, it should be understood that when the terms "comprise" and / or "include" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0017] Unless otherwise specifically stated, the relative arrangements of components and steps, numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present invention. At the same time, it should be understood that, for the sake of convenience of description, the dimensions of the various parts shown in the drawings are not drawn in actual proportional relationships. Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and devices should be regarded as part of the specification. In all the examples shown and discussed herein, any specific value should be construed as merely exemplary and not as a limitation. Therefore, other examples of the exemplary embodiments may have different values. It should be noted that like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0018] As Figure 1 shown, according to a specific embodiment of the present invention, a method for designing an embedded software function module based on software product line variability is provided. The method for designing an embedded software function module based on software product line variability includes: sorting out and designing the overall function requirements of the embedded software function module; sorting out and designing a plurality of basic modules required to meet the overall function requirements; sorting out the variability parameter requirements in the overall function requirements, and designing the form and transmission method of the variability parameters according to the variability parameter requirements; designing a plurality of combined function architectures for guiding the plurality of basic modules according to the variability parameters; and assembling the plurality of combined function architectures to form a complete embedded software function module.

[0019] By applying this configuration method, a design method for embedded software functional modules based on the variability of software product lines is provided. This design method for embedded software functional modules designs multiple basic modules according to the overall functional requirements, which are used as the smallest granularity of the functional modules, and designs a combined functional architecture adapted to the basic modules according to the variability parameter requirements to form a complete embedded software functional module. The functional module design method of the present invention can improve the software reuse rate, more conveniently use mature software functional modules, and omit the secondary development process of the reused modules. Compared with the prior art, the technical solution of the present invention can solve the technical problems of low reliability and low reuse degree in software development of software functional modules.

[0020] In order to implement the design of embedded software functional modules based on the variability of software product lines, first, organize and design the overall functional requirements of the embedded software functional modules. In order to enable the embedded software functional modules to adapt to various different demand patterns and thus improve the utilization rate of the functional modules, it is necessary to design the functional requirements of the embedded software from an overall perspective, so as to construct a relatively large software functional module according to the overall functional requirements.

[0021] In the present invention, after organizing and designing the overall functional requirements of the embedded software functional modules, organize and design multiple basic modules required to meet the overall functional requirements. The basic module is the smallest granularity in the functional module. The basic module cannot be further decomposed and is not directly open to the outside and cannot be directly called. Multiple basic modules form a basic module pool.

[0022] In the present invention, after organizing and designing multiple basic modules required to meet the overall functional requirements, organize the variability parameter requirements in the overall functional requirements, and design the variability parameter form and transmission method according to the variability parameter requirements. Different functional requirements of different software functional modules correspond to different variability parameter requirements. It is necessary to design an adapted variability parameter form and transmission method for the variability parameter requirements in the overall functional requirements of the current software functional module.

[0023] In the present invention, after designing the variability parameter form and transmission method according to the variability parameter requirements, design multiple combined functional architectures to guide multiple basic modules according to the variability parameters. Construct multiple combined functional architectures adapted to multiple basic modules for the multiple variability parameters corresponding to the current software functional module, and each combined functional architecture realizes the function related to the variability parameter.

[0024] In the present invention, after designing to guide multiple combined functional architectures, assemble multiple combined functional architectures to form a complete embedded software functional module. Assemble multiple combined functional architectures representing multiple combined functional branches to form a complete embedded software functional module.

[0025] The design method of embedded software functional modules based on the variability of software product lines proposed by the present invention can adapt to a variety of different requirement patterns, improve the utilization rate of functional modules, enhance their adaptability to software product lines, enable the software design to make the most of mature functional modules as much as possible, and each functional module can be compatible with multiple different requirements without the need for each independent project to conduct secondary development on the reused modules, ensuring the integrity and reliability of the reused software, improving the software reuse rate, and also enhancing the efficiency and quality of software R & D.

[0026] The software functional module design of the present invention can achieve the same function to meet multiple different requirements during software design, and there is no need to redesign and change the reused modules during software design, ensuring the quality of software product development. The design method of the reused software modules of the present invention has the advantages of variability and adaptability to multiple requirements, so it can adapt to the assembly process of software product lines, can be applied to the reused software technology of multiple projects, and can improve the reliability and reuse degree of software development. This method has been popularized and applied to multiple models and achieved very good results.

[0027] For a further understanding of the present invention, the following combines Figures 1 to 3 to elaborate in detail on the design method of the embedded software functional module based on the variability of software product lines of the present invention.

[0028] As Figure 2 shown, according to a specific embodiment of the present invention, a design method of a filtering functional module is provided, and the method specifically includes the following steps.

[0029] Step 1, sort out the overall functional requirements for designing the filtering functional module.

[0030] Step 2, sort out multiple basic modules required to meet the overall functional requirements of the filtering functional module, including a basic first-order filtering module, a basic second-order filtering module, and a basic third-order filtering module. These three basic modules cannot be directly called, and the requirements for the above basic modules are that the filtering coefficient can be transmitted and the process data of filtering can be recorded.

[0031] Step 3, sort out the variability parameter requirements in the overall functional requirements of the filtering functional module, as shown in Table 1.

[0032] Table 1 Variability parameter requirements table of the filtering functional module

[0033]

[0034]

[0035] Form variability parameters according to the above variability requirements of the filtering functional module, including: data body; whether to filter multiple times; and the required filtering order and corresponding filtering coefficients.

[0036] Among the above-mentioned variability parameters obtained according to the sorted variability parameter requirements, the data body is the source data of the software and does not require much design; whether to perform multiple filtering needs to clearly indicate the number of filtering times; the required filtering order and the corresponding filtering coefficients need to correspond to the number of filtering times.

[0037] Design the variability parameter form according to the above description as a filtering analysis word. This word is a 16-bit unsigned integer data, and its content can represent the number of filtering times required and the required filtering order. Then design a four-dimensional array corresponding to the filtering analysis word. The array can store up to four groups of filtering coefficients at most, and each group of filtering has at most 3 orders. The schematic diagram of the filtering analysis word is as Figure 3 shown.

[0038] Step 4: Design multiple combined function architectures to guide multiple basic modules according to the variability parameters, and complete the design of each combined function architecture corresponding to the variability parameters.

[0039] In this embodiment, for the sorting of the variability requirements in the filtering function module, multiple combined function architectures are sorted out as follows:

[0040] 1) Judge the validity of the parameters according to the parameter limitations in the variability parameter requirements. If the parameters are invalid, return a fault flag.

[0041] Make a preliminary judgment according to the filtering analysis word to judge whether the parameters are within three orders and at most four times of filtering. If the parameters are not within this range, the parameters are invalid and an error code is reported.

[0042] 2) Assign parameters and perform filtering processing for the data that only needs single filtering according to different orders.

[0043] For the data that only needs single filtering, call the corresponding basic filtering module according to the required filtering order, and assign coefficient values each time.

[0044] 3) For the data that needs multiple filterings, perform parameter assignment and filtering processing for the multiple filterings with the same order.

[0045] For the data that needs multiple filterings and has the same order, call the corresponding basic filtering modules in series according to the required filtering order, and assign coefficient values each time.

[0046] 4) For the data that needs multiple filterings, perform parameter assignment and filtering combination processing for the multiple filterings with different orders each time.

[0047] For the data that needs multiple filterings and has different orders, call different basic filtering modules in series according to the required filtering order, and assign coefficient values each time.

[0048] 5) Return the final filtering result.

[0049] Step 5: Assemble multiple combined functional architectures to form a complete embedded software functional module, as Figure 2 shown.

[0050] In summary, the present invention provides a design method for an embedded software functional module based on software product line variability. This design method for the embedded software functional module designs multiple basic modules according to the overall functional requirements, which are used as the smallest granularity of the functional module, and designs a combined functional architecture adapted to the basic module according to the variability parameter requirements to form a complete embedded software functional module. The functional module design method of the present invention can improve the software reuse rate, more conveniently use mature software functional modules, and omit the secondary development process of the reused modules. Compared with the prior art, the technical solution of the present invention can solve the technical problems of low reliability and low reuse degree in software development of software functional modules.

[0051] For ease of description, spatial relative terms such as "above", "on top of", "on the upper surface of", "above" etc. can be used here to describe the spatial positional relationship between a device or feature shown in the figure and other devices or features. It should be understood that the spatial relative terms are intended to encompass different orientations in use or operation in addition to the orientation depicted in the figure. For example, if the device in the figure is inverted, the device described as "above" or "on top of" other devices or structures will then be positioned "below" or "beneath" the other devices or structures. Thus, the exemplary term "above" can include both the orientations of "above" and "below". The device can also be positioned in other different ways (rotated 90 degrees or in other orientations), and the corresponding explanations for the spatial relative descriptions used here will be made accordingly.

[0052] In addition, it should be noted that the use of terms such as "first" and "second" to limit components is only for the convenience of distinguishing the corresponding components. Without further statement, the above terms have no special meaning, and thus cannot be construed as limiting the protection scope of the present invention.

[0053] The above are only the preferred embodiments of the present invention and are not used to limit the present invention. For those skilled in the art, the present invention can have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. An embedded software functional module design method based on the variability of software product lines, characterized in that The design method of embedded software functional modules based on software product line variability includes: sorting out and designing the overall functional requirements of the embedded software functional modules; sorting out and designing multiple basic modules required to meet the overall functional requirements; sorting out the variability parameter requirements in the overall functional requirements, and designing the form and transmission method of the variability parameters according to the variability parameter requirements; constructing multiple combined functional architectures adapted to the multiple basic modules according to the multiple variability parameters corresponding to the current software functional module, and each combined functional architecture realizes the functions related to the variability parameters; assembling the multiple combined functional architectures to form a complete embedded software functional module; The embedded software functional module is a filtering functional module; the filtering functional module includes a basic first-order filtering module, a basic second-order filtering module, and a basic third-order filtering module; the variability parameters of the filtering functional module include the data body, whether to filter multiple times, the required filtering order, and the corresponding filtering coefficients; The multiple combined functional architectures of the filtering functional module include: Judging the parameter validity according to the parameter restrictions in the variability parameter requirements, and returning a fault flag if the parameter is invalid; For the data that only needs to be filtered once, parameter assignment and filtering processing are performed according to different orders; For the data that needs to be filtered multiple times, parameter assignment and filtering processing are performed for multiple times with the same order; For the data that needs to be filtered multiple times, parameter assignment and filtering combination processing are performed for multiple times with different orders each time; Return the final filtering result; The form of the variability parameter of the filtering functional module is a filtering analysis word, and the content represents the number of times of filtering required and the filtering order required.

Images