[雙語翻譯]計(jì)算機(jī)類外文翻譯原文使用java異常堆棧跟蹤來改進(jìn)中級(jí)java學(xué)習(xí)者的漏洞修復(fù)技巧（國(guó)外作者，字符數(shù)17000）

1、Use of Java Exception Stack Trace to Improve Bug Fixing Skills of Intermediate Java Learners Trupti S. Indi1, Pratibha S. Yalagi2 and Manisha A. Nirgude3 Assistant Professor, Department of Information Technology Walchand

2、 Institute of Technology Solapur, India. Abstract—Today industry demands attention towards the software quality in the development process than only software delivery. The quality of software can be measured, monitored

3、 and tested during different phases of software development lifecycle. Major failures of software affect money as well as the reputation of a company. In this scenario, fixing bugs in less time is an important factor.

4、 Today’ s challenge for engineering students is to have program writing skills as well as bug fixing skills and complete the task in stipulated time period. Here, we present the experiment on how bug fixing skills are

5、improved. We have conducted the experiment during Java programming course for Third Year students of Information Technology discipline. This experiment was to use Java exception stack trace to find bugs in Java progr

6、am and fix them in stipulated time. To test the effect of this experiment, a pre-test post-test experimental study along with perception survey was carried out. We found that more than 65% students were successful in

7、fixing bugs in stipulated time and about 20% students were able to fix bugs, but not in stipulated time. About 80-85% students were in state to analyze and fix the bugs in program. Keywords— Java prgramming, debugg

8、ing, Java exception stack trace, exception handling, bug fixing skills I. INTRODUCTION Computer programming is fundamental course in engineering curriculum. Various computer programming languages added in this c

9、ategory are C programming language, C++, C#, Java and others. These computer programming languages are basic building blocks required for software development process. The students should have good knowledge of compu

10、ter programming concepts which includes program writing skills, problem solution design skills, program analyzing skills and program debugging skills. Today industry demands attention towards the software quality in

11、the development process than only software delivery. The quality of software can be measured, monitored and tested during different phases of software development lifecycle. All these facts need be elaborated to the s

12、tudents while teaching programming courses. Only knowledge of program writing skills are not sufficient in today’s teaching- learning process [8]. Along with program writing skills, bug fixing skills helps students t

13、o write quality program. In many practical systems, such as servers, android platform based systems and devices and embedded system, the Java is highly demanding programming language due to its object-oriented featu

14、res, robustness, portability and security features [7]. So IT industries demands for good Java programmers in terms of program writing skills and bug fixing skills. In this paper, we have presented the experiment, cond

15、ucted during Java programming course for Third Year students of Information Technology discipline. The main objective of this experiment was to use Java exception stack trace to understand exception in Java program a

16、nd fix error in program in stipulated time. In presented experiment, a pre-test post-test experimental study along with perception survey was carried out. In section II related work regarding different teaching methodo

17、logies used to teach Java programming language concepts and debugging methods presented. In Section III explains the background study behind this experiment and Section IV illustrates methodology followed in this exp

18、eriment includes samples used, experimental setup and instruments used. Experiment results and students feedback described in Section V. This is followed by discussion in section VI and conclusion in section VII. II.

19、 LITERATURE REVIEW Various experiments conducted to study and use stack trace in debugging. Adrian Schroter, Nicolas Bettenburg and Rahul Premraj [1] conducted an experiment to know that do stack traces help speed up

20、debugging. They explained how stack traces indicates which parts of the code could contain the defect and this helps speed up debugging. Also Shujuan Jiang, Hongchang Zhang, Qingtan Wang and Yanmei Zhang [2] presente

21、d a debugging approach for Java Runtime Exceptions based on program slicing and stack traces for locating faults in Java programs that cause runtime exceptions. In their approach, first program slicing used to reduce

22、the search scope, and then backward data flow analysis is performed starting from the point where the exception occurred. Then stack trace information is used to guide the analysis to determine the source statement t

23、hat is responsible for the runtime exception. There are difficulties in understanding exception-handling mechanism which explained by Rashkovits Rami and Lavy Ilana [3]. Also they focused on improving the student

24、s' ability to properly utilize the advanced properties of exceptions to produce higher quality software. The study conducted by Ioana Tuugalei Chan Mow on novice programming errors in Java programming and aimed a

25、t identifying what are the common types of programming errors students make based on the categorization as syntax, semantic and logical errors. The study ascertained common programming errors but did not look at

26、 the time taken by 2016 International Conference on Learning and Teaching in Computing and Engineering978-1-5090-2504-6/16 $31.00 © 2016 IEEE DOI 10.1109/LaTiCE.2016.9 194in those programs and to execute those progr

27、ams successfully. Every student’s program execution status and time duration was noted down. After conducting pre-test, teacher taught “ Java Exception Stack Trace concept” in the classroom. During this lecture, how

28、to read and interpret Stack trace was explained. Java Exception Stack Trace was illustrated with the help of demo examples and power point presentations. Next day, post-test was conducted in programming lab. In this t

29、est, three programs with errors given to students and also time duration mentioned to student to successfully execute respective program. Post-test’s program execution status and time duration noted down for each stu

30、dent. C. Instruments Used: To test the effect of this experiment two tests were designed by a teacher, a pre-test and a post-test. In order to collect students' feedback regarding use of Java exception stack trace

31、 for fixing bugs, a survey questionnaire was designed and conducted. Fig 1: Sample Program from Pre-Test 1) Pre-test: A Pre-test was conducted to know the bug fixing ability of students. Three programs with predefined

32、 errors were given to the students to fix bugs in predetermined time period. One of the sample program used in Pre-Test is shown in Fig 1. As the output of this test, for every program actual time taken by student, a

33、t the start number of exceptions and at end of given time period number of exceptions were noted down. Sample assessment sheet is shown in Fig. 2. 2) Post-Test After “ Java Exception Stack Trace” concept explanation, n

34、ext-day Post-test was conducted to check the effect of use of Java exception stack trace to fix bugs in program. This test was including three programs which were similar at cognitive level to pre-test programs. One of

35、 the sample program used in Post- Test is shown in Figure 3. The assessment method for the pos- test was similar to assessment method used in pre-test as shown in Figure 4. Fig 2: Assessment method for Pre-Test Fig 3:

36、Sample Program from Post-Test Pre-test and post-test programs were validated by Java programming experts before conducting test. The content validity was checked and also the two tests were checked for equivalence. Pr

37、e-Test Assessment sheet Student Information: Name: Sign: Roll#: Class: Date: Program1: (FileName: FileNotFoundExceptionExample.java) Time given to complete: 5 mins Sr# Parameter Answer 1. At start: number of Exception

38、s 2. At End: number of Exceptions 3. Actual time taken Program2: (FileName: Stud_db.java) Time given to complete: 10 mins Sr# Parameter Answer 1. At start: number of Exceptions 2. At End: number of Exceptions 3. Actual

39、 time taken Prgram3: (Concept: Remote Method Invocation in Java) Time given to complete: 10 mins Sr# Parameter Answer 1. At start: number of Exceptions 2. At End: number of Exceptions 3. Actual time taken Program1:(Fil

40、eName: FileNotFoundExceptionExample.java) import java.io.BufferedReader; import java.io.File; import java.io.FileReader; import java.io.IOException; public class FileNotFoundExceptionExample { private static final

41、 String filename = “input.txt“; public static void main(String[] args) { BufferedReader rd = null; try { // Open the file for reading. rd = new BufferedReader(new FileReader(new File(filename))); // Read all content

42、s of the file. String inputLine = null; while((inputLine = rd.readLine()) ! = null) System.out.println(inputLine); }catch(IOException ex) { System.err.println(“Exception1: An IOException was caught! “); }finally { //

43、Close the file. try { rd.close(); }catch(IOException ex) { System.err.println(“Exception2: An IOException was caught! “); } } } } Program1: (FileName: file.java) import java.io.FileReader; import java.io.FileW

44、riter; import java.io.IOException; public class file { public static void main(String[] args){ FileReader inputStream = null; FileWriter outputStream = null; try { inputStream = new FileReader(“xanadu.txt“); outpu

45、tStream = new FileWriter(“characteroutput.txt“); int c; while ((c = inputStream.read()) ! = -1) { outputStream.write(c); } } finally { if (inputStream ! = null) { inputStream.close(); } if (outputStream ! = null)