BANKING SYSTEM’S OBJECT MODEL AND AN INSTANCE DIAGRAM OF THE

MODEL

KWADWO KYEREMEH
SUNYANI TECHNICAL UNIVERSITY
DEPARTMENT OF ACCOUNTANCY

KYEREMEH BEDIAKO BRIGHT

SUNYANI TECHNICAL UNIVERSITY
DEPARTMENT OF COMPUTER SICIENCE

Abstract

We have seen developing enthusiasm for approval of a business handle before it is executed due
to the many-sided quality to model business handle. In this paper, we propose a technique for
examining and approving the practical accuracy of a business, procedure shows. In view of our
past work, we display a business procedure in UML action outlines with OCL imperatives, then
we give a formal semantics of the business prepare the show, at long last, we approve the model
by prototyping. We have built up an apparatus—AutoPA to bolster our strategy. At the point when
applying the apparatus, a business procedure demonstrates indicated by UML action outlines with
OCL requirements are changed into an executable model in Java. Both the control stream
measurement also, the data flow measurement of the model is considered. With the model, clients
can approve the practical properties of the business handle shows in an intelligent way. We utilize
a certifiable the case as a contextual investigation: the business procedure of the primary
conveyance of home loan document in a hazard alleviation arrangement of a boycott (Isoda, 2003).

Literature Review

As the software project manager at the bank, I am going to use this work to provide a formalized
banking system’s Object Model and an instance diagram of the model with the head office

Electronic copy available at: https://ssrn.com/abstract=3455429

coordinates transactions and management activities of the 10 branches Transactions involving
credit and debit of accounts are done at all branches and the two types of accounts at the bank
owned by customers are savings and current accounts. This work will show how the banking
network is done and how they operate from head office to the branches using UML diagrams.

Introduction

In the present Situation according to (Isoda, 2003), the focused environment in managing a
banking sector, worldview is evolving quickly. Different new things can be found in managing a
banking sector, since it is embracing new ideas furthermore, innovation to enhance their business
and to win the fulfillment of their clients. The show paper talks about the part of Unified Modeling
Language (UML) in the Object Oriented Database Management Systems (OODBMS) banking
sector. The Object Oriented Database innovation is considered as the fifth era database innovation.
OODBMS can be considered as a mix of two technologies, Database Management Systems and
Object Oriented systems. A contextual investigation in to the banking systems has been taken to
clarify how different accounts and transactions can be arranged. Object oriented Data Modeling
procedure has been used to store the information and it is spoken to with the assistance of UML
Use-Case diagram, Object Model Diagram, Sequence diagram and Instance diagrams

Object Model

The diagram below is as opined by (Simons, A. J. H., 1999), describing a formalized banking
system’s Object Model and an instance diagram of the model with a head office that coordinates
transactions and management activities of the 10 branches and it also show that transactions
involving credit and debit of accounts are done at all branches. The types of accounts at the bank
owned by customers are savings and current accounts of Bank Accounts using
UML generalization sets. Bank accounts could be grouped into UML generalization sets based on
different criteria. Example diagram below shows bank accounts split by savings type and current
account type. These two dimensions also have corresponding branches out of the 10 branches and
it also show that a customer can have two or more bank accounts either for personal or for business
purposes. From the diagram again you can see that all the branches are being supervised and
coordinates by the head office

Electronic copy available at: https://ssrn.com/abstract=3455429

Take note of, that entrepreneurs still may utilize an individual accounts for their business purposes
yet it is not suggested basically on the grounds that it can influence lawful risk of entrepreneur.
From the bank's perspective, e.g. at the point of account opening, these two will be two various
types of accounts.

Transaction
Head Office Withdrawal Amount
Deposit Amount
Location
* Time
City

Ad
Transaction Type
mi
Branch Identifier Code ist n
e

Name of Bank
rs

* *
tra
ns
ac

1
tio
n

Coordinates
* Credit
1
Debit from to

Branches (10) 1 1

Accounts Customer
Branch Identifier Code Account Number Customer Number
keeps Owns by
* Account balance *
1 1 Customer Full Name
Address Interest on Account Customer Address
Account Fees Date of Birth
City

1 Account Type

Belongs to
*

Employee Current Accounts

Savings Accounts Account Number
Employee Number Account Number Account Balance
Employee Name Account Balance Account Fees
Account Fees Interest on Accounts
Employee Branch Code
Interest on Accounts
Address

Figure 1: Object Model

Source: Source: (Self Work)

People open savings account so as to allow them to make savings. The holder of the account can
be making some withdrawals and deposit in a limited options each month and this kind of
accounts provides no cheque books but they usually gives interest on the amount in the accounts
which is mostly higher than that of the current account but also lower than the investment
account.
Current account is a type of account at the bank that uses cheque as the way withdraws or
transfer money from account and also do some transactions like, paying bills, transfer or loans. It
also happens that, holders of current account are allowed to make withdrawals and make deposits

Electronic copy available at: https://ssrn.com/abstract=3455429

using automated teller machines (ATM) at the various branches of the banks. Current accounts
that offer interest normally require higher minimum balances but they pay interest based on the
amount maintained in the account as a minimum balance and usually offer the best of services
and allow them to make unlimited withdrawals through cheque. We will use the diagram to talk
much about how case diagrams relates (Jacobson, 2004).

1.3 Use Case Diagram

Branch Report Perform Transaction

Customer
Branch
Employee

Debit and Credit

Accounts

Headquarters
Officer

Charge Accounts Fees

Branch

Check Customer Get Branch Report

Balance

Figure 2: Use Case Diagram

Source: (Self Work)
The Use Case Diagram depicts how various actors in NYALEY banking system interacts with the
system. The role perform by each actor is displayed with an arrow linking to the diagram. Actors
could be human being or other parts of the system interacting with each other.

The actors are:

Electronic copy available at: https://ssrn.com/abstract=3455429

1. Branch Employee

2. Branch (Manager)

3. Headquarters Officer

4. Customer

1. Branch Employee: The Branch employee is an actor who can get, print or change the
branch reports. The branch employee can also check customer balance, debit or credit
customer accounts as depicted by the Use Case Diagram.
2. Branch (Manager): In this instance represents by the Manager or anybody with manager
privileges can charge accounts fees or set up new fees in the system.
3. Headquarters Officer: The headquarters officer can request to get branch report and get it
back by interacting with the system through various faces until the report is displayed and
made available to the Officer.
4. Customer: The customer can perform a transaction on the account and check balance from
the system as depicts by the use case diagram.

The Use Case is very important during documentation of system requirements. It helps the
developer and other stakeholders to understand how various actors can interact with the system. It
also helps stakeholders identify the functions or what business needs the system will solve and at
what level.

Also from the use case, you can determine other areas of the system that can be represented at the
same level of abstraction and other areas that can be represented at lower levels of abstraction. It
also represents external view of the system and help you to understand how interaction will be
done from external sources.

Electronic copy available at: https://ssrn.com/abstract=3455429

1.4 Sequence Diagram

Figure 3: Sequence Diagram

Source: (Self Work)

The Sequence Diagram above depicts steps by steps head office officer will follow to get a report
from a branch.

1. The Officer selects Reports button from the banking system.

2. The officer select branch identifier code from the lists of code displayed.
3. The Officer confirms that the right branch code has been selected.

Electronic copy available at: https://ssrn.com/abstract=3455429

 4. Having confirm the branch code, the officer then retrieves the branch reports by selecting
Get Branch Reports.
5. The branch returns all the transaction of the branch in a form of reports.
6. The Branch Reports is then display to head office through the Baking System. The
process then ends.

1.5 Instance Diagram Showing Branch and Accounts

Figure 4: Instant Diagram

Source: (Self Work)

This Sequence diagram above shows how transaction is done from the head office Nyaley Savings
and Loans to the branches on customers accounts. we can see according to the diagram that the
work mostly comes from the head office and they accountant at the head office has to choose the
branch where the customer account is and in reaching out to the branch he has to also select the
type of account that the client is operating, that is either Saving Account or Current Account.

Electronic copy available at: https://ssrn.com/abstract=3455429

Transaction request can be sent then to search for the customer information and this request would
either go to the customer service or be processed instantly and afterwards a notification would be
sent to the customer through sms or email after the account of the customer has been duly updated.

Conclusion

I conclusion I will say that according the diagrams so far I can confidently say that the models
that I have provided above and the explanations shown so far that they can assist the
analysis/design process of the banking systems on Nyaley Savings and Loans in their day to day
banking activities at the head office and also the 10 networked branches. With the model, clients
can approve the practical banking transactions. We utilize a certifiable the case as a contextual
investigation: the business procedure of the primary conveyance of home loan document in a
hazard alleviation arrangement of a boycott in the banking industry.

Reference
• Ge’nova, G., Llorens, J. and Quintana, V . (2002) Digging into use case relationships.
Proc.UML’2002, Dresden, Germany, September 30-October 4, pp. 115-127.LNCS 2460,
Springer-Verlag, London, UK.
• Genilloud, G. and Frank, W.F. (2005) Use case concept using a clear, consistent, concise
ontology. J.Object Technol., 4, 95-107
• Isoda, S. (2003) A critique of UML’s definition of use case class. Proc. UML 2003, San
Francsico, CA,USA, October 20-24, pp. 280-294. LNCS2863, Springer-Verlag, London,
UK.
• Jacobson, I. (2004) Use cases-yesterday, today, and tomorrow, Software Syst. Model., 3,
210-220.
• Simons, A. and Graham, I. (1999) 30 things to go wrong in object modelling with UML
1.3. In Kilov, H., Rumpe, B and Simmonds, I. (eds), Behavioural Specifications of
Businesses and Systems. Kluwer Academics Publishers, Norwel, MA, USA.

Electronic copy available at: https://ssrn.com/abstract=3455429

• Simons, A.J.H. (1999) Use case considered harmful. Proc. TOOLS/Europe’99, Nancy,
France, June 7-10, pp. 194-203. IEEE Computer Society, Washington, DC, USA.
• Page-Jones, Meilir (2000) Fundamentals of Object-Oriented Design in UML.
AddisonWesley, Boston, USA.

• Rumbaugh, James, Ivar, Jacobson, and Grady Booch (2005) The Unified Modeling
Language Reference Manual, 2nd ed. Addison-Wesley, Boston, USA.
• A Case Study of an Object Oriented Data base Implementation, Billy Gibson, APM.
1608.00.02 Draft 10th October 1995
• Saxena, V., Ajay Pratap, “Modeling Obeject Oriented Data base through UML: A Case
Study of Post Office Savings Bank in India” International Conference on Technology and
Innovation (ICT 2011), 26 July, 2011, Gren Park Hotels Chennai.
• Albano, G. Ghelli, and R, Orsini (1991) A relationship mechamsm for strongly typed
Object Oriented database programming Languages. In Proc. Of VLDB-91, pages 565-575,
Barclelona, Spain.
• Hurson, A. R. And Pakzad, H (1993) Object Oriented Database Management System:
Evolution and Performance Issies, IEEE Publication,
• 10. Hurson A. R. And Pakzad H. Object Oriented Database Management System:
Evoluation and Performance Issues, IEEE Publication, 1993.
• http://www.uml.org.cn/UMLApplication/UMLApplication2.htm.
• https://northwinddatabase.codeplex.com/.
• https://www.tutorialspoint.com/uml/uml_class_diagram.htm.
• http://www.ie.inf.uc3m.es/wuscam-05/5-WUsCaM.pdf.
• http://www.uml.org.cn/UMLApplication/UMLApplication2.htm.
• http://www.dba-oracle.com/t_object_oriented_approach.htm.

Electronic copy available at: https://ssrn.com/abstract=3455429