Validating Pragmatic Reuse Tasks
| atmire.migration.oldid | 2907 | |
| dc.contributor.advisor | Walker, Robert | |
| dc.contributor.author | Makady, Soha | |
| dc.date.accessioned | 2015-01-28T22:33:26Z | |
| dc.date.available | 2015-02-23T08:00:38Z | |
| dc.date.issued | 2015-01-28 | |
| dc.date.submitted | 2015 | en |
| dc.description.abstract | Disciplined software development involves the ad hoc reuse of source code that was not designed for that reuse. Such pragmatic reuse tasks have long been criticized due to a lack of systematic support, and an inability to validate that the reused code still provides its functionality of interest within the target system. Although recent work has successfully systematized support for pragmatic reuse tasks, validating those reuse tasks has not been tackled yet. Current approaches to validating reuse tasks require the developer to rely on automated test generation techniques which could miss serious defects, or to create his own test suite—a time consuming process whose correctness would be questioned due to the developer’s limited knowledge about the reused code. A third alternative would be to modify the originating system’s test suite to only exercise and validate the reused code. But such a manual editing process can result in injecting more defects into the originally high quality source code and its corresponding test suite. The thesis of this dissertation is that, by providing developers with tool support to reuse test cases within pragmatic reuse scenarios, we can leverage the quality of the pragmatically reused code, while reducing the needed manual intervention. To validate this claim, we have proposed a novel approach and tool to semi-automatically reuse and transform relevant portions of the test suite associated with pragmatically reused source code, as a means to validate that the relevant constraints from the originating system continue to hold, while minimizing the needed developer intervention. We have evaluated various aspects of our proposed approach, through a series of empirical studies, and using a variety of source systems and tasks. The results show that, relative to the manual approach, our approach reduces task completion time and improves the correctness of the reused test cases. Furthermore, our proposed approach can make the process of finding and fixing errors within pragmatic reuse tasks faster, and its transformed test cases can be maintained. | en_US |
| dc.identifier.citation | Makady, S. (2015). Validating Pragmatic Reuse Tasks (Doctoral thesis, University of Calgary, Calgary, Canada). Retrieved from https://prism.ucalgary.ca. doi:10.11575/PRISM/28625 | en_US |
| dc.identifier.doi | http://dx.doi.org/10.11575/PRISM/28625 | |
| dc.identifier.uri | http://hdl.handle.net/11023/2032 | |
| dc.language.iso | eng | |
| dc.publisher.faculty | Graduate Studies | |
| dc.publisher.institution | University of Calgary | en |
| dc.publisher.place | Calgary | en |
| dc.rights | University of Calgary graduate students retain copyright ownership and moral rights for their thesis. You may use this material in any way that is permitted by the Copyright Act or through licensing that has been assigned to the document. For uses that are not allowable under copyright legislation or licensing, you are required to seek permission. | |
| dc.subject | Computer Science | |
| dc.subject.classification | Pragmatic software reuse | en_US |
| dc.subject.classification | Skipper | en_US |
| dc.subject.classification | Empirical Software Engineering | en_US |
| dc.subject.classification | software engineering | en_US |
| dc.subject.classification | Test suite reuse | en_US |
| dc.title | Validating Pragmatic Reuse Tasks | |
| dc.type | doctoral thesis | |
| thesis.degree.discipline | Computer Science | |
| thesis.degree.grantor | University of Calgary | |
| thesis.degree.name | Doctor of Philosophy (PhD) | |
| ucalgary.item.requestcopy | true |