Abstract
Traceability is commonly adopted as an aid to manage test cases in face of changing requirements. Our approach to traceability is to help decide which tests and bugs should be prioritized in order to minimize the time necessary to execute acceptance test activities of testing, debugging and fixing. Our approach is to apply a set of models based on traceability among requirements, tests, and software components. In this paper we demonstrate the facts motivating the model and how the model is to be operated. We also offer as future work some research questions and possible extensions. Index Terms — Model-Driven Engineering, Traceability, Bug Triage.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
