Value-Based Requirements Traceability: Lessons Learned

Egyed, Alexander; Grünbacher, Paul; Heindl, Matthias; Biffl, Stefan

doi:10.1007/978-3-540-92966-6_14

Cited by 21 publications

(16 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It differs from a usual recording activity in that the supporting traceability tools and metamodels have to be reviewed and adjusted, resulting in a new iteration of planning and preparing, or in that missing traces have to be identified and errors have to be corrected following the recording activity. The latter can also be seen as a separate enhancement activity [62].…”

Section: Activities Supporting Traceabilitymentioning

confidence: 98%

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: Activities Supporting Traceabilitymentioning

confidence: 98%

“…Tailor traceability to the project's needs [59,62] value-based/cost-benefit aware traceability [84,85] provide immediate benefit to management [105] use different traceability methods for links of different importance [41] research towards easily tailoring traceability [97,115] …”

Section: Economic Aspectsmentioning

confidence: 99%

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

2009

View full text Add to dashboard Cite

show abstract

“…Parallel research has therefore focused on those issues that frame the initial planning and management of traceability. Promising examples include a valuebased approach to determine what traces to capture, and adaptive strategies to e↵ectively migrate between simple and more detailed forms of traceability as needs evolve [26]. Case study reports provide mature insights into industrial practices for planning and managing traceability [51,79,78,75,71,38], suggesting that the potential for researchers and practitioners to work together to synthesize lessons and inform practice is now mature.…”

Section: Traceability Information Modelsmentioning

confidence: 99%

Software traceability: trends and future directions

Cleland‐Huang

Gotel²,

Hayes

et al. 2014

Future of Software Engineering Proceedings

231

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

“…In our study, both the RTM decision and the rational decision-making process are examined. While our work demonstrates the value of optimal foraging models, how to expand the analysis to account for the predictable level of human fallibility [50] and to balance the economics of maintaining and utilizing the requirements traces [73,74] remains an open question.…”

Section: Studies Of Human Factors In Tracingmentioning

confidence: 99%

Toward an effective automated tracing process

Mahmoud

2012

2012 20th IEEE International Conference on Program Comprehension (ICPC)

View full text Add to dashboard Cite

Traceability is defined as the ability to establish, record, and maintain dependency relations among various software artifacts in a software system, in both a forwards and backwards direction, throughout the multiple phases of the project's life cycle. The availability of traceability information has been proven vital to several software engineering activities such as program comprehension, impact analysis, feature location, software reuse, and verification and validation (V&V).The research on automated software traceability has noticeably advanced in the past few years. Various methodologies and tools have been proposed in the literature to provide automatic support for establishing and maintaining traceability information in software systems. This movement is motivated by the increasing attention traceability has been receiving as a critical element of any rigorous software development process. However, despite these major advances, traceability implementation and use is still not pervasive in industry. In particular, traceability tools are still far from achieving performance levels that are adequate for practical applications. Such low levels of accuracy require software engineers working with traceability tools to spend a considerable amount of their time verifying the generated traceability information, a process that is often described as tedious, exhaustive, and error-prone.Motivated by these observations, and building upon a growing body of work in this area, in this dissertation we explore several research directions related to enhancing the performance of automated tracing tools and techniques. In particular, our work addresses several issues related to the various aspects of the IR-based automated tracing process, including trace link retrieval, performance enhancement, and the role of the human in the process. Our main objective is to achieve performance levels, in terms of accuracy, efficiency, and usability, that are adequate for practical applications, and ultimately to accomplish a successful technology transfer from research to industry.

show abstract

Value-Based Requirements Traceability: Lessons Learned

Cited by 21 publications

References 12 publications

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

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

Software traceability: trends and future directions

Toward an effective automated tracing process

Contact Info

Product

Resources

About