Online Electronic Payment System Using PREDICT II Protocol Mid Term Project Presentation 6 th September, 2001 By Nishanth Menon 98m11, S 6 MCA
Mar 26, 2015
Online Electronic Payment System Using PREDICT II Protocol
Mid Term Project Presentation6th September, 2001
By
Nishanth Menon98m11, S6 MCA
2
Contents
Problem statement Use case view Database design General package layout Test plan Deployment diagram Implementation so far Development platform
3
Problem Statement
The objective of this project is to create a scalable model of an
online electronic payment system, allowing authorized users to
access and utilize their wealth from anywhere in the Internet using
the PRotocol Enhancement of DIgital Cash Transaction- II protocol.
4
Problem Statement .Contd..
Inputs.• User Information – name, Pass Phrase
etc.
• Amount of Cash to be transacted.
• The IP of the Zone Server.
• The IP and optionally the port of the Server socket of the remote client software.
• The Key Generation information (including no: bits RSA Key, Hashing algorithm for the password storage and other configuration information).
Outputs.
• Transaction Result–Whether
completed or aborted etc.
• Passbook format Transaction
information.
• Complete transaction
information.
• Personal information of
authorized client.
5
Entire System Use Case Diagram
BankCorporation Merchant Citizen
Delete AccountCreate Account
PassBook RequestRequest Transaction
History
Change Personal Information
Send Cash token
Recieve cash token
Decide on the Amount of cash to send
Client
Freeze Account
Collect Transaction Information
Imposition of Regulations
Government
6
Client Use Case Diagram
Select Operation Mode
Identify Zone Server
Authentication
Initiate Transaction
Local ClientZone Server
Remote Client
Handle Cash token Transfer
7
Zone Server Use Case Diagram
Zone Server Information Provider
Authenticator
Handle Conversion Request
Conversion Table Updater
Page Request HandlerKuchelanMaster Server
Handle Cash Token Transaction
8
Master Server Use Case
Conversion Table Provider
Master Server Zone Reliablity Maintainer
Identifier Storage Manager
Remote Master Server Identifier Validation
Kuberan
Remote Master Server
Identifier Validator
9
Database Design
IdentifierInformation- Brahma DB
Password – Kuberan DB
PersonalInformation- Kuberan DB
TransactionInformation –Kuberan DB
10
General Package Layout
DataBase
utils
crypto(from utils)
misc(from utils)
messages
networking
serverStuff(from networking)
clientStuff(from networking)
The Networking Aspects are handled by this package
The Aspects of the Database Connection, query etc.. are handled
Miscellaneous functions needed by all the packages are held in this package
Messages as required by the PREDICT II are defined in this package.
11
Test Plan
Main operation (function) in every class - allows for separate testing of each class. Functional tests –shows I/P and O/P of
each method for given set of values. Stress tests & boundary tests. Integration tests.
12
<<Internet>>
Remote Client 1
<<Kuchel Software>>
Zone Server 1
<<Kuberan Software>>
<<Internet>>
Master Server 1
<<Brahma Software>>
Master Server 2
<<Brahma Software>>
Zone Server 2
<<Kuberan Software>>
Zone Server n
<<Kuberan Software>>
<<High Security Private Network>>
<<High Security Private Network>>
<<High Security Private Network>> <<High Security Private Network>>
Remote Client 2
<<Kuchel Software>>
Remote Client m
<<Kuchel Software>>
<<Internet>>
Deployment Diagram
13
Implementation So Far
Prototypes for the networking and database package have been tested.
Encryption package (crypto) is fully implemented and tested.
HTTPS server setup complete.
14
Development Platforms
Operating System – RH Linux 7.1 and Windows 2000 (JDK1.3 support)
Language – JDK1.3.1, Perl (Server Side CGI)
Database – Oracle 8i
Getting All the Keys
Hash_File_And_IP
IP : StringFileName : String
toString()
(from misc)
Hash_Name_IP_And_Key
IP : StringName : StringKey : CipherKey
toString()
(from misc)
hashencrypt
decrypt
GetMyKey
GetMyKey()
GetAllKeys
GetAllKeys()
1
1
1
1
StringFileRead
(from misc)
KeyinTheFile
MyName : StringPublicKey : KeyMyIP : String
ReadFileAndGetKey
0..*
1
11 11
PRotocol Enhancement for
DIgital Cash Transaction-
II
Zone 1SERVER
MASTERSERVER
Zone 2SERVER
ReceiverSender
1Cash
Transmit6
Deposit Confirm 2
Cash Forward
3Cash
Deposit
4Deposit
Acknowledge
5 Deposit
Acknowledge Forward
10Confirm Acknowledge
OrReject Confirm9
Confirm Request
7Reject / Status Check
11Transact Complete
11Transact Complete
8Status
Confirm
‘Kuberan’ handle Cash token
Handle Transaction Abort
<<include>>
Delete Identifier
Validate Cash Token Receive Validation Result
Store Information to Database
<<include>>
Master Server
<<communicate>>
<<communicate>><<communicate>>
Handle Cash token Deposit
<<include>><<include>>
Cash Token generate
Confirm Identifier
<<communicate>>
Get Result
<<communicate>>
Handle Cash token Withdrawal<<include>>
<<include>>
<<include>>
Handle Cash Token Transaction
<<include>>
<<extend>>
<<communicate>>
<<extend>>
Send Cash Token Generation Result
<<include>>
Send Acknowledgement
<<include>>
Handle Acknowledgement
<<include>>
Kuchelan
<<communicate>>
<<communicate>>
<<communicate>>
<<communicate>>