CN114281797A - Method for quickly creating basic level data aggregation warehouse based on agile low-code platform - Google Patents

Abstract

The invention discloses a method for quickly creating a base layer data aggregation warehouse based on an agile low-code platform, which is characterized by comprising the following steps of: step one, designing a data model; designing a front end; step three, designing a rear end; step four, setting rules; fifthly, compiling and constructing the page; step six, importing a data source; and step seven, generating a page. The method greatly improves the online efficiency of basic level special item check, reduces the development cost of professional software and accelerates the special item response speed.

Description

Method for quickly creating basic level data aggregation warehouse based on agile low-code platform

Technical Field

The invention relates to a method for quickly creating a base layer data aggregation warehouse based on an agile low-code platform.

Background

The existing traditional software has the following problems or defects:

first, traditional software development is very costly. The establishment of a customized special verification module from the beginning requires the establishment of a module containing information for different terminal devices (e.g., a Web end, a mobile end, an Android end, an iOS end, etc.), and requires the analysis of services and the independent development of different terminal devices. Because the development module that personnel are responsible for can produce the function complicacy, business module numerous, development degree of difficulty is big etc. complicated problem to be restricted in cost and the time, consume a large amount of resources.

Second, conventional software systems are not flexible enough. The government department relates to complex processes, the process rules can be changed continuously due to different departments and users, the traditional software cannot adapt to frequently changed work processes, the changing requirements still need to strictly follow the traditional software development mode, and the steps of analyzing, designing, coding, integrating, testing and maintaining the requirements need to be carried out in sequence. It is difficult to adapt to the changing flow among government departments, and development teams often perform time-consuming and tedious task responses, such as temporary demand change, data change and the like. Meanwhile, the developers need to wait for the scheduling to meet the requirement of business change, so that the functional requirements of a system with low structural degree are difficult to lock in the initial development stage, the development period is long, and the system is difficult to adapt to government affair changes.

Third, conventional software systems are prone to information islanding. The traditional systems are all developed and introduced dispersedly, information is sealed in services provided by different terminal devices, the information is defined and collected independently to form a plurality of sub-modules, a large amount of useful information is scattered in dead corners of each system, and the useful information cannot be effectively utilized and shared. In addition, it is difficult to integrate with other business systems of government departments, and a large amount of manpower and material resources are required to be switched among different application systems to obtain corresponding information for analysis, which results in resource waste and repeated labor. The first premise of establishing government digitalization for government sharing is to ensure smooth and efficient use of information, and the traditional software development system cannot establish such a cooperation environment due to the relatively old architecture.

Therefore, it is urgently needed to provide a method for solving the above technical problem.

Disclosure of Invention

The invention aims to provide a method for quickly creating a basic level data convergence warehouse based on an agile low-code platform, which greatly improves the online efficiency of basic level special item check, reduces the development cost of professional software and accelerates the special item response speed.

In order to achieve the above object, the present invention provides a method for quickly creating a base-level data aggregation warehouse based on an agile low-code platform, the method comprising:

step one, designing a data model;

designing a front end;

step three, designing a rear end;

step four, setting rules;

fifthly, compiling and constructing the page;

step six, importing a data source;

and step seven, generating a page.

Preferably, the first step includes performing data connection configuration and form configuration on a common database and language; wherein the content of the first and second substances,

the data connection configuration generates a database table connection code by defining a configuration database, and is used for connecting the database;

the form configuration describes the table structure in the database according to the UML, extracts the database table structure from the existing database or data definition language ddl by using the two-way engineering technology, establishes a model, and automatically generates a corresponding table structure in the database according to the defined data model for the form configuration.

Preferably, in the second step, components of the page content definition specification are adopted, a code form based on JSON Schema page component structural templating and a corresponding data model replaces front-end hard coding, one or a group of DOM grammar forms and style styles containing specific functions are generated by using a program, and a plurality of defined component trees are displayed on a front-end page in a dragging and configuring mode and contain Dynamic interactive Logic Dynamic Logic.

Preferably, in step three, the data model is used as a driver to realize the configured personalized requirements, and the corresponding back-end code is designed according to the DDD according to the analysis of the domain and the aggregation.

Preferably, in step four, according to the data domain situation used by the actual service requirement, the related data domain is subjected to verification rule setting and binding rule setting; wherein the content of the first and second substances,

the setting of the checking rule comprises checking that the data field must be filled, checking that the data field has a unique value, checking whether the data field is a 6-16 digit number, checking whether the data field is a 6-16 digit arbitrary character, checking whether the data field is a website, checking whether the data field is an email and checking whether the data field is a mobile phone number;

the binding rule setting comprises the steps of generating binding aiming at classes to bind a structural body and an independent function, binding a corresponding interface of a back end by the binding rule, binding a component rule and a front end component by a dom mode, and binding an API interface and a back end data model by an AJAX mode.

Preferably, in the step five, a certain rule is divided according to the business requirements to limit the business problems within a specific boundary, so that a plurality of core field ranges are divided; the low code core domain uses a flow abstraction to abstract out the following modules: form design- > data modeling- > process design- > view design, and a user of the designed page can see corresponding page data in the view by filling data- > submitting the form- > and the user can see the corresponding page data in the view.

Preferably, the data in the step six is imported through a database, imported through a system and docked through the database.

Preferably, the page generation in the step seven includes: according to the special development requirements, the low-code platform provides a plurality of sets of configurable page interaction templates with different styles; and constructing the application software by adopting a building block mode through the constructed service components.

According to the technical scheme, the invention develops the rich components and the data visualization framework by using micro-service technology such as front-end and back-end separation frameworks SpringBoot2.x, SpringCloud, AntDesign & Vue, Mybatis-plus, Shiro, JWT, json Schema, MybatisPlus and the like through research on the basic-level service and understanding on the special basic-level service. Business personnel use the interface of the visual graph to configure special information by dragging various rich controls on line, do not need the assistance of professional developers to carry out a large amount of program coding work, and create a special checking task under the condition of not needing or writing a small amount of codes.

Most of the UI components and the visual modules are dragged to replace or even not need coding work, and the project components (code files such as front end, back end and database configuration) are automatically generated through standardized tools and are deployed through seamless pages, so that the rapid business special item check online operation is realized.

By adopting a low-code technology to quickly establish a digital solution for basic level special inspection and an automatic working process, the online efficiency of basic level special inspection is greatly improved, the development cost of professional software is reduced, the special response speed is accelerated, and a basic level special inspection task can be established and deployed within a few days.

Additional features and advantages of the invention will be set forth in the detailed description which follows.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention. In the drawings:

fig. 1 is a framework diagram of a method for quickly creating a base-level data aggregation warehouse based on an agile low-code platform according to the present invention.

Detailed Description

The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.

Referring to fig. 1, the present invention provides a method for quickly creating a base-level data aggregation warehouse based on an agile low-code platform, which specifically includes:

the method comprises the following steps: data model design

The software system is a very complex system, and the final expression is that executable program code (front end code + back end code) calls data in a database to be displayed at a page end.

The data table in the database is a table for storing data (records), the data table is composed of three parts of a table name, fields in the table and records in the table, a corresponding database table is usually designed by professional technicians in the traditional software development process, and if the field design in the database needs to be adjusted due to business adjustment after the system is on line, the processes of development, testing and the like need to be carried out again according to software development specifications.

According to actual business needs, the patent performs data connection configuration and form configuration on commonly used databases and languages. Wherein the content of the first and second substances,

when configuring data connection, developing corresponding database connection adaptive drive according to common database data types, wherein the specific data connection configuration steps are as follows:

1. by defining driver _ class, the database can be adapted to the class name of a common database driver;

2. by defining a driverClassName, a connection name of a corresponding database can be configured;

3. configuring a data source database address by defining a jdbc connection url;

4. configuring a data source database user name and a password by defining the user name and the password of an access database;

through the definition, the program can generate database table connection codes, and the database can be connected in the subsequent use.

In the form configuration, the table structure inside the database is described according to the UML, the database table structure is extracted from the existing database or the data definition language ddl by utilizing the two-way engineering technology, a model is built, and the corresponding table structure is automatically generated in the database according to the defined data model for carrying out the form configuration.

The specific form configuration steps are as follows:

1. creating database code: and according to the concise and intuitive database table providing page configuration and the management and operation of the fields, remarks of a data field configuration support table and an extended attribute list.

2. And supporting data type and data field configuration: according to the UML language, a special service model is described by using an IDFE language, and Data modeling (Data modeling) design is completed by analyzing and defining the same type of Data types with specific service meanings as Data fields after design.

2.1, defining database data types, including creating the database data types used by the patent according to the database ddl syntax: integer (int), decimal (decimal), date (data), binary (blob), text (varchar), large text (text), etc.;

2.2, defining database field data fields, including defining data fields in the system according to the data types used in the database: character strings, amounts, dates and times, data dictionaries, descriptive text, etc.

Step two: front end design

The front part of a project is essentially connected with different pages through URL routing, each page is displayed and rendered in a browser, html needs to be loaded when a website page is visited, and a complete html structure comprises: the browser completes page display by analyzing the DOM syntax Tree (DOM Tree) and the Style (Style) to generate Dynamic interaction Logic (Dynamic Logic).

A website page can be understood as a page Tree, the method adopts components of page content definition specifications, replaces front-end hard coding with code forms based on JSON Schema page component structural templating and a corresponding data model, uses a program to generate one or a group of DOM grammar forms and style styles containing specific functions, and displays a plurality of defined component trees (Componet Tree) and Dynamic interaction Logic (Dynamic Logic) on a front-end page in a dragging and configuring mode. When the page is developed, the front end does not need to manually write codes.

The form component and the form component attribute data are respectively from a step definition database data type generation form component and a step definition database field data field generation form component attribute.

The left component group is constructed by using JSON Schema as follows:

1. and defining the Type name of the component, wherein the component is a universal service component or a component library developed according to the unified UI design front end.

Taking a common table component as an example, the main construction mode of the business component is as follows:

1.1, the table is built in by setting the following custom attributes actions, columns, serchSchema and modelschema:

1.1.1, using actions to define the event responded by the table component, responding the content in the api interface and the like;

1.1.2, defining table component header related content by using Columns;

1.1.3, using Dataset to define the text content in the table;

1.1.4, defining the content and the style of a search form of a table by using a serchSchema;

1.1.5, defining popup form contents and styles by using a modelschema;

2. and defining attribute profiles configuration, and simultaneously configuring the front-end rendering execution sequence by defining the attributes and values of the components, so that the browser can execute the components according to the schema rendering principle.

3. Defining child nodes, setting text nodes, components or child element lists, and enabling the browser to display corresponding components after rendering according to the specification.

4. Defining custom render, registering the defined components. The browser can transmit the parameter params required by the patent and finally return the data required to be displayed on the page.

5. Interaction functions are defined, and common page display can relate to interaction modes such as mouse events, keyboard events and the like, so that the interaction functions need to be built in for a browser to generate interaction logic.

6. And defining page routing, wherein the page routing is generally an entrance of page access, and the related page can be opened by accessing the corresponding url when the page routing is defined for use.

The corresponding front-end components can be generated by the above definitions. After the components are defined, a component moving mode is defined by a method supported by front ends such as definition moveNodes and the like, so that the components can automatically drag the middle view domain to interactively display and preview the page in a dragging mode.

Step three: design of back end

The backend program needs to manage and maintain the database, system, and backend operations' portals. And (3) realizing the configured personalized requirements by taking the data model as a driver, and designing a corresponding back-end code according to the DDD according to the analysis of the field and the aggregation.

The patent defines the design of the back-end low code as follows according to the actual business requirement:

1. defining application layer application, mainly responsible for editing field service;

2. defining a domain layer, which is mainly responsible for domain objects, storage and domain services;

3. defining a basic layer infrastructure, and mainly providing basic tools and components of the project for use;

4. defining user interface layers, and mainly providing services such as API (application programming interface) and the like for a front end;

the main steps of the back-end low code design are as follows:

1. designing a back-end data model: the read-write operation of acquiring the data table by dynamically configuring and generating the Model is completed by designing the following functions, including: dynamically generating a model by using a back-end program, dynamically generating an ORM query logic according to the dynamically generated model and dynamically generating a serialization class of the model by using the back-end program;

2. designing a management interface back-end program: through a designed back-end program, management interfaces such as a list page, a form page and a detail page can be configured;

3. designing a trigger, and carrying out encapsulation processing on the expansion modes before and after the interface calling;

4. and for the function which cannot be customized, writing a corresponding interface function in a pure function mode.

Step four: rule setting

And according to the data domain condition used by the actual service requirement, carrying out verification rule setting and binding rule setting on the relevant data domain. Wherein the content of the first and second substances,

the verification rule setting comprises:

checking the data field must be filled: registering metadata fields needing uniqueness verification in a required filling rule table, and calling a verification rule class to verify whether the data field verification fields need to be filled;

checking the data field unique value: registering metadata fields needing uniqueness verification into a uniqueness verification rule table, and calling a verification rule class to judge whether the field values of the current database are unique;

check if the data field is a 6 to 16 digit number: registering metadata fields needing to be checked into a regular expression table, and calling the regular expression/[ a-z0-9] {6,16 }; judging whether the stored value of the database is 6 to 16 digits or not;

check if the data field is any character from 6 to 16 bits: registering metadata fields needing to be verified in a regular expression table, and calling the regular expression/[ 0-9a-zA-Z ] {6,16 }; judging whether the stored value of the database is any character of 6 to 16 bits;

checking whether the data field is a website: registering a metadata field needing to be checked into a regular expression table, and calling a regular expression/(http | ftp | https):/\\\\ \ w \ + (\\ \ w \ \? V,; judging whether the stored value of the database is a website or not;

checking whether the data field is an email: the basic format of the mailbox is formed by a name @ domain name, the start part of a ^ matching mailbox is used, the end part of a ^ matching mailbox is used to ensure that other characters cannot exist before and after the mailbox, a metadata field needing to be checked is registered in a regular expression table, and a regular expression ^/[ a-zA-Z0-9_ ] + (\[ a-zA-Z0-9_ ] +/; judging whether the stored value of the database is an email or not;

checking whether the data field is a mobile phone number: since the mobile phone number is generally 11 bits, the mobile number segment can only start with 1 by using the identifier of ^ 139, 138, 137, 136, 135, 134, 150, 151, 152, 157, 158, 159, 182, 183, 187, 188, 147; 130, 131, 132, 136, 185, 186, 145; registering metadata fields needing to be checked in a regular expression table, calling the regular expression/^ 1 (.

The binding rule configuration comprises the following steps:

binding is generated aiming at the class, and a structural body, an independent function and the like can be bound;

binding rules, which can bind the corresponding interface of the back end;

the dom mode is used. Binding component rules, binding front-end components;

binding an API (application programming interface) interface, binding a back-end data model and the like in an AJAX mode;

according to the rule configuration, a special database can be created and stored in a related way, and the subsequent effective retrieval and access to the data are facilitated.

Step five: page compilation build

And a certain rule is divided according to the service requirement, so that the service problem is limited within a specific boundary, and a plurality of core field ranges are divided.

The low code core domain uses a flow abstraction to abstract out the following modules: form design- > data modeling- > process design- > view design, and a user of the designed page can see corresponding page data in the view by filling data- > submitting the form- > and the user can see the corresponding page data in the view.

Form design field:

the form refers to a form submitted by html, and form entities comprise form attributes, form configuration modules and the like. The form design domain comprises the following main steps:

1. setting the attribute and configuration of a single component on a page;

2. setting form attributes and configuration on a page, wherein one form corresponds to N components, and one component has the attributes and configuration;

3. designing a page display form by dragging a page component on a page and using a custom layout;

4. the front end and the back end are separately designed, the back end is only responsible for storing the data model, and the front end is used for adjusting;

5. the front end renders a page according to the design layout and the components of the front-end low-code design component in the second step;

6. and the back end obtains the data model field according to the third step of the back end low code to render the page data.

Data model field:

the data model is a data structure formed by component fields, and can enable a WEB request to process an Action through operation and configuration of components and values, including but not limited to a CURD operation.

The data model domain comprises the following main steps:

1. initializing a data model after the form is built;

2. five methods are built in the initialized data model: adding, updating, deleting, inquiring and listing inquiring can be bound with self-defined method integrated service. The CURD operation can be carried out on the data model;

3. the data model allows binding rules, triggering events. Such as: when the data model is newly added, the event B can be triggered under the condition of meeting the condition A;

4. the data model can be internally provided with permission setting, namely a designated role can view which data;

5. and the automatic assembly of the data model is used for validation.

The work flow field:

workflow is independent from other domains, mainly meaning that parts or the whole of a business process automatically perform operations in a computer application environment.

The workflow is a core technology for realizing business process modeling, business process simulation, business process management and integration, thereby realizing final business process automation.

The workflow domain establishing steps are as follows:

1. establishing a display layer: the system consists of HTML pages and provides an interactive interface with a user. A user inputs data, submits the data and obtains an execution result;

2. establishing a control layer: processing the request of the presentation layer, forwarding the data submitted by the user to the business logic layer, processing the returned data of the application layer of the business logic layer, and generating a corresponding component to be transmitted to the presentation layer;

3. establishing a service logic layer: and carrying out actual service logic processing, storing the data into a data persistence layer, and realizing the buffering of service data by a service logic application layer.

According to the business analysis, the workflow domain comprises a process definition part, a process management part, a monitoring part, a workflow engine part, a work item list part and the like.

View field:

the view is a background management view page, the form data submitted by the front end can be rendered and displayed on the view, the view domain mainly enables a web request to process an Action, and corresponding page routing can be automatically switched by clicking a corresponding button.

The view domain establishment steps are as follows:

1. a service designer specifies which components and fields are displayed on a view page;

2. five CURD operation methods are built in the data model, five buttons are shown on a view, and the configuration is according to binding rules and permissions;

3. the view is saved and then assembled for effective use;

4. the front end transmits the layout configuration of the view to the back end;

5. data flow for front and back end view pages;

6. and (4) assembling and using a built-in method.

Step six: data source import

The established data related to the special items are mainly subjected to data initialization and warehousing in the following modes:

firstly, database import:

aiming at the electronic account book data of the community, the file type of the stored account book data is firstly changed into the file type capable of being imported into the database, and then the data is imported into the system in a database import mode.

And converting the community paper account into an electronic account by a community worker and then importing the database aiming at the community paper account.

Secondly, system import:

for information of each business department, information systems, such as civil administration, health care, human society and other department data, are researched, analyzed and combed, data of the existing system of the department are exported by using an automatic data acquisition function through guide type operation without a database docking mode, and then base warehouse data import is carried out according to related data import standards.

Thirdly, docking the database:

and aiming at the data of the big data center, importing the data into the system by using a front-end processor.

Step seven: page generation

The advantage of the platform can be fully utilized in the architectural design of the low-code design, and the visual modeling tool of the low-code platform can be presented in the language of the business, so that the architectural scheme can better meet the business requirement, and the design efficiency is higher.

The main method for generating the page comprises the following steps:

according to the special development requirement, a low-code platform provides a plurality of sets of configurable page interaction templates with different styles, and application software is built in a mode of building blocks by building a plurality of built service components which are verified by a large number of projects. And, the existing service components are utilized as much as possible to realize 'primary modeling and multi-channel equipment (such as Web end, mobile end, Android end, iOS end and the like) distribution'.

According to the technical scheme, elements such as the business rules and the business objects are stripped from the program codes by defining the complex business rule configuration module, business personnel are allowed to participate in the configuration of the rules by carrying out unified management and visual business rule modeling on the elements such as the business rules and the business objects, and then the codes are automatically generated by using the program, so that unified pages are provided for the outside. The requirement of rule configurability can be well solved, and the complexity of application system codes is reduced.

Meanwhile, when a special service to be processed by digital application is complex, ordinary coding cannot well describe the complex service objects, and traditional hard coding cannot be used for agile development of complex application. However, the low-code platform has strong capability of defining and processing complex business object models, and is very suitable for agile development.

Furthermore, the digital government affair application bears a plurality of related government affair core business processes; these flows consist of many sub-flows, each in turn consisting of different processing modules/pages. The low-code platform can realize module/page configuration through a componentization and configuration method, and then different application subsystems are formed through a building block method.

In addition, the low-code platform can provide reusable service components, and by continuously accumulating special checking knowledge, the application development of government affairs special is more agile, and the expansion capability of IT system supporting special services is stronger.

The preferred embodiments of the present invention have been described in detail with reference to the accompanying drawings, however, the present invention is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present invention within the technical idea of the present invention, and these simple modifications are within the protective scope of the present invention.

It should be noted that the various technical features described in the above embodiments can be combined in any suitable manner without contradiction, and the invention is not described in any way for the possible combinations in order to avoid unnecessary repetition.

In addition, any combination of the various embodiments of the present invention is also possible, and the same should be considered as the disclosure of the present invention as long as it does not depart from the spirit of the present invention.

Claims (8)

1. A method for quickly creating a base-level data aggregation warehouse based on an agile low-code platform, the method comprising:

step one, designing a data model;

designing a front end;

step three, designing a rear end;

step four, setting rules;

fifthly, compiling and constructing the page;

step six, importing a data source;

and step seven, generating a page.

2. The method of claim 1, wherein step one comprises configuring data connection and form for common database and language; wherein the content of the first and second substances,

the data connection configuration generates a database table connection code by defining a configuration database, and is used for connecting the database;

the form configuration describes the table structure in the database according to the UML, extracts the database table structure from the existing database or data definition language ddl by using the two-way engineering technology, establishes a model, and automatically generates a corresponding table structure in the database according to the defined data model for the form configuration.

3. The method according to claim 1, wherein in step two, components of the page content definition specification are adopted, a code form based on JSON Schema page component structure templating and a corresponding data model is used for replacing front-end hard coding, one or a group of DOM grammar forms and style styles containing specific functions are generated by a program, and a plurality of defined component trees are displayed on a front-end page in a dragging and configuring mode and contain Dynamic interactive Logic Dynamic Logic.

4. The method of claim 1, wherein in step three, the personalized requirements of the configuration are implemented by taking the data model as a driver, and the corresponding back-end code is designed according to the DDD according to the analysis of the domain and the aggregation.

5. The method according to claim 1, wherein in step four, according to the data domain situation used by the actual service requirement, the related data domain is subjected to the verification rule setting and the binding rule setting; wherein the content of the first and second substances,

the setting of the checking rule comprises checking that the data field must be filled, checking that the data field has a unique value, checking whether the data field is a 6-16 digit number, checking whether the data field is a 6-16 digit arbitrary character, checking whether the data field is a website, checking whether the data field is an email and checking whether the data field is a mobile phone number;

the binding rule setting comprises the steps of generating binding aiming at classes to bind a structural body and an independent function, binding a corresponding interface of a back end by the binding rule, binding a component rule and a front end component by a dom mode, and binding an API interface and a back end data model by an AJAX mode.

6. The method according to claim 1, wherein in step five, a certain rule is divided according to business requirements to limit business problems within a specific boundary, thereby dividing a plurality of core domain ranges; the low code core domain uses a flow abstraction to abstract out the following modules: form design- > data modeling- > process design- > view design, and a user of the designed page can see corresponding page data in the view by filling data- > submitting the form- > and the user can see the corresponding page data in the view.

7. The method of claim 1, wherein the data in step six is imported through a database, imported through a system, and docked through a database.

8. The method of claim 1, wherein the page generation in step seven comprises: according to the special development requirements, the low-code platform provides a plurality of sets of configurable page interaction templates with different styles; and constructing the application software by adopting a building block mode through the constructed service components.

Images