E-banking

  • View
    27

  • Download
    0

Embed Size (px)

Text of E-banking

ABSTRACTE- Banking refers to systems that enable bank customers to access accounts and general information on bank products and services through a personal computer or other intelligent device. Internet banking products and services can include detailed account information for corporate customers as well as account summery and transfer money. Ultimately, the products and services obtained through Internet Banking may mirror products and services offered through other bank delivery channel. The project gives real life understanding of Internet banking and activities performed by various roles in the supply chain. Here, we provide an automation for banking system through Internet. Internet banking system project captures activities performed by different roles in real life banking which provides enhanced techniques for maintaining the required information up-todate, which results in efficiency. The project gives real life understanding of Internet banking and activities performed by various roles in the supply chain. The meaning of Internet markets or online business has been widely used in these days. The success of the business depends on its flexibility, availability and security. Since that the web-based systems should have a special way to design the system and implement it. Nowadays, the Internet Banking System widely used and the banks looking to provide the best quality system with highly available,fast response, secure and safe to use.

PAGE INDEX

Candidate Declaration ..

I

Certificate II Acknowledgement .. III List of Figures . IV List of Tables ... V Table of Content... VI

1. Introduction................................................. 1.1 Problem Description................................................... 1.2 Problem Solution........................................................ 1.3 Need and Scope ....... .......................................... 1.4 Plateform Specification........................................................ 1.4.1 Hardware Specification...................................................... 1.4.1 Software Specification........................................................ 2. Feasibility.............................................................. 3.1 Technical Feasibility................................................................ 3.2 Economical Feasibility............................................................. 3.2 Operational Feasibility.............................................................. 3. Software Engineering Approach.................................................. 3.1 Software Model Used ..................................................... 3.1.1 Description............................................................................

1 2 2 2 2 2 2 7 8 8 8 1 2 2

3.1.2 Reason for Use.................................................................... 3.2 Planning managerial issus....................................................... 3.2.1 Planning scoped Project resources........................................ 3.2.2 Team organization.................................................................. 3.2.3 Project Scheduling.................................................................. 3.2.4 Cost Estimation....................................................................... 3.3 Requirement.................................................................................. 3.3.1 Functional requirement............................................................ 3.3.2 Non-functional requirement..................................................... 4. Designs.................................................................................................................. 4.1 Use Case Diagram................................................................................... 4.2 Data flow diagram................................................................................... 4.3 Data Dictionary........................................................................................ 4.4 E-R Diagram............................................................................................ 4.5 Class Diagram.......................................................................................... 4.6 Sequence diagram.................................................................................... 4.7 Activity Diagram....................................................................................... 5. Implementation Phase....................................................................................... 5.1 Language used & its Characteristics...................................................... 5.2 GUI (Snapshot)........................................................................................

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

6. Testing................................................................................................................. 6.1 Testing Method & Strategies of used..................................................... 6.2 Test Case................................................................................................. 7. Conclusions......................................................................................................... 8. Limitation & Fure Enhancement..................................................................... 9. Bibliographand references................................................................................ 9.1 Reference books..................................................................................... 9.2 Other documentation and resources........................................................

2 2 2 2 2 2 2 2

CHAPTER 1 INTRODUCTION

1.1Problem DescriptionOur main aim to make a accounting and insurance system which handles the record of every customer (i.e. account summary, transaction, insurance etc. ) and function of software is to manage the whole detail (i.e. account summary, transaction, insurance etc. ) of a customer on the internet or local intranet directly submitted to the Admin.

1.2 Problem SolutionThe customer can put there details which will be submitted to the admin officer and can get the required details of the particular customer and other detail by sitting at home so this will help in maintain records and sending information very fast and easy. Hence an overall grade is generated for customer.

1.3 Need and ScopeThis application simply generates the list of the customer according to the account number. Also this application can have some co applications running on the client side that made the final updating to the main website at the server end. This process can be triggered on a particular event defined custom. The future use for this project will put a new thing in the mind for use in a large scale. It can be also in various industries for grading their products. This is a simple application with larger extensible and convenient uses.

1.4

Platform specification1.4.1 Hardware Specification For Client Side Description 1. Processor 2. Hard Disk 3. RAM Minimal 550 MHz 10 GB 256 MB Recommended 2GHz 32-bit processor or higher 40 GB or More 1 GB or more

For Server Side

Description 1. Processor 2. Hard Disk 3. RAM

Minimal 800 MHz 40 GB 512 MB

Recommended 2GHz 32-bit processor or higher 80 GB or More 2 GB or more

1.4.2

Software specificationFor Client Side

Particulars 1. 2.

Description Operating System Browser

Requirements Windows 98 or Above Internet Explorer 7.0 or Above

For Server Side

Particulars 1. 2. 3. 4.

Description Operating System Database Browser Technology

Requirements Windows 98 or Above Microsoft SQL server 2005 Internet Explorer 7.0 or Above ASP. Net 2008

1.5

Importance of project

CHAPTER 2 Feasibility

Feasibility StudyA feasibility study is a study made to decide whether or not the proposed system is worthwhile. The implementation of feasibility study is based on the information assessment (what is required), information collection and report writing. Feasibility study should be done with the help of project managers who is going to handle that particular project, software engineers who are about to develop that system, technical experts and customers who will be using the system. Typically the feasibility study should be completed within two or three weeks.

Types of Feasibility

2.1.

Technical Feasibility Technical feasibility around existing computer system and to what it can support proposed addition. Our project is technically feasible as it is coded in ASP. Net. Database Microsoft SQL Server 2005 which is easy to use and highly secure. All the Codes and Modules can be easily implemented. Database Connectivity is also highly feasible and quickly operable.

2.2.

Economical Feasibility Economic analysis is the most frequently used method for evaluating the effectives of a candidate system. Language used is easily available. More commonly known as cost benefit and savings that are expected for candidate system and then compare them with cost. Browsers come inbuilt with Operating System it adds to feasibility.

2.3.

Operational Feasibility

Operational feasibility is mainly concerned with issues like whether the system will be used if it is developed and implemented. Whether there will be resistance from users that will effect the possible application benefits? The essential questions that help in testing the operational feasibility of a system are following.

Does management support the project? Are the users not happy with current business practices? Will it reduce the time (operation) considerably? If yes, then they will welcome the change and the new system. Have the users been