Object Oriented UML Modeling for ATM Systems Rajni Pamnani, Pramila Chawan, Satish Salunkhe Department of computer technology, VJTI University, Mumbai Abstract The Object-Oriented Modeling assists the programmer to address the complexity of a problem domain by considering the problem not as a set of functions that can be performed but primarily as a set of related, interacting Objects. This article is based on the approach of Object Oriented modeling through Unified Modeling Language (UML) for an ATM system in Banking sector. The main aim of this article is to provide a flexible and faithful environment for a customer, who wants to do online banking transactions. After successful authentication, the customer can withdraw the desire amount (within the prescribed limit) from the ATM machine or can transfer amount to other account. User can also change the pin code. The ATM has solved many problems and now customer can have money transaction 24/7. In this article UML Class, Interaction diagram, Activity diagram & Use Case diagram are also designed for the ATM System. Key Words: UML dynamic modeling, UML static modeling, Use case modelling 1. Introduction The Unified Modeling Language (UML) is a very dominant modeling graphical language for specifying, constructing and documenting the artifacts of software system. UML is simply another graphical representation of a common semantic model. UML provides a comprehensive notation for the full lifecycle of object- oriented development UML is a collection of best engineering practices that have successful in the modeling for a design of a huge and complex systems. Modeling is very important for readability and reuse of the systems. UML offers a set of notations and rules for using the same. The main task of the UML is to create a simple, well documented and easy to understand software model for the people. The UML modeling consists of nine diagrams to model a software system & these diagrams are Use case Diagram, Class Diagram, Object Diagram, State Diagram, Activity Diagram, Sequence Diagram, Collaboration Diagram, Component Diagram & Deployment diagram. Nowadays knowledge based system is most popular and needed in every sector like medical sector, banking sector, engineering sector and traveling sector etc. In the Banking sector, knowledge means simply having the knowledge from expert. Knowledge modeling is the major activity used to understand the problem and sending the solution rapidly. 2. Features of ATM Systems The ATM will service one customer at a time. A customer will be required to insert an ATM card and enter a personal identification number (PIN) - both of which will be sent to the bank for validation as part of each transaction. The customer will then be able to perform one or more transactions. The card will be retained in the machine until the customer indicates that he/she desires no further transactions, at which point it will be returned - except as noted below. The ATM must be able to provide the following services to the customer: 1. A customer must be able to make a cash withdrawal from any suitable account linked to the card, in multiples of Rupees 100. Approval must be obtained from the bank before cash is dispensed. 2. A customer must be able to make a deposit to any account linked to the card, consisting of cash and/or checks in an envelope. The customer will enter the amount of the deposit into the ATM, subject to manual verification when the envelope is removed from the machine by an operator. Approval must be obtained from the bank before physically accepting the envelope. 3. A customer must be able to make a transfer of money between any two accounts linked to the card. 4. A customer must be able to make a balance inquiry of any account linked to the card. 3. Object-Oriented Analysis Object-oriented analysis looks at the problem domain, with the aim of producing a conceptual model of the information that exists in the area being analyzed. Analysis models do not consider any implementation constraints or how the system is to be built. The identified objects reflect entities and operations that are associated with the problem to be solved. 3.1.UML static modeling for ATM systems This part describes the way that system should look. It analyses the structure and substructure of the modeled system based on objects, attributes, operations and relationships. 3.1.1. Use case modeling for ATM systems