{ "version": "https://jsonfeed.org/version/1", "title": "Cesare Pautasso - Publications", "home_page_url": "http://www.pautasso.org/", "feed_url": "http://www.pautasso.org/biblio/feed.json", "description": "Publication list of Cesare Pautasso", "icon": "http://www.pautasso.org/img/CesarePautasso.jpg", "author": { "name": "Cesare Pautasso", "url": "http://www.pautasso.org/" }, "items": [ { "id": "biblio/2025/ese", "html_content": "", "url": "../biblio/2025/ese", "title": "Understanding Security Tactics in Microservice APIs using Annotated Software Architecture Decomposition Models – A Controlled Experiment", "summary": "While microservice architectures have become a widespread option for designing distributed applications, designing secure microservice systems remains challenging. Although various security-related guidelines and practices exist, these systems\\textquoteright sheer size, complex communication structures, and polyglot tech stacks make it difficult to manually validate whether adequate security tactics are applied throughout their architecture.\nTo address these challenges, we have devised a novel solution that involves the automatic generation of security-annotated software decomposition models and the utilization of security-based metrics to guide software architectures through the assessment of security tactics employed within microservice systems. To evaluate the effectiveness of our artifacts, we conducted a controlled experiment where we asked 60 students from two universities and ten experts from the industry to identify and assess the security features of two microservice reference systems. During the experiment, we tracked the correctness of their answers and the time they needed to solve the given tasks to measure how well they could understand the security tactics applied in the reference systems.\nOur results indicate that the supplemental material significantly improved the correctness of the participants\\textquoteright answers without requiring them to consult the documentation more. Most participants also stated in a self-assessment that their understanding of the security tactics used in the systems improved significantly because of the provided material, with the additional diagrams considered very helpful. In contrast, the perception of architectural metrics varied widely. We could also show that novice developers benefited most from the supplementary diagrams. In contrast, senior developers could rely on their experience to compensate for the lack of additional help. Contrary to our expectations, we found no significant correlation between the time spent solving the tasks and the overall correctness score achieved, meaning that participants who took more time to read the documentation did not automatically achieve better results. As far as we know, this empirical study is the first analysis that explores the influence of security annotations in component diagrams to guide software developers when assessing microservice system security.", "date_modified": "2025-01-01T00:00:00Z", "author": { "name": "Patric Genfer" } }, { "id": "biblio/2025/icsa", "html_content": "", "url": "../biblio/2025/icsa", "title": "Mining Security Documentation Practices in OpenAPI Descriptions", "date_modified": "2025-02-28T23:00:00Z", "author": { "name": "Diana Carolina Muñoz Hurtado" } }, { "id": "biblio/2024/plop", "html_content": "", "url": "../biblio/2024/plop", "title": "Dark Patterns for Unethical Software Engineering", "summary": "Unethical software engineers write software to satisfy harmful requirements. While patterns promote beneficial solutions to recurring problems, dark patterns intentionally introduce harmful solutions. In this paper we present a collection of 16 dark patterns widely used by unethical software engineers to violate users privacy (email pixel injector, stealthy input logger), pursue monetization at all costs (aggressive advertiser, ad-blocker detector, pay to win, artificial scarcity hoarder, DRM rug puller, obsolescence planner), commit digital frauds (cybersquatter, sneaky terms degrader, interoperability breaker), manipulate search rankings (fake review generator, search ranking kickbacker), and engage in unethical artificial intelligence practices (training data harvester, bot pretender, deceptive deepfaker). By discussing the ethical consequences of each pattern we aim to raise awareness about them and encourage their avoidance by ethical software engineers, architects and practitioners.", "date_modified": "2024-09-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2024/bpm", "html_content": "", "url": "../biblio/2024/bpm", "title": "Transparent Transaction Ordering in Blockchain-based Collaborative Processes", "summary": "Blockchain technology offers a promising solution for overcoming trust-related challenges, such as transparency in interorganizational collaborative processes. However, since the ordering of transactions in a block can affect the outcome of a process instance, fairness and transparency concerns regarding block selection may arise. This paper presents a consensus-agnostic approach to promote transparency in transaction ordering in blockchain-based business processes. The approach allows participants to align the execution order of their transactions with their business objectives, effectively mitigating the lack of transparency associated with the arbitrary selection and ordering of transactions during block selection. Our experiments reveal that the increased transparency mitigates the risks of suppression and displacement attacks at the cost of introducing additional latency and cost.", "image": "/biblio-covers/fc4mc-bpm2024.png", "date_modified": "2024-08-31T22:00:00Z", "author": { "name": "Hassan Atwi" } }, { "id": "biblio/2024/jwe", "html_content": "", "url": "../biblio/2024/jwe", "title": "How Are Web APIs Versioned in Practice? A Large-Scale Empirical Study", "summary": "Web APIs form the cornerstone of modern software ecosystems, facilitating seamless data exchange and service integration. Ensuring the compatibility and longevity of these APIs is paramount. This study delves into the intricate realm of API versioning practices, a crucial mechanism for managing API evolution. Exploring an expanded and diverse dataset of 603 293 APIs specifications created during the 2015–2023 timeframe and gathered from four different sources, we examined the adoption of the following versioning practices: Metadata-based, URL-based, Header-based and Dynamic versioning, with one or more versions in production. API developers use more than 50 different version identifier formats to encode information about the changes introduced with respect to the previous version (i.e., semantic versioning), about when the version was released (i.e., age versioning) and about which phase of the API development lifecycle the version belongs (i.e., stable vs. preview releases).", "image": "/biblio-covers/apiace-jwe-2024.png", "date_modified": "2024-07-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2024/ecsa", "html_content": "", "url": "../biblio/2024/ecsa", "title": "OAS2Tree: Visual API-First Design", "summary": "OAS2Tree is a tool designed to transform OpenAPI Specification (OAS) documents into tree-like visualizations, aiding in the understanding and navigation of the structure of REST APIs. By converting the detailed, verbose, and often complex OAS files into a visual tree structure, OAS2tree simplifies the comprehension of a Web API, highlighting the hierarchical relationships between endpoints, operations, and parameters. This visual representation is particularly useful for developers and stakeholders who need a quick overview of an API without delving into the intricate details of its technical specifications. OAS2tree can be integrated into the IDE through a Visual Studio code extension or used as a standalone web application. The tool currently has about 400 users and has been used on teaching, research, and development projects. In this paper, we present the design and implementation of OAS2tree, highlighting its features and use cases. We also highlight the limitations of the current version and discuss future improvements and potential extensions.", "image": "/biblio-covers/apiace-ecsa2024-oas2tree.png", "date_modified": "2024-08-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2024/msr", "html_content": "", "url": "../biblio/2024/msr", "title": "APIstic: A Large Collection of OpenAPI Metrics", "summary": "In the rapidly evolving landscape of web services, the significance of efficiently designed and well-documented APIs is paramount. In this paper, we present APIstic an API analytics dataset and exploration tool to navigate and segment APIs based on an extensive set of precomputed metrics extracted from OpenAPI specifications, sourced from GitHub, SwaggerHub, BigQuery and APIs.guru.\nThese pre-computed metrics are categorized into structure, data model, natural language description, and security metrics.\nThe extensive dataset of varied API metrics provides crucial insights into API design and documentation for both researchers and practitioners. Researchers can use APIstic as an empirical resource to extract refined samples, analyze API design trends, best practices, smells, and patterns. For API designers, it serves as a benchmarking tool to assess, compare, and improve API structures, data models, and documentation using metrics to select points of references among 1,275,568 valid OpenAPI specifications.\nThe paper discusses potential use cases of the collected data and presents a descriptive analysis of selected API analytics metrics. ", "image": "/biblio-covers/apiace-msr2024-apistic.png", "date_modified": "2024-03-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2024/ieeesw", "html_content": "", "url": "../biblio/2024/ieeesw", "title": "Continuous Integration and Delivery in Open Source Development and Pattern Publishing: Lessons Learned With Tool Setup and Pipeline Evolution", "summary": "Every software project that aims to deliver high quality output needs a continuous integration setup. However, once the build pipeline is working, one cannot rest and take things for granted. Over long periods of time, tools come and go, and even if they remain the same, vendors often tinker with their pricing model. Lacking standardized and portable build configurations, it is critical to minimize the coupling between what needs to be built, how and where it gets built.", "date_modified": "2024-01-31T23:00:00Z", "author": { "name": "Olaf Zimmermann" } }, { "id": "biblio/2024/asianplop", "html_content": "", "url": "../biblio/2024/asianplop", "title": "Decentralized Task Execution Patterns", "summary": "Decentralized task execution requires to assign planning, execution and control roles and responsibilities to at least two distinct parties. These include making decisions about \\textquoteleft\\textquoteleftwho does what when\\textquoteright\\textquoteright so that one party can track the progress and the outcome of tasks executed by another party. In this paper we outline the design space for decentralized task execution by presenting 18 different patterns, going from imperative task execution all the way to autonomous task execution. We will distinguish how decisions about who performs a task, what needs to be done and when to do it can be made by different parties and how these alternative decision-making locations impact the interactions between the parties responsible to plan, execute and control the task execution. The patterns are applicable within human organizations with many actors delegating or performing multiple tasks but also to fully automated systems, e.g., distributed operating systems, intelligent autonomous vehicles, blockchain-based workflow engines or high throughput job schedulers.", "image": "/biblio-covers/asianplop2024.png", "date_modified": "2024-02-29T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2024/icwe", "html_content": "", "url": "../biblio/2024/icwe", "title": "How Many Web APIs Evolve Following Semantic Versioning?", "summary": "More and more Web APIs use semantic versioning to represent the impact of changes on clients depending on previous versions. Our goal is to provide insights about the extent to which evolving Web APIs align with semantic versioning rules. In this paper we present the results of an empirical study on the descriptions of 3 075 Web APIs, which released at least one new version throughout their history. The APIs descriptions were mined by retrieving 132 909 commits from 2 028 different open source GitHub repositories. We systematically collected and examined 506 273 changes of 195 different types released within 16 053 new API versions. We classified whether each change is likely to break clients or not, and checked whether the corresponding version identifier has been updated following semantic versioning rules. The results indicate that in the best case, only 517 APIs consistently release major upgrades when introducing breaking changes, while 1 970 APIs will not always correctly inform their clients about breaking changes released as part of minor or patch-level upgrades. We also detected 927 APIs which use a backwards-compatible evolution strategy, as they never introduce any breaking change throughout their history.", "image": "/biblio-covers/apiace-icwe2024.png", "date_modified": "2024-05-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2023/bpm", "html_content": "", "url": "../biblio/2023/bpm", "title": "Loose Collaborations on the Blockchain: Survey and Challenges", "summary": "Blockchain technology has emerged as a promising infrastructure for enabling collaboration between mutually distrustful organizations. The enactment of blockchain-based collaborative processes typically requires a profound understanding of the process being executed, limiting support for flexible processes that cannot be fully prespecified at design time. To overcome this limitation, support for looseness, dealing with the configuration and execution of underspecified processes, is essential. In this paper, we conduct a systematic literature review to examine looseness support for blockchain-based collaborative processes from a behavioral and organizational perspective. In addition, we identify open research challenges to pave the way for further research in this area.", "image": "/biblio-covers/fc4mc-bpm2023.png", "date_modified": "2023-08-31T22:00:00Z", "author": { "name": "Tom Lichtenstein" } }, { "id": "biblio/2023/vissoft", "html_content": "", "url": "../biblio/2023/vissoft", "title": "Interactively exploring API changes and versioning consistency", "summary": "Application Programming Interfaces (APIs) evolve\nover time. As they change, they are expected to be versioned\nbased on how changes might affect their clients. In this paper, we\npresent two novel visualizations specifically designed to represent\nall structural changes and the level of adherence to semantic\nversioning practices over time. They can also serve for characterizing and comparing the evolution history of different Web\nAPIs. The API VERSION CLOCK helps to visualize the sequence\nof API changes over time and highlight inconsistencies between\nmajor, minor, or patch version changes and the corresponding\nintroduced breaking or non-breaking changes applied to the\nAPI. The API CHANGES overview aggregates all changes to\nan OpenAPI (OAS) description, highlighting the unstable vs.\nthe stable elements of the API over its entire history. Both\nvisualizations can be automatically created using the APICTURE,\na command-line and web-based tool that analyzes the histories\nof git code repositories containing OAS descriptions, extracting\nthe necessary data for generating visualizations and computing\nmetrics related to API evolution and versioning. The visualizations have been successfully applied to classify, compare, and\ninteractively explore the multi-year evolution history of APIs with\nup to hundreds of individual commits.", "image": "/biblio-covers/apiace-vissoft2023.png", "date_modified": "2023-09-30T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2024/sa-education", "html_content": "", "url": "../biblio/2024/sa-education", "title": "A Better Way to Teach Software Architecture", "summary": "Software architecture education is a weak spot in many undergraduate programs in computer science and software engineering. While the concepts and practices used by software architects in industry are rich and varied, transferring this expertise into a university classroom has proved problematic. Bridging the gap between industry and academia requires ongoing, often heroic, effort. This is a \\textquotedblleftchicken and egg\\textquotedblright problem: Because there is a lack of good teaching materials, architecture is seldom taught, and because it is seldom taught, there has been little incentive to create good materials. We would like to change that. Our goal is to establish guidelines for how software architecture practices should be taught\\textemdashboth technical and non-technical topics\\textemdashand to suggest appropriate teaching methods to best prepare students to be software architects in practice.", "date_modified": "2023-01-01T00:00:00Z", "author": { "name": "Rick Kazman" } }, { "id": "biblio/2024/sa-empirical", "html_content": "", "url": "../biblio/2024/sa-empirical", "title": "An Empirical Basis for Software Architecture Research", "summary": "Despite the clear need for and importance of performing empirical studies as part of software architecture research, there is still a lack of curated, standardized, clean, well-maintained, documented, easily accessible, reusable, and shared datasets. In this chapter, we provide an overview of the problems, of the motivations, and of the opportunities currently related to mining and sharing datasets for researchers in software architecture. We first explore and describe which artifacts should be included into such datasets, such as code, documentation, and requirements, but also including other architecturally relevant artifacts, such as architectural decision records, models, and other kinds of documentation. This information can be complemented with revision history logs, social metadata, and email or chat discussion archives. The availability of such datasets would enable not only architectural reconstruction studies but would also help to catalyze broader and more ambitious program of empirical studies in software architecture research.", "date_modified": "2023-01-01T00:00:00Z", "author": { "name": "Rick Kazman" } }, { "id": "biblio/2023/iedge-liquid", "html_content": "", "url": "../biblio/2023/iedge-liquid", "title": "A brief history of liquid software", "summary": "The concept of liquid software, i.e., software with flexible deployment, over the past two decades has appeared in the fields of edge computing, Internet of Things (IoT), Human-Computer Interaction, DevOps and Web engineering. In this paper, we survey, compare, and provide a comprehensive definition of liquid software by analyzing how the metaphor has been used in existing literature and identifying gaps and inconsistencies in the current vs. past understanding of the concept. \nOverall, liquid software can be seamlessly deployed and redeployed within a dynamic and distributed runtime environment in response to changes applied to the set of available devices and to the software itself. \nLiquid software has been introduced in the context of active networks and intelligent environments, it has been applied to describe the user interaction with multi and cross-device user interfaces, it has found a promising foundation in Web technology, continuous software delivery pipelines, as well as isomorphic software architectures running across the IoT, edge and Cloud continuum.", "image": "/biblio-covers/iedge2023-a-brief-history-of-liquid-software.png", "date_modified": "2023-06-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2023/europlop", "html_content": "", "url": "../biblio/2023/europlop", "title": "API Rate Limit Adoption - A Pattern Collection", "image": "/biblio-covers/apiace-europlop2023.png", "date_modified": "2023-06-30T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2023/icwe-api-versioning", "html_content": "", "url": "../biblio/2023/icwe-api-versioning", "title": "An empirical study of Web API versioning practices", "summary": "As Web APIs evolve, developers assign them version identifiers to reflect the amount and the nature of changes that the API clients should expect. In this work we focus on identifying versioning practices adopted by Web API developers by extracting and classifying version identifiers found in a large collection of OpenAPI descriptions.\nIn particular, we observe how frequently different versioning schemes have been adopted for identifying both stable and preview releases (e.g., simple version counters, semantic versioning, or release timestamps). We further study the stability of versioning schemes during APIs evolution. We also detect APIs which offer dynamic access to versioning metadata through dedicated endpoints as well as APIs which support clients expecting to reach up to 14 different versions of the same API at the same time.\nOverall the results offer a detailed view over current Web API versioning practices and can serve as the basis for future discussions on how to standardize critical API versioning metadata.", "image": "/biblio-covers/apiace-icwe2023-versioning.png", "date_modified": "2023-05-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2023/icwe-liquidai", "html_content": "", "url": "../biblio/2023/icwe-liquidai", "title": "LiquidAI: Towards an Isomorphic AI/ML System Architecture for the Cloud-Edge Continuum", "summary": "A typical Internet of Things (IoT) system consists of a large number of different subsystems and devices, including sensors and actuators, gateways that connect them to the Internet, cloud services, end-user applications and analytics. Today, these subsystems are implemented with a broad variety of programming technologies and tools, making it difficult to migrate functionality from one subsystem to another. In our earlier papers, we have predicted the rise of \\emphisomorphic IoT system architectures in which all the subsystems can be developed with a consistent set of technologies. \nIn this paper we expand the same research theme to machine learning technologies, highlighting the need to use ML in a consistent and uniform fashion across the entire Cloud-Edge continuum. ", "image": "/biblio-covers/icwe2023-liquidai.png", "date_modified": "2023-05-31T22:00:00Z", "author": { "name": "Kari Systa" } }, { "id": "biblio/2023/2023map", "html_content": "", "url": "../biblio/2023/2023map", "title": "Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges", "summary": "Proven Patterns for Designing Evolvable High-Quality APIs--For Any Domain, Technology, or Platform\n\nAPIs enable breakthrough innovation and digital transformation in organizations and ecosystems of all kinds. To create user-friendly, reliable and well-performing APIs, architects, designers, and developers need expert design guidance. This practical guide cuts through the complexity of API conversations and their message contents, introducing comprehensive guidelines and heuristics for designing APIs sustainably and specifying them clearly, for whatever technologies or platforms you use.\n\nIn Patterns for API Design: Simplifying Integration with Loosely Coupled Message Exchanges, five expert architects and developers cover the entire API lifecycle, from launching projects and establishing goals through defining requirements, elaborating designs, planning evolution, and creating useful documentation. They crystallize the collective knowledge of many practitioners into 44 API design patterns, consistently explained with context, pros and cons, conceptual solutions, and concrete examples. To make their pattern language accessible, they present a domain model, a running case study, decision narratives with pattern selection options and criteria, and walkthroughs of real-world projects applying the patterns in two different industries.", "image": "/biblio-covers/map.png", "date_modified": "2023-01-01T00:00:00Z", "author": { "name": "Olaf Zimmermann" } }, { "id": "biblio/2022/sose-ccc", "html_content": "", "url": "../biblio/2022/sose-ccc", "title": "Cargo-Cult Containerization: A Critical View of Containers in Modern Software Development", "summary": "Software is increasingly developed and deployed using containers. While the concept of a container is conceptually straightforward, there are various issues to be considered while using them, ranging from technical details inside containers to the orchestration of containers that jointly form a meaningful application. In recent years, the use of containers has become so prevalent that developers have a tendency to resort to cargo-cult containerization – ritual adherence to the use of containers just because so many others are doing the same thing. In this paper, we study advantages and downsides of containers in modern- day software development. We foresee the use of containers to spread into new areas, including IoT systems and embedded devices. At the same time, we caution against indiscriminate use of containers, since excessive containerization can have adverse impacts on software maintenance and overall complexity of a system architecture.", "image": "/biblio-covers/sose2022-ccc.png", "date_modified": "2022-07-31T22:00:00Z", "author": { "name": "Tommi Mikkonen" } }, { "id": "biblio/2022/ecsa-expresso", "html_content": "", "url": "../biblio/2022/ecsa-expresso", "title": "ExpressO: From Express.js implementation code to OpenAPI interface descriptions", "summary": "This tool demo paper brings forward a new CLI tool called ExpressO for developers who need to analyze a Web API implemented using the Express.js framework and automatically extract a specification written in the standard OpenAPI interface description language. The specification includes all of the implemented endpoints along with their response status codes and path and query parameters. Developers can use it to automatically determine whether the interface of a Web API matches its implementation based on the Express.js framework. The tool has been released on the npm component registry as 'expresso-api'.", "image": "/biblio-covers/apiace-ecsa2022-expresso.png", "date_modified": "2022-08-31T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2022/icws", "html_content": "", "url": "../biblio/2022/icws", "title": "How Composable is the Web? An Empirical Study on OpenAPI Data model Compatibility", "summary": "Composing Web APIs is a widely adopted practice by developers to speed up the development process of complex Web applications, mashups, and data processing pipelines. However, since most publicly available APIs are built independently of each other, developers often need to invest their efforts in solving incompatibility issues by writing ad-hoc glue code, adapters and message translation mappings. How likely are Web APIs to be directly composable?\n\nThe paper presents an empirical study to determine the potential composability of a large collection of 20,587 public Web APIs by verifying their schemas' compatibility. We define three levels of data model elements compatibility -- considering matches between property names and/or data types -- which can be determined statically based on API descriptions conforming to the OpenAPI specification. The study research questions address: to which extent are Web APIs compatible; the average number of compatible endpoints within each API; the likelihood of finding two APIs with at least one pair of compatible endpoints. \n\nTo perform the analysis we developed a compatibility checker tool which can statically determine API schema compatibility on the three levels and find matching pairs of API responses which can be directly forwarded as requests to the same or other APIs. We run the tool on a dataset of 751,390 request and response message schemas extracted from publicly available OpenAPI descriptions.\n\nThe results indicate a relatively high number of compatible APIs when matching their data models only on the level of their elements' data type. However, this number gets lower narrowing the scope to only the ones handling data objects having identical properties name. The average likelihood of finding two compatible APIs with both matching property names and data types reaches 21. Also, the number of compatible endpoints within the same API is very low.", "image": "/biblio-covers/apiace-icws2022.png", "date_modified": "2022-06-30T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2022/sose-api", "html_content": "", "url": "../biblio/2022/sose-api", "title": "Impact of API Rate Limit on Reliability of Microservices-Based Architectures", "summary": "Many API patterns and best practices have been developed around microservices-based architectures, such as Rate Limiting and Circuit Breaking, to increase quality properties such as reliability, availability, scalability, and performance. Even though estimates on such properties would be beneficial, especially during the early design of such architectures, the real impact of the patterns on these properties has not been rigorously studied yet. This paper focuses on API Rate Limit and its impact on reliability properties from the perspective of API clients. We present an analytical model that considers specific workload configurations and predefined rate limits and then accurately predicts the success and failure rates of the back-end services. The model also presents a method for adaptively fine-tuning rate limits. We performed two extensive data experiments to validate the model and measured Rate Limiting impacts, firstly on a private cloud to minimize latency and other biases, and secondly on the Google Cloud Platform to test our model in a realistic cloud environment. In both experiments, we observed a low percentage of prediction errors. Thus, we conclude that our model can accurately predict the impact of Rate Limiting on the reliability of microservices-based architectures.", "image": "/biblio-covers/apiace-sose2022.png", "date_modified": "2022-07-31T22:00:00Z", "author": { "name": "Amine El Malki" } }, { "id": "biblio/2022/jwe", "html_content": "", "url": "../biblio/2022/jwe", "title": "A Large-scale Empirical Assessment of Web API Size Evolution", "summary": "Like any other type of software, also Web Application Programming Interfaces (APIs) evolve over time. In the case of widely used API, introducing changes is never a trivial task, because of the risk of breaking thousands of clients relying on the API. In this paper we conduct an empirical study over a large collection of OpenAPI descriptions obtained by mining open source repositories. We measure the speed at which Web APIs change and how changes affect their size, simply defined as the number of operations. The dataset of API descriptions was collected over a period of one year and includes APIs with histories spanning across up to 7 years of commits. The main finding is that APIs tend to grow, although some do reduce their size, as shown in the case study examples included in the appendix.", "image": "/biblio-covers/apiace-jwe-2022.png", "date_modified": "2022-10-31T23:00:00Z", "author": { "name": "Fabio Di Lauro" } }, { "id": "biblio/2022/sosym", "html_content": "", "url": "../biblio/2022/sosym", "title": "Live process modeling with the BPMN Sketch Miner", "summary": "BPMN Sketch Miner is a modeling environment for generating visual business process models starting from constrained natural language textual input. Its purpose is to support business process modelers who need to rapidly sketch visual BPMN models during interviews and design workshops, where participants should not only provide input but also give feedback on whether the sketched visual model represents accurately what has been described during the discussion. In this article, we present a detailed description of the BPMN Sketch Miner design decisions and list the different control flow patterns supported by the current version of its textual DSL. We also summarize the user study and survey results originally published in MODELS 2020 concerning the tool usability and learnability and present a new performance evaluation regarding the visual model generation pipeline under actual usage conditions. The goal is to determine whether it can support a rapid model editing cycle, with live synchronization between the textual description and the visual model. This study is based on a benchmark including a large number of models (1350 models) exported by users of the tool during the year 2020. The main results indicate that the performance is sufficient for a smooth live modeling user experience and that the end-to-end execution time of the text-to-model-to-visual pipeline grows linearly with the model size, up to the largest models (with 195 lines of textual description) found in the benchmark workload.", "image": "/biblio-covers/bpmn-sketch-miner-sosym2022.png", "date_modified": "2022-09-30T22:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2022/ecsa", "html_content": "", "url": "../biblio/2022/ecsa", "title": "To deprecate or to simply drop operations? An empirical study on the evolution of a large OpenAPI collection", "summary": "OpenAPI is a language-agnostic standard used to describe Web APIs which supports the explicit deprecation of interface features. To assess how APIs evolve over time and observe how their developers handle the introduction of breaking changes, we performed an empirical study on a dataset composed of more thanone million API operations described using OpenAPI and Swagger format. Our results focus on detecting breaking changes engendered by operations removal and whether and to which extent deprecation is used to warn clients and developers about dependencies they should no longer rely on. Out of the 41,627 APIs considered, we found only 263 (0.6) in which some operations are deprecated before being removed, while the developers of 10,242 (24.6%) of them directly remove operations without first informing their clients about the potentially breaking change. Furthermore, we found that only 5.2% of the explicit-deprecated operations and 8.0% of the deprecated-in-description operations end with a removal, suggesting a tendency to deprecate operations without removing them. Overall, we observed a low negative correlation between the relative amount of deprecated operations and the age of the corresponding APIs.", "image": "/biblio-covers/apiace-ecsa2022-deprecate.png", "date_modified": "2022-08-31T22:00:00Z", "author": { "name": "Fabio Di Lauro" } }, { "id": "biblio/2022/icsa", "html_content": "", "url": "../biblio/2022/icsa", "title": "Web APIs Structures and Data Models Analysis", "summary": "Microservice architectures emphasize keeping components small, to foster autonomy, low coupling, and independent evolution. In this large-scale empirical study, we measure the size of Web API specifications mined from open source repositories. These APIs are modeled using the OpenAPI Specification (OAS), which, in addition to documenting the offered operations, also contain schemas definitions for the data exchanged with the API request and response message payloads. This study has as a goal to build empirical knowledge about: (1) How big and diverse are real-world web APIs both in terms of their operations and data, (2) How different API structures use and reuse schema definitions. By mining public software repositories on Github, we gathered 42,194 valid OAS specifications published between 2014-2021. ", "image": "/biblio-covers/apiace-icsa2022.png", "date_modified": "2022-02-28T23:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/book/beautiful-api-evolution", "html_content": "", "url": "../biblio/book/beautiful-api-evolution", "title": "Beautiful API Evolution", "summary": "This book presents the catalog of a virtual exhibition featuring different visualizations of the structural evolution of 51 Web APIs of different sizes and shapes, showing how they mostly grow but sometimes also shed some dead branches over the years.\n\nThe diagrams are drawn based on the exact OpenAPI specifications as they were versioned on some open source repository.\n\nWhile there are many books on how to improve the design of existing APIs, the goal of this book is to show a small sample of actual API designs undergoing change. Learn from these examples to avoid false starts and discover which structures turn out to be stable over the years.\n\nAll APIs represented are Web APIs: they come from the age when many attempted with very different results to use the HTTP protocol to remotely invoke software delivered as a service.\n\nThe APIs have been selected mainly due to their visual appearance.", "image": "/biblio-covers/beautiful-api-evolution.png", "date_modified": "2021-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/book/beautiful-apis", "html_content": "", "url": "../biblio/book/beautiful-apis", "title": "Beautiful APIs", "summary": "This book presents the catalog of a virtual exhibition featuring the structural visualizations of 93 Web APIs of different sizes and shapes. The diagrams are drawn based on the exact API specification found on some open source repository.\n\nWhile there are many books on how to design good APIs, the goal of this book is to show a small sample of actual API designs. There is a lot that can be learned from them.\n\nAll APIs represented are Web APIs: they come from the time when many attempted with very different results to use the HTTP protocol to remotely invoke software delivered as a service.\n\nThe APIs have been selected mainly due to their visual appearance.", "image": "/biblio-covers/beautiful-apis.png", "date_modified": "2021-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2021/europlop", "html_content": "", "url": "../biblio/2021/europlop", "title": "From OpenAPI Fragments to API Pattern Primitives and Design Smells", "summary": "In the past few years, the OpenAPI Specification (OAS) has emerged as a standard description language for accurately modeling Web APIs.\nToday, thousands of OpenAPI descriptions can be found by mining open source repositories. In this paper, we attempt to exploit these artifacts to extract commonly occurring building blocks used in Web API structures, in order to assist Web API designers in their modelling task. Our work is based on a fragmentation mechanism, that starts from OpenAPI descriptions of Web APIs to extract their structures, then fragment these structures into smaller blocks. This approach enabled us to extract a large dataset of reoccurring fragments from a collection of 6619 API specifications. \nSuch fragments have been found multiple times in the same or across different APIs. We have classified the most reoccurring fragments into four pattern primitives used to expose in the API access to collections of items. We distinguish for each primitive variants from design smells. This classification is based on the specific combinations of operations associated with the collection items and on an in-depth analysis of their natural language labels and descriptions. The resulting pattern primitives are intended to support designers who would like to introduce one or more collections for a specific class of items in their HTTP-based API.", "date_modified": "2021-06-30T22:00:00Z", "author": { "name": "Souhaila Serbout" } }, { "id": "biblio/2021/computer", "html_content": "", "url": "../biblio/2021/computer", "title": "Isomorphic Internet of Things Architectures With Web Technologies", "summary": "Internet of Things development needs isomorphic software architectures, in which every kind of device can be programmed with a consistent set of implementation technologies, allowing applications and their components to be statically deployed or dynamically migrated without having to change their shape.", "date_modified": "2021-06-30T22:00:00Z", "author": { "name": "Tommi Mikkonen" } }, { "id": "biblio/2021/plop", "html_content": "", "url": "../biblio/2021/plop", "title": "Patterns on Designing API Endpoint Operations", "summary": "Domain-driven design (DDD) is often applied when implementing microservices or communicating through APIs in distributed\nsystems. APIs expose a published language that provides a view on entire domain models or subsets of such models. Hence,\ntactical DDD patterns such as Aggregate, Service, and Entity may not only structure API implementations, but also guide API\nspecification work. In our previous work, we described endpoint-level patterns for this context. In this paper, we present three\ncomplementary patterns, namely Aggregated Domain Operation on API Endpoint, Event-Based API Endpoint Operation, and\nCRUD-Based API Operation. These patterns aim to derive API operations from the operations of Domain Services and Entities\nas well as Domain Events. We also discuss variants of these patterns, such as their combination with the patterns Command\nQuery Responsibility Segregation (CQRS) and Publish/Subscribe. Our pattern mining work is based on a data set from an\nempirical study of 32 grey literature sources investigating practitioner views on deriving API designs from DDD models.", "image": "/biblio-covers/plop21-api.png", "date_modified": "2021-09-30T22:00:00Z", "author": { "name": "Apitchaka Singjai" } }, { "id": "biblio/2021/icwe-liquid", "html_content": "", "url": "../biblio/2021/icwe-liquid", "title": "Towards Seamless IoT Device-Edge-Cloud Continuum", "summary": "In this paper we revisit a taxonomy of client-side IoT software architectures that we presented a few years ago. We note that the emergence of inexpensive AI/ML hardware and new communication technologies are broadening the architectural options for IoT devices even further. These options can have a significant impact on the overall end-to-end architecture and topology of IoT systems, e.g., in determining how much computation can be performed on the edge of the network. We study the implications of the IoT device architecture choices in light of the new observations, as well as make some new predictions about future directions. Additionally, we make a case for isomorphic IoT systems in which development complexity is alleviated with consistent use of technologies across the entire stack, providing a seamless continuum from edge devices all the way to the cloud.", "date_modified": "2021-01-01T00:00:00Z", "author": { "name": "Taivalsaari" } }, { "id": "biblio/2021/icwe-full-stack", "html_content": "", "url": "../biblio/2021/icwe-full-stack", "title": "Full Stack is Not What It Used to Be", "summary": "The traditional definition of full stack development refers to a skill set that is required for writing software both for the frontend and backend of a web application or site. In recent years, the scope of full stack development has expanded significantly, though. Today, a full stack software developer is assumed to master various additional areas especially related to cloud infrastructure and deployment, message brokers and data analytics technologies. In addition, the emergence of Internet of Things (IoT) and the rapidly spreading use of AI/ML technologies are introducing additional skill set requirements. In this paper, we discuss the expectations for a modern full stack developer based on our industry observations, and argue that these expectations have significant implications for software and web engineering education.", "image": "/biblio-covers/icwe2021-fullstack.png", "date_modified": "2021-04-30T22:00:00Z", "author": { "name": "Antero Taivalsaari" } }, { "id": "biblio/2021/icwe-wasm", "html_content": "", "url": "../biblio/2021/icwe-wasm", "title": "WebAssembly Modules as Lightweight Containers for Liquid IoT Applications", "summary": "Going all the way to IoT with web technologies opens up the door to isomorphic IoT system architectures, which deliver flexible deployment and live migration of code between any device in the overall system. In this vision paper, we propose using WebAssembly to implement lightweight containers and deliver the required portability. Our long-term vision is to use the technology to support developers of liquid IoT applications offering seamless, hassle-free use of multiple devices.", "date_modified": "2021-04-30T22:00:00Z", "author": { "name": "Niko Mäkitalo" } }, { "id": "biblio/2021/icwe-api-evolution", "html_content": "", "url": "../biblio/2021/icwe-api-evolution", "title": "Towards Large-scale Empirical Assessment of Web APIs Evolution", "summary": "Web Application Programming Interfaces (APIs) decouple the internal implementation of a service from its consumers which can reuse and compose them to rapidly build new applications.\nMany Web APIs are described with the OpenAPI Specification (OAS). The goal of our research is to check the feasibility of using API descriptions found in public open source repositories to study how APIs evolve over time. To do so, we collected a large dataset of OAS documents by crawling open source repositories, we parsed the corresponding metadata and measured the API size in order to extract a simple model to track the lifecycle of API artifacts and observe common evolution behaviors. Our preliminary results indicate that only a subset of the APIs changes, but as opposed to the expectation that APIs should only grow to maintain backward compatibility we also detected a number of APIs with a more variable history. We also study the stability of API artifacts over time and whether APIs are more or less likely to change as they age.", "date_modified": "2021-04-30T22:00:00Z", "author": { "name": "Fabio Di Lauro" } }, { "id": "biblio/book/business-process-management", "html_content": "", "url": "../biblio/book/business-process-management", "title": "Business Process Modeling, Management, and Mining: visual lecture notes", "summary": "Processes are everywhere. Learn how to recognize them using process modeling, reconstruct them with process mining, improve them with process simulation, and run them with process automation. And yes, also visualize them with the Business Process Model and Notation (BPMN).\n\nThese are the revised and illustrated notes of the BPM3 lecture of the Master in Management and Informatics held at the Faculty of Informatics and Economics at USI Lugano, Switzerland during the Spring of 2020.\n\nThe book includes the slides and the script for all lectures:\n\n
  1. Introduction
  2. Modeling
  3. BPMN
  4. Mining
  5. Improvement
  6. Simulation
  7. Automation
", "image": "/biblio-covers/business-process-management.png", "date_modified": "2021-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/book/software-architecture", "html_content": "", "url": "../biblio/book/software-architecture", "title": "Software Architecture: visual lecture notes", "summary": "From quality attributes to how to design and model components, interfaces, connectors, containers, all the way to services and microservices. \nThese are the revised and illustrated notes of the Software Architecture lecture of the Master in Software and Data Engineering held at the Software Institute at USI Lugano, Switzerland during the Spring of 2020.\nThe book includes the script for these lectures:\n", "image": "/biblio-covers/software-architecture.png", "date_modified": "2020-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2020/icwe2020", "html_content": "", "url": "../biblio/2020/icwe2020", "title": "20th International Conference on Web Engineering (ICWE)", "date_modified": "2020-05-31T22:00:00Z", "author": { "name": "Mária Bieliková" } }, { "id": "biblio/2020/sle", "html_content": "", "url": "../biblio/2020/sle", "title": "Role of interactive presentation platform ASQ in delivering web design course", "summary": "Contemporary technology enhanced learning together with different innovative learning methodologies are significantly initiating progress in educational ecosystems. Educational systems and tools that invoke active participation of learners are excellent facilitators of modern education. One such system is ASQ. ASQ is an interactive presentation platform that allows teachers to incorporate interactive questions in their presentations. Learners are then answering these questions on site on their digital devices. In that way teachers have immediate feedback from learners, allowing them to adjust course of presentation. In this paper we tried to determine in what extent is ASQ beneficial for learners. For that purpose we conducted analysis on the data collected from Web Design course, where ASQ was utilized during two school years. Results of the analysis suggest that ASQ has a positive influence on learners' acquired knowledge.", "image": "/biblio-covers/ASQ-sle2021.png", "date_modified": "2020-04-30T22:00:00Z", "author": { "name": "Brankica Bratić" } }, { "id": "biblio/2020/bpmn-sketch-miner-models", "html_content": "", "url": "../biblio/2020/bpmn-sketch-miner-models", "title": "From Text to Visual BPMN Process Models: Design and Evaluation", "summary": "Most existing Business Process Model and Notation (BPMN) editing tools are graphical, and as such based on explicit modeling, requiring good knowledge of the notation and its semantics, as well as the ability to analyze and abstract business requirements and capture them by correctly using the notation. As a consequence, their use can be cumbersome for live modeling during interviews and design workshops, where participants should not only provide input but also give feedback on how it has been represented in a model. To overcome this, in this paper we present the design and evaluation of BPMN Sketch Miner, a tool which combines notes taking in constrained natural language with process mining to automatically produce BPMN diagrams in real time as interview participants describe them with stories. In this work we discuss the design decisions regarding the trade-off between using mining vs. modelling in order to: 1) support a larger number of BPMN constructs in the textual language; 2) target both BPMN beginners and business analysts, in addition to the process participants themselves. The evaluation of the new version of the tool in terms of how it balances the expressiveness and learnability of its DSL with the usability of the text-to-visual sketching environment shows encouraging results. Namely while BPMN beginners could model a non-trivial process with the tool in a relatively short time and with good accuracy, business analysts appreciated the usability of the tool and the expressiveness of the language in terms of supported BPMN constructs. ", "date_modified": "2020-09-30T22:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2020/ieesw-blockchain", "html_content": "", "url": "../biblio/2020/ieesw-blockchain", "title": "Blockchain and Smart Contract Engineering", "summary": "Blockchains help to build trust among a decentralized network of unknown and untrusted peers who need to agree on a common protocol and trust the correctness and compatibility of the corresponding software implementations. The software engineering discipline cannot ignore this trend, as it fundamentally affects the way software is designed, developed, deployed, and delivered. Developers need guidance on how to write secure smart contracts for solving new classes of real-world problems, as opposed to introducing blockchains everywhere, where they may be unnecessary, or provide an inefficient and environmentally unsound solution.", "date_modified": "2020-09-30T22:00:00Z", "author": { "name": "Xabier Larrucea" } }, { "id": "biblio/2020/ieeesw-blockchain-interview", "html_content": "", "url": "../biblio/2020/ieeesw-blockchain-interview", "title": "Unchain or Block the Hype? Decision Drivers, Success Factors, and Perspectives for Blockchain Adoption", "summary": "For this special issue Insights features an interview with three domain experts on blockchain adoption", "date_modified": "2020-09-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2020/bac-iccs", "html_content": "", "url": "../biblio/2020/bac-iccs", "title": "Microservice Disaster Crash Recovery: A Weak Global Referential Integrity Management", "summary": "Microservices which use polyglot persistence (using multiple data storage techniques) cannot be recovered in a consistent state from backups taken independently. As a consequence, references across microservice boundaries may break after disaster recovery. \nIn this paper, we give a weak global consistency definition for microservice architectures and present a recovery protocol which takes advantage of cached referenced data to reduce the amnesia interval for the recovered microservice, i.e., the time interval after the most recent backup, during which state changes may have been lost.", "date_modified": "2020-05-31T22:00:00Z", "author": { "name": "Maude Manouvrier" } }, { "id": "biblio/2020/restalk-ms", "html_content": "", "url": "../biblio/2020/restalk-ms", "title": "Modeling Microservice Conversations with RESTalk", "summary": "Microservices are characterized by their small size and low degree of coupling. As a consequence, building microservice architectures requires composing multiple microservices and determine how they interact to achieve a given client's goal. In this chapter we introduce the concept of RESTful conversation, whereby clients or API gateways perform multiple basic HTTP request/response interactions with one or more microservice APIs. To represent possible sequences of interactions, we introduce the RESTalk visual notation, as well as its textual DSL, and the corresponding metamodel, and show how it can be used to complement existing structural approaches to represent RESTful APIs, such as the OpenAPI Specification. To reveal the degree of coupling between clients and microservices, the language supports the concept of hyperlink flow, showing whether, within a conversation, the links embedded into responses provided by a microservice are used by the client/API gateway to form the subsequent requests.", "date_modified": "2020-01-01T00:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2020/jwe", "html_content": "", "url": "../biblio/2020/jwe", "title": "Multi-Device Complementary View Adaptation with Liquid Media Queries", "summary": "Responsive Web applications assume that they run on a single device at a time. Developers use CSS3 media queries to declare how the Web application user interface adapts to specific capabilities (e.g., screen size or resolution) of individual devices. As users own and use multiple devices across which they attempt to run the same Web application at the same time, we propose to extend CSS media queries so that developers can also use them to dynamically adapt so-called liquid Web applications as they are seamlessly deployed across multiple devices. In this paper we present the concept of liquid media queries. They support features to detect the number of connected devices, the number of users running the application, or the role played by each device during the application execution. The liquid media query types and features defined in this paper are designed for component-based Web applications, and they enable developers to control the deployment and dynamic migration and cloning of individual Web components across multiple browsers. Furthermore we present the design of how liquid media queries are implemented within the Liquid.js for Polymer framework and the corresponding distributed adaptation algorithms. We discuss the implications of multi-device adaptation from the perspective of the developers and also the users of a liquid Web application. Finally we showcase the expressiveness of the liquid media queries to support real-world examples and evaluate the algorithmic complexity of our approach.\n", "image": "/biblio-covers/liquidjs-jwe2019.png", "date_modified": "2020-01-01T00:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2019/esdebp", "html_content": "", "url": "../biblio/2019/esdebp", "title": "Empirical Studies on the Development of Executable Business Processes", "summary": "This book collects essential research on the practical application of executable business process modeling in real-world projects, i.e., model-driven solutions for the support and automation of digital business processes that are created using languages such as BPEL or BPMN. It mainly focuses on empirical research, but also includes an up-to-date cross-section of case studies in order to assess examples of BPM's practical impact in the industry.\nOn the one hand, executable models are formally and precisely defined so that computers can interpret and execute them; on the other, they are visualized so that humans can describe, document and optimize business processes at a higher level of abstraction than with traditional textual programming languages. While these important research areas have long been separated from one another, this book is an attempt at cross-fertilization, driven by the insight that business processes are the software behind today's digital organizations, and that achieving a precise representation of such processes is key to their reliable execution. Consequently, the book presents various case studies and experiments that investigate questions of interest to both academia (e.g., identifying challenges for which no solution exists; sharing new insights into how existing approaches are actually used) and industry (e.g., guidelines on using certain technologies and on modeling comprehensible and executable processes).\nBoth researchers and practitioners will benefit from the presentation of how concepts are transformed into working solutions. The studies are presented in a structured manner and with sufficient rigor to be considered empirical research, further enhancing the book's value for the research community, while practitioners will find concrete guidance on making the right decisions for their projects.", "image": "/biblio-covers/esdebp.png", "date_modified": "2019-01-01T00:00:00Z", "author": { "name": "Daniel Lübke" } }, { "id": "biblio/2019/ce-askalot", "html_content": "", "url": "../biblio/2019/ce-askalot", "title": "Employing community question answering for online discussions in university courses: Students' perspective", "summary": "In university courses as well as in MOOCs, Community Question Answering (CQA) systems have been recently recognized as a promising alternative to standard discussion forums for mediating online discussions. Despite emerging research on educational CQA systems, a study investigating when and how to use these systems to support university education is still missing. We stress that such a study should effectively take into account students'perceptions of CQA systems rather than relying solely on an analysis of their effective usage based on data available in system logs. This paper therefore systematically analyzes perspective of 182 computer science students from three universities located in three different countries on concept of educational CQA systems. Students'opinions were collected using a questionnaire that was designed to assess conceptual issues of using CQA systems in university education, their core features as well as particular implementation of our CQA system Askalot. The analysis of collected responses based on non-parametric statistical tests revealed that there are various significant differences in the perception of CQA systems between different types of students (e.g. passive and active) and in different deployment settings (e.g. when using CQA in a small number of 1-3 courses during one academic year or in 50 courses for 5 years). The obtained findings supported by content and usage analysis finally resulted into the summary of 12 main characteristics of CQA systems which describe their suitability for mediating online discussions in different deployment settings and for different types of students.", "date_modified": "2019-06-30T22:00:00Z", "author": { "name": "Ivan Srba" } }, { "id": "biblio/2019/icwe-liquidstyle", "html_content": "", "url": "../biblio/2019/icwe-liquidstyle", "title": "Multi-device Adaptation with Liquid Media Queries", "summary": "The design of responsive Web applications is traditionally based on the assumption that they run on a single client at a time. Thanks to CSS3 media queries, developers can declaratively specify how the Web application UI adapts to the capabilities of specific devices. As users own more and more devices and they attempt to use them to run Web applications in parallel, we propose to extend CSS media queries so that they can be used to adapt the UI of liquid Web applications while they are dynamically deployed across multiple devices. In this paper we present our extension of CSS media queries with liquid-related types and features, allowing to detect the number of devices connected, the number of users running the application, or the role played by each device. The liquid media query types and features defined in this paper are designed and suitable for liquid component-based Web architectures, and they enable developers to control the deployment of individual Web components across multiple browsers. Furthermore we show the design of liquid media queries in the Liquid.js for Polymer framework and propose different adaptation algorithms. Finally we showcase the expressiveness of the liquid media queries to support real-world examples and evaluate the algorithmic complexity of our approach.", "image": "/biblio-covers/icwe2019-liquidstyle.png", "date_modified": "2019-05-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2019/icwe-cornucopia", "html_content": "", "url": "../biblio/2019/icwe-cornucopia", "title": "On the Web Platform Cornucopia", "summary": "The evolution of the Web browser has been organic, with new features introduced on a pragmatic basis rather than following a clear rational design. This evolution has resulted in a cornucopia of overlapping features and redundant choices for developing Web applications. These choices include multiple architecture and rendering models, different communication primitives and protocols, and a variety of local storage mechanisms. In this position paper we examine the underlying reasons for this historic evolution. We argue that without a sound engineering approach and some fundamental rethinking there will be a growing risk that the Web may no longer be a viable, open software platform in the long run.", "image": "/biblio-covers/icwe2019-cornucopia.png", "date_modified": "2019-05-31T22:00:00Z", "author": { "name": "Tommi Mikkonen" } }, { "id": "biblio/2019/icpe", "html_content": "", "url": "../biblio/2019/icpe", "title": "Behavior-driven Load Testing Using Contextual Knowledge - Approach and Experiences", "summary": "Load testing is widely considered a meaningful technique for performance quality assurance. However, empirical studies reveal that in practice, load testing is not applied systematically, due to the sound expert knowledge required to specify, implement, and execute load tests. Our Behavior-driven Load Testing (BDLT) approach eases load test specification and execution for users with no or little expert knowledge. It allows a user to describe a load test in a template based on natural language and to rely on an automated framework to execute the test. Utilizing the system's contextual knowledge such as workload-influencing events, the framework automatically determines the workload and test configuration. We investigated the applicability of our approach in an industrial case study, where we were able to express four load test concerns using BDLT and received positive feedback from our industrial partner. They understood the BDLT definitions well and proposed further applications, such as the usage for software quality acceptance criteria.", "image": "/biblio-covers/benchflow-icpe2019.png", "date_modified": "2019-03-31T22:00:00Z", "author": { "name": "Henning Schulz" } }, { "id": "biblio/2019/europlop", "html_content": "", "url": "../biblio/2019/europlop", "title": "Interface Evolution Patterns - Balancing Compatibility and Flexibility across Microservices Lifecycles", "summary": "Remote Application Programming Interfaces (APIs) are technology enablers for distributed system trends such as cloud-native application development. API providers find it hard to design their remote APIs so that they can be evolved easily; refactoring and extending an API while preserving backward compatibility is particularly challenging. If APIs are evolved poorly, clients are critically impacted; high costs to adapt and compensate for downtimes may result. For instance, if an API provider publishes a new incompatible API version, existing clients might break and not function properly until they are upgraded to support the new version. Hence, applying adequate strategies for evolving service APIs is one of the core problems in API governance, which in turn is a prerequisite for successfully integrating service providers with their clients in the long run. Although many patterns and pattern languages are concerned with API and service design and related integration technologies,patterns guiding the evolution of APIs are missing to date. Extending our pattern language on Microservice API Patterns (MAP), we introduce a set of patterns focusing on API evolution strategies in this paper: API Description, Version Identifier, Semantic Versioning, Eternal Lifetime Guarantee, Limited Lifetime Guarantee, Two in Production, Aggressive Obsolescence, and Experimental Preview.The patterns have been mined from public Web APIs and industry projects the authors have been involved in.", "image": "/biblio-covers/MAP-europlop2019.png", "date_modified": "2019-06-30T22:00:00Z", "author": { "name": "Daniel Lübke" } }, { "id": "biblio/2019/jwe", "html_content": "", "url": "../biblio/2019/jwe", "title": "The LiquidWebWorker API for Horizontal Offloading of Stateless Computations", "summary": "As most users access the Web from multiple devices with different characteristics, ranging from powerful desktops or laptops to tablets, mobile phones or watches and cars, liquid Web applications seamlessly flow across multiple Web-enabled devices and adapt their distributed user interface to the set of devices simultaneously accessing the application. In this paper we focus on the business logic layer of rich Web applications and explore the opportunity to reduce the execution time of CPU-intensive tasks or limit their energy consumption by offloading them among nearby devices running the same liquid Web application. We extend the standard HTML5 WebWorker API with the concept of liquid WebWorkers, so that developers can transparently offload parallel execution of stateless tasks by managing the necessary device selection and direct peer-to-peer data transfer. By introducing the liquid WebWorker API into our Liquid.js framework, we present how to create a pool of devices sharing their CPU processing capabilities according to different policies.", "date_modified": "2019-02-28T23:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2019/ijwgs", "html_content": "", "url": "../biblio/2019/ijwgs", "title": "SAW-Q: a dynamic composition approach of REST services based on queue model", "summary": "Service composition is one of the principles of service-oriented architecture; it enables reuse and allows developers to combine existing services in order to create new services that in turn can be part of another composition. Dynamic composition requires that service components are chosen from a set of services with equal or similar functionality at runtime and possibly automatically. The adoption of the REST services in the industry has led to a growing number of services of this type, many with similar functionality. The existing dynamic composition techniques are method-oriented whereas REST is resource-oriented and consider only traditional (WSDL/SOAP) services. We propose SAW-Q, an extension of simple additive weighting (SAW), as a novel dynamic composition technique that follows the principles of the REST style. Additionally, SAW-Q models quality attributes as a function of the actual service demand instead of the traditional constant values. Our model is much more accurate when compared to real implementation, positively improving the quality of dynamic service compositions.", "date_modified": "2018-12-31T23:00:00Z", "author": { "name": "Jesus Bellido" } }, { "id": "biblio/2018/icwe-workshops", "html_content": "", "url": "../biblio/2018/icwe-workshops", "title": "Proc. of the Workshops held at the 18th International Conference on Web Engineering (ICWE 2018): MATWEP, EnWot, KD-WEB, WEOD, TourismKG", "image": "/biblio-covers/icwe2018-workshops.png", "date_modified": "2018-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2018/icsoc", "html_content": "", "url": "../biblio/2018/icsoc", "title": "Guiding Architectural Decision Making on Quality Aspects of Microservice APIs", "summary": "Microservice APIs represent the client perspective on microservice-based software architecture design and related practices. Major issues in API design concern the quality aspects of the API. However, it is not well understood today what the established practices related to those quality aspects are, how these practices are related, and what the major decision drivers are. This leads to great uncertainty in the design process. In this paper, we report on a qualitative, in-depth study of 31 widely used APIs plus 24 API specifications, standards, and technologies. In our study we identified six recurring architectural design decisions in two API design contexts with a total of 40 decision options and a total of 47 decision drivers. We modelled our findings in a formal, reusable architectural decision model. We measured the uncertainty in the resulting design space with and without use of our model, and found that a substantial uncertainty reduction can be potentially achieved by applying our model.", "image": "/biblio-covers/MAP-icsoc2018.png", "date_modified": "2018-10-31T23:00:00Z", "author": { "name": "Uwe Zdun" } }, { "id": "biblio/2018/icsoc-restalk-electra", "html_content": "", "url": "../biblio/2018/icsoc-restalk-electra", "title": "ELeCTRA: induced usage limitations calculation in RESTful APIs", "summary": "As software architecture design is evolving to microservice paradigms, RESTful APIs become the building blocks of applications. In such a scenario, a growing market of APIs is proliferating and developers face the challenges to take advantage of this reality. For an example, third-party APIs typically define different usage limitations depending on the purchased Service Level Agreement (SLA) and, consequently, do- ing a manual limitation analysis of external APIs and their impact in a microservice architecture is a complex and tedious task. In this demonstration paper, we present ELeCTRA, a tool to automate the analysis of induced limitations in an API, derived from its usage of external APIs with limitations. Specifically, this tools takes the structural, conversational and SLA specifications of the API, generates a visual dependency graph and translates the problem into a constraint satisfaction optimization problem (CSOP) to obtain the optimal usage limitations.", "date_modified": "2018-10-31T23:00:00Z", "author": { "name": "Antonio Gamez-Diaz" } }, { "id": "biblio/2018/icsoc-demo-restalk", "html_content": "", "url": "../biblio/2018/icsoc-demo-restalk", "title": "RESTalk Miner: Mining RESTful Conversations, Pattern Discovery and Matching", "summary": "REST has become the architectural style of choice for APIs, where clients need to instantiate a potentially lengthy sequence of requests to the server in order to achieve their goal, effectively leading to a RESTful conversation between the client and the server. \nMining the logs of such RESTful conversations can facilitate knowledge sharing among API designers regarding design best practices as well as API usage and optimization. In this demo paper, we present the RESTalk Miner, which takes logs from RESTful services as an input and uses RESTalk, a domain specific language, to visualize them. It provides interactive coloring to facilitate graph reading, as well as statistics to compare the relative frequency of conversations performed by different clients. Furthermore, it supports searching for predefined patterns as well as pattern discovery. ", "image": "/biblio-covers/restalk-demo-icsoc2018.png", "date_modified": "2018-10-31T23:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2018/dsldi", "html_content": "", "url": "../biblio/2018/dsldi", "title": "Modeling REST API Behaviour with Text, Graphics or Both?", "summary": "The dissemination of domain specific modeling languages in the software engineering world can be challenging as developers love to code and frequently look at graphical modeling as unnecessary and inefficient. This is less true when they are developing business facing software as the end users are non-technical people, and models become a common language to facilitate the communication with them, which explains the diffusion of modeling languages such as for example the Business Process Modeling Notation (BPMN). However, in Application Programming Interface (API) design, where both the creators and the users of the API are developers, the perceived benefits of modeling using a visual notation can be less evident for the developers. When developing APIs adhering to the REpresentation State Transfer (REST) architectural style, the documentation best practices of the structure of the API, i.e., the exposed resources and the HTTP methods that they support together with the corresponding media types, has been evolving in the past decade across a number of textual Domain Specific Languages (DSLs) currently being standardized within the Open API initiative. However, modeling the dynamics of the REST API showing the request-response interactions leading to conversations between clients and one or more resources exposed within the API is not yet a common practice. Thus, we have been working on designing RESTalk, a visual DSL for modeling RESTful conversations, i.e., sequences of client-server interactions aimed at achieving a certain goal. We have conducted a short exploratory survey where, regardless of the positive feedback on the usefulness of such a DSL and the cognitive characteristics of RESTalk, many of the respondents conditioned the adoption of the language to the existence of a suitable modeling tool. Faced with the challenge of developing such a tool, in this talk we would like to pinpoint a critical issue within the design space concerning the input modalities supported by a modeling tool tailored for RESTful APIs. Our goal is to encourage further discussions and empirical studies on what are the pros and cons of different approaches to modeling tools' design and whether and how the targeted users of the modeling tool (e.g, business people, software architects, developers) affect the design choices.", "date_modified": "2018-10-31T23:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2018/coopis", "html_content": "", "url": "../biblio/2018/coopis", "title": "Evaluating Multi-Tenant Live Migrations Effects on Performance", "summary": "Multitenancy is an important feature for all Everything as a Service providers like Business Process Management as a Service. It allows to reduce the cost of the infrastructure since multiple tenants share the same service instances. However, tenants have dynamic workloads. The resource they share may not be sufficient at some point in time. It may require Cloud resource (re-)configurations to ensure a given Quality of Service. Tenants should be migrated without stopping the service from a configuration to another to meet their needs while minimizing operational costs on the provider side. Live migrations reveal many challenges: service interruption must be minimized and the impact on co-tenants should be minimal. In this paper, we investigate live tenants migrations duration and its effects on the migrated tenants as well as the co-located ones. To do so, we propose a generic approach to measure these effects for multi-tenant Software as a Service. Further, we propose a testing framework to simulate workloads, and observe the impact of live migrations on Business Process Management Systems. The experimental results highlight the efficiency of our approach and show that migration time depends on the size of data that have to be transferred and that the effects on co-located tenants should not be neglected. ", "date_modified": "2018-09-30T22:00:00Z", "author": { "name": "Guillaume Rosinosky" } }, { "id": "biblio/2018/wesoacs", "html_content": "", "url": "../biblio/2018/wesoacs", "title": "May Contain Nuts: The Case for API Labels", "summary": "As APIs proliferate, managing the constantly growing and evolving API landscapes inside and across organizations becomes a challenge. Part of the management challenge is for APIs to be able to describe themselves, so that users and tooling can use descriptions for finding and filtering APIs. A standardized labeling scheme can help to cover some of the cases where API self-description allows API landscapes to become more usable and scalable. In this paper we present the vision for standardized API labels, which summarize and represent critical aspects of APIs. These aspect allow consumers to more easily become aware of the kind of dependency they are going to establish with the service provider when choosing to use them. API labels not only summarize critical coupling factors, but also can include claims that require to be validated by trusted third parties.", "image": "/biblio-covers/wesoacs2018.png", "date_modified": "2018-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2018/webist2018", "html_content": "", "url": "../biblio/2018/webist2018", "title": "Web User Interface Implementation Technologies: An Underview", "summary": "Over the years, the World Wide Web has evolved from a document distribution environment into a rich development platform that can run compelling, full-fledged software applications. However, the programming capabilities of the web browser \\textendash designed originally for relatively simple scripting tasks \\textendash have evolved organically in a rather haphazard fashion. Consequently, there are many ways to build applications on the Web today. Depending on one's viewpoint, current standards-compatible web browsers support three, four or even five built-in application rendering and programming models. In this paper, we provide an \\textquotedblrightunderview\\textquotedblright of the built-in client-side web application UI implementation technologies, i.e., a summary of those rendering models that are built into the standards-compatible web browser out-of-the-box. While the dominance of the base HTML/CSS/JS technologies cannot be ignored, we foresee Web Components and WebGL gaining popularity as the world moves towards more complex and even richer web applications, including systems supporting virtual and augmented reality.", "image": "/biblio-covers/webist2018.png", "date_modified": "2018-08-31T22:00:00Z", "author": { "name": "Antero Taivalsaari" } }, { "id": "biblio/2018/scopes-disa2018", "html_content": "", "url": "../biblio/2018/scopes-disa2018", "title": "Short Texts Analysis for Teacher Assistance during Live Interactive Classroom Presentations", "summary": "We aim to improve the communication process of a teacher with students during lectures using question answering. Our work is focused on the analysis of students'answers to support the teacher in his or her lecturing. We work with students'answers to open questions, where it is impossible to identify finite number of solutions. In large classes it is impossible to react in real time to such answers since their evaluation is time consuming. We propose our own approach that helps the teacher by grouping similar answers. These groups are created based on proposed method employing text classification and clustering. Proposed method automatically estimates a number of clusters in answers using combination of k-Nearest Neighbors (KNN) algorithm and affinity propagation. We evaluated the method on real data in Slovak language collected from the course Principles of Software Engineering using real time presentation system ASQ.", "image": "/biblio-covers/scopes-disa2018.png", "date_modified": "2018-07-31T22:00:00Z", "author": { "name": "Michal Hucko" } }, { "id": "biblio/2016/sosym", "html_content": "", "url": "../biblio/2016/sosym", "title": "Visual modeling of RESTful conversations with RESTalk", "summary": "The cost savings introduced by Web services through code re-use and integration opportunities have motivated many businesses to develop Web APIs, with ever increasing numbers opting for the REST architectural style. RESTful Web APIs are decomposed in multiple resources, which the client can manipulate through HTTP interactions with well defined semantics. Getting the resource in the desired state might require multiple client-server interactions, what we define as a RESTful conversation. RESTful conversations are dynamically guided by hypermedia controls, such as links. Thus, when deciding whether and how to use a given RESTful service, the client might not be aware of all the interactions which are necessary to achieve its goal. This is because existing documentation of RESTful APIs describe the static structure of the interface, exposing low-level HTTP details, while little attention has been given to conceptual, high-level, modeling of the dynamics of RESTful conversations. Low-level HTTP details can be abstracted from during the design phase of the API, or when deciding which API to use. We argue that, in these situations, visual models of the required client-server interactions might increase developers' efficiency and facilitate their understanding. Thus, to capture all possible interaction sequences in a given RESTful conversation, we propose RESTalk, an extension to the BPMN Choreography diagrams to render them more concise and yet sufficiently expressive in the specific REST domain. We also report on the results obtained from an exploratory survey we have conducted to assess the maturity of the field for a domain specific language, and to obtain feedback for future improvements of RESTalk.", "image": "/biblio-covers/restalk-SoSyM2016.png", "date_modified": "2018-06-30T22:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2018/europlop-map", "html_content": "", "url": "../biblio/2018/europlop-map", "title": "Interface Quality Patterns --- Crafting and Consuming Message-Based Remote APIs", "summary": "The design and evolution of Application Programming Interfaces (APIs) in microservices architectures is challenging. General design issues in integration and programming have been covered in great detail in many pattern languages since the beginnings of the patterns movement, and service-oriented infrastructure design patterns have also been published in the last decade. However, the interface representations (i.e., the content of message payloads) have received less attention. We presented five structural representation patterns in our previous work; in this paper we continue our coverage of the API design space and propose five interface quality patterns that deal with the observable aspects of quality-attribute-driven interface design for efficiency, security, and manageability: An API Key allows API providers to identify clients. Providers may offer rich data contracts in their responses, which not all consumers might need. A Wish List allows the client to request only the attributes in a response data set that it is interested in. If a client makes many API calls, the provider can employ a Rate Limit and bill clients according to a specified Rate Plan . A provider has to provide a high-quality service while at the same time having to use its available resources economically. The resulting compromise is expressed in a provider's Service Level Agreement. ", "image": "/biblio-covers/MAP-europlop2018.png", "date_modified": "2018-07-05T22:00:00Z", "author": { "name": "Mirko Stocker" } }, { "id": "biblio/2018/europlop-blockchain", "html_content": "", "url": "../biblio/2018/europlop-blockchain", "title": "A Pattern Collection for Blockchain-based Applications", "summary": "Blockchain is an emerging technology that enables new forms of decentralized software architectures, where distributed components can reach agreements on shared system states without trusting a central integration point. Blockchain provides a shared infrastructure to execute programs, called smart contracts, and to store data. Since blockchains are at an early stage, there is a lack of a systematic and holistic view on designing software systems that use blockchain. We view blockchain as part of a bigger system, which requires patterns of using blockchain in the design of the bigger systems. In this paper, we collect a list of patterns for blockchain-based applications. The pattern collection is categorized into four types, including interaction with external world patterns, data management patterns, security patterns and contract structural patterns. Some patterns are designed specifically based on real-world blockchain-based applications considering the nature of blockchain. Others are variants of existing design patterns applied in the context of blockchain-based applications and smart contracts.", "image": "/biblio-covers/blockchain-europlop2018.png", "date_modified": "2018-07-04T22:00:00Z", "author": { "name": "Xiwei Xu" } }, { "id": "biblio/2018/liquidjs-icwe2018", "html_content": "", "url": "../biblio/2018/liquidjs-icwe2018", "title": "Decentralized Computation Offloading on the Edge with Liquid WebWorkers", "summary": "Liquid Web applications seamlessly flow across any kind of device ranging from powerful desktop and laptop devices to smaller devices, such as tablets, smart phones or any device capable of running a Web browser. In this context, there is the opportunity to reduce the execution time of CPU-intensive tasks or limit their energy consumption by offloading them across the set of machines running the liquid Web application. To do so, in this paper we present Liquid WebWorkers, which build upon the standard HTML5 WebWorker API and transparently offload the task execution to other devices and manage the corresponding data transfer. This way, Web developers can reuse their existing WebWorker scripts without any changes. We present how to create a pool of paired devices and compare different policies for choosing the target device that have been implemented in the Liquid.js framework.", "image": "/biblio-covers/liquidjs-icwe2018.png", "date_modified": "2018-06-05T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2018/ieeecloud-bac", "html_content": "", "url": "../biblio/2018/ieeecloud-bac", "title": "Consistent Disaster Recovery for Microservices: the BAC Theorem", "summary": "How do you backup a Microservice? You dump its database. How do you backup an entire application decomposed into microservices? In this paper we discuss the tradeoff between the availability and consistency of a microservice-based architecture, when the backup of the entire system is being performed. We demonstrate that service designers\nhave to select two out of three qualities: Backup, Availability and/or Consistency (BAC),\nand discuss how to deal with consequences such as broken links, orphan state and missing\nstate.", "image": "/biblio-covers/bac-theorem.png", "date_modified": "2018-01-31T23:00:00Z", "author": { "name": "Guy Pardon" } }, { "id": "biblio/2018/liquidjs-WWW2018", "html_content": "", "url": "../biblio/2018/liquidjs-WWW2018", "title": "The Liquid User Experience API", "summary": "Web applications are traditionally designed having in mind a server-centric architecture, whereby the whole persistent data, dynamic state and logic of the application are stored and executed on the Web server. The endpoint client device running the Web browser traditionally only renders pre-computed views fetched from the server. As more data, state and computations are shifted to the client, it becomes more challenging to run Web applications across multiple devices while ensuring they can synchronize their state and react in real-time to changes of the set of available devices. In this paper we present the API of the Liquid.JS framework, which allows developers to deploy their component-based rich Web applications across multiple Web-enabled devices. The framework is based on state of the art technologies such as Polymer, WebRTC DataChannel, WebWorkers, PouchDB and Yjs. Liquid.JS helps to build decentralized Web applications whose components can seamlessly flow directly between Web browsers carrying along their execution state. The Liquid.JS API deals with device discovery, the lifecycle of liquid components and the fine-grained control of the liquid user experience primitives.", "image": "/biblio-covers/liquidjs-WWW2018.png", "date_modified": "2018-04-24T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2018/icpe", "html_content": "", "url": "../biblio/2018/icpe", "title": "A Declarative Approach for Performance Tests Execution in Continuous Software Development Environments", "summary": "Software performance testing is an important activity to ensure quality in continuous software development environments. Current performance testing approaches are mostly based on scripting languages and frameworks where users implement, in a procedural way, the performance tests they want to issue to the system under test. However, existing solutions lack support for explicitly declaring the performance test goals and intents. Thus, while it is possible to express how to execute a performance test, its purpose and applicability context remain implicitly described. In this work, we propose a declarative domain specific language (DSL) for software performance testing and a model-driven framework that can be programmed using the mentioned language and drive the end-to-end process of executing performance tests. Users of the DSL and the framework can specify their performance intents by relying on a powerful goal-oriented language, where standard (e.g., load tests) and more advanced (e.g., stability boundary detection, and configuration tests) performance tests can be specified starting from templates. The DSL and the framework have been designed to be integrated into a continuous software development process and validated through extensive use cases that illustrate the expressiveness of the goal-oriented language, and the powerful control it enables on the end-to-end performance test execution to determine how to reach the declared intent.", "image": "/biblio-covers/benchflow-icpe2018.png", "date_modified": "2018-04-10T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2018/ieeesw", "html_content": "", "url": "../biblio/2018/ieeesw", "title": "The Web as a Software Connector: Integration Resting on Linked Resources", "summary": "The web, seen as a graph of linked resources shared between microservices, can serve as an integration style. It offers unique characteristics and possibilities regarding dataflow, control flow, and other qualities, compared to file transfer, shared databases, remote procedure calls, and asynchronous messaging. Carrying these insights in your toolbox will make you aware of all the options to consider next time you build loosely coupled integrated systems.", "image": "/biblio-covers/IEEESW-2018-WWW-Insights.png", "date_modified": "2018-01-31T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2017/jwe", "html_content": "", "url": "../biblio/2017/jwe", "title": "Architecting Liquid Software", "summary": "The Liquid Software metaphor refers to software that can operate seamlessly across multiple devices owned by one or multiple users. Liquid software applications can take advantage of the computing, storage and communication resources available on all the devices owned by the user. Liquid software applications can also dynamically migrate from one device to another, following the user's attention and usage context. The key design goal in Liquid Software development is to minimize the additional efforts arising from multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home and car displays, and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present the design space for Liquid Software, categorizing and discussing the most important architectural dimensions and technical choices. We also provide an introduction and comparison of two frameworks implementing Liquid Software capabilities in the context of the World Wide Web.\n", "image": "/biblio-covers/liquidjs-JWE2017-architecting-liquid-software.png", "date_modified": "2017-08-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2017/icsa-browser", "html_content": "", "url": "../biblio/2017/icsa-browser", "title": "Comparing the Built-In Application Architecture Models in the Web Browser", "summary": "Depending on one's viewpoint, a generic standards-compatible web browser supports three, four or five built-in application rendering and programming models. In this paper, we provide an overview of the built-in client-side web application architectures. While the dominance of the base HTML/CSS/JS technologies cannot be ignored, we foresee Web Components and WebGL gaining popularity as the world moves towards more complex and even richer web applications, including systems supporting virtual and augmented reality.", "image": "/biblio-covers/icsa2017-browser.png", "date_modified": "2017-03-31T22:00:00Z", "author": { "name": "Antero Taivalsaari" } }, { "id": "biblio/2017/pale", "html_content": "", "url": "../biblio/2017/pale", "title": "Experiences Using an Interactive Presentation Platform in a Functional and Logic Programming Course", "summary": "Modern constructivist approaches to education dictate active experimentation with the study material and have been linked with improved learning outcomes in STEM fields. During classroom time we believe it is important for students to experiment with the lecture material since active recall helps them to start the memory encoding process as well as to catch misconceptions early and to prevent them from taking root. In this paper, we report on our experiences using ASQ, a Web-based interactive presentation tool in a functional and logic programming course taught at the Faculty of Informatics and Information Technologies at the Slovak University of Technology in Bratislava. ASQ allowed us to collect immediate feedback from students and retain their attention by asking complex types of questions and aggregating student answers in real time. From our experience we identified several requirements and guidelines for successfully adopting ASQ. One of the most critical concerns was how to estimate the time when to stop collecting the students' answers and proceed to their evaluation and discussion with the class. We also report the students' feedback on the ASQ system that we collected in the form of the standard SUS questionnaire. \n", "image": "/biblio-covers/ASQ-pale2017.png", "date_modified": "2017-06-30T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/2016/wesoacs", "html_content": "", "url": "../biblio/2016/wesoacs", "title": "Lessons Learned from Evaluating Workflow Management Systems", "summary": "Workflow Management Systems (WfMSs) today act as service composition engines and service-oriented middleware to enable the execution of automated business processes. \nAutomation based on WfMSs promises to enable the model-driven construction of flexible and easily maintainable services with high-performance characteristics. \nIn the past decade, significant effort has been invested into standardizing WfMSs that compose services, with standards such as the Web Services Business Process Execution Language (WS-BPEL) or the Business Process Model and Notation (BPMN).\nOne of the aims of standardization is to enable users of WfMSs to compare different systems and to avoid vendor lock-in. \nDespite these efforts, there are many expectations concerning portability, performance efficiency, usability, reliability and maintainability of WfMSs that are likely to be unfulfilled.\nIn this work, we synthesize the findings of two research initiatives that deal with WfMSs conformance and performance benchmarking to distill a set of lessons learned and best practices. \nThese findings provide useful advice for practitioners who plan to evaluate and use WfMSs and for WfMS vendors that would like to foster wider adoption of process-centric service composition middleware. ", "image": "/biblio-covers/benchflow-wesoacs2017.png", "date_modified": "2017-10-31T23:00:00Z", "author": { "name": "Jörg Lenhard" } }, { "id": "biblio/2017/icwe", "html_content": "", "url": "../biblio/2017/icwe", "title": "Maturity Model for Liquid Web Architectures", "summary": "Whenever a user connects with more that one single device, either sequentially or concurrently, to a liquid Web application, the application adapts to the set of connected devices and it is able to flow seamlessly between them following the user attention. As opposed to traditional centralised architectures, in which the data and logic of the application resides entirely on a Web server, Liquid software needs decentralised or distributed architectures in order to achieve seamless application mobility between clients.\nBy decomposing Web application architectures into layers, following the Model View Controller design pattern, we define a maturity model for Web application architectures evolving from classical solid applications deployed on single devices, to fully liquid applications deployed across multiple Web-enabled devices.\nThe maturity model defines different levels based on where the application layers are deployed and how they migrate or synchronize their state across multiple devices. The goal of the maturity model described in this paper is to understand, control and describe how Web applications following the liquid user experience paradigm are designed and also provide Web developers with a gradual adoption path to evolve existing Web applications.", "image": "/biblio-covers/liquidjs-icwe2017-liquidmaturitymodel.png", "date_modified": "2017-05-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2017/umap", "html_content": "", "url": "../biblio/2017/umap", "title": "Measuring student behaviour dynamics in a large interactive classroom setting", "summary": "Digital devices (most often laptops and smartphones), though desired tools by students in a higher education classroom, have in the past been shown to serve more as distractors than supporters of learning. One of the reasons is the often undirected nature of the devices' usage. With our work we aim to turn students' digital devices into teaching and communication tools by seamlessly interleaving lecture material and complex questions in the students' browser through ASQ, a Web application for broadcasting and tracking interactive presentations. ASQ's fine-grained logging abilities allow us to track second by second to what extent students are engaging with ASQ which in turn enables insights into student behaviour dynamics. This setup enables us to conduct ''''in situ'' experiments. Based on the logs collected in a longitudinal study over a ten week period across 14 lectures with more than 300 students, we investigate (i) to what extent ASQ can be reliably employed to assess attention and learning in the classroom, and (ii) whether different in-class question spacing strategies impact student learning and engagement.", "image": "/biblio-covers/ASQ-UMAP2017.png", "date_modified": "2017-06-30T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/2017/ieeesw-ms1", "html_content": "", "url": "../biblio/2017/ieeesw-ms1", "title": "Microservices in Practice (Part 1): Reality Check and Service Design", "image": "/biblio-covers/IEEESW-2017-MS1.png", "date_modified": "2017-01-31T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2017/ieeesw-ms2", "html_content": "", "url": "../biblio/2017/ieeesw-ms2", "title": "Microservices in Practice (Part 2): Service Integration and Sustainability", "image": "/biblio-covers/IEEESW-2017-MS2.png", "date_modified": "2017-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2017/europlop", "html_content": "", "url": "../biblio/2017/europlop", "title": "A Pattern Language for Workflow Engine Conformance and Performance Benchmarking", "summary": "Workflow engines are frequently used in the domains of business process management, service orchestration, and cloud computing, where they serve as middleware platforms for integrated business applications. Engines have a significant impact on the quality of service provided by hosted applications. Therefore, it is desirable to compare them and to select the most appropriate engine for a given task. To enable such a comparison, approaches for benchmarking workflow engines have emerged. Although these approaches deal with different quality attributes, i.e., performance or standard conformance, they face many reoccurring design and implementation problems, which have been solved in similar ways. In this paper, we present a pattern language that captures such common solutions to reoccurring problems (e.g., from test identification, benchmarking procedure validation, automatic engine interaction, and workflow execution observation) in the area of workflow engine conformance and performance benchmarking. Our aim is to help future benchmark authors with the pattern language presented in this paper to benefit from our experience with the design and implementation of workflow engine benchmarks and benchmarking tools", "image": "/biblio-covers/benchflow-EuroPLoP2017.png", "date_modified": "2017-06-30T22:00:00Z", "author": { "name": "Simon Harrer" } }, { "id": "biblio/2017/bpmds", "html_content": "", "url": "../biblio/2017/bpmds", "title": "Performance Comparison Between BPMN 2.0 Workflow Management Systems Versions", "summary": "Software has become a rapidly evolving artifact and Workflow Management Systems (WfMSs) are not an exception. WfMSs' changes may impact key performance indicators or resource consumption levels may change among different versions. Thus, users considering a WfMS upgrade need to evaluate the extent of such changes for frequently issued workload. Deriving such information requires running performance experiments with appropriate workloads. \nIn this paper, we propose a novel method for deriving a structurally representative workload from a given business process collection, which we later use to evaluate the performance and resource consumption over four versions of two open-source WfMSs, for different numbers of simulated users. In our case study scenario the results reveal relevant variations in the WfMSs' performance and resource consumption, indicating a decrease in performance for newer versions.", "image": "/biblio-covers/benchflow-bpmds2017.png", "date_modified": "2017-05-31T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2017/bpm", "html_content": "", "url": "../biblio/2017/bpm", "title": "On the Performance Overhead of BPMN Modeling Practices", "summary": "Business process models can serve different purposes, from discussion and analysis among stakeholders, to simulation and execution. \nWhile work has been done on deriving modeling guidelines to improve understandability, it remains to be determined how different modeling practices impact the execution of the models. \nIn this paper we observe how semantically equivalent, but syntactically different, models behave in order to assess the performance impact of different modeling practices. \nTo do so, we propose a methodology for systematically deriving semantically equivalent models by applying a set of model transformation rules and for precisely measuring their execution performance. \nWe apply the methodology on three scenarios to systematically explore the performance variability of 16 different versions of parallel, exclusive, and inclusive control flows. \nOur experiments with two open-source business process management systems measure the execution duration of each model's instances. \nThe results reveal statistically different execution performance when applying different modeling practices without total ordering of performance ranks.\n", "image": "/biblio-covers/benchflow-bpm2017.png", "date_modified": "2017-08-31T22:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2017/zeus", "html_content": "", "url": "../biblio/2017/zeus", "title": "9th Central European Workshop on Services and their Composition (ZEUS 2017)", "image": "/biblio-covers/zeus2017.png", "date_modified": "2017-01-31T23:00:00Z", "author": { "name": "Oliver Kopp" } }, { "id": "biblio/2017/icsa-blockchain", "html_content": "", "url": "../biblio/2017/icsa-blockchain", "title": "A Taxonomy of Blockchain-based Systems for Architecture Design", "summary": "Blockchain is an emerging technology for decentralised and transactional data sharing across a large network of untrusted participants. It enables new forms of distributed software architectures, where agreement on shared states can be established without trusting a central integration point. A major difficulty for architects designing applications based on blockchain is that the technology has many configurations and variants. Since blockchains are at an early stage, there is little product data or reliable technology evaluation available to compare different blockchains. In this paper, we propose how to classify and compare blockchains and blockchain-based systems to assist with the design and assessment of their impact on software architectures. Our taxonomy captures major architectural characteristics of blockchains and the impact of their principal design decisions. This taxonomy is intended to help with important architectural considerations about the performance and quality attributes of blockchain-based systems.", "image": "/biblio-covers/blockchain-icsa2017.png", "date_modified": "2017-03-31T22:00:00Z", "author": { "name": "Xiwei Xu" } }, { "id": "biblio/2017/bpmforum", "html_content": "", "url": "../biblio/2017/bpmforum", "title": "A Template for Sharing Empirical Business Process Metrics", "summary": "Empirical Research is becoming increasingly important for understanding the practical uses and problems with business processes technology in the field. However, no standardization on how to report observations and findings exists. This sometimes leads to research outcomes which report partial or incomplete data and make published results of replicated studies on different data sets hard to compare. In order to help the research community improve reporting on business process models and collections and their characteristics, this paper defines a modular template with the aim of reports' standardization, which could also facilitate the creation of shared business process repositories to foster further empirical research in the future. The template has been positively evaluated by representatives from both BPM research and industry. The survey feedback has been incorporated in the template. We have applied the template to describe a real-world executable WS-BPEL process collection, measured from a static and dynamic perspective.", "image": "/biblio-covers/bpmforum2017.png", "date_modified": "2017-08-31T22:00:00Z", "author": { "name": "Daniel Lübke" } }, { "id": "biblio/2017/qudos", "html_content": "", "url": "../biblio/2017/qudos", "title": "Towards Holistic Continuous Software Performance Assessment", "summary": "In agile, fast and continuous development lifecycles, software performance analysis is fundamental to confidently release continuously improved software versions. \nResearchers and industry practitioners have identified the importance of integrating performance testing in agile development processes in a timely and efficient way. \nHowever, existing techniques are fragmented and not integrated taking into account the heterogeneous skills of the users developing polyglot distributed software, and their need to automate performance practices as they are integrated in the whole lifecycle without breaking its intrinsic velocity. \nIn this paper we present our vision for holistic continuous software performance assessment, which is being implemented in the BenchFlow tool.\nBenchFlow enables performance testing and analysis practices to be pervasively integrated in continuous development lifecycle activities. \nUsers can specify performance activities (e.g., standard performance tests) by relying on an expressive Domain Specific Language for objective-driven performance analysis. \nCollected performance knowledge can be thus reused to speed up performance activities throughout the entire process.\n", "image": "/biblio-covers/benchflow-qudos2017.png", "date_modified": "2017-03-31T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2017/icse", "html_content": "", "url": "../biblio/2017/icse", "title": "Workflow Management Systems Benchmarking: Unfulfilled Expectations and Lessons Learned", "summary": "Workflow Management Systems (WfMSs) are a type of middleware that enables the execution of automated business processes. Users rely on WfMSs to construct flexible and easily maintainable software systems. Significant effort has been invested into standardising languages for business processes execution, with standards such as the Web Services Business Process Execution Language 2.0 or the Business Process Model and Notation 2.0.\nStandardisation aims at avoiding vendor lock-in and enabling WfMS users to compare different systems. The reality is that, despite standardisation efforts, different independent research initiatives show that objectively comparing WfMSs is still challenging. As a result, WfMS users are likely to discover unfulfilled expectations while evaluating and using these systems. In this work, we discuss the findings of two research initiatives dealing with WfMSs benchmarking, presenting unfulfilled expectations and lessons learned concerning WfMSs' usability, reliability, and portability. Our goal is to provide advice for practitioners implementing or planning to use WfMSs.", "image": "/biblio-covers/benchflow-icse2017-wfms-benchmarking-poster.png", "date_modified": "2017-04-30T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2016/wicsa-liquid", "html_content": "", "url": "../biblio/2016/wicsa-liquid", "title": "On the Architecture of Liquid Software: Technology Alternatives and Design Space", "summary": "The liquid metaphor refers to software that operates seamlessly across multiple devices owned by one or multiple users. Liquid software architectures can dynamically deploy and redeploy stateful software components and transparently adapt them to the capabilities of heterogeneous target devices. The key design goal in liquid software development is to minimize the efforts that are related to multiple device ownership (e.g., installation, synchronization and general maintenance of personal computers, smartphones, tablets, home displays, cars and wearable devices), while keeping the users in full control of their devices, applications and data. In this paper we present a design space for liquid software, categorizing and discussing the most important architectural issues and alternatives. These alternatives represent relevant capabilities offered by emerging technologies and deployment platforms that are then positioned and compared within the design space presented in the paper.", "image": "/biblio-covers/liquidjs-WICSA2016.png", "date_modified": "2016-03-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2016/wicsa-blockchain", "html_content": "", "url": "../biblio/2016/wicsa-blockchain", "title": "The Blockchain as a Software Connector", "summary": "Blockchain is an emerging technology for decentralized and transactional data sharing across a large network of untrusted participants. It enables new forms of distributed software architectures, where components can find agreements on their shared states without trusting a central integration point or any particular participating components. Considering the blockchain as a software connector helps make explicitly important architectural considerations on the resulting performance and quality attributes (for example, security, privacy, scalability and sustainability) of the system. Based on our experience in several projects using blockchain, in this paper we provide rationales to support the architectural decision on whether to employ a decentralized blockchain as opposed to other software solutions, like traditional shared data storage. Additionally, we explore specific implications of using the blockchain as a software connector including design trade-offs regarding quality attributes.", "image": "/biblio-covers/blockchain-wicsa2016.png", "date_modified": "2016-03-31T22:00:00Z", "author": { "name": "Xiwei Xu" } }, { "id": "biblio/2016/closer", "html_content": "", "url": "../biblio/2016/closer", "title": "A Container-centric Methodology for Benchmarking Workflow Management Systems", "summary": "Trusted benchmarks should provide reproducible results obtained following a transparent and well-defined process. In this paper, we show how Containers, originally developed to ease the automated deployment of Cloud application components, can be used in the context of a benchmarking methodology. The proposed methodology focuses on Workflow Management Systems (WfMSs), a critical service orchestration middleware, which can be characterized by its architectural complexity, for which Docker Containers offer a highly suitable approach. The contributions of our work are: 1) a new benchmarking approach taking full advantage of containerization technologies; and 2) the formalization of the interaction process with the WfMS vendors described clearly in a written agreement. Thus, we take advantage of emerging Cloud technologies to address technical challenges, ensuring the performance measurements can be trusted. We also make the benchmarking process transparent, automated, and repeatable so that WfMS vendors can join the benchmarking effort.", "image": "/biblio-covers/benchflow-CLOSER2016.png", "date_modified": "2016-03-31T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2016/ieeesw-eip", "html_content": "", "url": "../biblio/2016/ieeesw-eip", "title": "A Decade of Enterprise Integration Patterns: A Conversation with the Authors", "summary": "Department editors Olaf Zimmerman and Cesare Pautasso interview Gregor Hohpe and Bobby Woolf, authors of Enterprise Integration Patterns. They discuss the book's impact, pattern language design, message-oriented middleware, integration technology's evolution, and the authors' future plans. ", "image": "/biblio-covers/IEEESW-2016-EIP-Insights.png", "date_modified": "2016-01-31T23:00:00Z", "author": { "name": "Olaf Zimmermann" } }, { "id": "biblio/2016/cbse", "html_content": "", "url": "../biblio/2016/cbse", "title": "Deploying Stateful Web Components on Multiple Devices with Liquid.js for Polymer", "summary": "Nowadays, the average users owns two or more Web-enabled devices (smart phones, personal computers and tablets), while more are coming: watches, cars, glasses. While responsive Web applications can adapt to the specific device (e.g., screen size or input method) on which they are deployed, they only provide limited support when one user connects from more than one device at the same time. In this paper we present Liquid.js for Polymer, a framework whose goal is to support developers that need to build liquid Web applications taking full advantage of multiple heterogeneous devices. It extends emerging Web components standards to enable the liquid user experience, whereby any device can be used sequentially or concurrently with applications that can roam from one device to another with no effort required by users controlling them. This way, users do not need to stop and resume their work on their Web application as they switch devices. Developers using Liquid.js do not need to worry about the underlying connectivity, pairing and synchronization issues of their stateful Web components. \n", "image": "/biblio-covers/liquidjs-CBSE2016.png", "date_modified": "2016-03-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2016/bpmforum", "html_content": "", "url": "../biblio/2016/bpmforum", "title": "Estimating the Cost for Executing Business Processes in the Cloud", "summary": "Managing and running business processes in the Cloud changes how Workflow Management Systems (WfMSs) are deployed. Consequently, when designing such WfMSs, there is a need of determining the sweet spot in the performance vs. resource consumption trade-off. While all Cloud providers agree on the pay-as-you-go resource consumption model, every provider uses a different cost model to gain a competitive edge. In this paper, we present a novel method for estimating the infrastructure costs of running business processes in the Cloud. The method is based on the precise measurement of the resources required to run a mix of business process in the Cloud, while accomplishing expected performance requirements. To showcase the method we use the BenchFlow framework to run experiments on a widely used open-source WfMS executing custom workload with a varying number of simulated users. The experiments are necessary to reliably measure WfMS's performance and resource consumption, which is then used to estimate the infrastructure costs of executing such workload on four different Cloud providers.", "image": "/biblio-covers/benchflow-bpmforum2016.png", "date_modified": "2016-08-31T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2016/ectel", "html_content": "", "url": "../biblio/2016/ectel", "title": "Inferring student attention with ASQ", "summary": "ASQ is a Web application for broadcasting and tracking interactive presentations, which can be used to support active learning pedagogies during lectures, labs and exercise sessions. Students connect their smartphones, tablets or laptops to receive the current slide as it is being explained by the teacher. Slides can include interactive teaching elements (usually questions of different forms). In contrast to other existing platforms, ASQ does not only collect, aggregate and visualize the answers in real-time, it also supports the data analytics in the classroom paradigm by providing the teacher with a real-time analysis of student behaviour during the entire session. One vital aspect of student behaviour is (in)attention and in this paper we discuss how we infer - in real-time - student attention based on log traces ASQ collects.", "image": "/biblio-covers/ASQ-ECTEL2016.png", "date_modified": "2016-08-31T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/2016/icpe", "html_content": "", "url": "../biblio/2016/icpe", "title": "Integrating Faban with Docker for Performance Benchmarking", "summary": "Reliability and repeatability are key requirements in performance benchmarking ensuring the trustworthiness of the obtained performance results. To apply a benchmark to multiple systems, the reusability of the load driver is essential. While Faban has been designed to ensure the reliability of the performance data obtained from a benchmark experiment, it lacks support for ensuring that the system under test is deployed in a known configuration. This is what Docker, a recently emerging containerization technology, excels at. In this demo paper we present how we integrated Faban with Docker as part of the BenchFlow framework to offer a complete and automated performance benchmarking framework that provides a reliable and reusable environment, ensuring the repeatability of the experiments. ", "image": "/biblio-covers/benchflow-icpe2016demo.png", "date_modified": "2016-02-29T23:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2016/www", "html_content": "", "url": "../biblio/2016/www", "title": "The Liquid.js Framework for Migrating and Cloning Stateful Web Components across Multiple Devices", "summary": "We are heading toward an era in which users own more than one single Web-enabled device. These devices range from smart phones, tablets and personal computers to smart Web-enabled devices found in houses and cars. The access mechanisms and usage patterns of Web applications are changing accordingly, as users interact more and more with Web applications through all their devices, even if the majority of Web applications are not ready to offer a good user experience taking full advantage of multiple devices. In this demonstration we introduce Liquid.js, a framework whose goal is to enable Web developers to take advantage of multiple heterogeneous devices and offer to their users a liquid user experience, whereby any device can be used sequentially or concurrently with Web applications that can effortlessly roam from one device to another. This way, as highlighted in the demonstration users do not need to stop and resume their work on their Web application as they migrate and clone them across different devices. The demo will also show how developers can easily add such liquid behavior to any Polymer Web component.", "image": "/biblio-covers/liquid-www2016demo.png", "date_modified": "2016-03-31T22:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/book/email-anti-patterns", "html_content": "", "url": "../biblio/book/email-anti-patterns", "title": "Just send an email: Anti-patterns for email-centric organizations", "summary": "Anti-patterns are practices that despite their negative consequences continue to be applied due to their low cost, ease of use and apparent good fit to solve pressing problems. It is possible to outgrow them by learning that a better way exists. While many organizations already learned how to take full advantage of business process management methods and tools, many still live in a world where email is the main (sometimes the only) tool used for internal and external communication, coordination and collaboration. Emails continue to provide a very fast and flexible asynchronous communication medium between two or more people, which however comes with many pitfalls. In this book published on LeanPub we present our ongoing work towards uncovering email anti-patterns which we have actually observed in the field. Some examples of anti-patterns we have uncovered so far are: Unsecured Sensitive Mail, Monday Morning Mail, 5pm Reply, Redirect, Re:gret, Ticketless Support, On Behalf, Fuzzy Link, Attached Body, Collaborative Edit, Datamail, Unintended Reply-To-All, Total Recall, Lightning Reply, Untimely Reminder, Mail from the Grave, Mail-Call-Meet and META SPAM.\n", "image": "/biblio-covers/just-send-an-email.png", "date_modified": "2015-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2015/wls", "html_content": "", "url": "../biblio/2015/wls", "title": "Mashup Development with Web Liquid Streams", "summary": "Web services such as Twitter and Facebook provide direct access to their streaming APIs. The data generated by all of their users is forwarded in quasi-real-time to any external client requesting it: this continuous feed opens up new ways to create mashups that differ from existing data aggregation approaches, which focus on presenting with multiple widgets an integrated view of the data that is pulled from multiple sources.\nStreaming data flows directly into the mashup without the need to fetch it in advance, making it possible to exchange data between mashup components through streaming channels. In this challenge submission we show how streaming APIs can be integrated using a stream processing framework. Mashup components can be seen as stream operators, while the mashup can be defined by building a streaming topology. The mashup is built with Web Liquid Streams, a dynamic streaming framework that takes advantage of standard Web protocols to deploy stream topologies both on Web servers and Web browsers.", "image": "/biblio-covers/wls-icwe-rmc2015-mashup_challenge_web_liquid_streams.png", "date_modified": "2016-01-01T00:00:00Z", "author": { "name": "Andrea Gallidabino" } }, { "id": "biblio/2016/caise", "html_content": "", "url": "../biblio/2016/caise", "title": "Micro-Benchmarking BPMN 2.0 Workflow Management Systems with Workflow Patterns", "summary": "Although Workflow Management Systems (WfMSs) are a key component in workflow technology, research work for assessing and comparing their performance is limited. This work proposes the first micro- benchmark for WfMSs that can execute BPMN 2.0 workflows. To this end, we focus on studying the performance impact of well-known workflow patterns expressed in BPMN 2.0 with respect to three open source WfMSs (i.e., Activiti, jBPM and Camunda). We executed all the experiments under a reliable environment and produced a set of meaningful metrics. This paper contributes to the area of workflow technology by defining building blocks for more complex BPMN 2.0 WfMS benchmarks. The results have shown bottlenecks on architectural design decisions, resource utilization, and limits on the load a WfMS can sustain, especially for the cases of complex and parallel structures. Experiments on a mix of workflow patterns indicated that there are no unexpected performance side effects when executing different workflow patterns concurrently, although the duration of the individual workflows that comprised the mix was increased.", "image": "/biblio-covers/benchflow-caise2016.png", "date_modified": "2016-05-31T22:00:00Z", "author": { "name": "Marigianna Skouradaki" } }, { "id": "biblio/2016/europlop", "html_content": "", "url": "../biblio/2016/europlop", "title": "A Pattern Language for RESTful Conversations", "summary": "As a good user interface design is important for the success of an app, so is a good API for the success of a Web service. Within the RESTful Web services community there is a need for a systematic approach in knowledge sharing, for which patterns are particularly suitable. Using a RESTful service to achieve a certain goal often requires multiple client-server interactions, i.e., to have a conversation. While patterns of such RESTful conversations can be uncovered from existing APIs' usage scenarios, or the service engineering literature, they have never been gathered in a pattern language, nor properly visualized with a Domain Specific Modeling Language (DSML). These patterns provide valuable input for API designers, as well as API consumers, by establishing a common vocabulary to describe recurring conversations. To do so, this paper uses RESTalk, a DSML, to model the basic RESTful conversation patterns structured around the life cycle of a resource (create, discover, read, edit, delete, protect) by showing the corresponding sequences of HTTP request-response interactions. We show how the resulting pattern language can be applied to individual resources, or also collections of resources.", "image": "/biblio-covers/resttalk-EuroPLoP2016-RESTfulConversationPatterns.png", "date_modified": "2016-06-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2015/rmc", "html_content": "", "url": "../biblio/2015/rmc", "title": "1st International Rapid Mashup Challenge (RMC 2015)", "image": "/biblio-covers/icwe-rmc2015.png", "date_modified": "2016-01-01T00:00:00Z", "author": { "name": "Florian Daniel" } }, { "id": "biblio/2016/icwe", "html_content": "", "url": "../biblio/2016/icwe", "title": "Proc. of the 16th International Conference on Web Engineering (ICWE 2016)", "image": "/biblio-covers/icwe2016.png", "date_modified": "2016-05-31T22:00:00Z", "author": { "name": "Alessandro Bozzon" } }, { "id": "biblio/2016/icwe-workshops", "html_content": "", "url": "../biblio/2016/icwe-workshops", "title": "Proc. of the Workshops held at the 16th International Conference on Web Engineering (ICWE 2016)", "image": "/biblio-covers/icwe2016w.png", "date_modified": "2016-05-31T22:00:00Z", "author": { "name": "Sven Casteleyn" } }, { "id": "biblio/2015/icwe-asqium", "html_content": "", "url": "../biblio/2015/icwe-asqium", "title": "asqium: A JavaScript Plugin Framework for Extensible Client and Server-side Components", "summary": "JavaScript has been growing from a language for embedding simple scripts into Web pages to a language for programming complex Web applications, whose logic is deployed across both Web browsers and Web servers. Current software packaging mechanisms for JavaScript enable a basic level of modularity and reuse. However, they have not yet reached full maturity in terms of enabling to extend a system with features contributed as third-party plugins, while encapsulating them adequately.\nIn this paper we present a novel plugin system for JavaScript applications, which integrate Node.js modules with HTML5 Web Components. It provides abstractions for: real time and loosely coupled communication between front-end and back-end components, persistent state storage, and isomorphic usage of JavaScript. Plugins can use hooks and events to contribute functionality and embed it into the main application flow, while respecting the common asynchronous non-blocking programming paradigm of JavaScript. We demonstrate the expressiveness of the framework as it is used to build ASQ: an open and extensible educational Web platform.\n", "image": "/biblio-covers/ASQ-icwe2015-asqium.png", "date_modified": "2015-05-31T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/2015/closer", "html_content": "", "url": "../biblio/2015/closer", "title": "\"BPELanon\": Protect Business Processes on the Cloud", "summary": "The advent of Cloud computing supports the offering of many Business Process Management applications on a\ndistributed, per-use basis environment through its infrastructure. Due to the fact that privacy is still an open\nissue in the Cloud, many companies are reluctant to move their Business Processes on a public Cloud. Since the\nCloud environment can be beneficiary for the Business Processes, the investigation of privacy issues needs to\nbe further examined. In order to enforce the Business Process sharing on the Cloud we propose a methodology\n(\"BPELanon\") for the anonymization of Business Processes expressed in the Web Service Business Process\nExecution Language (BPEL). The method transforms a process to preserve its original structure and run-time\nbehavior, while completely anonymizing its business semantics. In this work we set the theoretical framework\nof the method and define a five management layers architecture to support its realization. We developed a tool\nthat implements the \"BPELanon\" method, validate its functionality and evaluate its performance against a\ncollection of real-world process models that were conducted in the scope of research projects.", "image": "/biblio-covers/benchflow-CLOSER2015.png", "date_modified": "2015-04-30T22:00:00Z", "author": { "name": "Marigianna Skouradaki" } }, { "id": "biblio/2015/bpm", "html_content": "", "url": "../biblio/2015/bpm", "title": "BPMeter: Web Service and Application for Static Analysis of BPMN 2.0 Collections", "summary": "The number of business process models is constantly increasing as companies realize the competitive advantage of managing their processes. Measuring their size and structural properties can give useful insights. With the BPMeter tool, process owners can quickly compare their process with company's process portfolio, researchers can statically analyze a process to see which modeling language features have been used in practice, while modelers can obtain an aggregated view over their processes. In this demonstration we show how to use BPMeter, which provides a simple Web application to visualize the results of applying over 100 different size and structure metrics to BPMN 2.0 process models. The visualization features measurements, statistics and the possibility to compare the measurements with the ones obtained from the entire portfolio. Moreover we show how to invoke its RESTful Web API so that the BPMeter analyzer can be easily integrated with existing process management tools.", "image": "/biblio-covers/benchflow-bpm2015-demo.png", "date_modified": "2015-07-31T22:00:00Z", "author": { "name": "Ana Ivanchikj" } }, { "id": "biblio/2015/wicsa", "html_content": "", "url": "../biblio/2015/wicsa", "title": "A conversation based approach for modeling REST APIs", "summary": "Conversations are a well-known concept in service design to describe complex interactions between a client and one or multiple services. The REST architectural style constrains the characteristics of clients, servers and their interactions in REST architectures which consequently has an impact on conversations in such systems. The relation between conversations and REST architectures and how such RESTful conversations can be characterized has not been studied in detail yet. In this paper we discuss the characteristics of conversations in REST architectures and introduce an initial set of commonly used conversation types. Based on this, we propose to use conversations as a modeling tool for the design of REST APIs at a higher level of abstraction. We also introduce a corresponding interaction centric metamodel for REST APIs. The characterization of RESTful conversations enables a new interaction centric viewpoint on REST architectures which can be also applied for modeling REST APIs on an abstraction level that enables users to focus on the essential functionality of their REST API.", "image": "/biblio-covers/resttalk-wicsa2015.png", "date_modified": "2015-04-30T22:00:00Z", "author": { "name": "Florian Haupt" } }, { "id": "biblio/2015/esocc", "html_content": "", "url": "../biblio/2015/esocc", "title": "Decentralized Stream Processing over Web-enabled devices", "image": "/biblio-covers/wls-esocc2015.png", "date_modified": "2015-08-31T22:00:00Z", "author": { "name": "Masiar Babazadeh" } }, { "id": "biblio/2015/bpm", "html_content": "", "url": "../biblio/2015/bpm", "title": "A Framework for Benchmarking BPMN 2.0 Workflow Management Systems", "image": "/biblio-covers/benchflow-bpm2015.png", "date_modified": "2015-07-31T22:00:00Z", "author": { "name": "Vincenzo Ferme" } }, { "id": "biblio/2015/wesoa", "html_content": "", "url": "../biblio/2015/wesoa", "title": "From Choreography Diagrams to RESTful Interactions", "summary": "Today, business process management is a key approach to organize work, and many companies represent their operations in business process models. Recently, choreography diagrams have been introduced to represent interactions between business processes, run by different partners. While there is considerable work on using process models during process implementation, there is little work on using choreography models to implement interactions between business processes. In this paper, a novel approach to enhance choreography diagrams by execution information is introduced. The approach is based on the REST architecture style, which is the primary way for interacting systems. Using enhanced choreography diagrams allows us to develop REST-based interactions among business partners in an efficient manner. The approach is illustrated by an example of an accommodation reservation service.", "image": "/biblio-covers/resttalk-wesoa2015.png", "date_modified": "2015-10-31T23:00:00Z", "author": { "name": "Adriatik Nikaj" } }, { "id": "biblio/2015/icwe-lws", "html_content": "", "url": "../biblio/2015/icwe-lws", "title": "Liquid Stream Processing across Web browsers and Web servers", "summary": "The recently proposed API definition WebRTC introduced peer-to-peer real time communication between Web browsers, allowing streaming systems to be deployed on browsers in addition to traditional server-side execution environments. While streaming applications can be adapted to run on Web browsers, it remains difficult to deal with temporary disconnections, energy consumption on mobile devices and a potentially very large number of heterogeneous peers that join and leave the execution environment affecting the quality of the stream. In this paper we present the decentralized control approach followed by the Web Liquid Streams (WLS) framework, a novel framework for streaming applications running on Web browsers, Web servers and smart devices. Given the heterogeneity of the deployment environment and the volatility of Web browsers, we implemented a control infrastructure which is able to take operator migration decisions keeping into account the deployment constraints and the unpredictable workload.", "image": "/biblio-covers/lws-icwe2015.png", "date_modified": "2015-05-31T22:00:00Z", "author": { "name": "Masiar Babazadeh" } }, { "id": "biblio/2015/ecsa", "html_content": "", "url": "../biblio/2015/ecsa", "title": "Modeling RESTful Conversations with extended BPMN Choreography diagrams", "summary": "RESTful Web APIs often make use of multiple basic HTTP interactions to guide clients towards their goal. For example, clients may get redirected towards related resources by means of hypermedia controls such as links. Existing modeling approaches for describing RESTful APIs expose low-level HTTP details that help developers construct individual requests and parse the corresponding responses. However, very little attention has been given to high-level modeling of RESTful conversations, which abstracts the structure of multiple HTTP interactions. To address such issue in this paper we introduce an extension of the notation used in BPMN choreography diagrams. Its purpose is to represent concisely all possible interaction sequences in a given RESTful conversation.", "image": "/biblio-covers/resttalk-ecsa2015.png", "date_modified": "2015-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2015/icpe", "html_content": "", "url": "../biblio/2015/icpe", "title": "On the Road to Benchmarking BPMN 2.0 Workflow Engines", "summary": "Workflow Management Systems (WfMSs) provide platforms for delivering complex service-oriented applications that need to satisfy enterprise-grade quality of service requirements such as dependability and scalability. \nIn this paper we focus on the case of benchmarking the performance of the core of WfMSs, Workflow Engines, that are compliant with the Business Process Model and Notation 2.0 (BPMN 2.0) standard.\nWe first explore the main challenges that need to be met when designing such a benchmark and describe the approaches we designed for tackling them in the BenchFlow project.\nWe discuss our approach to distill the essence of real-world processes to create from it processes for the benchmark, and to ensure that the benchmark finds wide applicability.", "image": "/biblio-covers/benchflow-icpe2015.png", "date_modified": "2014-12-31T23:00:00Z", "author": { "name": "Marigianna Skouradaki" } }, { "id": "biblio/2015/ieeesw-insights", "html_content": "", "url": "../biblio/2015/ieeesw-insights", "title": "Seeking Your Insights", "image": "/biblio-covers/IEEESW-2015-Insights.png", "date_modified": "2015-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2015/icwe-liquidweb", "html_content": "", "url": "../biblio/2015/icwe-liquidweb", "title": "Towards Liquid Web Applications", "summary": "As the complexity of rich Web applications grows together with the power and number of Web browsers, the next Web engineering challenge to be addressed is to design and deploy Web applications to make coherent use of all devices. As users nowadays operate multiple personal computers, smart phones, tablets, and computing devices embedded into home appliances or cars, the architecture of current Web applications needs to be redesigned to enable what we call Liquid Software. Liquid Web applications not only can take full advantage of the computing, storage and communication resources available on all devices owned by the end user, but also can seamlessly and dynamically migrate from one device to another continuously following the user attention and usage context. In this paper we address the Liquid Software concept in the context of Web applications and survey to which extent and how current Web technologies can support its novel requirements.", "image": "/biblio-covers/liquidjs-icwe2015.png", "date_modified": "2015-05-31T22:00:00Z", "author": { "name": "Tommi Mikkonen" } }, { "id": "biblio/2015/btw", "html_content": "", "url": "../biblio/2015/btw", "title": "Towards Workflow Benchmarking: Open Research Challenges", "image": "/biblio-covers/benchflow-btw2015.png", "date_modified": "2015-02-28T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2014/wsrest", "html_content": "", "url": "../biblio/2014/wsrest", "title": "Atomic Distributed Transactions: a RESTful Design", "summary": "The REST architectural style supports the reliable interaction of clients with a single server. However, no guarantees can be made for more complex interactions which require to atomically transfer state among resources distributed across multiple servers. In this paper we describe a lightweight design for transactional composition of RESTful services. The approach -- based on the Try-Cancel/Confirm (TCC) pattern -- does not require any extension to the HTTP protocol. The design assumes that resources are designed to comply with the TCC pattern and ensures that the resources involved in the transaction are not aware of it. It delegates the responsability of achieving the atomicity of the transaction to a coordinator which exposes a RESTful API.", "image": "/biblio-covers/tcc-wsrest2014.png", "date_modified": "2014-03-31T22:00:00Z", "author": { "name": "Guy Pardon" } }, { "id": "biblio/2014/zeus", "html_content": "", "url": "../biblio/2014/zeus", "title": "\"BPELanon\": Anonymizing BPEL Processes", "summary": "We are currently developing a performance benchmark for Workflow Management System. As a first activity we are collecting real-world processes. However, to protect their competitive advantage, some companies are not willing to share their corporate assets. This work's objective is to propose a method (\"BPELanon\") for BPEL process anonymization in order to deal with the problem. The method transforms a process to preserve its original structure and runtime behaviour, while completely anonymizing its business semantics. Anonymization is a complicated task that must meet the requirements we outline in this paper. Namely, we need to preserve the structural and executional information while anonymizing information such as namespaces, names (activity names, variable names, partner link names etc.), and XPATH expressions that may reveal proprietary information. Furthermore, the names contained in the anonymized process should be chosen carefully in order to avoid conflicts, preserve privacy, and file-readability. Multiple dependency relations among process artifacts raise the challenge of fulfilling the aforementioned requirements, as a unique change in a file potentially leads to a flow of changes to other related process artifacts. ", "image": "/biblio-covers/benchflow-zeus2014.png", "date_modified": "2014-01-31T23:00:00Z", "author": { "name": "Marigianna Skouradaki" } }, { "id": "biblio/2013/jvlc", "html_content": "", "url": "../biblio/2013/jvlc", "title": "End-User Development of Mashups with NaturalMash", "summary": "Context: The emergence of the long-tail in the market of software applications is shifting the role of end-users from mere consumers to becoming developers of applications addressing their unique, personal, and transient needs. On the Web, a popular form of such applications is called mashup, built out of the lightweight composition of Web APIs (reusable software components delivered as a service through the Web). To enable end-users to build mashups, there is a key problem that must be overcome: End-users lack programming knowledge as well as the interest to learn how to master the complex set of Web technologies required to develop mashups. End-User Development (EUD) is an emerging research field dealing with this type of problems. Its main goal is to design tools and techniques facilitating the development of software applications by non-programmers.\n\nObjective: The paper describes the design and evaluation of NaturalMash, an innovative EUD tool for mashups (a mashup tool). NaturalMash aims at enabling non-professional users without any knowledge of programming languages and skills to create feature-rich, interactive, and useful mashups.\n\nMethods: The design of NaturalMash adopts a formative evaluation approach, and has completed three design and evaluation iterations. The formative evaluations utilize usability testing, think aloud protocol, questionnaires, observation, and unstructured interviews. Additionally, we compare the expressive power of naturalmash with the state-of-the-art mashup tools.\n\nResults: The results from the formative evaluations helped us identify important usability problems. From an assessment point of view, the results were promising and sggested that the proposed tool has a short and gentle learning curve in a way that even non-programmers are able to rapidly build useful mashups. Also, the comparative evaluation results showed that NaturalMash offers a competitive level of expressive power compared with existing mashup tools targeting non-programmers.\n\nConclusion: As the evaluation results indicate, NaturalMash provides a high level of expressive power while it is still highly usable by non-programmers. These suggest that we have successfully achieved the objective of the proposed tool, distinguishing it from existing mashup tools that are either too limited or highly specialized for non-professional users.", "image": "/biblio-covers/naturalmash-jvlc2013.png", "date_modified": "2014-07-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2014/cpe", "html_content": "", "url": "../biblio/2014/cpe", "title": "High Performance Execution of Service Compositions: a Multicore-aware Engine Design", "summary": "Although modern computer hardware offers an increasing number of processing elements organized in nonuniform memory access (NUMA) architectures, prevailing middleware engines for executing business processes, workflows, and Web service compositions have not been optimized for properly exploiting the abundant processing resources of such machines. Amongst others, factors limiting performance are inefficient thread scheduling by the operating system, which can result in suboptimal use of system memory and CPU caches, and sequential code sections that cannot take advantage of multiple available cores.\nIn this article, we study the performance of the JOpera process execution engine on recent multicore machines. We first evaluate its performance without any dedicated optimization for multicore hardware, showing that additional cores do not significantly improve performance, although the engine has a multithreaded design. Therefore, we apply optimizations on the basis of replication together with an improved, hardware-aware usage of the underlying resources such as NUMA nodes and CPU caches. Thanks to our optimizations, we achieve speedups from a factor of 2 up to a factor of 20 (depending on the target machine) when compared with a baseline execution 'as is'. ", "image": "/biblio-covers/jopera-cpe2012.png", "date_modified": "2013-12-31T23:00:00Z", "author": { "name": "Achille Peternier" } }, { "id": "biblio/2013/fgcs", "html_content": "", "url": "../biblio/2013/fgcs", "title": "Improving execution unit occupancy on SMT-based processors through hardware-aware thread scheduling", "summary": "Modern processor architectures are increasingly complex and heterogeneous, often requiring software solutions tailored to the specific hardware characteristics of each processor model. In this article, we address this problem by targeting two processors featuring Simultaneous MultiThreading (SMT) to improve the occupancy of their internal execution units through a sustained stream of instructions coming from more than one thread. We target the AMD Bulldozer and IBM POWER7 processors as case studies for specific hardware-oriented performance optimizations that increase the variety of instructions sent to each core to maximize the occupancy of all its execution units. WorkOver, presented in this article, improves thread scheduling by increasing the performance of floating point-intensive workloads on Linux-based operating systems. WorkOver is a user-space monitoring tool that automatically identifies FPU-intensive threads and schedules them in a more efficient way without requiring any patches or modifications at the kernel level. Our measurements using standard benchmark suites show that speedups of up to 20 can be achieved by simply allowing WorkOver to monitor applications and schedule their threads, without any modification of the workload.", "image": "/biblio-covers/overseer-fgcs2013.png", "date_modified": "2013-12-31T23:00:00Z", "author": { "name": "Achille Peternier" } }, { "id": "biblio/2014/icwe", "html_content": "", "url": "../biblio/2014/icwe", "title": "Interactive Scalable Lectures with ASQ", "summary": "Taking full advantage of the Web technology platform dur- ing in-class lectures requires a shift from the established scheme of online education delivery that utilizes the video channel to embed all types of content and gathers student feedback via multiple choice questions or textual answers. In this paper we present the design of ASQ to deliver interactive content for use in heterogeneous educational settings with a large number of students, taking advantage of the co-location of students and instructors and building upon the latest capabilities of the Web platform. ASQ is centered around interactive HTML5 presentations coupled with a versatile microformat to create and deliver various types quizzes and scalable, synchronous/asynchronous feedback mechanisms.", "image": "/biblio-covers/ASQ-icwe-demo-2014.png", "date_modified": "2014-06-30T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/book/rest2", "html_content": "", "url": "../biblio/book/rest2", "title": "REST: Advanced Research Topics and Practical Applications", "image": "/biblio-covers/rest2014.png", "date_modified": "2014-11-30T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2014/wsrest-lws", "html_content": "", "url": "../biblio/2014/wsrest-lws", "title": "A RESTful API for Controlling Dynamic Streaming Topologies", "summary": "Streaming applications have become more and more dynamic and heterogeneous thanks to new technologies which enable platforms like microcontrollers and Web browsers to be able to host part of a streaming topology. \nA dynamic heterogeneous streaming application should support load balancing and fault tolerance while being capable of adapting and rearranging topologies to user needs at runtime. \nIn this paper we present a REST API to control dynamic heterogeneous streaming applications. By means of resources, their uniform interface and hypermedia we show how it is possible to monitor, change and adapt the deployment configuration of a streaming topology at runtime.", "image": "/biblio-covers/lws-wsrest2014.png", "date_modified": "2014-03-31T22:00:00Z", "author": { "name": "Masiar Babazadeh" } }, { "id": "biblio/2014/wicsa", "html_content": "", "url": "../biblio/2014/wicsa", "title": "The Stream Software Connector Design Space: Frameworks and Languages for Distributed Stream Processing", "summary": "In recent years we witnessed the rise of applications in which data is continuously generated and pushed towards consumers in real time through complex processing pipelines. Software connectors like remote procedure call (RPC) do not fit with the needs of such applications, for which the publish/subscribe and the stream connectors are more suitable. \nThis paper introduces the design space of the stream software connector by analyzing recent stream processing engine frameworks and domain specific languages featuring native streaming support. On the one side, we want to classify and compare streaming systems based on a taxonomy derived from the wide range of features they offer (i.e., pipeline dynamicity and representation, load balancing and deployment flexibility).\nOn the other side, the gaps in the design space we identify point at future research directions in the area of distributed stream processing. \nTo do so, we gather valuable architectural knowledge in terms of architectural issues and alternatives, elicited by surveying the most important architectural decisions made by the designers of several representative streaming framework architectures.", "image": "/biblio-covers/lws-wicsa2014.png", "date_modified": "2014-03-31T22:00:00Z", "author": { "name": "Masiar Babazadeh" } }, { "id": "biblio/2014/sosp", "html_content": "", "url": "../biblio/2014/sosp", "title": "Technical Open Challenges on Benchmarking Workflow Management Systems", "summary": "The goal of the BenchFlow project is to design the first benchmark for assessing and comparing the performance of BPMN 2.0 Workflow Management Systems (WfMSs). WfMSs have become the platform to build composite service-oriented applications, whose performance depends on two factors: the performance of the workflow system itself and the performance of the composed services (which could lie outside of the control of the workflow). Our main goal is to present to the community the state of our work, and the open challenges of a complex industry-relevant benchmark", "image": "/biblio-covers/benchflow-sosp2014.png", "date_modified": "2014-10-31T23:00:00Z", "author": { "name": "Marigianna Skouradaki" } }, { "id": "biblio/2013/www-asq", "html_content": "", "url": "../biblio/2013/www-asq", "title": "ASQ: Interactive Web Presentations for Hybrid MOOCs", "summary": "ASQ is a Web application for creating and delivering interactive HTML5 presentations. It is designed to support teachers that need to gather real-time feedback from the students while delivering their lectures. Presentation slides are delivered to viewers that can answer the questions embedded in the slides. The objective is to maximize the efficiency of bi-directional communication between the lecturer and a large audience. More specifically, in the context of a hybrid MOOC classroom, a teacher can use ASQ to get feedback in real time about the level of comprehension of the presented material while reducing the time for gathering survey data, monitoring attendance and assessing solutions.", "image": "/biblio-covers/ASQ-www2013.png", "date_modified": "2013-04-30T22:00:00Z", "author": { "name": "Vasileios Triglianos" } }, { "id": "biblio/2013/www-tcc", "html_content": "", "url": "../biblio/2013/www-tcc", "title": "The Atomic Web Browser", "summary": "The Atomic Web Browser achieves atomicity for distributed transactions across multiple RESTful APIs. Assuming that the participant APIs feature support for the Try-Confirm/Cancel pattern, the user may navigate with the Atomic Web Browser among multiple Web sites to perform local resource state transitions (e.g., reservations or bookings). Once the user indicates that the navigation has successfully completed, the Atomic Web browser takes care of confirming the local transitions to achieve the atomicity of the global transaction.", "image": "/biblio-covers/resttcc-www2013.png", "date_modified": "2013-04-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2013/tweb", "html_content": "", "url": "../biblio/2013/tweb", "title": "Control-Flow Patterns for Decentralized RESTful Service Composition", "summary": "The REST architectural style has attracted a lot of interest from industry due to the nonfunctional properties it contributes to Web-based solutions. SOAP/WSDL-based services, on the other hand, provide tools and methodologies that allow the design and development of software supporting complex service arrangements, enabling complex business processes which make use of well-known control-flow patterns. It is not clear if and how such patterns should be modeled, considering RESTful Web services that comply with the statelessness, uniform interface and hypermedia constraints. In this article, we analyze a set of fundamental control-flow patterns in the context of stateless compositions of RESTful services. We propose a means of enabling their implementation using the HTTP protocol and discuss the impact of our design choices according to key REST architectural principles. We hope to shed new light on the design of basic building blocks for RESTful business processes.", "image": "/biblio-covers/rest-tweb-dcfw.png", "date_modified": "2013-11-30T23:00:00Z", "author": { "name": "Jesus Bellido" } }, { "id": "biblio/2013/iseud", "html_content": "", "url": "../biblio/2013/iseud", "title": "Guidelines for Efficient and Effective End-User Development of Mashups", "summary": "End-User Development (EUD) is an emerging research area aiming at empowering non-technical users to somehow create or design software artifacts. Mashups provide a high potential for EUD activities on the Web. Users on the Web can tap into a vast resource of off-the-shelf components in order to rapidly compose new lightweight software applications called mashups. In this paper, we provide a set of guidelines to design EUD systems for mashups that are widely referred to as mashup tools. The guidelines are derived from our experience with the (ongoing) design and evaluation of NaturalMash, a novel mashup tool targeted for a wide range of users to create feature-rich mashups.", "image": "/biblio-covers/naturalmash-iseud2013.png", "date_modified": "2013-05-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2013/ic", "html_content": "", "url": "../biblio/2013/ic", "title": "Kriging Controllers for Cloud Applications", "summary": "Infrastructure as a Service is a Cloud computing paradigm that enables service providers to execute applications on third-party infrastructures with the pay-as-you-go billing model. Service providers can balance operational costs and quality of service by monitoring the application behavior and changing the deployed configuration at runtime as operating conditions change. Current approaches for automatically scaling cloud applications exploit user defined rules that respond well to events that can be predicted at design time, but have no provision for learning, hence do not react adequately to unexpected execution conditions. In this article we present a new approach for designing autonomic controllers that automatically adapt to unpredicted conditions by dynamically updating a model of the system behavior. The approach demonstrates Kriging models as a suitable means to design efficient autonomic controllers.", "image": "/biblio-covers/kriging-ic2013.png", "date_modified": "NaN-NaN-NaNTNaN:NaN:NaNZ", "author": { "name": "Giovanni Toffetti-Carughi" } }, { "id": "biblio/2013/live", "html_content": "", "url": "../biblio/2013/live", "title": "Live Mashup Tools: Challenges and Opportunities", "summary": "Live programming is a programming style in which the repetitive task of compiling and running the software being programmed is managed automatically. This style can be a helpful practice in End-User Development (EUD) where the non-professional end-users are to be supported through techniques and tools that empower them to create or modify software artifacts. Mashups — a form of lightweight Web applications composing reusable content and functionalities available on the Web — are a popular target for EUD activities on the Web. EUD for mashups is enabled by intuitive composition environments, called mashup tools. In this paper, we introduce live mashup tools, a new class of mashup tools based on the live programming style. We give a comprehensive definition and classification of live mashup tools, giving examples of how well existing tools fit in this category and discuss open research challenges and opportunities.", "image": "/biblio-covers/naturalmash-icselive2013.png", "date_modified": "2013-04-30T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2013/vlhcc", "html_content": "", "url": "../biblio/2013/vlhcc", "title": "Natural End-User Development of Web Mashups", "summary": "End-User Development (EUD) can be exploited on the Web, where users have the opportunity to create niche \"Web Mashup\" applications as a means to address their long tail of situational needs in different domains of application. In this paper, we describe the design and evaluation of NaturalMash, an innovative EUD system for mashups. NaturalMash provides a high level of expressive power while it is still usable by non-professional users. This clearly distinguishes NaturalMash from existing mashup EUD tools that are either too limited or highly specialized for inexperienced users. The NaturalMash user interface efficiently combines different techniques such as live programming, natural language programming, What You See Is What You Get (WYSIWYG), and Programming by Demonstration (PbD). The design of NaturalMash adopts a formative evaluation approach, and has completed two design and evaluation iterations. The paper reports the results of the last formative evaluation and discusses the implications of the findings. The results are promising and suggest that the proposed system has a short and gentle learning curve and enables even non-professional users to rapidly build useful mashups.", "image": "/biblio-covers/naturalmash-vlhcc2013.png", "date_modified": "2013-08-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2013/icsoc", "html_content": "", "url": "../biblio/2013/icsoc", "title": "Proceedings of the 11th International Conference on Service-Oriented Computing (ICSOC 2013)", "image": "/biblio-covers/icsoc2013.png", "date_modified": "2013-11-30T23:00:00Z", "author": { "name": "Samik Basu" } }, { "id": "biblio/2013/pesos", "html_content": "", "url": "../biblio/2013/pesos", "title": "RESTful Business Process Management in the Cloud", "summary": "As more and more business processes are migrated into cloud-based runtimes, there is a need to manage their state to provide support for quality attributes such as elasticity, scalability and dependability. In this paper we discuss how the REST architectural style provides a sensible choice to manage and publish service compositions under the Platform as a Service paradigm. We define the design principles of RESTful business process management in the cloud and compare several architectural alternatives to support elastic processes which can be monitored and dynamically adapted to workload changes.", "image": "/biblio-covers/restbpm-pesos2013.png", "date_modified": "2013-04-30T22:00:00Z", "author": { "name": "Alessio Gambi" } }, { "id": "biblio/2013/rest", "html_content": "", "url": "../biblio/2013/rest", "title": "RESTful Web Services: Principles, Patterns and Emerging Technologies", "summary": "RESTful Web services are software services which are published on the Web, taking full advantage and making correct use of the HTTP protocol. This chapter gives an introduction to the REST architectural style and how it can be used to design Web service APIs. We summarize the main design constraints of the REST architectural style and discuss how they impact the design of so-called RESTful Web service APIs. We give examples on how the Web can be seen as a novel kind of software connector, which enables the coordination of distributed, stateful and autonomous software services. We conclude the chapter with a critical overview of a set of emerging technologies which can be used to support the development and operation of RESTful Web services. ", "image": "/biblio-covers/restws2013.png", "date_modified": "2013-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/book/soa-with-rest", "html_content": "", "url": "../biblio/book/soa-with-rest", "title": "SOA with REST - Principles, Patterns and Constraints for Building Enterprise Solutions with REST", "image": "/biblio-covers/soawithrest.jpeg", "date_modified": "2013-01-01T00:00:00Z", "author": { "name": "Thomas Erl" } }, { "id": "biblio/2013/ecsa", "html_content": "", "url": "../biblio/2013/ecsa", "title": "Team Situational Awareness and Architectural Decision Making with the Software Architecture Warehouse", "summary": "The core of the design of software architecture is all about architectural decision making. A high-quality design outcome sets high requirements, not only on the skills and knowledge of the design team members, but also on the management of the decision making process. We claim that in order to deliver high quality decisions, the design team needs to obtain a high level of situational awareness. To address this, we present an analysis of the problem of team situational awareness in design workshops and propose a model on how stakeholder positions help to build consensus within the argumentation viewpoint of architectural decisions. We show how the Software Architecture Warehouse tool has been extended to support the argumentation viewpoint within its live design document metaphor to provide support for co-located and distributed design workshops.", "image": "/biblio-covers/SAW-ecsa2013.png", "date_modified": "2013-06-30T22:00:00Z", "author": { "name": "Marcin Nowak" } }, { "id": "biblio/2013/ppopp", "html_content": "", "url": "../biblio/2013/ppopp", "title": "TigerQuoll: parallel event-based JavaScript", "summary": "JavaScript, the most popular language on the Web, is rapidly moving to the server-side, becoming even more pervasive. Still, JavaScript lacks support for shared memory parallelism, making it challenging for developers to exploit multicores present in both servers and clients. In this paper we present TigerQuoll, a novel API and runtime for parallel programming in JavaScript. TigerQuoll features an event-based API and a parallel runtime allowing applications to exploit a mutable shared memory space. The programming model of TigerQuoll features automatic consistency and concurrency management, such that developers do not have to deal with shared-data synchronization. TigerQuoll supports an innovative transaction model that allows for eventual consistency to speed up high-contention workloads. Experiments show that TigerQuoll applications scale well, allowing one to implement common parallelism patterns in JavaScript.", "image": "/biblio-covers/pjs-ppopp2013.png", "date_modified": "2013-01-31T23:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2012/composableweb", "html_content": "", "url": "../biblio/2012/composableweb", "title": "EnglishMash: Usability Design for a Natural Mashup Composition Environment", "summary": "The design of mashup tools combines elements from end-user development and software composition in the context of the Web. The challenge for mashup tool designers is to provide end-users with suitable abstractions, programming models and tool support for easily composing mashups out of existing Web services and Web data sources. In this paper we describe the design of a natural mashup composition environment based on the EnglishMash controlled natural language. The environment proactively supports users as they are learning the syntax of the EnglishMash language with features such as auto-completion, immediate feedback, live preview of the mashup execution and component discovery and selection based on natural language descriptions.", "image": "/biblio-covers/naturalmash-composableweb2012.png", "date_modified": "2012-06-30T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2012/icpads", "html_content": "", "url": "../biblio/2012/icpads", "title": "Hardware-aware thread scheduling: the case of asymmetric multicore processors", "summary": "Modern processor architectures are increasingly complex and heterogeneous, often requiring solutions tailored to the specific characteristics of each processor model. In this paper we address this problem by targeting the AMD Bulldozer processor as case study for specific hardware-oriented performance optimizations. The Bulldozer architecture features an asymmetric simultaneous multithreading implementation with shared floating point units (FPUs) and per-core arithmetic logic units (ALUs). Bulld Over, presented in this paper, improves thread scheduling by exploiting this hardware characteristic to increase performance of floating point-intensive workloads on Linux-based operating systems. Bulld Over is a user-space monitoring tool that automatically identifies FPU-intensive threads and schedules them in a more efficient way without requiring any patches or modifications at the kernel level. Our measurements using standard benchmark suites show that speedups of up to 10 can be achieved by simply allowing Bulld Over to monitor applications, without any modification of the workload.", "image": "/biblio-covers/overseer-icpads2012.png", "date_modified": "2012-11-30T23:00:00Z", "author": { "name": "Achille Peternier" } }, { "id": "biblio/2012/europar", "html_content": "", "url": "../biblio/2012/europar", "title": "Node.Scala: Implicit Parallel Programming for High-Performance Web Services", "image": "/biblio-covers/nodeS-europar2012.png", "date_modified": "2012-07-31T22:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2012/ic", "html_content": "", "url": "../biblio/2012/ic", "title": "Programmatic Interfaces for Web Applications", "image": "/biblio-covers/restapi-ic2012.png", "date_modified": "2012-01-01T00:00:00Z", "author": { "name": "Tomas Vitvar" } }, { "id": "biblio/2012/icse-scube", "html_content": "", "url": "../biblio/2012/icse-scube", "title": "Research challenges on service technology foundations", "summary": "This work gives an overview of the future research challenges on enabling technologies for service-based applications that have been identified in the network of excellence S-Cube. Service-based applications comprise three layers: business processes, service compositions and services and service infrastructures. The goal of this work is to present a roadmap for future research in technologies for software and system services.", "image": "/biblio-covers/scube-icse2012.png", "date_modified": "2012-05-31T22:00:00Z", "author": { "name": "Dimka Karastoyanova" } }, { "id": "biblio/2012/eics", "html_content": "", "url": "../biblio/2012/eics", "title": "Reusable decision space for mashup tool design", "summary": "Mashup tools are a class of integrated development environments that enable rapid, on-the-fly development of mashups - a type of lightweight Web applications mixing content and services provided through the Web. In the past few years there have been growing number of projects, both from academia and industry, aimed at the development of innovative mashup tools. From the software architecture perspective, the massive effort behind the development of these tools creates a large pool of reusable architectural decisions from which the design of future mashup tools can derive considerable benefits. In this paper, focusing on the design of mashup tools, we explore a design space of decisions comprised of design issues and alternatives. The design space knowledge not only is broad enough to explain the variability of existing tools, but also provides a road-map towards the design of next generation mashup tools.", "image": "/biblio-covers/SAW-naturalmash-eics2012.png", "date_modified": "2012-05-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2012/ppopp", "html_content": "", "url": "../biblio/2012/ppopp", "title": "S: a scripting language for high-performance RESTful web services", "summary": "There is an urgent need for novel programming abstractions to leverage the parallelism in modern multicore machines. We introduce S, a new domain-specific language targeting the server-side scripting of high-performance RESTful Web services. S promotes an innovative programming model based on explicit (control-flow) and implicit (process-level) parallelism control, allowing the service developer to specify which portions of the control-flow should be executed in parallel. For each service, the choice of the best level of parallelism is left to the runtime system. We assess performance and scalability by implementing two non-trivial composite Web services in S. Experiments show that S-based Web services can handle thousands of concurrent client requests on a modern multicore machine.", "image": "/biblio-covers/S-ppopp2012.png", "date_modified": "2012-01-31T23:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2012/wicsa", "html_content": "", "url": "../biblio/2012/wicsa", "title": "Software Architecture Warehouse: live and collaborative architectural decision making", "date_modified": "2012-01-01T00:00:00Z", "author": { "name": "Marcin Nowak" } }, { "id": "biblio/2013/icse-seip", "html_content": "", "url": "../biblio/2013/icse-seip", "title": "Specification patterns from research to industry: A case study in service-based applications", "summary": "Specification patterns have proven to help developers to state precise system requirements, as well as formalize them by means of dedicated specification languages. Most of the past work has focused its applicability area to the specification of concurrent and real-time systems, and has been limited to a research setting. In this paper we present the results of our study on specification patterns for service-based applications (SBAs). The study focuses on industrial SBAs in the banking domain. We started by performing an extensive analysis of the usage of specification patterns in published research case studies - representing almost ten years of research in the area of specification, verification, and validation of SBAs. We then compared these patterns with a large body of specifications written by our industrial partner over a similar time period. The paper discusses the outcome of this comparison, indicating that some needs of the industry, especially in the area of requirements specification languages, are not fully met by current software engineering research.", "image": "/biblio-covers/clavos-icse2013-seip.png", "date_modified": "2012-05-31T22:00:00Z", "author": { "name": "Domenico Bianculli" } }, { "id": "biblio/2012/wsrest", "html_content": "", "url": "../biblio/2012/wsrest", "title": "Third International Workshop on RESTful Design (WS-REST 2012)", "image": "/biblio-covers/wsrest2012.png", "date_modified": "2012-02-29T23:00:00Z", "author": { "name": "Rosa Alarcón" } }, { "id": "biblio/2011/ecows", "html_content": "", "url": "../biblio/2011/ecows", "title": "9th IEEE European Conference on Web Services (ECOWS 2011)", "image": "/biblio-covers/ecows2011.png", "date_modified": "2011-08-31T22:00:00Z", "author": { "name": "Gianluigi Zavattaro" } }, { "id": "biblio/2011/wicsa", "html_content": "", "url": "../biblio/2011/wicsa", "title": "An Architectural Style for Liquid Web Services", "summary": "Just as liquids adapt their shape to the one of their container, liquid architectures feature a high degree of adaptability so that they can provide scalability to applications as they are executed on a wide variety of heterogeneous deployment environments. In this paper we enumerate the properties to be guaranteed by so-called liquid service-oriented architectures and define a set of design constraints that make up a novel architectural style for liquid architectures. These constraints drive the careful construction of a pattern, the Restful Actor (Reactor), which enables to deliver the required scalability by means of replication of its constituent parts. Reactors feature a Restful Web service interface and a composable architecture which is capable of delivering scalability and high performance in a way that is independent from the chosen deployment infrastructure. We discuss how the Reactor can be deployed to run on distributed (shared-nothing) execution environments typical of virtualized Cloud computing environments as well as on modern multicore processors with shared memory architectures.", "image": "/biblio-covers/liquidws-wicsa2011.png", "date_modified": "2011-05-31T22:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2011/bpmn", "html_content": "", "url": "../biblio/2011/bpmn", "title": "BPMN for REST", "summary": "The Representational State Transfer (REST) architectural style has seen substantial growth and adoption for the design of modern Resource-Oriented Architectures. However, the impact of fundamental constraints such as stateful resources, stateless interactions, and the uniform interface have had only limited uptake and impact in the Business Process Modeling (BPM) community in general, and in the standardization activities revolving around the BPMN notation. In this paper we propose a simple and minimal extension of the BPMN 2.0 notation to provide first-class support for the concept of resource. We show several examples of how the extended notation can be used to externalize the state of a process as a resource, as well as to describe process-driven composition of resources.", "image": "/biblio-covers/rest-bpmn2011.png", "date_modified": "2011-10-31T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2011/icwe-phd", "html_content": "", "url": "../biblio/2011/icwe-phd", "title": "End-User Programming for Web Mashups - Open Research Challenges", "summary": "Mashup is defined as the practice of lightweight composition, serendipitous reuse, and user-centric development on the Web. In spite of the fact that the development of mashups is rather simple due to the reuse of all the required layers of a Web application (functionality, data, and user interface), it still requires programming experience. This is a significant hurdle for non-programmers (end-users with minimal or no programming experience), who constitute the majority of Web users. To cope with this, an End-User Programming (EUP) tool can be designed to reduce the barriers of mashup development, in a way that even non-programmers will be able to create innovative, feature-rich mashups. In this paper, we give an overview of the existing EUP approaches for mashup development, as well as a list of open research challenges.", "image": "/biblio-covers/naturalmash-icwe2011phd.png", "date_modified": "2011-05-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2011/composableweb", "html_content": "", "url": "../biblio/2011/composableweb", "title": "An Evaluation of Mashup Tools Based on Support for Heterogeneous Mashup Components", "summary": "Mashups are built by combining building blocks, which are commonly referred to as mashup components. These components are characterized by a high level of heterogeneity in terms of technologies, access methods, and the behavior they may exhibit within a mashup. Abstracting away this heterogeneity is the mission of the so-called mashup tools aiming at automating or semi-automating mashup development to serve non-programmers. The challenge is to ensure this abstraction mechanism does not limit the support for heterogeneous mashup components. In this paper, we propose a novel evaluation framework that can be applied to assess the degree to which a given mashup tool addresses this challenge. The evaluation framework can serve as a benchmark for future improved design of mashup tools with respect to heterogeneous mashup components support. In order to demonstrate the applicability of the framework, we also apply it to evaluate some existing tools.", "image": "/biblio-covers/naturalmash-composableweb2011.png", "date_modified": "2011-05-31T22:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2011/shark", "html_content": "", "url": "../biblio/2011/shark", "title": "Goals, questions and metrics for architectural decision models", "summary": "Architectural decisions are the key element behind the design process leading to a software architecture. Making software architects aware of the implications of their decisions is only the beginning of what can be achieved by capturing the rationale and the constraints influencing the decision making process in a reusable body of architectural knowledge. In this paper we propose a metric-based approach to the analysis of architectural decision models. Using a hierarchically-structured approach we identify a number of useful goals and stakeholders involved in the architectural design process. Next, we sketch a set of metrics to provide data for the evaluation of the aforementioned goals. Our aim is to stimulate a discussion on how to find indicators relevant for software architects by measuring the intrinsic properties of architectural knowledge.", "image": "/biblio-covers/SAW-shark2011.png", "date_modified": "2011-04-30T22:00:00Z", "author": { "name": "Marcin Nowak" } }, { "id": "biblio/2011/icsoc-phd", "html_content": "", "url": "../biblio/2011/icsoc-phd", "title": "ICSOC2011 Phd Symposium Preface", "image": "/biblio-covers/icsoc2011-phd.png", "date_modified": "2011-11-30T23:00:00Z", "author": { "name": "Quan Z. Sheng" } }, { "id": "biblio/2011/iiwas", "html_content": "", "url": "../biblio/2011/iiwas", "title": "The mashup component description language", "summary": "Mashups can be seen as the result of software composition applied to the Web. One of the characteristics of mashup development is the heterogeneity of its building components in terms of logical layering (e.g., user interface, application logic, and data), access method (e.g., REST, SOAP), and composition technique (e.g., scraping vs. clipping, synchronous vs. asynchronous interaction, discrete vs. streaming). This poses a challenge towards the design of mashup tools aiming at lowering the barriers of mashup development, as this heterogeneity needs to be abstracted. In this paper, we address this challenge by proposing a new JSON-based domain-specific language for describing heterogeneous mashup components, called the Mashup Component Description Language (MCDL). MCDL lies at the core of a meta-model for mashup component modeling, and can be used for component discovery and classification but also for user-centric mashup development as it decouples the interface of a mashup component from its underlying implementation technologies.", "image": "/biblio-covers/naturalmash-iiwas2011.png", "date_modified": "2011-11-30T23:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2011/pppj", "html_content": "", "url": "../biblio/2011/pppj", "title": "Overseer: low-level hardware monitoring and management for Java", "summary": "The high-level and portable nature of the Java platform allows applications to be written once and executed on all the supported systems. However, such a feature comes at the cost of hardware abstraction, making it more difficult or even impossible to access several low-level functionalities. Overseer is a Java framework that makes it possible on Linux systems by simplifying access to real-time measurement of low-level data such as Hardware Performance Counters (HPCs), IPMI sensors, and Java VM internal events. Overseer supports functionalities such as HPC-management, process/thread affinity settings, hardware topology identification, as well as power-consumption and temperature monitoring. In this paper we describe Overseer and how to use it to extend Java applications with functionalities not provided by the default runtime. A public release of Overseer is available.", "image": "/biblio-covers/overseer-pppj2011.png", "date_modified": "2011-07-31T22:00:00Z", "author": { "name": "Achille Peternier" } }, { "id": "biblio/2011/icsoc", "html_content": "", "url": "../biblio/2011/icsoc", "title": "Push-Enabling RESTful Business Processes", "summary": "Representational State Transfer (REST) as an architectural style for service design has seen substantial uptake in the past years. However, some areas such as Business Process Modeling (BPM) and push services so far have not been addressed in the context of REST principles. In this work, we look at how both BPM and push can be combined so that business processes can be modeled and observed in a RESTful way. Based on this approach, clients can subscribe to be notified when certain states in a business process are reached. Our goal is to design an architecture that brings REST's claims of loose coupling and good scalability to the area of BPM, and still allow process-driven composition and interaction between resources to be modeled.", "image": "/biblio-covers/restbpm-icsoc2011.png", "date_modified": "2011-11-30T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/book/rest", "html_content": "", "url": "../biblio/book/rest", "title": "REST: From Research to Practice", "image": "/biblio-covers/rest2011.png", "date_modified": "2011-01-01T00:00:00Z", "author": { "name": "Erik Wilde" } }, { "id": "biblio/2011/wsrest", "html_content": "", "url": "../biblio/2011/wsrest", "title": "Second international workshop on RESTful design (WS-REST 2011)", "image": "/biblio-covers/wsrest2011.png", "date_modified": "2011-02-28T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2011/rest-tcc", "html_content": "", "url": "../biblio/2011/rest-tcc", "title": "Towards Distributed Atomic Transactions over RESTful Services", "summary": "There is considerable debate in the REST community whether or not transaction support is needed and possible. This chapter's contribution to this debate is threefold: we define a business case for transactions in REST based on the Try-Cancel/Confirm (TCC) pattern; we outline a very light-weight protocol that guarantees atomicity and recovery over distributed REST resources; and we discuss the inherent theoretical limitations of our approach. Our TCC for REST approach minimizes the assumptions made on the individual services that can be part of a transaction and does not require any extension to the HTTP protocol. A very simple but realistic example helps to illustrate the applicability of the approach.", "image": "/biblio-covers/rest-tcc.png", "date_modified": "2011-01-01T00:00:00Z", "author": { "name": "Guy Pardon" } }, { "id": "biblio/2011/www-phd", "html_content": "", "url": "../biblio/2011/www-phd", "title": "Towards liquid service oriented architectures", "summary": "The advent of Cloud computing platforms, and the growing pervasiveness of Multicore processor architectures have revealed the inadequateness of traditional programming models based on sequential computations, opening up many challenges for research on parallel programming models for building distributed, service-oriented systems. More in detail, the dynamic nature of Cloud computing and its virtualized infrastructure pose new challenges in term of application design, deployment and dynamic reconfiguration. An application developed to be delivered as a service in the Cloud has to deal with poorly understood issues such as elasticity, infinite scalability and portability across heterogeneous virtualized environments. In this position paper we define the problem of providing a novel parallel programming model for building application services that can be transparently deployed on multicore and cloud execution environments. To this end, we introduce and motivate a research plan for the definition of a novel programming framework for Web service-based applications. Our vision called \"Liquid Architecture\" is based on a programming model inspired by core ideas tied to the REST architectural style coupled with a self-configuring runtime that allows transparent deployment of Web services on a broad range of heterogeneous platforms, from multicores to clouds.", "image": "/biblio-covers/liquidws-www2011-phd.png", "date_modified": "2011-03-31T22:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2011/seass", "html_content": "", "url": "../biblio/2011/seass", "title": "Towards Self-Organizing Service-Oriented Architectures", "summary": "Service-oriented architectures (SOAs) provide a successful model for structuring complex distributed software systems, as they reduce the cost of ownership and ease the creation of new applications by composing existing services. However, currently, the development of service-oriented applications requires many manual tasks and prevailing infrastructure is often based on centralized components that are central points of failure and easily become bottlenecks. In this paper, we promote self-organizing SOA as a new approach to overcome these limitations. Self-organizing SOA integrates research results in the areas of autonomic and service oriented computing. We consider self-organizing features for the whole life-cycle of a service-oriented application, from the creation to the execution, optimization, and monitoring.", "image": "/biblio-covers/sosoa-seass2011.png", "date_modified": "2011-06-30T22:00:00Z", "author": { "name": "Walter Binder" } }, { "id": "biblio/2010/ecows", "html_content": "", "url": "../biblio/2010/ecows", "title": "8th IEEE European Conference on Web Services (ECOWS 2010)", "image": "/biblio-covers/ecows2010.png", "date_modified": "2010-11-30T23:00:00Z", "author": { "name": "Antonio Brogi" } }, { "id": "biblio/2010/shark", "html_content": "", "url": "../biblio/2010/shark", "title": "Architectural decision modeling with reuse", "summary": "Architectural decision modeling aims at supporting the software architecture design process by capturing a reusable body of architectural knowledge. Whereas significant progress has been made towards this vision, there still remains a number of open problems. This paper outlines selected research challenges and opportunities related to knowledge capturing and sharing, model evolution and verification, and the integration of the architectural design process with existing software development methodologies. Our goal is to start a discussion on a roadmap for future research on reusable modeling of architectural decisions.", "image": "/biblio-covers/SAW-shark2010.png", "date_modified": "2010-04-30T22:00:00Z", "author": { "name": "Marcin Nowak" } }, { "id": "biblio/2010/icwe", "html_content": "", "url": "../biblio/2010/icwe", "title": "Engineering autonomic controllers for virtualized web applications", "image": "/biblio-covers/jopera-icwe2010.png", "date_modified": "2010-06-30T22:00:00Z", "author": { "name": "Giovanni Toffetti-Carughi" } }, { "id": "biblio/2010/soca", "html_content": "", "url": "../biblio/2010/soca", "title": "Exploiting multicores to optimize business process execution", "summary": "While modern CPUs offer an increasing number of cores with shared caches, prevailing execution engines for business processes, workflows, or Web service compositions have not been optimized for properly exploiting the abundant processing resources of such CPUs. One factor limiting performance is the inefficient thread scheduling by the operating system, which can result in suboptimal use of shared caches. In this paper we study performance of the JOpera business process execution engine on a recent multicore machine. By analyzing the engine's architecture and by binding threads that are likely to access shared data to cores with a common cache, we achieve speedups up to 13 for a variety of workloads, without modifying the engine's architecture and implementation, apart from binding threads to CPUs. As the engine is implemented in Java, we provide a new Java library to manage thread bindings and hardware performance counters. We also leverage hardware performance counters to explain the observed speedup in our performance analysis.", "image": "/biblio-covers/jopera-soca2010.png", "date_modified": "2010-11-30T23:00:00Z", "author": { "name": "Achille Peternier" } }, { "id": "biblio/2010/wsrest", "html_content": "", "url": "../biblio/2010/wsrest", "title": "First International Workshop on RESTful Design (WS-REST 2010)", "image": "/biblio-covers/wsrest2010.png", "date_modified": "2010-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2010/ic", "html_content": "", "url": "../biblio/2010/ic", "title": "Information Quality in Mashups", "summary": "Modern Web 2.0 applications are characterized by high user involvement: users receive support for creating content and annotations as well as \"composing\" applications using content and functions from third parties. This latter phenomenon is known as Web mashups and is gaining popularity even with users who have few programming skills, raising a set of peculiar information quality issues. Assessing a mashup's quality, especially the information it provides, requires understanding how the mashup has been developed, how its components look alike, and how quality propagates from basic components to the final mashup application.", "image": "/biblio-covers/mashupsquality-ic2010.png", "date_modified": "2010-07-31T22:00:00Z", "author": { "name": "Cinzia Cappiello" } }, { "id": "biblio/2010/mashups", "html_content": "", "url": "../biblio/2010/mashups", "title": "Mashup Development with HTML5", "summary": "HTML5 is a new technology standard promising to empower browsers to become a suitable platform for developing rich Web applications. Whilst it is still considered an emerging technology, in this paper we attempt to capture and explore its impacts on mashup development. To do so, we start with a mashup case study showcasing new HTML5 features. We then move on to explore those aspects of mashup development that are affected and will possibly be enabled by HTML5 in the near future. These aspects are grouped into two categories: short-term impacts, that can be harnessed by mashup developers, and long-term impacts, that should be considered by service/content providers.", "image": "/biblio-covers/html5-mashups2010.png", "date_modified": "2010-11-30T23:00:00Z", "author": { "name": "Saeed Aghaee" } }, { "id": "biblio/2010/apscc", "html_content": "", "url": "../biblio/2010/apscc", "title": "A Multicore-Aware Runtime Architecture for Scalable Service Composition", "summary": "Middleware for web service orchestration, such as runtime engines for executing business processes, workflows, or web service compositions, can easily become performance bottlenecks when the number of concurrent service requests increases. Many existing process execution engines have been designed to address scalability with distribution and replication techniques. However, the advent of modern multicore machines, comprising several chip multi-processors each offering multiple cores and often featuring a large shared cache, offers the opportunity to redesign the architecture of process execution engines in order to take full advantage of the underlying hardware resources. In this paper we present an innovative process execution engine architecture. Its design takes into account the specific constraints of multicore machines and scales well on different processor architectures, as shown by our extensive performance evaluation. A key feature of the design is self-configuration at startup according to the type and number of available CPUs. We show that our design makes efficient use of the available resources and can scale to run thousands of concurrent business process instances per second, highlighting the potential and the benefits for multicore-awareness in the design of scalable process execution engines.", "image": "/biblio-covers/jopera-apscc2010.png", "date_modified": "2010-11-30T23:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2010/swws", "html_content": "", "url": "../biblio/2010/swws", "title": "Towards scalable service composition on multicores", "summary": "The advent of modern multicore machines, comprising several chip multi-processors each offering multiple cores and often featuring a large shared cache, offers the opportunity to redesign the architecture of service composition engines in order to take full advantage of the underlying hardware resources. In this paper we introduce an innovative service composition engine architecture, which takes into account specific features of multicore machines while not being constrained to run on any particular processor architecture. Our preliminary performance evaluation results show that the system can scale to run thousands of concurrent business process instances per second.", "image": "/biblio-covers/jopera-swws2010.png", "date_modified": "2010-09-30T22:00:00Z", "author": { "name": "Daniele Bonetta" } }, { "id": "biblio/2009/hrbpm", "html_content": "", "url": "../biblio/2009/hrbpm", "title": "Compiling Business Process Models into Executable Code", "summary": "Model-driven architecture (MDA), design and transformation techniques can be applied with success to the domain of business process modeling (BPM) with the goal of making the vision of business-driven development a reality. This chapter is centered around the idea of compiling business process models for executing them, and how this idea has been driving the design of the JOpera for Eclipse workflow management tool. JOpera presents users with a simple, graph-based process modeling language with a visual representation of both control and data-flow aspects. As an intermediate representation, the graphs are converted into Event-Condition-Action rules, which are further compiled into Java bytecode for efficient execution. These transformations of process models are performed by the JOpera process compiler in a completely transparent way, where the generated executable artifacts are kept hidden from users at all times (i.e., even for debugging process executions, which is done by augmenting the original, high level notation). We evaluate our approach by discussing how using a compiler has opened up the several possibilities for performing optimization on the generated code and also simplified the design the corresponding workflow engine architecture.", "image": "/biblio-covers/jopera-hrbpm2009.png", "date_modified": "2009-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2009/sc", "html_content": "", "url": "../biblio/2009/sc", "title": "Composing RESTful Services with JOpera", "summary": "The REST architectural style is emerging as an alternative technology platform for the realization of service-oriented architectures. In this paper, we apply the notion of composition to RESTful services and derive a set of language features that are required by composition languages for RESTful services: dynamic late binding, dynamic typing, content-type negotiation, state inspection, and compliance with the uniform interface principle. To show how such requirements can be satisfied by an existing composition language, we include a case-study using the JOpera visual composition language. In it, we present how to build a composite application (DoodleMap) out of some well-known, public and currently existing RESTful service APIs.", "image": "/biblio-covers/jopera-rest-sc2009.png", "date_modified": "2009-06-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2009/pesos", "html_content": "", "url": "../biblio/2009/pesos", "title": "Embedding continuous lifelong verification in service life cycles", "summary": "Service-oriented systems are an instantiation of open world software, which is characterized by high dynamism and decentralization. These properties strongly impact on how service-oriented systems are engineered, built, and operated, as well as verified. To address the challenges of applying verification to open service-oriented systems, in this position paper we propose to apply verification across the entire life cycle of a service and introduce a verification-oriented service life cycle.", "image": "/biblio-covers/clavos-pesos2009.png", "date_modified": "2009-04-30T22:00:00Z", "author": { "name": "Domenico Bianculli" } }, { "id": "biblio/2009/mediation", "html_content": "", "url": "../biblio/2009/mediation", "title": "Mediation", "image": "/biblio-covers/db2009.png", "date_modified": "2009-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2009/jdke", "html_content": "", "url": "../biblio/2009/jdke", "title": "RESTful Web service composition with BPEL for REST", "summary": "Current Web service technology is evolving towards a simpler approach to define Web service APIs that challenges the assumptions made by existing languages for Web service composition. RESTful Web services introduce a new kind of abstraction, the resource, which does not fit well with the message-oriented paradigm of the Web service description language (WSDL). RESTful Web services are thus hard to compose using the Business Process Execution Language (WS-BPEL), due to its tight coupling to WSDL. The goal of the BPEL for REST extensions presented in this paper is twofold. First, we aim to enable the composition of both RESTful Web services and traditional Web services from within the same process-oriented service composition language. Second, we show how to publish a BPEL process as a RESTful Web service, by exposing selected parts of its execution state using the REST interaction primitives. We include a detailed example on how BPEL for REST can be applied to orchestrate a RESTful e-Commerce scenario and discuss how the proposed extensions affect the architecture of a process execution engine. ", "image": "/biblio-covers/bpel4rest-jdke2009.png", "date_modified": "2009-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2009/mashups", "html_content": "", "url": "../biblio/2009/mashups", "title": "Third international workshop on web APIs and services Mashups (Mashups 2009)", "image": "/biblio-covers/mashups2009.png", "date_modified": "2009-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2009/gpc", "html_content": "", "url": "../biblio/2009/gpc", "title": "The Tiny Instrument Element", "summary": "In the past few years, the idea of extending the Grid to cover also the remote access, control, management of instrument devices has been explored in a few initiatives. Existing tools lack in generality and require advanced specialized computer science knowledge, thus making them difficult to be broadly adopted in the scientific community. In this paper we present a new open source initiative that is designed to overcome these problems. The Tiny Instrument Element project defines a high level architecture for plugging instruments into the Grid and provides the corresponding skeleton implementation. This lightweight approach, as opposed to existing middleware-based solutions, reduces the effort required to Gridify existing instruments. The paper evaluates the proposed abstraction with a case study from a pervasive computing scenario.", "image": "/biblio-covers/tie-gpc2009.png", "date_modified": "2009-04-30T22:00:00Z", "author": { "name": "Francesco Lelli" } }, { "id": "biblio/2009/www", "html_content": "", "url": "../biblio/2009/www", "title": "Why is the Web Loosely Coupled? A Multi-Faceted Metric for Service Design", "summary": "Loose coupling is often quoted as a desirable property of systems architectures. One of the main goals of building systems using Web technologies is to achieve loose coupling. However, given the lack of a widely accepted definition of this term, it becomes hard to use coupling as a criterion to evaluate alternative Web technology choices, as all options may exhibit, and claim to provide, some kind of \"loose\" coupling effects. This paper presents a systematic study of the degree of coupling found in service-oriented systems based on a multi-faceted approach. Thanks to the metric introduced in this paper, coupling is no longer a one-dimensional concept with loose coupling found somewhere in between tight coupling and no coupling. The paper shows how the metric can be applied to real-world examples in order to support and improve the design process of service-oriented systems.", "image": "/biblio-covers/restws-www2009.png", "date_modified": "2009-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2008/jopera-icac2008", "html_content": "", "url": "../biblio/2008/jopera-icac2008", "title": "Automatic Configuration of an Autonomic Controller: An Experimental Study with Zero-Configuration Policies", "summary": "Autonomic control managers can remove the need for manual system configuration in order to achieve good performance and efficient resource utilization. However, simple controllers based on reconfiguration actions tied to thresholds, or 'if-then' rules, themselves need to be configured and tuned in order to adapt the controller behavior to the expected workload characteristic. In this paper we present an experimental study of zero-configuration policies that can be automatically tuned based on analytical models of the system under control. In particular, we have designed and implemented a threshold-free self-configuration policy for a distributed workflow execution engine and compared it with a standard PID controller. The experimental results included in the paper show that using such a policy the controller can tune itself in addition to reconfiguring the distributed engine and the proposed policy out-performs simpler policies that require manual and error-prone tuning of their parameters.", "image": "/biblio-covers/jopera-icac2008.png", "date_modified": "2008-05-31T22:00:00Z", "author": { "name": "Thomas Heinis" } }, { "id": "biblio/2008/bpm", "html_content": "", "url": "../biblio/2008/bpm", "title": "BPEL for REST", "summary": "Novel trends in Web services technology challenge the assumptions made by current standards for process-based service composition. Most RESTful Web service APIs, which do not rely on the Web service description language (WSDL), cannot easily be composed using the BPEL language. In this paper we propose a lightweight BPEL extension to natively support the composition of RESTful Web services using business processes. We also discuss how to expose the execution state of a business process so that it can be manipulated through REST primitives in a controlled way.", "image": "/biblio-covers/bpel4rest-bpm2008.png", "date_modified": "2008-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/book/wewst08", "html_content": "", "url": "../biblio/book/wewst08", "title": "Emerging Web Services Technology", "summary": "This book contains a collection of selected and revised papers originally presented at the Workshop on Emerging Web Service Technology (WEWST'07) held in conjunction with the 5th European Conference on Web Services (ECOWS'07) in November 2007 in Halle (Saale), Germany. Acting as the natural extension to the main ECOWS conference, the main goal of the WEWST workshop is serving as a forum for providing early exposure and much needed feedback to grow and establish original and emerging ideas within the Web Services community. The wide variety of tools, techniques and technological solutions presented in WEWST share one common feature: they advance the current Web services research in new directions by introducing new and sometimes controversial ideas into the field.", "image": "/biblio-covers/wewst2008.png", "date_modified": "2008-01-01T00:00:00Z", "author": { "name": "Thomas Gschwind" } }, { "id": "biblio/2008/ccgrid", "html_content": "", "url": "../biblio/2008/ccgrid", "title": "Initializing a National Grid Infrastructure Lessons Learned from the Swiss National Grid Association Seed Project", "summary": "In addition to multi-national Grid infrastructures, several countries operate their own national Grid infrastructures to support science and industry within national borders. These infrastructures have the benefit of better satisfying the needs of local, regional and national user communities. Although Switzerland has strong research groups in several fields of distributed computing, only recently a national Grid effort was kick-started to integrate a truly heterogeneous set of resource providers, middleware pools, and users. In the following article we discuss our efforts to start Grid activities at a national scale to combine several scientific communities and geographical domains. We make a strong case for the need of standards that have to be built on top of existing software systems in order to provide support for a heterogeneous Grid infrastructure.", "image": "/biblio-covers/swing-ccgrid2008.png", "date_modified": "2008-04-30T22:00:00Z", "author": { "name": "Nabil Abdennadher" } }, { "id": "biblio/2008/mashups", "html_content": "", "url": "../biblio/2008/mashups", "title": "Second International Workshop on Web APIs and Services Mashups (Mashups 2008)", "image": "/biblio-covers/mashups2008.png", "date_modified": "2008-11-30T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2008/mde4bpm", "html_content": "", "url": "../biblio/2008/mde4bpm", "title": "First International Workshop on Model-Driven Engineering for Business Process Management (MDE4BPM 2008)", "image": "/biblio-covers/bpm2008w.png", "date_modified": "2008-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2008/mashups-atelier", "html_content": "", "url": "../biblio/2008/mashups-atelier", "title": "The Mashup Atelier", "summary": "Can mashups be used to make high school students interested in studying computer science? To answer this question, we have designed the mashup atelier. The goal of this experimental lecture is to make students realize that the Web is not only a medium for passively consuming information but it can be actively reprogrammed as they see fit. The atelier introduces the topic of Web 2.0 Mashups to students without any formal pre-existing computer science education. After giving the atelier several times, we report on the results of a student evaluation survey showing that, if supported with right kind of mashup tools, creative students can become very productive developing interesting mashups in a short timeframe. The feedback we gathered from the students can also be used to improve existing mashup languages and tools, with the ultimate goal of understanding what makes them intuitive and fun to use.", "image": "/biblio-covers/mashupatelier2008.png", "date_modified": "2008-11-30T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2008/www", "html_content": "", "url": "../biblio/2008/www", "title": "RESTful Web Services vs. Big Web Services: Making the Right Architectural Decision", "summary": "Recent technology trends in the Web Services (WS) domain indicate that a solution eliminating the presumed complexity of the WS-* standards may be in sight: advocates of REpresentational State Transfer (REST) have come to believe that their ideas explaining why the World Wide Web works are just as applicable to solve enterprise application integration problems and to simplify the plumbing required to build service-oriented architectures. In this paper we objectify the WS-* vs. REST debate by giving a quantitative technical comparison based on architectural principles and decisions. We show that the two approaches differ in the number of architectural decisions that must be made and in the number of available alternatives. This discrepancy between freedom-from-choice and freedom-of-choice explains the complexity difference perceived. However, we also show that there are significant differences in the consequences of certain decisions in terms of resulting development and maintenance costs. Our comparison helps technical decision makers to assess the two integration styles and technologies more objectively and select the one that best fits their needs: REST is well suited for basic, ad hoc integration scenarios, WS-* is more flexible and addresses advanced quality of service requirements commonly occurring in enterprise computing. ", "image": "/biblio-covers/www2008-restws-pautasso-zimmermann-leymann.png", "date_modified": "2008-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2008/bioinformatics", "html_content": "", "url": "../biblio/2008/bioinformatics", "title": "swissPIT: a novel approach for pipelined analysis of mass spectrometry data", "summary": "The identification and characterization of peptides from tandem mass spectrometry (MS/MS) data represents a critical aspect of proteomics. Today, tandem MS analysis is often performed by only using a single identification program achieving identification rates between 10-50 (Elias and Gygi, 2007). Beside the development of new analysis tools, recent publications describe also the pipelining of different search programs to increase the identification rate (Hartler et al., 2007; Keller et al., 2005). The Swiss Protein Identification Toolbox (swissPIT) follows this approach, but goes a step further by providing the user an expandable multi-tool platform capable of executing workflows to analyze tandem MS-based data. One of the major problems in proteomics is the absent of standardized workflows to analyze the produced data. This includes the pre-processing part as well as the final identification of peptides and proteins. The main idea of swissPIT is not only the usage of different identification tool in parallel, but also the meaningful concatenation of different identification strategies at the same time. The swissPIT is open source software but we also provide a user-friendly web platform, which demonstrates the capabilities of our software and which is available at http://swisspit.cscs.ch upon request for account.", "image": "/biblio-covers/bioinformatics2008.png", "date_modified": "2008-01-01T00:00:00Z", "author": { "name": "Andreas Quandt" } }, { "id": "biblio/2007/seke", "html_content": "", "url": "../biblio/2007/seke", "title": "ADkwik: Web 2.0 Collaboration System for Architectural Decision Engineering", "summary": "Capturing and sharing software architecture design rationale has always been particularly challenging in complex application domains such as enterprise computing. Facing the ongoing acceleration of technology innovation and economic forces such as outsourcing and offshoring, conservative knowledge management practices and existing tools are no longer sufficient, offering only rudimentary support for knowledge exchange and collaboration on the Internet. In this paper, we present ADkwik, a Web 2.0 collaboration system supporting the cooperative decision making work of software architects. We describe the realization of ADkwik as a situational application wiki and discuss initial evaluation results. Thanks to its ease of use, ADkwik has already shown concrete benefits to its users, including rapid team orientation, tangible decision making advice, and simplification of asset harvesting.", "image": "/biblio-covers/adkwik-seke2007.png", "date_modified": "2007-06-30T22:00:00Z", "author": { "name": "Nelly Schuster" } }, { "id": "biblio/2007/jist", "html_content": "", "url": "../biblio/2007/jist", "title": "Autonomic resource provisioning for software business processes", "summary": "Software development nowadays involves several levels of abstraction: starting from the programming of single objects, to their combination into components, to their publication as services and the overall architecture linking elements at each level. As a result, software engineering is dealing with a wider range of artifacts and concepts (i.e., in the context of this paper: services and business processes) than ever before. In this paper we explore the importance of having an adequate engine for executing business processes written as compositions of Web services. The paper shows that, independently of the composition language used, the overall scalability of the system is determined by how the run-time engine treats the process execution. This is particularly relevant at the service level because publishing a process through a Web service interface makes it accessible to an unpredictable and potentially very large number of clients. As a consequence, the process developer is confronted with the difficult question of resource provisioning. Determining the optimal configuration of the distributed engine that runs the process becomes sensitive both to the actual number of clients and to the kinds of processes to be executed. The main contribution of the paper is to show how resource provisioning for software business processes can be solved using autonomic computing techniques. The engine separates execution in two stages (navigation and dispatching) and uses a controller to allocate the node of a cluster of computers to each one of those stages as the workload changes. The controller can be configured with different policies that define how to reconfigure the system. To prove the feasibility of the concept, we have implemented the autonomic controller and evaluated its performance with an extensive set of experiments.", "image": "/biblio-covers/jopera-jist2007.png", "date_modified": "2006-12-31T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2007/agtive", "html_content": "", "url": "../biblio/2007/agtive", "title": "Combining Quality Assurance and Model Transformations in Business-Driven Development", "summary": "Business-driven development is a methodology for developing IT solutions that directly satisfy business requirements. At its core are business processes, which are usually modeled by combining graphical and textual notations. During business-driven development, business process models are taken to the IT level, where they are implemented in a Service-Oriented Architecture. A major challenge in business-driven development is the semantic gap between models captured at the business and the IT level. Model transformations play a major role in bridging this gap.\n\nThis paper presents a transformation framework for IBM WebSphere Business Modeler that enables programmers to quickly develop in-place model transformations, which are then made available to users of this tool. They address various user needs such as quickly correcting modeling errors, refining a process model, or applying a number of refactoring operations. Transformations are combined with quality assurance techniques, which help users to preserve or improve the correctness of their business process models when applying transformations.\n", "image": "/biblio-covers/ibm-agtive2007.png", "date_modified": "2007-09-30T22:00:00Z", "author": { "name": "Jana Koehler" } }, { "id": "biblio/2007/wewst", "html_content": "", "url": "../biblio/2007/wewst", "title": "Emerging Web Services Technology", "image": "/biblio-covers/wewst2007.png", "date_modified": "2007-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2007/healthgrid", "html_content": "", "url": "../biblio/2007/healthgrid", "title": "Grid-based Analysis of Tandem Mass Spectrometry Data in Clinical Proteomics", "summary": "Biomarker detection is one of the greatest challenges in Clinical Proteomics. Today, great hopes are placed into tandem mass spectrometry (MS/MS) to discover potential biomarkers. MS/MS is a technique that allows large scale data analysis, including the identification, characterization, and quantification of molecules. Especially the identification process, that implies to compare experimental spectra with theoretical amino acid sequences stored in specialized databases, has been subject for extensive research in bioinformatics since many years. Dozens of identification programs have been developed addressing different aspects of the identification process but in general, clinicians are only using a single tools for their data analysis along with a single set of specific parameters. Hence, a significant proportion of the experimental spectra do not lead to a confident identification score due to inappropriate parameters or scoring schemes of the applied analysis software. The swissPIT (Swiss Protein Identification Toolbox) project was initiated to provide the scientific community with an expandable multi-tool platform for automated and in-depth analysis of mass spectrometry data. The swissPIT uses multiple identification tools to automatic analyze mass spectra. The tools are concatenated as analysis workflows. In order to realize these calculation-intensive workflows we are using the Swiss Bio Grid infrastructure. A first version of the web-based front-end is available (http://www.swisspit.cscs.ch) and can be freely accessed after requesting an account. The source code of the project will be also made available in near future.", "image": "/biblio-covers/jopera-healthgrid2007.png", "date_modified": "2007-01-01T00:00:00Z", "author": { "name": "Andreas Quandt" } }, { "id": "biblio/2007/mashups", "html_content": "", "url": "../biblio/2007/mashups", "title": "Let it flow: Building Mashups with Data Processing Pipelines", "summary": "Mashups are a new kind of interactive Web application, built out of the composition of two or more existing Web service APIs and data sources. Whereas \"pure\" mashups are built relying entirely on the Web browser as a platform for integration at the presentation layer, this approach is not always feasible and part of the mashup integration logic must be deployed on the Web server instead. In the case study presented in this paper, we explore a novel approach to build mashups out of heterogeneous sources of streaming data. In particular, we introduce a layered mashup architecture, with a clear separation between the mashup user interface and the mashup integration logic run by a mashup engine. To do so, we show how to build a mashup application that displays in real time the location of visitors connecting to a Website. The integration logic feeding a map widget by processing the Web site logs is developed using a data flow model that connects a set of reusable and heterogeneous components into a data processing pipeline. We conduct a brief performance evaluation of the mashup showing that the pipeline introduces minimal delay and discuss several extensions of the mashup.", "image": "/biblio-covers/jopera-mashup07.png", "date_modified": "2007-08-31T22:00:00Z", "author": { "name": "Biörn Biörnstad" } }, { "id": "biblio/2006/hasler", "html_content": "", "url": "../biblio/2006/hasler", "title": "Autonomic Computing for Virtual Laboratories", "summary": "Virtual laboratories can be characterized by their long-lasting, large-scale computations, where a collection of heterogeneous tools is integrated into data processing pipelines. Such virtual experiments are typically modeled as scientific workflows in order to guarantee their reproduceability. In this chapter we present JOpera, one of the first autonomic infrastructures for managing virtual laboratories. JOpera provides a sophisticated Eclipse-based graphical environment to design, monitor and debug distributed computations at a high level of abstraction. The chapter describes the architecture of the workflow execution environment, emphasizing its support for the integration of heterogeneous tools and evaluating its autonomic capabilities, both in terms of reliable execution (self-healing) and automatic performance optimization (self-tuning).", "image": "/biblio-covers/jopera-hasler2006.png", "date_modified": "2006-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2006/scc", "html_content": "", "url": "../biblio/2006/scc", "title": "Control the Flow: How to Safely Compose Streaming Services into Business Processes", "summary": "Although workflow languages are widely used for composing discrete services, these are not suitable for stream based interactions. In this paper we address the problem of how to extend a conventional Web service composition language with the ability to deal with data streaming services. The paper discusses several modeling alternatives and presents a marker based semantics for safely dealing with pipelined processing in service compositions. The paper also presents application examples that illustrate the advantages of the proposed approach", "image": "/biblio-covers/jopera-scc2006.png", "date_modified": "2006-01-01T00:00:00Z", "author": { "name": "Biörn Biörnstad" } }, { "id": "biblio/2006/sigmodrec", "html_content": "", "url": "../biblio/2006/sigmodrec", "title": "Developing scientific workflows from heterogeneous services", "summary": "Scientific Workflows (SWFs) need to utilize components and applications in order to satisfy the requirements of specific workflow tasks. Technology trends in software development signify a move from component-based to service-oriented approach, therefore SWF will inevitably need appropriate tools to discover and integrate heterogeneous services. In this paper we present the SODIUM platform consisting of a set of languages and tools as well as related middleware, for the development and execution of scientific workflows composed of heterogeneous services.", "image": "/biblio-covers/jopera-sigmodrec2006.png", "date_modified": "2006-05-31T22:00:00Z", "author": { "name": "Aphrodite Tsalgatidou" } }, { "id": "biblio/2006/ijwet", "html_content": "", "url": "../biblio/2006/ijwet", "title": "Enforcing Web Services Business Protocols at Run-Time: a Process Driven Approach", "summary": "Business processes provide abstractions for modelling business protocols that define the correct interactions between two or more Web services (WS). It has been shown that it is possible to automatically derive role-specific processes from a global protocol definition and also statically verify the compliance of a local process with the corresponding global business process. In this paper, we show that a similar approach can be used at run-time. We propose to employ process-based tools to enforce that the messages exchanged between different WS comply with a given business protocol, both in terms of sequencing constraints and data flow characteristics. Our solution simplifies the implementation of WS because it helps to separate the concern of business protocol compliance from the actual service implementation. To do so, we show how to transparently add a protocol enforcement layer to the WS messaging stack. Our experimental results indicate that this imposes a minimal overhead.", "image": "/biblio-covers/jopera-ijwet2006.png", "date_modified": "2006-01-01T00:00:00Z", "author": { "name": "Biörn Biörnstad" } }, { "id": "biblio/2006/deb", "html_content": "", "url": "../biblio/2006/deb", "title": "JOpera: Autonomic Service Orchestration", "image": "/biblio-covers/jopera-debull2006.png", "date_modified": "2006-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2006/ccgrid", "html_content": "", "url": "../biblio/2006/ccgrid", "title": "Mirroring Resources or Mapping Requests: implementing WS-RF for Grid workflows", "summary": "The Web Services Resource Framework (WS-RF) and the Web Services Notification (WS-N) specifications are a crucial component of Grid infrastructures. They provide a standardized interface to stateful services so that they can be managed remotely. There are already several implementations of these specifications and initial performance studies have compared them in terms of the overhead observed by a single client. In this paper we address the problem of implementing the WS-RF and WS-N specifications for large scale systems. In particular, we discuss how to implement WS-RF and WSN as the management interfaces to a Grid workflow engine. In the paper we describe and compare two different architectures for mapping resources to processes. The first one mirrors the state of the process as a resource. The second one maps the client requests to access the state of a resource embedded into the Grid workflow engine. We include an extensive performance evaluation, comparing the resulting systems in terms of scalability when servicing a large number of concurrent clients. ", "image": "/biblio-covers/jopera-ccgrid2006.png", "date_modified": "2006-04-30T22:00:00Z", "author": { "name": "Thomas Heinis" } }, { "id": "biblio/2006/works", "html_content": "", "url": "../biblio/2006/works", "title": "Parallel Computing Patterns for Grid Workflows", "summary": "Whereas a consensus has been reached on defining the set of workflow patterns for business process modeling languages, no such patterns exists for workflows applied to scientific computing on the Grid. By looking at different kinds of parallelism, in this paper we identify a set of workflow patterns related to parallel and pipelined execution. The paper presents how these patterns can be represented in different Grid workflow languages and discusses their implications for the design of the underlying workflow management and execution infrastructure. A preliminary classification of these patterns is introduced by surveying how they are supported by several existing advanced scientific and Grid workflow languages.", "image": "/biblio-covers/jopera-works2006.png", "date_modified": "2006-05-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2006/ac", "html_content": "", "url": "../biblio/2006/ac", "title": "A Self-Configuring Service Composition Engine", "image": "/biblio-covers/jopera-acbook2006.png", "date_modified": "2006-01-01T00:00:00Z", "author": { "name": "Thomas Heinis" } }, { "id": "biblio/2005/icws", "html_content": "", "url": "../biblio/2005/icws", "title": "Autonomic Execution of Service Compositions", "summary": "An increasing amount of Web services are being implemented using process management tools and languages (BPML, BPEL, etc.). The main advantage of processes is that designers can express complex business conversations at a high level of abstraction, even reusing standardized business protocols. The downside is that the infrastructure behind the Web service becomes more complex. This is particularly critical for Web services that may be subjected to high variability in demand and suffer from unpredictable peaks of heavy load. In this paper we present a flexible architecture for process execution that has been designed to support autonomic scalability. The system runs on a cluster of computers and reacts to workload variations by altering its configuration in order to optimally use the available resources. Such changes happen automatically and without any human intervention. This feature completely removes the need for the manual monitoring and reconfiguration of the system, which in practice is a difficult and time-consuming operation. In the paper we describe the architecture of the system and present an extensive performance evaluation of its autonomic capabilities.", "image": "/biblio-covers/jopera-icws2005.png", "date_modified": "2005-06-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2005/icac", "html_content": "", "url": "../biblio/2005/icac", "title": "Design and Evaluation of an Autonomic Workflow Engine", "summary": "In this paper we present the design and evaluate the performance of an autonomic workflow execution engine. Although there exist many distributed workflow engines, in practice, it remains a difficult problem to deploy such systems in an optimal configuration. Furthermore, when facing an unpredictable workload with high variability, manual reconfiguration is not an option. Thanks to its autonomic controller, the engine features self-configuration, self-tuning and self-healing properties. The engine runs on a cluster of computers using a tuple space to coordinate its various components. Its autonomic controller monitors its performance and responds to workload variations by altering the configuration. In case failures occur, the controller can recover the workflow execution state from persistent storage and migrate it to a different node of the cluster. Such interventions are carried out without any human supervision. As part of the results of our performance evaluation, we compare different autonomic control strategies and discuss how they can automatically tune the system", "image": "/biblio-covers/jopera-icac2005.png", "date_modified": "2005-05-31T22:00:00Z", "author": { "name": "Thomas Heinis" } }, { "id": "biblio/2005/sc", "html_content": "", "url": "../biblio/2005/sc", "title": "Flexible Binding for Reusable Composition of Web Services", "summary": "In addition to publishing composite services as reusable services, compositions can also be reused by applying them to orchestrate different component services. To do so, it is important to describe compositions using flexible bindings, which define only the minimal constraints on the syntax and semantics of the services to be composed. This way, the choice of which service to invoke can be delayed to later stages in the life cycle of the composition. In the context of Web service composition, we refine the concept of binding beyond the basic distinction of static and dynamic binding. Bindings can be evaluated during the design, the compilation, the deployment, the beginning of the execution of a composition, or just before the actual service invocation takes place. Considering the current limited support of dynamic binding in the BPEL service composition language, we show how we addressed the problem in JOpera, where modeling bindings does not require a specific language construct as it can be considered a special application of reflection.", "image": "/biblio-covers/jopera-sc2005.png", "date_modified": "2005-03-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2005/vlhcc", "html_content": "", "url": "../biblio/2005/vlhcc", "title": "JOpera: an Agile Environment for Web Service Composition with Visual Unit Testing and Refactoring", "summary": "Agile methodologies employ light-weight development practices emphasizing a test-driven approach to the development of software systems. Modern agile development environments support this approach by providing tools that automate most of the work required to effectively deal with change, including unit testing and different forms of refactoring. In this paper we discuss how to apply such techniques within the JOpera Visual Composition Language. More precisely, we show how we used the visual language to implement a regression testing framework for compositions written in the language itself and how we introduced support in the visual environment for refactorings such as renaming, synchronization of service interface changes, and extraction/inlining across different levels of nesting. This is done in the context of the Web service composition tools provided with the JOpera for Eclipse research platform.", "image": "/biblio-covers/jopera-vlhcc2005.png", "date_modified": "2005-08-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2005/jvlc", "html_content": "", "url": "../biblio/2005/jvlc", "title": "The JOpera visual composition language", "summary": "Composing Web services into a coherent application can be a tedious and error-prone task when using traditional textual scripting languages or emerging XML-based approaches. As an alternative, complex interactions patterns and data exchanges between different Web services can be effectively modeled using a visual language. In this paper, we discuss the requirements of such an application scenario and we fully describe the JOpera Visual Composition Language. An extensive set of visual editing tools, a compiler and a debugger for the language have been implemented as part of the JOpera system with the goal of providing a true visual environment for Web service composition with usability features emphasizing rapid development and visual scalability. ", "image": "/biblio-covers/jopera-jvlc2005.png", "date_modified": "2005-01-31T23:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2005/escience", "html_content": "", "url": "../biblio/2005/escience", "title": "Publishing Persistent Grid Computations as WS Resources", "summary": "Grid services can be composed into processes, providing a high level definition of the computations involved in terms of their data exchanges and control flow dependencies. We show how processes themselves can be efficiently published as Grid services by mapping the persistent state of the process executions to standard compliant interfaces as defined by the Web Services Resource Framework (WS-RF). Mapping processes to resources is a fundamental step to enable recursive Grid service composition, where composite Grid services are themselves published as services. This gives processes a standardized and wellunderstood interface that enables their management, monitoring, steering and adaptation. Additionally it eases their reusability and simplifies integration into existing Grid applications and portals. In order to determine the mapping's overhead, we include the results of a comprehensive performance evaluation.", "image": "/biblio-covers/jopera-escience2005.png", "date_modified": "2005-11-30T23:00:00Z", "author": { "name": "Thomas Heinis" } }, { "id": "biblio/2004/phd", "html_content": "", "url": "../biblio/2004/phd", "title": "A Flexible System for Visual Service Composition", "summary": "This dissertation brings together ideas of different research areas. First of all, we propose the application of visual languages to service composition. In order to connect basic services of various kinds into a larger system, their interactions along the time dimension are defined with the JOpera Visual Composition Language. As opposed to the textual or XML-based syntax of existing approaches, our language features a very simple graphical notation. This visual syntax is used to specify the data flow and control flow graphs linking the various service invocations. This way, it becomes possible to rapidly build distributed applications out of a set of reusable services by literally drawing the interactions between them. To achieve this, we present how usability features such as automatic, incremental graph layout and visual scalability features such as multiple views have been driving the design of JOpera's visual service composition environment. To provide support for realistic application scenarios, we have also included recursion, iteration and reflection constructs with minimal changes to the syntax of the visual language. Supported by the JOpera system, our visual language for service composition has been applied to many scenarios, as documented by the examples shown throughout the dissertation. Underneath the visual syntax, our approach to modeling service composition is based on the concept of process. In this dissertation we borrow the notion of business process so that it can be extended to model service oriented architectures. Thus, the structure of a process defines the partial order of invocation of its services, the data exchanges between them and the necessary failure handling behavior. In this context, an important contribution of this dissertation is the idea that a composition language should be orthogonal with respect to the types of components that are employed. More precisely, in our approach, composition is defined at the level of service interfaces. Therefore, a process is completely independent from the mechanisms and protocols used to access the implementation of its services. In other words, we introduce a composition language which is not limited to describing how components of a specific type (e.g., Web services) should be composed. Instead, in our open component meta-model, we generalize the notion of service by abstracting common features among a large set of different component types. This abstraction has several important implications. By supporting a large and open set of types of services, the composition language is simplified because many constructs (e.g., modeling synchronous or asynchronous service invocation) can be shifted from the composition language to the component meta-model. Also, the service composer is free to choose the most appropriate mechanism to access the functionality of an existing service. Thus, the runtime overhead of a service invocation can be minimized as it becomes possible to choose the most effcient access mechanism. This optimization regarding the service access mechanism would not make much of a difference regarding the overall system's performance if the execution of the visual language would incur in a high overhead, as typically process-based languages are executed by an interpreter. On the contrary, in this dissertation we propose to compile the visual specification of a process into executable code. One of the challenges of doing so is that the resulting code should still support the concurrent execution of multiple process instances. The choice of applying compilation to the execution of processes brings the following benefits. In addition to the potential for providing better performance through the optimization of the generated code, compiling processes also helps to simplify the design of the corresponding runtime system. As opposed to having a full-blown process interpreter, it is enough to design and build a flexible container of compiled processes. Following this approach, in the last part of the dissertation we present the design of a flexible architecture for a process support system. Flexibility is an important aspect of our design which, according to our experimental results, does not contradict the goal of building an efficient system. First, flexibility enables JOpera to support heterogeneous types of services. To do so, plug-ins are used to map the invocation of a service to the corresponding protocol in the most effcient manner. Second, the flexible architecture of JOpera's kernel can be deployed in a variety of configurations. This way, costly features such as reliable process execution can be added only if they are truly needed. Likewise, the system shows good scalability when deployed in a cluster-based configuration, as large workloads are shared among multiple cluster nodes. Thanks to a wise choice of architectural abstractions, the code generated by the compiler is kept independent of the actual configuration of the kernel into which it is loaded. Third, flexibility is also a fundamental property for an autonomic system, where the optimal configuration is determined automatically at runtime.", "image": "/biblio-covers/jopera-diss-cesare.pautasso.png", "date_modified": "2004-01-01T00:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2004/vldb-tes", "html_content": "", "url": "../biblio/2004/vldb-tes", "title": "From Web Service Composition to Megaprogramming", "summary": "With the emergence of Web service technologies, it has become possible to use high level megaprogramming models and visual tools to easily build distributed systems using Web services as reusable components. However, when attempting to apply the Web service composition paradigm in practical settings, some limitations become apparent. First of all, all kinds of existing \"legacy\" components must be wrapped as Web services, incurring in additional development, maintenance, and unnecessary runtime overheads. Second, current implementations of Web service protocols guarantee interoperability at high runtime costs, which justifies the composition of only coarse-grained Web services. To address these limitations and support the composition of also fine-grained services, in this paper we generalize the notion of service by introducing an open service meta-model. This offers freedom of choice between different types of services, which also include, but are not limited to, Web services. As a consequence, we argue that service composition - defined at the level of service interfaces - should be orthogonal from the mechanisms and the protocols which are used to access the actual service implementations.", "image": "/biblio-covers/jopera-vldbtes2004.png", "date_modified": "2004-07-31T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2004/ijec", "html_content": "", "url": "../biblio/2004/ijec", "title": "JOpera: a Toolkit for Efficient Visual Composition of Web Services", "summary": "Web services are attracting attention because of their ability to provide standard interfaces to heterogeneous distributed services. Standard interfaces make it possible to compose more complex services out of basic ones. This paper tackles the problem of visual service composition and the efficient and scalable execution of the resulting composite services. The effort revolves around the JOpera system, which combines a visual programming environment for Web services with a flexible execution engine that interacts with Web services through the simple object access protocol (SOAP), described with Web services language description (WSDL) and registered with a universal description discovery and integration (UDDI) registry. The paper explains the syntax and implementation of the JOpera Visual Composition Language (JVCL) and its ability to provide different quality of service (QoS) levels in the execution of composite services. ", "image": "/biblio-covers/jopera-ijec2004.png", "date_modified": "NaN-NaN-NaNTNaN:NaN:NaNZ", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2004/ercim", "html_content": "", "url": "../biblio/2004/ercim", "title": "JOpera: Visual Composition of Grid Services", "summary": "The recent shift to service-based Grids enables the use of service composition tools for rapidly building and efficiently running distributed computations. At ETH Zurich, we have developed JOpera, a visual composition language and a set of integrated software development tools for composing Grid services. The system can be freely downloaded and has been successfully tested with data-intensive bioinformatics applications as well as large-scale, Monte-Carlo network simulations.", "image": "/biblio-covers/jopera-ercim2004.png", "date_modified": "2004-09-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2003/ccgrid", "html_content": "", "url": "../biblio/2003/ccgrid", "title": "Programming for dependability in a service-based grid", "summary": "Service-based Grid infrastructures emphasize service composition rather than sharing of low level resources. The idea is to build Grid applications out of computational services provided by the different sites of the Grid. Recent developments in the area of Web services have strengthened this idea by standardizing procedures like service description, publication and invocation. What is still missing is the infrastructure necessary to support the complete life cycle of applications running on service based Grids, i.e., suitable programming paradigms, execution infrastructure, and the ability to monitor and control such computations. Moreover, once computations are made of composable services, dependability becomes a key issue that needs to be addressed by the infrastructure as it cannot be addressed separately by each individual service. To address these concerns, we have developed the BioOpera Grid computing platform. BioOpera is a process support system for dependable cluster computing that has been extended with additional functionality to provide adequate support for service-based Grids. In this paper we describe how BioOpera can be used to develop, execute, and administer highly dependable computations over service-based Grids.", "image": "/biblio-covers/bioopera-ccgrid2003.png", "date_modified": "2003-04-30T22:00:00Z", "author": { "name": "Win Bausch" } }, { "id": "biblio/2003/hcc", "html_content": "", "url": "../biblio/2003/hcc", "title": "Visual composition of Web services", "summary": "Composing Web services into a coherent application can be a tedious and error prone task when using traditional textual scripting languages. As an alternative, complex interactions patterns and data exchanges between different Web services can be effectively modeled using a visual language. In this paper we discuss the requirements of such an application scenario and we present the design of the BioOpera Flow Language. This visual composition language has been fully implemented in a development environment for Web service composition with usability features emphasizing rapid development and visual scalability.", "image": "/biblio-covers/jopera-hcc2003.png", "date_modified": "2003-09-30T22:00:00Z", "author": { "name": "Cesare Pautasso" } }, { "id": "biblio/2002/cluster", "html_content": "", "url": "../biblio/2002/cluster", "title": "BioOpera: cluster-aware computing", "summary": "In this paper we present BioOpera, an extensible process support system for cluster-aware computing. It features an intuitive way to specify computations, as well as improved support for running them over a cluster providing monitoring, persistence, fault tolerance and interaction capabilities without sacrificing efficiency and scalability.", "image": "/biblio-covers/bioopera-cluster2002.png", "date_modified": "2002-08-31T22:00:00Z", "author": { "name": "Win Bausch" } }, { "id": "biblio/2001/icde", "html_content": "", "url": "../biblio/2001/icde", "title": "Dependable computing in virtual laboratories", "summary": "Many scientific disciplines are shifting from in vitro to in silico research as more physical processes and natural phenomena are examined in a computer (in silico) instead of being observed (in vitro). In many of these virtual laboratories, the computations involved are very complex and long lived. Currently, users are required to manually handle almost all aspects of such computations, including their dependability. Not surprisingly, this is a major bottleneck and a significant source of inefficiencies. To address this issue, we have developed BioOpera, an extensible process support management system for virtual laboratories. The authors briefly discuss the architecture and functionality of BioOpera and show how it can be used to efficiently manage long lived computations", "image": "/biblio-covers/bioopera-icde2001.png", "date_modified": "2001-03-31T22:00:00Z", "author": { "name": "Gustavo Alonso" } } ] }