1.4 Research Methods
To answer the first research question, I made a literature study on the source code metrics and the bad code smells. Based on what I had learned from the literature, I tried to propose possible measures for the smells and evaluate how measurable the smells are. The measurability would be based on my personal evaluation of how good a chance the measure has of detecting the smell correctly.
To answer the second research question, I utilized the information gathered from the literature and my personal knowledge as a programmer. Based on this I created a taxonomy that maps the 22 smells to 7 higher-level categories.
To answer the research questions 3, 3a, and 4, I conducted a web-based survey in which the developers of the case company participated. The survey contained 22 questions that asked each respondent to evaluate how much of each smell exists in the modules they had primarily worked with. The case company had 18 Software developers and 12 of them participated the survey. To answer the research question 3, I used the developers' opinions on the bad code smells. Then I studied how uniformly the developers had evaluated the particular smells in the same software modules. In this effort, I uscd the standard deviation of the smell evaluation in a particular module. In research question 3a I tried to find
In this work, the bad code smells are studied empirically and their rclabonship source code metrics is evaluated. This work also presents an initial taxonomy for the bad code smell, which improves their understandability and feasibility The bad code smells, presented by Martin Fowler and Kent Beck, are dissatisfactory structures in the source code of software that decrease software quality by making it less maintainable. The maintainability of software is important, because it is one of the factors affecting the cost of the future development activities. The literature study looks at the concept of software maintainability, discusses how software maintainability can be measured, and provides motivation and migration techniques to achieve more maintainable software. Based on the literature study, this work proposes a taxonomy for the bad code smells and evaluates the measurability of each bad code smell with source code metrics. A survey is used to collect the developers' opinions on the existence of bad code smells in particular software modules. The results of this survey show that the developers' opinions on a particular smell in a particular software module are not very uniform. The survey also provides more support to the theoretical taxonomy by showing that there are many strong correlations within the taxonomy's categories This study also compares the results of the smell survey to the source code metrics collected with automatic tools. The results show that developers' evaluations of the bad code smells do not correlate with the actual source code metrics. This means that the smell evaluations from developers are not very reliable and that there is a need for
1.4 ระเบียบวิธีวิจัย ตอบคำถามวิจัยแรก ฉันทำเป็นเอกสารประกอบการศึกษาดรหัสแหล่งที่มา และรหัสไม่ดีกลิ่น ขึ้นอยู่กับสิ่งที่ฉันได้เรียนรู้จากวรรณคดี พยายามที่จะเสนอมาตรการที่เป็นไปได้กลิ่น และมีกลิ่นวิธีวัดประเมิน Measurability ที่จะยึดตามการประเมินของฉันส่วนบุคคลโอกาสวัดได้ตรวจกลิ่นอย่างไรดี ตอบคำถามวิจัยที่สอง ฉันใช้ข้อมูลที่รวบรวมจากวรรณคดีและความรู้ส่วนบุคคลของฉันเป็นโปรแกรมเมอร์ ตามนี้ สร้างระบบภาษีที่แมปกลิ่น 22 ประเภทสูงกว่า 7 ตอบคำถามการวิจัย 3, 3a และ 4 ฉันดำเนินการสำรวจเว็บไซต์ที่นักพัฒนาของบริษัทกรณีเข้าร่วม แบบสำรวจประกอบด้วย 22 คำถามที่ถามผู้ตอบแต่ละการประเมินจำนวนของแต่ละกลิ่นมีอยู่ในโมดูลหลักพวกเขาได้ทำงานกับ กรณีมีผู้พัฒนาซอฟต์แวร์ 18 และ 12 ของพวกเขาเข้าร่วมการสำรวจ ตอบคำถามการวิจัย 3 ฉันใช้ความคิดเห็นของนักพัฒนาในกลิ่นรหัสไม่ถูกต้อง แล้วเรียนสม่ำเสมอเมื่อเทียบเคียงว่านักพัฒนามีประเมินกลิ่นเฉพาะในโมดูลซอฟต์แวร์เดียวกัน ในความพยายามนี้ ฉัน uscd ส่วนเบี่ยงเบนมาตรฐานของการประเมินกลิ่นในโมดูลเฉพาะ ใน 3a คำถามวิจัย ได้พยายามค้นหาIn this work, the bad code smells are studied empirically and their rclabonship source code metrics is evaluated. This work also presents an initial taxonomy for the bad code smell, which improves their understandability and feasibility The bad code smells, presented by Martin Fowler and Kent Beck, are dissatisfactory structures in the source code of software that decrease software quality by making it less maintainable. The maintainability of software is important, because it is one of the factors affecting the cost of the future development activities. The literature study looks at the concept of software maintainability, discusses how software maintainability can be measured, and provides motivation and migration techniques to achieve more maintainable software. Based on the literature study, this work proposes a taxonomy for the bad code smells and evaluates the measurability of each bad code smell with source code metrics. A survey is used to collect the developers' opinions on the existence of bad code smells in particular software modules. The results of this survey show that the developers' opinions on a particular smell in a particular software module are not very uniform. The survey also provides more support to the theoretical taxonomy by showing that there are many strong correlations within the taxonomy's categories This study also compares the results of the smell survey to the source code metrics collected with automatic tools. The results show that developers' evaluations of the bad code smells do not correlate with the actual source code metrics. This means that the smell evaluations from developers are not very reliable and that there is a need for
การแปล กรุณารอสักครู่..