Reengineering of Module for Public Sector & Complexity Measurement

Table of contents

1. INTRODUCTION

oday public sector is an integral part of Govt. and performance of it, has considerable scope for improvement. However, these sector such as govt. hospital, depends on information system, which have been engineered in earlier days, such legacy system using procedural methodology, db handling , GUI etc. As services grow in size or the requirement of public increases continuously, due to this there is accelerating need software maintenance. It has been observed that, the cost of the maintenance is much higher than the cost of reengineering of the software. And also continue maintenance of such system become tedious and cost approach and occurrence of software failure is more due to poor documentation, poorly structured & transparency, and also changes technology infra structured in hardware and software, complexity of module increases continuously, and finally logic code written is outdated hardware and software. Therefore, maintenance is not a good choice. Reengineering, is much better than maintenance. It is an approach to solve problem of legacy system. Its aim is the qualitative improvement of existing software and the extension of its life expectancy. It consists of examination (reverse engineering) and alteration (forward engineering) of legacy system.

2. II.

3. PURPOSED WORK

The purposed methodology, used to reengineering of module of public sector i.e. more suitable, for available tools and techniques. It will create significant improvement to measure the complexity and Author : Professor, Department of Computer Science & Application Kurukshetra University, Kurukshetra, India. E-mail : [email protected] Author : Asst. Professor, Computer Science & Engg. Vaish College of Engineering, Rohtak, India. E-mail : [email protected] effort of module individually by using Excel Template [9]. The Excel Template that is used to measure complexity of each and every modules of hospital are Modified Method Hiding Factor It also specifies causes of errors and the use of the safety design concepts, to prevent minimize errors by detecting them, before undesirable effect takes place. The excel template provides facility to reengineering the modules in such a way that help enables the doctors to better serve their patients, Reducing the time spent by staff filling out forms, Control over the costs incurred by diagnosis -related groups, Increased nursing productivity, Faster and informed decision-making by doctors, Improve decision support for the management, Cost-effective patient transactions.

4. III.

5. PROBLEM DESCRIPTION

HMS is powerful, flexible, easy to use and has designed & developed to deliver real conceivable benefits to hospitals and clinics. It is designed for multi specialty hospitals, to cover a wide range of hospital administration and management processes.

Hospital Management System is a product of our deep experience in delivering successful solutions to various customers in the healthcare space and our expertise in developing unique Intellectual Property in the form of products and re-usable components for the Healthcare Industry. Conventional methodology, based on SDLC, there is no way to measurement of complexity and effort of module during reengineering of module as well as this methodology not support reusability and also productivity of module not very much effective.

Structured Methodology is slightly improvement of conventional methodology. If we reengineering the module by using this methodology, it help to measure control but not support reusability, but help in productivity and quality of analysis and design. It will provide more effective analysis & more stable or maintainable design. However, both these methodology not support today's available tool and techniques.

6. IV.

7. RESULTS AND DISCUSSION

There are twelve excel template that are used to determine complexity of module that are more efficient as compared to other methodologies. Six excel template [9] such as M-MHF, M-AHF, M-MIF, M-AIF, M-PF & M-CF are used to determine complexity of each and every module of the system, as well as it also provides facilities to hide information, to increase reusability & productivity of modules, measure the degree of method overriding in class inheritance and also measure degree of coupling among different types of modules.

Other six excel template [9] , such as M-WMC, M-DIT, M-NOC, M-CBO, M-RFC & M-LCOM, are used to determine effort i.e. required to reengineering of the module during Post Martem Methodology [1 2,3] . The purposed methodology also, allows the developer to communicate using well-known, well understood names for the software interactions. Common design pattern can improved over time, making them more robust than ad-hoc (in-formal or unplanned) design.

V.

8. CONCLUSION

Overall objective of this paper, is that modules are design in such a way that if any time any where any module need for reengineering in future, it is easily takes place. As well as it provides facilities to determine complexity [3,4] and effort from that module, where reengineering happens. It does not need to determine complexity of entire modules again and again. And it will focus on optimization and increase productivity [7], reusability [7] , flexibility [7] , understandability and also support reliability of modules [10] .

Figure 1.
(M-MHF), Modified Attributes Hiding Factor (M-AHF), Modified Method Inheritance Factor (M-MIF), Modified Attributes Inheritance Factor (M-AIF), Modified Coupling Factor (M-CF), and Modified Polymorphism Factor (M-PF); And the Excel Template that are used for measuring effort of each and every modules of hospital during reengineering of the modules are, Modified Weighted Method Per Class (M-WMC), Modified Depth of Inheritance (M-DIT), Modified Number of Children (M-NOC), Modified Coupling Between Object (M-CBO), Modified Response for a class (M-RFC) and Modified Lack of Cohesion in Method (M-LCOM).
Figure 2. T © 2011
2011Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XVI Version I 25 2011 September Reengineering of Module for Public Sector & Complexity Measurement Keywords The legacy system (i.e. hospital) is engineered by using Conventional and Structured Methodology.
Figure 3. Fig. 1 :
1Fig.1 : 'The above graph show complexity of reengineering of module by using values given in table 1
Figure 4. Fig. 2 :
2Fig. 2 : 'The above graph show effort required during reengineering of module by using value given in table 2' The design of modules based on purposed methodology provides facilities such as: It enables the doctors to better serve their patients. Reducing the time spent by staff filling out forms. Control over the costs incurred by diagnosisrelated groups. Increased nursing productivity. Faster and informed decision-making by doctors Improve decision support for the management Cost-effective patient transactionsThe purposed methodology also, allows the developer to communicate using well-known, well understood names for the software interactions. Common design pattern can improved over time, making them more robust than ad-hoc (in-formal or unplanned) design.
Figure 5. Table 1 :
1
determined by Complexity Measurement Template'
Sr Post Martem Conventional
No Activity Methodology methodology
1 H HMS Staff 36.5141 60
2 E Emergency 70.47 85
3 E Enquiry 46.806 78
4 OPD 52.9121 75
5 M Managing Unit 51.8 77
Doctor
6 Examination 33.1916 56
7 N Nurse Detail 36.914 62
8 P Patient Status 20.4 56
9 P Pharmacy/Drug 61.2712 80
10 Laundry 33.4272 75
11 Kitchen 33.4272 75
Figure 6. Table 2 :
2
Reengineering of Module for Public Sector & Complexity Measurement
Sr No Activity M-WMC M-DIT M-NOC M-CB0 M-RFC M-LCOM
1 HMS Staff 3 4 3 2 2 3
2 Emergency 3 9 3 1 2 4
3 Enquiry 3 3 4 2 2 4
4 OPD 2 20 4 2 2 4
5 Managing Unit 5 20 9 4 4 5
6 Doctor Exam 2 8 3 1 2 4
7 Nurse Detail 2 9 3 1 2 4
8 P Patient Status 3 4 5 2 2 2
9 Pharmacy/Drug 4 14 7 3 2 4
10 Laundry 1 2 1 1 2 2
11 Kitchen 1 2 1 1 2 2
1
2

Appendix A

  1. IEEE Standard for a Software Quality Metrics Methodology, 1998. p. . Software Engineering Standards Committee of the IEEE Computer Society
  2. The process redesign-the implementation guide for managers, A R Tenner , I J Detoro . 1992. New Jersey: Prentice Hall.
  3. An Empirical Study of Representation Methods for Reusable Software Components. B William , Thomas P Frakes , Pole . IEEE Transactions on Software Engineering August 1990. 20 (8) p. .
  4. A methodology and modeling technique for systems of BDI agents. D; Kinny , M Georgeff , A Rao . LNAI 1996. Springer Verlag. 1038.
  5. Evaluating Software Complexity Measures. Elaine J Weyuker . IEEE Transactions on Software Engineering 1988. 14 (9) p. .
  6. A methodology for business redesign: experience and issues. G W Wastell , P White , P Kawalek . Journal of Strategic Information Systems 1994. 3 (1) p. .
  7. Developing interpretable models with optimized set reduction for identifying high-risk software components. Lionel C Briand , Victor R Basili , Christopher J Hetmanski . IEEE Transactions on Software Engineering November 1993. 19 (11) p. .
  8. Business process reengineering: a consolidated methodology. S Muthu , L Whitman , H S Cheraghi . Proceedings of the 4th Annual International Conference on Industrial Engineering Theory, Applications and Practice, (the 4th Annual International Conference on Industrial Engineering Theory, Applications and Practice) 1999.
  9. Business process change: a study of methodologies, techniques, and tools. W J Kettinger , J T C Teng , S Guha . MISQ Quarterly March, 1997. p. .
  10. The C Information Abstraction System. Yin-Farn Chen , Michael Y Nishimoto , C V Ramamoorthy . IEEE Transactions on Software Engineering March 1990. 16 (3) p. .
Notes
1
© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XVI Version I 26
2
© 2011 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XI Issue XVI Version I 28 2011 September This page is intentionally left blank
Date: 2011-08-20