 | | | 33 pages | | | 27-04-2010 | | |  |
| | Not evaluated | | |
|
“Online Banking " is a computerized telecommunications application that provides the customers of a financial institution with access to financial transactions in a public space without the need for a human clerk or bank teller. On most modern ATMs, the customer is identified by inserting a plastic ATM card with a magnetic stripe or a plastic smartcard with a chip, that contains a unique card number and some security information, such as an expiration date or CVC (CVV). Security is provided by the customer entering a personal identification number (PIN).
In the existing system the transactions can only be done manually but in the system we have developed all banking transactions will be computerized using our new software "Online Banking".
This project looks at the technical, economic and behavioural feasibility of computerizing certain financial transactions and providing clients with access to them from an ATM.
System analysis is a process of gathering and interpreting facts, diagnosing problems and information in order to recommend improvements to the system. It is a problem solving activity that requires intensive communication between the system users and developers. System analysis or study is an important phase of any system development process. The system is studied in the minutest detail and analyzed. The system analyst plays the role of the interrogator and delves deep into the working of the present system. The system is viewed as a whole and the inputs to the system are identified. The outputs from the organizations are traced to the various processes. System analysis is concerned with becoming aware of the problem, identifying the relevant and decisional variables, analyzing and synthesizing the various factors and determining an optimal or at least a satisfactory solution or program of action.
A detailed study of the process must be made by various techniques like interviews, questionnaires etc. The data collected by these sources must be scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions. This system is called the existing system. Now the existing system is subjected to close study and problem areas are identified. The designer now functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions are given as proposals. Proposals are then weighed with the existing system analytically and the best one is selected. The proposal is presented to the user for an endorsement by the user. The proposal is reviewed on user request and suitable changes are made. This is a loop that ends as soon as the user is satisfied with proposal.
Preliminary study is the process of gathering and interpreting facts, using the information for further studies on the system. Various feasibility studies are carried out. Through these studies a rough figure of the system activities can be obtained, from which the decision about the strategies to be followed for effective system study and analysis can be taken[...]
1. Introduction
1.1 Abstract
1.2 Objectives
1.3 Administrative Module
2. System Study & Analysis
2.1 Existing System
2. 1.1 Problems with the existing system
2.2 Proposed System
2. 2. 1 Advantages of the proposed system
2.3. Feasibility study
2.3.1 Technical feasibility
2.3.2 Economic feasibility
2.3.3 Behavioural feasibility
3.1 System Design Introduction
3.1.1 Logical design
3.1.2 Physical design
3.1.3 Design/specification activities
3.1.4 Module design
3.1.5 Input design
3.1.6 Objectives
3.1.7 Output design
3.2 Database design
3.2.1 Relational database management system (rdbms):
3.2.2 Relations, domains & attributes
3.3 Normalization
3.1 First Normal Form
3.2 Second Normal Form
3.3 Third Normal Form
3.4 Tables structure
3.5 System development
4.1 System Specifications
4.1.1 Hardware requirements
4.1.2 Software requirements
4.2 Software environment
4.2.1 Text Box
4.2.2 Label
4.2.3 Command Button
4.2.4 Picture Box
4.2.5 Image Box
4.2.6 List Box
4.2.7 Combo Box
4.2.8 Check Box
4.2.9 Option Box
4.2.10 Drive List Box
4.2.11 Directory List Box
4.2.12 File List Box
5. System Implementation and Testing
5.1 Coding
5.1.1 Main Form Coding
5.1.2 Change Pin
5.1.3 Transaction
5.1.4 Statements View
5.2 System Implementation and Testing
5.2.1 System testing
5.2.2 Test plan
5.2.3 Unit testing
5.2.4 Integration testing
5.2.5 Validation testing or system testing
5.2.6 Output testing or user acceptance testing
5.3. Training
Appendices
1. Screen Shots
2. Login
3. ATM home
4. Withdrawal
5. Transaction
6. Amount Type
7. Success Transaction
8. Balance
9. Transaction Progress
10. Transaction Report
11. Cash Transfer
Conclusion
Bibliography
