ArchTrace: Policy-Based Support for Managing Evolving Architecture-to-Implementation Traceability Links

Murta, Leonardo P.; Hoek, Andre Der; Werner, Cláudia

doi:10.1109/ase.2006.16

Cited by 36 publications

(34 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An extension of this work was presented in [71] in which a graph-theoretic model for formally defining the problem of associating UML models with related code has been proposed. The work in [48] describes ArchTrace, a tool to support automatic evolution of traceability links between architecture models and source code. The approach uses policies to assist with the addition of new links, removal of existing links, and changes in existing links.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

XTraQue: traceability for product line systems

Jirapanthong

Zisman

2007

Softw Syst Model

View full text Add to dashboard Cite

Section: Related Workmentioning

confidence: 99%

“…Examples of these activities are change impact analysis, system validation and verification, system reuse, and system understanding [4,6,15,17,25,38,48,75].…”

Section: Related Workmentioning

confidence: 99%

XTraQue: traceability for product line systems

Jirapanthong

Zisman

2007

Softw Syst Model

View full text Add to dashboard Cite

“…Our approach can be combined with trace generation methods and tools (Grechanik et al, 2007;Hayes et al, 2006;Murta et al, 2006) for tracing requirements/architecture to source code. In cases where code is automatically generated from the architecture, changes in code can be traced and implemented automatically.…”

Section: Identifying Changes In the Codementioning

confidence: 99%

Generation and validation of traces between requirements and architecture based on formal trace semantics

Göknil

Kurtev²,

Berg

2014

Journal of Systems and Software

View full text Add to dashboard Cite

Please cite this article in press as: Goknil, A., et al., Generation and validation of traces between requirements and architecture based on formal trace semantics. J. Syst. Software (2013) The size and complexity of software systems make integration of the new/modified requirements to the software system costly and time consuming. The impact of requirements changes on other requirements, design elements and source code should be traced to determine parts of the software to be changed. Considerable research has been devoted to relating requirements and design artifacts with source code. Less attention has been paid to relating requirements (R) with architecture (A) by using well-defined semantics of traces. Traces between R&A might be manually assigned. This is time-consuming, and error prone. Traces might be incomplete and invalid. In this paper, we present an approach for automatic trace generation and validation of traces between requirements (R) and architecture (A). Requirements relations and architecture verification techniques are used. A trace metamodel is defined with commonly used trace types between R&A. We use the semantics of traces and requirements relations for generating and validating traces with a tool support. The tool provides the following: (1) generation and validation of traces by using requirements relations and/or verification of architecture, (2) generation and validation of requirements relations by using traces. The tool is based on model transformation in ATL and termrewriting logic in Maude.

show abstract

“…Mäder et al explored the use of heuristic techniques that recognize specific development activities, such as changes applied to a UML model [61], and then evolve trace links according to a set of heuristics. Similar approaches have been explored for changes in requirements [11], and between architectures defined using xADL and source code [70]. Researchers have also developed trace retrieval approaches which attempt to identify deltas between the artifacts retrieved over consecutive traces [92].…”

Section: Evolving Linksmentioning

confidence: 99%

Software traceability: trends and future directions

Cleland‐Huang

Gotel²,

Hayes

et al. 2014

Future of Software Engineering Proceedings

233

View full text Add to dashboard Cite

Software traceability is a sought-after, yet often elusive quality in software-intensive systems. Required in safety-critical systems by many certifying bodies, such as the USA Federal Aviation Authority, software traceability is an essential element of the software development process. In practice, traceability is often conducted in an ad-hoc, after-the-fact manner and, therefore, its benefits are not always fully realized. Over the past decade, researchers have focused on specific areas of the traceability problem, developing more sophisticated tooling, promoting strategic planning, applying information retrieval techniques capable of semi-automating the trace creation and maintenance process, developing new trace query languages and visualization techniques that use trace links, and applying traceability in specific domains such as Model Driven Development, product line systems, and agile project environments. In this paper, we build upon a prior body of work to highlight the state-of-the-art in software traceability, and to present compelling areas of research that need to be addressed.

show abstract

ArchTrace: Policy-Based Support for Managing Evolving Architecture-to-Implementation Traceability Links

Cited by 36 publications

References 20 publications

XTraQue: traceability for product line systems

XTraQue: traceability for product line systems

Generation and validation of traces between requirements and architecture based on formal trace semantics

Software traceability: trends and future directions

Contact Info

Product

Resources

About