INDIPROJECTREVIEW

Running head: BANKING SYSTEM

BANKING SYSTEM

Mahamadou Mahi Diallo
University of Maryland Global Campus
ITEC 630: Information Systems Analysis, Modeling and Design
Banking System

Banking System

Phase 1: Requirement Analysis

1. Problem definition

A banking system enables customers to carry out their basic banking transactions by just sitting at their homes or offices through a personal computer. This system is also very useful to the bank and its employees. Most of the banking systems that exist are not able to accommodate many customers at the same time which makes them unstable. In addition, most of the banking systems in existence are not secure especially accessing them through the web. I am proposing a more secure, effective, and efficient system than those in existence (de Vries et al, 2007). Furthermore, the access speed of resources from the system will be much improved.
In addition, the existing systems comprise of the following activities.
· Most of the banking records are kept on paper registers.
· Great amount of manpower is used in manually generation of reports in most of the areas.
· A networking environment exists in the present systems whereby there is automation of regular activities.
· Banking systems in existence mostly allow services to their customers during bank hours only and this is their great limitation.
· Since most of the records are maintained manually, their readability is limited in the existing systems.
· Most of the existing systems are less secure since they mostly use the web and so they vulnerable to social engineering attacks such as phishing.
2. Issues

This project tries to address some issues in the banking sector (De Jonghe, 2010). These issues include the following.
· Outdated experiences on mobile phones and personal computers
· Security breaches
· The increasing competition in the banking sector
· A shift in the culture of people
· Regulatory compliance
· Changes in business models
· Antiquated business systems
· Rising expectations of people.
3. Objectives

Some of the objectives include.
i. To design a secure banking system.
ii. To automate all the activities carried out in the bank premises.
iii. To make sure there is improved performance in the banking processes.
iv. To introduce paperless banking.
v. To ensure that taking customer details, updating, and maintaining of their data is done more effectively and efficiently.
vi. To introduce a more convenient way of banking and checking of details by customers.
vii. To make it easy for the administrators to update, modify and delete customers’ data.
4. Requirements

A bank can have many branches but with this system, customers are able to synchronously have access to their banking details whenever they need it. A transaction is initiated when a customer inputs his/her personal identification number (PIN) into the system then they select the service they need and this is finalized after the system has validated the transaction being made (De Jonghe, 2010).
Customers are prompted for a withdrawal, transfer or query transaction after their PIN has been satisfactorily validated by the system. The system is linked with the server of the bank through communication system. The system server should also maintain customers’ record, debit card records and account records.
Furthermore, the system should give a report of the transaction made after the approval of a transaction and cancel any incomplete transaction. The system should allow customers to check their account balances and be able to transfer their funds too.
The hardware and software requirements for the system are as follows.

Software requirements

Database Server

Microsoft SQL Server 2005 or later

Server

Windows Server 2003 or later

User Interface

Asp.Net with Ajax

Client

Mozilla, Google Chrome or Microsoft Internet Explorer

Operating system

Windows XP or later

Code Behind

C#.Net

Tools

Microsoft Visual Studio .Net 2008 or later

Hardware requirements

Hard Disk

At least 20GB of PC free storage

RAM

512MB

Motherboard

ASRock K7VM3

Cache Memory

256K or more

CD ROM

52X

Processor

Intel Pentium or more

Keyboard

Standard 101/102 key

Mouse

PS/2 compatible

Floppy Disk Drive

1.44MB or more

5. Constraints

Some constraints should be pointed out and clearly explained in order to have a great impact on the overall success of this banking system.
i. Safety and security

The system from this project must be highly secure and safe since the users will directly access their accounts through the internet. Therefore, the system should be able to identify valid customers according to their details of the bank and password. Due to this, it is not easy to protect the system by major disasters by minimizing the unauthorized access to it.
ii. Hardware requirements

Since this system is accessed from the internet, a client server will be the most suitable style for the organization’s system. Personal computers or mobile phones will be required by each user of the system, and they must be connected to the internet.
In summary the following hardware will be required for the users.
· Mobile phones (should be able to access the internet)
· Availability of the internet
· Personal computers

6. Description of the banking system

This banking system is more advanced than the other systems in existence. The system database has been improved to be.
· Highly consistent
· More reliable
· Easily accessible
· Can be easily integrated with other applications and platforms.
· More secure
· More flexible
· Highly efficient on how it utilizes resources.
· Easier to delete any errors from the system by offering appropriate error message.
· User friendly and menu driven.
· Able to validate input data by automatically checking and immediate signaling of errors.
In addition, this system has.
· A better and highly efficient way of retrieving data which is more secure than the existing systems.
· To offer a more improved way of viewing reports as and when needed.
· To have a better way of retrieving information.
· To use less time in generation of reports.
Furthermore, the system has a user-friendly user interface, the database’s data retrieval speed is very high, and I am working to improve its security. I am also working to integrate the system with anti-phishing programs to protect the system against phishing attacks (Hole et al, 2006).
7. Logical model design

i. Data flow diagrams

· Context Diagram

This design demonstrates how the banking system acts as the central point where all the actors such as bank customer, system administrator and the bank itself carry out their daily activities. The bank receives requests from the system, and it responds appropriately during the transaction. The system administrator submits instructions to the system and gets back responses according to their request and bank customer inputs their details and they go ahead with the transactions once allowed by the system.

· Dataflow Diagram

This diagram describes and analyzes data movement throughout the system. It is the central tool and the basis from which other components of the system are created. The transformation of data from input to output, through the processes shown above, represents the physical entities associated with the banking system. The users, that is, customers, bank staff and the administrators interact with the system to carry out their tasks as shown in the diagram.
ii. Inputs and outputs

Input: The system gives its users a friendly interface to enter their details such as names, phone number, username, password and other banking details for example; account number (Dianat et al, 2019). During a transaction, the system displays sections where the user is supposed to input details such as the receiving account number, amount to be transferred, name of the recipient and other details. All the information is under the management of system and in order to have access to it the user has to provide their identity by entering the username and password. Every user has their own access domain beyond which the access is dynamically refrained rather denied.

Output: tables and reports are the major outputs of the system. Tables are provided dynamically to meet the requirements on demand. Reports carry the whole information flowing across the bank.
8. Specific requirements

The way this baking system interacts with the environment determines its functional and non-functional requirements. The functional and non-functional requirements should be defined more clearly and accurately to make the designing of this system more effective (Aladwani, 2001).

Functional requirements

The functions and facilities needed by the computer and services that will be provided by the system include.
· Transfer of account balance
· Updating of the system data
· Online entry of data by the bank staff
· Checking of account balance
· Checking of book allotment
· Opportunity for online shopping

Non-functional requirements

This constitutes of requirements that are not the functionalities of the system, but they are its features. The system should be kept accurate, reliable, secure, and easy to maintain (Aladwani, 2001). The non-functional requirements for this system include.
· Testable
· Hardware limitations: the system should be platform independent, supported on cheap hardware and able to work with low specification hardware.
· Should be maintainable.
· Highly reliable
· Performance constraints: it must be fit in terms of performance.
· Conformance to specific standards

Phase 2: System and Database Design

a. User Interface

The figure below shows the user interface of the banking system.

When users try to access the system, they will an interface similar to this. The physical inputs will be located as shown above and users will be asked for more details as they proceed.
Furthermore, for the output, the system will generate a report of the transaction that has been done by the customer.
b. Data Design

i. Database Design

More information on the relevant data that came into the system are identified. The tables are designed according to their relationship as per the standard database design methods. Data types for each data in the tables is defined. In addition, for optimum database design, to avoid redundancy, boosting security and to have data integrity of the database, the tables were created as normalized and denormalization was applied.

ii. Entity-relationship Diagram

The design above shows an analysis of the relationship between various system components and their attributes. It provides means of communication between the system and the administrators. For instance, the components include debit card, cheque requests, Users, accounts types, branch and others with their attributes below them.

iii. Data file storage and access

Handling of unstructured information by the end-users has a strong effect on the infrastructure of information technology. This data stored is also duplicated to make sure that it is secure. The banking data is hence kept in various forms; tapes, file system and even in the cloud storage or object storage (Dianat et al, 2019).
In addition, backups and data protection measures are implemented for the end-users. Movement of data in the system is also automated. Ensuring that there is secure file sharing within the organization is also very essential.
c. System architecture

Today, financial surrounding is changing constantly and for this reason banks need to discover new and advanced ways of streaming their architectures of banking. Therefore, going for easier and less complicated architectures through the virtual space of banks is very favorable for many customers. This banking system will be integrated with internet banking services and adopting a more customer-focused system and home-accessible bank accounts (Dianat et al, 2019).
I intend to improve on the security of the system especially when being accessed through the web since it is more vulnerable to attacks when accessed through the web-interface. The system will also have a simple web-interface.
The banking architecture will be broken down into the following categories.
· Mobile applications
· Web banking
· Employee portals

Phase 3: Project Plan

The figures below show a project plan for this banking system.

References

de Vries, C. G., Straetmans, S., & Hartmann, P. (2007). 4. Banking System Stability: A Cross-Atlantic Perspective (pp. 133-192). University of Chicago Press.
De Jonghe, O. (2010). Back to the basics in banking? A micro-analysis of banking system stability. Journal of financial intermediation, 19(3), 387-417.
Qureshi, T. M., Zafar, M. K., & Khan, M. B. (2008). Customer acceptance of online banking in developing economies. Journal of Internet Banking and Commerce, 13(1), 1-9.
Khrais, L. T. (2015). Highlighting the vulnerabilities of online banking system. Journal of Internet Banking and Commerce, 20(3), 1-10.
Aladwani, A. M. (2001). Online banking: a field study of drivers, development challenges, and expectations. International journal of information management, 21(3), 213-225.
Hole, K. J., Moen, V., & Tjostheim, T. (2006). Case study: Online banking security. IEEE Security & Privacy, 4(2), 14-20.
Edge, K., Raines, R., Grimaila, M., Baldwin, R., Bennington, R., & Reuter, C. (2007, January). The use of attack and protection trees to analyze security for an online banking system. In 2007 40th Annual Hawaii International Conference on System Sciences (HICSS’07) (pp. 144b-144b). IEEE.
Dianat, I., Adeli, P., Jafarabadi, M. A., & Karimi, M. A. (2019). User-centred web design, usability and user satisfaction: The case of online banking websites in Iran. Applied ergonomics, 81, 102892.

16