3.

2 Software Design Specification

3.2.1 Introduction
3.2.1.1 Goals and Objectives
The primary responsibility and objective of an effective teller is to satisfy customers. A daily goal for a
teller is accurate handling of money and a precise accounting. Accurately and efficiently process and
record routine transaction for bank customers including cashing checks, accepting deposits and
withdrawals.

3.2.1.2 Statement of Scope
The software allows handling the teller, member, and administrator records. The teller is identified by
unique id. Further the software allows generating accounts and transaction of a member also. Not only
for teller, has it stored information about the whole micro financing. So it can be used to generate
paychecks, withdrawal and deposits etc.

Major Inputs
Member name, Address, Phone numbers and email address
Member name, birthdates, class, photo
Transaction dates
Members information
Teller name, group
Billing period
Overtime
Teller pay period
Overtime
Tax rates




Processing Functionalities
Function Priority
Member information entry Essential
Teller information entry Essential
Account information Essential
Billing Essential
Overtime Essential
Receipt printing Essential
Pay check generating Essential
Verifying transaction Essential
Calculating accounts Desirable
Recording of accounts with member Desirable
Updating transaction Desirable


3.2.1.3 Software Context
This teller system software is a very efficient one, which maintains database of teller, member and their
account and transactions record. And this software is less expensive and also reduces complexity. In this
software we use Java and Net beans for the database connectivity. The database search is very fast such
that the system responds to all requests.



3.2.1.4 Major Constraints
This software is to run a system, with SQL. Therefore the system should be properly connected to server
to access database. The System should be good enough to perform all the actions.

3.2.2 Date Design
Designing data is about discovering and completely defining your applications data characteristics and
processes. Data design is a process of gradual refinement.

This systems makes no assumptions about the eventual data storage technology used to store and
retrieve your applications data. After all, it is not always obvious at the beginning of an application
design just exactly how or where the data will be stored. While most formal data modeling
methodologies anticipate using a relational database engine, an enterprise application has many data
storage options.

3.2.2.1 Internal Data Structure
In this chapter we discuss the choice of data structures for the different application parts. Next to the
top-level design, this is the most important aspect that must be specified correctly right from the
beginning of a project. The wrong choice of data structure may mean significant re-work in order to
change some deficiency later on, while on the other hand a good data structure design can simplify the
coding process and can lead to a very efficient implementation.

3.2.2.2 Global Data Structure
Date Structure and Algorithms in Java 6.0 continues to offer accessible coverage of fundamental data
structure, using consistent object-oriented framework. The authors provide intuition, description, and
analysis of fundamental data structures and algorithms. Numerous illustrations, web-based animations,
and simplified mathematical analysis justify important analytical concepts.

3.2.2.3 Temporary Data Storage
The teller system application does not use any intermediate temporary files of data.


3.2.2.4 Database Description
Below are mentioned all tables, their corresponding attributes and a small description of each.
Table name: Transaction:
Attributes: Transaction ID, Transaction no., Available balance, Amount, Remaining balance, Account ID,
Representative ID, Transaction type, Transaction Date.
Description: It hold all the general information of the teller of members facility, Primary key of this table
is transaction ID.

Table Name: Transaction Types
Attributes: Transaction Type ID, Name.
Description: It hold all general Transaction types of a teller, Primary key of this table is transaction type
ID.

Table Name: Costumers
Attributes: Members ID, Account ID, Costumer info ID, Date Created, Last Updated.
Description: This table holds the Costumers Account information of the teller. The Primary key of this
tables is member ID.

Table Name: Accounts
Attributes: Account ID, Account No., Account Types ID, Balance.
Description: The Purpose of this table is to holds the Account of a member, The Primary key of this table
is Account ID.

Table Name: Account Type
Attributes: Account Types ID, Name.
Description: The table holds the account types of a members, The primary key of this table is accounts
types ID.


ARCHITECTURAL AND COMPONENT LEVEL DESIGN
3.2.3.1 Architectural Diagram
The Architectural Context diagram for the software is shown below. As it is clear from the diagram
various actor are manager, admin staff and member, which use the system. Maintenance system is
super ordinate, which needs the software for testing and maintenance purpose.














Architectural Context Diagram
There are various types of architectural to represent the context. Basically the architectural can be
divided as system architectural.

A diagram the defines the boundary between the system or part of a system and its environment
showing the entities that interact with it. This diagram is a high level view of system.

TELLER
TRANSACTION
SYSTEM
MICROFINANCE
JAVA
(IDE 7.3)
Database
(MY SQL)
MANAGER
ADMIN STAFF
MEMBER
The call and return architecture for the child care software system is shown below (using UML
Component diagram;




















The call and Returned architecture
The call and return architecture has been dominant architecture style in large system. This is directly
supported by the classical and current programming paradigms. A number of sub-types of the styles
have emerged including main program and sub routine with shared data, layered system abstract data
type and object oriented systems etc.
MEMBER
ACCOUNT
INFORMATION
TELLER
DEPOSIT/WITHDRAWAL
INFORMATION
QUERY
(INNER JOIN)
MEMBERSHIP
PAYMENTS
ADD/MODIFY/SAVE
/DELETE
COSTUMER
INFORMATION
ADD/MODIFY/SAVE
/DELETE TELLER
INFORMATION
MEMBER
INFORMATION
MEMBER
TRANSACTION
INFORMATION

TELLER
INFORMATION
EXTERNAL
COMMUNICATION
MANAGEMENT
MAIN TELLER
TRANSACTION SYSTEM
EXECUTIVE
PRINT OR DISPLAY
HISTORY
3.2.3.2 Description of Components
3.2.3.2.1 Component Teller
Processing narrative of component Teller
The component teller contains the class teller. It contains attributes, which are the basic data, It
contains the functions, which sets all the related data into and out of database. The class teller contains
the data members and functions, which are unique to the teller. The responsibility of this component is
to declare variables of the basic data.

Interface description of the component Teller
The component teller has an interface with the class person from which it inherits attributes and
functions.

Algorithmic description of component Teller
Component Teller;
The intent of this component is to set basic teller data into the database and get data from the
database.

Start
Declare variables of the basic data
Set the basic data of the teller in the database
Get the data from the database
End

Teller
Name; String
Design class hierarchy
Person
Firstname;
Getfirstname()

Setfirstname()

3.2.3.2.2 Component Member
Processing narrative of component Member
The component member contains the class Member. It contains the attributes, which are the basic data.
It contains the function, which sets all the related data into and out of database. The class member
contains the data members and functions, which are unique to the teller. The responsibility of this
component is to declare variables of the basic data.

Interface description of the component Member
The component member has an interface with the class person from which it inherits attributes and
functions.
Algorithmic description of component Member
Component Member;
The intent of this component is to set basic member data into the database and get data from the
database.


Start
Declare variables of the basic data
Set the basic data of the teller in the database
Get the data from the database
End
Getfirstname()

Setfirstname()
Design class hierarchy
Person
Firstname;
Setfirstname()

Getfirstname()



3.2.3.2.3 Component Admin staff
Processing narrative of component Member
The component admin staff contains the class admin staff. It contains the attributes, which are the basic
data. It contains the functions, which sets all the related data into and out of database. The class admin
staff contains the data members and functions, which are unique to the admin staff the responsibility of
this component is to declare variables of the basic data.

Interface description of the component admin staff
The component admin staff has an interface with the class person from whom it inherits attributes and
functions.

Algorithmic description of components admin staff
Component admin staff;
The intent of this component is to set basic admin staff data into the database and get data from the
database.
Start
Declare variables of the basic data
Set the basic data of the admin staff in the database
Get the data from the database
Member
Account Number;

Account Name;
Set_number()

Set_name()

Set_amount()

3.2.3.2.4 Component Manager
Processing narrative of component Manager
The component Manager contains the class Manager. It contains the attributes, which are the basic
data. It contains the functions, which sets all the related data into and out of database. The class
Manager contains the data members and function, which are unique to the manager. The responsibility
of this component is to declare variables of the basic data.

Interface description of the component Manager
The company Manager has an interface with the class person from whom it inherits attributes and
functions.

3.2.3.2.5 Algorithmic description of component Manager
Component Manager;
The intent of this component is to set basic Manager Data into the database and get data from the
database.

Start
Declare variables of the basic data
Set the basic data of the teller in the database
Get the data from the database






3.2.3.2.6 Algorithmic description of component Reports
Component Reports

The intent of this component is to print the reports
Start
Get member data
Print the member data report
Get the teller data
Print the member data report
Get the withdrawal and deposit slip
Print the withdrawal and deposit report
Get the transaction data
Print the transaction data report
Get the members data
Print the members data report


3.2.3.3 Dynamic behavior for component
3.2.3.3.1 Interaction Diagrams
3.2.4 User Interface Design
3.2.4.1 Description of the user interface
3.2.4.2 Interface Design rules
3.2.4.3 Component available
3.2.4.4 UIDS Description
3.2.5 Restrictions, Limitations and constraints
3.2.6 Testing Issues




WALA PATO . :P
MEMBER
ACCOUNT
INFORMATION
TELLER
DEPOSIT/WITHDRAWAL
INFORMATION
QUERY
(INNER JOIN)
MEMBERSHIP
PAYMENTS
ADD/MODIFY/SAVE
/DELETE
COSTUMER
INFORMATION
ADD/MODIFY/SAVE
/DELETE TELLER
INFORMATION
MEMBER
INFORMATION
MEMBER
TRANSACTION
INFORMATION

TELLER
INFORMATION
EXTERNAL
COMMUNICATION
MANAGEMENT
MAIN TELLER
TRANSACTION SYSTEM
EXECUTIVE
PRINT OR DISPLAY
HISTORY