Negotiation in a multiagent system is a topic of active interest for enabling the allocation of scarce resources among autonomous agents. This paper presents a discussion of the research on negotiation criteria, which puts in context the contributions to resource allocation from the fields of economics, mathematics, and multiagent systems. We group the criteria based on how they relate to each other as well as their historical origin. In addition, we present three new criteria: verifiability, dimensionality, and topology. The criteria are organized into five categories. The allocation category contains criteria concerning fairness and envy-freeness with respect to how resources are allocated to agents. The protocol category covers criteria for stability, strategy-proofness, and communication costs. The procedure category includes criteria about the complexity of allocation procedures. The resource category has criteria for the properties that various resources can take and how they affect allocation. The paper concludes with a discussion of the criteria for agent utility functions. The overall objectives of this paper are (1) to create a starting point for protocol engineering by future negotiation designers and (2) to enumerate the criteria and their measures that enable negotiation and allocation mechanisms to be compared objectively.

Nowadays, Multi-Agent Systems (MAS) are broadening their applications to open environments, where heterogeneous agents could enter into the system, form agents’ organizations and interact. The high dynamism of open MAS gives rise to potential conflicts between agents and thus, to a need for a mechanism to reach agreements. Argumentation is a natural way of harmonizing conflicts of opinion that has been applied to many disciplines, such as Case-Based Reasoning (CBR) and MAS. Some approaches that apply CBR to manage argumentation in MAS have been proposed in the literature. These improve agents’ argumentation skills by allowing them to reason and learn from experiences. In this paper, we have reviewed these approaches and identified the current contributions of the CBR methodology in this area. As a result of this work, we have proposed several open issues that must be taken into consideration to develop a CBR framework that provides the agents of an open MAS with arguing and learning capabilities.

The automatic assessment of students’ free-text answers has recently received much attention, due to the necessity of exploring and taking advantage of new and more complex computer-based assessment methods. In this paper, a review of the state-of-art of the field is presented, focusing on the techniques that underpin these systems and their evaluation metrics. Although there is still a long way to go so as to reach the ideal system, the fact that the existing systems are already being used commercially and as a second opinion in exams such as GMAT proves the uptake of this field.

Recently, the number of ontology matching techniques and systems has increased significantly. This makes the issue of their evaluation and comparison more severe. One of the challenges of the ontology matching evaluation is in building large-scale evaluation datasets. In fact, the number of possible correspondences between two ontologies grows quadratically with respect to the numbers of entities in these ontologies. This often makes the manual construction of the evaluation datasets demanding to the point of being infeasible for large-scale matching tasks. In this paper, we present an ontology matching evaluation dataset composed of thousands of matching tasks, called TaxME2. It was built semi-automatically out of the Google, Yahoo, and Looksmart web directories. We evaluated TaxME2 by exploiting the results of almost two-dozen of state-of-the-art ontology matching systems. The experiments indicate that the dataset possesses the desired key properties, namely it is error-free, incremental, discriminative, monotonic, and hard for the state-of-the-art ontology matching systems.

In this paper, we discuss the challenges posed by the NEUROWEB project, as a case study of ontological modeling at a knowledge interface between neurovascular medicine and genomics. The aim of the project is the development of a support system for association studies. We identify the notion of clinical phenotypes, that is, the pathological condition of a patient, as the central construct of the knowledge model. Clinical phenotypes are assessed through the diagnostic activity, performed by clinical experts operating within communities of practice; the different communities operate according to specific procedures, but they also conform to the minimal requirements of international guidelines, displayed by the adoption of a common standard for the patient classification. We develop a central model for the clinical phenotypes, able to reconcile the different methodologies into a common classificatory system. To bridge neurovascular medicine and genomics, we identify the general theory of biological function as the common ground between the two disciplines; therefore, we decompose the clinical phenotypes into elementary phenotypes with a homogeneous physiological background, and we connect them to the biological processes, acting as the elementary units of the genomic world.

Modelling is one of the most frequent tasks in the area of information systems (ISs), with models such as schemata, ontologies, patterns and architectures forming the bases for their creation. Very often, however, the difference between these types of models is not clear and causes confusion and erratic use of the terms. The aim of this paper is to clarify the concept of model through a study of some of the more common ones used in ISs. This proposal is presented through an ontology, where we show how we conceptualize models according to their role in the development of an IS: the model understood as the representation of a domain or as a reality serving as an example.

Ripple Down Rules (RDR) were developed in answer to the problem of maintaining medium to large rule-based knowledge systems. Traditional approaches to knowledge-based systems gave little thought to maintenance as it was expected that extensive upfront domain analysis involving a highly trained specialist, the knowledge engineer, and the time-poor domain expert would produce a complete model capturing what was in the expert’s head. The ever-changing, contextual and embrained nature of knowledge were not a part of the philosophy upon which they were based. RDR was a paradigm shift, which made knowledge acquisition and maintenance one and the same thing by incrementally acquiring knowledge as domain experts directly interacted with naturally occurring cases in their domain. Cases played an integral part of the acquisition process by motivating the capture of new knowledge, framing the context in which new knowledge would apply and ensuring that previously correctly classified cases remained so by requiring that the classification of the new case distinguish it from the system’s classification and be justified by features of the new case. RDR has moved beyond its first representation which handled single classification tasks within the domain of pathology to support multiple conclusions across a wide range of domains such as help-desk support, email classification and RoboCup and problem types including configuration, simulation, planning and natural language processing. This paper reviews the history of RDR research over the past two decades with a view to its future.

This paper will summarize and analyze the work of the different research groups who have recently made significant contributions in using Reinforcement Learning techniques to learn dialogue strategies for Spoken Dialogue Systems (SDSs). This use of stochastic planning and learning has become an important research area in the past 10 years, since it promises automatic data-driven optimization of the behavior of SDSs that were previously hand-coded by expert developers. We survey the most important developments in the field, compare and contrast the different approaches, and describe current open problems.

Ontologies are frequently used in the context of software and technology engineering. These can be grouped into two main categories, depending on whether they are used to describe the knowledge of a domain (domain ontologies) or whether they are used as software artifacts in software development processes. This paper presents some experiences and lessons learnt from the effective use of an ontology for Software Measurement, called software measurement ontology (SMO). The SMO was developed some years ago as a result of a thorough analysis of the software measurement domain. Its use as a domain ontology is presented first, a description of how the SMO can serve as a conceptual basis for comparing international standards related to software measurement. Second, the paper describes several examples of the applications of SMO as a software artifact. In particular, we show how the SMO can be instantiated to define a data quality model for Web portals, and also how it can be used to define a Domain-Specific Language (DSL) for measuring software entities. These examples show the significant role that ontologies can play as software artifacts in the realm of model-driven engineering and domain-specific modeling.

In the field of software architecture, there has been a paradigm shift from describing structural information, such as components and connectors, to documenting architectural knowledge (AK), such as design decisions and rationale. To this end, a series of industrial and academic domain models have been proposed for defining the concepts and their relationships in the field of AK. To a large extent the merit of this new paradigm is to share and reuse AK across organizations, especially in geographically distributed settings. However, the employment of different AK domain models by different parties makes effective AK sharing challenging, as it needs to be mapped from one domain model to another. In this paper, we investigate two different approaches for sharing AK, based on either direct or indirect mapping between different AK domain models. We compare the cost and quality of these two approaches, with respect to the processing of large amounts of AK instances. To predict the quality and costs of this processing in advance, a prediction model is proposed and validated with a concrete AK sharing case. Based on the comparison results, stakeholders involved with AK sharing can select an appropriate approach by trading off quality and cost in their own context.

This paper develops an ontological basis for evaluating software design methods, based on the situated function–behaviour–structure framework. This framework accounts for the situatedness of designing, viewing it as a dynamic activity driven by interactions between designers and the artefacts being designed. On the basis of this framework, we derive a general evaluation schema that we apply to five software design methods. The ideas presented in this work contribute to a better understanding of design methods, and uncover opportunities for method integration and development.

In this paper, we present an approach to solve the drawbacks of manual composition of software components. Our approach is applied within the jcolibri framework for building case-based reasoning (CBR) applications. We propose a system design process based on reusing templates obtained from previously designed CBR systems. Templates store the control flow of the CBR applications and include semantic annotations conceptualizing its behavior and expertise. We use CBR ontology to formalize syntactical, semantical and pragmatical aspects of the reusable components of the framework. The ontology vocabulary facilitates an annotation process of the components and allows to reason about their composition, facilitating the semi-automatic configuration of complex systems from their composing pieces.

This paper presents a conceptual and computational framework for supporting the development of knowledge management systems based on ontology design and implementation. This framework supports enterprises involved in the design and manufacturing of complex mechanical products: in particular, we focus our attention on a network of small/medium Italian enterprises that collaborates in the production of a supermotard bike called Terra Modena 198. Starting from some theoretical considerations about the role of ontologies in engineering design, this paper reflects on the difficulties that arise when knowledge is distributed, and misunderstanding and communication problems among partners could easily lead to errors in the final product.

Component-based development (CBD) has become an important emerging topic in the software engineering field. It promises long-sought-after benefits such as increased software reuse, reduced development time to market and, hence, reduced software production cost. Despite the huge potential, the lack of reasoning support and development environment of component modeling and verification may hinder its development. Methods and tools that can support component model analysis are highly appreciated by industry. Such a tool support should be fully automated as well as efficient. At the same time, the reasoning tool should scale up well as it may need to handle hundreds or even thousands of components that a modern software system may have. Furthermore, a distributed environment that can effectively manage and compose components is also desirable. In this paper, we present an approach to the modeling and verification of a newly proposed component model using Semantic Web languages and their reasoning tools. We use the Web Ontology Language and the Semantic Web Rule Language to precisely capture the inter-relationships and constraints among the entities in a component model. Semantic Web reasoning tools are deployed to perform automated analysis support of the component models. Moreover, we also proposed a service-oriented architecture (SOA)-based semantic web environment for CBD. The adoption of Semantic Web services and SOA make our component environment more reusable, scalable, dynamic and adaptive.