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.

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.

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.

Ontology has been recently proposed as an appropriate formalism to model software project management antipatterns, in order to encode antipatterns in a computer understandable form and introduce antipatterns to the Semantic Web. However, given two antipattern ontologies, the same entity can be described using different terminology. Therefore, the detection of similar antipattern ontologies is a difficult task. In this paper, we introduce a three-layered antipattern semantic social network, which involves the social network, the antipattern ontology network and the concept network. Social Network Analysis (SNA) techniques can be used to assist software project managers in finding similar antipattern ontologies. For this purpose, SNA measures are extracted from one layer of the semantic social network to another and this knowledge is used to infer new links between antipattern ontologies. The level of uncertainty associated with each new link is represented using Bayesian Networks (BNs). Furthermore, BNs address the issue of quantifying the uncertainty of the data collected regarding antipattern ontologies for the purposes of the conducted analysis. Finally, BNs are used to augment SNA by taking into account meta-information in their calculations. Hence, other knowledge not included in the social network can be used in order to search the social network for further inference. The benefits of using an antipattern semantic social network are illustrated using an example community of software project management antipattern ontologies.

Engineering knowledge is a specific kind of knowledge that is oriented to the production of particular classes of artifacts, is typically related to disciplined design methods, and takes place in tool-intensive contexts. As a consequence, representing engineering knowledge requires the elaboration of complex models that combine functional and structural representations of the resulting artifacts with process and methodological knowledge. The different categories used in the engineering domain vary in their status and in the way they should be manipulated when building applications that support engineering processes. These categories include artifacts, activities, methods and models. This paper surveys existing models of engineering knowledge and discusses an upper ontology that abstracts the categories that crosscut different engineering domains. Such an upper model can be reused for particular engineering disciplines. The process of creating such elaborations is reported on the particular case study of Software Engineering as a concrete application example.