Advertisement

Re-engineering a Credit Card Authorization System for Maintainability and Reusability of Components – A Case Study

  • Kyo Chul Kang
  • Jae Joon Lee
  • Byungkil Kim
  • Moonzoo Kim
  • Chang-woo Seo
  • Seung-lyeol Yu
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4039)

Abstract

A credit card authorization system (CAS) is a large information system performing diverse activities such as purchase authentication, balance transfer, cash advances, etc. One characteristic of CAS is its frequent update to satisfy the needs of customers and newly enforced governmental laws. Thus, CAS should be designed to minimize the effects of updates, for which high reusability of the CAS components is desired. In this paper, we present our experience of re-engineering CAS based on a feature model for improved reusability of components, which alleviates the difficulty of system maintenance. The result of this project has been successfully transferred to the company.

Keywords

Business Process Feature Model Transaction Information Business Component Revision History 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Bergey, J., O’Brien, L., Smith, D.: Option Analysis for Re-engineering (OAR): A Method for Mining Legacy Assets (CMU/SEI-2001-TN-013). Software Engineering Institute, Carnegie Mellon University, Pittsburgh (2001)Google Scholar
  2. 2.
    Kim, M., Lee, J., Kang, K.C., Hong, Y., Bang, S.: Re-engineering Software Architecture of Home Service Robots: A Case Study. In: International Conference on Software Engineering, Missouri, USA, pp. 505–513 (2005)Google Scholar
  3. 3.
    Kang, K.C., Kim, M., Lee, J., Kim, B.: Feature-oriented Re-engineering of Legacy Systems into Product Line Assets. In: The 9th International Software Product Line Conference, Rennes, France, pp. 45–56 (2005)Google Scholar
  4. 4.
    Ghezzi, C., Jazayeri, M., Mandrioli, D.: Fundamentals of Software Engineering, 2nd edn. Prentice-Hall, Englewood Cliffs (2004)Google Scholar
  5. 5.
    Magdalena, B., Ettore, M., Michel, D., Bruno, L., Kostas, K.: Measuring Clone Based Reengineering Opportunities. In: Sixth International Software Metrics Symposium (METRICS 1999), p. 292 (1999)Google Scholar
  6. 6.
    Baburin, D.E., et al.: Visualization Facilities in Program Re-engineering. Programming and Computer Software 27(2), 69–77 (2001)zbMATHCrossRefGoogle Scholar
  7. 7.
    Snelting, G., Tip, F.: Re-engineering Class Hierarchies Using Concept Analysis. In: Proc. Foundations of Software Eng., pp. 99–110 (1998)Google Scholar
  8. 8.
    Holinsworth, D.: The Workflow Reference Model, Workflow Management Coalition, TC00-1003 (1995)Google Scholar
  9. 9.
    Russell, N., van der Aalst, W.M.P., ter Hofstede, A.H.M., Edmon, D.: Workflow Resource Patterns: Identification, Representation and Tool Support. In: Pastor, Ó., Falcão e Cunha, J. (eds.) CAiSE 2005. LNCS, vol. 3520. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  10. 10.
    Baster, G., Konana, P., Scott, J.E.: Business Components: A Case Study of Bankers Trust Australia Limited. Communication of the ACM 44(5) (2001)Google Scholar
  11. 11.
    Neill, C.J., Gill, B.: Refactoring Reusable Business Components. IEEE Computer Society, Los Alamitos, 1520-9202/03 (2003)Google Scholar
  12. 12.
    LG Card Co. Ltd homepage, http://www.lgcard.com
  13. 13.
    D’sousz, D., Willi, A.: Object, Components, and Frameworks with UML: The Catalysis Approach. Addison-Wesley, Reading (1998)Google Scholar
  14. 14.
    Kang, K.C.: Issues in Component-Based Software Engineering. In: Proceeding of the 21st International Conference Software Engineering (1999)Google Scholar
  15. 15.
    Boertien, N., Steen, M., Jonkers, H.: Evaluation of Component-Based Development Methods. In: International Workshop on Evaluation of Modeling Methods in Systems Analysis and Design (2001)Google Scholar
  16. 16.
    Bohner, S.A.: Extending Software Change Effect Analysis into COTS Components. In: Proceedings of the 27th Annual NASA Goddard/IEEE Software Engineering Workshop (2003)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Kyo Chul Kang
    • 1
  • Jae Joon Lee
    • 1
  • Byungkil Kim
    • 1
  • Moonzoo Kim
    • 1
  • Chang-woo Seo
    • 2
  • Seung-lyeol Yu
    • 2
  1. 1.Software Engineering Lab. Computer Science and Engineering Dept.Pohang University of Science and TechnologyPohangSouth Korea
  2. 2.System Development Team and Quality Management Team, LG-Card Co.SeoulSouth Korea

Personalised recommendations