SOFTWARE MODELING

FIANL ATM BANKING SYTEM REPORT

UNIVERSITY OF PAPALESTINECOLLEGE OF APPLIED ENGINEERING & URBAN SOFTWARE ENGINEERING DEPARTMENT

PREPARED BY:MOHAMMED MAJED ERHEEM 120090013MOHAMMED MAMDOUH AL-AZAIZA 120070309NAEL M.WAEL SKAIK 120070275

SUPERVISED BY:

ENG. MOHAMMED TIMRAZ

Introduction

In the age of cybercrimes and the introduction of online services, financial institutions are facing different kinds of risks that are specific to conducting business that requires communication over the internet. It is imperative that these institutions implement strong security approaches that can adequately address, monitor, manage, and control risks and security threats, at the same time in the increasingly federated, network-based it environment, networks often include different operating systems, a variety of web-based and client/server applications, all accessed by internal and external users, the complexity of such heterogeneous networks makes it impossible to effectively secure the entire networking environment with a single component; instead a total security solution has to be implemented in order effectively eliminate risks without leaving any holes in the security shield that could be exploited.

Banking system case study is a client /server case study. This is a popular example. A bank has several automated teller machines (atms), which are geographically distributed and connected via a wide area network to a central server. Each atm machine has a card reader, a cash dispenser, a keyboard/display, and a receipt printer by using the atm machine, a customer can withdraw cash from either a checking or savings account, query the balance of an account, or transfer funds from one account to another. A transaction is initiated when a costumer inserts an atm car into the dark number, the system validates the atm card to determine that the expiration date has not passed, that the user entered pin (personal identification number) matches the pin maintained by the system, and that the card is not lost or stolen. The customer if the third attempt fails. Cards that have been reported lost or stolen are also confiscated.

If the pin is validated satisfactorily, the customer is prompted for a withdrawal, query, or transfer transaction. Before a withdrawal transaction can be approved, the system determines that sufficient funds exist in the requested account, that the maximum daily limit will not be exceeded, and that there are sufficient funds at the local cash dispenser. If the transaction is approved, the requested amount of cash is dispensed, a receipt is printed containing information about the transaction, and the card is rejected. Before a transfer action can be approved, the system determines that the customer has at least two accounts and that there are sufficient funds in the account to be debited. For approved query and transfer requests, a receipt is printed and the card ejected. A customer may cancel a transaction at any time; the transaction is terminated and the card is ejected. Customer records, account records and is not part of this problem.

An atm operator may start up and close down the atm to replenish the atm cash dispenser and for routine maintenance. It is assumed that functionality to open and close accounts and to create, update, and delete customer and debit card records is provided by existing system and is not part of this problem.

1 | P A G E

Problem Abstraction

BY USING THE ATM MACHINE, A CUSTOMER CAN: 1. WITHDRAW CASH 2. QUERY THE BALANCE OF AN ACCOUNT3. TRANSFER FUNDS FROM ONE ACCOUNT TO ANOTHER.

A CARD INCLUDES INFORMATION SUCH AS:1. CARD NUMBER.2. EXPIRED DATE.3. START DATE.

2 | P A G E

Several Automated Teller Machines (Atms) Connected Via A Wan To A Central Server.

Each ATM machine has a card reader, a cash dispenser, a keyboard/display, And a receipt

printer

3 | P A G E

Use Case Diagram

4 | P A G E

5 | P A G E

Use Case Description

6 | P A G E

Activity Diagram

7 | P A G E

8 | P A G E

9 | P A G E

Class Diagram

10 | P A G E

11 | P A G E

Sequence Diagram

12 | P A G E

13 | P A G E

14 | P A G E

State Machine Diagram

15 | P A G E

16 | P A G E

Task diagram

17 | P A G E

18 | P A G E

19 | P A G E

20 | P A G E