Show simple item record

dc.contributor.advisorSchneider, Kevinen_US
dc.contributor.advisorRoy, Chanchalen_US
dc.contributor.advisorChowdhury, Nurulen_US
dc.creatorKhan, Mohammaden_US
dc.date.accessioned2013-11-09T12:00:12Z
dc.date.available2013-11-09T12:00:12Z
dc.date.created2013-10en_US
dc.date.issued2013-11-08en_US
dc.date.submittedOctober 2013en_US
dc.identifier.urihttp://hdl.handle.net/10388/ETD-2013-10-1266en_US
dc.description.abstractSoftware maintenance is a significant phase of a software life-cycle. Once a system is developed the main focus shifts to maintenance to keep the system up to date. A system may be changed for various reasons such as fulfilling customer requirements, fixing bugs or optimizing existing code. Code needs to be studied and understood before any modification is done to it. Understanding code is a time intensive and often complicated part of software maintenance that is supported by documentation and various tools such as profilers, debuggers and source code analysis techniques. However, most of the tools fail to assist in locating the portions of the code that implement the functionality the software developer is focusing. Mining execution traces can help developers identify parts of the source code specific to the functionality of interest and at the same time help them understand the behaviour of the code. We propose a use-driven hybrid framework of static and dynamic analyses to mine and manage execution traces to support software developers in understanding how the system's functionality is implemented through feature analysis. We express a system's use as a set of tests. In our approach, we develop a set of uses that represents how a system is used or how a user uses some specific functionality. Each use set describes a user's interaction with the system. To manage large and complex traces we organize them by system use and segment them by user interface events. The segmented traces are also clustered based on internal and external method types. The clusters are further categorized into groups based on application programming interfaces and active clones. To further support comprehension we propose a taxonomy of metrics which are used to quantify the trace. To validate the framework we built a tool called TrAM that implements trace mining and provides visualization features. It can quantify the trace method information, mine similar code fragments called active clones, cluster methods based on types, categorise them based on groups and quantify their behavioural aspects using a set of metrics. The tool also lets the users visualize the design and implementation of a system using images, filtering, grouping, event and system use, and present them with values calculated using trace, group, clone and method metrics. We also conducted a case study on five different subject systems using the tool to determine the dynamic properties of the source code clones at runtime and answer three research questions using our findings. We compared our tool with trace mining tools and profilers in terms of features, and scenarios. Finally, we evaluated TrAM by conducting a user study on its effectiveness, usability and information management.en_US
dc.language.isoengen_US
dc.subjectstatic, dynamic, instrumentation, execution trace, program comprehensionen_US
dc.titleSupporting Source Code Feature Analysis Using Execution Trace Miningen_US
thesis.degree.departmentComputer Scienceen_US
thesis.degree.disciplineComputer Scienceen_US
thesis.degree.grantorUniversity of Saskatchewanen_US
thesis.degree.levelMastersen_US
thesis.degree.nameMaster of Science (M.Sc.)en_US
dc.type.materialtexten_US
dc.type.genreThesisen_US
dc.contributor.committeeMemberDeters, Ralphen_US
dc.contributor.committeeMemberMcCalla, Gorden_US


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record