Software Product Lines (SPLs) refer to some software engineering methods, tools and techniques for creating a collection of similar systems from shared set assets using common means production. This concept is recognized as successful approach reuse in development. Its purpose reduce production costs by reusing existing features managing the variability between different products with respect p...

In this paper, Section II represents the OSS case studies of GIPSY and DMARF. All the summaries of team members were gathered together and defined a decent background for both GIPSY and DMARF separately and participates in presenting the metrics definition. The Metrics presented are of the DMARF and GIPSY measured using Logiscope. Table 3 in Section II.C outlines the individual selection of OSS...

Build systems are crucial for software system development. However, there is a lack of tool support to help with their high maintenance overhead. GNU Autotools are widely used in the open-source community, but users face various challenges from its hard to comprehend nature and staging of multiple code -generation steps, often leading to low quality and error-prone build code. In this paper, we...

The deeper problem in the source code are the bad smells that indicates something is wrong and if they are not detected timely, then they lead towards the complete deterioration of the working software causing major financial and productivity loss. Refactoring helps in removing these bad smells by improving internal quality attributes of the software without affecting its external behaviour. Ho...

Although architectural smells are one of the most studied type technical debt, their impact on maintenance effort has not been thoroughly investigated. Studying this would help to understand how much debt interest is being paid due existence architecture and can be calculated. This work a first attempt address issue by investigating relation between source code changes. Specifically, we study w...

Code smells are symptoms of poor design, leading to future problems, such as reduced maintainability. Therefore, it becomes necessary understand their evolution and how long they stay in code. This paper presents a longitudinal study on the survival code (CS) for web apps built with PHP, most widely used server-side programming language development seldom studied.

iii 谨将此论文 献给敬爱的父亲，罗孝杨 对您的怀念将伴我一生 和我的家人 母亲，蒋亚平 爷爷， 罗重秀 奶奶， 蒋金莲 外公， 蒋荣陪 外婆， 黄淑华 公公， 周垠庚 阿婆， 蒋宏英 岳母， 曾桂芳 你们的关爱是我完成此文的动力之源 iv Acknowledgements I express my deepest gratitude to Dr. Doris Carver, my supervising professor, for her guidance, patience, and encouragement throughout my graduate studies. It is an honor and a blessing for being her student. She has a great knowledge and her wisdom is secon...

To maintain software and enhance its code quality, code smell, i.e., undesired design flaws need to be detected. However, as the system size increases, manual smell detection becomes difficult. In this paper, a static code analysis framework, named code sniffer, is proposed to detect code smells with predicting their risk severity. This has been calculated using code metrics, and defined as low...

Code smells are structures in code that often harm its quality. Manually detecting is challenging, so researchers proposed many automatic detectors. Traditional smell detectors employ metric-based heuristics, but have recently adopted a Machine-Learning (ML) based approach. This paper compares the performance of multiple ML-based detection models against heuristics for God Class and Long Method...