CN114153425A

CN114153425A - Application modeling system and modeling method thereof

Info

Publication number: CN114153425A
Application number: CN202111450720.4A
Authority: CN
Inventors: 周剑
Original assignee: Ping An Property and Casualty Insurance Company of China Ltd
Current assignee: Ping An Property and Casualty Insurance Company of China Ltd
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2022-03-08

Abstract

The application is applicable to the technical field of software programs, and provides an application program modeling system and a modeling method thereof. Therefore, the modeling process of the application program is unified, data distortion is reduced, the development difficulty of the application program is reduced, and modification and adjustment of secondary development of the application program are facilitated.

Description

Application modeling system and modeling method thereof

Technical Field

The application relates to the technical field of software programs, in particular to an application program modeling system and a modeling method thereof.

Background

With the development of computer technology and the continuous progress of application programs and web page technologies, the functions of application program items are more and more, and the application program items are more and more powerful. One application program is developed from design to completion on line, and different analysis, design and development tools are required to be adopted for respective development aiming at different functions. At present, in a traditional application development process, each link is modeled by different modes, different tools and different environments, for example, developers continuously switch among different systems, different applications and different development tools, and documents and conclusions generated by different tools are converted, and the like. The modeling process is not convenient for developers to modify and adjust the application program because the flow is not uniform and systematic, and intermediate data information among modeling links is easy to be distorted due to different groups or different developers, so that the development difficulty of the application program is increased.

Disclosure of Invention

In view of this, the embodiment of the present application provides an application modeling system and a modeling method thereof, which can unify an application modeling process, avoid distortion of intermediate data information between modeling links due to different groups or different developers in the application modeling process, reduce development difficulty of an application, and facilitate modification and adjustment of secondary development of the application.

A first aspect of an embodiment of the present application provides an application modeling system, including a user manager, a role manager, a menu manager, an object manager, and a process manager, where:

the user manager is used for storing user basic information and marking roles for target users participating in the application modeling process in the application modeling system;

the role manager is used for providing a role creation window for the application program modeling process and configuring the operation authority of the target user in the application program modeling system according to the role label obtained by the target user through role labeling processing;

the menu manager is used for providing a menu creation window for the application program modeling process and generating a function menu applied to the application program according to the menu information input by the target user in the menu creation window;

the object manager is used for providing an object creation window for the application program modeling process and generating an object database table applied to the application program according to the object information input by the target user in the object creation window;

the process manager is used for providing a process creation window for the application program modeling process, and generating an execution flow chart applied to the application program according to process information input by the target user in the process creation window, wherein the execution flow chart is used for controlling an execution flow of functions in the application program.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the user manager includes a user role associating unit, where the user role associating unit is configured to:

calling a role manager, and acquiring a plurality of role labels established based on a modeling process of a target application program from the role manager;

selecting a target role label matched with the target user from the plurality of role labels according to the basic information of the target user, and labeling the target user by adopting the target role label so as to enable the target user to associate roles.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the role manager further includes:

the new user information unit is used for displaying an information acquisition table on an interactive interface and indicating a login user to fill in new user information in the information acquisition table so as to generate a first basic information table of the new user based on the information acquisition table and store the first basic information table in a database built in the user manager; and/or

A delete user information unit, configured to retrieve a second basic information table corresponding to a specified user from a database built in the user manager, and delete the second basic information table; and/or

And the user information modifying unit is used for calling a third basic information table corresponding to a specified user from a database built in the user manager, displaying the third basic information table in an interactive interface, indicating a login user to modify the third basic information table, and storing the modified third basic information table in the database built in the user manager.

With reference to the first aspect, in a third possible implementation manner of the first aspect, the role manager includes a role authorization unit, where the role authorization unit is configured to:

and configuring the operation authority of the role label in the target application program modeling process according to the application program content range matched with the role label, wherein the application program content range matched with the role label is determined by the login user when the target application program modeling process is subjected to role division.

With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the menu manager includes:

the menu creation task configuration unit is used for identifying the role label correspondingly labeled by the target user and configuring a menu creation task for the target user according to the application program content range matched with the role label;

the menu view template generating unit is used for calling a template file configuration page, acquiring template coding data input by the target user based on the template file configuration page and generating a menu view template according to the template coding data input by the target user;

and the menu view template application unit is used for identifying a menu view template selection instruction initiated by the target user and applying the menu view template selected in the menu view template selection instruction to the function menu generated by the target user in the menu creation window.

With reference to the first aspect or the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the menu manager further includes:

the menu newly-built unit is used for calling a menu newly-built page, acquiring directory item information input by the target user based on the menu newly-built page, generating a newly-built local function menu according to the input directory item information, and storing the newly-built local function menu in a database built in the menu manager; and/or

The menu modification unit is used for calling a local function menu related to the ID information of the target user from a database built in the menu manager, and displaying the local function menu on an interactive interface so as to indicate the target user to modify the local function menu; and/or

And the menu deleting unit is used for calling a local function menu related to the ID information of the target user from a database built in the menu manager, and displaying the local function menu in an interactive interface so as to indicate whether the target user deletes the local function menu.

With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the object manager is further configured to perform read-only setting on an object attribute in the generated object database table, perform primary key setting on an object attribute in the generated object database table, and/or create an index for the generated object database table.

With reference to the first aspect, in a seventh possible implementation manner of the first aspect, the process manager includes:

the flow chart drawing unit is used for generating a corresponding flow chart code file according to the flow components drawn by the target user in the flow chart drawing board integrated by the flow manager and the incidence relation among the flow components;

and the flow code generating unit is used for identifying the logic codes which are input in each flow component of the flow chart by the target user and generating a flow chart running code file matched with the flow chart according to the incidence relation among the flow components.

A second aspect of an embodiment of the present application provides an application modeling method, which is applied to the application modeling system according to any one of the first aspect, and includes:

according to operation information executed by a login user in the application program modeling system, a user manager is adopted to mark a corresponding role label for a target user, wherein the role label is obtained by dividing the role of a target application program project through the role manager;

configuring the operation authority of the target user in a menu manager, an object manager and/or a process manager according to the role label;

and identifying effective operation executed by the target user in the menu manager, the object manager and/or the process manager based on the operation authority, and performing application program modeling processing aiming at the target application program project according to the effective operation.

A third aspect of embodiments of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the electronic device, where the processor implements the steps of the application modeling method provided in the second aspect when executing the computer program.

A fourth aspect of embodiments of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the application modeling method provided by the second aspect.

The application modeling system and the application modeling method provided by the embodiment of the application have the following beneficial effects:

unifying an application modeling process through a user manager, a role manager, a menu manager, an object manager and a process manager, wherein the user manager stores basic user information and performs role marking processing on users participating in the application modeling process in the application modeling system, the role manager configures operation authority of the users in the application modeling system according to role labels obtained by the users through the role marking processing, the menu manager generates a function menu applied to the application according to the entered menu information, the object manager generates an object database table applied to the application according to the entered object information, and the process manager generates an execution flow chart applied to the application according to the entered process information, so that the complete modeling process of the application in the application modeling system is realized, the problem that intermediate data information distortion exists among modeling links due to different groups or different developers in the application program modeling process is solved, the development difficulty of the application program is reduced, and meanwhile, the application program is convenient to modify and adjust by the developers during secondary development.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

FIG. 1 is a schematic diagram of an infrastructure of an application modeling system according to an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a user manager in an application modeling system according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a role manager in an application modeling system according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a menu manager provided in the application modeling system according to an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a process manager in the application modeling system according to an embodiment of the present application;

FIG. 6 is a schematic basic flowchart of an application modeling method according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a basic structure of an application modeling apparatus according to an embodiment of the present application;

fig. 8 is a block diagram of a basic structure of an electronic device according to an embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The embodiment of the application program modeling system is provided for developers and testers to use, is used for executing all modeling steps in the application program modeling process, and generates an application program containing one or more functions.

Referring to fig. 1, fig. 1 is a schematic diagram of an infrastructure of an application modeling system according to an embodiment of the present application. As shown in fig. 1, the application modeling system 100 provided in the present application is provided with a user manager 10, a role manager 20, a menu manager 30, an object manager 40, and a flow manager 50. Wherein:

the user manager 10 is configured to perform user basic information storage and role labeling processing on a target user participating in an application modeling process in the application modeling system 100.

The target users managed by the user manager 10 are developers and testers who use the application modeling system 100. In the application modeling system 100, an interactive interface for interacting with a user is provided. The user manager 10 may acquire and store the basic information of the target user by instructing the login user to fill in the information acquisition table through the interactive interface, perform role labeling processing on the target user based on the basic information of the target user, and set a corresponding matched role tag for the target user, so that the target user associates roles. It should be noted that, in this embodiment, the login user may be an administrator of the application program project, or may also be a developer and a tester participating in the application program project, that is, the basic information of the target user may be created uniformly in the application program modeling system 100 by the administrator of the application program project, or may be created by the target user participating in the application program project in the application program modeling system 100 by himself.

For example, please refer to fig. 2, fig. 2 is a schematic structural diagram of a user manager in an application modeling system according to an embodiment of the present application. As shown in fig. 2, a user-associated character unit 11 is provided in the user manager 10. Wherein:

the user associated role unit 11 is used for calling a role manager 20 and acquiring a plurality of role labels created based on a target application program modeling process from the role manager 20; and selecting a target role label matched with the target user from the plurality of role labels according to the basic information of the target user, and labeling the target user by adopting the target role label so as to enable the target user to associate roles.

In the application modeling system 100, the user association role unit 11 associates the target user with the role, and thus, the management of the operation authority of the target user based on the role label can be realized. For example, different role labels may be set to correspond to different modeling tasks in the modeling process of the associated application, the role label labeled by the target user determines the modeling task that the target user correspondingly undertakes in the modeling process of the application, and in the application modeling system 100, only the operation permission of the modeling task that the target user correspondingly undertakes is opened for the target user. Moreover, in the application modeling system 100, each target user may be labeled with one role label or with a plurality of role labels. For example, when a target user participates in multiple application projects in the application modeling system 100, a role label corresponding to the application project may be labeled for each application project for the target user, and thus, multiple role labels may be labeled for target users participating in multiple application projects.

Illustratively, as shown in fig. 2, the user manager 10 may further include a new user information unit 12, a delete user information unit 13, and a modify user information unit 14. Wherein:

and a newly-built user information unit 12, configured to display an information collection table on an interactive interface, instruct a login user to fill in new user information in the information collection table, generate a first basic information table of the new user based on the information collection table, and store the first basic information table in a database built in the user manager 10.

In the application modeling system 100, a login user can generate a user information creation command by clicking a user information creation button on an interactive interface. Furthermore, the new user information creating unit 12 displays the editable information collection table on the interactive interface according to the user information new creating instruction, and instructs the login user to fill in new user information in the information collection table. After the logged-in user completes the table filling operation and clicks the confirmation, the application modeling system 100 may generate the first basic information table of the new user based on the information collection table, and store the first basic information table in the database built in the user manager 10 for the subsequent modeling process to call.

A delete user information unit 13, configured to retrieve the second basic information table corresponding to the specified user from the database built in the user manager 10, and delete the second basic information table.

In the application modeling system 100, the login user may generate a user information deletion instruction including ID information of a specified user by inputting the ID information of the specified user in the interactive interface and clicking a user information deletion button. Furthermore, the delete user information unit 13 queries the database built in the user manager 10 according to the ID information of the specified user in the user information delete instruction, so as to retrieve and obtain the second basic information table corresponding to the specified user in the user information delete instruction from the database built in the user manager 10, and indicate whether the login user deletes the second basic information table through a pop-up window in the interactive interface. And if the login user clicks the confirmation button in the window, deleting the second basic information table. In this embodiment, if the login user is an administrator of the application program item, the ID information of the specified user in the user information deletion instruction may be ID information of any target user participating in the application program item. If the login user is the target user, the ID information of the specified user in the user information deleting instruction can only be the ID information of the target user.

A modify user information unit 14, configured to retrieve a third basic information table corresponding to the specified user from the database built in the user manager 10, display the third basic information table in an interactive interface, instruct a login user to modify the third basic information table, and store the modified third basic information table in the database built in the user manager 10.

In the application modeling system 100, the login user may generate a user information modification instruction including ID information of a specific user by inputting the ID information of the specific user in the interactive interface and clicking a user information modification button. Furthermore, the modify user information unit 14 queries the database built in the user manager 10 according to the ID information of the specified user in the user information modification instruction, so as to retrieve and obtain a third basic information table corresponding to the specified user in the user information modification instruction from the database built in the user manager 10, display the third basic information table in the interactive interface, and make the third basic information table in an editable state to instruct the login user to modify the third basic information table. After the login user completes modification and click confirmation, the application modeling system 100 may obtain the modified third basic information table, and then store the modified third basic information table in the database built in the user manager 10 instead of the original third basic information table, thereby completing the operation of modifying the user information. In this embodiment, if the login user is an administrator of the application program project, the ID information of the specified user in the user information modification instruction may be the ID information of any target user participating in the application program project. If the login user is the target user, the ID information of the specified user in the user information modification instruction can only be the ID information of the target user.

And the role manager 20 is configured to provide a role creation window for the application modeling process, and configure the operation permission of the target user in the application modeling system 100 according to the role tag obtained by the target user through role tagging.

In the application modeling system 100, based on the role manager 20, the complete application modeling process can be divided into multiple modeling tasks, and different modeling tasks can be assigned to target users labeled with different role labels for completion. For example, a role creation window is set in the role manager 20, the role creation window may divide roles of the application modeling process according to a role dimension, an application project dimension or/and a business process dimension, create a plurality of different role labels in advance, and then set a system operation permission according to the role labels for the application modeling process, where the system operation permission is represented as an operable modeling task. And finally, performing association binding on each role label and the system operation authority correspondingly set by the role label to obtain an association binding relationship between the role label and the system operation authority. Based on the role manager 20, by identifying the role label labeled by the target user, the application modeling system 100 may be triggered to open the system operation authority corresponding to the labeled role label for the target user according to the role label labeled by the target user, according to the association binding relationship between the role label and the system operation authority, thereby configuring the modeling task that the target user needs to execute in the application modeling system 100.

For example, please refer to fig. 3, fig. 3 is a schematic structural diagram of a role manager in an application modeling system according to an embodiment of the present application. As shown in fig. 3, a character authorization unit 21 is provided in the character manager 20. Wherein:

and a role authorization unit 21, configured to configure an operation permission of the role tag corresponding to the target application program in the modeling process according to the application program content range matched with the role tag, where the application program content range matched with the role tag is determined by the login user when performing role division on the target application program modeling process.

In the application modeling system 100, an application modeling process is built based on an application modeling project. In this embodiment, a login user can perform role division on the target application modeling process according to the structure of the application content in the target application modeling project, the function dimension, the application function dimension or/and the business process dimension, and the like, and create a plurality of role labels in advance. Furthermore, for the created role labels, the role authorization unit 21 configures the operation authority corresponding to each role label in the target application modeling process according to the application content range matched with each role label. It will be appreciated that the scope of application content for which role labels match is determined by the logged-in user when the target application modeling process is personalised.

Illustratively, as shown in fig. 3, the role manager 20 may further include a new role unit 22, a modified role unit 23, and a deleted role unit 24. Wherein:

the new role element 22 is used to create a new role label. Specifically, the login user can generate a role new-creation instruction by clicking a new-creation role button in the interactive interface. Then, the new role unit 22 displays the role creation window in the role manager 20 on the interactive interface and calls a role new page in the role creation window according to the role new creation instruction, so as to instruct the login user to newly create a role tag in the role new page, and stores the newly created role tag in a database built in the role manager 20 for subsequent call.

The role modification unit 23 is used for modifying the originally labeled role label of the target user. Specifically, the login user can generate a role modification instruction containing the ID information of the specified user by inputting the ID information of the specified user in the interactive interface and clicking the modify role button. Then, the role label associated with the ID information of the specified user is acquired from the database built in the role manager 20 by the modified role unit 23 according to the ID information of the specified user in the role modification instruction to instruct the login user to perform modification processing on the role label in the role creation window. When the login user completes modification and click confirmation, the modified role tag is stored in the database built in the role manager 20 instead of the original role tag. In this embodiment, the modification of the role label may include, but is not limited to, modifying the target user of the role label association binding based on the role label and/or modifying the application content scope matched with the role label, and unbinding and/or replacing the association binding of the original annotated role label based on the target user. In this embodiment, if the login user is an administrator of the application program project, the ID information of the specified user in the role modification instruction may be the ID information of any target user participating in the application program project. If the login user is the target user, the ID information of the specified user in the role modification instruction can only be the ID information of the target user.

The role deleting unit 24 is configured to delete the originally labeled role tag of the target user. Specifically, the login user can generate a role deletion instruction including the ID information of the specified user by inputting the ID information of the specified user in the interactive interface and clicking the modify role button. Then, the delete role unit 24 acquires the role label associated with the ID information of the specified user from the database built in the role manager 20 according to the ID information of the specified user in the role delete command, and displays the acquired role label on the interactive interface through the role creation window in the role manager 20 to indicate whether the login user deletes the role label in the role creation window, and if the login user confirms the deletion, deletes the role label. It should be noted that, when a role label is deleted, the role label no longer exists in the database built in the role manager 20. In this embodiment, if the login user is an administrator of the application program item, the ID information of the specified user in the role deletion instruction may be the ID information of any target user participating in the application program item. If the login user is the target user, the ID information of the specified user in the role deleting instruction can only be the ID information of the target user.

And the menu manager 30 is configured to provide a menu creation window for the application modeling process, and generate a function menu applied to the application according to the menu information entered by the target user in the menu creation window.

In the application modeling system 100, based on the menu manager 30, all application functions developed and completed by each target user in the application modeling process can be configured in a cascade manner, and a corresponding cascade menu is generated. Illustratively, in the menu manager 30, a menu creation window is provided, and a target user may enter directory entry information for characterizing an application function developed based on his modeling task. Menu manager 30 may generate a local function menu for application to the application based on the directory entries that characterize the application's functions. In the menu manager 30, based on the role labels of the target users, each target user can generate a local function menu corresponding to the application function completed within its operation authority. After each target user generates a local function menu corresponding to the application program function completed in the operation authority, the menu manager 30 associates each local function menu according to the superior-inferior relation of each application program function in the whole application program modeling process to generate a final complete function menu applied to the application program.

For example, please refer to fig. 4, fig. 4 is a schematic structural diagram of a menu manager provided in an application modeling system according to an embodiment of the present application. As shown in fig. 4, the menu manager 30 is provided with a menu creation task configuration unit 31, a menu view template generation unit 32, and a menu view template application unit 33. Wherein:

and the menu creation task configuration unit 31 is configured to identify the role label correspondingly labeled by the target user, and configure a menu creation task for the target user according to the application program content range matched with the role label.

In the application modeling system 100, when a target user uses the menu manager 30 to construct a function menu, the menu creation task configuration unit 31 may configure a corresponding menu creation task for the target user according to a role label correspondingly labeled by the target user, so that the target user can only construct a local function menu corresponding to an application function completed within the system operation permission range of the target user. The menu creation task configuration unit 31 may divide the complete function menu creation task applied to the application program into a plurality of local function menu creation tasks according to the application program content range matched with the role tags, where one role tag corresponds to one local function menu creation task, and further, due to the role labeling of the target user, each local function menu creation task is allocated to the corresponding target user for creation and management.

And the menu view template generating unit 32 is configured to invoke a template file configuration page, acquire the template encoding data input by the target user based on the template file configuration page, and generate a menu view template according to the template encoding data input by the target user.

In the application modeling system 100, a target user may generate a menu view template creation instruction by clicking a menu view template creation button in an interactive interface. The menu view template generating unit 32 displays the menu creation window in the menu manager 30 on the interactive interface and calls a template file configuration page in the menu creation window according to the menu view template creation instruction. The content in the template file configuration page is a template file for entering template encoded data, and the target user can enter the template encoded data into the template file, so that the menu view template generating unit 32 can obtain the template encoded data entered by the target user based on the template file configuration page. And after template coding data is input into the template file, the corresponding menu view template can be generated by operating the template file.

A menu view template application unit 33, configured to identify a menu view template selection instruction initiated by the target user, and apply a menu view template selected in the menu view template selection instruction to a function menu generated by the target user in the menu creation window.

In the application modeling system 100, a target user may generate a menu view template selection instruction by clicking a menu view template selection button in an interactive interface, where the menu view template selection instruction includes a menu view template selected by the target user. The menu attempt template application unit 33 applies the menu view template correspondingly selected by the target user to the function menu generated by the target user in the menu creation window according to the menu view template selection instruction, so that the function menu is presented according to the menu view template. In this embodiment, through the application modeling system, after the menu manager 30 generates the function menu and displays the function menu by using the menu view template, the menu display with the style template feature can be automatically realized only by applying the code file of the function menu to the running code of the application.

Illustratively, as shown in fig. 4, a menu new creation unit 34, a menu modification unit 35, and a menu deletion unit 36 are further provided in the menu manager 30. Wherein:

the menu newly-built unit 34 is configured to invoke a menu newly-built page, acquire directory entry information entered by the target user based on the menu newly-built page, and generate a newly-built local function menu according to the entered directory entry information.

In the application modeling system 100, a target user can generate a menu new instruction by clicking a new menu button in the interactive interface. Then, the menu creating unit 34 displays the menu creating window in the menu manager 30 on the interactive interface and calls the menu creating page in the menu creating window according to the menu creating instruction to instruct the target user to enter the directory entry information of the newly created menu in the menu creating window, after obtaining the directory entry information of the newly created menu, automatically generates a newly created local function menu according to the entered directory entry information, and after obtaining the newly created local function menu, stores the newly created local function menu in the database built in the menu manager 30 for subsequent call.

A menu modification unit 35, configured to retrieve a local function menu associated with the ID information of the target user from a database built in the menu manager 30, and display the local function menu on an interactive interface, so as to instruct the target user to modify the local function menu.

In the application modeling system 100, a target user clicks a modify menu button in an interactive interface to generate a menu modification command, and the menu modification command includes ID information of the target user. Then, according to the menu modification instruction, the menu modification unit 35 calls a local function menu associated with the ID information of the target user from a database built in the menu manager 30, and displays the local function menu in the interactive interface through a menu creation window in the menu manager 30, and makes the local function menu in an editable state to instruct the target user to perform modification processing on the local function menu. When the target user completes modification and clicks confirmation, the modified local function menu is stored in the built-in database of the menu manager 30 in place of the original called local function menu for subsequent calling.

A menu deleting unit 36, configured to retrieve the local function menu associated with the ID information of the target user from the database built in the menu manager 30, and display the local function menu in the interactive interface to indicate whether the target user deletes the local function menu.

In the application modeling system 100, a target user clicks a delete menu button in an interactive interface to generate a menu delete command, and the menu modify command includes ID information of the target user. Then, according to the menu deletion instruction, the local function menu associated with the ID information of the target user is called from the database built in the menu manager 30 by the menu deletion unit 36, and whether the target user deletes the local function menu associated therewith is instructed through the menu creation window in the interactive interface. And if the login user clicks a confirmation button in the menu creation window, deleting the local function menu. When the local function menu is deleted, the local function menu is no longer present in the database built in the menu manager 30.

And the object manager 40 is used for providing an object creation window for the application program modeling process and generating an object database table applied to the application program according to the object information input by the target user in the object creation window.

In the application modeling system 100, based on the object manager 40, a database table that needs to be configured for an application project in the application modeling process can be generated by creating an object. In the object manager 40, a base code for generating an object database table is configured, wherein in the base code, an object represents a database table and an object attribute represents a field in the database table. In the object manager 40, an object creation window is provided, and a target user can automatically generate a corresponding object database table by the object manager 40 by entering relevant object information such as an object and an object attribute in the object creation window, and store the generated object database table in a database built in the object manager 40. The object database table is used for storing program operation data and business data of the application program corresponding to the object. In this embodiment, in the application modeling system 100, a database table that an application project needs to be configured is represented as an object, and a user only needs to enter corresponding object information to automatically generate an object database table corresponding to the object, without paying attention to a creation script of the database table, and the operation of adding/deleting/changing the database table can also be implemented by adding/deleting/changing the object information in an object creation window of the object manager 40. In the object manager 40, based on the role labels of the target users, each target user can operate the database table which needs to be configured within the range of the system operation authority owned by the target user. For example, assume that the target user currently needs to configure an employee database table, the object is an employee table, and the object attributes include name, age, and job title. Accordingly, the target user may create an employee database table by entering the object "employee form" and the object attribute information "name, age, title" in the object creation window of the object manager 40, and the employee database table has fields corresponding to the name, age, title, respectively. Further, when generating the database table, based on the object manager 40, the name, age, and title fields may also be set under the staff base information group by grouping the object attributes, such as the three object attributes of name, age, and title, into the staff base information group in the staff database table.

In application modeling system 100, object manager 40 is also used to perform read-only setting of object properties in the generated object database tables, primary key setting of object properties in the generated object database tables, and/or creating an index for the generated object database tables. In the application modeling system 100, when a target user enters object attribute information using an object creation window in the object manager 40, the object manager 40 gives three selectable options of "read only", "primary key", and "index" for the created object attribute for the target user to select, every time an object attribute is created. When one or more of the three selectable options are selected by the target user, object manager 40 configures the object properties with corresponding properties according to the option selected by the target user. For example, if the "read only" option is selected, the object property is set to read only in the object database table; if the 'primary key' option is selected, setting the object attribute as the primary key in the object database table; if the "index" option is selected, the object attribute is set to the index of the object database table. It should be noted that, when the target user selects the "primary key" option of multiple object attributes, the multiple object attributes are set as the joint primary key in the object database table. And when creating an index for the generated object database table, a single index or an index group can be created to form a combined index.

And the process manager 50 is configured to provide a process creation window for the application modeling process, and generate the process creation window according to the process information entered by the user in the process creation window, where the execution flowchart is used to control an execution process of a function in an application.

In the application modeling system 100, based on the process manager 50, the execution processes of all the program functions to be developed in the application modeling process can be generated in a drawing-board drawing manner. Illustratively, in the process manager 50, a process creation window integrating a process drawing board function is provided, and an application function developed by the target user based on its modeling task may draw a process frame diagram of the application function through the integrated process drawing board function in the process creation window, and configure the entered process information into the drawn process frame diagram in the process creation window, so as to generate an execution process diagram applied to the application. The execution flow chart is used for controlling the execution flow of the functions in the application program.

For example, please refer to fig. 5, fig. 5 is a schematic structural diagram of a process manager in an application modeling system according to an embodiment of the present application. As shown in fig. 5, the flow manager 50 is specifically provided with a flow chart drawing unit 51 and a flow code generation unit 52. Wherein:

and a flow chart drawing unit 51, configured to generate a corresponding flow chart according to the flow components drawn by the target user in the flow chart drawing board integrated by the flow manager and the association relationship between the flow components.

In the application modeling system 100, when a target user draws a flowchart using the flowchart manager 50, the flowchart drawing unit 51 calls the flowchart board integrated in the flowchart manager, and the flowchart board integrated in the flowchart manager 50 is displayed in the interactive interface through the flowchart creation window in the flowchart manager 50, so that the target user can draw the flowchart on the flowchart board. In this embodiment, the flowchart board integrated by the flowchart manager 50 is configured with flowchart components for drawing a flowchart, where the flowchart components include a flowchart node component and a migration line component, and the migration line component is used to connect two associated flowchart nodes. In this embodiment, the flow node components and the migration line components are set as encodable components, and a target user may connect the flow node components together in a manner of dragging the flow node components and the migration line components in the flow chart drawing board according to the flow components drawn by the target user in the flow chart drawing board and the association relationship between the flow components, that is, in a manner of connecting the migration line components in series or in parallel, so as to draw a flow chart. In this embodiment, after the target user draws a flowchart in the flowchart drawing board and clicks confirmation, a corresponding flowchart may be generated.

And the flow code generating unit 52 is configured to identify a logic code entered by the target user in each flow component of the flow chart, and generate a flow chart running code file matched with the flow chart according to an association relationship between the flow components.

In the application modeling system 100, after the target user draws the flow chart, the target user can click and drag a flow component in the flow chart drawing board to display a coding frame corresponding to the component. The target user can input the flow node and logic codes for realizing personalized control at a plurality of time points before the migration line enters the node, after the migration line enters the node, before the migration line exits the node and/or after the migration line exits the node by writing the codes in the coding frame. Then, the flow code generation unit 52 identifies the logic codes entered by the target user in each flow component of the flow chart, and further generates a flow chart running code file matched with the flow chart according to the association relationship between each flow component. After the operation code file of the flow chart is generated, the operation code file of the flow chart is applied to an application program, and the purpose of special control or flow circulation display can be achieved. For example, support for control of node flow (commit, agree, return) and flow content exposure, support for serial and parallel countersign control; and displaying the process links with the authority of the target user according to the role labels of the users. In the displayed process links, an inbox, an outbox and a backspace box are arranged in each process link, and process operation buttons such as editing, submitting and backspace are arranged in a toolbar so as to provide a login user with operations such as adding, deleting and changing the execution process diagram.

In the application modeling system 100, the usage right of the target user in the process manager 50 may also be configured through the role tag, and an attribution role is set for the process flow node corresponding to each application function in the application project. Illustratively, a modeling task born by a user is obtained through a role tag, a preset natural language recognition model is called to recognize text content in a drawn execution flow chart, whether the text content in the execution flow chart drawn by a login user is matched with the content of the modeling task born by the login user is judged, if so, the execution flow chart is set to be effective, otherwise, the execution flow chart is set to be unavailable and the login user is instructed to modify the execution flow chart.

As can be seen from the above, the application modeling system provided in this embodiment unifies the application modeling processes through the user manager, the role manager, the menu manager, the object manager, and the process manager, the user manager performs user basic information storage and role labeling processing on users participating in the application modeling process in the application modeling system, the role manager configures operation permissions of users in the application modeling system according to role labels obtained by the users through the role labeling processing, the menu manager generates a function menu applied to the application according to the entered menu information, the object manager generates an object database table applied to the application according to the entered object information, and the process manager generates an execution flowchart applied to the application according to the entered process information, thereby implementing a complete application modeling process in an application modeling system, the problem that intermediate data information distortion exists among modeling links due to different groups or different developers in the application program modeling process is solved, the development difficulty of the application program is reduced, and meanwhile, the application program is convenient to modify and adjust by the developers during secondary development.

In some embodiments of the present application, please refer to fig. 6, and fig. 6 is a basic flowchart illustrating an application modeling method according to an embodiment of the present application. The details are as follows:

s61: according to operation information executed by a login user in the application program modeling system, a user manager is adopted to mark a corresponding role label for a target user, wherein the role label is obtained by dividing the role of a target application program project through the role manager;

s62: configuring the operation authority of the target user in a menu manager, an object manager and/or a process manager according to the role label;

s63: and identifying effective operation executed by the target user in the menu manager, the object manager and/or the process manager based on the operation authority, and performing application program modeling processing according to the effective operation.

In the present embodiment, when performing application modeling for a certain application item, a modeling file of the application item is input to an application modeling system, and the modeling file includes application contents related to the application item and a structural relationship between the application contents. And after the application modeling system obtains the modeling file, building an application modeling process corresponding to the application project based on the modeling file, wherein the application modeling process comprises all application contents related to the application project. In this embodiment, according to the structural relationship between the application program contents in the modeling file, the application program modeling system first uses the role manager to perform role division on the application program contents in the application program modeling process according to the function dimension, the application program project dimension or/and the business process dimension and create a corresponding role label, so that each part of the application program contents obtained through role division has a corresponding role label. The system operation authority is set according to the role labels, and the role labels and the system operation authority set correspondingly are associated and bound to obtain the association and binding relationship between the role labels and the system operation authority. For example, in this embodiment, the login user may perform a relevant operation in the application modeling system, obtain corresponding operation information, such as an entry operation, a modification operation, and the like of the basic information of the target user, and obtain the latest basic information of the target user. After obtaining the latest basic information of the target user, the application modeling system can manage the users participating in the application modeling process by adopting the user manager. Specifically, users participating in the application modeling process can be respectively used as target users, and one role label matched with the target user is selected from role labels created in the role manager according to basic information of the target users and used as the target role label to label the target user, so that the target user associates roles. Because each role label created in the role manager has the corresponding system operation authority, the operation authority of the target user in the menu manager, the object manager and/or the process manager can be configured according to the system operation authority corresponding to the role label. After the target user executes the relevant modeling operation in the application modeling system, the application modeling system can identify the effective operation executed by the target user in the menu manager, the object manager and/or the process manager based on the operation authority of the target user, and further perform relevant application modeling processing according to the effective operation.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

In some embodiments of the present application, please refer to fig. 7, and fig. 7 is a schematic diagram illustrating a basic structure of an application modeling apparatus according to an embodiment of the present application. As shown in fig. 7, the application modeling apparatus includes a label labeling module 71, a permission configuration module 72, and a modeling processing module 73. The label labeling module 71 is configured to label, according to operation information executed by a login user in the application modeling system, a role label corresponding to a target user by using a user manager, where the role label is obtained by dividing a role of a target application project by using the role manager. The permission configuration module 72 is configured to configure the operation permission of the target user in the menu manager, the object manager and/or the process manager according to the role tag. The modeling processing module 73 is configured to identify an effective operation performed by the target user in the menu manager, the object manager, and/or the process manager based on the operation permission, and perform application modeling processing for the target application item according to the effective operation.

It should be understood that the above-mentioned application modeling apparatus corresponds to the above-mentioned application modeling method, and is not described herein again.

In some embodiments of the present application, please refer to fig. 8, and fig. 8 is a block diagram illustrating a basic structure of an electronic device according to an embodiment of the present application. As shown in fig. 8, the electronic apparatus 8 of this embodiment includes: a processor 81, a memory 82 and a computer program 83, e.g. a program applying a program modeling method, stored in said memory 82 and executable on said processor 81. The processor 81 implements the steps in the various embodiments of the application modeling method described above when executing the computer program 83. Alternatively, the processor 81 implements the functions of the modules in the embodiment corresponding to the application modeling apparatus when executing the computer program 83. Please refer to the description related to the embodiment, which is not repeated herein.

Illustratively, the computer program 83 may be divided into one or more modules (units) that are stored in the memory 82 and executed by the processor 81 to accomplish the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 83 in the electronic device 8. For example, the computer program 83 may be divided into a label labeling module, a permission configuration module, and a modeling processing module, and the specific functions of the modules are as described above.

The electronic device may include, but is not limited to, a processor 81, a memory 82. Those skilled in the art will appreciate that fig. 8 is merely an example of an electronic device 8 and does not constitute a limitation of the electronic device 8 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the electronic device may also include input-output devices, network access devices, buses, etc.

The Processor 81 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 82 may be an internal storage unit of the electronic device 8, such as a hard disk or a memory of the electronic device 8. The memory 82 may also be an external storage device of the electronic device 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 8. Further, the memory 82 may also include both an internal storage unit and an external storage device of the electronic device 8. The memory 82 is used for storing the computer program and other programs and data required by the electronic device. The memory 82 may also be used to temporarily store data that has been output or is to be output.

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments. In this embodiment, the computer-readable storage medium may be nonvolatile or volatile.

The embodiments of the present application provide a computer program product, which when running on a mobile terminal, enables the mobile terminal to implement the steps in the above method embodiments when executed.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media which may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. An application modeling system comprising a user manager, a role manager, a menu manager, an object manager, and a process manager, wherein:

2. The application modeling system of claim 1, wherein the user manager comprises a user role association unit configured to:

3. The application modeling system of claim 1 or 2, wherein the role manager further comprises:

4. The application modeling system of claim 1, wherein the role manager comprises a role authorization unit configured to:

5. The application modeling system of claim 1, wherein the menu manager comprises:

6. The application modeling system of claim 1 or 5, wherein the menu manager further comprises:

7. The application modeling system of claim 1, wherein the object manager is further configured to perform read-only setting of object properties in the generated object database table, primary key setting of object properties in the generated object database table, and/or creating an index for the generated object database table.

8. The application modeling system of claim 1, wherein the process manager comprises:

9. An application modeling method applied to the application modeling system according to any one of claims 1 to 8, comprising:

10. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the steps of the method as claimed in claim 9 are implemented when the computer program is executed by the processor.