International Journal of Computer Science Engineering and Information Technology Research (IJCSEITR) ISSN(P): 2249-6831; ISSN(E): 2249-7943 Vol. 3, Issue 5, Dec 2013, 115-128 © TJPRC Pvt. Ltd. REVERSE ENGINEERING OF CLINICAL SOFTWARE AND TYPES OF HAZARD LALITA M. LOKHANDE & N. V. KALYANKAR Department of Computer Science, Yeshwant Mahavidyalaya, Nanded, Maharashtra, India ABSTRACT This paper is based on the hazards of Reverse Engineering Software of the system’s code, documentation and behavior to create system abstractions and design information. Reverse engineering processes were used as a part of a software development, an implementation of a better program and to upgrade the existing documentation. The experiments carried out by recovering the information and it will implemented, dealing with some incomplete part of information and reverse engineering. The different types of Hazards are found in reverse engineering of the software, in this paper we have studied only few types hazards of reverse engineering of the software. To achieve this functionality, we have come across the situations like, how to load selected employee's entire record to main screen. This software has multifunctional uses a property which keeps data of salary, attendance, blood analysis and other types clinical test data of patient. KEYWORDS: Reverse Engineering, Types of Hazards, Codes of Software INTRODUCTION The practice of software engineering practice tends to focus on the design and implementation of a software product without considering its lifetime[1], usually ten years or more. However, the major effort in software engineering organizations is spent after development on maintaining the systems to remove existing errors and to adapt them to changed requirements. Furthermore, reverse engineering is the process of learning the design of an object by studying its implementation. The core of reverse engineering consists in deriving information from the available software artifacts and translating it into abstract representations more easily understandable by humans[2-3]. The benefits are maximal when it is supported by tools. Reverse engineering can extract design information from source code, but the abstraction level, the completeness of the documents, the degree to which tools and a human analyst work together (interactivity), and the directionality of the process are highly variable[4]. The completeness of a reverse engineering process refers to the level of details that is provided at an abstract level. In most cases, completeness decreases as the abstraction level increases. For example, when a source code listing is given, Reverse engineering process refers to the completeness level of details that is provided at an abstract level[6]. In most cases, abstraction level will increases and completeness decreases. For example, when a source code listing is given, a complete procedural design representation is relatively easy to develop. Completeness depends on the way how the reverse engineer performs the analysis. Interactivity refers the human integration with automated tools which he used to create an efficient process of engineering. As abstraction level increases, interactivity must increase or completeness will suffer. Related Work Reverse engineering process is directionally one-way; all the information extracted from the source code is provided to the software engineer who can then use it during any maintenance activity[7-8]. In other case, where the