A PERSPECTIVE SOURCE CODE ON SOFTWARE REENGINEERING APPLICATIONS

: Software Reengineering can be defined as the examination, analysis, and alteration of any existing software system to reconstitute it in a new form, and the subsequent implementation of the new form [12]. The current trends in software reengineering are “innovation for the third plat form”. Legacy is old. Developing on the third platform will accelerate in 2014. For developing a third platform require high skills of security, Social, Cloud, Mobile, Big Data/Analytics, IOT, HCI, Gamification, and Cognitive Computing. Daily as human beings, to use variable naming theories that they neither aware of nor understand, but by the end of the day our communication either forwards or backwards continue without understanding progress. This proposal is to apply a comprehensive Framework for extracting variable names from the source code, clean them through. This would be satisfied to show merely that the conditions within the framework can be used to help us achieve a mechanism for understanding at least some essential properties of the variable names within the system and how they are evolving over a given period of time. The question is to address is whether it is possible to have a framework for arriving at a critical decision as to how to use variable names in software reengineering. These modes of determination need play an important part in the explanation of mutual understanding, of communication.


INTRODUCTION
This research paper is a real time study in HealthCare Hospital and it's about the reengineering of existing system which has many named variable and to make the named variable meaningful in a particular environment the variable just have to be named domain specifically. Only the source code holds the key to successful application software reengineering with regards to cost, time to market, flexibility, and portability. This research paper proposes a Framework for extracting these variable names, from available source code, and cleaning them and then storing them in a database. This would satisfy to show merely that the conditions within the framework can be used to help us achieve a mechanism for understanding at least some essential properties of the variable names within the system and how they are evolving over a given period of time. To develop the process, designing phase is necessary and that design is created by the designer involved in that phase. The design is developed based on their idea and known technology. But it is necessary to convert the design according to the programming language used in the implementation phase. This conversion may leads to time consuming, when the programmer involves in this conversion since it has lot of work from identifying the tool to choosing the appropriate tool from the programming language implemented [7].

RELATED WORKS
The real time study is derived from the following references [1] Has discussed in Many modern software design methods have been developed to improve the reusability and maintainability of software and to reduce the time required for the maintenance and development operations, but many companies have old or legacy software systems, these companies spend a lot of money to maintain their old systems. These systems cannot be replaced by new systems because they contain implicit information and decisions cannot be lost. For these purposes, re-engineering becomes a useful tool to convert old, obsolete systems to more efficient, streamlined systems. [2] Models are new in the field of Reengineering of object oriented software systems. The future work is to test these models for suitability to fit on the basis of analysis of current and past data. These models can be accepted as it is or improved or rejected. Once fit and fine these models will help in reengineering the legacy software with optimal cost. [3] In this paper a systematic review of the work in the area of software reengineering is conducted and review results are presented. The review results shows that majority of the methodologies are process based, where a process is discussed to reengineer a legacy system, no validation or automatic tool is provided and the target legacy system is object oriented and orientation of the system are towards component based system. These results points out that most of the object oriented systems are becomes legacy now and software developers are more interested in migrating object oriented systems into component based systems. [4] This paper explains about the support of software metrics in Software reengineering. It clearly explains about the effect of metrics in the current system and how the metrics can be used in reengineering on the perspective of technical quality and business value. The collection of metrics for the new system can continue throughout development. To demonstrate, a metric framework has been used for reengineering process. This framework is used in different phases of the Rainfall model to make reengineering process easy, economical and efficient. Case study of software has been undertaken to validate this metric framework. The three Modules are integrated to form a framework to fully automate thereby eliminating the manual effort required thus making the system effective and efficient for the reengineering of the software. This framework applies metrics at both the levels design as well as code level by considering coupling of classes and objects. It generates spider graph to give the clear idea about the class coupling. It can identify high coupled class which may be vulnerable to attack in future.

CURRENT SYSTEM ANALYSIS
System analysis is the study of a system under consideration (which may be real or imagined). The main purpose is to understand and documentation of the essential characteristics of the system being studied. Its eventual goal is to come up with a specification of the system under study. In the above functions the first three is directly linked with the Operation of the healthcare domain and the rest two will be related to the supporting functions of the operation.

Figure 1 Existing System Framework
The Current software system has a lab master. The lab master consists of different lab such as hematology, blood glucose, liver, pathology, biometrics etc. The different forms have to be filled with different data's. The data updating will be in such a way that it can be filled manually or a pivot point or a drop box. After the data is updated in the appropriate fields the data access layer will be introduced to save data.

C. Program Creation in ASP.Net
From the software aspect for developing software they will find the requirement from the customer and convert the requirement into the software language and develop a work breakdown structure and provide the same to all programmers for developing the program as per the requirement of the customer. The ASP.Net programming is having the following flow of work process. The form creation is the ultimate requirement satisfaction of the research paper. The form is the presentation layer or application layer of the software system. It is how the user is interacting with the database to fetch or save data. The form is created with the help of ASPX coding. Databases are the ultimate source to store and maintain the data. It is also easy to retrieve the data from these databases than other source. This Re-Engineering technique also simplifies the process of the database operations using some implementations. Only the requirements are produced, the query will automatically generate and the result is produced [10]. The preparation of the coding sheet needs an in depth knowledge of coding and programming. The coding sheet provides the flow of function in the application layer. It defines the fields and variable required in the application layer.
Creating a basic  When they work with this data in ASP.NET, they will benefit by using common software patterns. One of these patterns is to separate the data-access code from the business-logic code that governs access to the data or that provides other business rules. In this pattern, these two layers are separate from the presentation layer, which consists of the pages that the Web site user accesses to view or change data [10].

a. Problem Faced in Existing System
• For each and every test the programmer needs to create a new ASP form and the subsequent Stored Procedure, Table Creation, Coding Sheet and Data Layer etc.
• In this format the entry of fields and variable were done manually by the end user who may lead to mistakes in the entries. • The Presentation layer form was created from a single design page which has more than 1500 no of codes. • While updating a page many updating comments are used to save, cancel update edit buttons are used. • The rectification of the error once occurred will be rectified with a tedious effort in updating the Coding sheet, table creation, Stored Procedure, Data and Business Layer • The Effort of the programmer was more in constructing the page and in rectifying the error

D. Significant of the study
This research paper will clearly explain about the existence software which has a separate form and application for each and every named variables is reengineered to a just by entering the variables in the presentation layer the software will capture the named variables and creates the forms in the application layer.
Only the source code holds the key to successful application software re-engineering with regards to cost, time to market, flexibility, and portability. This research paper proposes a Framework for extracting these variable names, from available source code, and cleaning them and then storing them in a database. The framework allows domain experts, assisted by the framework, to then conclude whether the names used are leading us towards or away from the actual domain or even that the words used are giving us enough knowledge and control of the subject under reengineering through a variable name scoring process. Propose to apply a comprehensive Framework for extracting variable names from the source code, clean them through. That would be satisfied to show merely that the conditions within the framework can be used to help us achieve a mechanism for understanding at least some essential properties of the variable names within the system and how they are evolving over a given period of time.
The question to address is whether it is possible to have a framework for arriving at a critical decision as how to use variable names in software reengineering. These modes of determination need play an important part in the explanation of mutual understanding, of communication. Or whether, as in the case of a name, it is sufficient for two people to understand one another that they know both associate with a predicate of the same reference. This is being achieved would mean it would be very possible for any person to read, understand source code that one has not written without problems and in the least possible timeframe.

E. Data Collection:
The Research paper is based on the exploratory research model which clearly explains a survey of related literature; experience survey such as focus Group and depth Interview; and Analysis of 'insight-stimulating' instances such as case studies. As a part of developing a program in an organization quantifying the work done will always exist in these cases the LOC is calculated at each layer through a separate framework developed by the focus group. The LOC Data Collection of different layers is as follows.

II. Comparison of the New System:
The line of code analysis existed in the old format and the new formats are as follows and the same is tabulated in table 1. •

CONCLUSION AND FUTURE WORK
Throughout this research paper, it has explored and closely followed the main reason why and how the application software ages overtime. The Approach is a gently skeptical approach, accepting and building on existing concepts and principles have to build a new more robust framework for extracting variable names from source code. The following contributions and conclusions may therefore be put forward • To developed a complete framework to explore source code files for variable names and their attributes; • To proposed several steps to be followed from extraction, cleaning, matching and storing the variable name; • As part of our Framework, to explore variable names from source code files, and also gone through several Software engineering principles.

Future Work
In our approach, it's clearly ignoring the effect of Architecture of the System as an Enterprise Solution.
The assumption that Architecture are not altered; only additional classes and variable names were added, subtracted or updated due to new business rules or change thereof. But no major rework has been conducted on the in as many as Architecture. However, where the Architecture have been altered, then a framework for understanding the Grammar and Architecture and a comprehensive follow-up of the same over a period of time has to be taken into consideration and mitigate all of them to come up with a comprehensive and wholesome Framework.