CN106126199A - The building method of viewdata model and device - Google Patents

The building method of viewdata model and device Download PDF

Info

Publication number
CN106126199A
CN106126199A CN201610413013.0A CN201610413013A CN106126199A CN 106126199 A CN106126199 A CN 106126199A CN 201610413013 A CN201610413013 A CN 201610413013A CN 106126199 A CN106126199 A CN 106126199A
Authority
CN
China
Prior art keywords
view
business
module
responsibility
data
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
Application number
CN201610413013.0A
Other languages
Chinese (zh)
Inventor
叶光焜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LeTV Holding Beijing Co Ltd
LeTV Information Technology Beijing Co Ltd
Original Assignee
LeTV Holding Beijing Co Ltd
LeTV Information Technology Beijing Co Ltd
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 LeTV Holding Beijing Co Ltd, LeTV Information Technology Beijing Co Ltd filed Critical LeTV Holding Beijing Co Ltd
Priority to CN201610413013.0A priority Critical patent/CN106126199A/en
Publication of CN106126199A publication Critical patent/CN106126199A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/211Schema design and management
    • G06F16/212Schema design and management with details for data modelling support
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/34Graphical or visual programming

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Stored Programmes (AREA)

Abstract

The present invention relates to Developing Technology of Applied Software field, disclose building method and the device of a kind of viewdata model.In the present invention, the building method of viewdata model includes: obtain at least one prototype data table;By prototype data table is analyzed, obtain at least one classification view;By classification view is combined, form at least one business module;By by business module objectification, construct at least one entity object view;Entity object view provides unified interface for application layer.The present invention also provides for the constructing apparatus of a kind of viewdata model.The modularity that the present invention realizes between data Layer and application layer by constructing multi-level virtual view data is docked, adapt to change or the extension of business demand, to reduce the impact that the change of business demand brings to software data layer and application layer, thus quick software iteration and the requirement of information-based renewal speed can be met.

Description

The building method of viewdata model and device
Technical field
The present invention relates to Developing Technology of Applied Software field, particularly to building method and the device of viewdata model.
Background technology
Data base is the main media of storage data, is also the basis accepting application layer, so the extension of database structure Need the factor considered the most with change.It is illustrated in figure 1 the data model of current data Layer and application layer, general database The amendment coverage of list structure is relatively wide, such as when adding a Database field or amendment attribute, needs to revise its current number According to the memorizer of layer, function, view etc., amendment is also related to for cluster or master-slave mode data base, then in the generation of application layer Code amendment is also inevitable.Simultaneously for the structural modification of tables of data, affecting index structure, efficiency is the slowest.Repairing of business structure Change the amendment that also can relate to software level.So maintenance cost for software is high.And owing to software design can not be complete The change of full anticipation future services itself, so the design amendment frequency of database structure and application layer is the highest.
But the extension of current enterprise business is a process the most quick, this also requires that enterprise information management updates also It must is fulfilled for the needs of operation expanding, so the information-based speed updated also has promoted the necessary iteratively faster of software product, this Situation is particularly evident for requirement drive software development.So for quick software iteration, it is desirable to software design expansible Property is high, the change of a demand or interpolation, it is impossible to bring greater impact to software itself.Design for application layer Requirement must so, and design and list structure for data base are all the more so.
At present in software design development process, due to data model ten branch office between existing application layer and data Layer Limit, can cause being continually changing along with business, it may be necessary to frequently revise tables of data, application layer code etc., it is impossible to meet quickly Software iteration and the requirement of IT application in enterprises renewal speed.
Summary of the invention
The purpose of the embodiment of the present invention is to provide building method and the device of a kind of viewdata model, many by structure Level virtual view data realize the modularity docking between data Layer and application layer, adapt to change or the expansion of business demand Exhibition, to reduce the impact that the change of business demand brings to software data layer and application layer, thus can meet quick software repeatedly Generation and the requirement of information-based renewal speed.
For solving above-mentioned technical problem, embodiments of the present invention provide the building method of a kind of viewdata model, Including: obtain at least one prototype data table;Described prototype data table is analyzed, obtains at least one classification view;Right Described classification view is combined, and forms at least one business module;By described business module objectification, construct at least one Entity object view;Wherein, described entity object view provides unified interface for application layer.
Embodiments of the present invention additionally provide the constructing apparatus of a kind of viewdata model, including: acquisition module, it is used for Obtain at least one prototype data table;Generation module, is analyzed for the prototype data table obtaining described acquisition module, To at least one view of classifying;Composite module, is combined for the classification view generating described generation module, is formed at least One business module;Constructing module, for described composite module combines the business module objectification obtained, constructs at least one Individual entity object view;Wherein, described entity object view provides unified interface for application layer.
Prototype data table in terms of existing technologies, is classified by analyzing, is divided by embodiment of the present invention Class view, classification view, as basic functional units, is mutually combined and i.e. can get business module, then business module is carried out object Change, obtain entity object view one by one, i.e. generation basic views is carried out modularization assembling, so that the view mould assembled Block business demand.Therefore, present invention, avoiding in prior art, when business frequently changes, need frequently in amendment data Layer Tables of data and the defect of application layer code, meet different business demand by quick assembled view module, and amendment is convenient, fast Speed, it is achieved flexibly, current information renewal speed and Fast Software iteration demand can be met.
It addition, described prototype data table is analyzed, obtain at least one classification view, according to described prototype data table In data and field meanings, described prototype data table responsibility is turned to responsibility view;Described classification view is combined, shape Become at least one business module, according to business need, described responsibility view is polymerized, form business polymerization view;By institute State business module objectification, when constructing at least one entity object view, process according to the data of application layer and represent, structure Business Entity.In this embodiment, according to the data in prototype data table and field meanings, prototype data table responsibility is turned to one Each and every one responsibility view, such that it is able to responsibility view is as basic view unit one by one, due to the merit of each responsibility view Can be single, not there is between function coupling, so, can neatly each responsibility view be combined, and can be to by multiple duties The business module of duty sets of views synthesis is disassembled, and the assembling of view is very convenient.And based on business need to different duties Duty view is polymerized, and can quickly form business polymerization view, meets information-based renewal speed and requires and Fast Software iteration Requirement.Further, when to business module objectification, process according to the data of application layer and represent, by business polymerization view object Turn to entity object view, use for application layer.Thus, grow up to service view from basic duty sets of views, then objectification is real Body object view whole during, assemble very convenient, quickly, it is to avoid relate to the complex modifications of tables of data, code revision, soft The change of part structure, can quickly meet business change demand.
It addition, the data virtualization of at least one prototype data table described obtains responsibility view window;Described responsibility view Extension can be combined randomly and obtain business polymerization view.Thus, it is possible to regard based on virtualizing the responsibility obtained according to business demand Figure extends window maximizedly and obtains miscellaneous service Aggregation view, fully meets the demand of different business.
Accompanying drawing explanation
Fig. 1 is the structural representation according to data Layer in prior art and application layer;
Fig. 2 is the flow chart of the building method according to first embodiment of the invention viewdata model;
Fig. 3 is viewdata virtual workflow mould in the building method according to first embodiment of the invention viewdata model Type schematic diagram;
Fig. 4 is viewdata virtual workflow mould in the building method according to second embodiment of the invention viewdata model Type schematic diagram;
Fig. 5 is the viewdata extension flow process mould of the building method according to second embodiment of the invention viewdata model Type schematic diagram;
Fig. 6 is regarding in the viewdata model construction method according to second embodiment of the invention developer's statistical system Diagram data model structure schematic diagram;
Fig. 7 is the structural representation of the constructing apparatus according to third embodiment of the invention viewdata model;
Fig. 8 is the structural representation of the constructing apparatus according to four embodiment of the invention viewdata model.
Detailed description of the invention
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with the accompanying drawing each reality to the present invention The mode of executing is explained in detail.But, it will be understood by those skilled in the art that in each embodiment of the present invention, In order to make reader be more fully understood that, the application proposes many ins and outs.But, even if there is no these ins and outs and base Many variations and amendment in following embodiment, it is also possible to realize the application technical scheme required for protection.
First embodiment of the present invention relates to the building method of a kind of viewdata model.Idiographic flow as in figure 2 it is shown, Comprising:
Step 20: obtain at least one prototype data table.Physical data table in prototype data table i.e. data base, modal number Generally including data and field according to table, the field in prototype data table has the implication determined.Data tool in prototype data table Having certain calculating, incidence relation, therefore, the various requirement of application layer can come real by tables of data carries out the operation of correspondence Existing.
Step 21: be analyzed prototype data table, obtains at least one classification view.For example, in step 21, right Prototype data table is analyzed, and obtains view of classifying, is such as according to the data in prototype data table and field meanings, by prototype Tables of data responsibility turns to responsibility view.Can be according to the single responsibility principle in software design by each classification view in step 21 Responsibility turns to single responsibility view.So, the function singleness of different single responsibility views and different, thus, when one When single responsibility view changes, do not interfere with other single responsibility views, due to different single responsibility views each other There is logical independence, so each single responsibility view has high reusability.Such as, can be by single responsibility view be entered Row combination, obtains the view model of combination, at the same time it can also be disassemble the view model of combination, removes one therein Or think single responsibility view more, obtain new view model.That is, each single responsibility view is just as building block module one by one, can To be combined easily, to dismantle, and combine dismounting and be all not related to the amendment of tables of data self, repairing of overall software level Change, decrease modification amount.
Step 22: classification view is combined, forms at least one business module.For example, can be according to business Require responsibility view is polymerized, form business polymerization view, in other words, be i.e. the merit needing realization according to business need Can, each single responsibility view is polymerized, the business polymerization view enabling each single responsibility view to aggregate into undertakes business The operations required.
In actual applications, can according to the single responsibility principle of software design, opening and closing principle, synthesis multiplexing principle, with And combine Flyweight Pattern, the design philosophy of bridge mode carries out responsibility metaplasia to prototype data table and becomes responsibility view, and to duty Dutyization view effectively combines, so that the business module being combined into disclosure satisfy that business demand.
Step 23: by business module objectification, constructs at least one entity object view.Specifically, according to application The data of layer process and represent, and construct Business Entity, as preferably, can construct at least one service sub-system topology view, Service sub-system topology view object is turned at least one Business Entity.
In conjunction with Fig. 3, present embodiment view data structures flow chart is explained: in step 21, to obtaining The prototype data table taken carries out responsibility, obtains the classification view corresponding to prototype data table, wherein it is possible to based on each data Table respectively obtains multiple classification view, based on application business demand, multiple classification views are combined, obtain one or Multiple business modules (1,2,3,4 ...), then by each business module objectification, be configured to entity object view.Entity object The quantity of view is depending on the actual demand of business.Entity object view provides unified interface for application layer, and this interface is such as Including: function, storing process etc..
When setting up classification view based on prototype data table, and application demand can be met by the combination formation of classification view Business module, when business module objectification is obtained the most concrete entity object view, this by classification view to industry Business module arrives the framework of entity object view again and just establishes multi-level between prototype data table and application layer, assemble, The virtual view model of convenient disassembly.The business module of different classification sets of views synthesis can be considered as separate business mould Block, therefore present embodiment has the advantages that
1, when business need is added or revises the field of prototype data table (physical data table), can only need to change indivedual The classification structure of view and the individual subsystem (business module) of application program, and without revise storing process in data Layer, Code etc. in function and application journey, reduces amendment scope.
2, when business module is deleted, only business module view corresponding to business module and Business Entity object need to be deleted View, it is not necessary to prototype data list structure is made any amendment.
3, when needing the structure (prototype data table) according to current system, during system of activating business, only need to be according to current number According to the content information of table, responsibility dissolves classification view, and being then assembled into business module can be for application layer, so that apply Extension very flexibly, quickly.
4. owing to amendment is just for view window, so not affecting prototype data list structure and index information, to actual number Disturbance degree according to storehouse is little, it is to avoid the complexity of frequent amendment data base.
Embodiment of the present invention, by structure virtual module Data View model as prototype data table and application layer it Between carry out the passage of data interaction so that the dependency between prototype data table and application layer reduces, and has higher logic only Vertical property, adapts to change or the extension of business demand according to this, changes to soft such that it is able to reduce business demand to greatest extent The impact that part data Layer and application layer are brought.
Second embodiment of the present invention relates to the building method of a kind of viewdata model.Second embodiment is first Make improvement on the basis of embodiment, mainly the improvement is that: in this second embodiment, when business demand is based on being During current data of uniting, the data virtualization of at least one prototype data table is obtained responsibility view window, by responsibility is regarded Figure carries out random combine extension and obtains business polymerization view.Such that it is able to meet miscellaneous service requirement neatly.
When business demand extension is based on the data that system is current (prototype data table is constant), need the tool of connected applications Body demand, carries out labor to structure in prototype data table and data, and real according to Fig. 4, the data structure flow chart shown in 5 Existing extendible business model system:
1, the data of clear and definite prototype data table and field meanings, turn to the view of single responsibility to prototype data table responsibility Class, i.e. each responsibility view only has a function, and therefore, each responsibility view can be combined with other views neatly.
2, it is polymerized responsibility view according to business need, forms the little module business polymerization view model of a comparison system.
3, process according to the data of application layer and represent, constructing service sub-system structural representation.
4, service sub-system topology view object is turned to Business Entity, provides a unified interface for application program, Thus application layer coding can be simplified.
The responsibility view of present embodiment, business polymerization view and service sub-system topology view can the sides of similar building blocks Formula is extended, as it is shown in figure 5, be described in detail as follows to the autgmentability of present embodiment:
The extension of responsibility view: the data in multiple prototype data tables virtual can dissolve according to application demand point requirement The responsibility view window of various satisfied requirements.
The extension of business polymerization view: the virtual responsibility view dissolved can be carried out random combine, makes new advances with extension Business polymerization view.
The extension of service sub-system topology view: utilize existing Data View window, Quick Extended virtual data layers, carry High application and development speed.
As shown in Figure 6, existing as a example by developer's statistical system is applied, the structure to the viewdata model of present embodiment Method is illustrated as follows:
SDA system data analysis: current system store the hour of log-on of application developer, registration type, liveness, The prototype datas such as click time and interbehavior.According to these prototype datas, various types of exploitation can be sorted out Person's information (i.e. function dissolves responsibility view), such as: registration developer, newly-increased effective exploitation person, personal development person etc., further according to this Each class developer's information of a little responsibility views offers one dimension by the hour.Then, sky is taken out according to a hour dimensional information Dimensional information, takes out the dimensional information of week, the moon again according to the dimensional information in sky, thus combination hour, day, week, the letter of the moon etc. Breath, can form developer's statistical system model.
Owing to application platform development system needs to analyze the user behavior of each class developer, need existing former based on system Type data, according to information such as the log-on message of developer's type with the time different developers of statistics, registration amount, liveness, convenient Analyze developer's user behavior, and a reference can be provided for preferably improving system developer application system.
The step of the most various methods divides, and is intended merely to describe clear, it is achieved time can merge into a step or Some step is split, is decomposed into multiple step, as long as including identical logical relation, all at the protection domain of this patent In;To adding inessential amendment in algorithm or in flow process or introducing inessential design, but do not change its algorithm With the core design of flow process all in the protection domain of this patent.
Third embodiment of the invention relates to the constructing apparatus of a kind of viewdata model, as it is shown in fig. 7, this viewdata The constructing apparatus 7 of model includes:
Acquisition module 70, is used for obtaining at least one prototype data table.
Generation module 71, is analyzed for the prototype data table obtaining acquisition module 70, obtains at least one classification View.
In present embodiment, generation module 71 is for according to the data in prototype data table and field meanings, by modal number Turn to responsibility view according to table responsibility, and responsibility view is single responsibility view.
Composite module 72, is combined for the classification view generating generation module, forms at least one business module. In present embodiment, responsibility view can be polymerized by composite module 72 according to business need, forms business polymerization view.
Constructing module 73, for composite module combines the business module objectification obtained, constructs at least one entity Object view.Wherein, entity object view can be that application layer provides unified interface.For example, constructing module can root Process according to the data of application layer and represent, constructing Business Entity.In present embodiment, constructing module includes: constructor module and Objectification submodule.Constructor module processes for the data according to application layer and represents, and constructs at least one service sub-system Topology view, objectification submodule turns at least one for service sub-system topology view object constructor module structure gone out Individual Business Entity.
It is seen that, present embodiment is the system embodiment corresponding with the first embodiment, and present embodiment can be with First embodiment is worked in coordination enforcement.The relevant technical details mentioned in first embodiment the most still has Effect, in order to reduce repetition, repeats no more here.Correspondingly, the relevant technical details mentioned in present embodiment is also applicable in In first embodiment.
It is noted that each module involved in present embodiment is logic module, in actual applications, one Individual logical block can be a physical location, it is also possible to be a part for a physical location, it is also possible to multiple physics lists The combination of unit realizes.Additionally, for the innovative part highlighting the present invention, will be with solution institute of the present invention in present embodiment The unit that the technical problem relation of proposition is the closest introduces, but this is not intended that in present embodiment the list that there is not other Unit.
Four embodiment of the invention relates to the constructing apparatus of a kind of viewdata model.4th embodiment is real the 3rd Making improvement on the basis of executing mode, mainly the improvement is that: in the 4th embodiment, generation module is for by least one The data virtualization of individual prototype data table obtains responsibility view window, and composite module is for combining extension randomly by responsibility view Obtain business polymerization view.
In actual applications, as shown in Figure 8, the constructing apparatus 8 of the viewdata model of present embodiment includes: processor 80, memorizer 81, display 82 and transceiver 83.
Wherein, processor 80 is the core of constructing apparatus, and it can be CPU (central processing unit), DSP (Digital Signal Processor, digital signal processor) etc., its be mainly responsible in the constructing apparatus of viewdata model each parts it Between co-ordination, and above-mentioned side execute mode is mentioned classification view, responsibility view, the polymerization of responsibility view, business son The formation of system structure view, and the operation of the objectification etc. to service sub-system topology view.Wherein, memorizer 81 is permissible For ROM (Read Only Memory, read only memory), RAM (Random Access Memory, random access storage device), Caching or the storage device such as flash memory, it may be used for storing computer-readable programmed instruction, and this programmed instruction is used for so that place Reason device realizes the conformation function of the viewdata model shown in embodiment 1 or embodiment 2, and such as, the classification that storage generates regards Figure, responsibility view, the polymerization of classification view, the polymerization of responsibility view, service sub-system topology view, and objectification obtain business Entity etc..Wherein, display 82 is mainly used in showing human-computer interaction interface, to facilitate software developer to operate.Wherein, Transceiver 83 is mainly used in each server communication in distribution service (when each prototype data table is distributed in distributed clothes Time in business system), thus realize the data interaction of application layer and data Layer.
Owing to the second embodiment is the most corresponding with present embodiment, therefore present embodiment can be mutual with the second embodiment Match enforcement.The relevant technical details mentioned in second embodiment is the most effective, implements second The technique effect that can reach in mode is the most too it is achieved that in order to reduce repetition, the most superfluous State.Correspondingly, the relevant technical details mentioned in present embodiment is also applicable in the second embodiment.
It will be understood by those skilled in the art that the respective embodiments described above are to realize the specific embodiment of the present invention, And in actual applications, can to it, various changes can be made in the form and details, without departing from the spirit and scope of the present invention.

Claims (10)

1. the building method of a viewdata model, it is characterised in that including:
Obtain at least one prototype data table;
Described prototype data table is analyzed, obtains at least one classification view;
Described classification view is combined, forms at least one business module;
By described business module objectification, construct at least one entity object view;Wherein, described entity object view is for answering Unified interface is provided with layer.
The building method of viewdata model the most according to claim 1, it is characterised in that to described prototype data table It is analyzed, when obtaining at least one classification view, according to the data in described prototype data table and field meanings, by described former Type tables of data responsibility turns to responsibility view;
Described classification view is combined, forms at least one business module, according to business need, described responsibility view is entered Row polymerization, forms business polymerization view;
By described business module objectification, construct at least one entity object view, process and exhibition according to the data of application layer Existing, construct Business Entity.
The building method of viewdata model the most according to claim 2, it is characterised in that at the data of application layer Manage and represent, constructing Business Entity, specifically include:
Data according to application layer process and represent, and construct at least one service sub-system topology view;
Described service sub-system topology view object is turned at least one Business Entity.
The building method of viewdata model the most according to claim 3, it is characterised in that at least one modal number described Responsibility view window is obtained according to the data virtualization of table;
Described responsibility view can combine extension randomly and obtain business polymerization view.
The building method of viewdata model the most according to claim 2, it is characterised in that described responsibility view is single Responsibility view.
6. the constructing apparatus of a viewdata model, it is characterised in that including:
Acquisition module, is used for obtaining at least one prototype data table;
Generation module, is analyzed for the prototype data table obtaining described acquisition module, obtains at least one classification view;
Composite module, is combined for the classification view generating described generation module, forms at least one business module;
Constructing module, for described composite module combines the business module objectification obtained, constructs at least one entity pair As view;Wherein, described entity object view provides unified interface for application layer.
The constructing apparatus of viewdata model the most according to claim 6, it is characterised in that
Described generation module is for according to the data in described prototype data table and field meanings, by described prototype data table responsibility Turn to responsibility view;
Described composite module, for being polymerized described responsibility view according to business need, forms business polymerization view;
Described constructing module processes for the data according to application layer and represents, and constructs Business Entity.
The constructing apparatus of viewdata model the most according to claim 7, it is characterised in that described constructing module includes:
Constructor module, processes for the data according to application layer and represents, constructing at least one service sub-system topology view;
Objectification submodule, turns at least one for the service sub-system topology view object described constructor module structure gone out Individual Business Entity.
The constructing apparatus of viewdata model the most according to claim 8, it is characterised in that
Described generation module is for obtaining responsibility view window by the data virtualization of at least one prototype data table described;
Described composite module obtains business polymerization view for described responsibility view is combined extension randomly.
The constructing apparatus of viewdata model the most according to claim 7, it is characterised in that
Described responsibility view is single responsibility view.
CN201610413013.0A 2016-06-13 2016-06-13 The building method of viewdata model and device Pending CN106126199A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610413013.0A CN106126199A (en) 2016-06-13 2016-06-13 The building method of viewdata model and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610413013.0A CN106126199A (en) 2016-06-13 2016-06-13 The building method of viewdata model and device

Publications (1)

Publication Number Publication Date
CN106126199A true CN106126199A (en) 2016-11-16

Family

ID=57270295

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610413013.0A Pending CN106126199A (en) 2016-06-13 2016-06-13 The building method of viewdata model and device

Country Status (1)

Country Link
CN (1) CN106126199A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101609461A (en) * 2009-07-29 2009-12-23 孟小峰 A kind of space querying system of personal core data and method based on user characteristics
US20130063459A1 (en) * 2011-09-09 2013-03-14 Microsoft Corporation Primitive composition
CN104809597A (en) * 2015-05-14 2015-07-29 国家电网公司 Data resource management platform based on data fusion

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101609461A (en) * 2009-07-29 2009-12-23 孟小峰 A kind of space querying system of personal core data and method based on user characteristics
US20130063459A1 (en) * 2011-09-09 2013-03-14 Microsoft Corporation Primitive composition
CN104809597A (en) * 2015-05-14 2015-07-29 国家电网公司 Data resource management platform based on data fusion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
税伯琪: "基于.NetRemoting机制的货运结算系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 *

Similar Documents

Publication Publication Date Title
JP6388711B2 (en) High speed railway vehicle rapid design method and system
Terkaj et al. Ontology-based modeling of production systems for design and performance evaluation
Ivson et al. A systematic review of visualization in building information modeling
Barbierato et al. Modeling apache hive based applications in big data architectures
CN103530134B (en) A kind of configurable software platform structure
CN102780583B (en) Method for service description, service combination and service quality assessment of Internet of Things
CN105338045A (en) Cloud computing resource processing device, method and cloud computing system
US20160162607A1 (en) Model for Managing Variations in a Product Structure for a Product
Dou et al. Tracking the research on ten emerging digital technologies in the AECO industry
Saraireh et al. Understanding the conceptual of building information modeling: a literature review
US10140387B2 (en) Model for managing variations in a product structure for a product
Pandya Review of modelling techniques and tools for decision making in manufacturing management
EP3206143A1 (en) System and method for managing variations in a product structure for a product
Zheng et al. Survey on design approaches for robotic manufacturing systems in SMEs
CA2816830A1 (en) Model for managing variations in a product structure for a product
Kuczenski Partial ordering of life cycle inventory databases
Kuzminykh et al. 4D and 5D design processes automation using databases, classification and applied programming
CN106126199A (en) The building method of viewdata model and device
Bohács et al. Production logistics simulation supported by process description languages
Mohandes et al. Building information modeling in construction industry
Vilela et al. Hierarchical planning in a supervisory control context with compositional abstraction
Wang et al. Research on the reliability allocation method for a production system based on availability
CN111562904B (en) Reliability block diagram RBD (radial basis function) auxiliary modeling method based on SysML (SysML) system model
Dureigne Collaborative large engineering: from IT dream to reality
Shahrokni et al. Beyond Information Silos

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
WD01 Invention patent application deemed withdrawn after publication
WD01 Invention patent application deemed withdrawn after publication

Application publication date: 20161116