Why and How of Requirements Tracing
IEEE Software
Software reflexion models: bridging the gap between source and high-level models
SIGSOFT '95 Proceedings of the 3rd ACM SIGSOFT symposium on Foundations of software engineering
Reengineering class hierarchies using concept analysis
SIGSOFT '98/FSE-6 Proceedings of the 6th ACM SIGSOFT international symposium on Foundations of software engineering
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
Subject-oriented design: towards improved alignment of requirements, design, and code
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
On the inevitable intertwining of specification and implementation
Communications of the ACM
An Object-Oriented Tool for Tracing Requirements
IEEE Software
Design Traceability of Complex Systems
HICS '98 Proceedings of the Fourth Symposium on Human Interaction with Complex Systems
Maintaining Traceability During Object-Oriented Software Evolution: A Case Study
ICSM '99 Proceedings of the IEEE International Conference on Software Maintenance
Improving Reviews by Extended Traceability
HICSS '99 Proceedings of the Thirty-Second Annual Hawaii International Conference on System Sciences-Volume 3 - Volume 3
Heterogeneous view integration and its automation
Heterogeneous view integration and its automation
Automated abstraction of class diagrams
ACM Transactions on Software Engineering and Methodology (TOSEM)
Domain Networks in the Software Development Process
ICSR-7 Proceedings of the 7th International Conference on Software Reuse: Methods, Techniques, and Tools
Using Software Architecture for Code Testing
IEEE Transactions on Software Engineering
A Weakly Constrained Approach to Software Change Coordination
Proceedings of the 26th International Conference on Software Engineering
A case study on value-based requirements tracing
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Traceability in viewpoint merging: a model management perspective
TEFSE '05 Proceedings of the 3rd international workshop on Traceability in emerging forms of software engineering
An XML based approach to support the evolution of model-to-model 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
Risk management with enhanced tracing of requirements rationale in highly distributed projects
Proceedings of the 2006 international workshop on Global software development for the practitioner
The MT model transformation language
Proceedings of the 2006 ACM symposium on Applied computing
Utilizing use case classes for requirement and traceability modeling
MS'06 Proceedings of the 17th IASTED international conference on Modelling and simulation
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
Recovering and using use-case-diagram-to-source-code traceability links
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
An end-to-end industrial software traceability tool
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Science of Computer Programming
Science of Computer Programming
A Collaborative Method for Reuse Potential Assessment in Reengineering-Based Product Line Adoption
Balancing Agility and Formalism in Software Engineering
Software Engineering
Towards traceable test-driven development
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
Tracing the rationale behind UML model change through argumentation
ER'07 Proceedings of the 26th international conference on Conceptual modeling
Traceability between function point and source code
Proceedings of the 6th International Workshop on Traceability in Emerging Forms of Software Engineering
Problem-solution mapping for forward and reengineering on architectural level
Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution
CAiSE'11 Proceedings of the 23rd international conference on Advanced information systems engineering
Explicit use-case representation in object-oriented programming languages
Proceedings of the 7th symposium on Dynamic languages
An overview of techniques for detecting software variability concepts in source code
ER'11 Proceedings of the 30th international conference on Advances in conceptual modeling: recent developments and new directions
EA-tracer: identifying traceability links between code aspects and early aspects
Proceedings of the 27th Annual ACM Symposium on Applied Computing
Hi-index | 0.00 |
Design traceability has been widely recognized as being an integral aspect of software development. In the past years this fact has been amplified due to the increased use of legacy systems and COTS (commercial-off-the-shelf) components mixed with the growing use of elaborate “upstream” software modeling techniques such as the Unified Modeling Language (UML). The more intensive emphasis on upstream (non-programming) software development issues has, however, widened the gap between software components (e.g., subsystems, modules) and software models (e.g., class diagrams, data flow diagrams), creating the need for a better understanding of the intricacies and interrelationships between the two. This paper demonstrates how observable run-time information of software systems can be used to detect traceability information between software systems and their models. We do this by employing a technique that evaluates the “footprints” that usage scenarios (e.g., test cases) make during the execution of software systems. Those footprints can be compared, resulting in additional traceability information among modeling elements associated with those scenarios. Our approach is tool supported.