A traceability metamodel for change management of non-functional requirements

M. Kassab, O. Ormandjieva, M. Daneva

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Requirements changes are an issue in the software development life cycle which often originates from an incomplete knowledge of the domain of interest. Hardly any requirement manifests in isolation, and usually the provision of one requirement may affect the level of provision of another. Understanding the relations among system requirements is essential to ensuring their consistency and change management. In practice, many organizations either focus their traceability efforts on functional requirements (FRs) or else fail entirely to implement an effective traceability process. Tracing non-functional requirements (NFRs) has, by and large, been neglected. In this paper, we propose a metamodel which explicitly captures NFRs and their relations, and which is independent from any programming paradigm. In addition, we present an implementation using XML-based representations for the metamodel and XQuery queries to represent tracing information.

Original languageEnglish (US)
Title of host publicationProceedings - 6th ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2008
Pages245-254
Number of pages10
DOIs
StatePublished - 2008
Event6th ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2008 - Prague, Czech Republic
Duration: Aug 20 2008Aug 22 2008

Publication series

NameProceedings - 6th ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2008

Conference

Conference6th ACIS International Conference on Software Engineering Research, Management and Applications, SERA 2008
Country/TerritoryCzech Republic
CityPrague
Period8/20/088/22/08

ASJC Scopus subject areas

  • Computer Science Applications
  • Software

Fingerprint

Dive into the research topics of 'A traceability metamodel for change management of non-functional requirements'. Together they form a unique fingerprint.

Cite this