Design method, device and development platform of engineering template application

Abstract

The application provides a design method and device of an engineering template and a development platform of a core system. The design method comprises: performing architecture design layering according to a technical dimension to obtain a framework layer, a parent field layer, a business function field layer and a deployment layer, the framework layer is used to provide common services, the parent field layer comprises a plurality of parent modules, the business function field layer comprises a plurality of sub-modules, one sub-module corresponds to one parent module, the parent module is used to import a dependent package so that the corresponding sub-module inherits and uses, the dependent package at least comprises a version dependent package, the sub-module is used to provide atomic services or combined services, and the deployment layer is used to combine different services to generate an application; and the technical dimension is a dimension corresponding to an implementation logic of the services. The framework layer, the parent field layer, the business function field layer and the deployment layer are combined to generate an application engineering template, and the problem of code redundancy in the design and development of the application of the business core system in the prior art is solved.

Description

Technical Field

[0001] This invention relates to the field of application development technology, and more specifically, to a design method, design device, computer-readable storage medium, and core system development platform for application engineering templates. Background Technology

[0002] In the construction of the new generation of personal business core systems, the new core technology platform serves as the technical foundation of the core system, providing underlying functional support and related technical standards for application design and development. With the construction and promotion of the core business technology platform, more and more upper-layer application systems, such as corporate banking, personal banking, credit card banking, and accounting systems, are developing applications based on this platform. How to more effectively design and develop applications based on the framework and services provided by the technology platform is a challenge facing application developers.

[0003] After connecting to the core technology platform, various upper-layer application systems have encountered the following problems:

[0004] 1) The common capabilities of the core technology platform framework are repeatedly encapsulated and implemented, resulting in redundant code.

[0005] 2) The version dependency management of the various components provided by the technology platform is chaotic, resulting in conflicts due to different dependency versions.

[0006] 3) After the application system adopts a microservice architecture, the boundaries between services are not clearly defined, and common capabilities cannot be reused.

[0007] 4) Development and deployment were not separated, resulting in chaotic development and deployment management. Summary of the Invention

[0008] The main objective of this application is to provide a design method, design device, computer-readable storage medium, and core system development platform for application engineering templates, so as to at least solve the problem of code redundancy in the design and development of application core systems in the prior art.

[0009] To achieve the above objectives, according to one aspect of this application, a method for designing an application engineering template is provided, comprising: layering the architecture according to a technical dimension to obtain a framework layer, a parent domain layer, a business function domain layer, and a deployment layer; wherein the framework layer is used to provide common services, the parent domain layer includes multiple parent modules, the business function domain layer includes multiple sub-modules, one sub-module corresponds to one parent module, the parent module is used to import dependency packages so that the corresponding sub-modules inherit and use them, the dependency packages include at least version dependency packages, the sub-modules are used to provide atomic services or composite services, the deployment layer is used to combine different services to generate an application, and the technical dimension is the dimension corresponding to the implementation logic of the service; and combining the framework layer, the parent domain layer, the business function domain layer, and the deployment layer to generate an application engineering template.

[0010] Optionally, the architecture is layered according to the technical dimension to obtain a framework layer, including: a project-common module, a project-exception module, and a project-dict module designed according to the functions corresponding to the public services. The project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system. The project-exception module is used to provide system-level exception handling mechanisms. The project-dict module is used to provide a data dictionary. The project-common module, the project-exception module, and the project-dict module are combined to generate the framework layer.

[0011] Optionally, the architecture is layered according to technical dimensions to obtain a business function domain layer, including: an interface management domain, a functional module management domain, and a business domain management domain, wherein the interface management domain is used to provide application interfaces, each corresponding one-to-one with a sub-module; the functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions; and the business domain management domain is used to provide online and batch functions. The interface management domain, the functional module management domain, and the business domain management domain are combined to generate the business function domain layer.

[0012] Optionally, an architecture design is performed based on the aforementioned technical dimensions to obtain a business domain management domain, including: designing an application-level online module and an application-level batch module based on the online function and the batch function. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a composite service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The composite service sublayer and the atomic service sublayer provide corresponding services to associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the composite service of the composite service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the composite service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. The application-level online module and the application-level batch module are combined to generate the business domain management domain.

[0013] Optionally, the architecture is layered according to the technical dimension to obtain a deployment layer, including: designing an online packaging module and a batch packaging module based on the application combination packaging function corresponding to the online function and the batch function, wherein the online packaging module is used to deploy components for online transactions, and the batch packaging module is used to deploy components for batch transactions; and combining the online packaging module and the batch packaging module to generate the deployment layer.

[0014] Optionally, after designing the online packaging module and the batch packaging module according to the application combination packaging function corresponding to the online function and the batch function, the method further includes: adding an application development online packaging tutorial project to the online packaging module, wherein the application development online packaging tutorial project is used to provide application developers with application project templates for learning and use.

[0015] Optionally, after designing the application-level online module and the application-level batch module based on the online function and the batch function, the method further includes: deploying the combined service sublayer and the atomic service sublayer separately or in combination. The separate deployment refers to a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using different channels, and the separate deployment refers to a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using the same channel.

[0016] According to another aspect of this application, an application engineering template design apparatus is provided, comprising: a processing unit, configured to perform architectural design layering based on technical dimensions to obtain a framework layer, a parent domain layer, a business function domain layer, and a deployment layer, wherein the framework layer is used to provide common services, the parent domain layer includes multiple parent modules, the business function domain layer includes multiple sub-modules, one sub-module corresponds to one parent module, the parent module is used to import dependency packages so that the corresponding sub-modules inherit and use them, the dependency packages include at least version dependency packages, the sub-modules are used to provide atomic services or composite services, and the deployment layer is used to combine different services to generate an application, wherein the technical dimension is the dimension corresponding to the implementation logic of the service; and a generation unit, configured to combine the framework layer, the parent domain layer, the business function domain layer, and the deployment layer to generate an application engineering template.

[0017] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform any of the described design methods.

[0018] According to another aspect of this application, a development platform for a core system is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include methods for performing any of the design methods described herein.

[0019] Applying the technical solution of this application, the design method of the above-mentioned application engineering template firstly involves layering the architecture according to technical dimensions to obtain a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules, and the business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate an application. The technical dimensions are the dimensions corresponding to the implementation logic of the services. Then, the framework layer, the parent domain layer, the business function domain layer, and the deployment layer are combined to generate the application engineering template. This design methodology utilizes an architecture framework layer to provide common services, encapsulating and extending the common capabilities of the underlying framework, thus reducing code redundancy. Furthermore, it employs a parent domain layer and a business function domain layer. By importing dependency packages into the parent module of the parent domain layer, the corresponding submodules in the business function domain layer can inherit and use these packages without importing dependency packages themselves. For example, if the dependency package includes version dependencies, the submodule's code does not need to include version numbers, further reducing code redundancy. The deployment layer combines the common services and the services provided by the submodules to generate the application, completing the application design. This application engineering template is used for the design and development of the core business system. The framework layer and the parent domain layer form a common functional component management domain, enabling the management of platform component versions in the core business system and providing clear functional divisions and unified common capabilities, thereby significantly reducing code redundancy and solving the problem of code redundancy in the design and development of core business systems in existing technologies. Attached Figure Description

[0020] Figure 1 A hardware structure block diagram of a mobile terminal for implementing an application engineering template design method is shown in an embodiment of this application.

[0021] Figure 2 A flowchart illustrating a design method for an application engineering template according to an embodiment of this application is shown.

[0022] Figure 3 A partial architecture diagram of an application engineering template provided in an embodiment of this application is shown;

[0023] Figure 4 This illustration shows another portion of the architecture diagram of an application engineering template provided in an embodiment of this application;

[0024] Figure 5A structural block diagram illustrating the component relationships of an online transaction in development mode according to an embodiment of this application is shown.

[0025] Figure 6 A structural block diagram illustrating the component relationships of a typical batch transaction in development mode, according to an embodiment of this application, is shown.

[0026] Figure 7 A structural block diagram of a separate deployment of an online transaction runtime for an engineering template, according to an embodiment of this application, is shown.

[0027] Figure 8 A structural block diagram of a merged deployment of an online transaction runtime for an engineering template, according to an embodiment of this application, is shown.

[0028] Figure 9 A structural block diagram of a design apparatus for an application engineering template provided according to an embodiment of this application is shown. Detailed Implementation

[0029] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0030] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this application described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] For ease of description, the following explains some of the nouns or terms used in the embodiments of this application:

[0033] DDD: Domain Driven Design.

[0034] PBB: Physical Building Block, a component that performs a simple set of business logic.

[0035] PBC: Physical Basic Component. A component is an encapsulation of business rules within an aggregate, enabling hierarchical business processing by calling the component.

[0036] PBS: Physical Basic Service, or atomic service, combines and encapsulates aggregations from multiple microservice components to achieve relatively independent, fully functional, and reusable basic services.

[0037] PCS: Physical Composition Service. It is composed of one or more atomic services. Internally, it enables orchestration of capabilities across data objects, and externally, it exposes the capabilities of this component to front-end applications and other back-end components.

[0038] Online trading: The system provides trading services directly to external parties, meaning that trading is real-time;

[0039] Batch trading: The relevant parameters and system status of the transaction have been locked. The system needs to perform a certain type of operation, namely, to process a large amount of transaction data using the same rules.

[0040] As described in the background section, code redundancy occurs in the design and development of core business systems in the prior art. To solve this technical problem, embodiments of this application provide a design method, design device, computer-readable storage medium, and core system development platform for application engineering templates.

[0041] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention.

[0042] The methods and embodiments provided in this application can be executed on a mobile terminal, computer terminal, or similar computing device. Taking running on a mobile terminal as an example, Figure 1 This is a hardware structure block diagram of a mobile terminal using an application engineering template design method according to an embodiment of the present invention. For example... Figure 1 As shown, a mobile terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The mobile terminal may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1The structure shown is for illustrative purposes only and does not limit the structure of the mobile terminal described above. For example, the mobile terminal may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0043] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the device information display method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof. The transmission device 106 is used to receive or send data via a network. Specific examples of the aforementioned networks may include wireless networks provided by the mobile terminal's communication provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0044] This embodiment provides a design method for an application engineering template that runs on a mobile terminal, computer terminal, or similar computing device. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0045] Figure 2 This is a flowchart illustrating the design method of an application engineering template according to an embodiment of this application. For example... Figure 2 As shown, the method includes the following steps:

[0046] Step S201: The architecture is layered according to the technical dimensions to obtain the framework layer, parent domain layer, business function domain layer and deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0047] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0048] Step S202: Combine the above framework layer, the above parent domain layer, the above business function domain layer and the above deployment layer to generate an application project template.

[0049] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0050] In the above application engineering template design method, firstly, the architecture is layered according to the technical dimension, resulting in a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer provides common services, the parent domain layer includes multiple parent modules, and the business function domain layer includes multiple sub-modules, with one sub-module corresponding to one parent module. The parent module imports dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules provide atomic services or composite services. The deployment layer combines different services to generate applications. The technical dimension refers to the dimension corresponding to the implementation logic of the services. Then, the framework layer, parent domain layer, business function domain layer, and deployment layer are combined to generate the application engineering template. This design methodology utilizes an architecture framework layer to provide common services, encapsulating and extending the common capabilities of the underlying framework, thus reducing code redundancy. Furthermore, it employs a parent domain layer and a business function domain layer. By importing dependency packages into the parent module of the parent domain layer, the corresponding submodules in the business function domain layer can inherit and use these packages without importing dependency packages themselves. For example, if the dependency package includes version dependencies, the submodule's code does not need to include version numbers, further reducing code redundancy. The deployment layer combines the common services and the services provided by the submodules to generate the application, completing the application design. This application engineering template is used for the design and development of the core business system. The framework layer and the parent domain layer form a common functional component management domain, enabling the management of platform component versions in the core business system and providing clear functional divisions and unified common capabilities, thereby significantly reducing code redundancy and solving the problem of code redundancy in the design and development of core business systems in existing technologies.

[0051] In order to integrate public capabilities, in one optional implementation, step S201 above includes:

[0052] Step S2011: Based on the functions corresponding to the above public services, the project-common module, project-exception module, and project-dict module are designed to obtain the following modules: the project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system; the project-exception module is used to provide system-level exception handling mechanisms; and the project-dict module is used to provide a data dictionary.

[0053] Step S2012: Combine the above-mentioned project-common module, project-exception module and project-dict module to generate the above-mentioned framework layer.

[0054] Specifically, such as Figure 3 As shown, the above-mentioned project-common module (system-level common module) provides system-level common capabilities, including common tools and common processing capabilities provided by the core technology platform. The above-mentioned project-exception module provides a system-level exception handling mechanism (exception handling capabilities provided by the core technology platform). The above-mentioned project-dict module provides an enterprise-level data dictionary, which encapsulates and extends the common capabilities of the underlying framework, reducing code redundancy.

[0055] In order to provide multiple functional services, in an optional implementation, step S201 above further includes:

[0056] Step S2013: Based on the above technical dimensions, an architecture design is carried out to obtain an interface management domain, a functional module management domain, and a business domain management domain. The interface management domain is used to provide application interfaces, and the application interfaces correspond one-to-one with the above sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain is used to provide services such as online functions and batch functions.

[0057] Step S2014: Combine the above-mentioned interface management domain, the above-mentioned functional module management domain, and the above-mentioned business domain management domain to generate the above-mentioned business function domain layer.

[0058] Specifically, such as Figure 3 and Figure 4As shown, the aforementioned business function domain layer includes the interface management domain `project-api`, the functional module management domain `project-component`, and the business domain management domain. The interface management domain `project-api` provides application-level interfaces that can be used for transaction development in different scenarios. All module interfaces are managed uniformly under the interface project, for example, including the `producer-api` and `consumer-api` interfaces. The parent module of the `project-api` project is the `api-parent` (the common parent of the API components) module under `project-parent`. The functional module management domain `project-component` includes the `project-outbound` module, the `project-sequence` module, the `project-message` module, and the `project-timer` module. `project-outbound` provides application-level outbound call-related functions, and its parent module is the `outbound-parent` (the common parent of the outbound components) module under `project-parent`. `project-sequence` provides application-level sequence number-related functions, and its parent module is the `sequence-parent` (the common parent of the sequence components) module under `project-parent`. `project-message` provides application-level message-related functions, and its parent module is the `message-parent` (the common parent of the message components) module under `project-parent`. Project-Timer provides application-level scheduled task development functionality. Its parent module is the Timer-Parent module (the common parent of the Timer component) under Project-Parent. The aforementioned business domain management domain includes the application-level online module Project-Online and the application-level batch module Project-Batch. Thus, it calls the sub-modules of the aforementioned functional module management domain Project-Components through the interfaces managed by the Interface Management Domain Project-API to provide services. The service modes are divided into the online transaction mode provided by the application-level online module Project-Online and the batch transaction mode provided by the application-level batch module Project-Batch.

[0059] To achieve online and batch processing capabilities, in one optional implementation, step S201 further includes:

[0060] Step S2015: Based on the above-mentioned online function and batch function, an application-level online module and an application-level batch module are designed. The application-level online module is used to provide the above-mentioned online function, and the application-level batch module is used to provide the above-mentioned batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer are used to provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer is used to combine the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer is used to generate instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer is used to interact with the associated systems.

[0061] Step S2016: Combine the above-mentioned application-level online module and the above-mentioned application-level batch module to generate the above-mentioned business domain management domain.

[0062] Specifically, such as Figure 4 As shown, project-online is the application-level online module (the online function provided by the core technology platform). According to the five-level modeling methodology, it is further divided into the composite service sub-layer (project-pcs), atomic service sub-layer (project-pbs), aggregation function sub-layer (project-pbc), instruction function sub-layer (project-pbb), and data access sub-layer (project-dao). The business function layer is further divided from a business perspective, which facilitates the combination and expansion of services and improves the system's business support capabilities. The parent modules of each business sub-layer correspond to the pcs-parent (pcs component common parent) module, pbs-parent (pbs component common parent) module, pbc-parent (pbc component common parent) module, pbb-parent (pbb component common parent) module, and dao-parent (dao component common parent) module under project-parent, respectively. project-batch is the application-level batch module (batch function provided by the core technology platform). It is responsible for providing application-level batch functions, including the corresponding pjs development (modulename-batch-pjs) and extension development (modulename-batch-extend). The parent module of project-batch is the batch-parent (batch component common parent) module under project-parent, which provides the online transaction mode for transaction business and the batch transaction mode through the application-level batch module project-batch.

[0063] To achieve lightweight deployment of the system engineering, in one optional implementation, step S201 further includes:

[0064] Step S2017: Based on the application combination packaging function corresponding to the above online function and the above batch function, design the online packaging module and the batch packaging module to obtain the online packaging module for deploying the components for online transactions, and the batch packaging module for deploying the components for batch transactions.

[0065] Step S2018: Combine the online packaging module and the batch packaging module to generate the deployment layer.

[0066] Specifically, such as Figure 4 As shown, the above deployment layer, project-boot, combines different services to generate the final deployed application. The project-boot module imports the Spring-Boot plugin, providing application composition and packaging functionality. project-boot contains two sub-modules: the online packaging module online-boot and the batch packaging module batch-boot. The component relationships of online transactions in development mode are as follows: Figure 5 As shown, the sub-modules corresponding to the composite service sub-layer (project-pcs), atomic service sub-layer (project-pbs), aggregation function sub-layer (project-pbc), instruction function sub-layer (project-pbb), and data access sub-layer (project-dao), namely the sub-modules xxx-pcs, xxx-pbs, xxx-pbc, xxx-pbb, and xxx-dao, all inherit from their respective parent modules. The parent modules inherit from the system-level parent module project-parent of the parent domain layer. The system-level parent module project-parent depends on the framework layer's project-common, project-exception, and project-dict modules. All of these sub-modules are called through their corresponding interfaces, such as xxx-pcs-api, xxx-pbs-api, xxx-pbc-api, xxx-pbb-api, and xxx-dao-api, and inherit from the version of the automatic design software ads-project. The component relationships for batch transactions in development mode are as follows: Figure 6 As shown, compared to the online transaction component, it lacks the xxx-pcs and xxx-pbs submodules. This means there's no need to call the xxx-pcs and xxx-pbs submodules to provide atomic and composite services; transaction data can be processed in batches according to unified rules. The online transaction runtime state of the project template is as follows: Figure 7 and Figure 8As shown, the development and deployment states are separated, and different services are combined in the deployment layer to generate the final deployment application, thus achieving lightweight deployment of the system engineering.

[0067] For ease of development, in an optional implementation, after step S2017, the method further includes:

[0068] Step S301: Add an application development online packaging tutorial project to the above-mentioned online packaging module. The application development online packaging tutorial project is used to provide application developers with an opportunity to learn how to use application project templates.

[0069] Specifically, such as Figure 4 As shown, an online packaging tutorial project based on this application project template has been added under the online packaging module, allowing application developers to better learn and use the aforementioned application project template. The ads-practice-online-resource module under the tutorial project provides application transaction development resource management, including Apollo factory configuration, database scripts, and transaction baseline data. The ads-practice-online-server module provides application packaging configuration management, such as online transaction merge deployment configuration. ads-practice-online can be released as an independent project, ensuring that the resource project version is consistent with the server project version.

[0070] To improve deployment flexibility, in an optional implementation, after step S2015, the method further includes:

[0071] Step S401: Deploy the combined service sublayer and the atomic service sublayer separately or in combination. The separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system through different channels, and the separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system through the same channel.

[0072] Specifically, both the PCS service and the PBS service are registered in the Apollo configuration center or the Nacos configuration center. Associated systems can then call the registered PCS service or PBS service through the online gateway. The aforementioned combined service sublayer and the aforementioned atomic service sublayer interact with the aforementioned associated systems through different channels, representing a separate deployment. Figure 7 As shown, the aforementioned combined service sublayer and the aforementioned atomic service sublayer interact with the aforementioned related systems through the same channel, which constitutes a merged deployment, as... Figure 8 As shown, those skilled in the art can choose the appropriate deployment method according to the actual situation, making the application quite flexible.

[0073] To enable those skilled in the art to better understand the technical solution of this application, the implementation process of the application engineering template design method of this application will be described in detail below with reference to specific embodiments.

[0074] This embodiment relates to a specific method for designing application engineering templates, including the following steps:

[0075] Step S1: Based on the functions corresponding to the above public services, design the project-common module, project-exception module, and project-dict module. The project-common module is used to provide system-level common processing capabilities, which are the common data processing capabilities of the current system. The project-exception module is used to provide system-level exception handling mechanisms. The project-dict module is used to provide a data dictionary. Combine the project-common module, project-exception module, and project-dict module to generate the above framework layer.

[0076] Step S2: Based on the above technical dimensions, design the architecture to obtain the interface management domain, functional module management domain, and business domain management domain. The interface management domain is used to provide application interfaces, which correspond one-to-one with the above sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain is used to provide online and batch functions. Combine the interface management domain, functional module management domain, and business domain management domain to generate the above business function domain layer.

[0077] Step S3: Based on the above-mentioned online and batch functions, design an application-level online module and an application-level batch module. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. Combine the application-level online module and the application-level batch module to generate the business domain management domain.

[0078] Step S4: Based on the application combination packaging function corresponding to the above online function and the above batch function, design the online packaging module and the batch packaging module. The online packaging module is used to deploy the components for online transactions, and the batch packaging module is used to deploy the components for batch transactions. Combine the online packaging module and the batch packaging module to generate the above deployment layer.

[0079] Step S5: Add an application development online packaging tutorial project to the above online packaging module. The application development online packaging tutorial project is used to provide application developers with an opportunity to learn how to use the application project template.

[0080] Step S6: Deploy the above-mentioned combined service sublayer and the above-mentioned atomic service sublayer separately or in combination. The above-mentioned separate deployment means that the above-mentioned combined service sublayer and the above-mentioned atomic service sublayer use different channels to interact with the above-mentioned associated system. The above-mentioned separate deployment means that the above-mentioned combined service sublayer and the above-mentioned atomic service sublayer use the same channel to interact with the above-mentioned associated system.

[0081] It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be executed in a different order than that shown here.

[0082] This application also provides a design apparatus for application engineering templates. It should be noted that this design apparatus for application engineering templates can be used to execute the Z method provided in this application. This apparatus is used to implement the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0083] The following describes the design device for application engineering templates provided in the embodiments of this application.

[0084] Figure 9 This is a schematic diagram of a design device for an application engineering template according to an embodiment of this application. For example... Figure 9 As shown, the device includes:

[0085] Processing unit 10 is used to perform architectural design layering based on technical dimensions to obtain a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0086] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0087] The generation unit 20 is used to combine the above-mentioned framework layer, the above-mentioned parent domain layer, the above-mentioned business function domain layer and the above-mentioned deployment layer to generate an application project template.

[0088] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0089] In the aforementioned application engineering template design device, the processing unit performs architectural design layering based on technical dimensions, resulting in a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer provides common services, the parent domain layer includes multiple parent modules, and the business function domain layer includes multiple sub-modules, with each sub-module corresponding to a parent module. The parent module imports dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules provide atomic services or composite services. The deployment layer combines different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services. The generation unit combines the framework layer, the parent domain layer, the business function domain layer, and the deployment layer to generate the application engineering template. This design device utilizes an architecture framework layer to provide common services, encapsulating and extending the common capabilities of the underlying framework, thus reducing code redundancy. Furthermore, through the architecture design of a parent domain layer and a business function domain layer, dependency packages are imported into the parent module of the parent domain layer, allowing corresponding submodules in the business function domain layer to inherit and use them. Submodules do not need to import dependency packages; for example, if the dependency package includes version dependencies, the submodule code does not need to include version numbers, further reducing code redundancy. The deployment layer combines the services provided by the common services and submodules to generate the application, completing the application design. This application engineering template is used for the design and development of the core business system. The framework layer and parent domain layer form a common functional component management domain, enabling the management of platform component versions in the core business system and providing clear functional divisions and unified common capabilities, thereby significantly reducing code redundancy and solving the problem of code redundancy in the design and development of core business systems in existing technologies.

[0090] To integrate common capabilities, in one optional implementation, the processing unit includes:

[0091] The first processing module is used to design the project-common module, project-exception module and project-dict module according to the functions corresponding to the above public services. The project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system. The project-exception module is used to provide system-level exception handling mechanism. The project-dict module is used to provide a data dictionary.

[0092] The second processing module is used to combine the above-mentioned project-common module, project-exception module and project-dict module to generate the above-mentioned framework layer.

[0093] Specifically, such as Figure 3 As shown, the above-mentioned project-common module (system-level common module) provides system-level common capabilities, including common tools and common processing capabilities provided by the core technology platform. The above-mentioned project-exception module provides a system-level exception handling mechanism (exception handling capabilities provided by the core technology platform). The above-mentioned project-dict module provides an enterprise-level data dictionary, which encapsulates and extends the common capabilities of the underlying framework, reducing code redundancy.

[0094] To provide a variety of functional services, in one optional implementation, the processing unit further includes:

[0095] The third processing module is used to design the architecture based on the above technical dimensions to obtain the interface management domain, the functional module management domain, and the business domain management domain. The interface management domain is used to provide application interfaces, which correspond one-to-one with the above sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timed functions. The business domain management domain is used to provide services such as online functions and batch functions.

[0096] The fourth processing module is used to combine the aforementioned interface management domain, the aforementioned functional module management domain, and the aforementioned business domain management domain to generate the aforementioned business function domain layer.

[0097] Specifically, such as Figure 3 and Figure 4As shown, the aforementioned business function domain layer includes the interface management domain `project-api`, the functional module management domain `project-component`, and the business domain management domain. The interface management domain `project-api` provides application-level interfaces that can be used for transaction development in different scenarios. All module interfaces are managed uniformly under the interface project, for example, including the `producer-api` and `consumer-api` interfaces. The parent module of the `project-api` project is the `api-parent` (the common parent of the API components) module under `project-parent`. The functional module management domain `project-component` includes the `project-outbound` module, the `project-sequence` module, the `project-message` module, and the `project-timer` module. `project-outbound` provides application-level outbound call-related functions, and its parent module is the `outbound-parent` (the common parent of the outbound components) module under `project-parent`. `project-sequence` provides application-level sequence number-related functions, and its parent module is the `sequence-parent` (the common parent of the sequence components) module under `project-parent`. `project-message` provides application-level message-related functions, and its parent module is the `message-parent` (the common parent of the message components) module under `project-parent`. Project-Timer provides application-level scheduled task development functionality. Its parent module is the Timer-Parent module (the common parent of the Timer component) under Project-Parent. The aforementioned business domain management domain includes the application-level online module Project-Online and the application-level batch module Project-Batch. Thus, it calls the sub-modules of the aforementioned functional module management domain Project-Components through the interfaces managed by the Interface Management Domain Project-API to provide services. The service modes are divided into the online transaction mode provided by the application-level online module Project-Online and the batch transaction mode provided by the application-level batch module Project-Batch.

[0098] To achieve online and batch processing capabilities, in one optional implementation, the processing unit further includes:

[0099] The fifth processing module is used to design an application-level online module and an application-level batch module based on the above-mentioned online and batch functions. The application-level online module provides the above-mentioned online function, and the application-level batch module provides the above-mentioned batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems.

[0100] The sixth processing module is used to combine the above-mentioned application-cascade module and the above-mentioned application-level batch module to generate the above-mentioned business domain management domain.

[0101] Specifically, such as Figure 4 As shown, project-online is the application-level online module (the online function provided by the core technology platform). According to the five-level modeling methodology, it is further divided into the composite service sub-layer (project-pcs), atomic service sub-layer (project-pbs), aggregation function sub-layer (project-pbc), instruction function sub-layer (project-pbb), and data access sub-layer (project-dao). The business function layer is further divided from a business perspective, which facilitates the combination and expansion of services and improves the system's business support capabilities. The parent modules of each business sub-layer correspond to the pcs-parent (pcs component common parent) module, pbs-parent (pbs component common parent) module, pbc-parent (pbc component common parent) module, pbb-parent (pbb component common parent) module, and dao-parent (dao component common parent) module under project-parent, respectively. project-batch is the application-level batch module (batch function provided by the core technology platform). It is responsible for providing application-level batch functions, including the corresponding pjs development (modulename-batch-pjs) and extension development (modulename-batch-extend). The parent module of project-batch is the batch-parent (batch component common parent) module under project-parent, which provides the online transaction mode for transaction business and the batch transaction mode through the application-level batch module project-batch.

[0102] To achieve lightweight deployment of the system engineering, in one optional implementation, the processing unit further includes:

[0103] The seventh processing module is used to design an online packaging module and a batch packaging module based on the application combination packaging function corresponding to the above online function and the above batch function. The online packaging module is used to deploy the components for online transactions, and the batch packaging module is used to deploy the components for batch transactions.

[0104] The eighth processing module is used to combine the online packaging module and the batch packaging module to generate the deployment layer.

[0105] Specifically, such as Figure 4 As shown, the above deployment layer, project-boot, combines different services to generate the final deployed application. The project-boot module imports the Spring-Boot plugin, providing application composition and packaging functionality. project-boot contains two sub-modules: the online packaging module online-boot and the batch packaging module batch-boot. The component relationships of online transactions in development mode are as follows: Figure 5 As shown, the sub-modules corresponding to the composite service sub-layer (project-pcs), atomic service sub-layer (project-pbs), aggregation function sub-layer (project-pbc), instruction function sub-layer (project-pbb), and data access sub-layer (project-dao), namely the sub-modules xxx-pcs, xxx-pbs, xxx-pbc, xxx-pbb, and xxx-dao, all inherit from their respective parent modules. The parent modules inherit from the system-level parent module project-parent of the parent domain layer. The system-level parent module project-parent depends on the framework layer's project-common, project-exception, and project-dict modules. All of these sub-modules are called through their corresponding interfaces, such as xxx-pcs-api, xxx-pbs-api, xxx-pbc-api, xxx-pbb-api, and xxx-dao-api, and inherit from the version of the automatic design software ads-project. The component relationships for batch transactions in development mode are as follows: Figure 6 As shown, compared to the online transaction component, it lacks the xxx-pcs and xxx-pbs submodules. This means there's no need to call the xxx-pcs and xxx-pbs submodules to provide atomic and composite services; transaction data can be processed in batches according to unified rules. The online transaction runtime state of the project template is as follows: Figure 7 and Figure 8As shown, the development and deployment states are separated, and different services are combined in the deployment layer to generate the final deployment application, thus achieving lightweight deployment of the system engineering.

[0106] For ease of development, in an optional embodiment, the above-mentioned apparatus further includes:

[0107] The addition unit is used to add an application development online packaging tutorial project to the online packaging module after designing the online packaging module and the batch packaging module according to the application combination packaging function corresponding to the online function and the batch function. The application development online packaging tutorial project is used to provide application developers with application project templates for learning and use.

[0108] Specifically, such as Figure 4 As shown, an online packaging tutorial project based on this application project template has been added under the online packaging module, allowing application developers to better learn and use the aforementioned application project template. The ads-practice-online-resource module under the tutorial project provides application transaction development resource management, including Apollo factory configuration, database scripts, and transaction baseline data. The ads-practice-online-server module provides application packaging configuration management, such as online transaction merge deployment configuration. ads-practice-online can be released as an independent project, ensuring that the resource project version is consistent with the server project version.

[0109] To improve deployment flexibility, in one alternative implementation, the above-mentioned apparatus further includes:

[0110] The deployment unit is used to separately deploy or merge the combined service sublayer and the atomic service sublayer after designing the application-level online module and the application-level batch module according to the above-mentioned online function and batch function. The above-mentioned separate deployment is a deployment state in which the above-mentioned combined service sublayer and the above-mentioned atomic service sublayer interact with the above-mentioned associated system through different channels, and the above-mentioned separate deployment is a deployment state in which the above-mentioned combined service sublayer and the above-mentioned atomic service sublayer interact with the above-mentioned associated system through the same channel.

[0111] Specifically, both the PCS service and the PBS service are registered in the Apollo configuration center or the Nacos configuration center. Associated systems can then call the registered PCS service or PBS service through the online gateway. The aforementioned combined service sublayer and the aforementioned atomic service sublayer interact with the aforementioned associated systems through different channels, representing a separate deployment. Figure 7 As shown, the aforementioned combined service sublayer and the aforementioned atomic service sublayer interact with the aforementioned related systems through the same channel, which constitutes a merged deployment, as... Figure 8 As shown, those skilled in the art can choose the appropriate deployment method according to the actual situation, making the application quite flexible.

[0112] The design apparatus for the aforementioned application engineering template includes a processor and a memory. The processing units and generation units are all stored as program units in the memory, and the processor executes these program units to achieve the corresponding functions. All of the above modules reside in the same processor; alternatively, the modules may be located in different processors in any combination.

[0113] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured, and adjusting kernel parameters can address the code redundancy issues that arise in the design and development of core business systems in existing technologies.

[0114] The memory may include non-permanent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0115] This invention provides a computer-readable storage medium including a stored program, wherein, when the program is executed, it controls the device where the computer-readable storage medium is located to execute the application engineering template design method.

[0116] Specifically, the design methods for applying engineering templates include:

[0117] Step S201: The architecture is layered according to the technical dimensions to obtain the framework layer, parent domain layer, business function domain layer and deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0118] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0119] Step S202: Combine the above framework layer, the above parent domain layer, the above business function domain layer and the above deployment layer to generate an application project template.

[0120] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0121] Specifically, step S201 includes: step S2011, designing the project-common module, project-exception module, and project-dict module according to the functions corresponding to the public services, wherein the project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system, the project-exception module is used to provide system-level exception handling mechanisms, and the project-dict module is used to provide a data dictionary; step S2012, combining the project-common module, the project-exception module, and the project-dict module to generate the framework layer.

[0122] Specifically, step S201 further includes: step S2013, designing the architecture based on the above technical dimensions to obtain an interface management domain, a functional module management domain, and a business domain management domain. The interface management domain is used to provide application interfaces, which correspond one-to-one with the above sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain is used to provide services such as online functions and batch functions. Step S2014, combining the interface management domain, the functional module management domain, and the business domain management domain to generate the above business functional domain layer.

[0123] Specifically, step S201 further includes: step S2015, designing an application-level online module and an application-level batch module based on the online function and the batch function. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. Step S2016, combining the application-level online module and the application-level batch module to generate the business domain management domain.

[0124] Specifically, step S201 further includes: step S2017, designing an online packaging module and a batch packaging module based on the application combination packaging function corresponding to the online function and the batch function, deploying the components of the online packaging module for online transactions, and deploying the components of the batch packaging module for batch transactions; step S2018, combining the online packaging module and the batch packaging module to generate the deployment layer.

[0125] Specifically, after step S2017, the method further includes step S301, adding an application development online packaging tutorial project to the online packaging module. The application development online packaging tutorial project is used to provide application developers with an opportunity to learn how to use application project templates.

[0126] Specifically, after step S2015, the method further includes: step S401, deploying the combined service sublayer and the atomic service sublayer separately or in combination. The separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using different channels, and the separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using the same channel.

[0127] This invention provides a processor for running a program, wherein the program executes the design method of the application engineering template.

[0128] Specifically, the design methods for applying engineering templates include:

[0129] Step S201: The architecture is layered according to the technical dimensions to obtain the framework layer, parent domain layer, business function domain layer and deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0130] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0131] Step S202: Combine the above framework layer, the above parent domain layer, the above business function domain layer and the above deployment layer to generate an application project template.

[0132] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0133] Specifically, step S201 includes: step S2011, designing the project-common module, project-exception module, and project-dict module according to the functions corresponding to the public services, wherein the project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system, the project-exception module is used to provide system-level exception handling mechanisms, and the project-dict module is used to provide a data dictionary; step S2012, combining the project-common module, the project-exception module, and the project-dict module to generate the framework layer.

[0134] Specifically, step S201 further includes: step S2013, designing the architecture based on the above technical dimensions to obtain an interface management domain, a functional module management domain, and a business domain management domain. The interface management domain is used to provide application interfaces, which correspond one-to-one with the above sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain is used to provide services such as online functions and batch functions. Step S2014, combining the interface management domain, the functional module management domain, and the business domain management domain to generate the above business functional domain layer.

[0135] Specifically, step S201 further includes: step S2015, designing an application-level online module and an application-level batch module based on the online function and the batch function. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. Step S2016, combining the application-level online module and the application-level batch module to generate the business domain management domain.

[0136] Specifically, step S201 further includes: step S2017, designing an online packaging module and a batch packaging module based on the application combination packaging function corresponding to the online function and the batch function, deploying the components of the online packaging module for online transactions, and deploying the components of the batch packaging module for batch transactions; step S2018, combining the online packaging module and the batch packaging module to generate the deployment layer.

[0137] Specifically, after step S2017, the method further includes step S301, adding an application development online packaging tutorial project to the online packaging module. The application development online packaging tutorial project is used to provide application developers with an opportunity to learn how to use application project templates.

[0138] Specifically, after step S2015, the method further includes: step S401, deploying the combined service sublayer and the atomic service sublayer separately or in combination. The separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using different channels, and the separate deployment is a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using the same channel.

[0139] This invention provides a development platform for a core business system. The device includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, it performs at least the following steps:

[0140] Step S201: The architecture is layered according to the technical dimensions to obtain the framework layer, parent domain layer, business function domain layer and deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0141] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0142] Step S202: Combine the above framework layer, the above parent domain layer, the above business function domain layer and the above deployment layer to generate an application project template.

[0143] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0144] This application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having at least the following method steps:

[0145] Step S201: The architecture is layered according to the technical dimensions to obtain the framework layer, parent domain layer, business function domain layer and deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimensions are the dimensions corresponding to the implementation logic of the services.

[0146] Specifically, the aforementioned framework layer, `project-framework`, is the common functional component management domain. It acts as a bridge between the parent POM and the sub-POM. "Bridging" refers to inheriting the core business platform from the parent POM and managing the platform component versions. "Bridging" refers to providing clear functional divisions, unified common capabilities, and a common parent POM for all related systems within the project. The parent domain layer, `project-parent`, is the system-level parent module, divided into various types of parent sub-modules for lower-level functions of the same type to inherit from. The business functional domain layer provides atomic or composite services, including at least the functional module management domain `project-component`. It extracts core technology platform functions such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions that may be used in various business applications into a unified common module for unified management. The aforementioned deployment layer, `project-boot`, is used to combine different services to generate applications and complete application design.

[0147] Step S202: Combine the above framework layer, the above parent domain layer, the above business function domain layer and the above deployment layer to generate an application project template.

[0148] Specifically, the architecture of the above application engineering template is as follows: Figure 3 and Figure 4 As shown, it includes the framework layer project-framework, which is the common functional component management domain, the parent domain layer project-parent, the deployment layer project-boot, and the interface management domain project-api, the functional module management domain project-component, the application-level online module project-online, and the application-level batch module project-batch under the business function domain layer.

[0149] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those described herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0150] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0151] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0152] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0153] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0154] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0155] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0156] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0157] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0158] As can be seen from the above description, the embodiments of this application achieve the following technical effects:

[0159] 1) In the design method of the application engineering template of this application, firstly, the architecture is layered according to the technical dimension to obtain the framework layer, the parent domain layer, the business function domain layer and the deployment layer. The framework layer is used to provide common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimension is the dimension corresponding to the implementation logic of the services. Then, the framework layer, the parent domain layer, the business function domain layer and the deployment layer are combined to generate the application engineering template. This design methodology utilizes an architecture framework layer to provide common services, encapsulating and extending the common capabilities of the underlying framework, thus reducing code redundancy. Furthermore, it employs a parent domain layer and a business function domain layer. By importing dependency packages into the parent module of the parent domain layer, the corresponding submodules in the business function domain layer can inherit and use these packages without importing dependency packages themselves. For example, if the dependency package includes version dependencies, the submodule's code does not need to include version numbers, further reducing code redundancy. The deployment layer combines the common services and the services provided by the submodules to generate the application, completing the application design. This application engineering template is used for the design and development of the core business system. The framework layer and the parent domain layer form a common functional component management domain, enabling the management of platform component versions in the core business system and providing clear functional divisions and unified common capabilities, thereby significantly reducing code redundancy and solving the problem of code redundancy in the design and development of core business systems in existing technologies.

[0160] 2) In the application engineering template design device of this application, the processing unit performs architectural design layering according to the technical dimension to obtain a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer is used to provide public services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules. Each sub-module corresponds to one parent module. The parent module is used to import dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules are used to provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimension is the dimension corresponding to the implementation logic of the services. The generation unit combines the framework layer, the parent domain layer, the business function domain layer, and the deployment layer to generate an application engineering template. This design device utilizes an architecture framework layer to provide common services, encapsulating and extending the common capabilities of the underlying framework, thus reducing code redundancy. Furthermore, through the architecture design of a parent domain layer and a business function domain layer, dependency packages are imported into the parent module of the parent domain layer, allowing corresponding submodules in the business function domain layer to inherit and use them. Submodules do not need to import dependency packages; for example, if the dependency package includes version dependencies, the submodule code does not need to include version numbers, further reducing code redundancy. The deployment layer combines the services provided by the common services and submodules to generate the application, completing the application design. This application engineering template is used for the design and development of the core business system. The framework layer and parent domain layer form a common functional component management domain, enabling the management of platform component versions in the core business system and providing clear functional divisions and unified common capabilities, thereby significantly reducing code redundancy and solving the problem of code redundancy in the design and development of core business systems in existing technologies.

[0161] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A design method for application engineering templates, characterized in that, include: The architecture is layered according to technical dimensions, resulting in a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer provides common services. The parent domain layer includes multiple parent modules. The business function domain layer includes multiple sub-modules, with one sub-module corresponding to one parent module. The parent module imports dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules provide atomic services or composite services. The deployment layer combines different services to generate applications. The technical dimension refers to the dimension corresponding to the implementation logic of the service. The framework layer, the parent domain layer, the business function domain layer, and the deployment layer are combined to generate an application engineering template. The architecture is layered according to technical dimensions to obtain a framework layer, including: a project-common module, a project-exception module, and a project-dict module designed according to the functions corresponding to the public services. The project-common module is used to provide system-level common processing capabilities, which are the common data processing capabilities of the current system. The project-exception module is used to provide system-level exception handling mechanisms. The project-dict module is used to provide a data dictionary. The framework layer is generated by combining the project-common module, the project-exception module, and the project-dict module. The architecture is layered according to technical dimensions to obtain the business function domain layer, which includes: an interface management domain, a functional module management domain, and a business domain management domain. The interface management domain provides application interfaces, which correspond one-to-one with the sub-modules. The functional module management domain provides services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain provides online and batch functions. The interface management domain, the functional module management domain, and the business domain management domain are combined to generate the business function domain layer. Based on the aforementioned technical dimensions, an architecture design is performed to obtain a business domain management domain, including: designing an application-level online module and an application-level batch module based on the online function and the batch function. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a composite service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The composite service sublayer and the atomic service sublayer provide corresponding services to associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the composite service of the composite service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the composite service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. The application-level online module and the application-level batch module are combined to generate the business domain management domain.

2. The design method according to claim 1, characterized in that, The architecture is layered based on technical dimensions, resulting in a deployment layer, which includes: Based on the application combination packaging function corresponding to the online function and the batch function, an online packaging module and a batch packaging module are designed. The online packaging module is used to deploy components for online transactions, and the batch packaging module is used to deploy components for batch transactions. The online packaging module and the batch packaging module are combined to generate the deployment layer.

3. The design method according to claim 2, characterized in that, After designing the online packaging module and the batch packaging module based on the application combination packaging functions corresponding to the online function and the batch function, the method further includes: Add an application development online packaging tutorial project to the online packaging module. The application development online packaging tutorial project is used to provide application developers with application project templates for learning.

4. The design method according to claim 1, characterized in that, After designing the application-level online module and the application-level batch module based on the online function and the batch function, the method further includes: The combined service sublayer and the atomic service sublayer can be deployed separately or combined. Separate deployment refers to a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using different channels, while separate deployment refers to a deployment state in which the combined service sublayer and the atomic service sublayer interact with the associated system using the same channel.

5. A design device for applying engineering templates, characterized in that, include: The processing unit is used to perform architectural design layering based on technical dimensions, resulting in a framework layer, a parent domain layer, a business function domain layer, and a deployment layer. The framework layer provides common services, the parent domain layer includes multiple parent modules, and the business function domain layer includes multiple sub-modules, with one sub-module corresponding to one parent module. The parent module imports dependency packages so that the corresponding sub-modules can inherit and use them. The dependency packages include at least version dependency packages. The sub-modules provide atomic services or composite services. The deployment layer is used to combine different services to generate applications. The technical dimension is the dimension corresponding to the implementation logic of the service. A generation unit is used to combine the framework layer, the parent domain layer, the business function domain layer, and the deployment layer to generate an application engineering template. The processing unit includes: a first processing module, used to design and obtain a project-common module, a project-exception module, and a project-dict module according to the functions corresponding to the public service; the project-common module is used to provide system-level common processing capabilities, which are the data processing capabilities commonly used in the current system; the project-exception module is used to provide a system-level exception handling mechanism; and the project-dict module is used to provide a data dictionary; and a second processing module, used to combine the project-common module, the project-exception module, and the project-dict module to generate the framework layer. The processing unit further includes: a third processing module, used to perform architectural design based on the technical dimensions to obtain an interface management domain, a functional module management domain, and a business domain management domain. The interface management domain is used to provide application interfaces, which correspond one-to-one with the sub-modules. The functional module management domain is used to provide services such as transaction outbound calls, sequence number generation, message sending and receiving, and timing functions. The business domain management domain is used to provide online and batch functions. A fourth processing module is used to combine the interface management domain, the functional module management domain, and the business domain management domain to generate the business functional domain layer. The processing unit further includes: a fifth processing module, used to design an application-level online module and an application-level batch module based on the online function and the batch function. The application-level online module provides the online function, and the application-level batch module provides the batch function. The application-level online module includes a combined service sublayer, an atomic service sublayer, an aggregation function sublayer, an instruction function sublayer, and a data access sublayer. The combined service sublayer and the atomic service sublayer provide corresponding services to the associated systems connected to the core system. The aggregation function sublayer combines the atomic services of the atomic service sublayer to form the combined service of the combined service sublayer. The instruction function sublayer generates instructions to control the sub-modules corresponding to the combined service sublayer and the atomic service sublayer to provide services. The data access sublayer interacts with the associated systems. A sixth processing module is used to combine the application-level online module and the application-level batch module to generate the business domain management domain.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the design method according to any one of claims 1 to 4.

7. A development platform for a core system, characterized in that, include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including methods for performing the design method according to any one of claims 1 to 4.

Images