CN107480186B - Business model data processing method and computer equipment - Google Patents
Business model data processing method and computer equipment Download PDFInfo
- Publication number
- CN107480186B CN107480186B CN201710550601.3A CN201710550601A CN107480186B CN 107480186 B CN107480186 B CN 107480186B CN 201710550601 A CN201710550601 A CN 201710550601A CN 107480186 B CN107480186 B CN 107480186B
- Authority
- CN
- China
- Prior art keywords
- business
- model data
- business model
- working space
- format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present disclosure provides a business model data processing method and a computer device, the method comprising: establishing connection with a Structured Query Language (SQL) database through ADO connection, taking a list associated with service model data as input of a query result acquiring function, calling the query result acquiring function to acquire service model data in a record set format, and converting the acquired service model data in the record set format into a display format supported by Office. According to the method and the device, the SQL database export is used for replacing the SA export, so that the problem of low SA data export efficiency is solved, the interruption caused by the abnormity that the SA cannot be captured is avoided, and the operation efficiency and the stability of the computing device are improved on the whole.
Description
Technical Field
The invention relates to the field of data processing, in particular to a business model data processing method and computer equipment.
Background
In the related art, the framework data is generally processed using IBM Rational System Architecture (SA). The business model can be modeled and analytically processed from multiple perspectives using the SA model.
Then, in the process of exporting business model data through the SA in the prior art, the efficiency of exporting data from the SA is low, and if there is a change in demand, a large amount of repeated development operations are required, which results in an increase in maintenance cost.
Disclosure of Invention
The present disclosure provides a business model data processing method and a computer device, which can avoid the problem of low data export efficiency by exporting a substitute SA through an SQL database, and can also avoid a large amount of repeated code development when the demand is changed.
According to a first aspect of the embodiments of the present invention, a method for processing business model data is provided, and the method may further include: establishing connection with a Structured Query Language (SQL) database through ADO connection, taking a list associated with service model data as input of a query result acquiring function, calling the query result acquiring function to acquire service model data in a record set format, and converting the acquired service model data in the record set format into a display format supported by Office.
In some embodiments, the display format comprises: text, tables, pictures, and lists.
In some embodiments, the method further comprises: before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, a derivation operation is executed, and a list which is required to be displayed and is associated with service model data is determined, wherein the list comprises the following items of application names, change records, service constraints, technical constraints, service practices, service association relation graphs, existing applications, supported basic products, new requirements, system requirements, performance requirements, user experience requirements and a target operation time table.
In some embodiments, the application component can inherit the scope of the business component and fulfill the requirements of the business component.
In some embodiments, when the display format is a table, the method further comprises: adjusting a tabular display format of business model data, the adjusting including one or more of: merging cells, setting the background color of the table and adding the header of the table.
In some embodiments, the method further comprises: before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, and difference comparison operation is executed to determine a list associated with service model data, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing chart differences.
According to a second aspect of embodiments of the present invention, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing when executing the program: establishing connection with a Structured Query Language (SQL) database through ADO connection, taking a list associated with service model data as input of a query result acquiring function, calling the query result acquiring function to acquire service model data in a record set format, and converting the acquired service model data in the record set format into a display format supported by Office.
In some embodiments, the display format comprises: text, tables, pictures, and lists.
In some embodiments, the processor when executing the program further implements, prior to establishing a connection with a Structured Query Language (SQL) database via an ADO connection, designating a source workspace and a target workspace with an application component as a keyword, running a macro, performing a derivation operation, and determining a list associated with business model data to be displayed, the list including a plurality of application names, change records, business constraints, technical constraints, business practices, business association maps, existing applications, supported base products, new requirements, system requirements, performance requirements, user experience requirements, and a target operational schedule.
In some embodiments, the application component can inherit the scope of the business component and fulfill the requirements of the business component.
In some embodiments, when the display format is a table, the processor when executing the program further implements: adjusting a tabular display format of business model data, the adjusting including one or more of: merging cells, setting the background color of the table and adding the header of the table.
In some embodiments, the processor, when executing the program, further implements: before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, and difference comparison operation is executed, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing chart differences.
According to the business model data processing method and the computer equipment provided by the embodiment of the invention, the connection with the SQL database is established through ADO connection, the business model data in a record set format is obtained by utilizing the query result function, and the SQL database is exported to replace SA export, so that the problem of low SA data export efficiency is avoided, the interruption caused by the abnormity that the SA cannot capture is also avoided, and the stability and the operation efficiency of the computer equipment are improved on the whole; and the business model data in the record set format is converted into a display format supported by Office, the processing logic of the business model data is kept controlled in a database, the Office on the upper layer is only responsible for report display, the data acquisition and display logic are separated, the reusability of program codes is improved, and the operation cost is reduced.
Drawings
FIG. 1 is a flow diagram of a business model data processing method according to an embodiment of the invention.
FIG. 2 is a schematic diagram of a computer device according to an embodiment of the present invention.
Detailed Description
Various aspects of the invention are described in detail below with reference to the figures and the detailed description. Well-known modules, units and their interconnections, links, communications or operations with each other are not shown or described in detail. Furthermore, the described features, architectures, or functions can be combined in any manner in one or more implementations. It will be understood by those skilled in the art that the various embodiments described below are illustrative only and are not intended to limit the scope of the present invention. It will also be readily understood that the modules or units or processes of the embodiments described herein and illustrated in the figures can be combined and designed in a wide variety of different configurations.
The terms used in the embodiments are explained below, but these explanations or illustrations should not be construed as limiting the terms.
The business model refers to standardized and structured description of business.
Business model data is the relevant data that characterizes the standardized and structured description of the business. The business model data may include data models, product models, and process models, among others. Wherein, the data model can comprise entities and the like, and the product model can comprise basic products, product groups, product lines and the like. The process model can be established into five levels from macro to micro, wherein the first level is description of business processes from an enterprise perspective, the second level is description of business processes from a user perspective, the third level is description of business processes from an activity perspective, the fourth level is description of business processes from a character perspective, and the fifth level is description of business processes from a step perspective. In the process model, the third-level activity can be a section of business process, and the section of business process has a definite business purpose and can embody that a definite value is created for a client or a benefit related party. For example, "establish an electronic banking contract" and "establish a deposit contract" may both be considered a segment of a business process, belonging to a three-tier activity. The fourth-level task is to further subdivide the third-level activity, the fourth-level task is to divide the work of a section of business process corresponding to the third-level activity, and the division is based on the principles of completeness, correctness, reusability and uniqueness. The fifth stage is to further subdivide the fourth stage task, which is to divide the fourth stage task into different steps according to rules, CPC (client-Product-Channel), entity and other information records.
The application component refers to an element of an enterprise business capability model, supports business capability from an application architecture, completely inherits the range of the business component, and comprehensively meets the requirements of the business component.
Referring to fig. 1, fig. 1 is a flow chart illustrating a business model data processing method according to an embodiment of the present invention, which may include:
s101, establishing connection with a Structured Query Language (SQL) database through ADO connection, taking a list associated with business model data as input of a query result acquiring function,
s102, calling the function for obtaining the query result to obtain the service model data in the record set format,
s103, converting the obtained business model data in the record set format into a display format supported by Office.
In one embodiment, the framework of the implementation code of the method can be divided into the following parts, wherein WordCls/excelCls: and finishing the display work of the report document. ConnectorCls: and managing data connection, and acquiring a database record set through keywords. RSTConvertorCls: and modifying the obtained database record set into a format required by office display, wherein the format comprises texts, tables, pictures, lists and the like. Utilityfunction farosmql: some common logical processing methods such as file manipulation, string manipulation, lookup key, etc. The code framework of the embodiment of the invention has higher reusability and avoids the problem of repeated development of local variation.
In the embodiment of the present invention, in step S101, a list associated with the service model data that has been determined may be used as an input to obtain a Query result function getquerresult () by connecting a function getconnection () in connectctorcis with a Structured Query Language (SQL) database, where the list may be in a form of a character string.
In step S102, a function getquerresult () is called and input as a list associated with the service model data, so as to obtain the service model data in the record set format. The record set may be in the form of a database table, or may be a subset of rows or columns of a table. In a specific implementation manner, fields in different database tables can be acquired through a database view, and query results can also be acquired through a database storage process. The query result function getquerresult (querystr) of the embodiment of the invention can be a table value function, and the result list with a specific format can be obtained by setting the input parameters in the form of query character string querystr through the table value function.
The embodiment of the invention uses the view, the storage process and the function to process the data processing logic related to the business model data, achieves the effect of separating the display logic from the data acquisition logic, and can complete the data acquisition only by simple query or call in ConnectorCIs. Moreover, data acquisition is completed in a packaging function mode, when the required display result changes, the data acquisition can be completed only by modifying the query character string querystr in the function getqueryresult, and repeated development of program codes when the value requirement changes is avoided.
In step S103, the business model data in the record set format read from the SQL database is converted into a display format supported by office. In some embodiments, the record set may be converted into text, tables, pictures, lists, and the like through a function call, for example, the record set may be converted into a text format through a function change (recordset rst), the record set may be converted into a table format through a function change (recordset rst), the business model data in the record set format may be converted into an image format through a function change (recordset rst), and the business model data in the record set format may be converted into a list format through a function change (recordset rst). The formats of text, tables, pictures, lists, etc. described above, which need to be explained, each may include a specific display style.
In some embodiments, before step S101, the method may further include: and using the application component as a keyword, designating a Source workspace (Source workspace) and a target workspace (TargetWorkspace), running the macro, executing export operation, and determining a list which needs to be displayed and is associated with the service model data. The list may include: application name, change record, business constraint, technical constraint, business practice, business association relationship graph, existing application, supported base product, new requirement, system requirement, performance requirement, user experience requirement and target operation schedule. In some specific embodiments, the list may include: application name, purpose, definition, scope, change log, related business line personnel, related IT personnel, discussion log, existing process, legacy problem, primary decision, unsolved need, channel specific date, business constraint, technical constraint, management or business environment constraint, business practice, business simulation policy, other system impact, business association graph, tertiary and quaternary process profiles, process structure, inclusion, exclusion, existing system or application, existing application, business objective, end user group, supported base product, capability requirement, add-on requirement, event profile, base product supported by the application, system requirement, performance requirement, availability, user experience requirement, report specific additional requirement, target operational schedule.
The application component in the embodiment of the invention can inherit the range of the service component and can realize the requirement of the service component.
When the display format is a table, the format of the business model data after being converted may also be adjusted, for example, the table display format of the business model data may be adjusted, and one or two or three items of merging cells, setting the background color of the table, adding the header of the table, and the like may be performed.
Format adjustment may also be performed for other display formats. The adjusted business model data can generate an application component development requirement definition.
In the business model data processing method, the keywords can comprise three-level activities and four-level tasks besides application components. The specific processing method is similar to the application component, the working space and the three-level activities are used as input, the macro is operated, the export tool is executed, and the report needing to be displayed is determined, wherein the report can comprise the business activities, the involved tasks, the business events, the key quality characteristics and the electronic channels. And then, obtaining connection with a database to obtain a database record set, converting the record set into a displayable format of Excel, printing a report, adjusting the format, and generating a three-level activity model. For the five-level step, taking the working space and the four-level task as input, running a macro, executing a derivation tool, and determining a report needing to be displayed, wherein the report can comprise the task, the step, complex rules, account accounting, authorization conditions, screen certificates, policy and institutional approaches, business requirements, derivative data and the like. Determining a report needing to be displayed, obtaining connection with a database to obtain a record set of the database, converting the record set into an excel display format, then printing the report and subsequent acquisition and conversion of the database, and after all reports are printed, carrying out format adjustment to generate a five-level step flow.
In some embodiments, the method may further include: before establishing the connection with the SQL data through ADO connection, designating a source working space and a target working space by taking an application component as a keyword, running a macro, and executing difference comparison operation, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing a chart difference. In a specific implementation mode, SQL server is used as a data source, a difference information record set which is connected with a database and is associated with an application component is obtained through a VBA script, then the record set is converted into a displayable format of Excel, and adjustment of the related format is completed, so that an application component difference report can be generated by using the application component as a unit, difference contents among model asset libraries of different versions are displayed, the evolution process of the model asset libraries is tracked, and changes are displayed. In one embodiment, the macro may be run with the source workspace, the target workspace, and the application component as inputs, the difference comparison tool may be executed, the difference comparison functions may be invoked, and the comparison may be performed, where the difference comparison may include finding new and modified content, finding deleted content, and comparing chart differences. After the difference list needing to be displayed is determined, connection with a database is obtained, a record set of the database is obtained, the record set is converted into an excel display format, format adjustment is carried out, and an application component version difference report is generated.
The method for processing business model data according to the embodiment of the present invention is described above with reference to specific embodiments, and a computer device to which the above processing method is applied will be described below.
An embodiment of the present invention further provides a computer device, as shown in fig. 2, the computer device 200 may include: a memory 201, a processor 202 and a computer program stored on the memory and capable of running on the processor, wherein the number of processors may be one or more. Programs may include computer languages in the form of VBA and SQL.
The one or more processors when executing the program are capable of: establishing connection with a Structured Query Language (SQL) database through ADO connection, taking a list associated with service model data as input of a query result acquiring function, calling the query result acquiring function to acquire service model data in a record set format, and converting the acquired service model data in the record set format into a display format supported by Office. The display formats may include text, tables, pictures, and lists.
In some embodiments, execution of the programs by the one or more processors may further enable: before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, a derivation operation is executed, and a list which is required to be displayed and is associated with service model data is determined, wherein the list comprises the following items of application names, change records, service constraints, technical constraints, service practices, service association relation graphs, existing applications, supported basic products, new requirements, system requirements, performance requirements, user experience requirements and a target operation time table. The application component can inherit the scope of the business component and fulfill the requirements of the business component.
In some embodiments of the present invention, when the display format is a table, the processor executes the program to further implement: adjusting a tabular display format of business model data, the adjusting including one or more of: merging cells, setting the background color of the table and adding the header of the table.
In some embodiments of the invention, the processor executing the program may further implement: before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, and difference comparison operation is executed, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing chart differences.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present invention can be implemented by combining software and a hardware platform. With this understanding in mind, all or part of the technical solutions of the present invention that contribute to the background art may be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, a smart phone, or a network device, etc.) to execute the methods according to the embodiments or some parts of the embodiments.
The terms and expressions used in the specification of the present invention have been set forth for illustrative purposes only and are not meant to be limiting. It will be appreciated by those skilled in the art that changes could be made to the details of the above-described embodiments without departing from the underlying principles thereof. The scope of the invention is, therefore, indicated by the appended claims, in which all terms are intended to be interpreted in their broadest reasonable sense unless otherwise indicated.
Claims (10)
1. A method for processing business model data, the method comprising:
using an application component as a keyword, designating a source working space and a target working space, running a macro, executing export operation, and determining a list which needs to be displayed and is associated with business model data, wherein the application component is an element of an enterprise business capability model and is a support for business capability from an application architecture, and the application component can inherit the range of the business component and realize the requirement of the business component;
establishing connection with a Structured Query Language (SQL) database through ADO connection, and taking a list associated with business model data as input of a query result acquiring function, wherein the list associated with the business model data is in a character string form;
calling the query result acquiring function to acquire service model data in a record set format, wherein the query result function is a table value function;
and converting the obtained business model data in the record set format into a display format supported by Office.
2. The method of claim 1, wherein the display format comprises: text, tables, pictures, and lists.
3. The method of claim 1, wherein the list comprises a plurality of application names, change records, business constraints, technical constraints, business practices, business association graphs, existing applications, supported base products, new requirements, system requirements, performance requirements, user experience requirements, and target operational schedules.
4. The method of claim 2, wherein when the display format is a table, the method further comprises:
adjusting a tabular display format of business model data, the adjusting including one or more of: merging cells, setting the background color of the table and adding the header of the table.
5. The method of claim 1, further comprising:
before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, and difference comparison operation is executed to determine a list associated with service model data, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing chart differences.
6. A computer device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the processor when executing the program implements:
using an application component as a keyword, designating a source working space and a target working space, running a macro, executing export operation, and determining a list which needs to be displayed and is associated with business model data, wherein the application component is an element of an enterprise business capability model and is a support for business capability from an application architecture, and the application component can inherit the range of the business component and realize the requirement of the business component;
establishing connection with a Structured Query Language (SQL) database through ADO connection, and taking a list associated with business model data as input of a query result acquiring function, wherein the list associated with the business model data is in a character string form;
calling the query result acquiring function to acquire service model data in a record set format, wherein the query result function is a table value function;
and converting the obtained business model data in the record set format into a display format supported by Office.
7. The computer device of claim 6, wherein the display format comprises: text, tables, pictures, and lists.
8. The computer device of claim 6, wherein the list comprises a plurality of application names, change records, business constraints, technical constraints, business practices, business association graphs, existing applications, supported base products, new requirements, system requirements, performance requirements, user experience requirements, and target operational schedules.
9. The computer device of claim 7, wherein when the display format is a table, the processor when executing the program further implements:
adjusting a tabular display format of business model data, the adjusting including one or more of: merging cells, setting the background color of the table and adding the header of the table.
10. The computer device of claim 6, wherein the processor, when executing the program, further implements:
before establishing connection with a Structured Query Language (SQL) database through ADO connection, an application component is used as a keyword, a source working space and a target working space are designated, a macro is operated, and difference comparison operation is executed, wherein the difference comparison operation comprises the steps of searching for new and modified contents, searching for deleted contents and comparing chart differences.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710550601.3A CN107480186B (en) | 2017-07-07 | 2017-07-07 | Business model data processing method and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710550601.3A CN107480186B (en) | 2017-07-07 | 2017-07-07 | Business model data processing method and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107480186A CN107480186A (en) | 2017-12-15 |
| CN107480186B true CN107480186B (en) | 2021-08-27 |
Family
ID=60596620
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710550601.3A Active CN107480186B (en) | 2017-07-07 | 2017-07-07 | Business model data processing method and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107480186B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108875029A (en) * | 2018-06-22 | 2018-11-23 | 国网北京市电力公司 | Data processing method and device, storage medium and processor |
| CN109062883B (en) * | 2018-07-18 | 2022-07-26 | 平安科技（深圳）有限公司 | Data table dynamic derivation method and device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102819609A (en) * | 2012-08-23 | 2012-12-12 | 国电南京自动化股份有限公司 | Modeling method for persisting data model |
| CN105183735A (en) * | 2014-06-18 | 2015-12-23 | 阿里巴巴集团控股有限公司 | Data query method and query device |
| CN105701220A (en) * | 2016-01-14 | 2016-06-22 | 周敏 | Internal business data system and processing method of enterprise |
| CN105786937A (en) * | 2014-12-26 | 2016-07-20 | 远光软件股份有限公司 | ECP (Enterprise Cloud Platform) based universal table entity selection and conversion device and selection and conversion method |
| CN106909596A (en) * | 2016-06-23 | 2017-06-30 | 阿里巴巴集团控股有限公司 | Method for processing business, apparatus and system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080255974A1 (en) * | 2007-04-12 | 2008-10-16 | Microsoft Corporation | Techniques to manage financial performance data exchange with standard taxonomies |
| CN101854652A (en) * | 2010-06-23 | 2010-10-06 | 天元莱博(北京)科技有限公司 | Telecommunications network service performance monitoring system |
| US8874601B2 (en) * | 2010-12-17 | 2014-10-28 | Sap Ag | SADL query view—a model-driven approach to speed-up read-only use cases |
| CN103136445B (en) * | 2013-01-29 | 2015-11-04 | 浙江大学 | A kind of conversion method of openEHR information into relation database |
| CN103455325A (en) * | 2013-07-24 | 2013-12-18 | 北京起步科技有限公司 | Business-model-based architecture platform |
| CN104572894A (en) * | 2014-12-24 | 2015-04-29 | 天津南大通用数据技术股份有限公司 | Method for describing service model by utilizing XML (Extensible Markup Language) in business intelligence and business intelligence system |
| CN106802993B (en) * | 2017-01-11 | 2019-05-21 | 云南电网有限责任公司电力教育培训评价中心 | A kind of operation of the electric network swim under three-dimensional scenic shows method |
-
2017
- 2017-07-07 CN CN201710550601.3A patent/CN107480186B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102819609A (en) * | 2012-08-23 | 2012-12-12 | 国电南京自动化股份有限公司 | Modeling method for persisting data model |
| CN105183735A (en) * | 2014-06-18 | 2015-12-23 | 阿里巴巴集团控股有限公司 | Data query method and query device |
| CN105786937A (en) * | 2014-12-26 | 2016-07-20 | 远光软件股份有限公司 | ECP (Enterprise Cloud Platform) based universal table entity selection and conversion device and selection and conversion method |
| CN105701220A (en) * | 2016-01-14 | 2016-06-22 | 周敏 | Internal business data system and processing method of enterprise |
| CN106909596A (en) * | 2016-06-23 | 2017-06-30 | 阿里巴巴集团控股有限公司 | Method for processing business, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107480186A (en) | 2017-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9800675B2 (en) | Methods for dynamically generating an application interface for a modeled entity and devices thereof | |
| US10055426B2 (en) | System and method transforming source data into output data in big data environments | |
| US9659073B2 (en) | Techniques to extract and flatten hierarchies | |
| US8522195B2 (en) | Systems and methods to generate a software framework based on semantic modeling and business rules | |
| US7418453B2 (en) | Updating a data warehouse schema based on changes in an observation model | |
| US20090222749A1 (en) | Apparatus and method for automated creation and update of a web service application | |
| EP4339802A2 (en) | Methods and apparatus for integrated management of structured data from various sources and having various formats | |
| US20110295791A1 (en) | System and method for specifying metadata extension input for extending data warehouse | |
| US9229971B2 (en) | Matching data based on numeric difference | |
| US11461410B2 (en) | Case leaf nodes pointing to business objects or document types | |
| CN107506383B (en) | Audit data processing method and computer equipment | |
| Delgado et al. | Towards a unified vision of business process and organizational data | |
| CN107480186B (en) | Business model data processing method and computer equipment | |
| Carneiro et al. | X-META: A methodology for data warehouse design with metadata management. | |
| Orlovskyi et al. | Enterprise architecture modeling support based on data extraction from business process models. | |
| US20210390496A1 (en) | Method for model-based project scoring classification and reporting | |
| CN111984826B (en) | XML-based data automatic warehousing method, system, device and storage medium | |
| US20100324953A1 (en) | Method and system for determining entitlements to resources of an organization | |
| US11113664B2 (en) | Data provisioning system and method | |
| Khawla et al. | A Survey on Dynamic Business Processes and Dynamic Business Processes Modelling | |
| US9489438B2 (en) | Systems and methods for visualizing master data services information | |
| Oliveira et al. | Overcoming traditional ETL systems architectural problems using a service‐oriented approach | |
| Petersson et al. | Analysing, Designing, and Evaluating Database Schema Designs in Azure Data Explorer | |
| Belo et al. | RAID-B2K, transforming BPMN conceptual schemas into Kettle execution primitives | |
| Tippapharat et al. | Test case impact analysis for BPMN input changes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |