Software Design Change Artifacts Generation through Software Architectural Change Detection and Categorisation
| dc.contributor.committeeMember | Gokaraju, Ramakrishna | |
| dc.contributor.committeeMember | Codabux, Zadia | |
| dc.contributor.committeeMember | Mondal, Manishankar | |
| dc.contributor.committeeMember | Yoshida, Norihiro | |
| dc.creator | Mondal, Amit Kumar | |
| dc.date.accessioned | 2023-01-26T19:22:06Z | |
| dc.date.available | 2023-01-26T19:22:06Z | |
| dc.date.copyright | 2022 | |
| dc.date.created | 2023-01 | |
| dc.date.issued | 2023-01-26 | |
| dc.date.submitted | January 2023 | |
| dc.date.updated | 2023-01-26T19:22:06Z | |
| dc.description.abstract | Software is solely designed, implemented, tested, and inspected by expert people, unlike other engineering projects where they are mostly implemented by workers (non-experts) after designing by engineers. Researchers and practitioners have linked software bugs, security holes, problematic integration of changes, complex-to-understand codebase, unwarranted mental pressure, and so on in software development and maintenance to inconsistent and complex design and a lack of ways to easily understand what is going on and what to plan in a software system. The unavailability of proper information and insights needed by the development teams to make good decisions makes these challenges worse. Therefore, software design documents and other insightful information extraction are essential to reduce the above mentioned anomalies. Moreover, architectural design artifacts extraction is required to create the developer’s profile to be available to the market for many crucial scenarios. To that end, architectural change detection, categorization, and change description generation are crucial because they are the primary artifacts to trace other software artifacts. However, it is not feasible for humans to analyze all the changes for a single release for detecting change and impact because it is time-consuming, laborious, costly, and inconsistent. In this thesis, we conduct six studies considering the mentioned challenges to automate the architectural change information extraction and document generation that could potentially assist the development and maintenance teams. In particular, (1) we detect architectural changes using lightweight techniques leveraging textual and codebase properties, (2) categorize them considering intelligent perspectives, and (3) generate design change documents by exploiting precise contexts of components’ relations and change purposes which were previously unexplored. Our experiment using 4000+ architectural change samples and 200+ design change documents suggests that our proposed approaches are promising in accuracy and scalability to deploy frequently. Our proposed change detection approach can detect up to 100% of the architectural change instances (and is very scalable). On the other hand, our proposed change classifier’s F1 score is 70%, which is promising given the challenges. Finally, our proposed system can produce descriptive design change artifacts with 75% significance. Since most of our studies are foundational, our approaches and prepared datasets can be used as baselines for advancing research in design change information extraction and documentation. | |
| dc.format.mimetype | application/pdf | |
| dc.identifier.uri | https://hdl.handle.net/10388/14448 | |
| dc.language.iso | en | |
| dc.subject | Architectural change | |
| dc.subject | categories | |
| dc.subject | design document | |
| dc.subject | automated technique | |
| dc.title | Software Design Change Artifacts Generation through Software Architectural Change Detection and Categorisation | |
| dc.type | Thesis | |
| dc.type.material | text | |
| thesis.degree.department | Computer Science | |
| thesis.degree.discipline | Computer Science | |
| thesis.degree.grantor | University of Saskatchewan | |
| thesis.degree.level | Doctoral | |
| thesis.degree.name | Doctor of Philosophy (Ph.D.) |