Adapting traceability environments to project-specific needs
Communications of the ACM
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
ADAMS Re-Trace: A Traceability Recovery Tool
CSMR '05 Proceedings of the Ninth European Conference on Software Maintenance and Reengineering
Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
When and how to visualize traceability links?
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
IEEE Transactions on Software Engineering
Can Information Retrieval Techniques Effectively Support Traceability Link Recovery?
ICPC '06 Proceedings of the 14th IEEE International Conference on Program Comprehension
Poirot: A Distributed Tool Supporting Enterprise-Wide Automated Traceability
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
Visualization and Analysis in Automated Trace Retrieval
REV '06 Proceedings of the 1st international workshop on Requirements Engineering Visualization
Using task context to improve programmer productivity
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Information Visualization: Design for Interaction (2nd Edition)
Information Visualization: Design for Interaction (2nd Edition)
Visual Support In Automated Tracing
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
REV '07 Proceedings of the Second International Workshop on Requirements Engineering Visualization
The Value of Information Visualization
Information Visualization
Graph-based Visualization of Requirements Relationships
REV '08 Proceedings of the 2008 Requirements Engineering Visualization
On Usability in Requirements Trace Visualizations
REV '08 Proceedings of the 2008 Requirements Engineering Visualization
Getting back to basics: Promoting the use of a traceability information model in practice
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Cross-artifact traceability using lightweight links
TEFSE '09 Proceedings of the 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering
Task-First or Context-First? Tool Integration Revisited
ASE '09 Proceedings of the 2009 IEEE/ACM International Conference on Automated Software Engineering
Assisting engineers in switching artifacts by using task semantic and interaction history
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
A survey of traceability in requirements engineering and model-driven development
Software and Systems Modeling (SoSyM)
| Hi-index | 0.00 |
Traceability supports users in describing and tracking the relationships between software artifacts. Techniques such as traceability matrices and graphs visualize these relationships and help users to access and understand them. Researchers agree that different visualization techniques add valuable information in different contexts. However, there is an ambiguity which visualization is suitable for which context. To clarify this we conducted a comparative study of common visualization techniques, including an experiment and interviews with 24 participants. We found that traceability matrices and graphs are most preferred in management tasks, while hyperlinks are preferred in implementation and testing tasks. Traceability lists seem to be the least attractive technique for most participants. Graphs are preferred to navigate linked artifacts, while matrices are appropriate for overview. Hyperlinks are regarded to fit for fine-grained information. Participants stressed the importance of visualizing semantics of artifacts and links. Our finding also indicates that users are not always able to choose the most suitable visualization.