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

Abstract

The invention discloses a method for quickly creating a base data aggregation warehouse based on an agile low-code platform, which is characterized by comprising the following steps of: 1, designing a data model; 2, designing a front end; 3, designing a rear end; step 4, setting rules; 5, compiling and constructing a page; step 6, importing a data source; and step 7, generating a page. According to the method, the basic-level special item checking online efficiency is greatly improved, the professional software development cost is reduced, and the special item response speed is increased.

Description

technical field [0001] The invention relates to a method for quickly creating a grass-roots data aggregation warehouse based on an agile low-code platform. Background technique [0002] Existing traditional software has the following problems or defects: [0003] First, the investment in traditional software development is large. To build a customized special verification module from scratch needs to be built for different terminal devices (for example: Web terminal, mobile terminal, Android terminal, iOS terminal, etc.), it needs to analyze the business, and then invest in different terminal equipment separately develop. Because the development modules in charge of personnel will produce complicated problems such as complex functions, numerous business modules, and difficult development, and the conversion cost and time are limited, consuming a lot of resources. [0004] Second, traditional software systems are not flexible enough. The government affairs department invo...

AI Technical Summary

Problems solved by technology

Because the development modules in charge of personnel will produce complex functions, numerous business modules, and difficult development, etc., and the transfer cost and time are limited, consuming a lot of resources

[0004] Second, traditional software systems are not flexible enough

The government affairs department involves complex processes. Because different departments and users are involved, these process rules will continue to change. Traditional software cannot adapt to the frequently changing workflow. The changing needs still need to strictly follow the traditional software development model, conduct demand analysis, Design, code, integrate, test, and maintain steps all in sequence

It is difficult to adapt to the changing process between government departments, and the development team often responds to time-consuming and tedious tasks, such as temporarily changing requirements, changing data, etc.

At the same time, it is necessary to wait for developers to schedule to meet business change requirements, making it difficult to lock in the functional requirements of a system with a low structural level in the early stage of development, and the development cycle is long, making it difficult to adapt to changes in government affairs

[0005] Third, traditional software systems are prone to information islands

Traditional systems are developed and introduced in a decentralized manner. Information is sealed in the services provided by different terminal devices. Definition and collection are independent of each other, forming many sub-modules. A large amount of useful information is scattered in the "dead corners" of each system, which cannot be effectively used and shared

Moreover, it is difficult to tightly integrate with other business systems of the government department, and it takes a lot of manpower and material resources to switch between different application systems to obtain corresponding information for analysis, resulting in waste of resources and duplication of labor

The first premise of establishing government sharing and digitalization of government is to ensure the smooth flow and efficient use of information, while traditional software development systems cannot establish such a collaborative environment due to their relatively outdated architecture

Images