Concept mapping as a means of requirements tracing

L. Kof; R. Gacitua; M. Rouncefield; P. Sawyer

doi:10.1109/MARK.2010.5623813

Concept mapping as a means of requirements tracing

L. Kof, R. Gacitua, M. Rouncefield, P. Sawyer

College of Engineering and Physical Sciences

Research output: Chapter in Book/Published conference output › Conference publication

Abstract

Requirements documents often describe the system on different abstraction levels. This results in the fact that the same issues may be described in different documents and with different vocabulary. For analysts who are new to the application domain, this poses a major orientation problem, as they cannot link different concepts or documents with each other. In the presented paper, we propose an approach to map concepts extracted from different documents to each other. This, in turn, allows us to find related passages in different documents, even though the documents represent different levels of abstraction. Practical applicability of the approach was proven in a case study with real-world requirements documents.

Original language	English
Title of host publication	2010 Third International Workshop on Managing Requirements Knowledge (MARK)
Publisher	IEEE
Pages	22-31
Number of pages	10
ISBN (Print)	978-1-4244-8783-7
DOIs	https://doi.org/10.1109/MARK.2010.5623813
Publication status	Published - 1 Sept 2010
Event	2010 Third International Workshop on Managing Requirements Knowledge (MARK) - Sydney, Australia Duration: 27 Sept 2010 → 27 Sept 2010

Conference

Conference	2010 Third International Workshop on Managing Requirements Knowledge (MARK)
Country/Territory	Australia
City	Sydney
Period	27/09/10 → 27/09/10

Access to Document

10.1109/MARK.2010.5623813

Cite this

@inproceedings{a46427a9d1624bfda26b1bddac5d8a5f,

title = "Concept mapping as a means of requirements tracing",

abstract = "Requirements documents often describe the system on different abstraction levels. This results in the fact that the same issues may be described in different documents and with different vocabulary. For analysts who are new to the application domain, this poses a major orientation problem, as they cannot link different concepts or documents with each other. In the presented paper, we propose an approach to map concepts extracted from different documents to each other. This, in turn, allows us to find related passages in different documents, even though the documents represent different levels of abstraction. Practical applicability of the approach was proven in a case study with real-world requirements documents.",

author = "L. Kof and R. Gacitua and M. Rouncefield and P. Sawyer",

year = "2010",

month = sep,

day = "1",

doi = "10.1109/MARK.2010.5623813",

language = "English",

isbn = "978-1-4244-8783-7",

pages = "22--31",

booktitle = "2010 Third International Workshop on Managing Requirements Knowledge (MARK)",

publisher = "IEEE",

address = "United States",

note = "2010 Third International Workshop on Managing Requirements Knowledge (MARK) ; Conference date: 27-09-2010 Through 27-09-2010",

}

TY - GEN

T1 - Concept mapping as a means of requirements tracing

AU - Kof, L.

AU - Gacitua, R.

AU - Rouncefield, M.

AU - Sawyer, P.

PY - 2010/9/1

Y1 - 2010/9/1

N2 - Requirements documents often describe the system on different abstraction levels. This results in the fact that the same issues may be described in different documents and with different vocabulary. For analysts who are new to the application domain, this poses a major orientation problem, as they cannot link different concepts or documents with each other. In the presented paper, we propose an approach to map concepts extracted from different documents to each other. This, in turn, allows us to find related passages in different documents, even though the documents represent different levels of abstraction. Practical applicability of the approach was proven in a case study with real-world requirements documents.

AB - Requirements documents often describe the system on different abstraction levels. This results in the fact that the same issues may be described in different documents and with different vocabulary. For analysts who are new to the application domain, this poses a major orientation problem, as they cannot link different concepts or documents with each other. In the presented paper, we propose an approach to map concepts extracted from different documents to each other. This, in turn, allows us to find related passages in different documents, even though the documents represent different levels of abstraction. Practical applicability of the approach was proven in a case study with real-world requirements documents.

UR - http://ieeexplore.ieee.org/document/5623813/

U2 - 10.1109/MARK.2010.5623813

DO - 10.1109/MARK.2010.5623813

M3 - Conference publication

SN - 978-1-4244-8783-7

SP - 22

EP - 31

BT - 2010 Third International Workshop on Managing Requirements Knowledge (MARK)

PB - IEEE

T2 - 2010 Third International Workshop on Managing Requirements Knowledge (MARK)

Y2 - 27 September 2010 through 27 September 2010

ER -

Concept mapping as a means of requirements tracing

Abstract

Conference

Access to Document

Other files and links

Fingerprint

Cite this