A multi-channel-based software engineering source code management method

Abstract

The application discloses a kind of based on multi-channel software engineering source code management method, comprising the following steps: S1: according to design requirement, collate software function attribute, obtain the data satisfying design needs and process and define it;S2: according to the definition of data in S1, unify all business interfaces and form basic layer, provide basic service;S3: according to different chip code, in the same parent class structure of basic layer, different chip code is constructed in multi-channel directory identification;S4: different source code packaging mode is formed to form packaged file according to the difference of terminal environment;S5: the packaged file in S4 is packaged.The present application provides a kind of based on multi-channel software engineering source code management method for the problems such as that existing technology is not strong, is not conducive to version control and rapid iteration.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a multi-channel software engineering source code management method. Background Technology

[0002] Event-driven architecture is frequently used in software engineering source code management. This approach divides the system into three layers: the UI layer, the business logic layer, and the data layer. When an event state changes, such as when a user triggers the current interface, the system sends a message to an event queue, which is then distributed to different event handlers based on the specific business logic. Event-driven architecture facilitates the expansion of distributed asynchronous architectures and can drive various types of business logic. However, depending on the specific business logic, a fixed set of code is required for implementation. Faced with frequent changes in requirements, such as changes in chip manufacturers' solutions, a single fixed codebase leads to poor adaptability. Programmers need to rebuild the underlying foundational code, resulting in a large amount of repetitive business logic code when copying code for common requirements. This is prone to bugs and hinders version control and rapid iteration. Summary of the Invention

[0003] In view of the above-mentioned shortcomings of the existing technology, the purpose of this invention is to provide a software engineering source code management method based on multiple channels, so as to solve the problems of poor adaptability and unfavorable version control and rapid iteration of the existing technology by using a fixed set of code.

[0004] To address the aforementioned technical problems, this invention provides a multi-channel software engineering source code management method, comprising the following steps:

[0005] S1: Based on the design requirements, organize the software functional attributes, obtain the data that meets the design needs, and process and define it;

[0006] S2: Based on the data definition in S1, unify all business interfaces and form a basic layer to provide basic business services;

[0007] S3: Based on different chip codes, construct multi-channel directory identifiers for different chip codes within the same parent class structure in the base layer;

[0008] S4: Different source code packaging methods are used to create packaged files depending on the terminal environment;

[0009] S5: Package the files in S4.

[0010] Compared with the prior art, the present invention has the following beneficial effects:

[0011] This invention addresses different scenarios for chip manufacturers' exchange solutions, enabling the implementation of multiple different scenarios using a single codebase. This greatly enhances adaptability and scalability. The multi-channel catalogs built for different chip manufacturers, combined with version management tools, greatly improve version readability and effectively solve the problems of version control and rapid iteration. Attached Figure Description

[0012] Figure 1 This is the overall flowchart of the present invention.

[0013] Figure 2 This is a flowchart illustrating the overall packaging process of the Apk file for this invention.

[0014] Figure 3 This is a schematic diagram of the multi-channel configuration directory of the present invention. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on the present invention. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0016] This invention provides a multi-channel software engineering source code management method, such as... Figure 1 As shown, it includes the following steps:

[0017] S1: Based on the design requirements, organize the software functional attributes, obtain data that meets the design needs, and process and define it. After obtaining, processing, and defining the data that meets the design requirements, a complete data requirements document is obtained. In this practical step, it is necessary to negotiate with the chip manufacturer in advance to obtain a complete requirements document, as subsequent interface definition operations depend on this.

[0018] S2: Based on the data definition in S1, unify all business interfaces and form a basic layer for... Figure 2 The base layer provides basic business logic. In S2, a complete list of interface definitions is extracted and used as a common dependency for the multi-channel directories in the base layer. In practice, a new `src / main` directory is created, and the various interface definitions are established as unified API interfaces exposed by the business logic. All subsequent business logic must implement the interfaces in the base layer.

[0019] S3: Based on different chip codes, multi-channel directory identifiers are constructed within the same parent class structure of the base layer for different chip codes. In S3, based on the different version identifiers of different chips, and also based on the structure of the multi-channel software engineering source code, multi-channel directory identifiers are constructed within the same parent class structure of the base layer according to the version identifiers of different chips. When referenced, the core business logic is implemented by relying on the base layer.

[0020] Different terminal environments will lead to differences in the configuration of the packaged files. This operation needs to be based on the structure of the source code of the software engineering from multiple channels.

[0021] In an Android development environment, when using multi-channel packaging technology, you configure files in the root tag file to define product features, and define the names of the multi-channels according to different chipsets. In practice, this relies on the base layer in S2, using Gradle multi-channel packaging technology to first generate the necessary packaging files. Specifically, you need to configure `productFlavors` in `build.grale`, and the defined multi-channel names can be customized according to the chip manufacturer, such as... Figure 3 The directory shown requires defining module1 and module2 in flavorDimensions. This approach greatly improves the extensibility requirements in software engineering. If new business functions are needed, simply extend productFlavors to define module3, and so on. It also meets the readability requirements of version control. Furthermore, defining modules for different chip manufacturers allows users to view the commit history of the corresponding versions, facilitating management and maintenance.

[0022] In an Android source code environment, different version identifiers are defined for different chips on the server. In practice, this requires defining version identifiers for different chip manufacturers on a Linux server.

[0023] S4: Different source code packaging methods are used to form packaged files depending on the terminal environment.

[0024] If the terminal environment is an Android development environment, the source code sets for different chips are generated and packaged according to the S3 configuration files. In practice, Gradle multi-channel packaging technology is used to integrate and package the source code of different chip manufacturers into APK files. This operation relies on the Gradle framework built in S3, which uses a JVM-based build tool primarily for Java, and uses SDL to configure the project structure, avoiding the cumbersome XML configuration of other methods.

[0025] If the terminal environment is an Android source code environment, a new script file is created within this environment. This script file reads the identifiers of different chips and configures different multi-channel file directories accordingly, integrating the Android source code compilation and packaging image file. In practical implementation, relying on the main compilation rules in `build / core / Makefile`, version identifiers for different chip manufacturers need to be defined on the Linux server. Within the current source code environment, a new `Android.mk` file is created, configuring different multi-channel file directories based on the read chip manufacturer version identifiers, integrating the Android source code compilation and packaging image file.

[0026] S5: Package the files in S4.

[0027] Among them, such as Figure 2 As shown, in the Android development environment, if the packaging files generated in S4 are packaged together using packaging tools, the specific steps are as follows: use the AAPT tool to compile the relevant resource files to generate R files, then use the Javac tool to compile the project source code to generate class files, and finally use the Dx tool to convert the class files into bytecode files.

[0028] In the Android source code environment, the files generated by S4 are packaged using a tool program, signed by a signing tool, and then output to the final directory. The specific operation is as follows: use the ApkBuilder tool to package the files that need to be generated before step S5 into an Apk file, sign the Apk file through KeyStore, and build a release version for further optimization before releasing the official version.

[0029] This invention addresses different scenarios for chip manufacturers' exchange solutions, enabling the implementation of multiple different scenarios using a single codebase. This greatly enhances adaptability and scalability. The multi-channel catalogs built for different chip manufacturers, combined with version management tools, greatly improve version readability and effectively solve the problems of version control and rapid iteration.

[0030] As described above, the reminder system of the present invention is not limited to the configuration described herein, and other systems that can implement the embodiments of the present invention can fall within the scope of protection of the present invention.

[0031] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit the technical solutions. Those skilled in the art should understand that any modifications or equivalent substitutions to the technical solutions of the present invention without departing from the spirit and scope of the present invention should be covered within the scope of the claims of the present invention.

Claims

1. A software engineering source code management method based on multiple channels, characterized in that, Includes the following steps: S1: Based on the design requirements, organize the software functional attributes, obtain the data that meets the design needs, and process and define it; S2: Based on the data definition in S1, unify all business interfaces and form a base layer to provide basic business services; among them, create a new src / main directory, establish the definitions of each interface, which serve as the unified API interfaces exposed by the business. All subsequent businesses need to implement the interfaces in the base layer. S3: Based on different chip codes, construct different multi-channel directories and place them in the same parent directory within the base layer; based on different version identifiers in different chips, and based on the structure of the multi-channel software engineering source code, construct multi-channel directory identifiers in the same parent class structure of the base layer according to the version identifiers of different chips, and rely on the base layer to implement core business logic when referencing them; if in the Android development environment, through multi-channel packaging technology, configure files for defining product characteristics in the root tag file, and define the names of the multi-channels according to different chips; if in the Android source code environment, define different version identifiers for different chips in the server; S4: Depending on the terminal environment, different packaging methods are used to form corresponding packaged files for different source code structures; among them, if in the Android source code environment, a new script file is created in the current source code environment, and the script file reads the identification number of different chips, thereby configuring different multi-channel file directories and integrating the Android source code compilation and packaging image file. S5: Package the files in S4.

2. The software engineering source code management method based on multiple channels according to claim 1, characterized in that, In S1, after acquiring, processing, and defining the data that meets the design requirements, a complete data requirements document is obtained.

3. The software engineering source code management method based on multiple channels according to claim 1, characterized in that, In S4, if in the Android development environment, based on the files configured in S3, source code sets of different chips can be generated and packaged.

4. The software engineering source code management method based on multiple channels according to claim 3, characterized in that, In S5, the packaging files generated in S4 are packaged together using packaging software.

5. The software engineering source code management method based on multiple channels according to claim 1, characterized in that, In S5, if in the Android source code environment, the files generated by S4 are packaged using a tool program, signed by a signing tool, and then output to the final directory.

Images