CN117234466B - Enterprise management software development method, system, equipment and storage medium - Google Patents
Enterprise management software development method, system, equipment and storage medium Download PDFInfo
- Publication number
- CN117234466B CN117234466B CN202310988192.0A CN202310988192A CN117234466B CN 117234466 B CN117234466 B CN 117234466B CN 202310988192 A CN202310988192 A CN 202310988192A CN 117234466 B CN117234466 B CN 117234466B
- Authority
- CN
- China
- Prior art keywords
- information
- software
- product
- data dictionary
- program
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 73
- 238000013439 planning Methods 0.000 claims abstract description 51
- 238000011161 development Methods 0.000 claims abstract description 35
- 230000006870 function Effects 0.000 claims description 37
- 239000000203 mixture Substances 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 13
- 238000013515 script Methods 0.000 claims description 12
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 238000007726 management method Methods 0.000 abstract description 34
- 238000013461 design Methods 0.000 abstract description 31
- 238000012356 Product development Methods 0.000 abstract description 11
- 230000018109 developmental process Effects 0.000 description 130
- 238000010586 diagram Methods 0.000 description 20
- 230000008569 process Effects 0.000 description 10
- 238000012986 modification Methods 0.000 description 9
- 230000004048 modification Effects 0.000 description 9
- 238000013068 supply chain management Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 8
- 238000004519 manufacturing process Methods 0.000 description 7
- 230000000875 corresponding effect Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000033772 system development Effects 0.000 description 2
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The application provides an enterprise management software development method, system, equipment and storage medium, wherein software components and module components contained in each software package of a product to be developed are planned and configured, and a system configuration path of each software component is planned; configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; creating a running period data dictionary when releasing and deploying the product; the running period data dictionary accords with the running format requirement of the deployment environment; and reading the running data dictionary and executing the program of the product to be developed. The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
Description
Technical Field
The application belongs to the technical field of software development, and particularly relates to an enterprise management software development method, system, equipment and storage medium.
Background
With the development of the technical field of computer network application, the field of production data increasingly requires software development technology for production. For example, in the enterprise resource management planning (ERP) and Supply Chain Management (SCM) application software development direction in the field of industrial software management, application development and adaptive updating of software components of software packages and related modules are required in the scenes of production, manufacture, sales and purchasing, financial management, warehouse logistics, quality service and the like, and the software components of the software packages related modules comprise components such as menus, forms, reports, program scripts and the like; the software packages and the components thereof in the production scenes need to adopt metadata to store, change and convert source information and object information in the system operation.
At present, with the increase and the complexity of enterprise management scenes, the current software development function design is single, and the function and concept design of the whole software development flow are incomplete; and the system is low in configurable degree during software development. Therefore, the software package developed by the current enterprise management software is too simple in system design and cannot complete application realization of complex business application scenes, or the system is complex in operation and unfriendly in use experience.
Disclosure of Invention
The enterprise management software development system, the enterprise management software development method, the enterprise management software development equipment and the storage medium provide two metadata of the application data dictionary and the runtime data dictionary, realize the enterprise management software development scheme of the whole product development life cycle from the product planning design to the release operation period, improve the adaptability of enterprise management scenes, meet the functional requirements of complex scenes and greatly improve the software development quality and development efficiency.
According to a first aspect of an embodiment of the present application, there is provided an enterprise management software development method, including: planning and configuring software components and module components contained in each software package of a product to be developed, and planning a system configuration path of each software component; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script;
configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; the application data dictionary, that is, the source information of the software components is stored in a database in the form of a database table;
when a product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, and a running period data dictionary is created; the running period data dictionary accords with the running format requirement of the deployment environment;
And reading the running data dictionary and executing the program of the product to be developed.
In some embodiments of the present application, planning and configuring versions and module compositions of software components included in each software package of a product to be developed includes:
planning and configuring software package attribute information and software component information of each software package of a product to be developed to obtain system configuration table definition information and software component configuration information; the system configuration table definition information includes table definition files for all software packages, and the software component configuration information includes system configuration paths for the software components.
In some embodiments of the present application, the software package attribute information includes software package version information, software package state information, and software package set information; planning and configuring software package attribute information and software component information of each software package of a product to be developed to obtain system configuration table definition information and software component configuration information, wherein the method comprises the following steps:
planning each software package and defining a plurality of modules included in the software package; the method specifically comprises the steps of defining a software package identifier and a description composition, and defining a module identifier, a description composition and a configuration state;
configuring version information, software package set information and software package state information of each software package to obtain definition information of a system configuration table; version information of the software package needs to specify software package set information, the version information comprises at least one of version number, release identifier and client identifier, and the software package state information comprises one of development state, release state and termination state; the software package set information comprises package set description information, table definition file storage position information and at least one piece of information whether the package set description information and the table definition file storage position information are stored in a shared memory or not;
The software package and version are specified, and the system storage path is configured for the software components in the system.
In some embodiments of the present application, configuring an application data dictionary, and performing program development of a product to be developed based on the application data dictionary includes:
configuring a plurality of component information in a product to be developed by using a development tool, wherein the component information is domain information, table information, prompt information, labels, menus, functional interfaces, forms or reports;
and writing a program script in an encoding mode to write business logic of the program.
In some embodiments of the present application, a development tool is used to configure component information in a product to be developed, where the component information includes at least one of domain information, table information, a message, a prompt message, a tag, a menu, a function interface, a form, and a report, and the method includes the following steps:
designating a current software package of a current version;
configuring component information of a current software package, wherein the component information is composed of at least one item of component identification, an expiration flag, component name description, data type and format information;
the developer can perform the operations of inquiring, adding, deleting and modifying the component information configured above, and the operation results are stored in a physical data table defined about the component.
In some embodiments of the present application, configuring a data type of component information of a current software package includes:
the configuration is carried out through a character string data type configuration item, including character string length, alignment mode, conversion type and internal format convention.
Configuring through a numerical data type configuration item, including a digit before decimal point, a digit after decimal point, a division factor and a rounding method;
date, enumeration and collection class data type configuration items are length;
the configuration is carried out through format information configuration items including display formats, legal characters, illegal characters and range definitions.
In some embodiments of the present application, creating a runtime data dictionary includes:
traversing application data dictionary data and dividing the application data dictionary data into three types of data, wherein the first type of data comprises at least one item of data in a report, a script and a file contained in the report; the second type of data comprises at least one item of data in a form and a menu; the third class of data includes at least one of basic data, user data, database information, shared memory, tables/fields, device data, task data, text data, developer data, messages, and questions;
And obtaining a running period data dictionary of a running format required by the deployment environment by compiling the first type data, directly exporting the second type data and directly converting the third type data.
In some embodiments of the present application, reading a runtime data dictionary, executing a program of a product to be developed, includes:
when executing menu objects, form objects, program objects and report objects in the program, accessing and reading a running period data dictionary according to the configuration information of the software components;
when table information and field information in the program are executed, accessing and reading the operation period data dictionary according to the definition information of the system configuration table;
and loading the read-accessed running data dictionary into the shared memory.
In some embodiments of the present application, after publishing the product to be developed, the method further includes:
modifying the software component of the product, and correspondingly storing and updating the application dictionary;
and converting the new running period data dictionary according to the updated application program dictionary, and reading and checking the new running period data dictionary so as to execute the updated program of the product to be developed.
According to a second aspect of embodiments of the present application, there is provided an enterprise management software development system comprising:
Planning and configuring module: the system comprises a software package, a software module and a system configuration path, wherein the software package is used for planning and configuring each software package of a product to be developed; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script;
configuring an application data dictionary module: the method comprises the steps of configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; the application data dictionary, that is, the source information of the software components is stored in a database in the form of a database table;
and the release deployment module: when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported and deployed, basic system data are installed in a table appointed in a physical database, and software components configured in a planning mode are deployed in a corresponding system catalog to create a running period data dictionary; the running period data dictionary accords with the running format requirement of the deployment environment;
program execution module: and the program is used for reading the running data dictionary and executing the product to be developed.
According to a third aspect of embodiments of the present application, there is provided an enterprise management software development device, including: a memory for storing executable instructions; and a processor coupled to the memory for executing the executable instructions to complete the enterprise management software development method.
According to a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium having a computer program stored thereon; the computer program is executed by the processor to implement an enterprise management software development method.
Adopting an enterprise management software development method, system, equipment and storage medium, and planning and configuring software components and module components contained in each software package of a product to be developed and planning a system configuration path of each software component; configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; when a product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, and a running period data dictionary is created; the running period data dictionary accords with the running format requirement of the deployment environment; and executing the program of the product to be developed by the read running data dictionary. The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
The method further solves the problems that the existing software development has single function design, the function and concept design of the whole software development flow are incomplete, the system is low in configurable degree during software development, and the software development requirement under the complicated trend of enterprise management scenes cannot be met.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
a schematic of steps of an enterprise management software development method according to an embodiment of the present application is shown in fig. 1;
a schematic of the steps of planning a software package to configure a product to be developed according to an embodiment of the present application is shown in fig. 2;
a simplified schematic diagram of a software package for planning configuration of a product to be developed according to an embodiment of the present application is shown in fig. 3;
an interface schematic of configuration package version information according to an embodiment of the present application is shown in fig. 4;
an interface schematic of configuration package collection information according to an embodiment of the present application is shown in fig. 5;
a hierarchical schematic of a table definition file according to an embodiment of the present application is shown in fig. 6.
A storage structure schematic of a storage path of a software component according to an embodiment of the present application is shown in fig. 7.
FIG. 8 illustrates a schematic diagram of steps for configuring an application data dictionary and program development according to an embodiment of the present application;
a schematic step of configuring component information in a product to be developed according to an embodiment of the present application is shown in fig. 9;
a schematic diagram of the steps of converting an application data dictionary into a runtime data dictionary according to an embodiment of the present application is shown in fig. 10;
a schematic flow diagram of converting an application data dictionary into a runtime data dictionary in accordance with an embodiment of the present application is shown in fig. 11;
a schematic flow chart of program operation according to an embodiment of the present application is shown in fig. 12;
an overall schematic diagram of an enterprise management software development method according to an embodiment of the present application is shown in fig. 13;
FIG. 14 is a schematic diagram of an enterprise management software development system according to an embodiment of the present application;
a schematic structural diagram of an enterprise management software development device according to an embodiment of the present application is shown in fig. 15.
Detailed Description
In this application, the software package and its components need metadata to store, change and transform source information and object information during system operation, which is oriented to the development direction of enterprise resource management planning (ERP) and Supply Chain Management (SCM) application software in the field of industrial software management. With the increase and the complexity of enterprise management scenes, the current software development function design is single, and the function and concept design of the whole software development flow are incomplete; and the system is low in configurable degree during software development. Therefore, the software package developed by the current enterprise management software is too simple in system design and cannot complete application realization of complex business application scenes, or the system is complex in operation and unfriendly in use experience.
Specifically, the existing software development technology using metadata management is divided into two types, namely, an online analysis processing OLAP type system which is oriented to the data analysis field, and an online transaction processing OLTP type system which is oriented to the metadata management.
The existing metadata management technology has the following problems in terms of application software development and system operation: for example, 1) the system architecture is not designed enough and lacks systematic thinking, and although some simple business management application programs can be developed, the development needs of large industrial software such as ERP, SCM and the like cannot be met. 2) The functional design is single, the conceptual design is incomplete, the metadata management is focused on the aspects of database table management, field mapping, system and application field definition and application interface metadata definition of a physical database and a data source layer, and the aspects of software component development such as menus, forms, reports, program scripts and the like are rarely related to other aspects in the application development process. 3) The method has the advantages of low production degree and narrow application range, and most of metadata management application ranges stay in some aspects of system development and system configuration stages, so that the method cannot meet the use of developers and system management staff in complex business scenes. 4) The system has low configurable degree, or the system design is too simple, the application realization of complex business application scenes can not be completed, or the system operation is complex, and the use experience is not friendly.
In contrast, the present application is mainly directed to online transaction OLTP type systems, and is mainly applied to enterprise resource management planning (ERP) and Supply Chain Management (SCM) application software development directions in the field of industrial software business management.
In addition, compared with the prior art, the technical scheme is complete in overall planning and architecture design, the product characteristics and the system characteristics of industrial software are fully considered, and metadata management and other system composition overall analysis are considered for software customization development.
The application data dictionary meets the development requirements of developers on all aspects of the software component, and the runtime data dictionary meets the operation requirements of complex services in the running process of system management personnel and service user programs during the running period of the system.
The system has wide application range, and the technical scheme covers all stages of system design, system installation, release and operation in the development life cycle, and software development technical scheme and design strategy corresponding to adaptability of each stage. Therefore, the software development technical scheme can meet the requirements of developing general service application programs and enterprise resource management planning (ERP) and Supply Chain Management (SCM) application software in the field of industrial software operation and management.
Other terms describe, the present application employs two types of metadata (data dictionaries), which are conceptually equivalent to metadata, an application data dictionary and a runtime data dictionary, respectively. There is one set of application data dictionaries for each set of published products, and one unique runtime data dictionary for each set of software packages in the published products.
The application data dictionary is also called a development data dictionary, and contains source information of all product software components, such as menus, forms, reports and program scripts. When the software component is modified and customized, the application data dictionary will be modified.
The runtime data dictionary (also called runtime data dictionary) contains object information of all product software components, and is used by the business system when executing the program, instead of the application data dictionary. The modification of the software component is stored in the application program dictionary, the system cannot recognize and immediately take effect at the moment, the application program dictionary can be converted into the runtime data dictionary through conversion operation, after conversion, the system can check the runtime data dictionary, and after the check is successful, the new modification of the software component can be embodied in the system, so that the safety and usability of the system are ensured to a certain extent, and the abnormality of online business caused by sudden update can be avoided.
The metadata management of the method comprises the whole product research and development life cycle from product planning and design to release operation, and plays a very important role in each stage.
Specifically, by adopting the enterprise management software development method, system, equipment and storage medium, the version and module composition of the software components contained in each software package of the product to be developed are planned and configured, and the system configuration path of each software component is planned; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script; configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; the application data dictionary, that is, the source information of the software components is stored in a database in the form of a database table; when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, basic system data are installed in a designated table in a physical database, and software components which are planned and configured are deployed in a corresponding system catalog to create a running period data dictionary; the running period data dictionary accords with the running format requirement of the deployment environment; and executing the program of the product to be developed by the read running data dictionary.
The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following detailed description of exemplary embodiments of the present application is given with reference to the accompanying drawings, and it is apparent that the described embodiments are only some of the embodiments of the present application and not exhaustive of all the embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.
Example 1
A schematic of the steps of an enterprise management software development method according to an embodiment of the present application is shown in fig. 1.
As shown in fig. 1, the enterprise management software development method according to the embodiment of the application includes the following steps:
s1: planning and configuring software components and compositions contained in each software package and module of the product to be developed, and planning a system configuration path of each composition; the composition includes at least one of a form, a menu, an object, a function, a program script, and a report script. S2, configuring an application data dictionary, and performing program development of a product to be developed based on the application data dictionary; the application data dictionary, i.e. the source information of the software components, is stored in the database in the form of a database table. S3: when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, basic system data are installed in a designated table in a physical database, and software components which are planned and configured are deployed in a corresponding system catalog to create a running period data dictionary; the runtime data dictionary meets the runtime format requirements of the deployment environment. S4: and reading the running data dictionary and executing the program of the product to be developed.
Based on the above, the embodiment of the application provides two metadata of the application data dictionary and the runtime data dictionary, realizes the enterprise management software development scheme of the whole product development life cycle from product planning design to release running period, improves the adaptability of enterprise management scenes, meets the functional requirements of complex scenes, and greatly improves the software development quality and development efficiency.
In other embodiments, the planning in S1 configures the version and module composition of the software component included in each software package of the product to be developed, including: planning and configuring software package attribute information and software component information of each software package of a product to be developed to obtain system configuration table definition information and software component configuration information; the system configuration table definition information includes table definition files of all software packages and modules thereof, and the software component configuration information includes system configuration paths of the software components.
A schematic of the steps of planning to configure a software package of a product to be developed according to an embodiment of the present application is shown in fig. 2.
In other embodiments, the package attribute information includes package version information, package state information, and package set information.
As shown in fig. 2, in S1, software package attribute information and software component information of each software package of a product to be developed are planned and configured to obtain system configuration table definition information and software component configuration information, including:
S11: planning each software package and defining a plurality of modules included in the software package; the method specifically comprises the steps of defining the identification and description composition of the software package, and defining the identification, description composition and configuration state of the module.
S12: configuring version information, software package set information and software package state information of each software package to obtain definition information of a system configuration table; version information of the software package needs to specify software package set information, the version information comprises at least one of version number, release identifier and client identifier, and the software package state information comprises one of development state, release state and termination state; the software package set information includes package set description information, table definition file storage location information, and at least one information of whether to store in the shared memory.
S13: the software package and version are specified, and the system storage path is configured for the software components in the system.
A simplified schematic diagram of a software package for planning configuration of a product to be developed according to an embodiment of the present application is shown in fig. 3.
To further describe S1, in the implementation, as shown in FIG. 3, a software package and a module are planned first; then configuring software package version information; next configuring package collection information; and finally, configuring the software component information.
Wherein, regarding planning software packages and modules, the definition of the software package includes a software package identifier and a description composition, and the software package identifier is generally composed of 2-bit english letters representing the name of the software package. The software package is composed of a plurality of modules, and the definition of the modules comprises a module identifier, a description and a configuration state, wherein the module identifier is generally composed of 3-bit English letters representing the software modules.
An interface schematic of configuring package version information according to an embodiment of the present application is shown in fig. 4.
Regarding the configuration package version information, the configuration package version information is received through a configuration package version information interface as shown in fig. 4. Software version information, software package state information and software package set information are set for each software package in the system composition. The version information includes version number, release identification, customer identification. Software package states are generally classified into states of development, release, termination, etc. The package version information needs to specify package collection information.
The system configuration manager designates version configuration information of a certain software package according to the above interface information.
An interface schematic of configuring package collection information according to an embodiment of the present application is shown in fig. 5.
Regarding configuration package set information, the package set configuration information is received through the configuration package set information interface of fig. 5. As shown in fig. 5, the system configuration manager specifies configuration information of a certain software package set according to the above interface information, and other software package sets in the system can be maintained according to the above information.
The configuration of the software package set information generally requires that the designated package set be configured with information such as description information, table definition file storage location information, and whether or not to store a table definition in the shared memory.
A hierarchical schematic of a table definition file according to an embodiment of the present application is shown in fig. 6.
As shown in FIG. 6, the hierarchy of table definition files includes table definition files for all software packages and their associated modules in the set of software packages.
The generic system tool package exists as a separate set of packages, with the generic set of packages typically containing only business layer application packages.
Regarding the last configuration software component information, for a specified software package and version, a system storage path is configured for a software component (form, menu, object, function, program script, report script) in the system, and a storage structure of the storage path of the software component is shown in fig. 7.
A schematic diagram of the steps for configuring an application data dictionary and program development according to an embodiment of the present application is shown in fig. 8.
Next, as shown in fig. 8, the application data dictionary is configured through S2, and program development of the product to be developed is performed based on the application data dictionary, specifically including: s21: firstly, configuring a plurality of software component information in a product to be developed by using a development tool, wherein the software component information is domain information, table information, prompt information, labels, menus, function interfaces, forms or reports. S22: and writing a program script in a coding mode to write service logic of the program.
In the process of implementing S2 to carry out software development test, a mode of configuring an application data dictionary firstly and then coding when the business logic program is required to be written is adopted to write a program script. The process is different from the general system development which is completed through coding, and the method has the advantages of small coding program quantity, good software development effect and high speed.
A schematic step of configuring component information in a product to be developed according to an embodiment of the present application is shown in fig. 9.
As shown in fig. 9, wherein S21 configures component information in a product to be developed using a development tool, comprising the steps of:
S211: designating a current software package of a current version;
s212: configuring component information of a current software package, wherein the component information is composed of at least one item of component identification, an expiration flag, component name description, data type and format information;
s213: the developer can perform the operations of inquiring, adding, deleting and modifying the component information configured above, and the operation results are stored in a physical data table defined about the component.
The step S212 is to configure the data type of the component information of the current software package, which includes configuring by a string data type configuration item including string length, alignment mode, conversion type and internal format convention. Configuring through a numerical data type configuration item, including a digit before decimal point, a digit after decimal point, a division factor and a rounding method; date, enumeration and collection class data type configuration items are length; the configuration is carried out through format information configuration items including display formats, legal characters, illegal characters and range definitions.
Further describing step S2, regarding configuration of an application data dictionary and application development, the embodiment of the present application differs from the development of a general application development system through coding in that the application data dictionary is configured before service logic writing. Specifically, domains, tables, messages, prompts, labels, menus, functional interfaces, forms and reports in the system are configured by using the development tools. Only when the program script needs to be written, the program script is finished by a developer in a coding mode. The application data dictionary is configured by the developer and then related source information is stored in the form of a database table.
By way of illustration, the configuration of a domain-type application data dictionary, other types of data dictionaries are substantially similar in configuration procedures and methods, except for the configuration items and associated specific operations.
First, prior to configuring a domain, it is necessary to specify the current version of the software package so that domain modifications only affect the current version and other version domain definitions are not affected.
Then, the configuration domain information comprises domain name identification, an expiration flag, domain name description, data type information and format information, wherein the data type configuration information comprises a character string data type configuration item comprising a character string length, an alignment mode, a conversion type and an internal format convention. The numerical data type configuration items comprise a digit before a decimal point, a digit after the decimal point, a division factor and a rounding method. Date, enumeration, and collection class data type configuration items are lengths. The format information configuration items comprise display formats, legal characters, illegal characters and range definitions.
Next, the developer may perform operations such as querying, adding, deleting, modifying, etc. on the above domain configuration information, and the operation result may be stored in a physical data table related to the domain definition.
In addition to performing the above data operation on the domain information, the system may perform a conversion operation into a run-time operation, and after the conversion operation is performed successfully, the domain information is accessed again, so that it can be seen that the domain information has been updated, and meanwhile, the domain definition information in the system table definition storage is synchronously updated.
A schematic diagram of the steps of converting an application data dictionary into a runtime data dictionary according to an embodiment of the present application is shown in fig. 10. A schematic flow diagram of converting an application data dictionary into a runtime data dictionary according to an embodiment of the present application is shown in fig. 11.
As shown in fig. 10, the process of converting an application data dictionary into a runtime data dictionary can be seen directly in connection with fig. 11.
Converting the application data dictionary into a runtime data dictionary in S3 includes:
s31: firstly, traversing application data dictionary data, and dividing the application data dictionary data into three types of data according to different data properties, wherein the first type of data comprises at least one item of data in a report, a script and a file contained in the report; the second type of data comprises at least one item of data in a form and a menu; the third class of data includes at least one of basic data, user data, database information, shared memory, tables/fields, device data, task data, text data, developer data, messages, and questions;
S32: and then obtaining a running period data dictionary of a running format required by the deployment environment by compiling the first type data, directly exporting the second type data and directly converting the third type data.
And S3, when the system is installed, deployed and configured in an initialized mode, creating a data dictionary in the running process is carried out. When in installation and deployment, the software package is imported according to the software package of the selected version, the software package is deployed to a designated installation path after being imported, and basic system data is installed in a designated database; then, the system creates a running data dictionary, and the running data dictionary information such as data definition, menu, form, program, report and the like is stored in a created running data dictionary storage table and a table definition file, wherein the running data dictionary storage table is a special table and stores the running configuration information of all software modules in the system.
Next, in S4, the running data dictionary is read, and the program of the product to be developed is executed, including the following two parts: when executing menu objects, form objects, program objects and report objects in the program, accessing and reading a running period data dictionary according to the configuration information of the software components; when table information and field information in the program are executed, accessing and reading the operation period data dictionary according to the definition information of the system configuration table; and simultaneously, loading the read-accessed running data dictionary into the shared memory.
In other embodiments, after the S3 release deployment of the product to be developed, the method further comprises the steps of:
1. modifying the software component of the product, and correspondingly storing and updating the application dictionary;
2. and converting the new running period data dictionary according to the updated application program dictionary, and reading and checking the new running period data dictionary so as to execute the updated program of the product to be developed.
A schematic flow chart of program operation according to an embodiment of the present application is shown in fig. 12.
To further illustrate the step of reading the runtime data dictionary in the specified table in S4, a program of the product to be developed is executed. As shown in fig. 12, the system reads the runtime data dictionary instead of the application dictionary when the program is executed.
In the initial stage of application program execution, the system can perform function execution authority check, and the current software package, the application program module function and the system authority allocation information can be determined by accessing the runtime data dictionary, so that whether the application program accessed by the user is legal or not is determined. The information of the data dictionary in the operation is stored in the storage table and the table definition file of the data dictionary in the operation, so that a plurality of system tables are not required to be searched in a correlated way to obtain the information in the operation, and the processing can improve the system access performance.
When the menu object, the form object, the program object and the report object are executed by the application program, the running period data dictionary is accessed, and the running period data dictionary is determined by a software component dump file configured by the system and configuration file information thereof.
When the application program executes the accessed table information and field information, the operation period data dictionary is read according to the system configuration table definition information, and in order to improve the system access performance, the data dictionary information is loaded into the shared memory when executing.
In summary, by adopting the enterprise management software development method of the embodiment, the version and the module composition of the software components contained in each software package of the product to be developed are planned and configured, and the system configuration path of each software component is planned; configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; when a product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, and a running period data dictionary is created; the running period data dictionary accords with the running format requirement of the deployment environment; and executing the program of the product to be developed by the read running data dictionary. The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
The method further solves the problems that the existing software development has single function design, the function and concept design of the whole software development flow are incomplete, the system is low in configurable degree during software development, and the software development requirement under the complicated trend of enterprise management scenes cannot be met.
An overall schematic diagram of an enterprise management software development method according to an embodiment of the present application is shown in fig. 13.
As shown in FIG. 13, the principles of the enterprise management software development scheme of embodiments of the present application are further described below. In the application development and system operation integrated technical scheme based on metadata management in the embodiment of the application, metadata management comprises the whole product development life cycle from product planning and design to release operation. The main generalization includes the following four phases:
and in the planning and designing stage of the product, determining the product software package and the product module composition and the product development roadmap containing the version of the product to be distributed. At this stage, the version, composition (typically including forms, menus, objects, functions, program scripts, report scripts) and system configuration paths for each of the components contained by each of the software packages and modules are planned.
In the second stage, in the product development and test stage, the developer maintains domains, tables, messages, prompts, labels, configures or develops menus, function interfaces, forms, reports, writes and tests program scripts, functions/methods and the like by using the development tool, and in this stage, the application development is stored in the system tool table, for example, a domain information table stores domain information maintained by the developer, a table definition stores table definition information maintained by the developer, field information maintained in the table definition is stored in table field information, and the software components and the data definition are all processed in this way.
In the third stage, in the product release and deployment stage, a developer generates a release program package according to the definition of the formulated version and software package set, the software package, the module and the software component information to be released according to the appointed rule, such as according to the software package, the version, the update state, the software component and the language, the program package contains the data dictionary information, in the deployment process, the software to be released is deployed into the appointed server system through the execution of the customized installation program, in the execution process, the installation program is executed to create a running data dictionary, and the program software component of the developed stage is deployed into the appointed system catalog according to the data dictionary information.
And step four, during the running of the system, the data dictionary is loaded into the shared memory during the running of the system service, and the content input by the user is checked in the program executing process, so that the input of the user is confirmed to be the content meeting the system requirement.
The system can check the data dictionary in the operation period after conversion, and can embody the new modification of the software component in the system after the check is successful, so that the design ensures the safety and usability of the system to a certain extent, and the abnormality of online business can not occur due to abrupt updating.
Example 2
The present embodiment provides an enterprise management software development system, and for details not disclosed in the enterprise management software development system of the present embodiment, please refer to the specific implementation content of the enterprise management software development method in other embodiments.
A schematic of the architecture of an enterprise management software development system according to an embodiment of the present application is shown in fig. 14.
As shown in fig. 14, the enterprise management software development system includes a planning configuration module 10, a configuration application data dictionary module 20, a release deployment module 30, and a program execution module 40.
In particular, the method comprises the steps of,
planning configuration module 10: the system comprises a software package, a software module and a system configuration path, wherein the software package is used for planning and configuring the version and the module composition of software components contained in each software package of a product to be developed; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script;
configuration application data dictionary module 20: the method comprises the steps of configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; the application data dictionary, that is, the source information of the software components is stored in a physical database in the form of a database table;
Release deployment module 30: when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported and deployed, basic system data are installed in a table appointed in a physical database, and software components configured in a planning mode are deployed in a corresponding system catalog to create a running period data dictionary; the running period data dictionary accords with the running format requirement of the deployment environment;
program execution module 40: and the program is used for reading the running data dictionary and executing the product to be developed.
Using the enterprise management software development system, planning and configuring each software package of the product to be developed and the version and composition of the software components contained in the module through the planning and configuration module 10; the configuration application data dictionary module 20 configures an application data dictionary, and performs program development of a product to be developed based on the application data dictionary; the source information of the software components is stored in the application data dictionary in the form of a database table; the release and deployment module 30 is used for exporting software packages of products when releasing and deploying the products, making a system installation program, executing the system installation program, importing the released product software packages and each software component, installing basic system data into a designated table in a physical database, deploying the software components of planning configuration into a corresponding system catalog, and creating a running period data dictionary; the runtime data dictionary meets the runtime format requirements of the deployment environment. The program execution module 40 reads the run-time data dictionary in the specified table, and executes the program of the product to be developed.
The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
The method further solves the problems that the existing software development has single function design, the function and concept design of the whole software development flow are incomplete, the system is low in configurable degree during software development, and the software development requirement under the complicated trend of enterprise management scenes cannot be met.
Example 3
The present embodiment provides an enterprise management software development device, and for details not disclosed in the enterprise management software development device of the present embodiment, please refer to specific implementation contents of the enterprise management software development method or system in other embodiments.
A schematic structural diagram of an enterprise management software development device 400 or enterprise management software development device according to an embodiment of the present application is shown in fig. 15.
As shown in fig. 15, the enterprise management software development device 400 or the enterprise management software development device includes:
memory 402: for storing executable instructions; and
Processor 401 is operative to interface with memory 402 to execute executable instructions to perform an enterprise management software development method or enterprise management software development method.
It will be appreciated by those skilled in the art that schematic diagram 14 is merely an example of enterprise management software development device 400 or enterprise management software development device and is not intended to limit enterprise management software development device 400 or enterprise management software development device, and may include more or fewer components than illustrated, or may combine certain components, or different components, e.g., enterprise management software development device 400 may also include input and output devices, network access devices, buses, etc.
The processor 401 (Central Processing Unit, CPU) may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor 401 may be any conventional processor or the like, and the processor 401 is a control center of the enterprise management software development device 400, and various interfaces and lines are used to connect various portions of the entire enterprise management software development device 400.
Memory 402 may be used to store computer readable instructions, and processor 401 may implement various functions of enterprise management software development device 400 by executing or executing the computer readable instructions or modules stored in memory 402 and invoking data stored in memory 402. The memory 402 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like; the storage data area may store data created according to the use of the enterprise management software development device 400, etc. In addition, the Memory 402 may include a hard disk, memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), at least one disk storage device, a Flash Memory device, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or other non-volatile/volatile storage device.
The modules integrated by enterprise management software development device 400 may be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product. Based on such understanding, the present invention may implement all or part of the flow of the method of the above-described embodiments, or may be implemented by means of computer readable instructions to instruct related hardware, where the computer readable instructions may be stored in a computer readable storage medium, where the computer readable instructions, when executed by a processor, implement the steps of the method embodiments described above.
Example 5
The present embodiment provides a computer-readable storage medium having a computer program stored thereon; the computer program is executed by the processor to implement the enterprise management software development method in other embodiments.
The enterprise management software development device and the storage medium of the embodiment of the application program the version and the module composition of the software components contained in each software package of the product to be developed, and program the system configuration path of each software component; configuring an application data dictionary, and developing a program of a product to be developed based on the application data dictionary; when a product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, and a running period data dictionary is created; the running period data dictionary accords with the running format requirement of the deployment environment; and executing the program of the product to be developed by the read running data dictionary. The application data dictionary and the runtime data dictionary are used for realizing the enterprise management software development scheme of the whole product development life cycle from product planning design to release operation, improving the adaptability of enterprise management scenes, meeting the functional requirements of complex scenes and greatly improving the software development quality and development efficiency.
The method further solves the problems that the existing software development has single function design, the function and concept design of the whole software development flow are incomplete, the system is low in configurable degree during software development, and the software development requirement under the complicated trend of enterprise management scenes cannot be met.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may 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, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the invention. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.
Claims (8)
1. A method of enterprise management software development, comprising:
planning and configuring software components and module components contained in each software package of a product to be developed, and planning a system configuration path of each software component; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script;
configuring an application data dictionary, and performing program development of a product to be developed based on the application data dictionary; the application data dictionary, namely source information of the software component is stored in a database in the form of a database table;
when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported, basic system data are installed in a designated table in a physical database, and software components which are planned and configured are deployed in a corresponding system catalog to create a running period data dictionary; the operation period data dictionary accords with the operation format requirement of the deployment environment;
reading the running period data dictionary and executing the program of the product to be developed;
the configuration application data dictionary and program development of the product to be developed based on the application data dictionary comprise: configuring component information in a product to be developed by using a development tool, wherein the component information is domain information, table information, prompt information, labels, menus, function interfaces, forms or reports; programming a program script in a coding mode to program business logic programming;
The method comprises the following steps of configuring component information in a product to be developed by using a development tool, wherein the component information comprises at least one of domain information, table information, prompt information, labels, menus, function interfaces, forms and reports, and the method comprises the following steps:
designating a current software package of a current version;
configuring component information of a current software package, wherein the component information consists of at least one item of component identification, an expiration flag, component name description, data type and format information;
the developer performs the operations of inquiring, adding, deleting and modifying the component information configured above, and the operation result is stored in a physical data table defined about the component;
wherein the creating of the runtime data dictionary comprises:
traversing the application data dictionary data and dividing the application data dictionary data into three types of data, wherein the first type of data comprises at least one item of data in a report, a script and a file contained in the report; the second type of data comprises at least one item of data in a form and a menu; the third class of data includes at least one of basic data, user data, database information, shared memory, tables/fields, device data, task data, text data, developer data, messages, and questions;
Obtaining a running period data dictionary of a running format required by a deployment environment by compiling the first type data, directly deriving the second type data and directly converting the third type data;
wherein the reading the operation period data dictionary, executing the program of the product to be developed, comprises:
when executing menu objects, form objects, program objects and report objects in the program, accessing and reading the running period data dictionary according to the configuration information of the software components;
when table information and field information in the program are executed, accessing and reading the operation period data dictionary according to system configuration table definition information;
and loading the read-accessed running data dictionary into the shared memory.
2. The enterprise management software development method of claim 1, wherein the planning configuration comprises software components and module compositions contained in each software package of the product to be developed, comprising:
planning and configuring software package attribute information and software component information of each software package of a product to be developed to obtain system configuration table definition information and software component configuration information; the system configuration table definition information includes table definition files of all software packages, and the software component configuration information includes system configuration paths of the software components.
3. The enterprise management software development method of claim 2, wherein the software package attribute information comprises software package version information, software package status information, and software package collection information; the software package attribute information and the software component information of each software package of the product to be developed are planned and configured to obtain system configuration table definition information and software component configuration information, and the method comprises the following steps:
planning each software package and defining a plurality of modules included in the software package; the method specifically comprises the steps of defining a software package identifier and a description composition, and defining a module identifier, a description composition and a configuration state;
configuring version information, software package set information and software package state information of each software package to obtain definition information of a system configuration table; the version information of the software package needs to specify software package set information, the version information comprises at least one of version number, release identifier and client identifier, and the software package state information comprises one of development state, release state and termination state; the software package set information comprises package set description information, table definition file storage position information and at least one piece of information whether the information is stored in a shared memory or not;
The software package and version are specified, and the system storage path is configured for the software components in the system.
4. The method of claim 1, wherein the configuring the data type of the component information of the current software package comprises:
configuring through a character string data type configuration item, including character string length, an alignment mode, a conversion type and an internal format convention;
configuring through a numerical data type configuration item, including a digit before decimal point, a digit after decimal point, a division factor and a rounding method;
date, enumeration and collection class data type configuration items are length;
the configuration is carried out through format information configuration items including display formats, legal characters, illegal characters and range definitions.
5. The enterprise management software development method of any one of claims 1-4, wherein after publishing the product to be developed, the method further comprises:
modifying the software component of the product, and correspondingly storing and updating the application dictionary;
and converting the new running period data dictionary according to the updated application program dictionary, and reading and checking the new running period data dictionary so as to execute the updated program of the product to be developed.
6. An enterprise management software development system for performing the enterprise management software development method of any one of claims 1-5, comprising:
planning and configuring module: the system comprises a software package, a software module and a system configuration path, wherein the software package is used for planning and configuring each software package of a product to be developed; the software component comprises at least one of a form, a menu, an object, a function, a program script and a report script;
configuring an application data dictionary module: the method comprises the steps of configuring an application data dictionary, and performing program development of a product to be developed based on the application data dictionary; the application data dictionary, namely source information of the software component is stored in a database in the form of a database table; publishing deployment module
And the release deployment module: when the product is released and deployed, a software package of the product is exported, a system installation program is manufactured, the system installation program is executed, the software package of the released product and each software component are imported and deployed, basic system data are installed in a table appointed in a physical database, and software components configured in a planning mode are deployed in a corresponding system catalog to create a running period data dictionary; the operation period data dictionary accords with the operation format requirement of the deployment environment;
Program execution module: and the program is used for reading the running data dictionary and executing the product to be developed.
7. An enterprise management software development device, comprising:
a memory for storing executable instructions; and
a processor coupled to the memory for executing executable instructions to perform the method of any of claims 1-5.
8. A computer-readable storage medium, characterized in that a computer program is stored thereon; computer program to be executed by a processor to implement the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310988192.0A CN117234466B (en) | 2023-08-07 | 2023-08-07 | Enterprise management software development method, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310988192.0A CN117234466B (en) | 2023-08-07 | 2023-08-07 | Enterprise management software development method, system, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117234466A CN117234466A (en) | 2023-12-15 |
| CN117234466B true CN117234466B (en) | 2024-02-23 |
Family
ID=89086931
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310988192.0A Active CN117234466B (en) | 2023-08-07 | 2023-08-07 | Enterprise management software development method, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117234466B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246503A (en) * | 2012-02-10 | 2013-08-14 | 上海乘亿信息科技有限公司 | Application development framework for enterprise management software |
| CN108008940A (en) * | 2017-12-29 | 2018-05-08 | 成都邦永科技有限公司 | A kind of software customized platform of service management and its method for customizing |
| CN111414172A (en) * | 2020-03-18 | 2020-07-14 | 时时同云科技(成都)有限责任公司 | Automatic deployment and release system and method for application software |
| CN112433701A (en) * | 2020-12-01 | 2021-03-02 | 上海数设科技有限公司 | Industrial software development project implementation flow, content and code generation method and device |
| CN113127442A (en) * | 2020-01-10 | 2021-07-16 | 马上消费金融股份有限公司 | Visualization method and device of data model and storage medium |
| CN113515499A (en) * | 2021-03-25 | 2021-10-19 | 中国雄安集团数字城市科技有限公司 | Database service method and system |
| CN114089959A (en) * | 2020-08-24 | 2022-02-25 | 扬州旭尧信息技术有限公司 | Enterprise management software rapid development system |
| CN114253515A (en) * | 2021-11-19 | 2022-03-29 | 苏州趣谷科技有限公司 | Low-code development platform for quickly constructing manufacturing type enterprise management software |
| CN114490015A (en) * | 2020-11-13 | 2022-05-13 | 华为技术有限公司 | Method and device for configuring computing mode and computing equipment |
| CN114490594A (en) * | 2022-02-16 | 2022-05-13 | 中银金融科技有限公司 | Database management method and device, electronic equipment and computer storage medium |
| CN114881575A (en) * | 2022-05-31 | 2022-08-09 | 南京工业大学 | Rapid development framework and development method for inventory management software of process manufacturing enterprise |
| CN115438026A (en) * | 2022-09-15 | 2022-12-06 | 中国建设银行股份有限公司 | Database scanning method, device, equipment, storage medium and product |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060179065A1 (en) * | 2005-02-04 | 2006-08-10 | Xu Jordan J | Matrix oriented application framework with interchangeable data source mapping and user interface |
| US20170124464A1 (en) * | 2015-10-28 | 2017-05-04 | Fractal Industries, Inc. | Rapid predictive analysis of very large data sets using the distributed computational graph |
| US11531947B2 (en) * | 2018-10-19 | 2022-12-20 | Oracle International Corporation | System and method for software development including column-based process editor |
| US20200234241A1 (en) * | 2019-01-18 | 2020-07-23 | GalaxE.Solutions, Inc. | Systems and Methods for Automated SDLC, Portfolio, Program and Project Management |
| WO2021019302A1 (en) * | 2019-07-31 | 2021-02-04 | JFrog Ltd. | Metadata storage architecture and data aggregation |
-
2023
- 2023-08-07 CN CN202310988192.0A patent/CN117234466B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246503A (en) * | 2012-02-10 | 2013-08-14 | 上海乘亿信息科技有限公司 | Application development framework for enterprise management software |
| CN108008940A (en) * | 2017-12-29 | 2018-05-08 | 成都邦永科技有限公司 | A kind of software customized platform of service management and its method for customizing |
| CN113127442A (en) * | 2020-01-10 | 2021-07-16 | 马上消费金融股份有限公司 | Visualization method and device of data model and storage medium |
| CN111414172A (en) * | 2020-03-18 | 2020-07-14 | 时时同云科技(成都)有限责任公司 | Automatic deployment and release system and method for application software |
| CN114089959A (en) * | 2020-08-24 | 2022-02-25 | 扬州旭尧信息技术有限公司 | Enterprise management software rapid development system |
| CN114490015A (en) * | 2020-11-13 | 2022-05-13 | 华为技术有限公司 | Method and device for configuring computing mode and computing equipment |
| CN112433701A (en) * | 2020-12-01 | 2021-03-02 | 上海数设科技有限公司 | Industrial software development project implementation flow, content and code generation method and device |
| CN113515499A (en) * | 2021-03-25 | 2021-10-19 | 中国雄安集团数字城市科技有限公司 | Database service method and system |
| CN114253515A (en) * | 2021-11-19 | 2022-03-29 | 苏州趣谷科技有限公司 | Low-code development platform for quickly constructing manufacturing type enterprise management software |
| CN114490594A (en) * | 2022-02-16 | 2022-05-13 | 中银金融科技有限公司 | Database management method and device, electronic equipment and computer storage medium |
| CN114881575A (en) * | 2022-05-31 | 2022-08-09 | 南京工业大学 | Rapid development framework and development method for inventory management software of process manufacturing enterprise |
| CN115438026A (en) * | 2022-09-15 | 2022-12-06 | 中国建设银行股份有限公司 | Database scanning method, device, equipment, storage medium and product |
Non-Patent Citations (3)
| Title |
|---|
| "Database Evolution for Software Product Lines";Helfert, M.等;《4th International Conference on Data Management Technologies and Applications》;20160211;全文 * |
| "中国中小软件企业软件开发项目管理的应用分析";吕清瑶;《中国优秀博硕士学位论文全文数据库 信息科技辑》;20070615;全文 * |
| "互联网企业软件开发项目人力资源配置优化研究";梅翔;《中国优秀博硕士学位论文全文数据库 信息科技辑》;20190115;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117234466A (en) | 2023-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11392393B2 (en) | Application runtime configuration using design time artifacts | |
| US11526656B2 (en) | Logical, recursive definition of data transformations | |
| JP5049280B2 (en) | Extensible XML format and object model for localization data | |
| RU2445682C2 (en) | Graph-oriented programming and implementation based on manufacturers | |
| US8392873B2 (en) | Methods and apparatus for implementing model-based software solution development and integrated change management | |
| TWI556170B (en) | Projecting native application programming interfaces of an operating system into other programming languages (2) | |
| US9037595B2 (en) | Creating graphical models representing control flow of a program manipulating data resources | |
| US7861222B2 (en) | Discoscript: a simplified distributed computing scripting language | |
| CN111399853A (en) | Templated deployment method of machine learning model and custom operator | |
| US20080235661A1 (en) | System and method for using annotations to automatically generate a framework for a custom javaserver faces (jsf) component | |
| US11288062B2 (en) | Automatic source code refactoring | |
| CN116755669A (en) | Low code development method and tool based on DSL language operation model | |
| JP4806158B2 (en) | System and method for declaratively defining and using subclasses in markup | |
| US10839124B1 (en) | Interactive compilation of software to a hardware language to satisfy formal verification constraints | |
| JP7373587B2 (en) | Service management in DBMS | |
| US20160283291A1 (en) | Facilitating communication between software components that use middleware | |
| US11977473B2 (en) | Providing a pseudo language for manipulating complex variables of an orchestration flow | |
| CN117234466B (en) | Enterprise management software development method, system, equipment and storage medium | |
| KR100985192B1 (en) | System for developing software | |
| CN113504904A (en) | User-defined function implementation method and device, computer equipment and storage medium | |
| US6782523B2 (en) | Parallel configurable IP design methodology | |
| US11941386B2 (en) | Flexible provision of multi-application content | |
| CN118295638A (en) | Block chain service generation method and related equipment | |
| CN116881218A (en) | Meta model, processing method and device of model and computing device cluster | |
| KR20220112977A (en) | System and method for user interface management of AUTOSAR setting tool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |