Overview of methodologies for building ontologies

A few research groups are now proposing a series of steps and methodologies for developing ontologies. However, mainly due to the fact that Ontological Engineering is still a relatively immature discipline, each work group employs its own methodology. Our goal is to present the most representative methodologies used in ontology development and to perform an analysis of such methodologies against the same framework of reference. So, the goal of this paper is not to provide new insights about methodologies, but to put it all in one place and help people to select which methodology to use

Narratives of an outsourced information systems failure in a small enterprise

In this study we investigate a case of an outsourced information systems (IS) failure (OISF) within the collaborative partnership among asymmetric partners. A small and medium-sized enterprise (SME) is dealing with an independent software vendor (ISV) conducting a project of implementing an IS that fails. We used a narrative research methodology for our enquiry. In the construction of our narrative we followed the OISF framework as a theoretical touchstone. As a major conclusion we found that asymmetric collaborations with partners with inadequate managerial and technical IT capabilities are extremely prone to OISF’s. We showed that an outcome-based and fixed price contract is not an adequate instrument to conduct such a partnership and to avoid a failure

Narratives of an outsourced information systems failure in a small enterprise

In this study we investigate a case of an outsourced information systems (IS) failure (OISF) within the collaborative partnership among asymmetric partners. A small and medium-sized enterprise (SME) is dealing with an independent software vendor (ISV) conducting a project of implementing an IS that fails. We used a narrative research methodology for our enquiry. In the construction of our narrative we followed the OISF framework as a theoretical touchstone. As a major conclusion we found that asymmetric collaborations with partners with inadequate managerial and technical IT capabilities are extremely prone to OISF’s. We showed that an outcome-based and fixed price contract is not an adequate instrument to conduct such a partnership and to avoid a failure

An overview of decision table literature 1982-1995.

This report gives an overview of the literature on decision tables over the past 15 years. As much as possible, for each reference, an author supplied abstract, a number of keywords and a classification are provided. In some cases own comments are added. The purpose of these comments is to show where, how and why decision tables are used. The literature is classified according to application area, theoretical versus practical character, year of publication, country or origin (not necessarily country of publication) and the language of the document. After a description of the scope of the interview, classification results and the classification by topic are presented. The main body of the paper is the ordered list of publications with abstract, classification and comments.

Formalising responsibility modelling for automatic analysis

Modelling the structure of social-technical systems as a basis for informing software system design is a difficult compromise. Formal methods struggle to capture the scale and complexity of the heterogeneous organisations that use technical systems. Conversely, informal approaches lack the rigour needed to inform the software design and construction process or enable automated analysis. We revisit the concept of responsibility modelling, which models social technical systems as a collection of actors who discharge their responsibilities, whilst using and producing resources in the process. Responsibility modelling is formalised as a structured approach for socio-technical system requirements specification and modelling, with well-defined semantics and support for automated structure and validity analysis. The effectiveness of the approach is demonstrated by two case studies of software engineering methodologies