Ontology Knowledge Engineering

Context: Software architecture documentation is used to communicate architectural knowledge. It is often difficult for document users to find all the architectural knowledge they need to do their tasks, and this results in wasted time and mistakes during development. Objective: In this paper we investigate how ontology-based documentation may support users in finding the architectural knowledge they need. Method: We executed a controlled experiment to test for differences in knowledge retrieval efficiency and effectiveness between two groups of master students that used two ontologies built from different understandings of the architectural knowledge needs of document users. Results: Use of the ontology built based on a better understanding of architectural knowledge needs was significantly more efficient or effective for retrieving part of the knowledge needed by document users. We analysed participants' search actions and identified which organisation of knowledge in the ontologies resulted in efficient and effective knowledge retrieval. Conclusion: We found that an improved understanding of knowledge needs allows for the construction of an ontology from which document users retrieve knowledge more efficiently and effectively. In some cases we found that the ontology support for knowledge needs had to be traded off against ontology design criteria.

A common approach to software architecture documentation in industry projects is the use of file-based documents. This approach offers a single-dimensional perspective on the architectural knowledge contained. Knowledge retrieval from file-based architecture documentation is efficient if the perspective chosen fits the needs of the readers; it is less so if the perspective does not match the needs of the readers. In this paper we describe an approach aimed at addressing architecture documentation retrieval issues. We have employed a software ontology in a semantic wiki optimized for architecture documentation. We have evaluated this ontologybased approach in a controlled industry experiment involving software professionals. The efficiency and effectiveness of the proposed approach is found to be better than that of the filebased approach.

The usefulness of Software Architecture (SA) documentation depends on how well its Architectural Knowledge (AK) can be retrieved by the stakeholders in a software project. Recent findings show that the use of ontology-based SA documentation is promising. However, different roles in software development have different needs for AK, and building an ontology to suit these needs is challenging. In this paper we describe an approach to build an ontology for SA documentation. This approach involves the use of typical questions for eliciting and constructing an ontology. We outline eight contextual factors, which influence the successful construction of an ontology, especially in complex software projects with diverse AK users. We tested our 'typical question' approach in a case study and report how it can be used for acquiring and modeling AK needs.

Within the scope of ANSWER, an EC-supported research project, a new artistic notation system, called DirectorNotation, is being developed for describing media content, much like notes are used to document a music composition. Our current research focuses on developing “notation-enabled” offline authoring tools, but interactive applications are an anticipated extension. Here, we summarise the key aspects of DirectorNotation and the ANSWER project, from the point of view of a multimedia-technology audience interested in content-based manipulation of media.

Over the years, there has been an increasing adoption of ontology-driven conceptual models to represent the conceptual structure of critical domains in reality. Given the complexity of this task, there has been a growing demand for the development of proper engineering tools for supporting the design of these models. Despite a number of advances in this area, there is still a shortage of tools directed at novice and non-technical users that can, at the same time, address two competing requirements, namely: maintain modeling expressivity by being able to represent true ontological distinctions, while remaining intuitive and easy to learn by this class of users. In this article, we sketch a proposal in this direction by introducing the idea of an Ontology Model Canvas.

As there is considerable freedom for software workers to decide what to do in an agile environment, there is a need to be explicit about social aspects such as task ownership between roles and the agility in owning those tasks. We have conducted interviews and a survey at a large organization to explore these issues. The results indicate that there are areas where architects and software engineers have different views on task ownership. Some of the less exciting tasks such as documentation and issue clarification then easily become a hot potato nobody wants.

A common approach to software architecture documentation in industry projects is the use of file-based documents. This approach offers a single-dimensional arrangement of the architectural knowledge. Knowledge retrieval from file-based architecture documentation is efficient if the organisation of knowledge supports the needs of the readers; otherwise it can be difficult. In this paper, we compare the organisation and retrieval of architectural knowledge in a file-based documentation approach and an ontology-based documentation approach. The ontology-based approach offers a multi-dimensional organisation of architectural knowledge by means of a software ontology and semantic wiki, whereas file-based documentation typically uses hierarchical organisation by directory structure and table of content. We conducted case studies in two companies to study the efficiency and effectiveness of retrieving architectural knowledge from the different organisations of knowledge. We found that the use of better knowledge organisation correlates with the efficiency and effectiveness of AK retrieval. Professionals who used the knowledge organisation found this beneficial.

Context: Software architecture documentation is used to communicate architectural knowledge. It is often difficult for document users to find all the architectural knowledge they need to do their tasks, and this results in wasted time and mistakes during development. Objective: In this paper we investigate how ontology-based documentation may support users in finding the architectural knowledge they need. Method: We executed a controlled experiment to test for differences in knowledge retrieval efficiency and effectiveness between two groups of master students that used two ontologies built from different understandings of the architectural knowledge needs of document users. Results: Use of the ontology built based on a better understanding of architectural knowledge needs was significantly more efficient or effective for retrieving part of the knowledge needed by document users. We analysed participants' search actions and identified which organisation of knowledge in the ontologies resulted in efficient and effective knowledge retrieval. Conclusion: We found that an improved understanding of knowledge needs allows for the construction of an ontology from which document users retrieve knowledge more efficiently and effectively. In some cases we found that the ontology support for knowledge needs had to be traded off against ontology design criteria.

Within the scope of ANSWER, an EC-supported research project, a new artistic notation system, called DirectorNotation, is being developed for describing media content, much like notes are used to document a music composition. Our current research focuses on developing “notation-enabled” offline authoring tools, but interactive applications are an anticipated extension. Here, we summarise the key aspects of DirectorNotation and the ANSWER project, from the point of view of a multimedia-technology audience interested in content-based manipulation of media.

In the present paper we explore Ontologies, as a means to capture knowledge of the film-making domain. More specifically, we intend to open a discussion so as to guide the development of DirectorNotation, an under-development open-source tool for representing media content, as of its pre-production and production phases, using a symbolic notation system, in which a film director can formally record his intentions. DirectorNotation’s authors suggest Ontologies for formalizing and reasoning over their notation system. The current paper discusses this technical choice, considering its limitations, and makes suggestions about the work that needs to be performed if these limitations are to be overcome.

This paper describes a software architecture documentation tool (KaitoroBase) built within the Thinkbase Visual Wiki to provide support for non-linear navigation and visualization of Software Architecture Documents (SADs) produced using the Attribute-Driven Design (ADD) method. This involves constructing the meta-model for the SAD in Freebase which provides the foundation for the graph-based interactive visualization enabled by Thinkbase. The resulting tool displays a graphical, high-level structure of SAD, allows for exploratory search, non-linear navigation, and at the same time connects to low-level details of SADs in a wiki.