A Proposal for Defining a Set of Basic Items for Project-Specific Traceability Methodologies

  • Authors:
  • Angelina Espinoza;Juan Garbajosa

  • Affiliations:
  • -;-

  • Venue:
  • SEW '08 Proceedings of the 2008 32nd Annual IEEE Software Engineering Workshop
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

One widely accepted approach to implement traceabilitypractices is the use of methodologies. But the information relatedto organization, stakeholders, product size, and qualityrequirements may change from one project to another. As aconsequence, traceability information differs as well, whicharises specific traceability requirements to each project.One common way to cope with this fact is the use ofmetamodels to underpin methodologies. However most ofthe traceability metamodeling approaches simply provide apredefined set of concepts, with no extension mechanism.Therefore, customizing a methodology for a specific projectis often unsatisfactory. This paper justifies that this problemcan be approached if traceability metamodels includea basic set of items, including concepts and traceabilitystructures, designed to be extended according to projectfeatures. For this, the right modeling tools are required:that is, some metamodeling principles that support typingand extensibility, together with a general and extensibledescription of the software process. This second issue isobtained from ISO/IEC 24744 with some additional inputs.This paper explains how to use these tools in practice todefine the so called TmM metamodel. Within this paper TmMis applied to a case study in which non-conventional workproducts have to be considered as part of the traceabilityinformation.