DOCSLIB.ORG

Loose Coupling and Substitution Principle in Objet-Oriented Frameworks for Web Services Diana Allam

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Loose Coupling and Substitution Principle in Objet-Oriented Frameworks for Web Services Diana Allam Loose coupling and substitution principle in objet-oriented frameworks for web services Diana Allam To cite this version: Diana Allam. Loose coupling and substitution principle in objet-oriented frameworks for web services. Software Engineering [cs.SE]. Ecole des Mines de Nantes, 2014. English. NNT : 2014EMNA0115. tel-01083286 HAL Id: tel-01083286 https://tel.archives-ouvertes.fr/tel-01083286 Submitted on 17 Nov 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Thèse de Doctorat Diana ALLAM Mémoire présenté en vue de l’obtention du grade de Docteur de l’École nationale supérieure des mines de Nantes sous le label de l’Université de Nantes Angers Le Mans École doctorale : Sciences et technologies de l’information, et mathématiques Discipline : Informatique et applications, section CNU 27 Unité de recherche : Laboratoire d’informatique de Nantes-Atlantique (LINA) Ecole des Mines de Nantes Soutenue le 10 Juillet 2014 Thèse n°: ED 503-2014 EMNA 0115 Loose Coupling and Substitution Principle in Object-Oriented Frameworks for Web Services JURY Rapporteurs : M. Farouk TOUMANI, Professeur, Université Blaise Pascal M. Gwen SALAÜN, Maître de conférences, ENSIMAG, Grenoble INP Examinateurs : M. Claude JARD, Professeur, Université de Nantes M. Anderson SANTANA DE OLIVEIRA, Chercheur senior, SAP Labs Directeur de thèse : M. Jean-Claude ROYER, Professeur, Ecole des Mines de Nantes Co-directeur de thèse : M. Hervé GRALL, Maître-Assistant, Ecole des Mines de Nantes Remerciements 1 Je tiens à remercier dans un premier temps, mon encadrant, Hervé Grall, et mon directeur de thèse, Jean-Claude Royer, pour leurs patiences pendant nos heures de discussion, pour leurs aides, leurs conseils avisés mais également pour leurs soutiens tout au long de ma thèse. Un grand MERCI! Merci à Gwen Salaün et Farouk Toumani pour avoir accepté d’être rapporteurs. Merci aussi à Claude Jard et Anderson Santana de Oliveira pour avoir accepté d’être membres du Jury. Merci à l’ensemble des membres du projet ANR CESSA, Mario Südholt, Rémi Douence, Hervé Grall, Jean-Claude Royer, Matteo Dell-Amico, Yves Roudier, Muhammad Sabir Idrees, Anderson Santana de Oliveira, Gabriel Serme et Gaëtan Harel avec qui j’ai eu des précieuses échanges. Merci au chef d’équipe Ascola, Mario Südholt, à l’ancien chef du département, Narendra Jussien et au nouveau chef du département, Jacques Noyé, d’avoir fourni un soutien financier pour participer à des divers activités et événements, particulièrement à des conferences na- tionales et internationales. Merci à Catherine Fourney, Florence Rogues, Cécile Derouet, Diana Gaudin, Michelle Dauvé, Sylvie le Goff et Delphine Turlier pour leurs aides en tout ce qui concerne les étapes administratives et les demandes de mission. Merci aux membres du département informatique pour leur belle ambiance amicale. Je tiens à remercier en particulier Jurgen pour sa disponibilité et ses conseils. Merci aux membres de CXF mailing-list, particulièrement Sergey Beryozkin, pour leurs réponses rapides à mes questions sur le forum et leurs aides à résoudre et comprendre certains problèmes. Merci à mes amis du département énergétique à l’école des Mines, Nadia, Charlotte, Emna, Elias, Maël et les autres, avec qui j’ai passé des très beaux moments. 1http://lylouannecollection.blogspot.fr/ 3 Merci à mes amis Libanais à Nantes (et qui sont passés par Nantes), Rémy, Nader et Ali el Housseini, Ali el Roz, Ali Yassin, Jaafar, Houssam, Haydar Abbass, Ghassan, Ahmad, Mo- hamed Jawad, Hosni, Ayman & Batoul, Zein & Majd, Youmna et les autres avec qui j’ai partagé des beaux souvenirs. Merci à ma famille de Roumanie, Carmen, Cilvio, Laura, Andra, Christina, Marta, Rodica, Alex, ma grande mère et les autres qui me sont chers. Merci à ma famille ALLAM de Hermel, particulièrement à mes cousins Dyala, Faten, Firas, Yahya, Zakaria, Mohamed, Malek, Sam, Khouzama, Malak, Rami, Ali, Layal, Rasha, Bachir, Houssein, Fatima2, Emne, Jawad, Widiane, Samaher, Amani, Lamis et tous les autres. Merci à la petite famille ASSAF, particulièrement à Mouchira, Sara et Nour, pour les beaux moments qu’on a passé ensemble et les beaux souvenirs inoubliables. Merci à mes deux plus chères personnes, mon père et ma mère, à qui je dois plus que toutes leurs années de sacrifice, leurs soutiens sans faille, leurs disponibiltés à tout moment, leurs encouragements et leurs prières. C’est grâce à vous deux que je suis qui je suis aujourd’hui. Merci à mes deux soeurs, Nadine et Karmen, et à mon frère Karim, à qui je réserve une place très particulière dans mon coeur et dans ma vie. Merci à mon précieux, Ali, mon compagnon du chemin, l’étoile qui éclaire ma vie et mon ange protecteur. 4 Contents 1 Introduction 11 I State of the Art 21 2 Service Oriented Architecture and Web Services 23 2.1 Service Oriented Architecture (SOA) concepts . 24 2.1.1 Interface-based interaction ........................ 24 2.1.2 Dynamic discovery ............................ 25 2.1.3 SOA entities ................................ 26 2.2 Web services ................................... 27 2.2.1 SOAP model ............................... 27 2.2.2 RESTful model ............................. 33 2.3 Discussion ..................................... 35 3 Distributed Objects and Web Services 37 3.1 The architecture of an object-oriented framework for Web services . 39 3.1.1 The object level and the service level . 39 3.1.2 Data binder ................................ 40 3.1.3 Development and execution ....................... 43 3.1.4 Data flow ................................. 45 3.1.5 Control flow ............................... 45 3.2 An overview about distributed object environments . 48 3.2.1 Distributed objects design ........................ 48 3.2.2 Object-oriented middleware ....................... 50 3.3 Discussion ..................................... 52 3.3.1 Service orientation vs object orientation in distributed systems . 52 3.3.2 Gap between objects and structural documents . 53 3.3.3 A need for a unified model at the service level . 54 4 Abstract Formal Models for Service-Oriented Computing 57 4.1 Abstract models for SOA ............................. 58 4.1.1 Communication requirements ...................... 58 5 CONTENTS 4.1.2 Message-based models .......................... 59 4.1.3 Unified models for SOAP and RESTful services . 59 4.1.4 From π-calculus to Join-calculus . 60 4.2 Type systems ................................... 61 4.2.1 Typing requirements for an interaction model . 61 4.2.1.1 Channels mobility: channel type and recursivity over channel types .............................. 61 4.2.1.2 Succession of interactions ................... 63 4.2.1.3 Customization of Web services interfaces . 63 4.2.1.4 Subtyping ........................... 64 4.2.2 Type systems in theory .......................... 65 4.2.3 Weaknesses in existing used type systems . 66 4.2.4 Type safety and type checking ...................... 66 4.3 Discussion ..................................... 67 II Towards a Well-Founded Object-Oriented Framework for Web Ser- vices 69 5 Inconsistencies in Object-Oriented Frameworks for Web Services 71 5.1 Requirements in object-oriented frameworks for Web services . 72 5.1.1 Loose coupling .............................. 73 5.1.2 Substitution principle ........................... 73 5.2 Weaknesses in existing frameworks ....................... 74 5.2.1 Tight coupling in object-oriented discovery APIs . 74 5.2.2 Weak interoperability in respect with the substitution principle . 80 5.2.3 Tight coupling between binding schema and service technology . 83 5.3 Conclusion .................................... 88 6 A Black Box Formal Model for Service-Oriented Computing 89 6.1 Web services communication ........................... 90 6.1.1 Components definition .......................... 90 6.1.2 Components deployment ......................... 91 6.2 Typing message-oriented services ........................ 94 6.2.1 Typing values ............................... 94 6.2.2 Application to examples ......................... 94 6.2.2.1 Channels mobility ....................... 95 6.2.2.2 Succession of interactions ................... 96 6.2.2.3 Customization of Web services interfaces . 97 6.2.3 Subtyping ................................. 97 6.2.3.1 Subtyping example ...................... 97 6.2.3.2 Subtyping algorithm ...................... 99 6.3 Well typed service communication . 100 6 CONTENTS 6.3.1 Type checking messages . 100 6.3.2 Type-checking in the presence of attackers . 103 6.3.2.1 Typing error example . 103 6.3.2.2 A need for a weak authentication . 103 6.4 Conclusion .................................... 105 III A New Specification for a Well-Founded Object-Oriented Frame- work for Web Services 107 7 A Unified Object-Oriented API for Dynamic Web Services Discovery 109 7.1 Unification of the standardized Web services components . 110 7.1.1 Components and interfaces . 110 7.1.2 Messages exchange between interfaces . 114 7.1.3 Matching with the type system . 115 7.2 Unification of dynamic Web services discovery protocols . 118 7.2.1 The
Load more

Recommended publications
  • Examining the Relationships Between Software Coupling and Software Performance: a Cross-Platform Experiment
    Journal of Computing and Information Technology - CIT 19, 2011, 1, 1–10 1 doi:10.2498/cit.1001353 Examining the Relationships between Software Coupling and Software Performance: A Cross-platform Experiment Liguo Yu1 and Srini Ramaswamy2 1 Computer and Information Sciences Department, Indiana University, South Bend, USA 2 Industrial Software Systems, ABB Corporate Research Center, Bangalore, India Coupling measures the degree of dependencies between Alexander et al., 2010). Table 1 lists the def- software modules. Considerable research has been initions of several major types of coupling in performed to relate software coupling with software understandability, maintainability, and reusability, which structured software systems, in which the de- are the key properties of software maintenance and gree of dependency is considered in increasing evolution. However, only a few research works have order from the bottom (data coupling) to the been reported that study the relationships between soft- ( ) ware coupling and software performance. This study top content coupling . Strong coupling means implemented two benchmarks that measure and compare a high degree of dependency between software the performance of software programs implemented with modules, while loose coupling means a low de- different kinds of coupling, common coupling, data coupling, and stamp coupling. The experiment is run gree of dependency between software modules. on three different platforms, Windows, Linux, and Mac. The results show that (1) the relative performance of systems implemented using different software coupling is platform dependent; (2) while loose coupling is more favorable than strong coupling with respect to software Name Definition maintenance and evolution, it has the drawback of re- duced performance of a software program.
    [Show full text]
  • Lesson 02: Distributed System Patterns
    Lesson 02: Distributed System Patterns Phillip​ J. Windley, Ph.D. CS462​ – Large-Scale Distributed Systems Lesson 02: Distributed System Patterns Contents 00 Coupling 03 Distributed Architectures 01 Distributed System Design Axes 04 Conclusion 02 Rethinking Distributed One​ of the most important Coupling properties of a distributed system is how tightly or loosely coupled the processing is. Lesson 02: Distributed System Patterns Coupling Coupling​ refers to the degree to which two or more processes are interdependent. We​ say two things are tightly coupled when they are interdependent and loosely coupled when they are independent. Tight​ and loose coupling are not binary positions, but rather relative terms. Any given architectural choice might make two processes more or less coupled. CS462​ – Large-Scale Distributed Systems 4 Lesson 02: Distributed System Patterns Distributed Systems and Loose Coupling Generally​ when designing If two processes are completely independent they can successfully operate without any kind of coordination with the other process. distributed systems Whenever​ we introduce dependencies, the processes must anything that makes the coordinate their activities. This requires some kind of system more loosely communication between the two processes. This can result in coupled is desirable. wasted computation, delays due to latency, and computational errors. But,​ no useful software Of​ course, we can’t accomplish most interesting computations without some coupling. Good distributed architectures accomplish system can be built where their tasks with a minimum of coupling. Good distributed system all the components are architects choose architectures that minimize the coupling necessary to get the job done. completely decoupled. CS462​ – Large-Scale Distributed Systems 5 Lesson 02: Distributed System Patterns System Level Coupling Coupling​ can occur on multiple levels within a system.
    [Show full text]
  • LNCS 5103, Pp
    An Event-Based Approach to Reducing Coupling in Large-Scale Applications Bartosz Kowalewski1, Marian Bubak1,2, and Bartosz Bali´s1 1 Institute of Computer Science, AGH, Krakow, Poland 2 Academic Computer Centre CYFRONET AGH, Krakow, Poland [email protected], {bubak,balis}@agh.edu.pl Abstract. Large-scale distributed applications tend to become more and more complex and hard to develop, and execute. Approaches used when building such systems have to be revised, in order to decrease coupling within the code and increase productivity during the devel- opment process. Especially event-based programming applied to Web services should gain much attention. In this paper, we present an experi- mental publish/subscribe infrastructure, which introduces robust event- based mechanisms to be used with Web services-enabled applications. The concept of this solution is built upon the extensibility and config- urability principles. We show that performance gap between traditional distributed event-based technologies and the Web also services-based ap- proach is not necessarily as significant as most people tend to think. Keywords: Large-scale computing, distributed computing, decoupling, Web services, event infrastructure, publish/subscribe, WS-Notification. 1 Introduction The main characteristic of an event-based design is its striving to decrease cou- pling in a system [5]. Coupling, usually contrasted with cohesion, is the degree of association between modules, components, subsystems, etc. [6] Over the past three decades a lot of attention has been paid to this concept, both in scientific and commercial computing. Besides many other measures, the level of coupling started to be treated as quality metrics for software design.
    [Show full text]
  • Software Maintainability and Reusability Using Cohesion Metrics
    International Journal of Computer Trends and Technology (IJCTT) – Volume 54 Issue 2-December2017 Software Maintainability and Reusability using Cohesion Metrics Adekola, O.D#1, Idowu, S.A*2, Okolie, S.O#3, Joshua, J.V#4, Akinsanya, A.O*5, Eze, M.O#6, EbiesuwaSeun#7 #1Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria *2Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #3Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #4Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria *5Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #6Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria #7Faculty, Computer Science Department, Babcock University,Ilishan-Remo, Ogun State, Nigeria Abstract - Among others, remarkable external software’s lifetime. Ahn et al., (2003) estimated that quality attributes of interest to software practitioners/ maintenance takes up to 80% of the total costof engineers include testability, maintainability and producing software applications. Expectation of reusability.Software engineers still combat achieving more reliable, quicker time-to-market and softwarecrisis and even chronic software affliction maintainable systems. A lot of research has gone into not because there is no standardized software the areas of software reuse and maintenance due to development process but because enough attention is the fact that these among other issues concern not given to seemingly insignificant but crucial intimately system developers/architects/engineers details of internal design attributes such as cohesion rather than end-users. Therehas been enormous and coupling especially in object-oriented systems. growth in software reuse research from the days of Consequently, the aftermath is increased structured programming concepts to object-oriented maintenance cost, effort and time which negatively methods and beyond (e.g.
    [Show full text]
  • Zapthink White Paper
    zapthink white paper GOVERNANCE, QUALITY, & MANAGEMENT THE FOUNDATIONS OF SOA ZapThink, LLC y 108 Woodlawn Road y Baltimore, MD 21210 y [email protected] y www.zapthink.com Governance, Quality, & Management July 2008 GOVERNANCE, QUALITY, & MANAGEMENT THE FOUNDATIONS OF SOA July 2008 Analyst: Jason Bloomberg Abstract Service-Oriented Architecture (SOA) is an approach to organizing IT resources to better meet the changing needs of the business. While many organizations are somewhere on their SOA roadmaps, many such organizations face challenges when planning the underlying infrastructure that will support their SOA implementation. One reason for this challenge is that there are three core infrastructure areas that are jointly essential to the success of separate, but overlapping SOA effort: governance, quality, and management. Governance means creating, communicating, and enforcing the policies that apply to the behavior of IT and its users. Quality is a measure of how well working systems meet the needs of the business. Management focuses on how well those systems meet performance, security, and other non-functional requirements for working software. In the context of SOA, however, these three sets of capabilities begin to merge. To provide the business agility benefit that is the core business motivation for many SOA initiatives, governance, quality, and management need not only apply to the design time and run time phases that traditional software projects exhibit. In addition, SOA requires these capabilities apply to the change time phase as well, where organizations reconfigure and recompose Services to meet changing business needs. As a result, the governance, quality, and management challenges that SOA presents go beyond traditional IT concerns.
    [Show full text]
  • Two Cases in High Reliability Organizing
    Two Cases in High Reliability Organizing: a Hermeneutic Reconceptualization GERD VAN DEN EEDE ii Two Cases in High Reliability Organizing: a Hermeneutic Reconceptualization iii Two Cases in High Reliability Organizing: a Hermeneutic Reconceptualization Twee Gevalsstudies over Organiseren voor Hoge Betrouwbaarheid: Een Hermeneutische Reconceptualisatie PROEFSCHRIFT ter verkrijging van de graad van doctor aan de Universiteit van Tilburg, op gezag van de rector magnificus, prof. dr. Ph. Eijlander, in het openbaar te verdedigen ten overstaan van een door het college voor promoties aangewezen commissie in de aula van de Universiteit op vrijdag 18 december 2009 om 14.15 uur door Gerd Geeraard Paula Van Den Eede geboren op 7 juni 1970 te Dendermonde, België iv Two Cases in High Reliability Organizing: a Hermeneutic Reconceptualization Promotor: Prof. dr. P.M.A. Ribbers Copromotor: dr. B.A. Van de Walle Overige leden: Univ.-Prof. dr.-Ing. F. Fiedrich Prof. dr. T.J. Grant Dr. F. Hardeman Dr. A-F. Rutkowski Prof. dr. M. Turoff Prof. dr. D. Van Lindt . Table of Contents v Table of Contents TABLE OF CONTENTS ................................................................................................................................ V LIST OF FIGURES ......................................................................................................................................XII LIST OF TABLES .......................................................................................................................................XIII GLOSSARY
    [Show full text]
  • Tight and Loose Coupling in Organizations
    BE J. Theor. Econ. 2016; aop Romans Pancs* Tight and Loose Coupling in Organizations DOI 10.1515/bejte-2015-0081 Abstract: Some industries have consumers who seek novelty and firms that innovate vigorously and whose organizational structure is loosely coupled, or easily adaptable. Other industries have consumers who take comfort in the traditional and firms that innovate little and whose organizational structure is tightly coupled, or not easily adaptable. This paper proposes a model that explains why the described features tend to covary across industries. The model highlights the pervasiveness of equilibrium inefficiency (innovation can be insufficient or excessive) and the nonmonotonicity of welfare in the equili- brium amount of innovation. Keywords: loose coupling, tight coupling, demand for novelty 1 Introduction Some industries have consumers who seek novelty and have firms that innovate vigorously and whose organizational structure is loosely coupled in the sense that it easily adjusts to the changes in the economic environment. The tech industry in the Silicon Valley is like this. Consumers expect regular upgrades to gadgets; the startup culture and high employee mobility breed firms ready to take advantage of the latest changes in the economic environment. Other indus- tries have consumers who take comfort in the traditional and have firms that innovate little and whose organizational structure is tightly coupled in the sense of being slow to adjust to the changes in the economic environment. The manufacturing industry was like this in Japan in the second-half of the twentieth century, during the industrialization stage. De-facto lifetime employment was common, and the firm’s organizational structure was rigid.
    [Show full text]
  • Security Model for Service-Oriented Architecture
    Advanced Computing: An International Journal ( ACIJ ), Vol.2, No.4, July 2011 Security Model For Service-Oriented Architecture Oldooz Karimi, MSc Department of Computer Engineering, sofiyan Azad University, sofiyan, Iran , [email protected] Abstract . In this article, we examine how security applies to Service Oriented Architecture (SOA). Before we discuss security for SOA, lets take a step back and examine what SOA is. SOA is an architectural approach which involves applications being exposed as "services". Originally, services in SOA were associated with a stack of technologies which included SOAP, WSDL, and UDDI. This article addresses the defects of traditional enterprise application integration by combining service oriented-architecture and web service technology. Application integration is then simplified to development and integration of services to tackle connectivity of isomerous enterprise application integration, security, loose coupling between systems and process refactoring and optimization. Key words : service-oriented architecture, enterprise application integration, security 1 Introduction It is tempting to launch into a description of SOA Security without first asking "Why?" Why apply security to SOA? One obvious answer is to protect the SOA infrastructure against attack. This is a valid reason, but there are also enabling, positive reasons for applying security to SOA, such as the ability to monitor usage of services in a SOA. We begin by examining the attacks against SOA technologies, both EAI and ESA. Abstract: Interoperable software architecture requires interoperable security mechanisms. Security is frequently looked at as a black art, but in reality the core concepts of security - knowing your assets and designing for failure - are just good engineering practices.
    [Show full text]
  • Master's Thesis
    MASTER’S THESIS Loosely-coupled user-friendly interface: a Window toward a better application of knowledge-based system in Architecture, Engineering and Construction Faridaddin Vahdatikhaki Master’s thesis in Construction Management and Engineering Loosely-coupled user-friendly interface: a Window toward a better application of knowledge-based system in Architecture, Engineering and Construction The Netherlands, January, 2011 Faridaddin Vahdatikhaki Delft University of Technology Van Hattum en Blankfort Supervisors: Prof. Dr. ir. Hennes De Ridder Ir. Marcel Ludema Ir. Sipke Huitema Ir. Martinus van de Ruitenbeek Dedicated to my father for being the embodiment of perfection in my life Acknowledgement: I shall express my most heartfelt gratitude to my parents without whose indelible support and inspiring words, this dissertation would not be. Their kindness has been my last and only recourse in years fraught with disquietude and tension. Their being out there for me never ceased to palliate my distress in every circumstances. I feel obliged to give my deepest thanks to my wife who has never refrained from infusing me with passion and inspiration throughout these years. Words may not convey my appreciation for her being such a supportive person despite all difficulties I put her through with not being next to her. This is my responsibility to thank Martinus van de Ruitenbeek whose brilliance has been my only torch in journeying through the dim realms of research. His enlightening ideas have kept my work progressing and coming to fruition. I am indebted to Dr. Reza Beheshti for being a marvelous friend and guide whenever I was desperate for help.
    [Show full text]
  • Xsd to Sql Schema Online
    Xsd To Sql Schema Online Maison is restitutory and set-to momentarily while superlunar Duffy patronizing and readied. Daintily viperous, Durand wane subdelirium and salaam bombardments. Sometimes rectilinear Jacques bridges her baby-sitter afterward, but formalistic Shanan garrotting linguistically or carks substitutively. Be the preview and to sql Due to these restrictions, SQL Server Authentication, the complete source of the imported schemas are being included in to the generated JSON Schema. Wild card components allow adding content that is not known at the time of schema design. Conformant yaml file formats as a pdf and convert sql format? XML Schema editors XML schema editor tools. This specification defines JSON Schema core terminology and mechanisms, and as such, we work with the various data format and gets the requirement to load the data into SQL Server. Otherwise, and innovative things. XML Schemas Inspection Results. An XML document contains elements, checking this option will generate attributes in both classes with each other as type. Via a corresponding to generate json from xml schema it is shown in the newer, it is well known that an update to a set of electronic data can be communicated either by relaying the set of updated data or by transmitting the set of changes in the data. However, XML data retrieved from the database has the same information as before it was inserted into the database, so any script or SQL statement you write must reflect the original XML data. Basically, optionally, and SPAs. Remove any yaml markup language has sent an xml serialization language for these options will be.
    [Show full text]
  • Design Principles for the Future Internet Architecture
    Design Principles for the Future Internet Architecture Dimitri Papadimitriou1, Theodore Zahariadis2, Pedro Martinez-Julia3, Ioanna Papafili4, Vito Morreale5, Francesco Torelli5, Bernard Sales1, and Piet Demeester6 1 Alcatel-Lucent Bell Labs, Belgium {dimitri.papadimitriou,bernard.sales}@alcatel-lucent.com 2 Synelixis Solutions, Greece [email protected] 3 Univ. of Murcia, Spain [email protected] 4 Athens University of Economics and Business (AUEB) [email protected] 5 Engineering, Italy {vito.morreale,francesco.torelli}@eng.it 6 Ghent University (UGent), Belgium [email protected] Abstract. Design principles play a central role in the architecture of the Internet as driving most engineering decisions at conception level and operational level. This paper is based on the EC Future Internet Architecture (FIArch) Group results and identifies some of the design principles that we expect to govern the future architecture of the Internet. We believe that it may serve as a starting point and comparison for most research and development projects that target the so-called Future Internet Architecture. 1 Introduction Design principles play a central role in the architecture of the Internet as driving most engineering decisions not only at conception level but also at operational level. Many ICT systems do not consider design principles and derive their model directly from requirements. However, when it comes to the design of the Internet, the formulation of design principles is a fundamental characteristic of the process that guides the design of its protocols. On the other hand, in searching for Internet architectural principles, we must remember that technical change is continuous in the information and communication technology industry.
    [Show full text]
  • Efficient Xml Stream Processing and Searching
    THE FLORIDA STATE UNIVERSITY COLLEGE OF ARTS AND SCIENCES EFFICIENT XML STREAM PROCESSING AND SEARCHING By WEI ZHANG A Dissertation submitted to the Department of Computer Science in partial fulfillment of the requirements for the degree of Doctor of Philosophy Degree Awarded: Spring Semester, 2012 Wei Zhang defended this dissertation on March 22, 2012. The members of the supervisory committee were: Robert A. van Engelen Professor Directing Dissertation Erlebacher Gordon University Representative Xiuwen Liu Committee Member Xin Yuan Committee Member Zhenhai Duan Committee Member The Graduate School has verified and approved the above-named committee members, and certifies that the dissertation has been approved in accordance with the university requirements. ii To Xiaobo, my love, whose wholehearted support helped me complete this dissertation. iii ACKNOWLEDGMENTS This dissertation would not have been completed without the helps of several people. I would like to express my gratitude to my advisor, Dr. Robert A. van Engelen, for his support, patience, and encouragement throughout my graduate studies. He has been instrumental in the successful completion of this work. He provided an environment that nurtured my growth during the early stages of the research process, while giving sufficient freedom and patience during the later stages of my dissertation research. His technical and editorial advice was essential to the completion of this dissertation and has taught me innumerable lessons and insights on the workings of academic research in general. I would give my thanks to my committee members, Dr. Xin Yuan, Dr. Zhenhai Duan, Dr. Xiuwen Liu and Dr. Gordon Erlebacher for reading my prospectus and previous drafts of this dissertation and providing many valuable comments that improved the presentation and contents of this dissertation.
    [Show full text]