Providing Component-Based Software Crash Diagnostic Information for JAVA using Program Slicing
| dc.contributor | 鄭永斌 | zh_TW |
| dc.contributor.author | 鐘淳文 | zh_TW |
| dc.date.accessioned | 2019-09-05T11:10:44Z | |
| dc.date.available | 2005-07-19 | |
| dc.date.available | 2019-09-05T11:10:44Z | |
| dc.date.issued | 2005 | |
| dc.description.abstract | The software nowadays is a black box to end user. It can allow users to configure which components to install, such as plug-in, and etc. But, after such initial configurations, the software remains as an abstract black box to end user. End users have no clues in the component inside a software. When software crash, end users can only accept the fact but can do nothing else. Unlike software, some daily used hardware, or consumer appliance may allow some extent of user configurations. For example, we can replace a malfunctioned part of a desktop computer by ourselves through some simple inspection and diagnosis. In this thesis, we propose a solution to address such issue. We use Java Class loader to execute a Java application and catch the exception when it occurs. Then, we use a Java parser to construct the component map of a Java application to show the architecture of the software to end-user. Program slicing technique is used to collect slices of each statement in the Java application. These slices are stored in XML format. When the Java application crashes and emits an exception, our monitor system catch the exception and conjecture the cause of exception via the slicing information stored in those XML. We compute a probability of each component in the component map. The probability shows the likelihood of the component to cause the crash of the application. | zh_TW |
| dc.description.abstract | The software nowadays is a black box to end user. It can allow users to configure which components to install, such as plug-in, and etc. But, after such initial configurations, the software remains as an abstract black box to end user. End users have no clues in the component inside a software. When software crash, end users can only accept the fact but can do nothing else. Unlike software, some daily used hardware, or consumer appliance may allow some extent of user configurations. For example, we can replace a malfunctioned part of a desktop computer by ourselves through some simple inspection and diagnosis. In this thesis, we propose a solution to address such issue. We use Java Class loader to execute a Java application and catch the exception when it occurs. Then, we use a Java parser to construct the component map of a Java application to show the architecture of the software to end-user. Program slicing technique is used to collect slices of each statement in the Java application. These slices are stored in XML format. When the Java application crashes and emits an exception, our monitor system catch the exception and conjecture the cause of exception via the slicing information stored in those XML. We compute a probability of each component in the component map. The probability shows the likelihood of the component to cause the crash of the application. | en_US |
| dc.description.sponsorship | 資訊工程學系 | zh_TW |
| dc.identifier | G0069247004 | |
| dc.identifier.uri | http://etds.lib.ntnu.edu.tw/cgi-bin/gs32/gsweb.cgi?o=dstdcdr&s=id=%22G0069247004%22.&%22.id.& | |
| dc.identifier.uri | http://rportal.lib.ntnu.edu.tw:80/handle/20.500.12235/106319 | |
| dc.language | 英文 | |
| dc.subject | Java parser | zh_TW |
| dc.subject | Program slicing | en_US |
| dc.title | Providing Component-Based Software Crash Diagnostic Information for JAVA using Program Slicing | zh_TW |
| dc.title | Providing Component-Based Software Crash Diagnostic Information for JAVA using Program Slicing | en_US |
Files
Original bundle
1 - 5 of 6