Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3....

52

Transcript of Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3....

Page 1: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 2: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Contents:-

1. IntroductionAbstract

2. System Analysisa. Existing Systemb. proposed System

3. System Requirement Specification Documenta. Modules Descriptionb. Software Requirementsc. Hardware Requirements

4. System Designa. UML

Page 3: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

5. Technology Description

6. Testing & Debugging Techniques

7. Output Screens

8. Future Enhancements

9. Conclusion

10. Bibliography  

Page 4: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

ABSTRACT:-The adoption of Electronic Banking by

commercial enterprise has been in existence since the mid 90s, much greater in number due to lower operating costs associated with it. Electronic banking has been in the form of automatic teller machines and telephone transactions. More recently, it has been transformed by the Internet, a new delivery channel for banking services that benefits both customers and banks. Access is fast, convenient, and available around the clock.

Furthermore, customer’s application for electronic banking facilities is expanding as the cost savings on transactions over the internet are significant. The chances and threats that the internet symbolizes is no longer news to the present day banking sector. No traditional bank would dare face investment analysts without an Internet strategy. Moreover, business success is not guaranteed by a detailed and thoughtful approach to the internet.

Page 5: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

The main intention behind the commencement of electronic banking services is to provide the customers with an alternative that is more responsive and with less expensive options. With options just a click away, customers have more control than ever. Their expectations are usability and real-time answers. They also want personal attention and highly customized products and services. This research intends to see how electronic banking has improved the efficiency and effectiveness in the bank, take a look at the security measures on ground and also prefer a solution that can eradicate fraud in electronic banking.

Page 6: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Objectives:• The Main Objective of Electronic Banking by commercial enterprise has been in existence since the mid 90s, much greater in number due to lower operating costs associated with it.

• Electronic banking has been in the form of automatic teller machines and telephone transactions.

• More recently, it has been transformed by the Internet, a new delivery channel for banking services that benefits both customers and banks

Page 7: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

System Analysis

a. Existing Systemb. proposed System

Page 8: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Existing System:

•Existing system does not provide the online transaction facility.

• This system does not give the updated account information to the customer.

•The system is not providing transaction between the Account to Account.

•The system is not providing secured login and authentication features.

•The existing system not providing the unlimited periodic statement facility.

Page 9: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Proposed System:

The development of this new system contains the following activities,

•Customer must have a valid User Id, password and Account Number to login to the system

•The system provides the all bank operations like deposit, withdraw, and funds transfer between the two accounts.

•The system providing the fully secured login features.

•Proposed system providing the statement facilities unlimited, that means the system can generate the any any number of months statements. By giving the from date and to date.

Page 10: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Number of Modules:

The system after careful analysis has been identified to be presented with the following modules:

The Modules involved are

1.Administrator

2.Customers

3.Transaction

4.Security and authentication

5.Reports

Page 11: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Modules Description:

1.Administrator Module:

Administrator can access all accounts information and provides some username and password for the customer. Accept the Cheque book requests and other queries, View all the bank Transactions. The administrator can also lock the user accounts and he can open the locks.

2.Customer Module:Can make a funds transfer to another account in

the same bank. And the customer can also access their accounts operations like deposit, withdraw and money transfer . Customer can send the cheque book request to the admin, and also they can send other queries.

Page 12: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

3.Transaction Module:

This module contains the total information of the transactions like the details of the transaction, description, transaction amount, date of transaction, etc..

4.Security and authentication Module:

The user details should be verified against the details in the user tables and if it is valid user, they should be entered into the system. Once entered, based on the user type access to the different modules to be enabled / disabled

Page 13: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

5.Reports Module:

In this Module the Customer and Administrator can generate the different types of Reports and statement according to their access.

Page 14: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Software Requirements:Operating System :Windows

XP/2003 or Linux

User Interface :HTML, CSS

Client-side Scripting :JavaScript

Programming Language :Java

Web Applications :JDBC, Servlets, JSP

IDE/Workbench :MyEclipse6.0

Database :Oracle10g

Server Deployment :Tomcat 5.x

Page 15: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Hardware Requirements:Processor :Pentium IV

Hard Disk :40GB

RAM :1GB or more

Page 16: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

UML DIAGRAMS

Page 17: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Class Diagram

Page 18: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Class collabration daigramsClass collabration daigrams

Page 19: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 20: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Use Case DiagramsUse Case Diagrams

Page 21: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Use-case Diagram :-

System Diagram 

Page 22: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Customer Diagram:-

Page 23: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Administrator Diagram:-

Page 24: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Squence DiagramSquence Diagram

Page 25: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

User Level Squence diagram

Customer:-

Page 26: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Administrator:

Page 27: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Operational Level Operational Level Sequence Sequence andand Collaboration Diagrams Collaboration Diagrams

Page 28: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Login Squence Diagram

Page 29: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Login Collabration Diagram

Page 30: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Deposit Squence Diagram

Page 31: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Deposit Sequence Diagram

Page 32: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Withdrawal Squence Diagram

Page 33: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Withdrawal Collabration Diagram

Page 34: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Activity DiagramsActivity Diagrams

Page 35: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Administrator Activity Diagram

Page 36: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Customer Activity Diagram

Page 37: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Withdraw Actvity Diagram

Page 38: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Deposit Activity Diagram

Page 39: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

TestingTesting

Page 40: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Software Testing is the process used to help identify the correctness, completeness, security, and quality of developed computer software.

Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate.

One definition of testing is "the process of questioning a product in order to evaluate it", where the "questions" are operations the tester attempts to execute with the product, and the product answers with its behavior in reaction to the probing of the tester[citation needed].

Page 41: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

Testing Methodologies: Black box Testing:

Black Box Testing is the testing process in which tester can perform testing on an application without having any internal structural knowledge of application.

Usually Test Engineers are involved in the black box testing.

White box Testing: White Box Testing is the testing process in

which tester can perform testing on an application with having internal structural knowledge.Usually The Developers are involved in white box testing. Gray Box Testing:

Gray Box Testing is the process in which the combination of black box and white box tonics’ are used.        

Page 42: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

OUTPUT SCREENSOUTPUT SCREENS

Page 43: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 44: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 45: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 46: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 47: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.
Page 48: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

CONCLUSIONCONCLUSION

Page 49: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

WORK DONE: 

The “e-Banking” was successfully designed and is tested for accuracy and quality.During this project we have accomplished all the objectives and this project meets the needs of the organization. The developed will be used in searching, retrieving and generating information for the concerned requests.

GOALSReduced entry workEasy retrieval of information Reduced errors due to human interventionUser friendly screens to enter the dataPortable and flexible for further enhancement Web enabled.Fast finding of information requested

       

Page 50: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

BIBILIOGRAPHYBIBILIOGRAPHY

Page 51: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.

(1) Java Complete Reference by Herbert Shield

(2) Database Programming with JDBC and Java by George Reese

(3) Java and XML By Brett McLaughlin

(4) Wikipedia, URL: http://www.wikipedia.org.

(5) Answers.com, Online Dictionary, Encyclopedia and much more, URL: http://www.answers.com

(6) Google, URL: http://www.google.co.in

(7)Project Management URL: http://www.startwright.com/project.htm 

Page 52: Contents :- 1. Introduction Abstract 2. System Analysis a. Existing System b. proposed System 3. System Requirement Specification Document a. Modules.