Bluetooth Banking

Post on 22-Nov-2014

113 views 1 download

Tags:

Transcript of Bluetooth Banking

BLUETOOTH BANKING

Presented by :Disha Puri

EC-7A0715031033

Submitted to :Mr.Amit GoswamiCET-IILM-AHL

Bluetooth

• It is more of a personal wireless network.• The BT specification has been converted into IEEE standard 802.15.• Current Bluetooth devices offer the modest range of 10 m using the (low) power class2. This is a deliberate action, as Bluetooth is currently primarily a technology for personal area networks (PAN), where device battery power is limited.• Bluetooth Protocol version 1.0 was introduced in the second quarter of 1999, and the 2.0 version will be produced between 2000 and 20001.

Modeling Technique

Software Requirements

Authentication

• Ensures security,thus preventing misuse of the account.• Generated an error message and stores the IMEI number of the device that tries to interface for record and guard against misuse.• Sends the error message to the registered Bluetooth device.

Deposit

• Temporary updation is required to make the process faster in case of crowded server.• Permanent update follows temporary update every time.• Request Number and Expiry date ensures security and expiry date for the request number reduces memory requirements.

Withdrawal• Generates an error message in case amount exceeds the availability.• Temporary updation message is destroyed in the above case without changing the balance, thus saving time.

Balance Enquiry

Screen Shot for Home Screen

Screen Shot For Authentication

Screen Shot for Existing Account

Screen Shot for Withdrawal

Screen Shot for Deposit Screen Shot for

Balance Enquiry

Screen Shot for Server Connection

Screen Shot for Admin Console : • Created for Permanent Update.• Uses the unique request number for permanent opdate.•

Screen Shot for Permanent Update

• This screen follows the admin console to finally validate the banking update.• Request Number can be destroyed after this even if the expiry date has not been reached.

Testing

Unit

White box

Black box

Inheritance

IntegrationTop

Down Approa

chBottom

Up Approa

chUmbrell

a Approa

ch

Validation System

Last stage of testing. System

is tested

as a whole and a fully

computer-

based is

exercised.

Unit Testing : Involves testing individual functions.The purpose of unit testing is to thoroughly exercise individual block of code to ensure high quality in their design and implementation.

White Box Testing : It is also called implementation testing. The tester tests and implements all the boundary, branching conditions and all possible boundary conditions.

Black Box Testing : Also called responsibility based testing. It checks all the classes of functions and finds the missing or incorrect missing functions and all kinds of errors such as intialisation,termination,performance,interface,etc.

Inheritance Testing : Tests the errors that might occur while inheriting behavior from other classes of functions during interconnection.

Integration Testing : Logical extension of unit testing. Checks whether the integration of the individual units to form the next level modules have been done properly and no errors occur. Umbrella Approach does testing along flow paths. Inputs are integrated in bottom up approach and outputs in top down manner.

Validation Testing : Software Requirement validation testing is done here according to the software requirements specified and a list of deficiency is created.

Thank You