Service Marts: a Service Framework for Search Computing Alessandro Campi Andrea Maesani.

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 2 4. Achieving Qualities.
Advertisements

Architecture Representation
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
An Associative Broadcast Based Coordination Model for Distributed Processes James C. Browne Kevin Kane Hongxia Tian Department of Computer Sciences The.
Software Testing and Quality Assurance
An Architecture-Based Approach to Self-Adaptive Software Presenters Douglas Yu-cheng Su Ajit G. Sonawane.
The Data Mining Visual Environment Motivation Major problems with existing DM systems They are based on non-extensible frameworks. They provide a non-uniform.
Transaction Processing IS698 Min Song. 2 What is a Transaction?  When an event in the real world changes the state of the enterprise, a transaction is.
1 Case Study: Starting the Student Registration System Chapter 3.
DISTRIBUTED COMPUTING
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
[ §6 : 1 ] 6. Basic Methods II Overview 6.1 Models 6.2 Taxonomy 6.3 Finite State Model 6.4 State Transition Model 6.5 Dataflow Model 6.6 User Manual.
Computer System Lifecycle Chapter 1. Introduction Computer System users, administrators, and designers are all interested in performance evaluation. Whether.
Aurora: A Conceptual Model for Web-content Adaptation to Support the Universal Accessibility of Web-based Services Anita W. Huang, Neel Sundaresan Presented.
Lecture 2 The Relational Model. Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical relations.
Chapter 4 The Relational Model Pearson Education © 2014.
Chapter 3 The Relational Model Transparencies Last Updated: Pebruari 2011 By M. Arief
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 19 Slide 1 Component-based software engineering 1.
Avalanche Internet Data Management System. Presentation plan 1. The problem to be solved 2. Description of the software needed 3. The solution 4. Avalanche.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Capacity analysis of complex materials handling systems.
An Introduction to Software Architecture
Active Monitoring in GRID environments using Mobile Agent technology Orazio Tomarchio Andrea Calvagna Dipartimento di Ingegneria Informatica e delle Telecomunicazioni.
An Integration Framework for Sensor Networks and Data Stream Management Systems.
1 Towards Recovering the Broken SOA Triangle: A Software Engineering Perspective Anton Michlmayr, Florian Rosenberg, Christian Platzer, Martin Treiber,
Architecting Web Services Unit – II – PART - III.
Chapter 3 The Relational Model. 2 Chapter 3 - Objectives u Terminology of relational model. u How tables are used to represent data. u Connection between.
Grid Resource Allocation and Management (GRAM) Execution management Execution management –Deployment, scheduling and monitoring Community Scheduler Framework.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved DISTRIBUTED SYSTEMS.
1 The Relational Database Model. 2 Learning Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical.
9/7/2012ISC329 Isabelle Bichindaritz1 The Relational Database Model.
Keyword Searching and Browsing in Databases using BANKS Seoyoung Ahn Mar 3, 2005 The University of Texas at Arlington.
Andrew S. Budarevsky Adaptive Application Data Management Overview.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
1 Introduction to Web Services Quality Model And Collaboration Issues for EERP Sojung Kim WSQM TC National Information society Agency.
Secure Systems Research Group - FAU SW Development methodology using patterns and model checking 8/13/2009 Maha B Abbey PhD Candidate.
Center for E-Business Technology Seoul National University Seoul, Korea Optimization of Multi-Domain Queries on the Web Daniele Braga, Stefano Ceri, Florian.
Database Environment Chapter 2. Data Independence Sometimes the way data are physically organized depends on the requirements of the application. Result:
1 Composing Web Services on the Semantic Web by Brahim Medjahed Presented by Dohan Kim Lichun Zhu.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Testing OO software. State Based Testing State machine: implementation-independent specification (model) of the dynamic behaviour of the system State:
OPERATING SYSTEMS CS 3530 Summer 2014 Systems and Models Chapter 03.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
What’s Ahead for Embedded Software? (Wed) Gilsoo Kim
MapReduce and the New Software Stack. Outline  Algorithm Using MapReduce  Matrix-Vector Multiplication  Matrix-Vector Multiplication by MapReduce 
03/02/20061 Evaluating Top-k Queries Over Web-Accessible Databases Amelie Marian Nicolas Bruno Luis Gravano Presented By: Archana and Muhammed.
1 Chapter 2 Database Environment Pearson Education © 2009.
The Relational Model © Pearson Education Limited 1995, 2005 Bayu Adhi Tama, M.T.I.
1 Integration of data sources Patrick Lambrix Department of Computer and Information Science Linköpings universitet.
Fundamentals of Information Systems, Sixth Edition Chapter 3 Database Systems, Data Centers, and Business Intelligence.
Instance Discovery and Schema Matching With Applications to Biological Deep Web Data Integration Tantan Liu, Fan Wang, Gagan Agrawal {liut, wangfa,
Contents. Goal and Overview. Ingredients. The Page Model.
OPERATING SYSTEMS CS 3502 Fall 2017
Fundamentals of Information Systems, Sixth Edition
Architecting Web Services
Chapter 17 - Component-based software engineering
Computational Models Database Lab Minji Jo.
Architecting Web Services
Service-centric Software Engineering
Database management concepts
An Introduction to Software Architecture
Database management concepts
Presented By: Darlene Banta
Chapter 17 - Component-based software engineering
Data Models in DBMS A model is a representation of reality, 'real world' objects and events, associations. Data Model can be defined as an integrated collection.
Design.
Presentation transcript:

Service Marts: a Service Framework for Search Computing Alessandro Campi Andrea Maesani

Alessandro Campi SeCo Service Framework  Registration of new search services –Their semantic description –The production of relevant parameters  Informal and quick registration of "myWebSite"

Alessandro Campi SeCo Search Services  A special class of software services whose responses are ranked lists of objects –Ranking reflects a combination of: item-based rank computation algorithms, social recommendations, personalization and context-based adaptation, business incentives,…  Interaction is based upon request-responses –Requests = queries –Responses = ranked lists of items Items contain attribute-value pairs, links to resources, and content Rankings are normally opaque Lists are too long and should be partially retrieved 3

Alessandro Campi SeCo Hotel AccessPattern1AccessPattern2AccessPattern3 BookingTripAdvisor Expedia Service Mart  A uniform paradigm for service deployment –Uniform interfaces to high-level service composition frameworks –Abstractions and technologies for hiding low-level service implementation

Alessandro Campi SeCo Service Mart  Inspired by "data marts" used as uniform paradigm for data integration and warehousing –with an associated high-level ER conceptual representation –along the direction already marked by Web marts in Web modelling and engineering  They roughly correspond to the notion of "domain" and hide multiple low-level services, possibly offered by distinct providers

Alessandro Campi SeCo Service Interfaces Hotel Input Output ERSPI Response Time Caching Time AccessPattern1AccessPattern2AccessPattern3 BookingTripAdvisor Expedia InputOutput InputOutput InputOutputInputOutput InputOutput Keywords (Light Semantic Description)

Alessandro Campi SeCo Service Parameters  Name  Input  Output  Order Type: defines the eventual order of the results.  CacheTTL: if the service is cacheable, this attribute defines the validity time of cached data  Chunked: describes if the service is chunked or not.  ChunkSize: defines the dimension of the result of each call  ERSPI: defines the average number of results of each invocation  Average response time  Keywords: Light Semantic Description  Cost 7

Alessandro Campi SeCo QoS Scalability Capacity (Limit of concurrent requests for guaranteed performance) Performance (a measure of the speed in completing a service request) –Response time –Latency –Throughput Reliability –Mean time between failure (MTBF) –Mean Time to Failure (MTF) –Mean Time To Transition (MTTT) Robustness/ Flexibility Exception handling 8

Alessandro Campi SeCo QoS Accuracy (Defines the error rate produced by the service) Supported Standard (A measure of whether the service complies with standards) Stability/change cycle (A measure of the frequency of change related to the service in terms of its interface and/or implementation) Completeness Confidentiality Accountability Traceability and Auditability Data encryption Non-Repudiation

Alessandro Campi SeCo Service Interfaces  Low-level services (real Web services or wrapped web sites) can be enclosed by means of two basic mechanisms: –Run-time invocation (flight availability) –Periodic materialization (major soccer events) –Mixed

Alessandro Campi SeCo Materialization Att1Att2… DB“Static” Web site Att1Att2…

Alessandro Campi SeCo Direct Web service call

Alessandro Campi SeCo Input1Input2…Output1Output2… Lixto wrappers

Alessandro Campi SeCo Att1Att2…Attn… Att1Att2…Attn… Att1Att2…Attn… Multiple Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Lixto wrappers

Alessandro Campi SeCo Service Mart Hotel AccessPattern1AccessPattern2AccessPattern3 Attribute NameTypeKeywords (Light Semantic Description) BookingTripAdvisor Expedia Key Multiplicity (1-N) Attribute … Certain Attributes have associated Domains (sets of legal values)

Alessandro Campi SeCo AttributeKeyAttribute … KeyAttribute … KeyAttribute … Edge connecting two service marts by means of a sequence of pairs of service mart attributes, such that every paired attributes have compatible types: comparison using predicates (=, ) is supported The same pair of access marts can have more than one join pattern Service Marts

Alessandro Campi SeCo Service Marts CityStartDateEndDate…… Hotel Start Place End Place Date… Flight NameCityStartDateEndDate… Event > < > <

Alessandro Campi SeCo Access patterns Hotel Input …Output NameTypeLight Semantic DescriptionCardinality AccessPattern1AccessPattern2AccessPattern3 BookingTripAdvisor Expedia

Alessandro Campi SeCo Access patterns  Patterns representing the allowed invocations of service marts  Access pattern attributes are classified as: –Input –Output  Access patterns have a flat representation –They receive as input singleton values for input parameters –They produce as output tuples of values for output parameters Multi-valued attributes are used in cartesian product with all other extracted combinations

Alessandro Campi SeCo Access patterns  Patterns are either ordered (search) or unordered  Rankings are crisp (when tuples are partially ordered by the explicit values of output attributes) or opaque

Alessandro Campi SeCo Mapping to access patterns  The process of selecting for a query plan consisting of a partial order of invocation of access patterns, such that all input parameters of the access pattern get bound, whereas: –an input parameter associated with an input value is bound –an input parameter associated with an output parameter of a precedent access pattern in the partial order is bound –an input parameter associated with a domain is (weakly) bound

Alessandro Campi SeCo Mapping to access patterns  The mapping process produces one or more query plans  Weak bindings should be used only if after the failing of all mappings which do not use them  Weak bindings require domain injection, domains are partially ordered, domains are injected according to such partial order  Selection among equivalent query plans - using the same domain injections - should be decided by an optimizer 29

Alessandro Campi SeCo Mapping to access patterns Input1Input2…Output1Output2… AP1 Input1Input2…Output1Output2… AP3 Input1Input2…Output1Output2Output3… AP2 Input1Output1… Output2Output3… AP4

Alessandro Campi SeCo Query execution time Input1Input2…Output1… S1 Input1Input2…Output1Output2… S3 Input1Output2 S2.1 Input1Output1… Output2Output3… S4 Input1…Output2Output3… S2.2 S2

Alessandro Campi SeCo Access Mart Engineering  Performed at registration time  Requires the right set of language abstractions and components  Requires Web integration technologies –e.g. Lixto  Dedicated to developers