Service platform customization method based on assembly line

Abstract

The invention discloses a service platform customization method based on an assembly line, and relates to the technical field of software development, and the method comprises the steps: carrying out the classification of collected customer demand data, and generating customized demand data; according to the customized demand data, assembly line configuration is carried out, a function module set is generated, and an assembly line comprises a data source production line, a computational logic production line and an interactive system production line; performing platform construction through the function module set to generate an expected platform; according to the method, customer demand data is classified to generate customized demand data, and assembly line configuration is carried out in combination with a specific function module set, so that personalized construction of the platform is realized; the method ensures that the construction of the platform completely meets the function requirements, the performance requirements, the user interaction requirements and the data processing requirements of customers, so that each requirement is accurately analyzed and processed; furthermore, through configuration of a function module set, the assembly line automatically generates required function modules, and efficient construction of the platform is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and in particular to a service platform customization method and system based on an assembly line. Background Art

[0002] With the continuous development of informatization and intelligence, enterprises have an increasing demand for service platforms. However, existing service platform development methods usually rely on customized development, which often requires professional technicians to manually write a large amount of code, resulting in a long development cycle, high cost, and poor flexibility. With the diversification and rapid changes in enterprise business needs, traditional customized development methods have been unable to meet enterprises' rapid response and personalized needs for service platforms. Based on research and practical applications of existing technologies, it is found that existing technologies have at least the following defects:

[0003] (1) Low development efficiency: The traditional customized development process is complex and involves a lot of demand analysis, design, coding, and testing, which results in a long development cycle and difficulty in rapid delivery.

[0004] (2) High cost: Since custom development usually requires a lot of human resources and it is difficult to reuse existing codes or modules, the development cost is high;

[0005] (3) Lack of flexibility: In traditional methods, the functions of the platform are often fixed, making it difficult to flexibly adjust and expand them according to the actual needs of users. Summary of the invention

[0006] In order to solve the above technical problems, the present invention provides a service platform customization method based on assembly line.

[0007] A service platform customization method based on pipeline, comprising:

[0008] Classify the collected customer demand data and generate customized demand data;

[0009] Perform pipeline configuration according to customized demand data to generate a set of functional modules, where the pipeline includes a data source production line, a computing logic production line, and an interactive system production line;

[0010] The platform is constructed through a collection of functional modules to generate the desired platform.

[0011] Furthermore, the customization requirement data includes software function requirement information, performance requirement information, user interaction requirement information and data processing requirement information. The logic for classifying the collected customer requirement data is:

[0012] α1. Obtain customer demand data through online interviews, questionnaires, online market research, and filling out online demand documents;

[0013] α2, preliminarily organize the collected demand data and remove duplicate, irrelevant or unclear information; preliminarily identify the categories of customer needs based on the information provided by the customer, which include functional requirements, performance requirements, user interaction requirements and data processing requirements; preliminarily classify the identified customer needs into four categories: function, performance, user interaction and data processing;

[0014] α3, conduct detailed analysis of the functions, performance, user interaction and data processing in customer requirements, and further refine specific functional modules.

[0015] Furthermore, the functional module set includes a data processing module, a computing logic module and a user interface module, and the logic of pipeline configuration according to the customized demand data is:

[0016] Based on the customized demand data, the pipeline configuration is performed through the decision tree method. The execution steps of the decision tree method are:

[0017] Q1. Is real-time data processing required?

[0018] Yes: Enable the data source production line, generate data processing modules, store them in the preset "personal data source library" or publish them to the "public data source library";

[0019] No: Skip the data source production line and directly consider the next condition;

[0020] Q2: Is complex business logic processing required?

[0021] Yes: Enable the computing logic production line, generate computing logic modules, store them in the preset "personal computing logic library" or publish them to the "public computing logic library";

[0022] No: Skip the calculation logic line and directly consider the next condition;

[0023] Q3. Is a user interface required?

[0024] Yes: Enable the interactive system production line, generate interactive system modules, store them in the preset "Personal Interactive System Library" or publish them to the "Public Interactive System Library";

[0025] No: Skip the interactive system production line and output the final set of functional modules.

[0026] Furthermore, the logic of platform construction through a collection of functional modules is:

[0027] According to the configured function module set, call the module from the function module set, execute the module operation in the set order, and automatically generate the service platform. The generation process includes code generation, module integration and preliminary testing.

[0028] Furthermore, the logic of code generation is:

[0029] Generate corresponding code according to the definition and configuration of each module:

[0030] The core logic and functions of each module generate code through preset templates. Among them, the data processing module generates corresponding SQL queries or data processing scripts, the calculation logic module generates business logic code, and the interactive system module generates front-end UI code. While generating the code, the code is merged and optimized until the codes of different modules can be seamlessly integrated and the performance is stable.

[0031] Furthermore, the logic of module integration is:

[0032] After the code generation is completed, the modules are integrated into a unified service platform. The input and output of each module are bound through pre-defined standardized interfaces until the data of each module can be smoothly transmitted between different modules. Among them, the output of the data source module becomes the input of the calculation logic module, and the output of the calculation logic module is transmitted to the interactive system module for display. Each module is registered as an independent service for calling and management through the service bus or API gateway.

[0033] Furthermore, the logic of the preliminary test is:

[0034] After the module integration is completed, the generated platform is preliminarily tested and verified to ensure that its basic functions and performance meet the requirements. The independent functions of each module are tested until the functions of each module run according to the preset standards. Functional testing includes unit testing and integration testing.

[0035] Test the correctness of data exchange and interface calls between modules until the accuracy of interface binding and data flow integration reaches the preset accuracy threshold, and conduct interface testing to verify data format, transmission efficiency and error handling mechanism until the communication stability graph between modules tends to be stable; perform performance testing on the expected platform to evaluate the platform's response speed under load pressure, concurrent processing capabilities and resource consumption, and perform security checks on the expected platform, including identity authentication, permission management, and data encryption.

[0036] Furthermore, a pipeline-based service platform customization system is implemented based on any one of the pipeline-based service platform customization methods, including a data collection layer, a module configuration layer and a platform construction layer, wherein:

[0037] Data collection layer: used to classify the collected customer demand data and generate customized demand data;

[0038] Module configuration layer: used to configure the pipeline according to the customized demand data and generate a set of functional modules. The pipeline includes the data source production line, the calculation logic production line, and the interactive system production line;

[0039] Platform construction layer: used to build the platform through a collection of functional modules to generate the desired platform.

[0040] Further, a computer server comprises: a processor and a memory, wherein the memory stores a computer program that can be called by the processor;

[0041] The processor executes any one of the pipeline-based service platform customization methods by calling the computer program stored in the memory.

[0042] Further, a computer-readable storage medium stores a rewritable computer program;

[0043] When the computer program is executed on a computer device, any one of the pipeline-based service platform customization methods is executed in the computer device.

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

[0045] The present invention classifies customer demand data to generate customized demand data, and configures the pipeline in combination with a specific set of functional modules, thereby realizing personalized construction of the platform; this method ensures that the construction of the platform fully meets the customer's functional requirements, performance requirements, user interaction requirements and data processing requirements, so that each requirement is accurately analyzed and processed; the present invention also automatically generates the required functional modules through the configuration of the functional module set, thereby ensuring the efficient construction of the platform; the process uses the decision tree method to optimize the configuration of the pipeline, and the service platform finally generated undergoes code generation, module integration and preliminary testing to ensure the stability and performance of the platform. This systematic construction process not only improves the functionality and reliability of the platform, but also can flexibly respond to different customer needs. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0047] Figure 1 A flow chart of a service platform customization method based on an assembly line provided in Example 1 of the present invention;

[0048] Figure 2A module diagram of a pipeline-based service platform customization method provided in Example 2 of the present invention. DETAILED DESCRIPTION

[0049] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0050] Example 1

[0051] See also Figure 1 As shown, this embodiment discloses a service platform customization method based on pipeline, and the method includes:

[0052] S101: Classify the collected customer demand data and generate customized demand data;

[0053] Specifically, the customization requirement data includes software function requirement information, performance requirement information, user interaction requirement information and data processing requirement information;

[0054] The logic for classifying the collected customer demand data is:

[0055] α1. Obtain customer demand data through online interviews, questionnaires, online market research, and filling out online demand documents;

[0056] It is important to understand that these demand data may exist in various forms, including but not limited to text descriptions, tables, and charts;

[0057] α2, preliminarily organize the collected demand data and remove duplicate, irrelevant or unclear information; preliminarily identify the categories of customer needs based on the information provided by the customer, which include functional requirements, performance requirements, user interaction requirements and data processing requirements; preliminarily classify the identified customer needs into four categories: function, performance, user interaction and data processing;

[0058] It should be noted that this step is mainly to classify requirements that clearly belong to a certain category. For example, users' requirements for platform response speed can be classified as performance requirements, and requirements for interface layout can be classified as user interaction requirements.

[0059] α3, conduct detailed analysis of the functions, performance, user interaction and data processing in customer requirements, and further refine specific functional modules;

[0060] It should be noted that if the customer mentions the need for "user management" functions, it will be refined into specific functions such as "user registration, login, and permission management"; for example, response time, throughput, and number of concurrent users, these requirements are classified into performance requirements and further refined into specific performance indicators; the customer's requirements for data processing are analyzed and classified into data processing requirements, and according to the customer's needs, they are refined into specific contents such as data collection efficiency, data storage capacity, data analysis speed, and data security level, and examples are given;

[0061] Assume that the following points are mentioned in the customer demand data:

[0062] A user management system is needed to support user registration, login and permission management;

[0063] Classification: Classified as "functional requirements", refined into "user management module", the specific functions include "user registration, login, and permission management";

[0064] The platform needs to support at least 1,000 users online at the same time;

[0065] Classification: Classified as "performance requirements", specifically "concurrent user number requirement: at least 1,000";

[0066] The interface should be simple and intuitive, the navigation bar should be fixed at the top of the page, and the color matching should be consistent with the brand tone;

[0067] Classification: Classified as "user interaction requirements", and refined into "interface design requirements: simple and intuitive, fixed navigation bar, color matching in line with brand tone";

[0068] Data processing should be able to complete 50MB of data analysis within 5 seconds;

[0069] Classification: Classified as "data processing requirements", and refined into "data analysis efficiency: processing 50MB of data within 5 seconds".

[0070] Specifically, the customization requirement data includes software function requirement information, performance requirement information, user interaction requirement information and data processing requirement information;

[0071] It should be noted that the functional requirements information includes the main functional modules and their specific functions that the platform is expected to achieve, such as user management, order processing, and data analysis;

[0072] Performance requirement information includes requirements for platform performance, such as platform response time, throughput, and number of concurrent users;

[0073] User interaction demand information includes requirements for platform interface design, user experience, and interaction methods, such as interface layout, operation process, and user feedback;

[0074] Data processing demand information includes data processing requirements for the platform, such as data collection efficiency, data storage size, data analysis efficiency, and data security level;

[0075] S102: Perform pipeline configuration according to the customization requirement data to generate a set of functional modules, wherein the pipeline includes a data source production line, a computing logic production line, and an interactive system production line;

[0076] Specifically, the functional module set includes a data processing module, a computing logic module and a user interface module;

[0077] Specifically, the logic of pipeline configuration according to customized demand data is:

[0078] Based on the customized demand data, the pipeline configuration is performed through the decision tree method. The execution steps of the decision tree method are:

[0079] Q1. Is real-time data processing required?

[0080] Yes: Enable the data source production line, generate data processing modules, store them in the preset "personal data source library" or publish them to the "public data source library";

[0081] No: Skip the data source production line and directly consider the next condition;

[0082] Q2: Is complex business logic processing required?

[0083] Yes: Enable the computing logic production line, generate computing logic modules, store them in the preset "personal computing logic library" or publish them to the "public computing logic library";

[0084] No: Skip the calculation logic line and directly consider the next condition;

[0085] Q3. Is a user interface required?

[0086] Yes: Enable the interactive system production line, generate interactive system modules, store them in the preset "Personal Interactive System Library" or publish them to the "Public Interactive System Library";

[0087] No: Skip the interactive system production line and output the final set of functional modules.

[0088] S103: constructing a platform through a set of functional modules to generate a desired platform;

[0089] Specifically, the logic of building a platform through a set of functional modules is:

[0090] According to the configured function module set, call the module from the function module set, execute the module operation in the set order, and automatically generate the service platform. The generation process includes code generation, module integration and preliminary testing;

[0091] Specifically, the logic of code generation is:

[0092] Generate corresponding code according to the definition and configuration of each module:

[0093] The core logic and functions of each module generate code through preset templates. Among them, the data processing module generates corresponding SQL queries or data processing scripts, the calculation logic module generates business logic code, and the interactive system module generates front-end UI code. While generating the code, the code is merged and optimized until the codes of different modules can be seamlessly integrated and the performance is stable.

[0094] It should be noted that the code optimization includes but is not limited to eliminating redundant code, merging repeated logic, and compressing code size.

[0095] Specifically, the logic of module integration is:

[0096] After the code generation is completed, the modules are integrated into a unified service platform. The input and output of each module are bound through pre-defined standardized interfaces until the data of each module can be smoothly transmitted between different modules. Among them, the output of the data source module becomes the input of the calculation logic module, and the output of the calculation logic module is transmitted to the interactive system module for display. Each module is registered as an independent service to be called and managed through the service bus or API gateway.

[0097] It is important to understand that service registration enables the system to schedule each module according to the actual operating conditions and support subsequent expansion.

[0098] Specifically, the logic of the preliminary test is:

[0099] After the module integration is completed, the generated platform is preliminarily tested and verified to ensure that its basic functions and performance meet the requirements. The independent functions of each module are tested until the functions of each module run according to the preset standards. Functional testing includes unit testing and integration testing.

[0100] It should be noted that: unit testing is used to test the independent functions of modules, and integration testing is used to test the collaborative work between modules;

[0101] Test the correctness of data exchange and interface calls between modules until the accuracy of interface binding and data flow integration reaches the preset accuracy threshold, and conduct interface testing to verify data format, transmission efficiency and error handling mechanism until the communication stability graph between modules tends to be stable; perform performance testing on the expected platform to evaluate the platform's response speed under load pressure, concurrent processing capabilities and resource consumption, and perform security checks on the expected platform, including identity authentication, permission management, and data encryption.

[0102] Example 2

[0103] See also Figure 2 As shown, based on the unified inventive concept, this embodiment discloses a service platform customization system based on pipeline, the system includes a data collection layer, a module configuration layer and a platform construction layer, wherein:

[0104] Data collection layer S203: used to classify the collected customer demand data and generate customized demand data;

[0105] The customization requirement data includes software function requirement information, performance requirement information, user interaction requirement information and data processing requirement information. The logic for classifying the collected customer requirement data is:

[0106] α1. Obtain customer demand data through online interviews, questionnaires, online market research, and filling out online demand documents;

[0107] α2, preliminarily organize the collected demand data and remove duplicate, irrelevant or unclear information; preliminarily identify the categories of customer needs based on the information provided by the customer, which include functional requirements, performance requirements, user interaction requirements and data processing requirements; preliminarily classify the identified customer needs into four categories: function, performance, user interaction and data processing;

[0108] α3, conduct detailed analysis of the functions, performance, user interaction and data processing in customer requirements, and further refine specific functional modules.

[0109] Module configuration layer S202: used to configure the pipeline according to the customized demand data and generate a set of functional modules. The pipeline includes a data source production line, a calculation logic production line, and an interactive system production line;

[0110] The functional module set includes a data processing module, a computing logic module and a user interface module. The logic of pipeline configuration according to customized demand data is:

[0111] Based on the customized demand data, the pipeline configuration is performed through the decision tree method. The execution steps of the decision tree method are:

[0112] Q1. Is real-time data processing required?

[0113] Yes: Enable the data source production line, generate data processing modules, store them in the preset "personal data source library" or publish them to the "public data source library";

[0114] No: Skip the data source production line and directly consider the next condition;

[0115] Q2: Is complex business logic processing required?

[0116] Yes: Enable the computing logic production line, generate computing logic modules, store them in the preset "personal computing logic library" or publish them to the "public computing logic library";

[0117] No: Skip the calculation logic line and directly consider the next condition;

[0118] Q3. Is a user interface required?

[0119] Yes: Enable the interactive system production line, generate interactive system modules, store them in the preset "Personal Interactive System Library" or publish them to the "Public Interactive System Library";

[0120] No: Skip the interactive system production line and output the final set of functional modules.

[0121] Platform construction layer S203: used to construct the platform through a set of functional modules to generate a desired platform;

[0122] The logic of platform construction through a collection of functional modules is:

[0123] According to the configured function module set, call the module from the function module set, execute the module operation in the set order, and automatically generate the service platform. The generation process includes code generation, module integration and preliminary testing;

[0124] The logic of code generation is:

[0125] Generate corresponding code according to the definition and configuration of each module:

[0126] The core logic and functions of each module are coded through preset templates. The data processing module generates corresponding SQL queries or data processing scripts, the calculation logic module generates business logic codes, and the interactive system module generates front-end UI codes. While generating codes, the codes are merged and optimized until the codes of different modules can be seamlessly integrated and stable in performance.

[0127] The logic of module integration is:

[0128] After the code generation is completed, the modules are integrated into a unified service platform. The input and output of each module are bound through pre-defined standardized interfaces until the data of each module can be smoothly transmitted between different modules. Among them, the output of the data source module becomes the input of the calculation logic module, and the output of the calculation logic module is transmitted to the interactive system module for display. Each module is registered as an independent service to be called and managed through the service bus or API gateway.

[0129] The logic of the initial test is:

[0130] After the module integration is completed, the generated platform is preliminarily tested and verified to ensure that its basic functions and performance meet the requirements. The independent functions of each module are tested until the functions of each module run according to the preset standards. Functional testing includes unit testing and integration testing.

[0131] Test the correctness of data exchange and interface calls between modules until the accuracy of interface binding and data flow integration reaches the preset accuracy threshold, and conduct interface testing to verify data format, transmission efficiency and error handling mechanism until the communication stability graph between modules tends to be stable; perform performance testing on the expected platform to evaluate the platform's response speed under load pressure, concurrent processing capabilities and resource consumption, and perform security checks on the expected platform, including identity authentication, permission management, and data encryption.

[0132] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website site, computer, server or data center to another website site, computer, server or data center through a wired network or a wireless network. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD) or a semiconductor medium. The semiconductor medium can be a solid-state hard disk.

[0133] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the present invention can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0134] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0135] In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a service platform customization method based on an assembly line. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0136] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0137] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0138] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

[0139] Finally: The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A service platform customization method based on assembly line, characterized in that: The method comprises: Classify the collected customer demand data and generate customized demand data; Perform pipeline configuration according to customized demand data to generate a set of functional modules, where the pipeline includes a data source production line, a computing logic production line, and an interactive system production line; The platform is constructed through a collection of functional modules to generate the desired platform.

2. The service platform customization method based on pipeline according to claim 1, characterized in that: The customization requirement data includes software function requirement information, performance requirement information, user interaction requirement information and data processing requirement information. The logic for classifying the collected customer requirement data is: α1. Obtain customer demand data through online interviews, questionnaires, online market research, and filling out online demand documents; α2, preliminarily organize the collected demand data and remove duplicate, irrelevant or unclear information; preliminarily identify the categories of customer needs based on the information provided by the customer, which include functional requirements, performance requirements, user interaction requirements and data processing requirements; Preliminarily categorize the identified customer needs into four categories: functionality, performance, user interaction, and data processing; α3, conduct detailed analysis of the functions, performance, user interaction and data processing in customer requirements, and further refine specific functional modules.

3. The service platform customization method based on pipeline according to claim 2, characterized in that: The functional module set includes a data processing module, a computing logic module and a user interface module. The logic of pipeline configuration according to customized demand data is: Based on the customized demand data, the pipeline configuration is performed through the decision tree method. The execution steps of the decision tree method are: Q1. Is real-time data processing required? Yes: Enable the data source production line, generate data processing modules, store them in the preset "Personal Data Source Library" or publish them to the "Public Data Source Library"; No: Skip the data source production line and directly consider the next condition; Q2: Is complex business logic processing required? Yes: Enable the computing logic production line, generate computing logic modules, store them in the preset "personal computing logic library" or publish them to the "public computing logic library"; No: Skip the calculation logic line and directly consider the next condition; Q3. Is a user interface required? Yes: Enable the interactive system production line, generate interactive system modules, store them in the preset "Personal Interactive System Library" or publish them to the "Public Interactive System Library"; No: Skip the interactive system production line and output the final set of functional modules.

4. The service platform customization method based on pipeline according to claim 3 is characterized in that: The logic of platform construction through a collection of functional modules is: According to the configured function module set, call the module from the function module set, execute the module operation in the set order, and automatically generate the service platform. The generation process includes code generation, module integration and preliminary testing.

5. The service platform customization method based on pipeline according to claim 4 is characterized in that: The logic of code generation is: Generate corresponding code according to the definition and configuration of each module: The core logic and functions of each module generate code through preset templates. Among them, the data processing module generates corresponding SQL queries or data processing scripts, the calculation logic module generates business logic code, and the interactive system module generates front-end UI code. While generating the code, the code is merged and optimized until the codes of different modules can be seamlessly integrated and the performance is stable.

6. The service platform customization method based on pipeline according to claim 5, characterized in that: The logic of module integration is: After the code generation is completed, the modules are integrated into a unified service platform. The input and output of each module are bound through pre-defined standardized interfaces until the data of each module can be smoothly transmitted between different modules. Among them, the output of the data source module becomes the input of the calculation logic module, and the output of the calculation logic module is transmitted to the interactive system module for display. Each module is registered as an independent service for calling and management through the service bus or API gateway.

7. The service platform customization method based on pipeline according to claim 6, characterized in that: The logic of the initial test is: After the module integration is completed, the generated platform is preliminarily tested and verified to ensure that its basic functions and performance meet the requirements. The independent functions of each module are tested until the functions of each module run according to the preset standards. Functional testing includes unit testing and integration testing. Test the correctness of data exchange and interface calls between modules until the accuracy of interface binding and data flow integration reaches the preset accuracy threshold, and conduct interface testing to verify data format, transmission efficiency and error handling mechanism until the communication stability graph between modules tends to be stable; perform performance testing on the expected platform to evaluate the platform's response speed under load pressure, concurrent processing capabilities and resource consumption, and perform security checks on the expected platform, including identity authentication, permission management, and data encryption.

8. A service platform customization system based on an assembly line, which is implemented based on the service platform customization method based on an assembly line according to any one of claims 1 to 7, characterized in that: It includes data collection layer, module configuration layer and platform construction layer, among which: Data collection layer: used to classify the collected customer demand data and generate customized demand data; Module configuration layer: used to configure the pipeline according to the customized demand data and generate a set of functional modules. The pipeline includes the data source production line, the calculation logic production line, and the interactive system production line; Platform construction layer: used to build the platform through a collection of functional modules to generate the desired platform.

9. A computer server, characterized in that: include: A processor and a memory, wherein the memory stores a computer program that can be called by the processor; The processor executes the pipeline-based service platform customization method described in any one of claims 1-7 by calling the computer program stored in the memory.

10. A computer-readable storage medium, characterized in that: It stores a rewritable computer program; When the computer program is run on a computer device, the computer device executes the pipeline-based service platform customization method described in any one of claims 1 to 7.

Images