Search

The Use Case Diagram (UCD) is a visual form of system design that helps software developers comprehend the system behavior. Maintaining and updating the system can be a difficult task when it has no visualization of a system behavior or software requirement specification document. Reverse engineering is an approach used to extract software requirement specifications from the existing systems. Research in reverse engineering has shown various techniques in which the processes are not fully understood. This study analyzes the University Community Services Information System (UCSIS) as the existing system in three processes: identifying the system domain process, elaborating system features by implementing the event table, and constructing the use case realization. The results showed that a UCD could be generated through the reverse engineering process on the existing system. Furthermore, a new feature for system improvement can also be detected using this method. It is expected that the reverse engineering approach in this study can be used as guidance for the software development team in extracting the use case diagram from the existing systems. [ABSTRACT FROM AUTHOR]

The existing works of software watermarking have the intrinsic defects: watermarking is independent of program semantics and have weak strength and resilience to state-of-the-art reverse engineering such as symbolic execution, dynamic taint analysis and theorem proving. In this paper, we propose a semantic-integrated watermarking with tamper-proofing to mitigate such problems. This work chooses neural network as the “integrator” and skillfully integrates the watermarking and tamper-proofing module into program semantics. The difficult of reverse engineering or tampering with watermarked program is equal to extracting the rules from neural networks, which had be proven as a NP-hard problem. We have deployed our work in SPECint-2006 benchmarks to evaluate the overhead, strength and resilience. Experiment results show that our watermarking could effectively resist the state-of-the-art reverse engineering, and the introduced overhead is acceptable. [ABSTRACT FROM AUTHOR]

A domain model can provide compact information about its corresponding software system for business people. If the software system exists without its domain model and documentation it is time-consuming to understand its behavior and structure only from the code. Reverse Engineering (RE) tools can be used for obtaining behavior and structure of the software system from source code. After that the domain model can be created. A short overview and an example of obtaining the domain model, Topological Functioning Model (TFM), from source code are provided in the paper. Positive and negative effects of the process of TFM backward derivation are also discussed. [ABSTRACT FROM AUTHOR]

Software reverse engineering involves analyzing computer program executables to understand their structure, functionality, and behavior. In this paper, common reverse engineering functions are decomposed to isolate the information-processing and sensemaking subtasks involved. This paper reviews the applicable literature on eliciting mental models of software reverse engineers. Based on the literature, a taxonomy of common processes is developed which leads to a methodology to elicit and represent reverse engineers' mental models of the tasks. [ABSTRACT FROM AUTHOR]

Reports on the recent actions against reverse engineering in Great Britain. Definition of reverse engineering; Reasons for reverse engineering; Exceptions permitting reverse engineering of computer programs.