Aspect-Oriented Programming

Aspect-oriented programming is a promising idea that can improve the quality of software by reduce the problem of code tangling and improving the separation of concerns. At ECOOP'97, the first AOP workshop brought together a number of researchers interested in aspect-orientation. At ECOOP'98, during the second AOP workshop the participants reported on progress in some research topics and raised more issues that were further discussed. \ud \ud This year, the ideas and concepts of AOP have been spread and adopted more widely, and, accordingly, the workshop received many submissions covering areas from design and application of aspects to design and implementation of aspect languages

BIM semantic-enrichment for built heritage representation

In the built heritage context, BIM has shown difficulties in representing and managing the large and complex knowledge related to non-geometrical aspects of the heritage. Within this scope, this paper focuses on a domain-specific semantic-enrichment of BIM methodology, aimed at fulfilling semantic representation requirements of built heritage through Semantic Web technologies. To develop this semantic-enriched BIM approach, this research relies on the integration of a BIM environment with a knowledge base created through information ontologies. The result is knowledge base system - and a prototypal platform - that enhances semantic representation capabilities of BIM application to architectural heritage processes. It solves the issue of knowledge formalization in cultural heritage informative models, favouring a deeper comprehension and interpretation of all the building aspects. Its open structure allows future research to customize, scale and adapt the knowledge base different typologies of artefacts and heritage activities

A semantic web approach for built heritage representation

In a built heritage process, meant as a structured system of activities aimed at the investigation, preservation, and management of architectural heritage, any task accomplished by the several actors involved in it is deeply influenced by the way the knowledge is represented and shared. In the current heritage practice, knowledge representation and management have shown several limitations due to the difficulty of dealing with large amount of extremely heterogeneous data. On this basis, this research aims at extending semantic web approaches and technologies to architectural heritage knowledge management in order to provide an integrated and multidisciplinary representation of the artifact and of the knowledge necessary to support any decision or any intervention and management activity. To this purpose, an ontology-based system, representing the knowledge related to the artifact and its contexts, has been developed through the formalization of domain-specific entities and relationships between them

From types to type requirements: Genericity for model-driven engineering

The final publication is available at Springer via http://dx.doi.org/10.1007/s10270-011-0221-0Model-driven engineering (MDE) is a software engineering paradigm that proposes an active use of models during the development process. This paradigm is inherently type-centric, in the sense that models and their manipulation are defined over the types of specific meta-models. This fact hinders the reuse of existing MDE artefacts with other meta-models in new contexts, even if all these meta-models share common characteristics. To increase the reuse opportunities of MDE artefacts, we propose a paradigm shift from type-centric to requirement-centric specifications by bringing genericity into models, meta-models and model management operations. For this purpose, we introduce so-called concepts gathering structural and behavioural requirements for models and meta-models. In this way, model management operations are defined over concepts, enabling the application of the operations to any meta-model satisfying the requirements imposed by the concept. Model templates rely on concepts to define suitable interfaces, hence enabling the definition of reusable model components. Finally, similar to mixin layers, templates can be defined at the meta-model level as well, to define languages in a modular way, as well as layers of functionality to be plugged-in into other meta-models. These ideas have been implemented in MetaDepth, a multi-level meta-modelling tool that integrates action languages from the Epsilon family for model management and code generation.This work has been sponsored by the Spanish Ministry of Science and Innovation with projects METEORIC (TIN2008-02081) and Go Lite (TIN2011-24139), and by the R&D program of the Community of Madrid with project “e-Madrid” (S2009/TIC-1650)

Traceability for Model Driven, Software Product Line Engineering

Traceability is an important challenge for software organizations. This is true for traditional software development and even more so in new approaches that introduce more variety of artefacts such as Model Driven development or Software Product Lines. In this paper we look at some aspect of the interaction of Traceability, Model Driven development and Software Product Line

Multi-Level Modeling of Quotation Families Morphogenesis

This paper investigates cultural dynamics in social media by examining the proliferation and diversification of clearly-cut pieces of content: quoted texts. In line with the pioneering work of Leskovec et al. and Simmons et al. on memes dynamics we investigate in deep the transformations that quotations published online undergo during their diffusion. We deliberately put aside the structure of the social network as well as the dynamical patterns pertaining to the diffusion process to focus on the way quotations are changed, how often they are modified and how these changes shape more or less diverse families and sub-families of quotations. Following a biological metaphor, we try to understand in which way mutations can transform quotations at different scales and how mutation rates depend on various properties of the quotations.Comment: Published in the Proceedings of the ASE/IEEE 4th Intl. Conf. on Social Computing "SocialCom 2012", Sep. 3-5, 2012, Amsterdam, N

Modeling Business Process Variability

This master thesis presents research findings on business process variability modeling. Its main goal is to analyze inherent problems of business process variability and solve them simply, innovatively and effectively. To achieve this goal, process variability is defined by analyzing scientific literature, its main problems identified and is illustrated using a healthcare running example: process variability is classified into process variability within the domain space and over time. These two forms of process variability respectively lead to process variability modeling and process model evolution problems. After defining the main problems inherent to process variability, the focus of this research project is defined: solving process variability modeling problems. First current business process modeling languages are evaluated to assess the effectiveness of their respective modeling concepts when modeling process variability, using a newly created set of evaluation criteria and the healthcare running example. The following business process modeling languages are evaluated: Event driven process chains (EPC), the Business Process Modeling Notation (BPMN) and Configurable EPC (C-EPC). Business process variability modeling and Software product line engineering have similar problems. Therefore the variability modeling concepts developed by software product line engineering are analyzed. Feature diagrams and software configuration management are the main variability management concepts provided by software product line engineering. To apply these variability management concepts to model process variability meant combining them with existing business modeling languages. Riebisch feature diagrams are combined with C-EPC to form Feature-EPC. Applying software configuration management, meant merging Change Oriented Versioning with basic EPC to create COV-EPC, and merging the Proteus Configuration Language with basic EPC to design PCL-EPC. Finally these newly created business process modeling languages are also evaluated using the newly designed evaluation criteria and the healthcare running example. EPC or BPMN are not suited to model business process variability within the domain space. C-EPC provide explicit means to model business process variability, however the process models tend to get big very fast. Furthermore the syntax, the contextual constraints and the semantics of the configuration requirements and guidelines used to configure the C-EPC process models are unclear. Feature-EPC improve C-EPC with domain modeling capability and clearly defined configuration rules: their syntax, contextual constraints and semantics have been clearly defined using a context free grammar in Backus-Naur form. Furthermore, consistent combinations of features and configuration rules are ensured using respectively constraints and a conflict resolution algorithm. However, Feature-EPC and C-EPC suffer from the same weakness: large configurable process models. In COV-EPC and PCL-EPC the problem of large configurable process models is solved. COV-EPC ensures consistent combinations of options and configuration rules using respectively validities and a conflict resolution algorithm. PCL-EPC guarantees consistent combinations of process fragments by means of a PCL specification

Patent Landscape of Influenza A Virus Prophylactic Vaccines and Related Technologies

Executive Summary: This report focuses on patent landscape analysis of technologies related to prophylactic vaccines targeting pandemic strains of influenza. These technologies include methods of formulating vaccine, methods of producing of viruses or viral subunits, the composition of complete vaccines, and other technologies that have the potential to aid in a global response to this pathogen. The purpose of this patent landscape study was to search, identify, and categorize patent documents that are relevant to the development of vaccines that can efficiently promote the development of protective immunity against pandemic influenza virus strains. The search strategy used keywords which the team felt would be general enough to capture (or “recall”) the majority of patent documents which were directed toward vaccines against influenza A virus. After extensive searching of patent literature databases, approximately 33,500 publications were identified and collapsed to about 3,800 INPADOC families. Relevant documents, almost half of the total, were then identified and sorted into the major categories of vaccine compositions (about 570 families), technologies which support the development of vaccines (about 750 families), and general platform technologies that could be useful but are not specific to the problems presented by pandemic influenza strains (about 560 families). The first two categories, vaccines and supporting technologies, were further divided into particular subcategories to allow an interested reader to rapidly select documents relevant to the particular technology in which he or she is focused. This sorting process increased the precision of the result set. The two major categories (vaccines and supporting technologies) were subjected to a range of analytics in order to extract as much information as possible from the dataset. First, patent landscape maps were generated to assess the accuracy of the sorting procedure and to reveal the relationships between the various technologies that are involved in creating an effective vaccine. Then, filings trends are analyzed for the datasets. The country of origin for the technologies was determined, and the range of distribution to other jurisdictions was assessed. Filings were also analyzed by year, by assignee, and by inventor. Finally, the various patent classification systems were mapped to find which particular classes tend to hold influenza vaccine-related technologies. Besides the keywords developed during the searches and the landscape map generation, the classifications represent an alternate way for further researchers to identify emerging influenza technologies. The analysis included creation of a map of keywords, as shown above, describing the relationship of the various technologies involved in the development of prophylactic influenza A vaccines. The map has regions corresponding to live attenuated virus vaccines, subunit vaccines composed of split viruses or isolated viral polypeptides, and plasmids used in DNA vaccines. Important technologies listed on the map include the use of reverse genetics to create reassortant viruses, the growth of viruses in modified cell lines as opposed to the traditional methods using eggs, the production of recombinant viral antigens in various host cells, and the use of genetically-modified plants to produce virus-like particles. Another major finding was that the number of patent documents related to influenza being published has been steadily increasing in the last decade, as shown in the figure below. Until the mid-1990s, there were only a few influenza patent documents being published each year. The number of publications increased noticeably when TRIPS took effect, resulting in publication of patent applications. However, since 2006 the number of vaccine publications has exploded. In each of 2011 and 2012, about 100 references disclosing influenza vaccine technologies were published. Thus, interest in developing new and more efficacious influenza vaccines has been growing in recent years. This interest is probably being driven by recent influenza outbreaks, such as the H5N1 (bird flu) epidemic that began in the late 1990s and the 2009 H1N1 (swine flu) pandemic. The origins of the vaccine-related inventions were also analyzed. The team determined the country in which the priority application was filed, which was taken as an indication of the country where the invention was made or where the inventors intended to practice the invention. By far, most of the relevant families originated with patent applications filed in the United States. Other prominent priority countries were the China and United Kingdom, followed by Japan, Russia, and South Korea. France was a significant priority country only for supporting technologies, not for vaccines. Top assignees for these families were mostly large pharmaceutical companies, with the majority of patent families coming from Novartis, followed by GlaxoSmithKline, Pfizer, U.S. Merck (Merck, Sharpe, & Dohme), Sanofi, and AstraZeneca. Governmental and nonprofit institutes in China, Japan, Russia, South Korea and the United States also are contributing heavily to influenza vaccine research. Lastly, the jurisdictions were inventors have sought protection for their vaccine technologies were determined, and the number of patent families filing in a given country is plotted on the world map shown on page seven. The United States, Canada, Australia, Japan, South Korea and China have the highest level of filings, followed by Germany, Brazil, India, Mexico and New Zealand. However, although there are a significant number of filings in Brazil, the remainder of Central and South America has only sparse filings. Of concern, with the exception of South Africa, few other African nations have a significant number of filings. In summary, the goal of this report is to provide a knowledge resource for making informed policy decisions and for creating strategic plans concerning the assembly of efficacious vaccines against a rapidly-spreading, highly virulent influenza strain. The team has defined the current state of the art of technologies involved in the manufacture of influenza vaccines, and the important assignees, inventors, and countries have been identified. This document should reveal both the strengths and weaknesses of the current level of preparedness for responding to an emerging pandemic influenza strain. The effects of H5N1 and H1N1 epidemics have been felt across the globe in the last decade, and future epidemics are very probable in the near future, so preparations are necessary to meet this global health threat