Zur Kurzanzeige

dc.contributor.authorGoman, Maksim
dc.contributor.authorRath, Michael
dc.contributor.authorMäder, Patrick
dc.date.accessioned2023-03-02T10:35:53Z
dc.date.available2023-03-02T10:35:53Z
dc.date.issued2018
dc.identifier.issn0720-8928
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/40541
dc.description.abstractEstablished traceability among development artifacts allows to apply structured analysis in order to answer questions posed by stakeholders. Typically, the artifacts and their links are stored in relational databases. However, answering trace related questions involves finding paths and patterns in the artifact graph - a difficult task to perform using generic query languages. Mapping the artifact and link data onto graph databases and utilizing specialized query languages may overcome this limitation. In this paper, this mapping from a relational traceability dataset to a graph database is demonstrated. Afterwards, the advantages and disadvantages of the approach are investigated by calculating three trace metrics, heavily relying on graph patterns, using a graph query language. Overall, utilizing a graph database proved to simplify traceability analysis.en
dc.language.isoen
dc.publisherGeselllschaft für Informatik e.V.
dc.relation.ispartofSoftwaretechnik-Trends Band 38, Heft 1
dc.titleLessons Learned from Analyzing Requirements Traceability using a Graph Databaseen
dc.typeJournal Articles
dc.pubPlaceBonn
mci.reference.pages27-30
mci.conference.sessiontitleFG ARC: Workshop des Arbeitskreises "Traceability/Evolution", 27.10.2017, Technische Universität Ilmenau


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige