Home > Research > Publications & Outputs > Concept mapping as a means of requirements tracing

Research

Associated organisational units

Links

Text available via DOI:

View graph of relations

Concept mapping as a means of requirements tracing

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Concept mapping as a means of requirements tracing. / Kof, L.; Gacitua, R.; Rouncefield, M. et al.
Managing Requirements Knowledge (MARK), 2010 Third International Workshop on. IEEE Computer Society, 2010. p. 22-31.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Kof, L, Gacitua, R, Rouncefield, M & Sawyer, P 2010, Concept mapping as a means of requirements tracing. in Managing Requirements Knowledge (MARK), 2010 Third International Workshop on. IEEE Computer Society, pp. 22-31, 18th IEEE INternational Conference on Requirements Engineering, Sydney, Australia, 27/09/10. https://doi.org/10.1109/MARK.2010.5623813

APA

Kof, L., Gacitua, R., Rouncefield, M., & Sawyer, P. (2010). Concept mapping as a means of requirements tracing. In Managing Requirements Knowledge (MARK), 2010 Third International Workshop on (pp. 22-31). IEEE Computer Society. https://doi.org/10.1109/MARK.2010.5623813

Vancouver

Kof L, Gacitua R, Rouncefield M, Sawyer P. Concept mapping as a means of requirements tracing. In Managing Requirements Knowledge (MARK), 2010 Third International Workshop on. IEEE Computer Society. 2010. p. 22-31 doi: 10.1109/MARK.2010.5623813

Author

Kof, L. ; Gacitua, R. ; Rouncefield, M. et al. / Concept mapping as a means of requirements tracing. Managing Requirements Knowledge (MARK), 2010 Third International Workshop on. IEEE Computer Society, 2010. pp. 22-31

Bibtex

@inproceedings{9c8d7e3385d243ddb835c457b82c76c9,
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 = "Managing Requirements Knowledge (MARK), 2010 Third International Workshop on",
publisher = "IEEE Computer Society",
note = "18th IEEE INternational Conference on Requirements Engineering ; Conference date: 27-09-2010 Through 01-10-2010",

}

RIS

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.

U2 - 10.1109/MARK.2010.5623813

DO - 10.1109/MARK.2010.5623813

M3 - Conference contribution/Paper

SN - 978-1-4244-8783-7

SP - 22

EP - 31

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

PB - IEEE Computer Society

T2 - 18th IEEE INternational Conference on Requirements Engineering

Y2 - 27 September 2010 through 1 October 2010

ER -