UML Based Visualization of Objects for Partial Software Reengineering

Sumesh Sood*, Arvind Kalia**, Hardeep Singh***, Shalini Sood****
* Assistant Professor, Department of Computer Applications, Swami Satyanand College of Management & Technology, Punjab, India.
** Professor, Department of Computer Science, Himachal Pradesh University, Shimla, Himachal Pradesh, India.
*** Professor, Department of Computer Science & Engineering, Guru Nanak Dev University, Punjab, India.
**** Lecturer, Department of Mathematics, M G S M Janta College, Punjab, India.
Periodicity:July - September'2010
DOI : https://doi.org/10.26634/jse.5.1.1210

Abstract

The law of software entropy dictates that even when a system start to function in a well-designed state, requirement of user changes and user demand new functionality. As the requirements of users change with the passage of time, it becomes mandatory to make changes in software. The new changes may result with the introduction of new bugs in the system. After some time it requires regular maintenance. To find whether software can be maintained, reengineer, or retire and build again, two metrics are proposed in this work. Proposed software reengineering metric (RRC and RRCM) can be used to calculate reengineering requirement cost of entire software and reengineering requirement cost of each Module. UML diagrams are used to identify different components of the software. The results obtained after applying the proposed metric become the basis for the decision whether there will be requirement of maintenance, reengineering or retirement of software.

Keywords

Software Reengineering, Partial Reengineering, UML, RRC, RRCM.

How to Cite this Article?

Sumesh Sood, Arvind Kalia, Hardeep Singh and Shalini Sood (2010). UML Based Visualization of Objects for Partial Software Reengineering. i-manager’s Journal on Software Engineering, 5(1),51-57. https://doi.org/10.26634/jse.5.1.1210

References

[1]. Abowd, G., et.al (1997). MORALE, Mission Oriented Architectural Legacy Evolution. Proceedings of International Conference on Software Maintenance, Bari (Italy), 150-159, October 1-3.
[2]. Abran, A., Moore, J. W., Bourque, P., & Dupuis, R. (2004). Guide to the Software Engineering Body of Knowledge, IEEE Computer Society, 1. Retrieved from http://www.computer.org/portal/web/swebok/html/forew ard.
[3]. Chiang, C.C. (2007). Software Stability in Software Reengineering. Proceedings of IEEE International Conference on Information Reuse and Integration, Las Vegas, 719-723.
[4]. Chikofsky, E.J., & Cross, J.H. (1990). Reverse engineering and Design Recovery: A Taxonaomy. IEEE Software, 7(1), 15.
[5]. Feiler, P.H. (July 1993). Reengineering: An Engineering Problem. Special Report CMU/SEI-93-SR-5.
[6]. Kalia, A., Singh, H., & Sood, S. (2008, April 19-20). Partial Reengineering: An Alternative to New Software Development. Proceedings of the Conference Enterprise Information Systems Technology, Ghaziabad, India, 20- 25.
[7]. Kalia, A., Singh, H., Sood, S., & Singh, J. (2009, March 7-8). Use of UML to Find the Objects for Software Reengineering. Proceedings of the Conference Innovative in Information Systems and Technology, Ghaziabad, India, 183-188.
[8]. Kazman, R., Woods, S.G., & Carriere, S.J. (1998, October 12-14). Requirements for Integrating Software Architecture and Reengineering Models: CORUM II. Proceedings of Working Conference on Reverse Engineering, Honolulu, HI, USA, 154-163.
[9]. Konda, K.R. (2005, July 1). Measuring Defect Removal Accurately. Proceeding of The Enterprise Development Conference, p. 35.
[10]. Mishra, S.K., Kushwaha, D.S., & Misra, A.K. (2009). Creating Reusable Software Component from Object- Oriented Legacy System through Reverse Engineering. Journal of Object Technology, 8(5), 133-152.
[11]. Pecht, M. (1995). Product Reliability, Maintainability, and Supportability Handbook. College Park, MD, USA: CRC Press.
[12]. Pressman, R.S. (2005). Software Engineering: A Practitioner's Approach. Singapore: McGraw-Hill International Edition, p. 889.
[13]. Putnam, L., & Meyers, W. (1992). Measure for Excellence: Reliable Software on Time, within Budget. Englewood Cliffs, NJ: Prentice Hall
[14]. Sellers, B.H. (1996). Object-oriented Metrics: Measures of Complexity. Sydney, Australia: Prentice Hall.
[15]. Singh, H., & Sood, S. (2006, April). Reengineering Process and Methods: A Study. Proceedings of Conference on Innovative Application of IT and Management for Economic Growth, Jalandhar, India, 392-404.
[16]. Singh, H., Kalia, A., Sood, S., Kaur, P., & Kaur, K., (2008). A Metric Framework for Determination of Requirement for Reengineering. The ICFAI Journal of System Management, 6(2), 37-43.
[17]. Singh, H., Sood, S., & Kalia, A. (2007). Use of Metrics in Reengineering Process. Ultra Scientist of Physical Sciences (International Journal of Physical Sciences), 19(1), 57-64.
[18]. Singh, H., Sood, S., Kaur, R., & Ratti, N. (2007). Metric Framework for Reengineering Process. Punjab University Research Journal [Science], 57, 251-255.
[19]. Tucker, D. C., & Simmonds, D. M. (2010, April 12-14). A Case Study in Software Reengineering. Proceeding of Seventh International Conference on Information Technology, Las Vegas, Nevada, USA, 1107-1112.
[20]. Woods, S., Carriere, S.J., & Kazman, R. (1999, August 30-September 3). A Semantic Foundation for Architectural Reengineering and Interchange. th Proceedings of 15 IEEE International Conference on Software Maintenance, Oxford, England, 391-398.
If you have access to this article please login to view the article or kindly login to purchase the article

Purchase Instant Access

Single Article

North Americas,UK,
Middle East,Europe
India Rest of world
USD EUR INR USD-ROW
Pdf 35 35 200 20
Online 35 35 200 15
Pdf & Online 35 35 400 25

Options for accessing this content:
  • If you would like institutional access to this content, please recommend the title to your librarian.
    Library Recommendation Form
  • If you already have i-manager's user account: Login above and proceed to purchase the article.
  • New Users: Please register, then proceed to purchase the article.