Cooperative research and development platform, method, medium and equipment
By defining a collaborative SDK in software development, a unified interface is provided to integrate the algorithm development code of various business lines, solving the problem of low efficiency in collaborative work between different R&D systems and achieving efficient software development and quality assurance.
Patent Information
- Application Number
- CN202410473691.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-19
- Publication Date
- 2025-10-24
AI Technical Summary
How to improve the collaborative efficiency of different R&D systems during the software development process and ensure project quality, especially in software projects with multiple business lines.
By defining and creating a collaboration SDK, a unified business collaboration interface is provided, enabling the algorithm development code of each business line to be integrated into the architecture development code repository. This allows each business line to independently develop business logic without directly accessing the underlying system architecture code, and provides a unified function call method for architecture development.
This enabled multiple business lines to independently develop their businesses on the same platform, reducing communication costs and improving development efficiency and project quality.
Smart Images
Figure CN120833130A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of software development, and particularly relates to a collaborative development platform, method, medium and device. BACKGROUND
[0002] With the development of information technology, software projects become more and more complex. For those skilled in the art, how to make different development systems work collaboratively to improve development efficiency and ensure project quality is a technical problem to be faced. SUMMARY
[0003] Therefore, the present application provides a collaborative development platform, method, medium and device, which mainly aims to improve software development efficiency.
[0004] According to an aspect of the present application, a collaborative development platform is provided, and the development platform comprises an architecture development system and an algorithm development system, wherein,
[0005] The architecture development system maintains an architecture development code repository;
[0006] The algorithm development system maintains an algorithm development code repository, wherein each business line function logic corresponds to a set of algorithm development code;
[0007] The architecture development system is further configured to define and create a collaborative SDK, the collaborative SDK defines a unified business collaboration interface for each business line, and the algorithm development system is further configured to write algorithm development code corresponding to each business line function logic according to the business collaboration interface of the collaborative SDK, and integrate the algorithm development code as content of the collaborative SDK into the architecture development code repository.
[0008] In an implementation manner,
[0009] The architecture development system is specifically configured to analyze and aggregate function requirement information corresponding to each business line, and determine a unified business collaboration interface according to the function requirement information of each business line, so that each business line calls front-end and back-end interaction interfaces according to the business collaboration interface to implement business line function logic.
[0010] In an implementation manner,
[0011] The architecture development system is specifically configured to open a public resource interface in the collaborative SDK to enable each business line to call a public resource through the public resource interface, and create a collaborative base class of abstract class functions in the collaborative SDK to enable each business line to inherit the collaborative base class to obtain the abstract class functions, and implement business line function logic in the abstract class functions according to the business collaboration interface.
[0012] In an implementation manner,
[0013] The common resource interface includes one or more of a data processing common interface, a log recording common interface, and an error processing common interface.
[0014] In an implementation manner,
[0015] The algorithm research and development system is specifically configured to: for a business line function logic, create a collaborative subclass corresponding to the function logic, and override the abstract class function of the collaborative base class in the collaborative subclass according to the business collaboration interface, to obtain an algorithm research and development code corresponding to the business line function logic.
[0016] In an implementation manner,
[0017] The algorithm research and development system is further configured to: determine business line function logic change information or modification information, and change or modify the collaborative subclass according to the change information or modification information.
[0018] In an implementation manner,
[0019] The architecture research and development system is further configured to: read the collaborative subclass from the collaborative SDK, and call the abstract class function of the collaborative subclass to reference the business line function logic implemented by the algorithm research and development code.
[0020] According to an aspect of the present application, a collaborative research and development method is provided, comprising:
[0021] An architecture research and development code repository is maintained;
[0022] An algorithm research and development code repository is maintained, wherein each business line function logic corresponds to a set of algorithm research and development codes;
[0023] The collaborative SDK is defined and created, the collaborative SDK defines a unified business collaboration interface for each business line, and the algorithm research and development code corresponding to each business line function logic is written according to the business collaboration interface of the collaborative SDK, and the algorithm research and development code is integrated into the architecture research and development code repository as the content of the collaborative SDK.
[0024] In an implementation manner, the process of defining the collaborative SDK includes:
[0025] The function requirement information corresponding to each business line is analyzed and summarized, and the unified business collaboration interface is determined according to the function requirement information of each business line, so that each business line calls the front-end and back-end interaction interface according to the business collaboration interface to implement each business line function logic.
[0026] In an implementation manner, the process of creating the collaborative SDK includes:
[0027] The public resource interface is opened in the collaborative SDK to enable each business line to call the public resource through the public resource interface, and a collaborative base class of abstract class functions is created in the collaborative SDK to enable each business line to inherit the collaborative base class to obtain the abstract class functions and implement business line function logic in the abstract class functions according to the business collaboration interface.
[0028] In an implementation manner,
[0029] The public resource interface includes one or more of a data processing public interface, a log recording public interface, and an error processing public interface.
[0030] In an implementation manner,
[0031] The algorithm research and development code corresponding to each business line function logic is written according to the business collaboration interface of the collaborative SDK, including: for the business line function logic, a collaborative subclass corresponding to the function logic is created, and the abstract class functions of the collaborative base class are rewritten in the collaborative subclass according to the business collaboration interface to obtain the algorithm research and development code corresponding to the business line function logic.
[0032] In an implementation manner,
[0033] The method further includes: determining business line function logic change information or modification information, and changing or modifying the collaborative subclass according to the change information or modification information.
[0034] In an implementation manner,
[0035] The method further includes: reading the collaborative subclass from the collaborative SDK, and calling the abstract class functions of the collaborative subclass to refer to the business line function logic implemented by the algorithm research and development code.
[0036] According to an aspect of the present application, a storage medium is provided, and the storage medium stores a computer program, wherein the computer program is configured to execute the above-mentioned collaborative research and development method when running.
[0037] According to an aspect of the present application, an electronic device is provided, including a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the above-mentioned collaborative research and development method.
[0038] By means of the above technical solution, the present application provides a collaborative R&D platform, method, medium and equipment, which defines and creates a collaborative SDK, writes the algorithm R&D code corresponding to the functional logic of each business line according to the business collaboration interface of the collaborative SDK, and integrates the algorithm R&D code into the architecture R&D code repository as the content of the collaborative SDK. The collaborative SDK can be understood as an intermediary between framework R&D and algorithm R&D, which allows the code of each business line of algorithm R&D to be integrated into the architecture of framework R&D. The goal of the collaborative SDK is to enable each business line of algorithm R&D to independently develop business logic without having to directly access the underlying architecture code of the system, and at the same time, to provide a unified way for framework R&D to publish and call functions externally. It can be seen that the present application uses the collaborative SDK to enable multiple business lines to independently develop business on the same platform. At the same time, architecture R&D can also easily call these algorithm codes encapsulated by the SDK to quickly implement various business functions and improve the efficiency of the entire R&D process.
[0039] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0041] Figure 1 A schematic diagram showing the relationship between AO and FO in an embodiment of the present application is shown;
[0042] Figure 2 A schematic diagram of functional requirement information corresponding to the business line in an embodiment of the present application is shown;
[0043] Figure 3 An example diagram of an implementation of AO calling FO provided in an embodiment of the present application is shown;
[0044] Figure 4 A flow chart of a collaborative R&D method provided in an embodiment of the present application is shown. DETAILED DESCRIPTION
[0045] In order for those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should fall within the scope of protection of the present application. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.
[0046] The embodiments of the present application aim to provide a scheme for the cooperation of an architecture research and development (AO) system and an algorithm research and development (FO) system, thereby reducing the communication cost between different research and development systems, improving the project development efficiency, and ensuring the project quality. The embodiments of the present application are particularly suitable for the scene that a software project contains multiple business lines and the business function logics are different.
[0047] The terms are explained as follows.
[0048] AO (Architect owner): architecture research and development, responsible for system architecture design and research and development, and maintaining a code repository for carrying out the functions of external services.
[0049] FO (Feature owner): algorithm research and development, responsible for business algorithm research and development, and maintaining another code repository for realizing the business function logics of each business line (responsible for each business team).
[0050] SDK (Software Development Kit): software development kit.
[0051] Referring to Figure 1 , the relationship between AO and FO is shown. Among them, the AO code repository is mainly responsible for the architecture design of the entire software project, and the FO code repository is responsible for the separate business algorithm research and development of multiple business lines. The two are connected and interacted through a collaborative SDK, so that each business line can realize the functions on a unified platform. At the same time, the AO code repository provides external service interfaces, which is convenient for the expansion and rapid iteration of different business lines.
[0052] The embodiment of the application provides a collaborative R&D platform, which comprises an architecture R&D system and an algorithm R&D system, wherein the architecture R&D system maintains an architecture R&D code repository; the algorithm R&D system maintains an algorithm R&D code repository, wherein each business line function logic corresponds to a set of algorithm R&D codes; wherein the architecture R&D system further defines and creates a collaborative SDK, the collaborative SDK defines a unified business collaboration interface for each business line, and the algorithm R&D system further writes the algorithm R&D codes corresponding to each business line function logic according to the business collaboration interface of the collaborative SDK, and integrates the algorithm R&D codes into the architecture R&D code repository as the content of the collaborative SDK.
[0053] The collaborative SDK can be understood as an SDK injected with FO codes, which is defined and created by the AO, and the collaborative SDK is embedded into the entire code running environment, so that the AO can call the FO codes injected into the collaborative SDK to quickly realize the business function logic of each business line.
[0054] In the embodiment of the application, the collaborative SDK can be understood as an intermediary between the AO and the FO, which allows the codes of each business line of the FO to be integrated into the architecture of the AO. The goal of the collaborative SDK is to enable each business line of the FO to develop business logic independently without directly contacting the system bottom layer architecture code, and to provide a unified way for the AO to publish and call functions externally.
[0055] The following describes the embodiment of the application based on the process of the collaborative SDK (which can be referred to as SDK) (including defining the SDK, creating the SDK, FO code development, integration into the SDK, and SDK updating).
[0056] 1. SDK definition
[0057] Firstly, the function requirements and interface definitions of the SDK need to be determined. In the embodiment of the application, the SDK needs to provide a set of unified interface definitions, and each FO team (business line) can implement its own business algorithm based on these interface definitions. For example, the obstacle detection team may need a detectObstacle() method, the road sign recognition team may need a recognizeSign() method, and so on.
[0058] In one implementation mode, the function requirement information corresponding to each business line needs to be analyzed and summarized; according to the function requirement information of each business line, a unified business collaboration interface is determined, so that each business line calls the front-end and back-end interaction interfaces according to the business collaboration interface to realize the function logic of each business line.
[0059] For example, the functional requirement is determined by FO, and one AO can correspond to multiple FOs, such as the target front team wants to view the values of the same indicator in different evaluation tasks and compare these values. Different evaluation data sets and different models will be an evaluation task, but these tasks all contain the same evaluation indicators, such as: “[SMALL_CIPV]recall@score>=0” This indicator means: the recall score of Closest In-Path Vehicle (the target vehicle closest to the current lane in the automatic driving algorithm) in the small data set is greater than 0.5. For details, refer to Figure 2 A functional requirement information diagram corresponding to a business line is shown.
[0060] The unified interface definition means that multiple FOs need to follow the front-end and back-end interaction interface defined by the AO to realize the running of the code function, such as FO triggering the above board code needs to execute the method obstacle_detect.run(), and the run() method is the unified interface defined by the AO.
[0061] 2. Create SDK
[0062] According to the interface definition, create and implement the SDK. The SDK should include all the public resources (services) required by the business line (all business teams), such as data processing, log recording, error handling, and other general modules. In the SDK, the AO defines the public interfaces for data processing, log recording, error handling, etc., and exposes the interfaces for FO to call. At the same time, this SDK contains the entire process of the task flow, and calling the run() method (abstract class function) will execute the data record processing, logic execution, and log recording of the current FO team's task in the SDK.
[0063] In one implementation, the public resource interface is opened in the collaborative SDK to enable each business line to call public resources through the public resource interface, and the collaborative base class of the abstract class function is created in the collaborative SDK to enable each business line to inherit the collaborative base class to obtain the abstract class function, and implement the business line function logic in the abstract class function according to the business collaboration interface.
[0064] Among them, the public resource interface includes but is not limited to data processing public interface, log recording public interface, error handling public interface, etc.
[0065] 3. FO business line development
[0066] After the SDK is created, the FO teams start to develop codes within the SDK framework. Among them, the business logic codes that meet the requirements are written according to the interface definitions provided by the SDK. For example, the obstacle detection team uses the detectObstacle() method to implement the function of detecting obstacles.
[0067] In an implementation manner, for the business line function logic, a collaborative subclass corresponding to the function logic is created, and the abstract class functions of the collaborative superclass are rewritten in the collaborative subclass according to the business collaboration interface, to obtain the algorithm research and development code corresponding to the business line function logic.
[0068] For example, the base class of the SDK is BaseDetect, and the run() function of BaseDetect is an abstract class function, which has no running logic. All subclasses that inherit the base class need to implement the run() function, and implement their own business logic in the run function. Different FO teams implement their own subclass based on BaseDetect, and then implement their own run() function. For example, the obstacle detection business line (team) and the target detection business line (team) need to implement their own subclass, and their specific logic is different, that is, the logic in the run() function is different.
[0069] 4. Integration into the SDK
[0070] After each FO business line completes its own code writing, it is submitted to the SDK. Among them, it is necessary to ensure that all codes meet the unified specifications and pass the tests before integration. As described in the previous example, the AO formulates the interface definition of the collaborative SDK, which stipulates that the run() method must be called in the subclass running. If this interface definition is not followed, the specific logic of the subclass cannot be run.
[0071] 5. SDK update iteration
[0072] Finally, when the FO team needs to add new functions or improve existing functions, the same process can be used to modify and update the SDK. Only the interfaces provided to the outside need to be kept consistent. In an implementation manner, the business line function logic change information or modification information is determined, and the collaborative subclass is changed or modified according to the change information or modification information.
[0073] Through the above steps of creating and integrating the collaborative SDK, the goal of multiple business teams (multiple FO business lines) independently developing business on the same platform can be achieved through the collaborative SDK. At the same time, the AO can also conveniently call these interfaces encapsulated by the SDK to quickly implement various business functions.
[0074] In an implementation, the process of AO calling the business line function logic can be: reading the collaborative subclass from the collaborative SDK, and calling the abstract class function of the collaborative subclass to reference the business line function logic implemented by the algorithm research and development code.
[0075] The implementation process of the embodiments of the present application is described below with a specific example in the field of unmanned driving.
[0076] In this specific example, it is assumed that there are two main research and development systems: an Architect Owner (AO) system and a Feature Owner (FO) system.
[0077] The AO system is responsible for designing and developing the system architecture of the entire unmanned vehicle, creating a code repository to host all system-related codes, and publishing interfaces according to the requirements of each business line.
[0078] The FO system is divided into multiple subsystems (multiple business lines), each of which focuses on a specific function or feature of the unmanned vehicle system.
[0079] In order to integrate various algorithms of the FO system into the entire unmanned system, a base class named BaseDetect is designed and implemented, which is located in the collaborative SDK. BaseDetect contains some general abstract methods such as run(), which is used to start the detection algorithm.
[0080] Each FO subsystem inherits BaseDetect according to its business requirements and implements the corresponding abstract methods, for example:
[0081] The automatic navigation team may create a class named NavigationDetect, which overrides the run() method of BaseDetect to implement the vehicle navigation function;
[0082] The obstacle detection team may create a class named ObstacleDetect, which also overrides the run() method of BaseDetect to implement the obstacle detection function.
[0083] When the AO system needs to use the function provided by a FO subsystem, it only needs to reference the corresponding subclass from the collaborative SDK and call its run() method. For example, if the obstacle detection function is needed, the implementation method like Figure 3 can be used.
[0084] In this way, it is ensured that each FO business line can develop business without touching the AO code, and at the same time, the AO system can conveniently call the functions provided by the FO system, greatly improving the development efficiency and reducing the communication cost.
[0085] Corresponding to the above-mentioned collaborative research and development platform, the embodiment of the present application also provides a collaborative research and development method, which comprises the following steps:
[0086] 11: maintaining an architecture research and development code repository; and,
[0087] 12: maintaining an algorithm research and development code repository, wherein each business line function logic corresponds to a set of algorithm research and development codes;
[0088] Wherein, a collaborative SDK is defined and created, the collaborative SDK defines a unified business collaboration interface for each business line, and the algorithm research and development code corresponding to each business line function logic is written according to the business collaboration interface of the collaborative SDK, and the algorithm research and development code is integrated into the architecture research and development code repository as the content of the collaborative SDK.
[0089] Referring to Figure 4 , which is a collaborative research and development method flowchart from the perspective of SDK.
[0090] S401: defining a collaborative SDK.
[0091] Specifically, the function requirement information corresponding to each business line is analyzed and summarized; according to the function requirement information of each business line, a unified business collaboration interface is determined, so that each business line calls the front-end and back-end interaction interface according to the business collaboration interface, to realize the function logic of each business line.
[0092] S402: creating a collaborative SDK.
[0093] Specifically, a public resource interface is opened in the collaborative SDK, so that each business line can call public resources through the public resource interface, and a collaborative base class of abstract class functions is created in the collaborative SDK, so that each business line inherits the collaborative base class to obtain the abstract class functions, and realizes the business line function logic in the abstract class functions according to the business collaboration interface.
[0094] S403: FO code development.
[0095] For the business line function logic, a collaborative subclass corresponding to the function logic is created, and the abstract class functions of the collaborative base class are rewritten in the collaborative subclass according to the business collaboration interface, to obtain the algorithm research and development code corresponding to the business line function logic.
[0096] S404: integration into the collaborative SDK.
[0097] After each FO business line completes its own code writing, it is submitted to the SDK. Among them, it is necessary to ensure that all codes conform to the unified specification and have passed the test before integration.
[0098] If the FO team needs to add new functions or improve existing functions, the same process can be followed to modify and update the collaborative SDK. Only ensure that the interface provided to the outside remains consistent. In an implementation, the business line function logic change information or modification information is determined, and the collaborative subclass is changed or modified according to the change information or modification information.
[0099] S405: The AO calls the FO code.
[0100] In an implementation, the process of the AO calling the business line function logic can be: reading the collaborative subclass from the collaborative SDK, and calling the abstract class function of the collaborative subclass to reference the business line function logic implemented by the algorithm research and development code.
[0101] Embodiments of the present application also provide a storage medium having a computer program stored therein, wherein the computer program is configured to execute the steps in any of the method embodiments described above when running.
[0102] Optionally, in the present embodiment, the storage medium described above can be configured to store a computer program for executing the following steps:
[0103] maintaining an architecture research and development code repository; and
[0104] maintaining an algorithm research and development code repository, wherein each business line function logic corresponds to a set of algorithm research and development code;
[0105] In the present embodiment, a collaborative SDK is defined and created, the collaborative SDK defines unified business collaboration interfaces for each business line, and the algorithm research and development code corresponding to each business line function logic is written according to the business collaboration interfaces of the collaborative SDK, and the algorithm research and development code is integrated into the architecture research and development code repository as the content of the collaborative SDK.
[0106] Optionally, in the present embodiment, the storage medium described above can include but is not limited to: a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.
[0107] Embodiments of the present application also provide an electronic device comprising a memory having a computer program stored therein and a processor configured to run the computer program to execute the steps in any of the method embodiments described above.
[0108] Optionally, the electronic device described above can further comprise a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
[0109] Optionally, in the embodiment, the processor can be configured to execute the following steps by a computer program:
[0110] maintain an architecture development code repository; and
[0111] maintain an algorithm development code repository, wherein each business line function logic corresponds to a set of algorithm development codes;
[0112] wherein a collaborative SDK is defined and created, the collaborative SDK defines a unified business collaboration interface for each business line, and algorithm development codes corresponding to each business line function logic are written according to the business collaboration interface of the collaborative SDK, and the algorithm development codes are integrated into the architecture development code repository as contents of the collaborative SDK.
[0113] Optionally, specific examples in the embodiment can refer to examples described in the above embodiments and optional implementation manners, which will not be repeated here.
[0114] The serial numbers of the embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.
[0115] In the above embodiments of the present application, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.
[0116] In the several embodiments of the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the above-described device embodiments are only schematic. The division of the units is only a logical function division. There can be another division manner for actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, units or modules, and can be electrical or other forms.
[0117] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on multiple network units. According to actual needs, some or all of the units can be selected to achieve the purpose of the embodiment.
[0118] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware, or in the form of software functional unit.
[0119] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or say the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.
[0120] The above is only the preferred embodiment of the present application, and it should be pointed out that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.
Claims
1. A collaborative research and development platform, characterized by, The development platform comprises an architecture development system and an algorithm development system, wherein, The architecture development system maintains an architecture development code repository; The algorithm development system maintains an algorithm development code repository, wherein each business line function logic corresponds to a set of algorithm development codes; The architecture development system is further configured to define and create a collaborative SDK, the collaborative SDK defines a unified business collaboration interface for each business line, and the algorithm development system is further configured to write algorithm development codes corresponding to each business line function logic according to the business collaboration interface of the collaborative SDK, and integrate the algorithm development codes as the content of the collaborative SDK into the architecture development code repository.
2. The platform of claim 1, wherein The architecture development system is specifically configured to analyze and aggregate function requirement information corresponding to each business line, and determine a unified business collaboration interface according to the function requirement information of each business line, so that each business line calls front-end and back-end interaction interfaces according to the business collaboration interface to implement business line function logic.
3. The platform of claim 2, wherein The architecture development system is specifically configured to open a public resource interface in the collaborative SDK to enable each business line to call a public resource through the public resource interface, and create a collaborative base class of abstract class functions in the collaborative SDK to enable each business line to inherit the collaborative base class to obtain the abstract class functions, and implement business line function logic in the abstract class functions according to the business collaboration interface.
4. The platform of claim 3, wherein The public resource interface comprises one or more of a data processing public interface, a log recording public interface, and an error processing public interface.
5. The platform of claim 3, wherein The algorithm development system is specifically configured to create a collaborative subclass corresponding to a function logic for a business line function logic, and rewrite the abstract class functions of the collaborative base class in the collaborative subclass according to the business collaboration interface to obtain algorithm development codes corresponding to the business line function logic.
6. The platform of claim 5, wherein The algorithm development system is further configured to determine business line function logic change information or modification information, and change or modify the collaborative subclass according to the change information or modification information.
7. The platform of claim 5, wherein The architecture development system is further configured to read the collaborative subclass from the collaborative SDK, and call the abstract class functions of the collaborative subclass to reference the business line function logic implemented by the algorithm development codes.
8. A collaborative development method characterized by, The method is used for the platform of any one of claims 1-7, and is used for performing collaborative control on the collaborative development platform.
9. A storage medium, characterized by The storage medium stores a computer program, wherein the computer program is configured to execute the method of claim 8 when running.
10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the computer program to execute the method of claim 8.