Modeling and querying business data with artifact lifecycle (Q1665847): Difference between revisions

From MaRDI portal
Created claim: Wikidata QID (P12): Q59118790, #quickstatements; #temporary_batch_1709550817224
ReferenceBot (talk | contribs)
Changed an Item
 
(2 intermediate revisions by 2 users not shown)
Property / MaRDI profile type
 
Property / MaRDI profile type: MaRDI publication profile / rank
 
Normal rank
Property / full work available at URL
 
Property / full work available at URL: https://doi.org/10.1155/2015/506272 / rank
 
Normal rank
Property / OpenAlex ID
 
Property / OpenAlex ID: W1542644660 / rank
 
Normal rank
Property / cites work
 
Property / cites work: Data Modeling in Dataspace Support Platforms / rank
 
Normal rank

Latest revision as of 11:52, 16 July 2024

scientific article
Language Label Description Also known as
English
Modeling and querying business data with artifact lifecycle
scientific article

    Statements

    Modeling and querying business data with artifact lifecycle (English)
    0 references
    0 references
    0 references
    27 August 2018
    0 references
    Summary: Business data has been one of the current and future research frontiers, with such big data characteristics as high-volume, high-velocity, high-privacy, and so forth. Most corporations view their business data as a valuable asset and make efforts on the development and optimal utilization on these data. Unfortunately, data management technology at present has been lagging behind the requirements of business big data era. Based on previous business process knowledge, a lifecycle of business data is modeled to achieve consistent description between the data and processes. On this basis, a business data partition method based on user interest is proposed which aims to get minimum number of interferential tuples. Then, to balance data privacy and data transmission cost, our strategy is to explore techniques to execute SQL queries over encrypted business data, split the computations of queries across the server and the client, and optimize the queries with syntax tree. Finally, an instance is provided to verify the usefulness and availability of the proposed method.
    0 references
    0 references
    0 references
    0 references