An Exploratory Study on Ontology Engineering for Software Architecture Documentation

K.A. de Graaf; P. Liang; A. Tang; W.R. van Hage; J.C. Vliet

doi:10.1016/j.compind.2014.04.006

An Exploratory Study on Ontology Engineering for Software Architecture Documentation

K.A. de Graaf, P. Liang, A. Tang, W.R. van Hage, J.C. Vliet

Research output: Contribution to Journal › Article › Academic › peer-review

187 Downloads (Pure)

Abstract

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. © 2014 Elsevier B.V.

Original language	English
Pages (from-to)	1053-1064
Journal	Computers in Industry
Volume	65
Issue number	7
Early online date	27 May 2014
DOIs	https://doi.org/10.1016/j.compind.2014.04.006
Publication status	Published - 2014

Access to Document

10.1016/j.compind.2014.04.006

OE for SAD - accepted prepubAccepted author manuscript, 437 KBLicence: CC BY-SA

Fingerprint Dive into the research topics of 'An Exploratory Study on Ontology Engineering for Software Architecture Documentation'. Together they form a unique fingerprint.

Cite this

@article{3d5dfc66f8a544449fa618f6e5ab3032,

title = "An Exploratory Study on Ontology Engineering for Software Architecture Documentation",

abstract = "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. {\textcopyright} 2014 Elsevier B.V.",

author = "{de Graaf}, K.A. and P. Liang and A. Tang and {van Hage}, W.R. and J.C. Vliet",

year = "2014",

doi = "10.1016/j.compind.2014.04.006",

language = "English",

volume = "65",

pages = "1053--1064",

journal = "Computers in Industry",

issn = "0166-3615",

publisher = "Elsevier",

number = "7",

}

TY - JOUR

T1 - An Exploratory Study on Ontology Engineering for Software Architecture Documentation

AU - de Graaf, K.A.

AU - Liang, P.

AU - Tang, A.

AU - van Hage, W.R.

AU - Vliet, J.C.

PY - 2014

Y1 - 2014

N2 - 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. © 2014 Elsevier B.V.

AB - 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. © 2014 Elsevier B.V.

U2 - 10.1016/j.compind.2014.04.006

DO - 10.1016/j.compind.2014.04.006

M3 - Article

VL - 65

SP - 1053

EP - 1064

JO - Computers in Industry

JF - Computers in Industry

SN - 0166-3615

IS - 7

ER -