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

Concept mapping as a means of requirements tracing

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Published
Publication date1/09/2010
Host publicationManaging Requirements Knowledge (MARK), 2010 Third International Workshop on
PublisherIEEE Computer Society
Pages22-31
Number of pages10
ISBN (electronic)978-1-4244-8784-4
ISBN (print)978-1-4244-8783-7
<mark>Original language</mark>English
Event18th IEEE INternational Conference on Requirements Engineering - Sydney, Australia
Duration: 27/09/20101/10/2010

Conference

Conference18th IEEE INternational Conference on Requirements Engineering
Country/TerritoryAustralia
CitySydney
Period27/09/101/10/10

Conference

Conference18th IEEE INternational Conference on Requirements Engineering
Country/TerritoryAustralia
CitySydney
Period27/09/101/10/10

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.