TRENT MONEY

NAME
DATE

ABS REPORT

Contents
1.

Introduction:......................................................................................................... 3

2.

System Architecture- Analysis:............................................................................. 3

3.

Components of the System:................................................................................. 4

4.

Software Architecture for ABS:.............................................................................4

5.

Appendix.............................................................................................................. 7

1. Introduction:
In this modern era, software technologies are emerging frequently. There are many
systems we interacts with, daily in our life. The successful systems, have a perfect system
architecture. A software system architecture is set of principles design decisions about the
system that meets all of the technical and operational requirements, while optimizing
common quality attributes such as performance, security, and manageability.
The Scope of the paper is developing a system architecture of Automated Banking
System for our company TrentMoney. The banking systems are complex, need to be

secure in order to avoid any financial loss. Different attributes must be taken in account
before creating a system architecture of ABS for TrentMoney: system performance,
usability, scalability, reliability and security. The system should be reliable so that it may
not crash on runtime. The system should be secure, private information should not be
exposed and it should be encrypted.

2. System Architecture- Analysis:

Different aspects should be taken into account in order to create architectural design. The
system should be able to add and modify features for future builds/amendments. The
bank workers and users should interacts with the system through different devices like
computers or mobile phones. The system should also needs to access through different
platforms. Sometimes protocols like SSL may cause installation failure, this should not
happen.

3. Components of the System:

The components of the system are Bank Server, Bank Database, Web Page, Mobile
Phone, and ATM (Automated Teller Machine).Webpage or userpanel can be accessed by
users via computers devices. Using user panel, users can do different transactions such as,
pay bills, transfer amount, and do subscriptions. Bank Workers can access webpage via
employee section using computer device. Employee can perform administrative tasks in
this section. User can also perform transactions from mobile device via TrentMoney
application installed on devices. Users can access ATM to withdraw amount, deposit
amount, transfer funds and pay bills.
All these components such as ATM, Webpage, and mobile phone application interacts
with bank server at backend. Every transaction record saves at the backend in Bank
database.

So system components are computers, mobile devices, ATM, bank database servers and
bank webservers. Before designing software architecture, keep in mind that all these
system components should be independent of other components. They must share the
information only at real time.

4. Software Architecture for ABS:

In this section we will discuss three software architectures for TrentMoney ABS: Clientserver architecture, Three-tier architecture, and Space based architecture.
4.1.
Client-server architecture:
This architecture ensures independent components sharing information run time. It
has two key groups: servers and clients. Clients request services from centralized
server and server responds them, serves client with transaction he requested. The
communication is done by standard TCP/IP network connection. For TrentMoney
ABS the client nodes are ATMS, mobile devices and computer that are requestors.
The transaction details are sent to server and saves in database to keep track of
records later. The server nodes is bank database and bank server which responds to
client on request. The benefit of using client architecture is that more devices can be
added to access same network using API (application programming interface). So
using this architecture, TrentMoney can give access clients to centralized system via
new devices in future (e.g. google glass, smart watches etc.). The concept of a
centralized system allows for the clients to access these servers without actually
knowing how many or which servers they are communicating with. The topological
diagram of client-server architecture for TrentMoney ABS is in Appendix 1.0.
Appendix 1.1 refers the deployment diagram of the current architecture.

The issue with client server architecture is that its all components needs to be
connected from server to server. If server is down, it will cause whole system
shutdown.
4.2.
Three-Tiered Architecture:
The server connection issue of client server architecture can be solved by separating
components in separate layers. For example put aside server side which will deal only
with the data. Three tiered architecture consists of three layers presentation layer,
domain layer and technical services layer. All these layers are impendent modules
coupled with each other using controllers or adapters. Each modules can be enhances
or modified using adapters leaving other modules unaffected. This is the major
benefit of architecture. The presentation layer includes client components. The
domain layer houses application logic in which all data processing takes place. The
technical services layer houses server components. Application layer takes
information from any device or medium and forward it to domain layer. Devices can
be added via writing adapters/programs on the top of this layer via API. Application
layer demands more security for user authentication, banking system may add more
secure protocols to make it more secure. The topological diagram for three- tiered
architecture is shown in Appendix 2.0 and deployment diagram in Appendix 2.1.
4.3.
Space Based Architecture:
This architecture supports scalability which supports many processing units to be
added in the system. With each transaction processed, each processing unit will be
created. With each processing unit, clients can post request to servers and servers do
work and return appropriate responses to the client. The topological diagram for
Space based architecture is shown in appendix 3.0 and deployment diagram in
Appendix 3.1.

5. Appendix
1.1.

Topological diagram for Client-Server Architecture:

1.2.

Deployment diagram for Client-Server Architecture:

2.0. Topological

diagram for Three-Tiered Architecture:

2.1. Deployment diagram for

Three-Tiered Architecture:

3.1. Topological diagram for Space Based Architecture:

3.2. Deployment diagram for Space Based Architecture:

References
Du, Richard T. "Client/Server Feasibility." Information Systems Management 11.3 (1994): 7982. Academic Search Premiere. Web. 05 Nov. 2010.
Gallaugher, John, and Suresh Ramanathan. "Choosing a Client/Server Architecture."
Information Systems Management 13.2 (1996): 7-13. Academic Search Premiere. Web. 05 Nov.
2010.

"Introduction to 3-Tier Architecture." DotNetSlackers: ASP.NET News and Articles For Lazy
Developers. Web. 05 Nov. 2010.
"Owen Taylor on 'Space Based Architecture' - TheServerSide.com." TheServerSide.com: Your
Java Community Discussing Server Side Development. Web. 05 Nov. 2010. .