CN110648081A - Business modeling method and device for computing system and computer system - Google Patents
Business modeling method and device for computing system and computer system Download PDFInfo
- Publication number
- CN110648081A CN110648081A CN201910948301.XA CN201910948301A CN110648081A CN 110648081 A CN110648081 A CN 110648081A CN 201910948301 A CN201910948301 A CN 201910948301A CN 110648081 A CN110648081 A CN 110648081A
- Authority
- CN
- China
- Prior art keywords
- model
- meta
- business
- client
- category
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/067—Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Abstract
The present disclosure provides a business modeling method for a computing system, comprising: managing a meta-model of one or more model categories in a meta-model database; receiving first modeling application data from a client, wherein the first modeling application data comprises a first model category; obtaining a first meta-model for the first model category from the meta-model database and sending the first meta-model to the client; receiving service configuration information from the client about the first meta-model, the service configuration information including object configuration information and relationship configuration information; and constructing a business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information. The present disclosure also provides a business modeling apparatus for a computing system and a computer system.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a business modeling method and apparatus for a computing system, and a computer system.
Background
At present, the banking industry at home and abroad is increasingly competitive in financial products and technical innovation, and provides higher requirements for the construction of banking business architecture and IT architecture for strengthening customer service, diversified business operation, income structure optimization, continuous innovation and risk management. Because the bank system is complex and huge, in order to meet the needs of the internal and external operating environments of the system, the traditional system solution only depends on the methods of upgrading and reconstructing the system, increasing the system resources, optimizing and improving the project driving mode and the like. The traditional business modeling method firstly analyzes the business requirement process change, then analyzes the application architecture influence and the data structure support, and finally evaluates the change of the IT infrastructure, and is an iterative and progressive process. Due to the lack of a complete technical architecture platform, the processing mode cannot effectively inherit the original system model assets.
In view of the above problems, there is a need for a method for performing business modeling based on existing model assets to improve the inheritance and stability of banking business systems.
Disclosure of Invention
One aspect of the present disclosure provides a business modeling method for a computing system, comprising: metamodels for one or more model categories are managed in a metamodel database. Receiving first modeling application data from a client, wherein the first modeling application data comprises a first model category; a first meta-model for the first model category is then retrieved from a meta-model database and sent to the client. Then, business configuration information about the first meta-model is received from the client, and the business configuration information comprises object configuration information and relation configuration information. And finally, constructing the business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information.
Optionally, the one or more model categories include at least one of: a business process model category, a primary and secondary application model category, a data flow model category, an application node model category, a logical data model category, and a physical deployment model category.
Optionally, the managing meta-models of one or more model categories in the meta-model database includes: second modeling application data is received from the client. The second modeling application data comprises a first model category and meta model modeling information, and the meta model modeling information comprises one or more element information and relationship information between elements. Then, a first meta-model for the first model category is constructed based on the meta-model modeling information. Next, the first meta-model is stored in a meta-model database.
Optionally, the method further includes: a model query request is received from the client, the model query request including a second model category. Then, a business model for the second model class is obtained from the business model database. And then, sending the business model aiming at the second model category to the client so that the client can display the business model aiming at the second model category.
Optionally, the managing meta-models of one or more model categories in the meta-model database includes: receiving modification application data from the client, the modification application data including modification information for the third model type. Then, a third meta-model for the third model type is obtained from the meta-model database. And then, modifying the third metamodel based on the modification information to obtain a modified third metamodel. And modifying one or more business models in the business model database belonging to the third model type based on the modified third meta-model.
Optionally, the method further includes: and sending the business models belonging to the first model category to the client so that the client can display the business models belonging to the first model category.
Optionally, the sending the service model belonging to the first model category to the client includes: and sending the flow chart aiming at the business model to the client.
Optionally, the sending the service model belonging to the first model category to the client further includes: input parameters are received from a client. And then operating the business model based on the input parameters to obtain an operation result. And then, sending the operation result to the client.
Another aspect of the present disclosure provides a business modeling apparatus for a computing system, comprising: the device comprises a management module, a first receiving module, a meta-model obtaining module, a second receiving module and a modeling module. The management module is to manage the meta-models of the one or more model categories in a meta-model database. The first receiving module is used for receiving first modeling application data from the client, and the first modeling application data comprises a first model category. The meta-model obtaining module is used for obtaining a first meta-model aiming at the first model category from the meta-model database and sending the first meta-model to the client. The second receiving module is used for receiving service configuration information of the first meta-model from the client, and the service configuration information comprises object configuration information and relation configuration information. The modeling module is used for constructing a business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information.
Another aspect of the present disclosure provides a computer system comprising: memory, a processor and a computer program stored on the memory and executable on the processor for implementing the method as described above when the processor executes the computer program.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
According to the embodiment of the disclosure, the meta-models of one or more model categories are centrally and uniformly managed in the meta-model database, the business models of one or more model categories are centrally and uniformly managed in the business model database, and the unified and structured management of the model assets is realized. When business modeling is carried out, the meta-model of the corresponding model category is used as a modeling basis for configuration and construction, and the modeling from beginning to end by a user is avoided. And the process can continuously increase the number and the types of the model assets, so that a user can know the relevant dynamics of the technical architecture, the data architecture, the application architecture, the business architecture and the like of the computing system based on the model assets.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 schematically illustrates an exemplary system architecture of application business modeling methods and apparatus according to embodiments of the present disclosure;
FIG. 2 schematically illustrates a flow diagram of a business modeling method for a computing system, in accordance with an embodiment of the present disclosure;
FIG. 3 schematically illustrates an example block diagram of a computing system in accordance with an embodiment of this disclosure;
FIG. 4 schematically illustrates an example structure diagram of the model data storage module 310 shown in FIG. 3, in accordance with an embodiment of this disclosure;
FIG. 5 schematically illustrates an example diagram of building meta-models for various model classes, according to an embodiment of this disclosure;
FIG. 6 schematically illustrates an example structure diagram of the model data processing module 320 shown in FIG. 3, in accordance with an embodiment of this disclosure;
FIG. 7 schematically illustrates a block diagram of a business modeling apparatus for a computing system, in accordance with an embodiment of the present disclosure; and
FIG. 8 schematically shows a block diagram of a computer system according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
The embodiment of the disclosure provides a business modeling method and device for a computing system and the computing system. The method may include a management process, a first receiving process, a meta model obtaining process, a second receiving process, and a modeling process. In the management process, the meta-models of one or more model categories are managed in a meta-model database to support a subsequent meta-model acquisition process. In a first receiving process, first modeling application data is received from a client, the first modeling application data including a first model category. And then, carrying out a meta-model obtaining process, obtaining a first meta-model aiming at the first model category from a meta-model database, and sending the first meta-model to the client. And responding to the operation of the client on the first meta-model, and performing a second receiving process. And receiving service configuration information from the client about the first meta-model, wherein the service configuration information comprises object configuration information and relation configuration information. And finally, carrying out a modeling process, and constructing the business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information.
FIG. 1 schematically illustrates an exemplary system architecture 100 to which the business modeling methods and apparatus may be applied, according to an embodiment of the disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server/server cluster 105. The network 104 serves to provide a medium of communication links between the terminal devices 101, 102, 103 and the server/server cluster 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
Various client applications, such as business modeling tools (for example only), may be installed on the terminal devices 101, 102, 103. The terminal devices 101, 102, 103 may interact with the server/server cluster 105 through various client applications to send various requests to the server/server cluster 105 or to receive results returned by the server/server cluster 105.
The terminal devices 101, 102, 103 may be various electronic devices including, but not limited to, smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
Server/server cluster 105 is a back-office management server or server cluster (for example only) that may provide various service support. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the business modeling method provided by the embodiments of the present disclosure may be generally performed by the server/server cluster 105. Accordingly, the business modeling apparatus provided by the embodiments of the present disclosure may be generally disposed in the server/server cluster 105. The service modeling method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster different from the server/server cluster 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server/server cluster 105. Correspondingly, the service modeling apparatus provided in the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server/server cluster 105 and capable of communicating with the terminal devices 101, 102, and 103 and/or the server/server cluster 105.
It should be understood that the number of end devices, networks, and server/server clusters in fig. 1 is illustrative only. There may be any number of end devices, networks, and server/server clusters, as desired.
The embodiment of the disclosure provides a business modeling method for a computing system, which realizes unified structural management of the computing system on business model resources by managing meta-models of various model types and business models. In the following description, the implementation of the method is described, and it should be noted that the sequence numbers of the operations in the following method are only used as the representation of the operations for description, and should not be regarded as representing the execution sequence of the operations. The method need not be performed in the exact order shown, unless explicitly stated.
FIG. 2 schematically illustrates a flow diagram of a business modeling method for a computing system, which may be applied to a server or server cluster of the computing system, according to an embodiment of the present disclosure.
As shown in fig. 2, the method may include the following operations S201 to S205.
In operation S201, a meta-model of one or more model categories is managed in a meta-model database.
Wherein models (models) belonging to different model classes are used to characterize different aspects of a computing system, exhibiting different points of interest for the computing system. The model classes may be divided according to the computing system reality. For example, for the software domain of a computing system, at least one of the following model categories may be classified: class models, functional models, communication models, deployment models, object models, and so forth. The object model concerns relationships between objects within the computing system, the communication model concerns communication relationships between distributed components of the computing system, the functional model concerns relationships between functional modules of the computing system, and so on. Each model class corresponds to a meta model (MetaModel). A meta-model for a model class defines the specification of the model class, e.g., the elements that make up the model and the relationships between the elements. The present operation S201 centrally and uniformly manages the meta-models of one or more model categories in the meta-model database to support the subsequent model creation process.
Then, in operation S202, first modeling application data is received from a client.
When a user wishes to construct a business model, first modeling application data can be sent to a server through a client. The first modeling application data may include a model category to which the business model that the user wishes to construct belongs, such as a first model category, so as to perform subsequent modeling based on the meta model of the corresponding model category. A "user" herein may be an operation or maintenance person of a computing system.
Next, in operation S203, a first meta-model for the first model category is acquired from the meta-model database, and the first meta-model is transmitted to the client.
It has been explained above that the first meta-model for a first model class defines a specification for this first model class, containing the most basic element information and relationship information between elements. And sending the first meta-model to a client, and displaying the first meta-model to a user by the client, namely displaying the basic model structure of the first model category to the user. On the basis, a user can configure on the basic model structure according to the service requirements of the service model that the user wants to construct, for example, element definition, object definition, application definition, relationship definition, and the like can be performed by filling configuration information, dragging, and the like, and the configuration process correspondingly generates service configuration information.
Next, in operation S204, business configuration information about the first meta-model is received from the client.
The service configuration information may include object configuration information and relationship configuration information.
Finally, in operation S205, a business model belonging to the first model category is constructed in a business model database based on the first meta model and the business configuration information.
Wherein each model category may correspond to one or more business models. And storing the service model obtained by each modeling into a service model database. In the business model database, business models can be stored according to model class classification.
As can be understood by those skilled in the art, the method shown in FIG. 2 centralizes and unifies management of the meta-models of one or more model categories in the meta-model database, centralizes and unifies management of the business models of one or more model categories in the business model database, and realizes unified and structured management of the model assets. When business modeling is carried out, the meta-model of the corresponding model category is used as a modeling basis for configuration and construction, and the modeling from beginning to end by a user is avoided. And the process can continuously increase the number and the types of the model assets, so that a user can know the relevant dynamics of the technical architecture, the data architecture, the application architecture, the business architecture and the like of the computing system based on the model assets.
According to the embodiment of the disclosure, the meta-model in the meta-model database can be obtained from other devices or generated by creation. When a user wishes to construct a meta-model for a new model category, second modeling application data may be sent to the server via the client. Illustratively, taking building a meta-model for a first model category as an example, managing meta-models for one or more model categories in a meta-model database as described above may include: second modeling application data is received from the client. The second modeling application data may include the first model category and meta model modeling information, and the meta model modeling information includes one or more element information and relationship information between elements. Then, a first meta-model for the first model category is constructed based on the meta-model modeling information. Next, the first meta-model is stored in a meta-model database. The process of constructing the meta-model for other model classes in the meta-model database is the same as the process of constructing the first meta-model, and is not described herein again. It can be understood that as the meta-model building process progresses, the number of meta-models in the meta-model database and the types of models for which the meta-models are aimed continuously increase, and optimization of the business model building process can be promoted.
Since the business models are managed in a unified manner in the business model database, the business modeling method according to the embodiment of the present disclosure can also support query for the business models. Illustratively, when a user wishes to query a business model, a model query request may be sent to the server via the client. The server receives a model query request from the client, wherein the model query request comprises a model category, such as a second model category, of the business model which the user wishes to query. And the server acquires the service model belonging to the second model category from the service model database and sends the acquired service model to the client so that the client can display the service model.
Furthermore, because the meta-models are managed in a unified manner in the meta-model database, the business modeling method according to the embodiment of the disclosure can also support modification of the meta-models, and can implement unified modification of a plurality of business models in the same model category by modifying one meta-model according to the inheritance relationship between the meta-model and the business model. Illustratively, when a user wishes to modify all business models of a model class already in the computing system, modification application data may be sent to the server via the client. The above meta-model managing one or more model categories in the meta-model database may further include: receiving, from the client, modification application data that may include modification information for the third model type. A third meta-model for the third model type is then obtained from the meta-model database. And then, modifying the third ternary model based on the modification information to obtain a modified third ternary model. And modifying one or more business models in the business model database belonging to the third model type based on the modified third meta-model.
Further, the business modeling method according to the embodiment of the present disclosure may further include: and sending the business model belonging to the first model category to the client so that the client can display the business model belonging to the first model category. Illustratively, a flow diagram for the business model can be generated, and the flow diagram is presented at the client to make the logic of the business model intuitively known to the user. On the basis, after the business model is displayed to the user, input parameters filled in by the user through the client can be received. And operating the service model based on the input parameters to obtain an operation result and sending the operation result to the client.
A business modeling method for a computing system according to an embodiment of the present disclosure is exemplarily described below with reference to fig. 3 to 6.
FIG. 3 schematically shows an example block diagram of a computing system in accordance with an embodiment of this disclosure.
As shown in fig. 3, for example, the computing system may be a computing system of a banking system architecture, and the business modeling method for the computing system may be a business modeling method for banking business. The computing system 300 may include: model data storage module 310, model data processing module 320, financial transmission network 330, system construction terminal 340. The model data storage module 310 and the model data processing module 320 are deployed in the above-mentioned server or server cluster, and the system building terminal 340 can be used as the above-mentioned client.
The model data processing module 320 is used for responding to the model modeling application, processing and processing the modeling data, and completing the processes of model modeling application, basic model data retrieval, data assembly and processing after modeling, and the like. The financial transmission network 330 is a bank internal network, and the system construction terminal 340 is connected to the model data processing module 320 through the financial transmission network 330. The system construction terminal 340 is a C/S type terminal supporting various types of model presentations.
The model data storage module 310 is used for storing basic architecture model data and various system architecture model data, and may be a database management system or a file system. For example, model data storage module 310 may include the meta model database and business model database described above. The model data storage module 310 takes the meta model as a core, and may divide the storage units according to the model categories. For example, the model categories may include at least one of: the system comprises a business process model, a main application model, an auxiliary application model, a data flow model, an application node model, a logic data model and a physical deployment model. The memory cell division of the model data storage module 310 is shown in fig. 4.
FIG. 4 schematically illustrates an example block diagram of the model data storage module 310 shown in FIG. 3, according to an embodiment of this disclosure.
As shown in fig. 4, the model data storage module 310 may include a business process model storage unit 311, a primary and secondary application model storage unit 312, a data flow model storage unit 313, an application node model storage unit 314, a logical data model storage unit 315, a physical deployment model storage unit 316, and a metadata storage unit 317.
Illustratively, the present disclosure adds an XCore meta-model on the basis of a model framework emf (Eclipse Modeling framework) of an Eclipse open source project, and the XCore meta-model can be stored in the metadata storage unit 317. The meta-model realizes the storage definition of the basic model of each model category and can be mainly divided into two parts: (1) model structures (data structures), also known as abstract syntax; (2) the description of the style and behavior definitions is presented in what is referred to as a concrete grammar.
For example, the abstract syntax is mainly composed of the following elements:
1. XPackage: the concept of a package is mainly used to control and manage the structure of a group of models and the instantiation of the model structure, and the result of the instantiation is XObject. It has some definitions of package names and some definitions of description information.
2. XClass: a model structure is defined, which mainly comprises attribute information (XAttribute) and reference information (XReference), and inherited parent XClass. It has the definition of structure name and some description information.
3. XAtteribute: attribute information defines, names specified for attributes, types of attributes, and some associated descriptive information.
4. XReference: and defining reference information, and defining reference relations between the models. XClass defining references, whether defining single or multiple references, and some associated descriptive information.
5. XObject: the result of instantiating the model structure (XClass) with XPackage is XObject. Data storage for such model structures is provided.
For example, the definition of the style and behavior of the corresponding model like grammar can include: frame style definition, line pattern, line thickness, line color, text style definition, etc., which will not be described herein.
On the basis of the XCore meta model, the metadata storage unit 317 may further include a meta model designer 3171, a model editor 3172, and a resource manager 3173 for accomplishing customization, editing, and parsing of the base model of various model classes. The connection relationship is shown in fig. 5.
FIG. 5 schematically shows an example schematic diagram of building meta-models for various model classes, according to an embodiment of the disclosure.
As shown in fig. 5, the meta model designer 3171 is used to customize various basic models, such as a business process model, a primary and secondary application model, a data flow model, an application node model, a logical data model, and a physical deployment model, which can be regarded as meta models of various model classes. The model editor 3172 realizes modeling design of business models related to each architecture field under guidance and constraint of the meta model by downloading the meta model of various model types from the meta model designer 3171, and saves information such as coordinate position, color, line thickness, and the like of each object, relationship, field in the model file as an XML text file. The resource manager 3173 is responsible for resource and version management, provides support for the meta model designer 3171 and the model editor 3172, parses the XML text file, analyzes and extracts display related information such as coordinate position, color, line thickness and the like of each object, relationship and field, and converts the information into an asset webpage, thereby providing complete and visual panoramic presentation for the bank.
Continuing back to fig. 4, the business process model storage unit 311 can be used to store specific business processes, applications supporting the banking core business process and the auxiliary business process, and can be changed according to business strategy and business process changes. The storage unit at least comprises: events, activities, conditions, sequence flows, message flows. Wherein an event refers to what happens during a business process. An event affects the flow of a flow, typically with one cause (trigger) or one effect (outcome). Based on their impact on the process, there are three events: start, intermediate, and end events. An activity refers to a specific link of work to be processed, conditions are used to control branching and merging of sequence flows, sequence flows are used to specify the order in which the activities are executed, and message flows are used to describe the flow of messages sent and received between two independent business participants (business entities or business roles).
The primary and secondary application model storage unit 312 can be used for storing an association relationship between the primary application and the related secondary applications, and at least includes: primary application, secondary application, association relationship. The main application is an application for realizing the service core function, and the auxiliary applications are all applications for completing the service system function in cooperation with the main application. The data flow model storage unit 313 may be configured to store the logic functions of the system, the logic flow direction of the data inside the system, and the logic transformation process, and at least includes: applications, online relationships, batch relationships, online and batch relationships, and the like. The online relationship is used for representing the relationship between two applications accessed through the online interface, the batch relationship is used for representing the relationship between the two applications accessed through the batch file interface, and the batch and online relationship is used for representing the relationship between the two applications accessed through the online interface and the batch file interface.
The application node model storage unit 314 may be configured to store application node partitions inside the application, and is a bridge connecting the application architecture and the technical architecture, and at least includes: host service nodes, WEB service nodes, standard application service nodes, non-standard application service nodes, data service nodes, client nodes, and the like. The system comprises a host service node, a WEB service node, a standard application service node, a non-standard application service node, a database server and a client node, wherein the host service node refers to application program resources needing to be deployed in a host system operating environment, the WEB service node refers to application resources following B/S structural technical requirements, the application is deployed on a WEB server, the standard application service node refers to application resources following B/S structural technical requirements, the application is deployed on the application server, the non-standard application service node refers to functions realized by adopting a C/S structure, the program resources are deployed on the server, the data service node refers to application resources needing to be deployed on the database server, and the client node refers to application.
The logical data model storage unit 315 may be used to store entities and relationships between them, including at least: entities, relationships, and the like. Where an entity is an "event" or "object" in the real world that is distinguishable from other objects, a relationship is a correlation between multiple entities, such as a one-to-one, one-to-many, many-to-many relationship, and the like. The physical deployment model storage unit 316 can be used for storing physical deployment conditions of the application in the production environment, and at least includes: area, network security area, application node, association, etc. The areas are divided according to different physical deployments, the Network security Area is a server set with the same security risk, the same security protection level and the same user access group, and is composed of one or more Virtual Local Area Networks (VLANs) in the same Network security level, and the association relationship describes the association relationship between the application nodes. The metadata storage unit 317 may further be configured to store association relationships between various models, and provide support services for the various model storage units, where the support services at least include: organization, role, area, security zone, etc. The organization and the role are used in a business process model storage unit to describe participants of a business process, and the area and the safe area are used in a physical deployment model storage unit to describe a deployment area of an application node.
FIG. 6 schematically illustrates an example block diagram of the model data processing module 320 shown in FIG. 3, according to an embodiment of this disclosure.
As shown in fig. 6, the model data processing module 320 may include: a main processing unit 321, an interface data processing means 322, a model control means 323, a model engine means 324, a model data equipping means 325, a model data processing means 326, and a model result data storage means 327.
The main processing unit 321 is a main control unit in the model data processing module 320, and is responsible for responding to modeling application data, retrieving basic model data, assembling and processing modeled data, and the like. The processing request (for example, modeling application data) initiated by the system construction terminal 340 is transmitted to the main processing unit 321 in the model data processing module 320 via the financial transmission network. The main processing unit 321 transmits a processing request to the model control means 323 through the interface data processing means 322. After obtaining the model type in the modeling application data, the model control device 323 calls the model engine device 324, calls the existing model (which may include the base model and the non-base model) belonging to the model type from the infrastructure asset library (such as the model data storage module 310), and returns the model to the client for presentation to the user. And the user configures the existing model according to the new product attribute in the actual service. After receiving the configuration data from the client, the main processing unit 321 calls the model data equipment device 325 to assemble the data according to the model structure requirement, processes the model data through the model data processing device 326, and finally calls the model result data storage device 327 to store the modeling data.
The interface data processing device 322 is used for data information interaction between modules in the system and as a portal for request and result interaction between the system and external users. The model control unit 323 is responsible for analyzing the processing request, and upon receiving the processing request transmitted from the interface data processing unit 322, analyzes the processing request to obtain the model type related to the processing request. After the model control device 323 acquires the model type information, the model engine device 324 is responsible for parsing various model storage units in the model data storage module 310 and feeding back the existing model assets belonging to the model type to the client through the interface data processing device 322. Then, the user performs configuration operations (such as input operations, dragging operations, etc.) on the fed-back model assets through the client based on the business requirements, and the configuration information is returned to the main processing unit 321 through the interface data processing device 322. The model data assembling device 325 is responsible for assembling the configuration information into executable model data processing instructions according to the model class requirements, and transmitting the executable model data processing instructions to the model data processing device 326 through the interface data processing device 322. The model data processing unit 326 receives the executable model data processing command transmitted from the model data equipping unit 325, performs an operation process, and transmits operation result information to the model result data storage unit 327 through the interface data processing unit 322. The model result data storage device 327 receives the operation result information through the interface data processing device 322, stores the operation result information into the corresponding model storage unit in the model data storage module 310, and feeds back the operation state (normal/failure) of the processing request to the main processing unit 321 through the interface data processing device 322. If the operation state is normal, the operation result information in the model result data storage device 327 is fed back to the system construction terminal 340 through the interface data processing device 322, and the system construction terminal 340 displays the operation result information to the user in a manner of strong readability, such as a flow chart, a data flow graph, and the like.
FIG. 7 schematically illustrates a block diagram of a business modeling apparatus for a computing system, in accordance with an embodiment of the present disclosure.
As shown in fig. 7, the business modeling apparatus 700 for a computing system may include: a management module 710, a first receiving module 720, a meta model obtaining module 730, a second receiving module 740, and a modeling module 750.
The management module 710 is used to manage the meta-models of one or more model categories in a meta-model database.
The first receiving module 720 is configured to receive first modeling application data from a client, where the first modeling application data includes a first model category.
The meta-model obtaining module 730 is configured to obtain a first meta-model for the first model category from the meta-model database, and send the first meta-model to the client.
The second receiving module 740 is configured to receive service configuration information from the client regarding the first meta-model, where the service configuration information includes object configuration information and relationship configuration information.
The modeling module 750 is configured to build a business model belonging to a first model category in a business model database based on the first meta-model and the business configuration information.
It should be noted that the implementation, solved technical problems, implemented functions, and achieved technical effects of each module/unit/subunit and the like in the apparatus part embodiment are respectively the same as or similar to the implementation, solved technical problems, implemented functions, and achieved technical effects of each corresponding step in the method part embodiment, and are not described herein again.
Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.
For example, any plurality of the management module 710, the first receiving module 720, the meta model obtaining module 730, the second receiving module 740, and the modeling module 750 may be combined into one module to be implemented, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the management module 710, the first receiving module 720, the meta-model obtaining module 730, the second receiving module 740, and the modeling module 750 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the management module 710, the first receiving module 720, the meta model obtaining module 730, the second receiving module 740, and the modeling module 750 may be at least partially implemented as a computer program module that, when executed, may perform a corresponding function.
FIG. 8 schematically illustrates a block diagram of a computer system suitable for implementing the above-described method, according to an embodiment of the present disclosure. The computer system illustrated in FIG. 8 is only one example and should not impose any limitations on the scope of use or functionality of embodiments of the disclosure.
As shown in fig. 8, a computer system 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flows according to embodiments of the present disclosure.
In the RAM 803, various programs and data necessary for the operation of the system 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or RAM 803. Note that the programs may also be stored in one or more memories other than the ROM 802 and RAM 803. The processor 801 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
System 800 may also include an input/output (I/O) interface 805, also connected to bus 804, according to an embodiment of the disclosure. The system 800 may also include one or more of the following components connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be understood by those skilled in the art that while the present disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.
Claims (10)
1. A business modeling method for a computing system, comprising:
managing a meta-model of one or more model categories in a meta-model database;
receiving first modeling application data from a client, wherein the first modeling application data comprises a first model category;
obtaining a first meta-model for the first model category from the meta-model database and sending the first meta-model to the client;
receiving service configuration information from the client about the first meta-model, the service configuration information including object configuration information and relationship configuration information; and
and constructing the business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information.
2. The method of claim 1, wherein the one or more model categories include at least one of:
a business process model category, a primary and secondary application model category, a data flow model category, an application node model category, a logical data model category, and a physical deployment model category.
3. The method of claim 1, wherein the managing meta-models of one or more model categories in a meta-model database comprises:
receiving second modeling application data from a client, wherein the second modeling application data comprises a first model category and meta-model modeling information, and the meta-model modeling information comprises one or more element information and relationship information between elements;
constructing a first meta-model for the first model category based on the meta-model modeling information; and
storing the first meta-model in the meta-model database.
4. The method of claim 1, further comprising:
receiving a model query request from a client, the model query request including a second model category;
obtaining a business model belonging to the second model category from the business model database; and
and sending the business model belonging to the second model category to a client so that the client can display the business model belonging to the second model category.
5. The method of claim 4, wherein the managing meta-models of one or more model categories in a meta-model database comprises:
receiving modification application data from a client, the modification application data including modification information for a third model type;
obtaining a third meta-model for the third model type from the meta-model database;
modifying the third meta-model based on the modification information to obtain a modified third meta-model; and
and modifying one or more business models in the business model database, which belong to the third model type, based on the modified third meta-model.
6. The method of claim 1, further comprising:
and sending the business model belonging to the first model category to the client so that the client can display the business model belonging to the first model category.
7. The method of claim 6, wherein the sending the business model belonging to the first model class to the client comprises:
and sending the flow chart aiming at the business model to the client.
8. The method of claim 7, wherein said sending the business model belonging to the first model class to the client further comprises:
receiving input parameters from a client;
operating the service model based on the input parameters to obtain an operation result; and
and sending the operation result to a client.
9. A business modeling apparatus for a computing system, comprising:
a management module for managing meta-models of one or more model categories in a meta-model database;
the system comprises a first receiving module, a first modeling application data processing module and a first modeling application data processing module, wherein the first modeling application data is received from a client and comprises a first model category;
the meta-model obtaining module is used for obtaining a first meta-model aiming at the first model category from the meta-model database and sending the first meta-model to the client;
a second receiving module, configured to receive service configuration information from the client regarding the first meta-model, where the service configuration information includes object configuration information and relationship configuration information; and
and the modeling module is used for constructing the business model belonging to the first model category in a business model database based on the first meta-model and the business configuration information.
10. A computer system, comprising: memory, processor and computer program stored on the memory and executable on the processor, the processor when executing the computer program for implementing the method according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910948301.XA CN110648081A (en) | 2019-09-30 | 2019-09-30 | Business modeling method and device for computing system and computer system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910948301.XA CN110648081A (en) | 2019-09-30 | 2019-09-30 | Business modeling method and device for computing system and computer system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110648081A true CN110648081A (en) | 2020-01-03 |
Family
ID=69012223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910948301.XA Pending CN110648081A (en) | 2019-09-30 | 2019-09-30 | Business modeling method and device for computing system and computer system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110648081A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114816389A (en) * | 2022-07-01 | 2022-07-29 | 北京远舢智能科技有限公司 | Management system building method, device, equipment and medium based on meta-model |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102867009A (en) * | 2012-04-27 | 2013-01-09 | 北京华胜鸣天科技有限公司 | Creation method, device and system for information system |
| US20150032783A1 (en) * | 2013-07-26 | 2015-01-29 | Netapp, Inc. | Systems and Methods for Meta-Model Based Data Transactions |
| CN105320498A (en) * | 2014-05-28 | 2016-02-10 | 中国科学院沈阳自动化研究所 | Configurable multi-layer production tracking visualization method based on graphs |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
-
2019
- 2019-09-30 CN CN201910948301.XA patent/CN110648081A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102867009A (en) * | 2012-04-27 | 2013-01-09 | 北京华胜鸣天科技有限公司 | Creation method, device and system for information system |
| US20150032783A1 (en) * | 2013-07-26 | 2015-01-29 | Netapp, Inc. | Systems and Methods for Meta-Model Based Data Transactions |
| CN105320498A (en) * | 2014-05-28 | 2016-02-10 | 中国科学院沈阳自动化研究所 | Configurable multi-layer production tracking visualization method based on graphs |
| CN108733713A (en) * | 2017-04-21 | 2018-11-02 | 阿里巴巴集团控股有限公司 | Data query method and device in data warehouse |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114816389A (en) * | 2022-07-01 | 2022-07-29 | 北京远舢智能科技有限公司 | Management system building method, device, equipment and medium based on meta-model |
| CN114816389B (en) * | 2022-07-01 | 2022-10-11 | 北京远舢智能科技有限公司 | Management system building method, device, equipment and medium based on meta-model |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10515205B2 (en) | Systems and methods for determining trust levels for computing components | |
| US10216490B2 (en) | Systems and methods for computing applications | |
| US8127237B2 (en) | Active business client | |
| US10845962B2 (en) | Specifying user interface elements | |
| US7669137B2 (en) | Computer method and apparatus for representing a topic in a software modeling system | |
| US8924914B2 (en) | Application creation tool toolkit | |
| US11797273B2 (en) | System and method for enhancing component based development models with auto-wiring | |
| US20130067456A1 (en) | Application configuration framework for enterprise resource planning application installation | |
| US9558215B2 (en) | Governing information | |
| US20120137005A1 (en) | Semantic- and Preference-Based Planning of Cloud Service Templates | |
| US20120185827A1 (en) | Custom code lifecycle management | |
| CN113835691A (en) | iOS application development method, system, device, medium and program product | |
| CN110648081A (en) | Business modeling method and device for computing system and computer system | |
| Sangwan et al. | Integrating a software architecture-centric method into object-oriented analysis and design | |
| CN116360735A (en) | Form generation method, device, equipment and medium | |
| US20140172955A1 (en) | Distributed mobile enterprise application platform | |
| CN115082247A (en) | System production method, device, equipment, medium and product based on label library | |
| US11113664B2 (en) | Data provisioning system and method | |
| US11949761B2 (en) | Techniques for distributed interface component generation | |
| US20240054145A1 (en) | Object Lineage Analysis For Package Transport | |
| WO2021254103A1 (en) | Information delivery method, apparatus and device, and computer-readable storage medium | |
| US11593251B2 (en) | Techniques for large-scale functional testing in cloud-computing environments | |
| US10203984B2 (en) | Data structure for multiple executable tasks | |
| CN115729567A (en) | Automatic deployment method and device of operation and maintenance product, electronic equipment and storage medium | |
| CN115309377A (en) | Running method, device and equipment of micro application and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200103 |
|
| RJ01 | Rejection of invention patent application after publication |