loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Modularization of a Large-Scale Business Application: A Case Study
March/April 2009 (vol. 26 no. 2)
pp. 28-35
ASCII Text
x 
 
Santonu Sarkar, Shubha Ramachandran, G. Sathish Kumar, Madhu K. Iyengar, K. Rangarajan, Saravanan Sivagnanam, "Modularization of a Large-Scale Business Application: A Case Study," IEEE Software, vol. 26, no. 2, pp. 28-35, March/April, 2009.
 
 
BibTex
x
 
@article{ 10.1109/MS.2009.42,
author = {Santonu Sarkar and Shubha Ramachandran and G. Sathish Kumar and Madhu K. Iyengar and K. Rangarajan and Saravanan Sivagnanam},
title = {Modularization of a Large-Scale Business Application: A Case Study},
journal ={IEEE Software},
volume = {26},
number = {2},
issn = {0740-7459},
year = {2009},
pages = {28-35},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.42},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Modularization of a Large-Scale Business Application: A Case Study
IS - 2
SN - 0740-7459
SP28
EP35
EPD - 28-35
A1 - Santonu Sarkar,
A1 - Shubha Ramachandran,
A1 - G. Sathish Kumar,
A1 - Madhu K. Iyengar,
A1 - K. Rangarajan,
A1 - Saravanan Sivagnanam,
PY - 2009
KW - modularization
KW - interfaces
KW - maintenance
KW - coupling
KW - metrics
KW - measurements
VL - 26
JA - IEEE Software
ER -
 
Santonu Sarkar, Accenture Technology Labs, India
Shubha Ramachandran, Infosys Technologies, India
G. Sathish Kumar, Infosys Technologies, India
Madhu K. Iyengar, Infosys Technologies, India
K. Rangarajan, Infosys Technologies, India
Saravanan Sivagnanam, Infosys Technologies, India
Large software systems, developed over several years, are the backbone of industries such as banking, retail, transportation, and telecommunications. With multiple bug fixes and feature enhancements, these systems gradually deviate from the intended architecture and deteriorate into unmanageable monoliths. This article presents a case study of a banking application besot with such problems and the modularization approach that the company adopted as a solution. It also highlights benefits unearthed as a result of this reengineering exercise.

1. F.P. Brooks, "No Silver Bullet: Essence and Accidents of Software Engineering," Computer, vol. 20, no. 4, 1987, pp. 10–19.
2. M.M. Lehman and L. Belady, Program Evolution—Processes of Software Change, Academic Press, 1985.
3. D.L. Parnas, "On the Criteria to Be Used in Decomposing Systems into Modules," Comm. ACM, vol. 15, no. 12, 1972, pp. 1053–1058.
4. M. Ramage and K. Bennett, "Maintaining Maintainability," Proc. Int'l Conf. Software Maintenance (ICSM), 1998, pp. 214–223.
5. J. Bisbal et al., "Legacy Information Systems: Issues and Directions," IEEE Software, vol. 16, no. 5, 1999, pp. 103–111.
6. N. Medvidovic and R.N. Taylor, "A Classification and Comparison Framework for Software Architecture Description Languages," IEEE Trans. Software Eng., vol. 26, no. 1, 2000, pp. 70–93.
7. S. Sarkar, G.M. Rama, and A.C. Kak, "API-Based and Information-Theoretic Metrics for Measuring the Quality of Software Modularization," IEEE Trans. Software Eng., vol. 33, no. 1, 2007, pp. 14–32.

Index Terms:
modularization, interfaces, maintenance, coupling, metrics, measurements
Citation:
Santonu Sarkar, Shubha Ramachandran, G. Sathish Kumar, Madhu K. Iyengar, K. Rangarajan, Saravanan Sivagnanam, "Modularization of a Large-Scale Business Application: A Case Study," IEEE Software, vol. 26, no. 2, pp. 28-35, Mar./Apr. 2009, doi:10.1109/MS.2009.42
Usage of this product signifies your acceptance of the Terms of Use.