Facilitating qualitative research in business studies - Using the business narrative to model value creation

This is a conceptual paper supported by empirical research giving details of a new Business Narrative Modelling Language (BNML). The need for BNML arose given a growing dissatisfaction with qualitative research approaches and also due to the need to bring entrepreneurs, especially those with little training in management theory, closer to the academic (as well as practitioner) discussion of innovation and strategy for value creation. We aim primarily for an improved communication process of events which can be described using the narrative, in the discussion of the value creation process. Our findings, illustrated through a case study, should be of interest to both researchers and practitioners alike

Referent tracking for corporate memories

For corporate memory and enterprise ontology systems to be maximally useful, they must be freed from certain barriers placed around them by traditional knowledge management paradigms. This means, above all, that they must mirror more faithfully those portions of reality which are salient to the workings of the enterprise, including the changes that occur with the passage of time. The purpose of this chapter is to demonstrate how theories based on philosophical realism can contribute to this objective. We discuss how realism-based ontologies (capturing what is generic) combined with referent tracking (capturing what is specific) can play a key role in building the robust and useful corporate memories of the future

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

Some Issues on Ontology Integration

The word integration has been used with different meanings in the ontology field. This article aims at clarifying the meaning of the word “integration” and presenting some of the relevant work done in integration. We identify three meanings of ontology “integration”: when building a new ontology reusing (by assembling, extending, specializing or adapting) other ontologies already available; when building an ontology by merging several ontologies into a single one that unifies all of them; when building an application using one or more ontologies. We discuss the different meanings of “integration”, identify the main characteristics of the three different processes and proposethree words to distinguish among those meanings:integration, merge and use

The use of the concept of event in enterprise ontologies and requirements engineering literature.

The concept of event is used in a lot of meanings. It can be the possible outcome of doing something (probability theory), it can be a business transaction (accounting), or just a plain happening. In software engineering, the concept of event is also used a lot. It is used to accomplish loose coupling between software components or to realise interaction between different services. There is however not a consensus on the meaning of `an event'. In enterprise ontologies, an event is defined as a happening at one point in time, or as an activity which takes time to complete. In requirement engineering, the same different uses can be found, together with an event as a request for something that needs to be done. These differences can also be found in implementation. All these distinct purposes of the word event make it difficult to integrate and use different requirement engineering techniques. Comparison or transformations between models drawn in different grammars is impossible because of the ambiguity of the concept of event. We define three meanings for an event that are used by enterprise ontologies and requirement engineering techniques: an achievement (happening at one point in time), an activity (happening over time) and a request (a demand for something that needs to be done). We also identify a missing link between real economic events, the events defined in the requirements model and the events used in implementation.Requirements modelling; Enterprise ontology; Process modelling; Dynamic; Event;

OBOME - Ontology based opinion mining in UBIPOL

Ontologies have a special role in the UBIPOL system, they help to structure the policy related context, provide conceptualization for policy domain and use in the opinion mining process. In this work we presented a system called Ontology Based Opinion Mining Engine (OBOME) for analyzing a domain-specific opinion corpus by first assisting the user with the creation of a domain ontology from the corpus. We determined the polarity of opinion on the various domain aspects. In the former step, the policy domain aspect has are identified (namely which policy category is represented by the concept). This identification is supported by the policy modelling ontology, which describe the most important policy – related classes and structure. Then the most informative documents from the corpus are extracted and asked the user to create a set of aspects and related keywords using these documents. In the latter step, we used the corpus specific ontology to model the domain and extracted aspect-polarity associations using grammatical dependencies between words. Later, summarized results are shown to the user to analyze and store. Finally, in an offline process policy modeling ontology is updated

A core ontology for business process analysis

Business Process Management (BPM) aims at supporting the whole life-cycle necessary to deploy and maintain business processes in organisations. An important step of the BPM life-cycle is the analysis of the processes deployed in companies. However, the degree of automation currently achieved cannot support the level of adaptation required by businesses. Initial steps have been performed towards including some sort of automated reasoning within Business Process Analysis (BPA) but this is typically limited to using taxonomies. We present a core ontology aimed at enhancing the state of the art in BPA. The ontology builds upon a Time Ontology and is structured around the process, resource, and object perspectives as typically adopted when analysing business processes. The ontology has been extended and validated by means of an Events Ontology and an Events Analysis Ontology aimed at capturing the audit trails generated by Process-Aware Information Systems and deriving additional knowledge

Building Context-Aware Access Control In Enterprise Ontologies

Knowledge centric management (KCM) has become a key strategy for competitive edge. As an essential of KCM, an enterprise ontology represents the knowledge of an organization. Thus, the need for securing enterprise ontologies (EO) becomes imperative. Adequate access control is a major component of ontology security. However, access control for EO is largely neglected in information systems (IS) literature. This paper presents the first research to fill this gap. I propose five requirements for good access-control solutions for EO. The proposed solution offers an architecture framework that meets the five requirements. Semantic Web technology is used to build context-aware access controls into EO. My proposal includes a novel resolution for policy conflicts. This study provides the first design of fine-grained and dynamically-adjusted access authorizations

The benefit of enterprise ontology in identifying business components

Companies are more than ever participating in so-called value networks while being confronted with an increasing need for collaboration with their business partners. In order to better perform in such value networks information systems supporting not only the intra- but also the inter-enterprise business processes are necessary in order to enable and ease collaboration between business partners. Therefore, they need to be interoperable. As the basis for building these information systems the concepts of enterprise ontology and business components are very promising. The notion of enterprise ontology, as presented in this paper, is a powerful revelation of the essence of an enterprise or an enterprise network. Reusable and self-contained business components with well-defined interaction points facilitate the accessing and execution of coherent packages of business functionality. The identification of business components, however, is still a crucial factor. The reported research seeks to improve the identification of business components based on the ontological model of an enterprise, satisfying well-defined quality criteriaThe past and the future of information systems: 1976-2006 and beyondRed de Universidades con Carreras en Informática (RedUNCI