Visitor Pattern: Implementation of Enquiry Pattern for Internet Banking

Visitor Pattern: Implementation of Enquiry Pattern for Internet Banking

J. Prabavadhi A.Meiappane Dr. V. Prasanna Venkatesan

PG Student, Department of CSE, Sri Manakula Vinayagar Engineering College, Puducherry

Research Scholar, , Pondicherry University, Puducherry

Associate Professor, Pondicherry University, Puducherry

auromei@yahoo.com prasanna_v@yahoo.com

Abstract

This paper brings out the design patterns according to the various services involved in internet banking. The Patt ern oriented Software Architecture uses the pattern which eliminates the difficulty of reusability in a particular context. The patterns are to be designed using BPM (Business Process Model) for effective cross cutting on process level. For implementing the above said BPM, the Internet banking has been taken to implement the pattern into it. The Analysis and identification of various processes in Internet Banking have been done, to identify the effective cross cutting features. With this process the pattern has been designed, as a reusability component to be used by the Software Architect. The pattern help us to resolve recurring problems constructively and based on proven solutions and also support us in understanding the architecture of a given software system. Once the model is finalized by analyzing we found enquiry pattern as the visitor pattern and implement the pattern.

Keywords: Pattern, Pattern Oriented Software Architecture,

Business Process Modeling.

1. Introduction

   In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed direct ly into code. It is a description or template for how to solve a problem that can be used in many diffe rent situations and it is also called as a blue-print of how to solve a proble m. It is used to

   determine imple mentation faster and ma ke code more readable to other programme rs the design pattern is divided into three types: creational, structural, and behavioral. Creational patterns create objects for you rather than having you instantiate objects directly. This gives your program more fle xibility in decid ing which objects need to be created for a given case. Structural patterns help you compose groups of objects into larger structures, such as comple x user interfaces or accounting data. Behavioral patterns help you define the communication between objects in your system and how the flow is controlled in a comple x progra m [14].

   Figure 1.Structure of Visitor Pattern

   The Visitor pattern has been concentrated here which is a behavioral pattern. The visitor design pattern is a way of separating an algorithm fro m an object structure on which it operates. A practical result of this separation is the ability to add new

   operations to existing object structures without modifying those structures.

   1. Software Architecture

      Soft ware arch itecture is the fundamental organization of a system, embodied in its components, their re lationships to each other and to the environment, and the principles guiding its design and evolution.

   2. Patterns

      A particula r recurring design problem that arises in specific design contexts, and presents a well- proven generic scheme for its solution. The solution scheme is specified by describing its constituent components, their responsibilities and relationships, and the ways in which they collaborate. Each pattern is a three-part rule, which e xpresses a relation between a certain context, a proble m and a solution. Patterns can be applied to many diffe rent areas of human endeavor, including software development [14].

   3. Architectural patte rn

      It is Standard design and it Exp ress a fundamental structural organization for software system and provide set of predefined sub system and inc ludes rules and guidelines for organizing the relationships between them.

   4. Usage of patte rns

      Co mprehend existing systems; customize systems to fit user needs; and construct new systems.

      Identify and specify higher level abstractions Re inforce an arch itectural vie w of the system Exp lic itly address non-functional properties

      High availability and minimizat ion of business risk They help in the construction of comple x and heterogeneous software architectures

      They help to manage co mple xity

2. Patte rn Mining

   Pattern min ing is same as the data mining. Min ing the pattern in internet banking by using the BPM (See Figure 2). It is used to representing process involved in internet banking and is used to analyze the process then apply the crosscutting concerns approach in this model. The c rosscutting concerns are the Aspect of

   program which affects the other concern. These concerns often cannot be cleanly decomposed from the rest of the system in both design and imple mentation and can the result in either scattering, tangling. The crosscutting concern is used to improve the modularity of the system.

   In internet bank has lots of services and we analysis this services and find the crosscutting in the process level. The services are the account, Third party transfer, bill payment, credit card, debit card, Mutual fund.

   Use of the crosscutting concern we found the enquiry pattern. The different types of enquiry available in the internet banking, we analysis the services and find the crosscutting in enquiry .The diffe rent types of enquiry are v iew account statement, balance, mini statement and in credit card it have the same view options are the statement, balance, mini statement. We put these services under the enquiry pattern and this pattern is like the visitor design pattern. The pattern is used to increase the reusability and reduce the number of code and easily add new services to the internet bank with the small modification.

3. Patte rn construction

   A pattern for software architecture describes a particular recurring design problem that arises in specific design contexts and presents a well-proven generic scheme fo r its solution. The solution scheme is specified by describing its constituent components, their responsibilities and relationships, and the ways in wh ich they collaborate."

   Each pattern is a three-part rule, wh ich e xpresses a relation between a certain conte xt, a certain system of forces which occurs repeatedly in that context, and a certain software configuration which allo ws these forces to resolve themselves. Context section describes the situation in which the design problem arises. Proble m section describes the problem that arises repeatedly in the context. And finally, solution section describes a proven solution to the problem. Mining the enquiry pattern for internet banking. This pattern is like the visitor pattern. The pattern is constructed by using the elements are Name , Intent, Proble m, and Solution (see Figure 3).

   1. Implementation of Enquiry Patte rn

      Intent: Th is pattern is used to view different account type by different services through online by separating the account type from the services.

      Proble m: how can easily add new services to the account type without modify the e xisting code.

      Solution: The Enquiry is the type of the visitor pattern. Two interfaces involved: Account and Services. The Account system is completely independent.How to get service tries to add new operation to Account system. It is done by adding another interface Services and parameter zing Account interace in the abstract method visit (composite pattern). The "how to get" classes imple ment services interface and make a connection with Account system.

      In this imp le mentation two interfaces are used one is the account type (visitor) and services (element). The concrete visitors are the account enquiry, credit card enquiry. Concrete ele ments are the statement visitor, balance visitor, mini statement visitor. The imple mentation mentioned below for the enquiry visitor pattern.

4. Conclusions

   The visitor pattern for internet banking has been presented over here. These patterns focus mainly on ways to solve usual problem. They provide hints to the Web application designer in order to make these applications more usable and effective both fro m the point of customers and designer of web application. These patterns help to improve the design and reusability. Further the research is preceded on mining some more patterns for internet banking which will be a reusable component for internet banking at a particula r conte xt.

5. References

1. Gustavo Rossi, Fernando Lyardet, Daniel Schwabe Patterns for E-commerce applications, EuroPlop 2001.

2. M arc Eaddy, Alfred Aho, Identifying, Assigning, and Quantifying Crosscutting Concerns ICSE Workshops ACoM '2007.

3. Yue-Shi Lee, Show-Jane Yen, Chia-1llji Wang, M ining browsing and purchasing behaviors of web users, Proceedings of the Ninth International Conference on M achine Learning and Cybernetics, Qingdao, 11-14 July 2010.

4. Eduardo B. Fernandez, Yi Liu, and RouYi Pan,

   Patterns for Internet shops, PLoP 2001 Conference.

5. Hassania OUCHETTO, Ounsa ROUDIES, M ounia FREDJ, Towards process patterns for a component retrieval system integrating the user profile, 978-1-4244- 3806-8/09/$25.00 © 2009 IEEE.

6. Jianguang Sun, Yan Chen, Building a Common Enterprise Technical Architecture for an Universal Bank, 978-1-4244-5326-9/10/$26.00 ©2010 IEEE.

7. Juan Danculovic *, Gustavo Rossi *, Daniel Schwabe

   **, Leonardo M iaton *, Patterns for Personalized WebApplications, EuroPLoPUVK – Universitaetsverlag Konstanz (2001), p. 423-436.

8. A.M eiappane, K.Gideon and Dr.V.Prasanna

   Venkatesan, Adaptive framework of the internet banking services based on customer classification , International Conference on Advances in Engg and Tech, (ICAET – 2011).

9. Jayadev Gyani, P.R.K. M urthi, A Pattern Language for

   Online Share Trading EuroPlop 2005.

10. Klaas van den Berg1 and José M aría Conejero2,1Trese Group, University

    ofTwente,k.g.vandenberg@ewi.utwente.nl,2 Quercus Software Engineering Group, University of Extremadura chemacm@unex.es, A Conceptual Formalization of Crosscutting in AOSD 2005.

11. Changsu Kim a,1, Wang Tao a,2, Namchul Shin b,*, Ki-Soo Kim a,2, An empirical study of customers perceptions of security and trust in e-payment systems, Electronic Commerce Research and Applications 9 (2010) 8495.

12. Catherine S. Weir a,*, Gary Douglas a, Tim Richardson b, M ervyn Jack a, User preferences for authentication methods in e Banking and the effects of experience, Interacting with Computers 22 (2010) 153 164.

13. Xiaohong Yuan1 and Eduardo B. Fernandez2, Patterns for Business-To-Consumer Ecommerce

    Applications, International Journal of Software Engineering & Applications (IJSEA), Vol.2, No.3, July 2011.

14. Erich Gamma, Richard Helm, Ralph Johnson, and

John Vlissides Design Pattern-Element of reusable Object Oriented Software, Addison-Wesley Professional, 1994.

Figure 2. Business Process Model for Int ernet Banking

Figure 3. Visitor Pattern for Enquiry

6

Figure 4. Enquiry

Figure 5. Balanc e Enquiry

7

Figure 6. View Balance Detail

8