Use Cases

for

Inter-Bank Fund Transfer

Version 1.0 approved

Prepared by Soumitra Ghosh

Roll Number: MT/CS/10016/14

BIT Mesra, Ranchi

23/01/2015

Copyright 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page ii

Revision History
Name

Date

Reason For Changes

Version

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 1

Guidance for Use Case Template

Document each use case using the template shown in the Appendix. This section provides a description of
each section in the use case template.

1. Use Case Identification

1.1. Use Case ID
Give each use case a unique numeric identifier, in hierarchical form: X.Y. Related use cases can be
grouped in the hierarchy. Functional requirements can be traced back to a labeled use case.

1.2. Use Case Name

State a concise, results-oriented name for the use case. These reflect the tasks the user needs to be able to
accomplish using the system. Include an action verb and a noun. Some examples:

View part number information.

Manually mark hypertext source and establish link to target.

Place an order for a CD with the updated software version.

1.3. Use Case History

1.3.1 Created By
Supply the name of the person who initially documented this use case.

1.3.2 Date Created

Enter the date on which the use case was initially documented.

1.3.3 Last Updated By

Supply the name of the person who performed the most recent update to the use case description.

1.3.4 Date Last Updated

Enter the date on which the use case was most recently updated.

2. Use Case Definition

2.1. Actor
An actor is a person or other entity external to the software system being specified who interacts with the
system and performs use cases to accomplish tasks. Different actors often correspond to different user
classes, or roles, identified from the customer community that will use the product. Name the actor(s) that
will be performing this use case.

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 2

2.2. Description
Provide a brief description of the reason for and outcome of this use case, or a high-level description of the
sequence of actions and the outcome of executing the use case.

2.3. Preconditions
List any activities that must take place, or any conditions that must be true, before the use case can be
started. Number each precondition. Examples:
1. Users identity has been authenticated.
2. Users computer has sufficient free memory available to launch task.

2.4. Postconditions
Describe the state of the system at the conclusion of the use case execution. Number each post-condition.
Examples:
1. Document contains only valid SGML tags.
2. Price of item in database has been updated with new value.

2.5. Priority
Indicate the relative priority of implementing the functionality required to allow this use case to be
executed. The priority scheme used must be the same as that used in the software requirements
specification.

2.6. Frequency of Use

Estimate the number of times this use case will be performed by the actors per some appropriate unit of
time.

2.7. Normal Course of Events

Provide a detailed description of the user actions and system responses that will take place during execution
of the use case under normal, expected conditions. This dialog sequence will ultimately lead to
accomplishing the goal stated in the use case name and description. This description may be written as an
answer to the hypothetical question, How do I <accomplish the task stated in the use case name>? This is
best done as a numbered list of actions performed by the actor, alternating with responses provided by the
system.

2.8. Alternative Courses

Document other, legitimate usage scenarios that can take place within this use case separately in this
section. State the alternative course, and describe any differences in the sequence of steps that take place.
Number each alternative course using the Use Case ID as a prefix, followed by AC to indicate
Alternative Course. Example: X.Y.AC.1.

2.9. Exceptions
Describe any anticipated error conditions that could occur during execution of the use case, and define how
the system is to respond to those conditions. Also, describe how the system is to respond if the use case
execution fails for some unanticipated reason. Number each exception using the Use Case ID as a prefix,
followed by EX to indicate Exception. Example: X.Y.EX.1.

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 3

2.10. Includes
List any other use cases that are included (called) by this use case. Common functionality that appears in
multiple use cases can be split out into a separate use case that is included by the ones that need that
common functionality.

2.11. Special Requirements

Identify any additional requirements, such as nonfunctional requirements, for the use case that may need to
be addressed during design or implementation. These may include performance requirements or other
quality attributes.

2.12. Assumptions
List any assumptions that were made in the analysis that led to accepting this use case into the product
description and writing the use case description.

2.13. Notes and Issues

List any additional comments about this use case or any remaining open issues or TBDs (To Be
Determineds) that must be resolved. Identify who will resolve each issue, the due date, and what the
resolution ultimately is.

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 4

Use Case for Fund Transfer

Use Case ID:
Use Case Name:
Created By:
Date Created:

1
Fund Transfer
Soumitra Ghosh
01/02/2015

Last Updated By: Soumitra Ghosh

Date Last Updated: 01/02/2015

Actor: Bank A (Remitter)

Description: Transfers required amount from one bank to another bank
Preconditions: 1. The Remitter must have a valid existing account in any
particular bank
2. A minimum amount must be present in the account to qualify for
the transfer.
Postconditions: Response message should be received from the receiver bank
regarding the fund transfer
Priority: Both banks must be participants in the qualifying list of banks to
Central Bank eligible for fund transfer
Frequency of Use: On need
Normal Course of Events: 1. Fill in the Inter-Bank Fund Transfer form available at the sender
bank.
2. Submit it to that bank.
Alternative Courses: In case of insufficient balance in the account or wrong information
provided in the fund transfer form, the customer must be notified
about it.
Exceptions: 1. Internet is not working
2. Sender has insufficient balance
3. Wrong details provided while filling the fund transfer form
Includes:
Special Requirements: 1. Hardware Requirement
a)

Processor - Pentium -Iii

b) Speed - 1.1 GHz

c)

Ram - 256 Mb(Min.)

d) Hard Disk - 20 Gb
e)

Floppy Drive - 1.44 Mb

f)

Key Board - Standard Windows Keyboard

g) Mouse - Two Or Three Button Mouse

h) Monitor - SVGA

2. Software requirement:
a) Operating System: Windows 2000.
b) Technology: Net/J2ee

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 5

c) Database: Oracle 8i
Assumptions: The customer has the receivers account number
Notes and Issues:

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 6

Use Case for Fund Receive

Use Case ID:
Use Case Name:
Created By:
Date Created:

2
Fund Receive
Soumitra Ghosh
01/02/2015

Last Updated By: Soumitra Ghosh

Date Last Updated: 01/02/2015

Actor: Bank B (Beneficiary)

Description: Receives the fund transferred by the remitter
Preconditions: A valid sender has sent fund to the remitter.
The clearing house has authenticated the remitter as well as the
receivers account details.
Postconditions: Acknowledge the sender about the successful fund transfer.
Priority:
Frequency of Use: On demand
Normal Course of Events: 1. The clearing house validates the transfer message of the sender
along with the receivers details, and forward the request to the
Central Bank.
2. The Central Bank makes the fund transfer between the accounts
of the sender and the receiving bank.
3. Updates the clearing house about the transfer.
4. The clearing house confirms the transfer to the receiver bank.
Alternative Courses: On failure of fund transfer, re-transfer mechanism must be tried out.
Exceptions:
Includes:
Special Requirements: 1. Hardware Requirement
A. Processor - Pentium -Iii
B. Speed - 1.1 GHz
C. Ram - 256 Mb(Min.)
D. Hard Disk - 20 Gb
E. Floppy Drive - 1.44 Mb
F. Key Board - Standard Windows Keyboard
G. Mouse - Two Or Three Button Mouse
H. Monitor SVGA
2.

Software requirement:
a) Operating System: Windows 2000.
b) Technology: Net/J2ee

c) Database: Oracle 8i
Assumptions: The sender has sent the fund.

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 7

The sender has sufficient amount in his account to make the fund
transfer.
Notes and Issues:

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 8

Use Case for SWIFT

Use Case ID:
Use Case Name:
Created By:
Date Created:

3
SWIFT
Soumitra Ghosh
01/02/2015

Last Updated By: Soumitra Ghosh

Date Last Updated: 01/02/2015

Actor: Remitter, Beneficiary, Clearing House, Central Bank

Description: The main security control features of the SWIFT system includes
end-to-end authentication, i.e. authentication between two banks
detecting any bogus payment message, sequence number control,
user access control, and encryption between operating centres.
Preconditions: SWIFT requires that each customer have a dedicated terminal with
pre-accredited software. That dedicated terminal will include
encryption, authentication, and data scrambling on it.
Postconditions:
Priority: Internet Connection
Frequency of Use: On any type of online transaction
Normal Course of Events: Operating centers of SWIFT are located in the U.S., Belgium, and
the Netherlands with store and forward procedures processing all
messages.
In member countries, there are regional processors connected to
operating centers by leased lines.
The connections are duplicated to cope with contingencies.
All connections from member banks to the network are concentrated
through regional processors, and there are emergency lines to let
customers connect to alternative regional processors when one
processor becomes corrupt.
The SWIFT system can report statistics on messages sent and
received.
Alternative Courses: In case of attempts to attack the system or hinderance caused during
fund transfer, reports must be generated about such events.
Exceptions:
Includes:
1. Bank-to-Center Authentication
2. Link-to-Link Authentication.
Special Requirements: 1. Hardware Requirement
a) Processor - Pentium -Iii
b) Speed - 1.1 GHz
c) Ram - 256 Mb(Min.)
d) Hard Disk - 20 Gb
e) Floppy Drive - 1.44 Mb
f) Key Board - Standard Windows Keyboard

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 9

g) Mouse - Two Or Three Button Mouse

h) Monitor SVGA
2.

Software requirement:
a) Operating System: Windows 2000.
b) Technology: Net/J2ee
c) Database: Oracle 8i

Assumptions:
Notes and Issues:

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 10

Use Case for Settlement

Positions
Use Case ID:
Use Case Name:
Created By:
Date Created:

4
Settlement Positions
Soumitra Ghosh
01/02/2015

Last Updated By: Soumitra Ghosh

Date Last Updated: 01/02/2015

Actor: Clearing House

Description: The clearing house is a voluntary association of banks under the
management of a bank where the settlement accounts are maintained.
Wherever Reserve Bank of India has its office (and a banking
department), the clearing house is managed by it.
Preconditions: A fund transfer request has been made by a sender bank with all the
required information about itself and the receiver bank.
Postconditions: 1. The clearing house has send the transfer request to the central
bank
2. The central bank has made the required transfer
Priority:
Frequency of Use: On any type of online transaction
Normal Course of Events: 1. The clearing house validates the transfer information of the
Sender
2. It sends the request to the Central Bank
3. The central bank makes the necessary transfer
4. The transfer is reflected in the receivers and senders account
5. Respective debit and credit is made in the involved banks
accounts
Alternative Courses: In case of any erroneous transaction or transaction failure, the
clearing house must set the scenario to a previous checkpoint.
Exceptions:
Includes:
Special Requirements: 1. Hardware Requirement
a) Processor - Pentium -Iii
b) Speed - 1.1 GHz
c) Ram - 256 Mb(Min.)
d) Hard Disk - 20 Gb
e) Floppy Drive - 1.44 Mb
f) Key Board - Standard Windows Keyboard
g) Mouse - Two Or Three Button Mouse

Use Cases for Inter-Bank Fund Transfer in Distributed Network

Page 11

h) Monitor SVGA
2.

Software requirement:
a) Operating System: Windows 2000.
b) Technology: Net/J2ee
c) Database: Oracle 8i

Assumptions: A sender has requested for fund transfer

Notes and Issues: