Analyzing and Systematizing Current Traceability Schemas

Espinoza, Angelina; Alarcón, Pedro Pablo; Garbajosa, Juan

doi:10.1109/sew.2006.12

Cited by 18 publications

(26 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In order to systematically approach traceability, a schema specification is needed. Espinoza et al [63] state, that such a schema specification has to include: a traceability type set which defines the types of links and their meaning for a project (see Sect. 2.4), a traceability role set which defines the stakeholders and their permission to access traces, a minimal links set that determines which links have to exist so that traceability information is regarded as correct and complete for a specific project.…”

Section: Object Sourcementioning

confidence: 99%

“…In addition to the aforementioned models, Dahlstedt and Persson [44], Espinoza et al [63], Limón and Garbajosa [109], Ramesh and Jarke [156], Spanoudakis and Zisman [171], von Knethen and Paech [193], and many others have published suggestions for classifying traceability links based on their structural and semantic properties. These proposed classifications are difficult to evaluate and compare because there is no common level of abstraction and usually no unambiguous or formal definition of the different categories.…”

Section: Traceability Link Typesmentioning

confidence: 99%

See 1 more Smart Citation

A survey of traceability in requirements engineering and model-driven development

2009

View full text Add to dashboard Cite

Traceability-the ability to follow the life of software artifacts-is a topic of great interest to software developers in general, and to requirements engineers and model-driven developers in particular. This article aims to bring those stakeholders together by providing an overview of the current state of traceability research and practice in both areas. As part of an extensive literature survey, we identify commonalities and differences in these areas and uncover several unresolved challenges which affect both domains. A good common foundation for further advances regarding these challenges appears to be a combination of the formal basis and the automated recording opportunities of MDD on the one hand, and the more holistic view of traceability in the requirements engineering domain on the other hand.Keywords Requirements engineering · Model-driven engineering · Model-driven development · Traceability

show abstract

Section: Object Sourcementioning

confidence: 99%

Section: Traceability Link Typesmentioning

confidence: 99%

A survey of traceability in requirements engineering and model-driven development

2009

View full text Add to dashboard Cite

show abstract

“…A conclusion of this analysis, pointed out in [29,30], is that traceability support for agile development practices can be improved taking into account at least three modeling issues. The first is that the traceability models must support userdefinable traceability types.…”

Section: Agile Versus Traditional From the Traceability Perspectivementioning

confidence: 99%

“…5, to show how the proposed ideas work in practice. In previous works [29,30], fundamental issues to define a project-specific traceability methodology were presented and discussed. Some of those results were to include, as part of the traceability implementation, traceability types with linkage rules, support for different granularity levels of the linking system artifacts, and traceability weights to indicate the relationship dependency force between two artifacts.…”

Section: Introductionmentioning

confidence: 99%

A study to support agile methods more effectively through traceability

Espinoza

Garbajosa

2011

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

Traceability is recognized to be important for supporting agile development processes. However, after analyzing many of the existing traceability approaches it can be concluded that they strongly depend on traditional development process characteristics. Within this paper it is justified that this is a drawback to support adequately agile processes. As it is discussed, some concepts do not have the same semantics for traditional and agile methodologies. This paper proposes three features that traceability models should support to be less dependent on a specific development process: (1) user-definable traceability links, (2) roles, and (3) linkage rules. To present how these features can be applied, an emerging traceability metamodel (TmM) will be used within this paper. TmM supports the definition of traceability methodologies adapted to the needs of each project. As it is shown, after introducing these three features into traceability models, two main advantages are obtained: 1) the support they can provide to agile process stakeholders is significantly more extensive, and 2) it will be possible to achieve a higher degree of automation. In this sense it will be feasible to have a methodical trace acquisition and maintenance process adapted to agile processes.

show abstract

“…In [Esp06], a so-called traceability meta-type specifies required or recommended elements a concrete traceability relationship type should possess. This generic concept allows for the definition of customized, application-specific relationship types.…”

Section: Traceability-related Activitiesmentioning

confidence: 99%