WO2016004814A1 - 一种业务可视化方法及系统 - Google Patents

一种业务可视化方法及系统 Download PDF

Info

Publication number
WO2016004814A1
WO2016004814A1 PCT/CN2015/081662 CN2015081662W WO2016004814A1 WO 2016004814 A1 WO2016004814 A1 WO 2016004814A1 CN 2015081662 W CN2015081662 W CN 2015081662W WO 2016004814 A1 WO2016004814 A1 WO 2016004814A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
unit
type
correspondence
page
Prior art date
Application number
PCT/CN2015/081662
Other languages
English (en)
French (fr)
Inventor
任翔
Original Assignee
阿里巴巴集团控股有限公司
任翔
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 任翔 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2016004814A1 publication Critical patent/WO2016004814A1/zh

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

Definitions

  • the present application relates to the field of computer data processing technologies, and in particular, to a service visualization method and system.
  • the traditional MVC (Model View Controller) mode allows you to access the same server-side code using a variety of different styles of views, ie accessing the same web page.
  • a user can order a product through a webpage through a computer or a mobile phone. Although the ordering process displays a different view of the webpage, the processing of ordering the product is the same.
  • Models can include data rules and data content.
  • the model generally corresponds to the business object that the application is to manage.
  • the model provides the controller with a way to process the data.
  • Usually the data returned by the model can be supplied to multiple views.
  • a view can be an interface for interacting with a user, which provides different ways of presenting model data.
  • the controller can be used to receive user requests and invoke models and views to fulfill the user's needs. Usually the controller will call the appropriate model for the task and choose the appropriate view.
  • the MVC mode application composed of the above three core components can generally be summarized as follows: the controller can receive the user's request and decide which model to call to process according to the content requested by the user.
  • the called model can process the user's request and return data to the controller based on the model's business logic.
  • the controller can receive the data returned by the model and call the corresponding view to display the data returned by the model to the user.
  • the inventor has found that at least the following problems exist in the prior art: since the model and the view are strictly separated in the MVC mode, when the service is applied to a specific service, the view cannot follow the business model. Change and change. For example, a displayable content is added to the business model, the view cannot be changed correspondingly, and the display interface of the view needs to be redesigned, thereby reducing the efficiency of the business visualization.
  • the purpose of the embodiments of the present application is to provide a service visualization method and system to improve the efficiency of generating a view corresponding to a service model.
  • the embodiment of the present application provides a service visualization method and system, which are implemented as follows:
  • a service visualization method comprising: receiving a data structure including a data rule between a base element data type and a base element; generating a correspondence corresponding to the base element according to a first correspondence between a preset data type and a page control type a page control; generating, according to a second correspondence between the preset data rule and the control rule, a constraint relationship between the page controls corresponding to the data rule between the base elements; according to the page control and the The constraint relationship between the page controls generates a view interface that displays the view interface.
  • a service visualization system comprising: a data receiving unit, a page control unit, a constraint relationship unit, and a view interface unit; wherein the data receiving unit is configured to receive a data structure including a data rule between a base element data type and a base element
  • the data type includes: a text type, a multiple-selection type, a single-selection type, or a numerical type
  • the data rule between the basic elements includes: a dependency relationship between the basic elements, a mutual exclusion relationship between the basic elements, and a basic element a parent-child relationship or a value of the basic element is defined;
  • the page control unit is configured to generate a page control corresponding to the basic element according to a first correspondence between the preset data type and the page control type
  • the control rule unit is configured to generate a constraint relationship between the page controls corresponding to the data rule between the basic elements according to the second correspondence between the preset data rule and the control rule;
  • the view interface unit The page control is configured to generate a view interface according to
  • the embodiment of the present application generates a corresponding page control of a constraint relationship according to a data structure for describing a service model, and displays a view interface formed by the page control.
  • the embodiment disclosed in the present application uses a data structure to describe a business model, and according to a correspondence between a preset data type and a page control type, and a correspondence between a data rule and a control rule, the business model and the displayed view interface are Correlation, when the business model changes, the view page can also be changed accordingly. You can improve the efficiency of generating views that correspond to business models.
  • FIG. 1 is a flow chart of an embodiment of a service visualization method of the present application
  • FIG. 2 is a schematic structural diagram of an embodiment of a service visualization system of the present application.
  • FIG. 3 is a schematic structural diagram of a page control unit in an embodiment of a business visualization system of the present application
  • FIG. 4 is a schematic structural diagram of a control rule unit in an embodiment of a service visualization system of the present application
  • FIG. 5 is a schematic structural diagram of a view interface unit in an embodiment of a service visualization system of the present application.
  • the embodiment of the present application provides a service visualization method and system.
  • FIG. 1 is a flow chart of an embodiment of a service visualization method of the present application.
  • the method of business visualization can include:
  • S101 Receive a data structure including a data rule between a base element data type and a base element.
  • a business model can typically include multiple objects, and control rules can exist between the objects.
  • an object included in an order model can include: customer name, order number, order time, and order amount.
  • customer name can have multiple order numbers, and each order number can have a corresponding order time and order amount.
  • Data structures can be used to describe business models.
  • the data structure may include: a base element, a data type of the base element, and a data rule between the base elements.
  • the base element can be used to describe objects in a business model.
  • the data type can be used to represent an attribute of the base element.
  • the data type may include a text type, a multiple selection type, a single selection type, or a numerical type.
  • the data type can be represented by a first identity in the data structure. For example, the first identifier of a certain basic element may be set to "txt" to indicate that the base element is an element of a text type.
  • the data rules can be used to describe control rules between objects in a business model, and correspondingly, the data rules can be used to represent constraints between basic elements in a data structure.
  • the data rule may include: a dependency relationship between the basic elements, a mutually exclusive relationship or a parent-child relationship, and a limitation on the value of the base element.
  • the data rules can be represented by a second identity in the data structure.
  • the computer can receive a data structure including the first identification and the second identification.
  • a business model for user account information for the business model, the basic elements in the data structure may include: a user name, a user account, whether the user account is contracted, and an interface owned by the account. among them,
  • the user name may be a basic element of a text type.
  • the basic element of the user name may be used to store user name information, and the default value of the basic element of the user name may be a null value.
  • the first identifier in the attribute of the base element of the user name can be set to "txt".
  • the user account may be a basic element of a multi-selection type, and the user account may store a list of accounts owned by the merchant.
  • the first identifier of the attribute of the basic element of the user account can be set to "checkbox".
  • the optional value of the user account may include: interface 1, interface 2, and/or interface 3.
  • Whether the user account is signed or not may be a single-selection element, and whether the user signs a contract may store the subscription information of an account of the user. You can set whether the first identifier in the attribute of the underlying element is "radio". Whether the user account signing optional value may include: yes or no.
  • the data rule may include: the interface of the user account and the interface 1, the interface 2, and the interface 3 may be a parent-child relationship.
  • the user account has a dependency relationship with the user account.
  • the interface 1, the interface 2, and the interface 3 owned by the user account are all dependent on the user's A account and are controlled by the user A account.
  • Whether the user account is signed and "yes” or “no” may be a parent-child relationship.
  • the "yes” and "no” may be mutually exclusive relationships.
  • S102 Generate a page control corresponding to the data structure according to a first correspondence between the preset data type and the page control type.
  • a page control can be included on the view interface that interacts with the user.
  • the page controls on the view interface may correspond to base elements in the data structure.
  • the type of page control on the view interface may correspond to a data type in the data structure.
  • the constraint relationship between the page controls on the view interface may correspond to data rules in the data structure.
  • the computer can receive the preset first correspondence.
  • the first correspondence may include: a first correspondence between a data type and a page control type.
  • the first correspondence between the data type and the page control type may include: a correspondence between all data types in the domain and all page control types.
  • the type of the page control corresponding to the basic element of the text type may be a text box
  • the type of the page control corresponding to the multi-selected basic element may be a multi-selection box
  • the type of the page control corresponding to the basic element of the single-selection type may be Single box.
  • the type of the page control corresponding to the base element of the numeric type can be a value box.
  • a page control corresponding to the base element may be generated according to the first correspondence.
  • the first correspondence and the first identifier in the data structure may be utilized to generate a page control corresponding to the basic element.
  • the data structure can be used to describe a business model, and the generated page control can correspond to a business model.
  • the text-based base element "user name” can generate a text box for entering text.
  • the multi-selection type of element "user account” can generate a checkbox containing a list of user accounts.
  • S103 Generate a constraint relationship between page controls corresponding to the data rule between the basic elements according to a second correspondence between the preset data rule and the control rule.
  • the computer can receive a preset second correspondence.
  • the second correspondence may include a data rule and a control rule The second correspondence between them.
  • the control rules are used to represent a constraint relationship between page controls.
  • the second correspondence between the data rule and the control rule may include: a correspondence between all data rules in the domain and all control rules.
  • a data rule with dependencies or mutually exclusive relationships between basic elements may correspond to a cascading relationship control rule between page controls; a data rule with parent-child relationships between base elements may correspond to a parent-child layer relationship control rule between page controls
  • the data rule that defines the value of the base element may correspond to the value check form control rule of the page control, for example, may correspond to a check of a mailbox format or a numerical precision.
  • a constraint relationship between page controls corresponding to the data rule between the basic elements may be generated.
  • the second correspondence and the second identifier in the data structure may be utilized to generate a constraint relationship between page controls corresponding to the data rule between the base elements.
  • the parent-child relationship in the data rule may correspond to the parent-child relationship in the control rule; then the interface list and the interface 1, the interface 2, and the interface 3 are parent-child relationships, and the interface is represented as an interface in the page control. 1. Interface 2 and Interface 3 are sublayers of the interface list.
  • S104 Generate a view interface according to a constraint relationship between the page control and the page control, and display the view interface.
  • the computer may form the view interface according to a constraint relationship between the page controls.
  • the view interface is used for interaction between a computer and a user.
  • the computer can display the view interface.
  • the view interface may include a text box corresponding to a basic element of a text type, a concatenated radio box corresponding to a single-type basic element of a mutually exclusive relationship, and the like.
  • the interface list owned by the user account A includes: interface 1, interface 2, and interface 3.
  • the effect displayed on the view interface may be: the interface list owned by the account A is controlled by the account A.
  • the interface list owned by the account A can be displayed, and the next layer of the interface list is the multi-selectable interface 1. Interface 2 and interface 3.
  • the data structure is used to describe a business model.
  • the page control can correspond to a base element in the data structure.
  • the type of the page control may correspond to a data type in the data structure.
  • the constraint relationship between the page controls may correspond to data rules in the data structure.
  • the view interface displayed according to the constraint relationship between the page control and the page control may correspond to the business model.
  • the objects in the model may include: customer name, customer order number, and order amount.
  • the customer order number can be controlled by the customer's name, which can include multiple order numbers.
  • Each order can contain a corresponding order amount.
  • the data structure used to describe the above business model may include a base element "customer name” of the text type, a base element “customer order number” of the multiple-selection type, and a base element “order amount” of the numerical type.
  • the data rule between the basic elements may include: the optional value of the basic element "customer order number” may include: “order 1" and "order 2".
  • the base element "customer order number” may depend on the base element "customer name”, which may depend on the base element "customer order number”.
  • the base elements "customer order number” and “order 1” may be parent-child relationships, and the "customer order number” and “order 2" may be parent-child relationships.
  • the first correspondence between the preset data type and the page control type may include: the type of the page control corresponding to the basic element of the text type may be a text box, and the type of the page control corresponding to the multi-selected basic element may be a multi-selection box
  • the type of the page control corresponding to the basic element of the single selection type may be a radio button.
  • the type of the page control corresponding to the base element of the numeric type can be a value box.
  • a page control corresponding to the base element can be generated.
  • the page control may include: a text box "customer name”, a multi-select box “customer order number”, and a value box "order amount”.
  • the second corresponding relationship between the preset data rule and the control rule may include: a dependency relationship between the basic elements may correspond to a cascading relationship between the page controls; a parent-child relationship between the basic elements may correspond to between the page controls Parent-child relationship; the value of the base element is limited to the value of the page control.
  • a constraint relationship between page controls corresponding to data rules between the basic elements may be generated.
  • the constraint relationship between the page controls may include: a multi-select box "customer order number” and a text box "customer name” are cascaded; a sub-layer “customer order number” sub-layer includes an order number list "order 1 And “Order 2"; check the value box "Order Amount", for example, the value in the value box should be greater than or equal to 0.
  • the computer can generate a view interface and display according to the constraint relationship between the generated page control and the page control.
  • the "customer age” associated with the "customer name” is added to the business model, and the value of "customer age” is greater than zero.
  • the base element "customer age” of the numeric type can be added to the data structure used to describe the business model, which depends on the base element "customer name”.
  • the view interface can also be changed accordingly.
  • the value box "customer age” can be added to the original view interface.
  • a constraint relationship between the value box "customer age” and other page controls can be generated.
  • the value box "customer age” may be in a cascading relationship with the text box "customer name”, and the value box "customer age” is checked for value, and the value in the value box is verified to be greater than zero.
  • the business visualization method disclosed in the present application generates a corresponding page control of a constraint relationship according to a data structure for describing a business model, and displays a view interface formed by the page control.
  • the business visualization method of the present application adopts a data structure to describe a business model, and according to a correspondence between a preset data type and a page control type, and a correspondence between a data rule and a control rule, the business model and the displayed view
  • the interfaces are related.
  • the data structure used to describe the business model changes, and the view page can also change with the data structure. You can improve the efficiency of generating views that correspond to business models.
  • FIG. 2 is a schematic structural diagram of an embodiment of a service visualization system of the present application.
  • the business visualization system may include: a data receiving unit 100, a page control unit 200, a constraint relationship unit 300, and a view interface unit 400. among them,
  • the data receiving unit 100 may be configured to receive a data structure including a data rule between a base element data type and a base element.
  • the data structure can include a base element for describing a business model, a data type of the base element, and a data rule.
  • the data type may include: a text type, a multiple selection type, a single selection type, or a numerical type.
  • the data rules between the basic elements may include: a dependency relationship between the basic elements, a mutual exclusion relationship between the basic elements, a parent-child relationship between the basic elements, or a value definition of the basic elements.
  • the page control unit 200 may be configured to generate a page control corresponding to the basic element according to a first correspondence between a preset data type and a page control type.
  • FIG. 3 is a schematic structural diagram of a page control unit in an embodiment of a business visualization system of the present application.
  • the page control unit 200 may include: a first correspondence unit 210 and a page control generating unit 220. among them,
  • the first correspondence unit 210 may be configured to receive a first correspondence between a preset data structure and a page control type.
  • the page control generating unit 220 may be configured to generate a page control according to the preset first correspondence relationship received by the first correspondence unit 210.
  • the page control corresponds to a base element in the data receiving unit 100.
  • the control rule unit 300 may be configured to generate a constraint relationship between the page controls corresponding to the data rule between the basic elements according to the second correspondence between the preset data rule and the control rule.
  • the constraint relationship unit 300 may include: a second correspondence relationship unit 310 and a constraint relationship generation unit 320. among them,
  • the second correspondence unit 310 may be configured to receive a second correspondence between a preset data rule and a control rule. relationship.
  • the constraint relationship generating unit 320 may be configured to generate a constraint relationship between the page controls of the page control unit 200 according to the preset second correspondence relationship received by the second correspondence unit 310.
  • the constraint relationship between the page controls corresponds to a data rule between the base elements received in the data receiving unit 100.
  • the view interface unit 400 may be configured to generate, by the page control, a view interface according to a constraint relationship between the page controls, and display the view interface.
  • FIG. 5 is a schematic structural diagram of a view interface unit in an embodiment of a service visualization system of the present application.
  • the view interface unit 400 may include: a view interface generating unit 410 and a view interface display unit 420.
  • the view interface generating unit 410 may be configured to generate a view interface according to a constraint relationship between the page control generated by the page control unit 200 and the generated page control of the constraint relationship unit 300.
  • the view interface display unit 420 can be configured to display the view interface generated by the view interface generating unit 410.
  • the business visualization system embodiment disclosed in the present application corresponds to the business visualization method embodiment.
  • the page control corresponding to the constrained relationship is generated according to the data structure used to describe the business model, and the business model is associated with the displayed view interface.
  • the view page can also be changed accordingly. You can improve the efficiency of generating views that correspond to business models.
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller can be implemented in any suitable manner, for example, the controller can take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (eg, software or firmware) executable by the (micro)processor.
  • computer readable program code eg, software or firmware
  • examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, The Microchip PIC18F26K20 and the Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic.
  • the controller can be logically programmed by means of logic gates, switches, ASICs, programmable logic controllers, and embedding.
  • Such a controller can therefore be considered a hardware component, and the means for implementing various functions included therein can also be considered as a structure within the hardware component.
  • a device for implementing various functions can be considered as a software module that can be both a method of implementation and a structure within a hardware component.
  • the system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function.
  • the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, portions of the technical solution of the present application that contribute substantially or to the prior art may be embodied in the form of a software product.
  • the computing device includes one or more processors (CPU ), input / output interface, network interface and memory.
  • the computer software product can include instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
  • the computer software product can be stored in a memory, which may include non-persistent memory, random access memory (RAM), and/or nonvolatile memory in a computer readable medium, such as read only memory (ROM) or Flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media including both permanent and non-permanent, removable and non-removable media can be implemented by any method or technology Information storage.
  • the information can be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically erasable programmable read only memory
  • flash memory or other memory technology
  • compact disk read only memory CD-ROM
  • DVD digital versatile disk
  • Magnetic tape cartridges magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include transitory computer readable media, such as modulated data signals and carrier waves.
  • This application can be used in a variety of general purpose or special purpose computer system environments or configurations.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

一种业务可视化方法及系统，所述方法包括：接收包含基础元素数据类型和基础元素之间数据规则的数据结构（S101）；根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件（S102）；根据预设的数据规则与控制规则之间的第二对应关系，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系（S103）；根据所述页面控件和所述页面控件之间的约束关系生成视图界面，显示所述视图界面（S104）。采用数据结构描述业务模型，利用数据结构中数据类型和页面控件类型的对应关系，以及数据规则与控制规则的对应关系，将业务模型与视图界面关联起来，当业务模型发生改变时，视图页面也可以相应地改变。

Description

一种业务可视化方法及系统 技术领域
本申请涉及计算机数据处理技术领域，特别涉及一种业务可视化方法及系统。
背景技术
随着技术的不断进步，现在需要用越来越多的方式来访问应用程序。例如需要用手机、台式电脑、平板电脑等不同的电子设备来访问同一个网页。
传统的MVC(Model View Controller，模型-视图-控制)模式可以实现使用各种不同样式的视图来访问同一个服务器端的代码，即访问同一个网页。例如，用户可以通过计算机或者手机通过某个网页来订购产品，虽然订购过程显示的网页视图不一样，但订购产品的处理过程是一样的。
利用传统的MVC模式设计的应用程序将输入、处理和输出分开，使MVC模式的应用程序被分为三个核心部件：模型、视图、控制器。上述三个核心部件各自处理各自的任务。其中，
模型可以包括数据规则和数据内容。所述模型一般对应于应用程序所要管理的业务对象。所述模型给控制器提供处理数据的方式。通常模型返回的数据可以提供给多个视图。
视图可以是用于与用户进行交互的界面，它提供了展示模型数据的不同方式。
控制器可以用于接收用户的请求并调用模型和视图去完成用户的需求。通常控制器会为任务调用合适的模型，以及选择合适的视图。
由上述三个核心部件构成的MVC模式的应用程序，其处理数据的过程一般可以概括为：控制器可以接收用户的请求，并根据用户请求的内容决定调用哪个模型来处理。被调用的模型可以根据模型的业务逻辑来处理用户的请求并返回数据至控制器。控制器可以接收模型返回的数据，并调用相应的视图来展示模型返回的数据给用户。
在实现本申请过程中，发明人发现现有技术中至少存在如下问题：由于MVC模式中，模型和视图要严格的分离，因此在应用于具体的业务实现业务可视化时，视图不能随业务模型的改变而改变。例如业务模型中增加了一个可显示的内容，视图不能相应地发生改变，需要重新设计视图的显示界面，降低了业务可视化的实现效率。
发明内容
本申请实施例的目的是提供一种业务可视化方法及系统，以提高生成与业务模型对应的视图的效率。
为解决上述技术问题，本申请实施例提供一种业务可视化方法及系统是这样实现的：
一种业务可视化方法，包括：接收包含基础元素数据类型和基础元素之间数据规则的数据结构；根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件；根据预设的数据规则与控制规则之间的第二对应关系，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系；根据所述页面控件和所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
一种业务可视化系统，包括：数据接收单元、页面控件单元、约束关系单元和视图界面单元；其中，所述数据接收单元，用于接收包含基础元素数据类型和基础元素之间数据规则的数据结构；所述数据类型包括：文本类型、多选类型、单选类型或数值类型；所述基础元素之间数据规则包括：基础元素之间的依赖关系、基础元素之间的互斥关系、基础元素之间的父子关系或对基础元素的值进行限定；所述页面控件单元，用于根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件；所述控制规则单元，用于根据预设的数据规则与控制规则之间的第二对应关系生成与基础元素之间数据规则相对应的页面控件之间的约束关系；所述视图界面单元，用于所述页面控件根据所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
由以上本申请实施例提供的技术方案可见，本申请实施例根据用于描述业务模型的数据结构生成对应的有约束关系的页面控件，显示所述页面控件形成的视图界面。本申请公开的实施例，采用数据结构描述业务模型，根据预设的数据类型和页面控件类型之间的对应关系，以及数据规则与控制规则之间的对应关系，将业务模型与显示的视图界面关联起来，当业务模型发生改变时，视图页面也可以相应地改变。可以提高生成与业务模型对应的视图的效率。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本申请业务可视化方法一个实施例的流程图；
图2是本申请业务可视化系统一个实施例的组成结构示意图；
图3是本申请业务可视化系统实施例中页面控件单元的组成结构示意图；
图4是本申请业务可视化系统实施例中控制规则单元的组成结构示意图；
图5是本申请业务可视化系统实施例中视图界面单元的组成结构示意图。
具体实施方式
本申请实施例提供一种业务可视化方法及系统。
为了使本技术领域的人员更好地理解本申请中的技术方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
图1是本申请业务可视化方法一个实施例的流程图。如图1所示，业务可视化的方法可以包括：
S101：接收包含基础元素数据类型和基础元素之间数据规则的数据结构。
一个业务模型中通常可以包括多个对象，所述对象之间可以存在控制规则。例如，一个订单模型中包含的对象可以包括：客户名称、订单号、订单时间、订单金额。一个客户名称可以拥有多个订单号，每个订单号可以有对应的订单时间和订单金额。
数据结构可以用于描述业务模型。所述数据结构可以包括：基础元素、基础元素的数据类型和基础元素之间的数据规则。
所述基础元素可以用于描述业务模型中的对象。所述数据类型可以用于表示基础元素的一个属性。所述数据类型可以包括文本类型、多选类型、单选类型或数值类型等。所述数据类型可以利用数据结构中的第一标识来表示。例如可以设定某一基础元素的第一标识为“txt”来表示该基础元素为文本类型的元素。
所述数据规则可以用于描述业务模型中对象之间的控制规则，相应地，所述数据规则可以用于表示数据结构中基础元素之间的约束关系。通常所述数据规则可以包括：基础元素之间的依赖关系、互斥关系或父子关系，以及对基础元素的值的限定。所述数据规则可以利用数据结构中的第二标识来表示。
计算机可以接收包含第一标识和第二标识的数据结构。
例如，一个关于用户账号信息的业务模型，对于该业务模型，数据结构中的基础元素可以包括：用户名称、用户账号、用户账号是否签约，以及账号拥有的接口。其中，
所述用户名称可以是文本型的基础元素。所述用户名称这一基础元素可以用于存放用户名称信息，所述用户名称这一基础元素的默认值可以是空值。可以设置用户名称这一基础元素的属性中第一标识为“txt”。
所述用户账号可以是多选型的基础元素，所述用户账号可以存放该商户所拥有的账号列表。可以设置用户账号这一基础元素的属性中第一标识为“checkbox”。所述用户账号的可选值可以包括：接口1、接口2和/或接口3。
所述用户账号是否签约可以是单选型的元素，所述用户是否签约可以存放该用户某一账号的签约信息。可以设置是否签约这一基础元素的属性中第一标识为“radio”。所述用户账号是否签约可选值可以包括：“是”或者“否”。
该业务模型中，数据规则可以包括：所述用户账号的接口与接口1、接口2、接口3可以是父子关系。所述用户的账号与用户账号拥有的接口为依赖关系，例如用户账号拥有的接口1、接口2、接口3都依赖于用户的A账号，受到用户A账号的控制。所述用户账号是否签约与“是”、“否”可以是父子关系。所述“是”和“否”可以是互斥关系。
S102：根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述数据结构对应的页面控件。
与用户交互的视图界面上可以包括页面控件。所述视图界面上的页面控件可以对应于所述数据结构中的基础元素。所述视图界面上页面控件的类型可以对应于所述数据结构中的数据类型。所述视图界面上页面控件之间的约束关系可以对应于所述数据结构中的数据规则。
计算机可以接收预设的第一对应关系。所述第一对应关系可以包括：数据类型与页面控件类型之间的第一对应关系。所述数据类型与页面控件类型之间的第一对应关系可以包括：本领域所有数据类型与所有页面控件类型之间的对应关系。
例如，文本型的基础元素对应的页面控件的类型可以是文本框，多选型的基础元素对应的页面控件的类型可以是多选框，单选型的基础元素对应的页面控件的类型可以是单选框。数值类型的基础元素对应的页面控件的类型可以是数值框。
根据所述第一对应关系可以生成与所述基础元素对应的页面控件。具体地，可以利用所述第一对应关系和所述数据结构中的第一标识，生成与所述基础元素对应的页面控件。所述数据结构可以用于描述业务模型，所述生成的页面控件可以与业务模型相对应。
例如，文本型的基础元素“用户名称”可以生成用于输入文本的文本框。多选类型的基础元素“用户账号”可以生成一个包含用户账号列表的多选框。
S103：根据预设的数据规则与控制规则之间的第二对应关系，生成与所述基础元素之间数据规则对应的页面控件之间的约束关系。
计算机可以接收预设的第二对应关系。所述第二对应关系可以包括数据规则与控制规则 之间的第二对应关系。所述控制规则用于表示页面控件之间的约束关系。所述数据规则与控制规则之间的第二对应关系可以包括：本领域所有数据规则与所有控制规则之间的对应关系。
例如，基础元素之间为依赖或互斥关系的数据规则可以对应页面控件之间的级联关系控制规则；基础元素之间为父子关系的数据规则可以对应页面控件之间的父子层关系控制规则；对基础元素进行值的限定的数据规则可以对应页面控件的值校验形式控制规则，例如可以对应为邮箱格式或数字精度的校验。
根据所述第二对应关系，可以生成与所述基础元素之间数据规则对应的页面控件之间的约束关系。具体地，可以利用所述第二对应关系和所述数据结构中的第二标识，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系。
例如，在建立的第二对应关系中，数据规则中的父子关系可以对应控制规则中的父子层关系；那么接口列表与接口1、接口2、接口3为父子关系，在页面控件中表现为接口1、接口2和接口3为接口列表的子层。
S104：根据所述页面控件和所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
根据生成的所述页面控件和所述页面控件之间的约束关系，计算机可以将所述页面控件按照所述页面控件之间的约束关系形成视图界面。所述视图界面用于计算机与用户之间的交互。计算机可以显示所述视图界面。
所述视图界面可以包括文本类型的基础元素对应的文本框、互斥关系的单选型基础元素对应的级联的单选框等。
例如，数据描述的业务模型中，用户帐号A拥有的接口列表包括：接口1、接口2和接口3。则视图界面显示的效果可以是：帐号A拥有的接口列表受到账号A的控制，当选择账号A时，可以显示账号A拥有的接口列表，接口列表的下一层为可多选的接口1、接口2和接口3。
所述数据结构用于描述业务模型。所述页面控件可以与数据结构中的基础元素相对应。所述页面控件的类型可以与数据结构中的数据类型相对应。所述页面控件之间的约束关系可以与数据结构中的数据规则相对应。根据所述页面控件和页面控件之间的约束关系所显示的视图界面可以与业务模型相对应。
举个例子来说明：
关于客户订单的业务模型，模型中的对象可以包括：客户姓名、客户订单号、订单金额。 客户订单号可以受到客户姓名的控制，客户订单号中可以包括多个订单号。每一订单可以包含一个对应的订单金额。
用于描述上述业务模型的数据结构可以包括：文本类型的基础元素“客户姓名”、多选类型的基础元素“客户订单号”和数值类型的基础元素“订单金额”。其中，基础元素之间的数据规则可以包括：所述基础元素“客户订单号”可选的值可以包括：“订单1”和“订单2”。所述基础元素“客户订单号”可以依赖于基础元素“客户姓名”，所述基础元素“订单金额”可以依赖于基础元素“客户订单号”。所述基础元素“客户订单号”与“订单1”可以是父子关系，所述“客户订单号”与“订单2”可以是父子关系。
预设的数据类型与页面控件类型的第一对应关系可以包括：文本型的基础元素对应的页面控件的类型可以是文本框，多选型的基础元素对应的页面控件的类型可以是多选框，单选型的基础元素对应的页面控件的类型可以是单选框。数值类型的基础元素对应的页面控件的类型可以是数值框。
根据上述的第一对应关系，可以生成与基础元素对应的页面控件。所述页面控件可以包括：文本框“客户姓名”、多选框“客户订单号”和数值框“订单金额”。
预设的数据规则与控制规则的第二对应关系可以包括：基础元素之间为依赖关系的可以对应页面控件之间的级联关系；基础元素之间为父子关系的可以对应页面控件之间的父子层关系；对基础元素进行值限定的可以对应页面控件的值校验形式。
根据上述的第二对应关系，可以生成与基础元素之间数据规则对应的页面控件之间的约束关系。所述页面控件之间的约束关系可以包括：多选框“客户订单号”与文本框“客户姓名”为级联关系；多选框“客户订单号”的子层包括订单号列表“订单1”和“订单2”；对数值框“订单金额”进行值校验，例如数值框中的值要大于或等于0。
计算机可以根据上述生成的页面控件和页面控件之间的约束关系，生成视图界面并显示。
当业务模型发生变化时，例如，业务模型中增加了与“客户姓名”相关联的“客户年龄”，“客户年龄”的值大于0。相应地，用于描述业务模型的数据结构中可以增加数值类型的基础元素“客户年龄”，该基础元素依赖于基础元素“客户姓名”。
所述数据结构发生变化后，视图界面也可以相应地改变。根据预设的第一对应关系，原视图界面上可以增加数值框“客户年龄”。根据预设的第二对应关系，可以生成数值框“客户年龄”与其他页面控件的约束关系。例如，数值框“客户年龄”可以与文本框“客户名称”为级联关系，并对所述数值框“客户年龄”进行值校验，校验该数值框中的数值大于0。
本申请公开的业务可视化方法，根据用于描述业务模型的数据结构生成对应的有约束关系的页面控件，显示所述页面控件形成的视图界面。本申请的业务可视化方法，采用数据结构来描述业务模型，根据预设的数据类型和页面控件类型之间的对应关系，以及数据规则与控制规则之间的对应关系，将业务模型与显示的视图界面关联起来，当业务模型发生改变时，用于描述业务模型的数据结构也发生改变，视图页面也可以随数据结构相应地改变。可以提高生成与业务模型对应的视图的效率。
图2是本申请业务可视化系统一个实施例的组成结构示意图。如图2所示，所述业务可视化系统可以包括：数据接收单元100、页面控件单元200、约束关系单元300和视图界面单元400。其中，
所述数据接收单元100，可以用于接收包含基础元素数据类型和基础元素之间数据规则的数据结构。
所述数据结构可以包括用于描述业务模型的基础元素、所述基础元素的数据类型和数据规则。所述数据类型可以包括：文本类型、多选类型、单选类型或数值类型。
所述基础元素之间的数据规则可以包括：基础元素之间的依赖关系、基础元素之间的互斥关系、基础元素之间的父子关系或对基础元素进行值限定。
所述页面控件单元200，可以用于根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件。
图3是本申请业务可视化系统实施例中页面控件单元的组成结构示意图。如图3所示，所述页面控件单元200，可以包括：第一对应关系单元210和页面控件生成单元220。其中，
所述第一对应关系单元210，可以用于接收预设的数据结构与页面控件类型之间的第一对应关系。
所述页面控件生成单元220，可以用于根据第一对应关系单元210接收的预设第一对应关系生成页面控件。所述页面控件与数据接收单元100中的基础元素相对应。
所述控制规则单元300，可以用于根据预设的数据规则与控制规则之间的第二对应关系生成与基础元素之间数据规则相对应的页面控件之间的约束关系。
图4是本申请业务可视化系统实施例中控制规则单元的组成结构示意图。如图4所示，所述约束关系单元300，可以包括：第二对应关系单元310和约束关系生成单元320。其中，
所述第二对应关系单元310，可以用于接收预设的数据规则与控制规则之间的第二对应 关系。
所述约束关系生成单元320，可以用于根据第二对应关系单元310接收的预设第二对应关系，生成所述页面控件单元200的中页面控件之间的约束关系。所述页面控件之间的约束关系与数据接收单元100中接收的基础元素之间的数据规则相对应。
所述视图界面单元400，可以用于所述页面控件根据所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
图5是本申请业务可视化系统实施例中视图界面单元的组成结构示意图。如图5所示，所述视图界面单元400，可以包括：视图界面生成单元410、视图界面显示单元420。
所述视图界面生成单元410，可以用于根据页面控件单元200生成的页面控件和约束关系单元300的生成的页面控件之间的约束关系，生成视图界面。
所述视图界面显示单元420，可以用于显示所述视图界面生成单元410生成的视图界面。
本申请公开的业务可视化系统实施例与业务可视化方法实施例相对应。根据用于描述业务模型的数据结构生成对应的有约束关系的页面控件，将业务模型与显示的视图界面关联起来，当业务模型发生改变时，视图页面也可以相应地改变。可以提高生成与业务模型对应的视图的效率。
在20世纪90年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device,PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片2。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、 Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog2。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。
本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本申请时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
通过以上的实施方式的描述可知，本领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。该计算机软件产品可以包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例或者实施例的某些部分所述的方法。该计算机软件产品可以存储在内存中，内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现 信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括短暂电脑可读媒体(transitory media)，如调制的数据信号和载波。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
本申请可用于众多通用或专用的计算机系统环境或配置中。例如：个人计算机、服务器计算机、手持设备或便携式设备、平板型设备、多处理器系统、基于微处理器的系统、置顶盒、可编程的消费电子设备、网络PC、小型计算机、大型计算机、包括以上任何系统或设备的分布式计算环境等等。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
虽然通过实施例描绘了本申请，本领域普通技术人员知道，本申请有许多变形和变化而不脱离本申请的精神，希望所附的权利要求包括这些变形和变化而不脱离本申请的精神。

Claims (11)

  1. 一种业务可视化方法，其特征在于，包括：
    接收包含基础元素数据类型和基础元素之间数据规则的数据结构；
    根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件；
    根据预设的数据规则与控制规则之间的第二对应关系，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系；
    根据所述页面控件和所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
  2. 如权利要求1所述的一种业务可视化方法，其特征在于，所述数据类型采用第一标识表示；相应地，
    根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件；具体包括：利用所述第一对应关系和所述数据结构中的第一标识，生成与所述基础元素对应的页面控件。
  3. 如权利要求1所述的一种业务可视化方法，其特征在于，所述数据规则采用第二标识表示；相应地，
    根据预设的数据规则与控制规则之间的第二对应关系，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系；具体包括：利用所述第二对应关系和所述数据结构中的第二标识，生成与所述基础元素之间数据规则相对应的页面控件之间的约束关系。
  4. 如权利要求1所述的一种业务可视化方法，其特征在于，所述基础元素数据类型包括下述中的至少一种：文本类型、单元类型、多选类型、数值类型。
  5. 如权利要求4所述的一种业务可视化方法，其特征在于，所述数据类型与页面控件类型的第一对应关系包括下述中的至少一种：
    文本类型与文本框对应的关系；多选类型与多选框对应的关系；单选类型与单选框对应的关系；数值类型与验证框的对应关系。
  6. 如权利要求1所述的一种业务可视化方法，其特征在于，所述基础元素之间数据规则包括下述中的至少一种：基础元素之间的依赖关系、基础元素之间的互斥关系、基础元素 之间的父子关系、对基础元素进行值的限定。
  7. 如权利要求6所述的一种业务可视化方法，其特征在于，所述数据规则与控制规则之间的第二对应关系至少包括下述中的一种：
    基础元素之间为依赖或互斥关系的数据规则对应页面控件之间的级联关系控制规则；
    基础元素之间为父子关系的数据规则对应页面控件之间的父子层关系控制规则；
    对基础元素进行值的限定的数据规则对应页面控件的值校验形式控制规则。
  8. 一种业务可视化系统，其特征在于，包括：数据接收单元、页面控件单元、约束关系单元和视图界面单元；其中，
    所述数据接收单元，用于接收包含基础元素数据类型和基础元素之间数据规则的数据结构；所述数据类型包括：文本类型、多选类型、单选类型或数值类型；所述基础元素之间数据规则包括：基础元素之间的依赖关系、基础元素之间的互斥关系、基础元素之间的父子关系或对基础元素的值进行限定；
    所述页面控件单元，用于根据预设的数据类型与页面控件类型之间的第一对应关系，生成与所述基础元素对应的页面控件；
    所述控制规则单元，用于根据预设的数据规则与控制规则之间的第二对应关系生成与基础元素之间数据规则相对应的页面控件之间的约束关系；
    所述视图界面单元，用于所述页面控件根据所述页面控件之间的约束关系生成视图界面，显示所述视图界面。
  9. 如权利要求8所述的一种业务可视化系统，其特征在于，所述页面控件单元包括：第一对应关系单元和页面控件生成单元；其中，
    所述第一对应关系单元，用于接收预设的数据结构与页面控件类型之间的第一对应关系；
    所述页面控件生成单元，用于根据第一对应关系单元接收的预设第一对应关系生成页面控件。
  10. 如权利要求8所述的一种业务可视化系统，其特征在于，所述约束关系单元包括：第二对应关系单元和约束关系生成单元；其中，
    所述第二对应关系单元，用于接收预设的数据规则与控制规则之间的第二对应关系；
    所述约束关系生成单元，用于根据第二对应关系单元接收的预设第二对应关系，生成所述页面控件单元中页面控件之间的约束关系。
  11. 如权利要求8所述的一种业务可视化系统，其特征在于，所述视图界面单元包括：视图界面生成单元和视图界面显示单元；其中，
    所述视图界面生成单元，用于根据页面控件单元生成的页面控件和约束关系单元生成的页面控件之间的约束关系，生成视图界面；
    所述视图界面显示单元，用于显示所述视图界面生成单元生成的视图界面。
PCT/CN2015/081662 2014-07-09 2015-06-17 一种业务可视化方法及系统 WO2016004814A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410325446.1A CN105335389B (zh) 2014-07-09 2014-07-09 一种业务可视化方法及系统
CN201410325446.1 2014-07-09

Publications (1)

Publication Number Publication Date
WO2016004814A1 true WO2016004814A1 (zh) 2016-01-14

Family

ID=55063566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/081662 WO2016004814A1 (zh) 2014-07-09 2015-06-17 一种业务可视化方法及系统

Country Status (2)

Country Link
CN (1) CN105335389B (zh)
WO (1) WO2016004814A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107066457B (zh) * 2016-08-23 2019-12-17 平安科技（深圳）有限公司 用户信息视图构建方法和系统
CN109992266B (zh) * 2017-12-29 2022-07-19 阿里巴巴集团控股有限公司 一种界面元素的处理方法和装置
CN110309034B (zh) * 2019-06-13 2023-05-16 阿里巴巴集团控股有限公司 业务流转链路视图生成方法及装置
CN110636016B (zh) * 2019-08-08 2023-09-29 西安万像电子科技有限公司 数据传输方法及系统
CN111459482A (zh) * 2020-03-27 2020-07-28 山东浪潮通软信息科技有限公司 一种界面定制控制方法、系统和软件
CN112000911B (zh) * 2020-07-08 2024-01-02 北京达佳互联信息技术有限公司 页面管理方法、装置、电子设备以及存储介质
CN112328341B (zh) * 2020-10-23 2021-07-23 前海飞算云创数据科技(深圳)有限公司 模型显示方法，装置，电子设备及存储介质
CN113553097B (zh) * 2021-07-30 2022-11-18 上海玳鸽信息技术有限公司 模型版本管理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090319548A1 (en) * 2008-06-20 2009-12-24 Microsoft Corporation Aggregation of data stored in multiple data stores
CN101901262A (zh) * 2010-07-26 2010-12-01 北京新洲协同软件技术有限公司 基于面向对象模型的企业建库和业务数据显示的方法
CN102830973A (zh) * 2012-08-14 2012-12-19 无锡哲勤科技有限公司 海量数据下Web应用开发双层MVC的方法和分层结构
CN103309964A (zh) * 2013-06-03 2013-09-18 广州市香港科大霍英东研究院 一种针对大规模交通数据的高效可视监测分析系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1924857B (zh) * 2006-04-27 2010-10-06 南京联创科技集团股份有限公司 复杂业务驱动的多层动态页面设计方法
CN101661508B (zh) * 2009-09-29 2012-08-22 金蝶软件（中国）有限公司 一种应用于多技术平台的生成表单的方法及装置
CN103631765A (zh) * 2012-08-21 2014-03-12 镇江雅迅软件有限责任公司 一种面向组件的业务系统自定义模型

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090319548A1 (en) * 2008-06-20 2009-12-24 Microsoft Corporation Aggregation of data stored in multiple data stores
CN101901262A (zh) * 2010-07-26 2010-12-01 北京新洲协同软件技术有限公司 基于面向对象模型的企业建库和业务数据显示的方法
CN102830973A (zh) * 2012-08-14 2012-12-19 无锡哲勤科技有限公司 海量数据下Web应用开发双层MVC的方法和分层结构
CN103309964A (zh) * 2013-06-03 2013-09-18 广州市香港科大霍英东研究院 一种针对大规模交通数据的高效可视监测分析系统

Also Published As

Publication number Publication date
CN105335389B (zh) 2019-02-19
CN105335389A (zh) 2016-02-17

Similar Documents

Publication Publication Date Title
TWI748175B (zh) 資料的處理方法、裝置及設備
WO2016004814A1 (zh) 一种业务可视化方法及系统
TWI695290B (zh) 登錄資訊處理方法及設備
TWI718375B (zh) 基於區塊鏈的資料處理方法及設備
US10691299B2 (en) Display of hierarchical datasets using high-water mark scrolling
JP6929278B2 (ja) タイトル表示方法及び装置
TWI712899B (zh) 資訊查詢方法及裝置
WO2019085615A1 (zh) 一种展示界面内容的数据处理方法、装置和处理设备
US10685024B2 (en) Tuple extraction using dynamically generated extractor classes
WO2016110202A1 (zh) 一种显示页面的方法、客户端及设备
US20160019464A1 (en) Adapting digital content based upon usage patterns
CN112000563B (zh) 用户行为的记录方法、装置及设备
WO2019218736A1 (zh) 一种页面处理方法、装置及设备
WO2019179243A1 (zh) 一种信息展示方法、装置及设备
WO2019085601A1 (zh) 一种任务执行的方法及装置
CN110020231A (zh) 网页截图方法及其装置
US20230385363A1 (en) Web site preview generation based on web site type
CN109710622A (zh) 一种数据更新方法、装置和系统
US11176161B2 (en) Data processing method, apparatus, and device
CN105589634B (zh) 一种信息反馈方法、装置及设备
WO2023229693A1 (en) Web site preview generation with action control
CN114201086B (zh) 信息的展示方法及装置
TWI685235B (zh) 事務處理方法和系統
US11122105B2 (en) System and method for component based web services development
TW201828113A (zh) 標題展示方法及裝置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15819708

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15819708

Country of ref document: EP

Kind code of ref document: A1