Component-based electronic product digitization debugging process debugging item design method

Abstract

The application relates to the technical field of digital debugging, and discloses a debugging item design method of an electronic product digital debugging process based on components, which explicitly defines the debugging item content and the design process of the debugging process, classifies the debugging item content and the design process, constructs a component library which can be dragged according to types by using software technology, and changes the debugging item design process from text editing to component design. The application solves the problems of poor universality, low standardization degree and difficulty in convenient and rapid design of the prior art.

Description

Technical Field

[0001] This invention relates to the field of digital debugging technology, specifically a debugging project design method for component-based digital debugging processes of electronic products. Background Technology

[0002] As electronic products evolve towards higher integration and multifunctionality, their manufacturing complexity increases accordingly. Debugging is a crucial process in electronic product manufacturing, especially for military products. After manufacturing and assembly, electronic products require debugging to ensure their performance meets design requirements. Debugging encompasses both adjustment and testing. Adjustment involves modifying the parameters of discrete or integrated components. Testing utilizes excitation signal generators to produce excitation signals, which are then processed by the product and output to testing instruments to verify if the signal parameters meet design requirements. Debugging is a complex process involving comprehensive operation of the product, instruments, and equipment. It requires guidance from debugging process guidelines for on-site workers to ensure accurate operation and product safety. The debugging process document defines the debugging procedures, requirements, and operating methods during product manufacturing. It serves as the sole basis for product debugging and quality assurance, and also acts as a work manual and operating guide for debugging personnel.

[0003] Current debugging processes are primarily described in text form, focusing on being "human-readable." This text-based approach results in lengthy documents that require careful manual reading. Users then set product operating parameters, adjust instrument parameters, manually record test data, and compare it with debugging indicators. The debugging process design relies heavily on the experience of product technicians for textual compilation. Different designers often provide highly arbitrary descriptions of the same thing, leading to inconsistent process structures, non-standardized content, ambiguity, and an inability to support digital debugging operations.

[0004] To improve debugging efficiency, the current manual debugging mode will be changed to automated debugging, especially the testing part. This will involve specialized software personnel, or collaboration with software development companies, to develop automated testing systems for specific products. The implementation of automated testing systems has significantly improved product debugging efficiency, saved human resources, and reduced the difficulty of debugging operations. However, the development process of automated testing systems is also relatively complex. It requires specialized software personnel familiar with product debugging methods and processes to develop the automated testing system and solidify these methods and processes through code. During the development of automated testing systems, developers need to consult product debugging processes and study their methods, which hinders the development efficiency of automated testing systems and is not conducive to improving the overall product debugging efficiency. Transforming text-based debugging processes into digital debugging processes, with the digital processes directly driving the debugging hardware system to execute automatically, eliminates the need for automated testing system development and facilitates the widespread application of debugging automation.

[0005] Digital debugging processes digitize text-based debugging procedures, enabling computers to recognize and load them, driving the debugging hardware system to execute automatically and automatically collect debugging data. The design process for digital debugging processes requires rigorous standardization; all aspects of the debugging process must be designed according to a prescribed format to drive the debugging hardware system to execute automatically. Traditional text-based editing methods are no longer suitable for the design requirements of digital debugging processes. A unified and convenient design model is needed to reduce the error rate in the digital debugging process design and improve its usability.

[0006] The digital commissioning process consists of numerous script files, including configuration files, commissioning procedures, and commissioning project sets. The commissioning project set is a crucial component of the process, comprising many individual commissioning project script files that describe the specific commissioning methods and steps for each project. The content and format of each script file are relatively fixed. The main tasks in designing commissioning projects are determining the instrument setup methods, setup sequence, data reading, and result processing. Summary of the Invention

[0007] To overcome the shortcomings of existing technologies, this invention provides a design method for debugging projects in the digital debugging process of electronic products based on components, which solves the problems of poor universality, low standardization, and difficulty in convenient and rapid design in existing technologies.

[0008] The technical solution adopted by the present invention to solve the above problems is:

[0009] This paper presents a component-based digital debugging process for electronic products, which defines the debugging project content and design process, and categorizes the debugging project content and design process. Then, using software technology, a draggable component library is built according to type. Components are dragged and dropped, and component parameters are set to generate debugging project content, thus transforming the debugging project design process from text-based editing to component-based design.

[0010] As a preferred technical solution, the steps include:

[0011] S1. Clarify the content of the commissioning process, as well as the operational steps required in designing the commissioning process, and classify these contents and steps.

[0012] S2, through code programming, multiple draggable controls are formed on the interface. Each control is named according to the classification type in step S1, forming a component library, which is displayed through the interface.

[0013] S3, Build a debug resource driver library: Encapsulate the content required for debugging process design into a debug resource driver library in the form of classes through code programming;

[0014] S4. Extract the class names, method names, parameter names and default parameter values ​​from the debug resource driver library encapsulated in step S3 to form a structured data resource library. According to the data type, associate the extracted data with the component library formed in step S2.

[0015] S5 allows you to create a component parameter setting interface through code programming to set component parameter content. When designing and debugging a project, drag and drop a component, click on the component, refresh the component parameter setting interface, and complete the setting of component parameter content.

[0016] S6 allows you to create and debug project design interfaces through code programming. The debug project design interface includes the current component and component content. The current component is used to place components dragged from the component library, and the component content is used to display information about the current component.

[0017] S7 allows you to drag and drop components, set component content, automatically generate debug project content, and complete the debug project design.

[0018] As a preferred technical solution, in step S1, the classification types include one or more of the following: debugging project creation, instrument settings, tooling settings, common methods, parameter settings, variable assignment, control statements, loop statements, and custom settings.

[0019] As a preferred technical solution, in step S3, the debugging resource driver library includes one or more of the following: instrument driver library, tooling driver library, general method library, and keyword library.

[0020] As a preferred technical solution, in step S5, the interface information of the component settings interface includes one or more of the following: project name, project parameters, and default parameters.

[0021] As a preferred technical solution, in step S5, the project name is dynamically refreshed according to the current component type.

[0022] As a preferred technical solution, in step S5, the project parameter display shows the structured data corresponding to the component extracted in step S4, with some information selected via drop-down menus.

[0023] As a preferred technical solution, in step S5, the default parameter displays the default parameter values ​​extracted in step S4.

[0024] As a preferred technical solution, the specific method of step S7 is as follows: according to the design requirements of the debugging project, drag the corresponding component from the component library to the current component column in step S6, click the component, automatically refresh the content of the component settings area in step S5, select the corresponding information from the drop-down menu, modify its default parameter value, and determine its component content; then, according to the component type, combine the component content information with the indentation amount when generating the content in the prescribed format.

[0025] As a preferred technical solution, the following steps are also included:

[0026] S8: After completing step S7, convert the debugging items in the component content column of step S6 into a computer-executable script file line by line.

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

[0028] (1) High versatility and standardization: This invention presents the creation of debugging projects, instrument settings, tooling settings, common methods, parameter settings, variable assignment, control statements, loop statements, and custom settings of the debugging process to process designers in the form of components, which standardizes the presentation of the debugging project content and can be applied to the design of all digital debugging processes, thus having high versatility; This invention specifies the design process of debugging projects. By dragging and dropping components and setting component content, the design of the debugging process can be completed, avoiding ambiguity in the description of the same debugging content by different debugging process designers, thus having high standardization;

[0029] (2) The design of debugging projects in digital debugging process is more convenient and faster: Based on the content and design process of debugging projects in digital debugging process, this invention uses software technology to transform the design process from the original text editing to component-based design; the debugging process designer does not need to care about the presentation of the content, but can complete the design of the debugging project content by dragging and dropping components and setting the component content. Compared with the text editing method of designing debugging project content, the component-based design is more convenient and faster.

[0030] (3) The design method of debugging projects has been optimized: This invention transforms the design of debugging projects from text-based editing to a component-based design method. The design process of debugging projects is presented to the designer in the form of a component library. The designer only needs to drag and drop components and set the component content to automatically generate the debugging project content, without having to edit the debugging project content through text input. Attached Figure Description

[0031] Figure 1 Design a flowchart for the debugging project;

[0032] Figure 2 Design an interface diagram for debugging the project;

[0033] Figure 3 A schematic diagram of the component parameter settings interface. Detailed Implementation

[0034] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.

[0035] Example 1

[0036] like Figures 1 to 3 As shown, in order to realize the transformation of electronic product text-based debugging process to digital debugging process and adapt to the needs of digital debugging process design, it is necessary to first ensure that the debugging project design process is digitalized, simplified and standardized. This invention proposes a debugging project design method for digital debugging process that is universal, highly standardized, fast, simple and easy to use.

[0037] In order to improve the design efficiency and reduce the design difficulty of debugging projects, this invention can solidify the design process and implement relevant design content by dragging and dropping components and setting the component content.

[0038] To achieve the above objectives, this invention provides a component-based digital debugging process design method for electronic products, comprising the following steps: First, clarifying the content and design process of the debugging process, and classifying the content and design process; the types can be divided into debugging project creation, instrument setting, tooling setting, common methods, parameter setting, variable assignment, control statements, loop statements, and custom settings; using software technology to construct a draggable component library according to type, providing it to the debugging process designer; encapsulating the underlying resource driver library in the form of classes and methods; extracting the resource driver library to form structured data information, and associating this data with the aforementioned component library; creating a component setting interface for setting component content; creating a debugging project design interface for designing the specific content of the debugging project; dragging and dropping the component library, setting component content, and automatically generating debugging project content according to the prescribed format; converting the debugging project content on the interface line by line into a computer-executable script file. This achieves a unified, standardized, and rapid design function for debugging process projects, reducing reliance on the experience of the debugging process designer.

[0039] See Figure 1 According to embodiments of the present invention, the debugging project content and design process of the debugging process are first clearly defined, and the content and design process are classified. These types can be categorized into debugging project creation, instrument settings, tooling settings, common methods, parameter settings, variable assignment, control statements, loop statements, and custom settings. A draggable component library is constructed according to these types using software technology and provided to the debugging process designer. The underlying resource driver library is encapsulated in the form of classes and methods. The resource driver library is extracted to form structured data information, and this data is associated with the aforementioned component library. A component setting interface is created for setting component content. A debugging project design interface is created for designing the specific content of the debugging project. The component library is dragged and dropped, component content is set, and the debugging project content is automatically generated according to a specified format. The debugging project content on the interface is converted line by line into a computer-executable script file. This achieves a unified, standardized, and rapid design function for the debugging project of the debugging process, reducing reliance on the experience of the debugging process designer.

[0040] Step S1: Clarify the content of the commissioning process, and what operation steps S need to be performed during the design and commissioning process. Classify these contents and steps S. The types can be divided into commissioning project creation, instrument setting, tooling setting, common methods, parameter setting, variable assignment, control statement, loop statement, custom settings, etc.

[0041] Step S2: Using software technology, multiple draggable controls are created on the interface through code programming. Each control is named according to the above classification type to form a component library. This component library is displayed to the debugging process designer through the interface. When designing and debugging processes, the corresponding components in the component library can be dragged and dropped.

[0042] Step S3: Construct debugging resource driver libraries, including instrument driver libraries, tooling driver libraries, general method libraries, keyword libraries, and other resource libraries. Through code programming, encapsulate the content required for debugging process design into class methods to form various resource and driver libraries.

[0043] Step S4: Extract the resource driver library, form structured data, and associate it with the component library. Extract the encapsulated class names, method names, parameter names, and default parameter values ​​to form a structured data resource library. Based on the data type, associate the extracted data with the aforementioned component library one by one.

[0044] Step S5: Using software technology, create a component settings interface through code programming to set component parameters. The interface information includes the project name, project parameters, and default parameters. During process design and debugging, drag and drop the component, click on the component, refresh the content of that area, and complete the settings. The project name dynamically refreshes based on the current component type; the project parameters display the structured data corresponding to the component extracted in step S4, with some information selected via dropdown menus; the default parameters display the default parameter values ​​extracted in step S4.

[0045] Step S6: Using software technology, create a debugging project design interface through code programming, which includes two columns of information: the current component and the component content. The current component column is used to place components dragged from the component library, and the component content is used to display the current component information.

[0046] Step S7: Drag and drop components, set component content, automatically generate debugging project content, and complete the debugging project design. According to the debugging project design requirements, drag the corresponding component from the component library to the current component column in Step S6. Click the component to automatically refresh the component settings area in Step S5. Select the corresponding information from the dropdown menu, modify its default parameter values, and confirm its component content. Based on the component type, combine the component content information and the indentation amount when generating the content according to the prescribed format. First, combine the component content information, such as the "Instrument Settings Component" combination format: Instrument Settings.Instrument Name.Instrument Capabilities (Parameter Values). Following this format requirement, set a spectrum analyzer sweep width of 400MHz. The content automatically generated by the component will be: Instrument Settings.Spectrum Analyzer.Set Sweep Width (400e6). Second, fill the combined content into the component content column of Step S6, increasing the indentation amount according to the format requirements of the programming language. Repeat Step S7 to complete the other content of this debugging project.

[0047] Step S8: After completing the operation in step S7, convert the debugging project content in the component content column of step S6 into a computer-executable script file line by line, thus completing the design work of a single debugging project.

[0048] This invention provides a technical foundation for the design of debugging projects in the digital debugging process of electronic products in a quick, simple, and easy-to-use manner, thereby improving the design efficiency of the entire digital debugging process of electronic products.

[0049] Compared with the prior art, the present invention has the following beneficial effects.

[0050] 1) High versatility and standardization. This invention presents the creation of commissioning projects, instrument settings, tooling settings, common methods, parameter settings, variable assignments, control statements, loop statements, and custom settings in a component-based manner to process designers. This standardizes the presentation of commissioning project content and can be applied to the design of all digital commissioning processes, demonstrating high versatility. This invention defines the design process for commissioning projects; simply drag and drop components and set their content to complete the design of the commissioning process. This avoids ambiguity in the description of the same commissioning content by different commissioning process designers, demonstrating high standardization.

[0051] 2) Digital debugging process design is more convenient and faster. Based on the content and design process of digital debugging processes, this invention utilizes software technology to transform the design process from text-based editing to component-based design. Debugging process designers no longer need to worry about the presentation format; they can complete the design of the debugging project content simply by dragging and dropping components and setting their content. Compared to text-based editing, component-based design is much more convenient and faster.

[0052] 3) The design method for debugging projects has been optimized. This invention transforms the design of debugging projects from text-based editing to a component-based design method. The design process is presented to designers in the form of a component library. Designers only need to drag and drop components and set their content to automatically generate the debugging project content, eliminating the need to edit the debugging project content through text input.

[0053] As described above, the present invention can be implemented well.

[0054] All features disclosed in all embodiments of this specification, or steps in all methods or processes implied in the disclosure, may be combined and / or extended or replaced in any way, except for mutually exclusive features and / or steps.

[0055] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Based on the technical essence of the present invention, any simple modifications, equivalent substitutions, and improvements made to the above embodiments within the spirit and principles of the present invention shall still fall within the protection scope of the present invention.

Claims

1. A method for designing debugging projects in the digital debugging process of electronic products based on components, characterized in that, Clearly define the content and design process of the commissioning process, and classify the content and design process of the commissioning items; Then, software technology is used to build a draggable component library by type. Components can be dragged and dropped, component parameters can be set, and debug project content can be generated, thus transforming the debug project design process from text-based editing to component-based design. The design method includes the following steps: S1. Clarify the content of the commissioning process, as well as the operational steps required in designing the commissioning process, and classify these contents and steps. S2, through code programming, multiple draggable controls are formed on the interface. Each control is named according to the classification type in step S1, forming a component library, which is displayed through the interface. S3, Build a debug resource driver library: Encapsulate the content required for debugging process design into a debug resource driver library in the form of classes through code programming; S4. Extract the class names, method names, parameter names and default parameter values ​​from the debug resource driver library encapsulated in step S3 to form a structured data resource library. According to the data type, associate the extracted data with the component library formed in step S2. S5 allows you to create a component parameter setting interface through code programming to set component parameter content. When designing and debugging a project, you can drag and drop a component, click on the component, refresh the component parameter setting interface, and complete the setting of the component parameter content. S6 allows you to create and debug project design interfaces through code programming. The debug project design interface includes the current component and component content. The current component is used to place components dragged from the component library, and the component content is used to display information about the current component. S7 allows you to drag and drop components, set component content, automatically generate debug project content, and complete the debug project design.

2. The debugging project design method for component-based digital debugging process of electronic products according to claim 1, characterized in that, In step S1, the classification types include one or more of the following: debugging project creation, instrument settings, tooling settings, common methods, parameter settings, variable assignment, control statements, loop statements, and custom settings.

3. The debugging project design method for component-based digital debugging process of electronic products according to claim 2, characterized in that, In step S3, the debugging resource driver library includes one or more of the following: instrument driver library, tooling driver library, general method library, and keyword library.

4. The debugging project design method for component-based digital debugging process of electronic products according to claim 3, characterized in that, In step S5, the interface information of the component settings interface includes one or more of the following: project name, project parameters, and default parameters.

5. The debugging project design method for component-based digital debugging process of electronic products according to claim 4, characterized in that, In step S5, the project name is dynamically refreshed based on the current component type.

6. The debugging project design method for component-based digital debugging process of electronic products according to claim 5, characterized in that, In step S5, the project parameters display the structured data corresponding to the component extracted in step S4, with some information selected via drop-down menus.

7. The debugging project design method for component-based digital debugging process of electronic products according to claim 6, characterized in that, In step S5, the default parameters are displayed as the default parameter values ​​extracted in step S4.

8. The debugging project design method for component-based digital debugging process of electronic products according to claim 7, characterized in that, The specific method for step S7 is as follows: According to the design requirements of the debugging project, drag the corresponding component from the component library to the current component column in step S6, click the component, automatically refresh the content of the component settings area in step S5, select the corresponding information from the drop-down menu, modify its default parameter value, and determine its component content; then, according to the component type, combine the component content information with the indentation amount when generating the content in the prescribed format.

9. The debugging project design method for component-based digital debugging process of electronic products according to any one of claims 1 to 8, characterized in that, It also includes the following steps: S8: After completing step S7, convert the debugging items in the component content column of step S6 into a computer-executable script file line by line.

Images