Project Documentation

Online Co-Operative System 2010
PROJECT
DOCUMENTATION
Project Title: Online Co-operative System
Sundar Saving & Credit Co-Operative Ltd.

Sinamangal, Kathmandu
Nepal.
Project Group Members:

Ram Kumar Bhandari (ID: 1801T3080068)
Bibek Bam (ID: 1801T3080056)
Sailesh Neupane (ID: 1801T3080076)
CENTER: INFORMATICS COLLEGE, KATHMANDU NEPAL
PROJECT SUPERVISOR: PRASHANT LAL SHRESTHA
TIME FRAME:
Sundar Saving & Credit Co-Operative Ltd. 1

TABLE OF CONTENTS
PROPOSAL .......................................................................................................................................................................... 6
Introduction...................................................................................................................................................................... 7
Organization ..................................................................................................................................................................... 8
Current System................................................................................................................................................................ 9
DFD for the Current System .................................................................................................................................... 9
Basic Problems and Limitations ......................................................................................................................... 11
Proposal of the New System .................................................................................................................................. 12
Objectives of the System:....................................................................................................................................... 12
Description of the system: .................................................................................................................................... 12
First Module: Admin Panel............................................................................................................................... 14
Second Module: Staff Panel .............................................................................................................................. 14
Third Module: Customer Panel / Guest Panel .......................................................................................... 14
Initial Specification .................................................................................................................................................... 15
Functional Specification: ....................................................................................................................................... 15
Non-Functional Specification............................................................................................................................... 15
Work Distribution ...................................................................................................................................................... 16
Benefits of the New System ................................................................................................................................... 20
Hardware and Software Specification............................................................................................................. 20
For development:...................................................................................................................................................... 20
For Operation of System: ....................................................................................................................................... 21
Cost/ Benefit Analysis of New System ............................................................................................................. 22
Payback Period Analysis Table:.......................................................................................................................... 24
Return on Investment Analysis: ......................................................................................................................... 24
Gantt Chart...................................................................................................................................................................... 24
ANALYSIS ......................................................................................................................................................................... 26

Introductive Description ........................................................................................................................................ 27
Fact findings................................................................................................................................................................... 28
Interview ...................................................................................................................................................................... 28
Questionnaire and survey ..................................................................................................................................... 34
Observations ............................................................................................................................................................... 41
Research ....................................................................................................................................................................... 42
Final Requirements from the Fact- Findings ............................................................................................... 42
Functional Requirements ...................................................................................................................................... 42
Non-Functional Requirements ............................................................................................................................ 43
Description of the Current System .................................................................................................................... 44
Organizational Structure ....................................................................................................................................... 45
Roles and Responsibilities within the organization ................................................................................... 45
Input/Output Specification of the current system ................................................................................... 48
Process Flow Diagram (Data Flow Diagram) .............................................................................................. 51
Problems and Limitation of the system.......................................................................................................... 53
Scope and Constraints .............................................................................................................................................. 55
Requirements Specification .................................................................................................................................. 57
Module 1: "System Administration Module" ................................................................................................. 57
Module 2: "Employee Panel Module" ............................................................................................................... 57
Module 3: "Customer Panel Module"................................................................................................................ 58
Module 4: "General Visitor Module" (Website)............................................................................................ 58
DESIGN .............................................................................................................................................................................. 59
Description of the new System ............................................................................................................................ 60
Functional Modeling ................................................................................................................................................ 60
Data Flow Diagram .............................................................................................................................................. 60
Data Dictionary ..................................................................................................................................................... 63
Behavioral Modeling ............................................................................................................................................... 79

State Transition Diagram.................................................................................................................................. 79
Data Design .................................................................................................................................................................... 86
Introduction ................................................................................................................................................................ 86
Database System ....................................................................................................................................................... 86
Data Used in system................................................................................................................................................. 86
Entity Relationship Diagram [Before Normalization] ............................................................................... 93
Normalization ............................................................................................................................................................ 95
Entity Relationship Diagram (After Normalization) ................................................................................ 100
Converting Entities into Relations (Tables) ................................................................................................ 102
Relationship Description between the entities (Relations) .................................................................. 113
Architectural Design ............................................................................................................................................... 118
Introduction .............................................................................................................................................................. 118
Architectural Modules .......................................................................................................................................... 118
Administrative Module .................................................................................................................................... 118
Employee Module .............................................................................................................................................. 120
Customer Module ............................................................................................................................................... 120
General Visitors Website ................................................................................................................................ 120
Program Structure.................................................................................................................................................. 122
Administrative Module .................................................................................................................................... 122
Employee Module .............................................................................................................................................. 128
Customer Module ............................................................................................................................................... 128
Procedural Design .................................................................................................................................................... 129
Interface Design......................................................................................................................................................... 137
Hardware and Software Selection .............................................................................................................. 159
DEVELOPMENT AND IMPLEMENTION ........................................................................................................... 163
Testing ............................................................................................................................................................................ 164
Introduction .............................................................................................................................................................. 164

Testing Strategies ................................................................................................................................................... 164
Testing Techniques ................................................................................................................................................ 164
Test Plan ..................................................................................................................................................................... 165
System Implementation ........................................................................................................................................ 206
USER MANUAL:........................................................................................................................................................ 207
Critical Appraisal ...................................................................................................................................................... 244

PROPOSAL

INTRODUCTION
With the purpose of serving the mankind, society and the economy of the nation as a whole,
Sundar Saving & Credit Co-Operative Ltd. was formally established in 2009 A.D. (2065
B.S.) getting approval by the Nepal Government under the “Co-Operative Act 2048” at
Sinamangal- 09, Kathmandu, Nepal with the total numbers of 27 shareholders who are doing
their best for the development of their organization.
The main objectives of the cooperatives is to promote and develop saving habits, provide
loan with reasonable interest rate to fulfill the financial necessities of its members as well as
provide loan for starting small business activities to the local people for improving their
socioeconomic condition as well as help in developing, promoting and strengthening
economic activities. It has introduced different deposit schemes which have encouraged
people for saving. Some of them are as follows:
 Fixed deposit Account
 Regular Saving Account
 Premium Saving Account
 Regular Fixed Account
 Monthly Saving Account
There are the different additional saving schemes that are going to be introduced
in near future which will even benefit the members more. Besides involving in the different
activities financial activities, it has been even organizing the different social programs in the
local area for creating the social awareness in the society.

ORGANIZATION
Started with the total of 27 shareholders, a chairman elected between them and managing
Director, this organization has three departments namely finance, marketing and
miscellaneous controlled by the central manager of the organization.
Board of Directors Chairman

Sunita Dhakal(Bhattarai)
Managing
Director
Sachin Bhattarai
Operational
Manager
Rahul Bhattarai
Human Resource Marketing

Finance Manager Miscellaneous
Manager Manager
Arun Adhikari Deepa Baral
Parmeswor Dahal Sumitra Kafle
Loan Manager Cash Manager Ward no.9 Ward no.34 Ward no 32

Pukar K.C. Sabina Dahal Sumi Khadka Ram Dahal Ramesh Thapa
Counter 1 Counter 2 Counter 3

Binisha Timsina Sailendra Duwadi Rina Bastola
Organization Chart

CURRENT SYSTEM
At present the Co-Operative doesn‟t have an internet based online banking system. They are
performing their transaction by using some desktop based accounting software such as Tally.
The data are fed into the system by using the batch processing. The database company is
using is the Microsoft Access 2003 and the company does not have any Database
Management System to manage and control the database.
A customer or an Account holder has to frequently visit the Co-Operative at its place to know
about their account information. The brochures and the verbal communication are the major
way of getting information about the Co-Operative. Different software is used for different
purpose. There is no one program that can handle the multitasking operations. Besides
customer stand up in the line and wait for their turn. Large numbers of staff are appointed to
handle the customer. The basic concept of current system can be portrait with the help of
following Data Flow Diagram.
DFD FOR THE CURRENT SYSTEM
Request for information Apply for Loan

Provides the information Issue Loan
Current Banking Customer (Loan)
Customer ( deposit ) Apply for account open
System
Provide the A/C No.
Context Diagram
(current system)

Customer A/C
reception Transaction
Customer (loan)
process Process
Request for Provides

Information the Information Accept/reject Apply for
Loan Loan
A/C Updated A/C
Information Information
Loan
Customer (deposit) Loan Information acception/
rejection
Customer A/C Loan data process
Apply for A/C Request for

Issue A/C no proposal study
Open
Proposal study
report
Customer Data
A/C opening Loan proposal
process Account Information study process
Diagram 0
(current system)

BASIC PROBLEMS AND LIMITATIONS
As mentioned the current system is not fully customer oriented. It has not been able to
address the basic problem of the optimizing use of valuable time of both the customers as
well as of the Co-Operative members including the staffs and other concerned personals.
Besides that, the current system has not been utilizing the full features of the technology
which is the most for the competitive business arena and to provide the best of the services to
the customer efficiently and reliably with the high degree of the security.
There is the lack of the mechanism that can handle the management of all the operations and
transactions along with the task of flexible transactions. There is no solid way for providing
the information regarding the Co-Operative so that the visitors have to use their valuable time
coming to the office itself and get information after some time of waiting.
So the basic problems faced with the current system can be summarized as follows:
 Lack of proper information management methodologies.
 Unavailability of efficient information processing system.
 Much time consuming.
 Lack of proper way of publicity and information flow between the customers.
 Lack of reliable and secure data storage medium with the provision of proper backup
system.
 The operation cost is very high.

PROPOSAL OF THE NEW SYSTEM
To trounce the problems and the limitations showed by the current system, a new system is
proposed. The new system (used as „System hereafter‟) will be a web based application
system which will use the well established way of information management.
OBJECTIVES OF THE SYSTEM:
 The system will address the problem of the information management by processing
the all data and information electronically.
 The system will have the provision of reliable and efficient data storage warehouse
with much higher flexibility.
 The system will maintain the higher degree of security of the data which is crucial.
 Customer can have more access to their account and data.
 The time consumption will be minimized since customer can get required information
from anywhere by the use of internet.
 System will not need many resources to operate and hence the operation cost can be
substantially reduced.
 It will help to eliminate the use of different types of software for a single transaction
purpose.
DESCRIPTION OF THE SYSTEM:
As motioned earlier, the system will be a web based application and use CMS (Contain
Management System) technology that it can be updated by the person who need not be an IT
professional. It means that the system will be user friendly. The system will be able to handle
the information processing plus the transaction processing.

Apply to open Apply for

account Loan
A/C no. Online Banking Accept/Reject Customer (Loan)

Customer (Deposit) System Loan
Deposit/Withdraw
A/C Information
Context Diagram
(New System)
A/C Information
Deposit/withdraw request
A/C Information
Money Deposit/ Queries
Withdraw processing
Banking Information
process process
Transaction
data
Customer(Deposit) Customer(Loan)
Online Banking
Apply for new Provides

Account A/C no. Accept/Reject Apply for
Loan loan
Customer data
New A/C Loan evaluation
Transaction
opening process A/C Information process
data
Diagram 0
(New System)
The new system will contain the 3 major modules.

FIRST MODULE: ADMIN P ANEL

This module contains the process for controlling the overall function of the system and can be
accessed by only one person i.e. administrator. The administrator can perform such as adding
the staff users, deleting the staff users, modifying the contents of the website and providing
privileges to different users.
SECOND MODULE: STAFF PANEL

This module acts as the platform for the staffs for the transaction. From this, the staffs can
add, delete, edit the customer account and also perform the daily transaction.
THIRD MODULE: CUSTOMER P ANEL / GUEST PANEL

The customer and other general viewer can access the system by this module. This module
will contain the information regarding the Co-Operative and also account holder can get their
account information by login through the system.

INITIAL SPECIFICATION
FUNCTIONAL SPECIFICATION:
 The system should provide the different types of interface for general users,
customers/members, staffs and administrator.
 The system should be able to carry out the simple accounting transaction
 A mailing system should be included.
 Customer should be able to print out their transaction statement whenever they need.
 The system should be such that it can be regularly updated without the need of the
system developer.
 The system should provide for the secure, reliable and efficient database.
 The system must be able to run with or without the internet.
NON-FUNCTIONAL SPECIFICATION
 User friendly interface
 The system must be robust and secure enough from the unauthorized access and loss
of data.
 A common platform for all the data processing.
 The system should meet the standard of the organization.

WORK DISTRIBUTION
The system is developed by the combined effort of the team. The team consisting of three
members will put their best effort to make the system meet up its requirements. The tasks to
perform will be evenly distributed among three members with regular consultation and
discussions to drive the way towards the best decisions regarding the development of the
system. The work of the individually will be checked by the group as well and pass out the
suggestions if needed. This will help to make the system follow its specification and the
development process will keep its track. For the co-ordination of the team, a team leader is
selected from within the three members who will act as the coordinator for the whole process.
1) Team Member: Ram Kumar Bhandari
Student ID : 1801T3080068
Responsibilities:
Proposal:
 Proposal of the new system
 Initial new system requirements
 Gantt Chart
Analysis:
 Feasibility study
 Fact findings
o Interview with the co-operative customers/members
o Research including the use of internet.

 Description of current system
 Requirement modeling
 Requirement Specification
Design:
 Data Design
 Architectural Design
 Procedural Design
 Interface Design
Development and implementation:
 Software Development
 Software Testing
 Operational manual
 Implementation
2) Team Member: Sailesh Neupane
Responsibilities:
Proposal:
 Introduction
 Description of Current System
 Basic Problems and Limitations of current system.
Analysis:
 Introduction
 Fact findings
o Interview with the top-level management of the co-operative
o Observation.
 Problems and Limitation of current system
Design:
 Data Design
 Architecture Design
 User training
 Data conversion
3) Team Member: Bibek Bam
Responsibilities:
Proposal:
 Hardware and Software requirement for development

 System benefits
 Cost/Benefit study
Analysis:
 Feasibility study
 Fact findings
o Questionnaire preparation
o Survey (with staffs)
 Scope and constraints
Design:
 Data Design
 Architecture Design
 User training
 Data Conversion

BENEFITS OF THE NEW SYSTEM
The major benefit of the system is that it will overcome the drawbacks of the current system
and helps to perform the banking operations efficiently. The overall benefits of implementing
the new system are summarized as below:
 Information can be handled with greater ease and with better management.
 The system can be use in network so that the resources can be shared.
 The cost of purchasing the vendor based software is reduced.
 The need of greater human resource only for the data handling process is reduced.
 The information regarding the website can be provided to the public via the public
view of the website.
 The services can be provided to the customer, online from the system itself wherever
and whenever they wish.
 System can alert or send the messages to the customer through web mail.
 With the implementation of this system, the co-operative can inherit the evolution
trend of the banking system.
HARDWARE AND SOFTWARE SPECIFICATION
FOR DEVELOPMENT:
Minimum hardware requirement:
 Pentium III with 1.66 GHz processor
 512 Mb of RAM,
 14 inch color monitor.
Tools requirement:

Web Browser, Dreamweaver, Web Server (XAMPP recommended), Graphic

Design tool (Photoshop recommended)
Programming/Scripting Languages to be used:
PHP with MYSQL, HTML, CSS, JAVASCRIPT
FOR OPERATION OF SYSTEM:

Minimum Hardware Requirement:
 Pentium III with 1.66 GHz processor or higher,
 512 Mb of RAM or higher,
 14 inch color monitor.
Software Requirement:
 O/S: Microsoft Windows 98, NT ME, 2000, XP (service packs 1, 2, or, 3),
VISTA or Windows 7 also compatible with Linux and MAC OS X...
 Web Server: XAMPP(APACHE included)
 Browser: Minimum Microsoft Internet explorer 7 or higher, Opera 6.x, Firefox

or Netscape 6.x, with JavaScript 1.3.
Server Requirement:
 Web Server
 Database Server

COST/ BENEFIT ANALYSIS OF NEW SYSTEM
Cost Analysis
Initial cost
 System Development cost (including hardware and software cost) : Rs. 75,000
 Server (Qty 1) : Rs. 37,200
 Workstation (Qty 4) : Rs. 35000 * 4 = Rs. 1,40,000
 Multipurpose Machine (Printer, Fax, Photocopy) : Rs. 7,500
 Diesel Generator (Qty 1) : Rs. 55,125
 Other Network Peripherals (including cables and modems) : Rs. 6,000
Total Initial Cost = Rs. 3, 20,825
Operational Cost
 Electricity
Suppose a workstation consumes the electricity of Rs. 10 in a day.
So 6 workstation will consume, 6*10 = Rs. 60 per day
Similarly, assuming that multipurpose device consumes Rs. 15 in a day and the server
will also consumes Rs 15 in a day.
So, the total electricity consumption in a day is 10+60+15+15 = Rs. 100
Therefore the total electricity consumption per year is Rs. 100*30*12 = Rs. 36,000
 Fuel for Generator per year : Rs.20,000

 Web hosting and domain Registration : Rs. 20,000 (for one year)
 Maintenance : Rs. 15,000
Total Operational cost for one year: Rs. 91,000
Expected Benefits from the New System
Although there are no significant tangible benefits acquiring from this system, it provides
intangible benefits which helps in the long term establishment of the organization. For the
intangible benefits we can keep in view the efficiency of the system and its reliability which
in turns can assure the customer to increase their relationship with the organization and hence
enlarging the market. This will obviously be an undeniable benefit in term of the
organization.
Mathematical Analysis of Benefits
Due to the online transaction, the customer handling capacity of the staffs increases. So let‟s
say if in manual system, one staff should need minimum of 30 minutes for the transaction,
now in the online system he/she only needs 5 minutes for each customer. So the staff can
handle more number of customers at the same time interval. Beside that customer may be
attracted by the e-banking features.
Let us assume that from the online transaction of one customer, the organization gets the app.
benefit of Rs. 10.
Suppose in the very first year of implementation, 45 customers perform their transaction on
one day in average. So Rs. 450 is benefited in one day.
Similarly, in a year, Rs. 450 * 30 *12 = Rs.1, 62,000
(Note: It is not the actual annual profit of the overall organization. This benefit is only from the online
service)
Cost/Benefit Analysis Chart

PAYBACK PERIOD ANALYSIS TABLE:
YEAR COSTS CUMULATIVE CUMULATIVE

BENEFITS
COSTS BENEFITS
0 320825 320825 0 0
1 91000 411825 162000 162000
2 95000 506825 183000 345000
3 90000 596825 190000 535000
4 120000 716825 212500 747500
5 92000 808825 225700 973200
6 90000 898825 250000 1223200
The payback period is app. 3.8 years
RETURN ON INVESTMENT ANALYSIS:
Return on Investment (ROI) is calculated over the six years of system implementation.
Total Benefits = Rs.1223200

Total Costs = Rs.898825
ROI = (Total Benefits - Total Costs)/Total Costs * 100
= (1223200 – 898825) / 898825 * 100
= 36.088 %
GANTT CHART
The project is of 210 days that is 30 weeks.
The project will be started on 24th April 2010 and end on 19th November 2010 about 210
days.

Apr 2010 May 2010 Jun 2010 Jul 2010 Aug 2010 Sep 2010 Oct 2010 Nov 2010
ID Task Name Start Finish Duration
4/11 4/18 4/25 5/2 5/9 5/16 5/23 5/30 6/6 6/13 6/20 6/27 7/4 7/11 7/18 7/25 8/1 8/8 8/15 8/22 8/29 9/5 9/12 9/19 9/26 10/3 10/10 10/17 10/24 10/31 11/7 11/14 11/21
1 Preparation of Proposal 24/04/2010 07/05/2010 14d
2 Analyze phase starts: Fact Finding 07/05/2010 26/05/2010 20d
3 Refinement 26/05/2010 30/05/2010 5d
4 Modelling 31/05/2010 03/06/2010 4d
5 Specification draft( to user) 04/06/2010 07/06/2010 4d
6 Review 07/06/2010 10/06/2010 4d
7 Final Requirement Specification 11/06/2010 16/06/2010 6d
8 Design Phase starts: Data Design 18/06/2010 10/07/2010 23d
9 Architectural Design 04/07/2010 23/07/2010 20d
10 Interface Design 24/07/2010 05/08/2010 13d
11 Procedural Design 06/08/2010 20/08/2010 15d
12 System Design Document 21/08/2010 21/08/2010 1d
13 Development 23/08/2010 06/10/2010 45d
14 Testing: Unit Testing 06/10/2010 10/10/2010 5d
15 Testing: Integration Testing 11/10/2010 13/10/2010 3d
16 Testing: System Testing 14/10/2010 15/10/2010 2d
17 Hardware and Software Installation 17/10/2010 19/10/2010 3d
18 Preparation of Manuals 21/10/2010 24/10/2010 4d
19 Data conversion 25/10/2010 31/10/2010 7d
20 Release user guide and User training 02/11/2010 06/11/2010 5d
21 Implementation 07/11/2010 08/11/2010 2d
22 Review and maintenance 09/11/2010 18/11/2010 10d

ANALYSIS

INTRODUCTIVE DESCRIPTION
The objective of building the new system is to manage the daily transaction of the customers
in an online manner and at the same time it must also provide the information about the co-
operative to the executives, stake holder, staffs, customer and the other visitors.
The initial study showed us that the online web application is the most feasible system that
can be implemented to fulfill our objective. Now the task is to find out more about the
requirements and the problem that the system must have a solution to. The system is mean to
be shared by all the respective responsive employees and the executives at the same time. It
must act as a common platform for sharing the resources of the co-operative. The problems of
the conventional file handling system must be eliminated or at least minimized to its lowest
level by the use of a reliable and consistent database system.
It is necessary for us to determine the scope and constraints of the new system. For this
getting the pertinent facts is inevitable to get a better view of the problem recognition. The
perception of the end system user and its owner plays the vital role in the better system
development and its usage after the implementation. If the perception and the desire of the
system user cannot be distinguished clearly in this phase of system development then there
will be doubt in the proper implementation and usage of the system. The system will become
rather useless than to solve the problems of the users.
Nobody can deny the power of the analysis tools. This section focuses on the problem
recognition by the use of different popular fact findings methodologies and their analytical
verification to determine how they can be incorporated in the system. The end of this phase
provides us the base framework in developing the accurate, efficient, consistent and reliable
system.

FACT FINDINGS
As the first step in the analysis phase, following fact findings techniques are espoused in
order to get the requirements for the new system.
 Interview/Meeting
 Questionnaire/Survey
 Observation
 Research
INTERVIEW
Interview is one of the most common methodologies for the fact findings. From interview we
can get the individual perceptions about a system. We believe in the fact that the interest of
an individual can have the direct relation with the growth of the organization and its
prosperity. For this reason, we conducted following interviews at the given time with
personnel from different aspects of area.
Interview with Co-operative top-level management:
Interview Objectives:
 To find the basic requirements of new system.
 To know new features that the different personnnel of the office want to include in
new system.
 To take the suggestion for developing the system as per their need..
1) Person Interviewed: Sunita Dhakal(Bhattarai)
Post: Chairman
Interview Date: 20/01/2010
Interview Time: 10 am

Interview Location: In her office
Interview Questions and Answers with Mrs. Sunita Dhakal(Bhattarai):
 What problems are you facing with current system?
 The main problem with current system is time and cost.

 What are the possible ways to eliminate the problem that are faced in current
system?
 Implementation of new online system that can resolve the current problem.
 Will the proposed new system solve the problems?
 Yes.
 What extra features should new system posses?
 The new system should provide the feature of online account query,cash transfer for
customer through their account number as well .
 Do you see any advantage and disadvange on implementing new system?
 On implemetation of this system not only time and cost can be minimized but I think
it would even make our system systematic and scientific which is flexible.
 I don‟t see any disadvantage till now.
Requirements gathered from Interview with Mrs. Sunita Dhakal(Bhattarai):
 Web based system .
 Should minimize the overall time and cost.
 Should be able to handle database.
 Should be able to act as website for the front user.
 Should have feature of account query and cash tansfer for the customer.

2) Person Intervied: Sachin Bhattarai
Post: Managing Director
Interview Date: 23/03/2010
Interview Time: 11am
Interview Location: In his own office
Interview Questions and Answers From Mr. Sachin Bhattarai:
 What problems are you facing with current system?
 Obviously it is taking more time since a transaction should be filed in paper first and
then stored in the computer.This has resulted in the cost as well since extra manpower
for handling the tramsaction.
 What are the possible ways to eliminate the problem that are faced in current
system?
 The database should be maintained directly by a person.
 Will the proposed new system solve the problems?
 Yes.
 What extra features should new system posses?
 Online account query for the customer.
 Do you see any advantage and disadvange on implementing new system?
 Less manpower is used.

 Not yet.
Requirements gathered from Interview with Mr. Sachin Bhattarai:
 System should take less time and cost.
 Can be run be less number of manpower.

 Should have online account query feature for the customer
Interview with Co-operative Customers:
Interview Objectives:
 To gather requirements for the new system from the customer‟s point of view.
 To know the problem background.
 To get the customer‟s perception about the new system procedure.
1) Interviewed Person: Dr. Salik Ram Burathoki
Profession: Lecturer (Trichandra College)
Date: 27/01/2010
Time: 1 PM
Location: Co-operative Office
Interview Question and Answers with Mr. Salik Ram Burathoki
 How long are you related with the Co-operative?

 From the starting time of the Co-Operative, near about 2 years.
 What do you want to say about the services provided by the Co-operative?
 Well, in the short time it has tried to provide its best, but that‟s enough.
 What are the problems that you are facing right now?
 The main problem that I am facing (and may others are facing it too) is of time
management. It takes a lot of time to do your transaction here. The staffs are not being
able to handle the customers.
 Will the online system be helpful to solve your problems?
 I am hopeful.
 What features do you think the online system must include?
 Umm, it would be better if we customer could get our account information from our
own site so that we could save our time coming out to the Co-operative itself.
 Is there anything you think that shouldn’t be included in online system?
 No, there‟s no such thing that should be excluded from going to online.

Requirement gathered from the Interview with Mr. Salik Ram Burathoki
 Online System for the Co-operative
 Should be efficient enough
 Customer should be able to access their account, electronically.
2) Interviewed person: Mr. Buddhi Ratna Bajracharya

Profession: Businessman
Date: 27/01/2010
Time: 1:30 PM
Location: Co-Operative Office
Interview Questions and Answers with Mr. Buddhi Ratna Bajracharya
 How long are you related with the Co-operative?

 It‟s about 1 and 1/2 years.
 What do you want to say about the services provided by the Co-operative?
 It‟s better than other places I have worked with, but there are many areas to improve.
 Like? Can you give some of the examples?
 Yes, for example customers has to wait for long time even to finish their very minor
jobs, the information desk is always full and one has to wait for their turn to get a
piece of information they need.
 Would these problems be solved if there was an online system?
 Definitely, in fact people would not be forced to wait for hours to get a piece of
information.
 What other features do you think the online system must include?
 I think the online system should feature the informative website for the general public
so that they don‟t need to come over the Office for the information.
 Is there anything in particular that you think the online system should not
feature?
 I don‟t think there is any.

Requirement gathered from the interview with Mr. Buddhi Ratna Bajracharya.
 Online System for the Co-operative
 Should be efficient
 The online system must include an informative site.
3) Interviewed person : Mrs. Shova Tamang

Profession: Counselor (Hi- tech Abroad Study)
Date: 29/01/2010
Time: 11 am
Location: Co-Operative Office
Interview Questions and Answers with Mrs. Shova Tamang
 How long have you been in touch with the co-operatives service?
 It‟s not more the 6 months that I have been utilizing the services of the co-operative.
 How did you know about it?
 One of my cousin is the customer from the starting days of this co-operative. She told
me about its services and I found it convincing.
 What do you feel about the services?
 I‟ve found it convincing and as a co-operative point‟s of view it‟s really nice to see
the services profound.
 Is there anything that you might want to change, add about the services and the
way it is provided?
 Services… , It‟s Ok and I m sure the management team will come up with new
strategy. And about the way, it would be better if the co-operative used the full
computerized system. That would make it easy for we customer and for them as well.
 How do you think an internet based system would help the customers?
 In many ways… in many ways. The major benefit that I think is of time. If member
could do simple account statement query from their site it would for them.
 Is there anything you want to add at last?
 It would be beneficial for us if the System goes to online. So I hope you will make it
your best.

Requirement gathered from the interview with Mrs. Shova Tamang

 Online System
 Customers view for statement enquiry.
QUESTIONNAIRE AND SURVEY
To find the common interest of a mass of people is very much important in the corporative
world. In fact it is not a piece of cake to determine the common interest from a big mass of
people. But with the use of methodologies like Questionnaire and Survey, it is not a big
deal.
Here is the report of Questionnaire and Survey conducted.
Participants
Co-operative Staffs: 15
Customers: 25
Total Number of Participants : 40
a. Are you satisfied with the old system?
Yes
No
Partially

b. Do you think the current system is flexible and systematic?
Yes
No
c. What are the problems you are facing with the current system?
Time and cost
Difficulty in management
Both

d. What measures can be taken to solve the existing problem?
Changes in current system
Online networking system
Stand alone system
e. Do you think the proposed system will eradicate the faced problem?
Yes
No
Partially

f. Should customers be given an online account space?
Yes
No
g. Should account query feature via account number be included in new system?
Yes
No

h. Should amount transfer feature be introduced in new system or not?
Yes
No
i. Should account E-mail feature be included or not?
Yes
No

j. Are there sufficient customers as per the hypothesis done?
Fair
More
Less
k. Should employee information be included in online system?
Yes
No

Requirement Gathered from the Questionnaire and Survey
As we had expected, the questionnaire distribution and the survey program was
successful and help us to gather the requirement of the new system and the end users and
beneficiary‟s perception and suggestion about our proposal for the new system. This has
helped us to be more precise about the problems that the new system must solve and the
opportunities/features that it must include.
So the facts that were summarized from the questionnaire and the survey are listed as
follows.
 The end users are not satisfied by the service provided by the new system.
 The new system must minimize the cost.
 It must be able to provide the best service in minimal of time.
 It must manage the transaction in effective way.
 The new system should be online and work in network.
 Customer should be given an account space through which they can utilize the
system features.
 The amount transfer system between the accounts in the co-operative must be
included.
 The notification and messaging system should be included.
 Staff‟s information should also be included within the online system.

OBSERVATIONS
On February 1st 2010 our analyst team went to the Co-operative office for the live
observation to know how the actual processing is done. The team spent couple of hours
observing and getting the information about the working of the staff personnel and the way
keeping the records of the customer. It was very much essential for our team to gain the
maximum knowledge of the current system as we were converting the current system into the
new online networking system with the added features keeping in view the problem
backgrounds and the future expansion of the organization.
Here are the requirements which should be included in the new system that we concluded
from our observation at the co-operative office.
 A separate account for each staff.

 Staffs that perform the direct transaction with the customers should be given authority
to create an account for a customer.
 Customers account can only be deleted by the Finance Manager only.
 The staffs account can be created, deleted and given the allowance by the Human
Resource Manager only.
 Customer through their account id (or a username) should be able to access their
current status.
 The new system should provide for the mailing system so that the co-operative can
send information to the customer when needed.

RESEARCH
In the recent years Internet has been the hugest source of the information. Anyone can get the
information about almost anything in the world by the use of the internet. So we choose the
Internet as a methodology for research with the objectives of gathering the requirement for
the new system. We surf through some of the sites of domestic and international Co-operative
sites and gather the following requirements.
Requirement gathered from the research through internet:
 The concept of e-banking is what the today‟s customer demand. So the new system
must incorporate the concept of e-banking in some way or other.
 An informative site for the visitors is must that gives the information about the co-
operative and the service provided by it.
 Besides the information the visitors must be able to send the query if they have any.
FINAL REQUIREMENTS FROM THE FACT- FINDINGS
FUNCTIONAL REQUIREMENTS
 Should include an informative site for the visitors.

 Visitors should be able to send feedback and query to the system.
 Each customer is given an individual account (space) for handling their e-banking
features.
 The data must be safely stored in the database.
 The information should be able to extract accurately in simple manner.
 Should have account query feature via account number.
 Must have online amount transfer feature.
 Should have mailing system for sending the news and latest information of the Co-
operative and Customer.
 A separate account for each staff.

 Staffs that perform the direct transaction with the customers should be given authority
to create an account for a customer.
 Customers account can only be deleted by the Finance Manager only.
 The staffs account can be created, deleted and given the allowance by the Human
Resource Manager only.
 Customer through their account id should be able to access their current status.
 Should have the option for recording the staff attendance.
 The logs of the users should be maintained.
 Should be able to perform simple bookkeeping transaction.
 A pop-up calendar should be included to make the users easy to view the date.
 The working area of the users should be set according to the privilege given.
NON-FUNCTIONAL REQUIREMENTS
 Should be flexible enough to save time and manual effort.

 Utilization of different techniques for the security and integrity of the database.
 The user interface must maintain the degree of consistency.
 The system contents must be simple enough to avoid the ambiguity and complex
enough to include the required information.
 It should be able to work under the critical conditions.
 It should be easy to update.
 In the case of error and exception, trouble shooting must be easier.

DESCRIPTION OF THE CURRENT SYSTEM
As mentioned regularly, the current is based on the manual file based record keeping system.
All the daily transaction is operated manually. The data are stored in a computer in the
applications such as MS-ASCESS which is not suitable for the organization such as Co-
operative which has to keep data of thousands of customers. The data are collected
throughout the day and entered to the computer at the end of the day.
When a customer wants to open an account on the co-operative, he has to go to the co-
operative office and fill up a form requesting for the open of a new account. Then he has to
stand in a line to submit the form. After that he has to wait till his form his processed which is
so boredom for the customer and consumes lot of time. Then one of the staff makes entry of
his number into the register file. Next staff input the data to put it into the file system. When
the customer asks for the information about his account, it is difficult for staff to provide it
immediately.
The same procedure is applied in the amount withdraw and deposit process and also the loan
requesting process which has been the loathsome process for the customer and the staff as
well.

ORGANIZATIONAL STRUCTURE
Board of Directors Chairman

Sunita Dhakal(Bhattarai)
Managing
Director
Sachin Bhattarai
Operational
Manager
Rahul Bhattarai
Human Resource Marketing

Finance Manager Miscellaneous
Manager Manager
Arun Adhikari Deepa Baral
Parmeswor Dahal Sumitra Kafle
Loan Manager Cash Manager Ward no.9 Ward no.34 Ward no 32

Pukar K.C. Sabina Dahal Sumi Khadka Ram Dahal Ramesh Thapa
Counter 1 Counter 2 Counter 3

Binisha Timsina Sailendra Duwadi Rina Bastola
Organization Chart
ROLES AND RESPONSIBILITIES WITHIN THE ORGANIZATION
Board of Directors
Board of Directors includes the primary stake holders of the Co-operative. As they have
invested the large sum of money in the co-operative, they are very much interested in the well
being of the organization. They do not have direct involvement in the daily transaction
though they may issue the directives to the company‟s business rule.

Chairman
One of the members from the Board of Directors is elected as the chairman of the co-
operative who invokes the decisions made by the Board of Directors and make sure that the
organization is progressing. He may ask for the report from the managing level officers time
to time. He may be responsible for making up the long term plan decisions.
Managing Director
Managing Director is the top most employee of the Co-operative. He is not one of the
members of the Board of Directors. He is the director of the managers i.e. directs other
members and manages the plan for achieving the goals of the Co-operative. He may ask
reports from the lower level managers and submit his reports to the higher level executives.
He inspects the working of all the departments.
Managers
Managers are the higher level employees to use this system frequently. Each manager handles
his own department. There are 5 departments namely:
 Operational Department – Handles the overall internal transaction of the Co-operative
 Finance Department – Handles loan and deposit section
 Human Resource Department – Handles the man power of the Co-operative.
 Marketing Department – Handles the marketing and promotion of the Co-operative
 Miscellaneous Department – Handles the system working and performance.
The managers make use of the system for performing the following jobs:
Operational Manager
 Control and co-ordinates the overall operations of the co-operative.
 Keep track of the services of the co-operative.
 Make sure that the employees are performing their jobs well

Finance Manager
 Co-ordinates the financial matters of the co-operative.
 Provide suggestion and advice on the financial matters to the upper level employees.
 Checks the account's status.
 Inspects the loan request and issue or reject the request.
Human Resource Manager
 Control and check the human resource of the co-operative.
 Recruit new employee to the co-operative.
 Remove an employee.
Marketing Manager
 Mobilize the employee to different area sector as marketing representatives.
 Build up the marketing schemes for the organization.
Miscellaneous Manager
 Check the system performance.
 Maintenance of the system.
 Make sure of the availability of the materials required to run the system.
 Computer operator.

INPUT/OUTPUT SPECIFICATION OF THE CURRENT SYSTEM
The current input and output of the process in system are shown in tabular form below.
Process No 01
Process Name Account opening process
Description Opening of the account for the saving and withdraw process.
Input Data Customer Information
Output Data Account Number
Process No 02
Process Name Money Deposit Process
Description Deposit the money in the account of the customer
Input Data Amount of money along with the account information
Output Data Deposit Voucher
Process No 03
Process Name Money Withdraw Process
Description Withdraw money from the account
Input Data Cheque Data
Output Data Withdrawn Money

Process No 04
Process Name Loan Request Process
Description Request a loan by customer to co-operative
Input Data Request Data including the customer information and the loan
information
Output Data Receipt to the customer.
Process No 05
Process Name Loan Inspection Process
Description Inspection of the loan request submitted by the customer.
Input Data Request form filled up by the customer.
Output Data Acceptance Notice or Rejection Notice to the customer.
Process No 06
Process Name Visitor's query manipulation process
Description Respond to the queries of the visitors at co-operative
Input Data Visitor's queries
Output Data Queries' responsive information.
Process Name 07

Process Name Account's Statement Generation Process
Description Generate the statement of the customer account
Input Data Account Number
Output Data Account's statement
Process Name 08
Process Name Customer Black listing Process
Description Put the customer's name in black list if he/she hasn't pay the loan in
required amount of time.
Input Data Loan Information along with the customer's information.
Output Data Selected Customer's Name

PROCESS FLOW DIAGRAM (DATA FLOW DIAGRAM)
The following data flow diagrams attempt to show the current system of processing the data
with the help of the input data and output data along with the processes
Context Diagram:
The context diagram shows the basic generalized form of the data flows with all the process
merged into one general system.
Visitors
Ask queries/
Response to
Feedback
the queries/feedback
Request for information Apply for Loan

Provides the information Issue/reject Loan
Current Banking Customer (Loan)
Customer ( deposit ) Apply for account open
System
Provide the A/C No.
Context Diagram

Level 1 Diagram
The level 1 diagram show the data floe between the process in lower level of abstraction i.e.
in more detail form. It alos includes the Data store in the system which was not included in
the context diagram.
Visitors
Queries Answer
Updated A/C
Customer A/C Information
Queries about
reception Transaction The services Customer (loan)
process Process
Respond to
queries
process
Provides
the Information Accept/reject Apply for
Loan Loan
A/C Services Information
Information
Customer (with saving Loan

Acccount) Loan Information acception/
Central Data Store rejection
Loan data process
File System
Apply for A/C Request for

Issue A/C no proposal study
Open
Proposal study
report
Customer Data
A/C opening Loan proposal
process Account Information study process
Level 1 DFD
(current system)

PROBLEMS AND LIMITATION OF THE SYSTEM
As discussed in the proposal section of this document, the one major problem of the system is
its inability to address and use the modern technologies. Here we will elaborate those
problems and limitation in detail as per our study from the fact finding techniques.
 Problems in Information Processing and Management
Data are the facts of an entity and Information are the processed data which has some
useful meaning about an entity. These two are the basic building blocks of an
organization. The ability of an organization to handle data and information depicts its
successfulness in the corporate world.
At present, the co-operative is facing the problem of handling and processing the data
and information as per their need. There is lack of the system which can handle and
process the data and information of the organization properly and in an efficient way.
The present system of manipulating the data with the use of cheap and unreliable
software such as MS-Access cannot properly handle huge amount of data.
 Time consumption is out of control
Most of the system operation is carried out by the manual basis. Huge amount of time
is consumed in the process involving the direct human power. When a customer wants
to open an account, he has to fill up an form which is later on inspects on and validate
by the staff before issuing an account number. This is one area where the time
consumption is must. The other area is when a customer demands his account
statement. It is difficult to generate a report in short period of time without the aid of
an efficient electronic system. Paper based system is always prone to the
unmanageable time consumption with compared to the automated system.
 Lack of proper warehouse of the Data with adequate back up system.
The co-operative is completely relying upon the small software for the purpose of
storing data. These small softwares do not provide the facilities required to manage
the data in an arranged manner. So the Data manipulation task is always stressful in

such software. Neither can these software support the sharing the data in the network.
There is no proper back up system in the co-operative. All the important data are
stored in a single computer and there is no networking between the workstation. If the
hard disk of the computer crashed by chances, then there is no way of retrieving the
data. Hence there is the always the risk of losing the data.
 Inability to use the Internet as the medium to flow information
The modern world is based on the one home concept by the use of the modern
technology concept. Internet is one of such technology which has make it easier to all
the people to get access to anything in any part of the world. It is the major source of
information. Most of the people seek their information need from the internet. The
modern corporate is totally based on it and they also performing well in their
business.
In such a facility of widening the information domain of an organization, the co-

operative is not being able to utilize it to their points. Visitors have to come to co-
operative office and collect a brochure or interrogate some staffs if they are interested
to know about the services provided by the co-operative. On the other hand, the staffs
who are very limited in number may not be able to respond to all the interrogation
made by the visitors.
 Higher Operation cost
The cost of operating the current system is higher in comparison to the output
provided by the system.

SCOPE AND CONSTRAINTS
The scope of this system is defined by the eminent requirement of the system which help us
to be focused on our objectives. There are the areas in the system which should be included in
the new system and the other areas are not necessary at the present context. The main areas to
undergo the change are the customer records manipulation process, account records
manipulation process, account transaction process including the amount transfer features
within the accounts of the co-operative, customer's self retrieval of the account statement.
The system need not include the staff's pay slip system. Only the staff's record is preferable to
keep track of the transaction. The process of information flow to the visitors must be included
to the system externally.
Constraints
The available budgets of the co-operative restrict the system features to be limited. The co-
operative policy also has some role for system to act within the certain boundary.
Some of the present/mandatory constraints and the future/optional constraints are listed
below.
Present/Mandatory constraints:
 be able to manipulate the customer data online.
 be able to credit and debit the account automatically with maximum degree of
accuracy.
 be able to produce the account statements on demands between any time of a year.
 be able to update the news and events, notice, schemes on the website.
 be able to create an account user for the customer.
 be able to send and receive messages between the various users.
 be able to send email notification to the customers.

 be able to receive, save and reply the queries from various users.
 be able to divide the responsibilities among the staff users.
Future / Optional Constraints
 may be able to produce the pay slip for each employee.
 may feature the amount transfer features with different financial sectors i.e. others
banking sectors.
 may be able to send the SMS notification services to the customers along with the
email notification.
 may incorporate the further e-banking features.

REQUIREMENTS SPECIFICATION
MODULE 1: "SYSTEM ADMINISTRATION MODULE"
i. Able to create new employee record and save it in the database.
ii. Able to update the employee records.
iii. Able to view all the employee records.
iv. Able to delete the employee records.
v. Able to search the employee records.
vi. Able to assign the functions to the employee as per their role in the organization.
vii. Able to de-assign the system responsibilities of the system users i.e. employees.
viii. Able to generate the predefined reports.
ix. Able to generate different reports or manipulate database using the SQL query.
x. Able to update the co-operative website as per required using CMS.
xi. Able to send messages to the staffs.
xii. Able to send the response message to the customers/vistotors.
MODULE 2: "EMPLOYEE PANEL MODULE"
The functions that the employees can use are based on their roles and responsibilities in the
organization. Following are the generalized form of the functions for employees.
i. Able to view all the employee records.
ii. Able to search the employee records.
iii. Able to create and save new customer records.
iv. Able to view all customer records.
v. Able to update customer records.
vi. Able to delete customer records.

vii. Able to create and save new account records.
viii. Able to view all account records.
ix. Able to update accounts records.
x. Able to delete account records.
xi. Able to fill the loan data form and save it.
xii. Able to view the loan information.
xiii. Able to update the loan information.
xiv. Able to delete the loan information.
xv. Able to send message to other staffs.
xvi. Able to send messages to the customers.
MODULE 3: "CUSTOMER PANEL MODULE"
i. Able to view owns profile.
ii. Able to view the updated statement of own.
iii. Able to transfer the amount between the accounts the co-operative. [Only can
transfer to other's account but not from the others account]
iv. Able to send the feedbacks, message.
MODULE 4: "GENERAL VISITOR MODULE" (WEBSITE)
i. Able to view the information about the co-operative and it'sservices.
ii. Able to send queries.
iii. Able to send feedback.

DESIGN

DESCRIPTION OF THE NEW SYSTEM
“Pictures can describe an event that even thousand sentences are unable to describe”. It is true
that a picture is easy to understand and more than that, it helps us to eliminate the ambiguity
of the sentences. For example the sentence “A fish is ready to eat” has a dual meaning. The
first meaning is that a fish in the event of eating another fish. The second meaning might be a
well cooked is ready to be eaten. But when a picture is shown where a fish is put on a plate,
then everyone can understand that the cooked fish is ready to be eaten. Hence modeling is an
important tool to eliminate the ambiguity.
During the analysis modeling of a system, we can have two types of modeling.
 Functional Modeling
 Behavioral Modeling
FUNCTIONAL MODELING
DATA FLOW DIAGRAM
Data Flow Diagram (DFD) represents the logical model and depicts what the system does. It
does not show how the data transformation is carried out by the system. It helps us to design
the system in the way that will try to cover the requirements of the system.
To clearly identify the system requirement we modeled Data Flow Diagram according to the
requirements gathered from the fact findings programs. From the fact findings we find that
the end users of the system can be basically divided into four different categories.
 Employees of the Co-operative,
 Customer having a saving account,.
 Customer taking loan from the Co-operative, and
 Visitors seeking information
Context Diagram

The context diagram depicts the general flow of data between the end users (entities) and the
system as whole. Here the individual processes are not distinctly shown. The data flow
between the processes and the entities will be shown in next level diagram. The context level
diagram also do not show the data store of the system which will also be shown in next level
DFD.
Amount Transfer Request Data to request loan
Request for statement

Customer Withdraw/Deposit Money Customer
(Account Holder) (Loan)
Provide Statement
Provide Statement
Perform Amount Transfer Issue/reject loan
Sundar CMS
Output Information System Provide response
Input Data Ask queries/ feedback

Employee Visitors
Context Diagram
Level 1 Diagram

Withdraw/deposit Loan request

Withdraw/deposit Data to request
form forms
money Money loan
Customer Withdraw/ Loan request Customer
Deposit process Notification
(Account Holder) Balance (Loan)
process
Request Amount Statement Statement
Cionfirmation Transfer Information Request
Provide Balance
Issue/Reject
Information
loan
Amount Transfer Form Statement Information
Amount Employee Statement

Confirmation Statement Request
transfer Query
process Processing
Processed Input Data
Information
Statement Statement
Information Request
Data store and

fetch process
Amount Transfer Form Store Data
Output
Confirmation
data
Central Data Store
Ask for Data Get Data
Query/
Feedback
Processing
Ask Queries/ Provide Response

Feedbacks
Visitors
Level 1 Diagram

DATA DICTIONARY
Data Elements:
Data Element Name : Staff Identification Number
Type : String [Alphanumeric]
Length : 5
Source : System
Data Element Name : Staff First Name
Type : String
Length : 15
Source : Staff Information Form
Data Element Name : Staff Middle Name
Type : String
Length : 15
Data Element Name : Staff Last Name
Type : String
Length : 15

Data Element Name : Staff Father Name
Type : String
Length : 25
Data Element Name : Staff Permanent Address
Type : String
Length :
Data Element Name : Staff Temporary Address
Type : String
Length :
Data Element Name : Staff Date of Birth
Type : Date
Length :
Source : Staff Registration Form
Data Element Name : Staff Citizenship
Type : String

Length : 20
Data Element Name : Staff Nationality
Type : String
Length : 20
Data Element Name : Staff Telephone
Type : Numbers
Length: 15
Source : Staff Informatin Form
Data Element Name : Staff Email
Type : String
Length: 25
Data Element Name : Staff Date of Join
Type : Date
Length:

Data Element Name : Department
Type : String
Length: 20
Data Element Name : Staff Post
Type : String
Length : 20
Data Element Name : Staff Type
Type : String
Length : 15
Data Element Name : Staff Username
Type : String
Length: 20
Source : Staff Addition Process
Data Element Name : Staff Password

Type : String
Length: 35
Source : Staff Adding Process
Data Element Name : Customer Name
Type : String
Length : 45
Source : Account Opening Form
Data Element Name : Customer Date of Birth
Type : Date
Length :
Data Element Name : Customer Occuption
Type : String
Length: 25
Data Element Name : Customer Gender
Type : String
Length: 6

Data Element Name : Customer Nationality
Type : String
Length : 50
Data Element Name : Customer GrandFather Name
Type : String
Length : 45
Data Element Name: Customer Father Name
Type : String
Length : 45
Data Element Name : Customer Husband/Wife Name
Type : String
Length : 45

Data Element Name : Customer Full Address
Type : String
Length : 50
Data Element Name : Nominee Person Name
Type : String
Length : 45
Source : Account Openin Form
Data Element name : Nominee Person Address
Type : String
Length : 50
Data Element Name : Nominee Phone
Type : String
Length : 15
Data Element Name : Nominee Relationship
Type : String

Length : 20
Data Element Name : Principle
Type : Floating point Number
Length:
Source : Account Opening Process
Data Element Name : Interest Rate
Type : Number
Length :
Data Element Name : Amount
Type : Floating point Numbers
Length :
Data Element Name : Account Number
Type : Number
Length :

Data Flows :
Data Flow Name : Withdrawal/Deposit Amount
Description : Withdrawing/deposting amount from/to an account
Origin : Customer (External Entity)
Destination : Amount withdraw/deposit Process (Process)
Data Flow Name : Statement
Description : Account Balance Information of an Customer
Origin : Amount Withdraw/Deposit Process (Process)
Destination : Customer (External Entity)
Data Flow Name : Withdraw/Deposit Information
Description : Details for withdrawing/deposting amount from/to an amount
Origin : Amount Withdraw/Deposit Process (Process)
Destination : Employee (External Entity)
Data Flow Name : Provide Statement Information
Description : Details of an Account Statement
Origin : Employee (Process)
Destination : Amount Withdraw/Deposit Process (Process)

Data Flow Name : Request Amount Transfer
Description : Details of Amount Transfer
Destination : Amount Transfer Process (Process)
Data Flow Name : Amount Transfer Form
Description : Details of Amount Transfer Request
Origin : Amount Transfer Process (Process)
Destination : Employee (External Entity) / Central Data Store (Data Store)
Data Flow Name : Confirmation Detail
Description : Details of Amount Transfer Transction
Origin : Employee (External Entity) / Central Data Store (Data Store)
Destination : Amount Transfer Process (Process)
Data Flow Name : Confirmation Message
Description : Details of Amount Transfer Transaction
Origin : Amount Transfer Process (Process)
Data Flow Name : Data to request Loan
Description : Detail data to request for loan

Destination : Loan request Process (Process)
Data Flow Name : Loan request Form
Description : Detail data for loan request
Origin : Loan request Process (Process)
Destination : Employee (External Entity)
Data Flow Name : Issue / Reject Loan
Description : Detail About the Acceptance or Rejection of Loan Request
Origin : Employee (External Entity)
Destination : Loan request Process (Process)
Data Flow Name : Notification
Description : Notification message to notify the customer about the acceptance or rejection of
the loan request.
Origin : Loan Request Process (Process)
Data Flow Name : Statement request
Description : Request for the account statement

Destination : Statement Query Process (Process)
Data Flow Name : Statement Request Processing
Description : Collect Require data for statement
Origin : Statement Query Process (Process)
Destination : Employee (External Entity)/ Central Data Store (Data Store)
Data Flow Name : Final Statement Information
Description : Generated Statement Infrmation
Origin : Central Data Store (Data Store) / Employee (External Entity)
Destination : Statement Query Process (Process)
Data Flow Name : Formatted Statement
Description : Statement report of an Account
Origin : Statement Query Process (Process)
Data Flow Name : Ask Queries/Feedback
Description : Queries and Feedbacks regarding the organisation
Origin : Visitors (External Entities)
Destination : Query/Feedback Processing (Process)

Data Flow Name : Ask for data
Description : fetch information regarding the concerned query or feedback
Origin : Query/Feedback Processing (Process)
Destination : Central Data Store (data store)
Data Flow Name : Get Data
Description: Data Received from database
Origin : Central Data Store (Data Store)
Destination : Query/Feedback Processing (Process)
Data Flow Name : Provide response
Description : Response for the queries and feedback
Origin : Query/Feedback Processing (Process)
Destination : Visitors (External Entity)
Data Flow Name : Input Data
Description : Commands to acces the database
Origin : Employee (External Entity)
Destination : Data Store and Fetch Process
Data Flow Name : Store Data
Description : Executes/ Store data in the data store

Origin : Data Store and Fetch Process (Process)
Destination : Central Data Store (Data Store)
Data Flow Name : Output Data
Description : The result set of Data From the database
Origin : Central Data Store (Data Store)
Destination : Data Store and Fetch Process (Process)
Data Flow Name : Processed Infomration
Description : Data Processed to meaningful Information
Origin : Data Store and Fetch Process (Process)
Destiantion : Employee (External Entity)
Data Store :
Data Store Name : Sundar
Description : Database used to store all the data used by the system
Input Data Flows : Statement Request Information, Store Data, Amount Transfer Form, Ask
For Data.
Output Data Flows : Statement Information, Output Data, Confirmation, Get Data
Process :
Process Name : Money Withdraw/Deposit Process

Purpose : To perform the appropriate transaction while depositing and withdrawing amount
from an account.
Input Data Flow : withdraw/deposit amount, provide statement information
Output Data Flow : withdraw/deposit form, balance information
Process Name : Amount Transfer Process
Purpose : To perform appropiate procedure while transformin amount from one account to
another account.
Input Data Flow : Request Amount Transfer, Confirmation
Output Data Flow : Confirmation, Amount transfer form
Process Name : Loan Request Process
Purpose : To perform approprite procedure while receiving the loan request
Input Data Flow : Data to request loan, Issue/reject loan
Output Data Flow : Loan request form, Notification
Process Name : Statement Query Processing
Purpose : To process the statement request by the customer
Input Data Flow : Statement Request, Statement Information
Output Data Flow : Statement Information, Statement Request
Process Name : Query/Feedback Processing
Purpose : To receive and respond the query and feedback from the visitors
Input Data Flow : Ask queries/feedback, Get data
Output Data Flow : Ask for data, Provide response
Process Name : Data Store and Fetch Process
Purpose : Act as intermediate process to perorm the task related with database
Input Data Flow : Input data, Output Data
Output Data Flow : Store Data, Processed Information
External Entities :
Entity Name : Customer(Account Holder)
Description : Customer of the organisation having a saving account
Input Data Flow : Statement , Confirmation
Output Data Flow : withdraw/deposit amount, request amount transfer
Entity Name : Customer (Loan)
Description : Customer of the organisation taking loan from it.
Input Data Flow : Statement Information, notification
Output Data Flow : Statement request, Data to request loan
Entity Name : Employee
Description : Active Employees of the organisation.

Input Data Flow : withdraw/deposit form, loan request form, statement request, amount
transfer form, processed information
Output Data Flow : Provide balance information, Issue/reject loan, Statement Information,
Input Data, Confirmation
Entity Name : Visitors
Description : Website visitors
Input Data Flow : Provide response
Output Data Flow : Ask Queries/Feedbacks
BEHAVIORAL MODELING
STATE TRANSITION DIAGRAM

Sundar Office System
Overall System State
False username or password

Invoke error message
Unauthenticate
Click on logout buton True username and passwod

Invoke session finished Invoke Main panel
User Authenticated

Staff panel
On click Staff link

Invoke staff panel
On click Add staff tab On click Report tabs

Invoke blank Staff Add form Invoke Reports
Staff panel Reading Command
On click View Record tab On click Attendance tab

Invoke all staff records Invoke Attendance Form
On click view button
Invoke detail record of a staff
Viewing
Adding Staff
Adding Staff Viewing Records Attendance
Attendance
Reports
On click Delete
On click X
Button
Invoke close privilege Box
On click Add Staff Button Invoke confirmation
Invoke appropriate message
On click Finish Button
On click done button Invoke Close privilege box On click logs Button
Invoke all staff Records Invoke logs box
On click Privilege Button
Invoke privilege box
Viewing single Setting up
Viewing logs
record detail On click Ok button privileges
Invoke Delete query
On click Edit link

Confirming
Invoke Edit Form On Click Edit/Cancel Button deletion of a
record On click next Button
Invoke database update
Invoke next priviege
On Click Cancel button

Editing part of
record Invoke all staff Record
Fig : State transition diagram for staff panel

Customer Panel
On click customer link

Invoke customer panel
On click Add customer tab

Invoke blank Customer Add form
Customer panel Reading
Command
On click View Record tab

Invoke all Customer records
On click view button
Invoke detail record of a
customer
Adding Customer Viewing Records
On click Delete
On click X
Button
Invoke close privilege Box
On click Add Customer Button Invoke confirmation
On click Finish Button
On click done button Invoke Close privilege box On click logs Button
Invoke all Customer Invoke logs box
Records On click Privilege Button
Invoke privilege box
Viewing single Setting up
Viewing logs
record detail On click Ok button privileges
Invoke Delete query
On click Edit link

Confirming
Invoke Edit Form On Click Edit/Cancel Button deletion of a
record On click next Button
Invoke database update
Invoke next priviege

Editing part of
Invoke all customer
record
Record
Fig : State transition diagram for Customer panel

Saving Panel
On click Saving link

Invoke Saving panel
On click New Account tab On click Report tabs

Invoke blank Saving Account form Invoke Reports
Saving panel Reading Command

Invoke all saving account
On click view button records
Invoke detail record of a customer
Creating New
Viewing Records Viewing Reports
Account
On click Delete
Button
On click X
On click Create Button Invoke confirmation
Invoke close statement Box
On click done button On click statement Button
Invoke all saving account Invoke statement box
Records
Viewing single
record detail On click Ok button
Invoke Delete query
On click Edit link

Confirming
Invoke Edit Form On Click Edit/Cancel Button Viewing statement
deletion of a
Invoke database update record

Editing part of
record Invoke all saving account
Record
Fig : State transition diagram for Saving panel

Loan Panel
On click Loan link

Invoke Loan panel
On click New Account tab On click Report tabs

Invoke blank Loan Account form Invoke Reports
Loan panel Reading Command

Invoke all Loan account
On click view button records
Invoke detail record of a customer
Creating New
Viewing Records Viewing Reports
Account
On click Delete
Button
On click X
On click Create Button Invoke confirmation
Invoke close statement Box
On click done button On click statement Button
Invoke all loan account Invoke statement box
Records
Viewing single
record detail On click Ok button
Invoke Delete query
On click Edit link

Confirming
Invoke Edit Form On Click Edit/Cancel Button Viewing statement
deletion of a
Invoke database update record

Editing part of
record Invoke all loan account
Record
Fig : State transition diagram for Loan panel

Transaction Panel
On click Transaction link

Invoke Transaction panel
Transaction panel Reading

Command
On Click loan repayment

On click withdraw Radio button radio button
Invoke Account checkiing Invoke submit Account No form
Asking For
Account No
On click deposit Radio

btn
Invoke Account
Checking
Checking the Checking the Checking the

validity of account validity of account validity of account
True Account no & PIN

True Account no True Account no
Invoke balance information
& withdraw form Invoke Deposit form Invoke Loan information
and pay form
Displaying Balance
Information & Prompting for Prompting for
prompting for amount amount
amount
On click withdraw On click Deposit Button On click Pay Button

Invoke submit PIN form Invoke submit Account No
Invoke submit Account No
form
form
Fig : State transition diagram for Transaction panel

Website
On click Website link

Invoke website panel
On click News & Events Tab

Invoke News and Events panel
Website panel reading command
On click Feedback On click Schemes

& query tab On click Career tab tab
Invoke FaQ panel Invoke Career panel Invoke Schemes tab
Feedback and
Career reading Schemes reading
query reading
News and Events command command
command
Reading command [like News & [like news &
[like News &
Events] events]
Events]
On click view records tab

On click Add tab Invoke all news record
Invoke add form
On click Delete Button

Invoke confirm message
Adding news & Viewing news &
events events
On click add tab

Invoke appropriate On click Edit
message Invoke edit form
Deleting record(s)
Editing the record

On click Done/Cancel
Invoke all news record
State Transition Diagram of Website Panel

DATA DESIGN
INTRODUCTION
Data design is one of the most important stages of the Design phase. It determines the use of
data and their management so that we can process them into the useful information. Since the
system use intensive amount of data, extreme care is to be taken while selecting them. The
ability to manage the data replicates the successfulness of the system.
DATABASE SYSTEM
Database with its greater number of advantages has been replacing the old system of file
keeping. The Sundar System also uses database to manage its data gracefully. Data are stored
in form of related tables. For maintaining the relationship between the tables, each table is
assigned with a primary key which also helps to identify each record.
Database Management System (DBMS) is database managing software which helps to

manage the multiple database and secure the databases. For Sundar System, MySQL DBMS
is used as it is open source DBMS and is suitable for middle sized organization. In future the
database can be easily shifted to any other database with only some minor changes.
DATA USED IN SYSTEM
The data used by the system can be categorized into two main categories.
1) Manually fed data
2) System generated data
1) Manually fed data
Manually fed data are those which are fed to the system by means of forms by the user.
These types of data need to be checked carefully before processing them.

Data fed from the staff registration form
a. First name, Middle name, Last name, Father‟s name
b. Permanent Address, Temporary Address
c. Date of Birth
d. Citizenship Number, Place of Issue, Nationality
e. Avatar (image)
f. Telephone No. Mobile No.
g. Email Id
h. Date of Join, Department, Post, Job type
i. Office timing
j. Username, Password
Data fed from the staff Attendance Form
a. Date
b. Incoming time
c. Outgoing Time
d. Remark
Data fed from the customer add form
a. Name
b. Date of Birth
c. Avatar (Image)
d. Occupation
e. Contact No

f. Mobile No
g. Email Address
h. Gender
i. Nationality
j. Grandfather‟s Name
k. Father‟s Name
l. Husband/Wife Name
m. Temporary Address, Permanent Address
n. Nominee‟s Person Name, Address, Phone No, Relation, Age
Data fed from the saving Account form
a. Account Holder‟s PIN
b. Account Name
c. Account type
d. Account Holder‟s Signature image
e. Entered By N
f. Approved By
g. Interest Rate
h. Principal Amount
i. Time
Data fed from the Loan Account form
a. Account Holder‟s PIN

b. Loan type
c. Applicant‟s Business Name
d. Address
e. Phone No
f. Requested Amount
g. Payback Time
h. Mortgage Item
i. Item‟s Name
j. Product‟s Name
k. Produced Year
l. Model No.
m. Issued loan amount
n. Service Charge
o. Installment charge
p. Interest rate
q. Approved By
Data fed from the withdraw, deposit and loan payment form
a. Amount
b. Payee
c. Cashier
Data fed from the add News and Events form
a. Heading

b. Body
c. Images
Data fed from the feedback and query form
a. Name
b. Email
c. Comments/ query
Data fed from the add career form
a. Post Title
b. Required no.
c. Qualification
d. Experience
e. Details
f. Last submission date
Data fed by Schemes Form
a. Schemes Type
b. Name
c. Rate
d. Details
Data fed by Notice Form
a. Heading
b. Details
Data fed by Message Form

a. Message Detail
2) System Generated Data
System generated data are those data that are generated by the system using the generic
logics or some predefined function.
Data generated in Staff adding Form
a. Staff Identification Number
Data generated in Customer Added Form
a. Customer PIN
b. Added Date
Data generated in Saving Account Form
a. Account Number
b. Date
Data generated in Loan Account Form
a. Account Number
b. Date
Data generated in withdraw, deposit and loan payment
a. Debit amount
b. Credit amount
c. Total balance
d. Available balance
Data generated in add News and Event Form
a. News id

b. Date
Data generated in add Feedback and Query form
a. Id
b. Date
c. Time
Data generated in career form
a. Id
b. Date
Data generated in schemes form
a. Id
Data generated in message form
a. ID
b. Date
c. Time

ENTITY RELATIONSHIP DIAGRAM [BEFORE NORMALIZATION]
Entity Relationship Diagram also known as ER Diagram is the another part of the functional
modeling which represents the relationship between the system entities in terms of modality
(Mandatory or Optional) and Cardinality (number of related occurrence with respect to the
existing entities). E.R. Diagram along with the help of Data Dictionary pave the way for the
building the Data Structure for the system.
Generalized Business rule
1. A staff can add one or more numbers of customers.

2. A staff can open one or more accounts.
3. A customer can only have one saving accounts.
4. Only customers having saving accounts active can apply for the loan.
5. Loan cannot be issued to same person twice at the same time.
Binary Relationship Between the entities
1. A staff can add one or more customers.
A customer must be added by only one staff.
Staff add Customer
2. A staff can open one or more accounts.
An account can be opened by only one staff.
Staff open Account
3. A customer can have only one saving account.

An account must belong to only one customer.
Customer Can have Account
4. A customer can be grant only one loan at a time.
A loan can be issued to only one customer.
Customer Can be granted Loan
5. A visitor can send many queries/feedbacks.
Queries/feedbacks must be sending by one or more visitors.
Queries/
Visitors send
Feedbacks
6. A staff may respond to one or more Queries/Feedbacks.
A query/Feedback must be responded by a staff.
Queries/
Staff respond
Feedbacks

NORMALIZATION
Normalization is a design technique to design a well managed relational database system. It

gives the necessary forms of the tables which holds the data removing the repeating groups.
UNF of the Sundar
Sundar (id, fullName, perAddress, tempAddress, landline, mobileNo, email, password, dob,
gender, avatar, citizenship, nationality, session_type, status, date_of_join, department, post,
type, officeTiming, cat_staff, cat_customer, cat_saving, cat_loan, cat_transaction,
cat_website, cat_reports, cat_settings, add_staffs, staff_responsibility, view_staff, edit_staff,
delete_staff, add_staff_attendance, attendance_reports, staff_logs, add_customer,
view_customer, edit_customer, delete_customer, customer_logs, customer_reports,
saving_create, saving_view, saving_edit, saving_delete, saving_statement, loan_create,
loan_view, loan_edit, loan_delete, loan_statement, occupation, fatherName,
grandFatherName, HusWife, nomineeName, nomineeAddress, nomineePhone,
nomineeRelation, nomineeDOB, addedDate, acc_statement, amt_transfer, chng_password,
view_summary, attend_date, attend_intime, attend_outtime, attend_remark, saving_acno,
saving_name, saving_type, saving_principal, saving_rate, saving_period, saving_enteredby,
saving_approvedby, saving_openeddate, saving_status, saving_signature,
saving_totalbalance, saving_availablebalance, savinglogs_date, savinglogs_description,
savinglogs_credit, savinglogs_debit, balance, loan_acno, loan_type, loan_bussname,
loan_bussadd, loan_ph_item, loan_ph_product, loan_ph_productyear, loan_ph_model,
loan_mortageitem, loan_requestedamount, loan_issuedamount, loan_paybacktime,
loan_installmentamount, loan_installment_time, loan_installmentperiod, loan_interestrate,
loan_approvedby, loan_approveddate, loan_paidamount, loan_status, loanlogs_date,
loan_acno, loanlogs_desc, loanlogs_credit, loanlogs_debit, loanlogs_balance, logs_id,
logs_date, logs_time, logs_desc, logs_concern, scheme_id, scheme_name, scheme_type,
scheme_rate, minimum_balance, scheme_detail, scheme_status, career_id, career_post,
career_qualification, career_experience, career_details, career_vacancyno,
career_submitdate, career_addeddate, career_status, comment_id, comment_name,
comment_email, comment_feedback, comment_date, comment_status, msg_id, msg_sender,
msg_receiver, msg_subject, msg_body, msg_time, msg_date, msg_status, news_id,
news_head, news_body, news_image, news_date, news_status)
1NF
Sundar(id, fullName, perAddress, tempAddress, landline, mobileNo, email, password, dob,

view_summary, attend_date, attend_intime, attend_outtime, attend_remark, saving_acno,
saving_name, saving_type, saving_principal, saving_rate, saving_period, saving_enteredby,
saving_approvedby, saving_openeddate, saving_status, saving_signature,
saving_totalbalance, saving_availablebalance, loan_acno, loan_type, loan_bussname,
loan_bussadd, loan_ph_item, loan_ph_product, loan_ph_productyear, loan_ph_model,
loan_mortageitem, loan_requestedamount, loan_issuedamount, loan_paybacktime,
loan_installmentamount, loan_installment_time, loan_installmentperiod, loan_interestrate,
loan_approvedby, loan_approveddate, loan_paidamount, loan_status, scheme_id,
scheme_name, scheme_type, scheme_rate, minimum_balance, scheme_detail, scheme_status,
career_id, career_post, career_qualification, career_experience, career_details,
career_vacancyno, career_submitdate, career_addeddate, career_status, comment_id,
comment_name, comment_email, comment_feedback, comment_date, comment_status,
msg_id, msg_sender, msg_receiver, msg_subject, msg_body, msg_time, msg_date,
msg_status, news_id, news_head, news_body, news_image, news_date, news_status)
Saving_logs(saving_acno, savinglogs_date, savinglogs_description, savinglogs_credit,

savinglogs_debit, balance)
Loan_logs()
Staff_attendance(id,attend_date, attend_intime, attend_outtime, attend_remark)
Logs(logs_id, logs_date, logs_time, logs_desc, logs_concern)

2NF
Sundar(id, fullName, perAddress, tempAddress, landline, mobileNo, email, password, dob,

view_summary)
Saving_account(saving_acno, saving_name, saving_type, saving_principal, saving_rate,

saving_period, saving_enteredby, saving_approvedby, saving_openeddate, saving_status,
saving_signature, saving_totalbalance, saving_availablebalance)
Loan_account(loan_acno, loan_type, loan_bussname, loan_bussadd, loan_ph_item,

loan_ph_product, loan_ph_productyear, loan_ph_model, loan_mortageitem,
loan_requestedamount, loan_issuedamount, loan_paybacktime, loan_installmentamount,
loan_installment_time, loan_installmentperiod, loan_interestrate, loan_approvedby,
loan_approveddate, loan_paidamount, loan_status)
Schemes(scheme_id, scheme_name, scheme_type, scheme_rate, minimum_balance,

scheme_detail, scheme_status)
Career(career_id, career_post, career_qualification, career_experience, career_details,

career_vacancyno, career_submitdate, career_addeddate, career_status)
Comments(comment_id, comment_name, comment_email, comment_feedback,

comment_date, comment_status)
Message(msg_id, msg_sender, msg_receiver, msg_subject, msg_body, msg_time, msg_date,

msg_status)

NewsEvents(news_id, news_head, news_body, news_image, news_date, news_status)

Loan_logs()
3NF
Personal_info(id, fullName, perAddress, tempAddress, landline, mobileNo, email, password,

dob, gender, avatar, citizenship, nationality, session_type, status)
Staff(id,date_of_join, department, post, type, officeTiming, cat_staff, cat_customer,

cat_saving, cat_loan, cat_transaction, cat_website, cat_reports, cat_settings, add_staffs,
staff_responsibility, view_staff, edit_staff, delete_staff, add_staff_attendance,
attendance_reports, staff_logs, add_customer, view_customer, edit_customer,
delete_customer, customer_logs, customer_reports, saving_create, saving_view, saving_edit,
saving_delete, saving_statement, loan_create, loan_view, loan_edit, loan_delete,
loan_statement)
Customer(id, occupation, fatherName, grandFatherName, HusWife, nomineeName,

nomineeAddress, nomineePhone, nomineeRelation, nomineeDOB, addedDate,
acc_statement, amt_transfer, chng_password, view_summary)
Saving_account(saving_acno, saving_name, saving_type, saving_principal, saving_rate,

saving_period, saving_enteredby, saving_approvedby, saving_openeddate, saving_status,
saving_signature, saving_totalbalance, saving_availablebalance)
Loan_account(loan_acno, loan_type, loan_bussname, loan_bussadd, loan_ph_item,

loan_ph_product, loan_ph_productyear, loan_ph_model, loan_mortageitem,
loan_issuedamount, loan_totalamount, loan_paybacktime, loan_installmentamount,

loan_installment_time, loan_installmentperiod, loan_interestrate, loan_approvedby,

loan_approveddate, loan_paidamount, loan_status)
Schemes(scheme_id, scheme_name, scheme_type, scheme_rate, minimum_balance,

scheme_detail, scheme_status)
Career(career_id, career_post, career_qualification, career_experience, career_details,

career_vacancyno, career_submitdate, career_addeddate, career_status)
Comments(comment_id, comment_name, comment_email, comment_feedback,

comment_date, comment_status)
Message(msg_id, msg_sender, msg_receiver, msg_subject, msg_body, msg_time, msg_date,

msg_status)
NewsEvents(news_id, news_head, news_body, news_image, news_date, news_status)

Loan_logs()

ENTITY RELATIONSHIP DIAGRAM (AFTER NORMALIZATION)
Staff Logs
PK STAFF_ID PK LOGS_ID
STAFF_FIRST_NAME LOGS_DATE
STAFF_MIDDLE_NAME Message FK1 LOGS_CONCERN
STAFF_LAST_NAME LOGS_DESCRIPTION
STAFF_PER_ADD PK MSG_ID LOGS_TIME
STAFF_TEMP-ADD
STAFF_DOB FK1 MSG_SENDER
STAFF_CITIZENSHIP FK2 MSG_RECEIVER
STAFF_NATIONALITY MSG_SUBJECT
STAFF_PLACEOF_ISSUE MSG_BODY Customer
STAFF_AVATAR MSG_TIME
STAFF_TEL MSG_DATE PK CUST_PIN
STAFF_MOB MSG_STATUS
STAFF_EMAILID CUST_NAME
STAFF_DOJ CUST_DOB
STAFF_DEPARTMENT CUST_AVATAR
STAFF_POST CUST_PHONE
Saving_Account
STAFF_TYPE CUST_MOB
STAFF_INTIME PK SAVING_ACNO CUST_EMAIL
STAFF_OUTTIME CUST_OCCUPATION
STAFF_STATUS SAVING_NAME CUST_GENDER
USERNAME SAVING_TYPE CUST_NATIONALITY
PASSWORD SAVING_SIGNATURE CUST_GRANDFATHER
SESSION_TYPE SAVING_PRINCIPAL CUST_FATHER
RES_CAT_STAFF SAVING_RATE CUST_HUSWIFE
RES_CAT_CUSTOMER SAVING_TIME CUST_TEMPADDRESS
RES_CAT_SAVING FK2 SAVING_ENTEREDBY CUST_PERADDRESS
RES_CAT_LOAN SAVING_APPROVEDBY CUST_NOMINEE
RES_CAT_TRANSACTION SAVING_STATUS CUST_NOM_ADDRESS
RES_CAT_WEBSITE SAVING_OPENEDDATE CUST_NOMINEE_PHONE
RES_CAT_REPORTS SAVING_TOTALBALANCE CUST_NOMINEE_RELATION
RES_CAT_SETTINGS SAVING_AVAILABLEBALANCE CUST_NOMINEE_AGE
RES_ADD_STAFF FK1 CUST_PIN CUST_ADDED_DATE
RES_STAFF_RESPOSIBILITY CUST_STATUS
RES_VIEW_STAFF
RES_EDIT_STAFF
RES_DELETE_STAFF Saving_Logs
RES_ADD_STAFF_ATTENDANCE
RES_ATTENDANCE_REPORTS PK SAVINGLOGS_DATE
RES_STAFF_LOGS PK,FK1 SAVING_ACNO
RES_ADD_CUSTOMER
RES_VIEW_CUSTOMER SAVINGLOGS_DESCRIPTION
RES_EDIT_CUSTOMER SAVINGLOGS_DEBIT
RES_DELETE_CUSTOMER SAVINGLOGS_CREDIT
RES_CUSTOMER_PRIVILEGE
RES_CUSTOMER_LOGS
RES_SAVING_CREATE
RES_SAVING_VIEW Loan_Account
RES_SAVING_EDIT
RES_SAVING_DELETE PK LOAN_ACNO
RES_SAVING_STATEMENT
RES_LOAN_CREATE LOAN_TYPE
RES_LOAN_VIEW LOAN_BUSSNAME
RES_LOAN_EDIT LOAN_BUSSADD
RES_LOAN_DELETE LOAN_REQUESTEDAMOUNT
RES_LOAN_STATEMENT LOAN_PAYBACKTIME
RES_DEPOSIT LOAN_MORTGAGEITEM
RES_WITHDRAW LOAN_PH_ITEM
RES_LOANPAYMENT LOAN_PH_PRODUCT
LOAN_PH_PRODUCTYEAR Loan_Logs
LOAN_PH_MODEL
LOAN_ISSUED_AMOUNT PK LOANLOGS_DATE
LOAN_SERVICECHARGE PK,FK1 LOAN_ACNO
staff_attendance LOAN_INSTALLMENTAMT
LOAN_INSTALLMENT_TIME
PK ATTEND_DATE LOAN_INTEREST_RATE LOANLOGS_DESCRIPTION
PK,FK1 STAFF_ID FK1 LOAN_APPROVEDBY LOANLOGS_AMOUNT
LOAN_APPROVEDDATE
ATTEND_INTIME LOAN_STATUS
ATTEND_OUTTIME LOAN_PAID_AMOUNT
ATTEND_REMARK FK2 CUST_PIN

Career
PK CAREER_ID Apply
CAREER_POST PK APPLY_ID
CAREER_QUALIFICATION
CAREER_EXPERIENCE APPLY_NAME
CAREER_DETAILS APPLY_ADDRESS
CAREER_DATE APPLY_EMAIL
CAREER_VACANCYNO APPLY_CV
CAREER_SUBMITDATE FK1 CAREER_ID
CAREER_STATUS
Comment Scheme Notice News
PK COMMENT_ID PK SCHEME_ID PK NOTICE_ID PK NEWS_ID
COMMENT_NAME SCHEME_NAME NOTICE_HEADING NEWS_HEAD

COMMENT_EMAIL SCHEME_TYPE NOTICE_DETAILS NEWS_BODY
COMMENT_FEEDBACK SCHEME_RATE NOTICE_STATUS NEWS_IMAGE
COMMENT_DATE SCHEME_DETAIL NEWS_DATE
COMMENT_STATUS SCHEME_STATUS NEWS_STATUS

CONVERTING ENTITIES INTO RELATIONS (TABLES)
Table Name: personal_info
Foreign Primary Not

Column Name Data Type Default
Key Key Null
ID Varchar(15) - -
 
FULLNAME Varchar(50) - - -

PERADDRESS Varchar(20) - - -


TEMPADDRESS Varchar(50) - - -


LANDLINE Integer - - -


MOBILENO Integer - - -


EMAIL Varchar(30) - - -


PASSWORD Varchar(120) - - -


DOB Date - - -


GENDER Varchar(6) - - -


AVATAR Varchar(50) - - -


CITIZENSHIP Varchar(15) - - -


NATIONALITY Varchar(20) - - -


SESSION_TYPE Varchar(15) - - -


STATUS Int (1) 1 -

 

Table Name : staff
Foreign Primary Not

Key Key Null
ID Varchar(15) - -
 
DATE_JOIN_NAME Date - - -

DEPARTMENT Varchar(20) - - -


POST Varchar(30) - - -


TYPE Varchar(25) - - -


OFFICETIMING Varchar(30) - - -


CAT_STAFF Int(1) 0 - - 



CAT_CUSTOMER Int(1) 0 - -


CAT_SAVING Int(1) 0 - -


CAT_LOAN Int(1) 0 - -


CAT_TRANSACTION Int(1) 0 - -


CAT_WEBISTE Int(1) 0 - -


CAT_REPORTS Int(1) 0 - -


CAT_SETTINGS Int(1) 0 - -


ADD_STAFF Int(1) 0 - -


STAFF_RESPONSOBILITY Int(1) 0 - -


VIEW_STAFF Int(1) 0 - -


EDIT_STAFF Int(1) 0 - -



DELETE_STAFF Int(1) 0 - -


ADD_STAFF-ATTENDANCE Int(1) 0 - -


ATTENDANCE_REPORTS Int(1) 0 - -


STAFF_LOGS Int(1) 0 - -


ADD_CUSTOMER Int(1) 0 - -


VIEW_CUSTOMER Int(1) 0 - -


EDIT_CUSTOMER Int(1) 0 - -


DELETE_CUSTOMER Int(1) 0 - -


CUSTOMER_LOGS Int(1) 0 - -


CUSTOMER_REPORTS Int(1) 0 - -


STAFF_LOGS Int(1) 0 - -


ADD_CUSTOMER Int(1) 0 - -


VIEW_CUSTOMER Int(1) 0 - -


EDIT_CUSTOMER Int(1) 0 - -


DELETE_CUSTOMER Int(1) 0 - -


CUSTOMER_LOGS Int(1) 0 - -


CUSTOMER_REPORTS Int(1) 0 - -


SAVING_CREATE Int(1) 0 - -


SAVING_VIEW Int(1) 0 - -


SAVING_EDIT Int(1) 0 - -


SAVING_DELETE Int(1) 0 - -



SAVING_STATEMENT Int(1) 0 - -


LOAN_CREATE Int(1) 0 - -


LOAN_VIEW Int(1) 0 - -


LOAN_EDIT Int(1) 0 - -


LOAN_DELETE Int(1) 0 - -


LOAN_STATEMENT Int(1) 0 - -


Table Name : Customer
Foreign Primary Not

Key Key Null
ID Varchar(15) - -
 
OCCUPATION Varchar(20) - - -

FATHERNAME Varchar(50) - - -


GRANDFATHERNAME Varchar(50) - - -


HUSWIFE Varchar(50) - - -

NOMINEENAME Varchar(50) - - -

NOMINEEADDRESS Varchar(50) - - -


NOMINEEPHONE Varchar(15) - - -

NOMINEERELATION Varchar(15) - - -

NOMINEEDOB Int (1) - - -



ADDEDDATE Date - - -



ACC_STATEMENT Int(1) 0 - -


AMT_TRANSFER Int(1) 0 - -


CHNG_PASSWORD Int(1) 0 - -


VIEW_SUMMARY Int(1) 0 - -


Table Name: Saving_Account
Foreign Primary Not

Key Key Null
SAVING_ACNO Varchar(15) - -
 
SAVING_NAME Varchar(20) - - -

SAVING_TYPE Varchar(20) - - -


SAVING_SIGNATURE Varchar(50) - - -


SAVING_PRINCIPAL Double 0.00 - -



SAVING_RATE Double 0.00 - -



SAVING_TIME Double - - -


SAVING_ENTEREDBY Varchar(15) - - -


SAVING_APPROVEDBY Varchar(15) - -
 

SAVING_STATUS Int (1) - - -



SAVING_OPENEDDATE Date - - -


SAVING_TOTALBALANCE Double - - -


SAVING_AVAILABLEBALANCE Double - - -



CUST_PIN Varchar(15) - -
 

SAVING_INTERESTDAY Date -
 
Table Name: Loan_Account
Foreign Primary Not

Key Key Null
LOAN_ACNO Varchar(15) - -
 
LOAN_TYPE Varchar(20) - - -

LOAN_BUSSNAME Varchar(20) - - -


LOAN_BUSSADD Varchar(50) - - -


LOAN_ISSUEDAMOUNT Double 0.00 - -



LOAN_PAYBACKTIME Time - - -


LOAN_MORTGAGEITEM Varchar(40) - - -


LOAN_PH_ITEM Varchar(20) - - -


LOAN_PH_PRODUCT Varchar(20) - - -


LOAN_PH_PRODUCTYEAR Varchar(4) - - -


LOAN_PH_MODEL Varchar(15) - - -


LOAN_INSTALLMENTAMT Double 0.00 - -



LOAN_INSTALLMENT_TIME Double 0.00 - -



LOAN_INTEREST_RATE Double 0.00 - -



LOAN_APPROVEDBY Varchar(15) - -
 


LOAN_APPROVEDDATE Date - - -


LOAN_STATUS Int (1) - - -



LOAN_PAID_AMOUNT Double 0.00 - -



CUST_PIN Varchar(15) - -
 

Table Name: Saving_Logs
Foreign Primary Not

Key Key Null
SAVINGLOGS_DATE Date - -
 
SAVING_ACNO Varchar(15) - -
 
SAVINGLOGS_DESCRIPTION Text - - -


SAVINGLOGS_DEBIT Double 0.00 - -



SAVINGLOGS_CREDIT Double 0.00 - -



BALANCE Double - - -

Table Name: Loan_Logs
Foreign Primary Not

Key Key Null
LOANLOGS_DATE Date - -
 
LOAN_ACNO Varchar(15) - -
 
LOANLOGS_CREDIT Double 0.00 - -




LOANLOGS_DEBIT Double 0.00 - -



Table Name: Staff _Attendance
Foreign Primary Not

Key Key Null
ATTEND_DATE Date - -
 
STAFF_ID Varchar(15) -
  
ATTEND_INTIME Time - - -


ATTEND_OUTTIME Double 0.00 - -



ATTEND_REMARK Text - - -


Table Name: Logs
Foreign Primary Not

Key Key Null
LOGS_ID Date - -
 
LOGS_DATE Date - - -

LOGS_CONCERN Varchar(15) - -
 

LOGS_DESCRIPTION Text - - -

LOGS_TIME Time - - - 



Table Name: Message
Foreign Primary Not

Key Key Null
MSG_ID Int(10) - -
 
MSG_SENDER Varchar(15) - -
 
MSG_RECEIVER Varchar(15) - -
 

MSG_SUBJECT Text - - -


MSG_BODY Text - - -


MSG_TIME Time - - -


MSG_DATE Time - - - 


MSG_STATUS Int(1) - - -


Table Name: News
Foreign Primary Not

Key Key Null
NEWS_ID Int(10) - -
 
NEWS_HEAD Text - - -

NEWS_BODY Text - - -


NEWS_IMAGE Text - - -


NEWS_DATE Date - - -


NEWS_STATUS Int(1) - - -



Table Name: Comments
Foreign Primary Not

Key Key Null
COMMENT_ID Int(10) - -
 
COMMENT_NAME Varchar(40) - - -

COMMENT_EMAIL Varchar(20) - - -


COMMENT_FEEDBACK Text - - -


COMMENT_DATE Date - - -


COMMENT_STATUS Int(1) - - -


Table Name: Career
Foreign Primary Not

Key Key Null
CAREER_ID Int(10) - -
 
CAREER_POST Varchar(25) - - -

CAREER_QUALIFICATION Text - - -


CAREER_EXPERIENCE Text - - -


CAREER_DETAILS Text - - -


CAREER_DATE Date - - -


CAREER_VACANCYNO Int(3) - - - 


CAREER_SUBMITDATE Date - - -



CAREER_STATUS Int(1) - - -

Table Name: Schemes
Foreign Primary Not

Key Key Null
SCHEME_ID Int(10) - -
 
SCHEME_NAME Varchar(25) - - -

SCHEME_TYPE Varchar(20) - - -


SCHEME_RATE Double 0.00 - -



SCHEME_DETAIL Text - - -


SCHEME_STATUS Int(10) - - -



RELATIONSHIP DESCRIPTION BETWEEN THE ENTITIES (RELATIONS)
Staff and Staff_Attendance
Parent Table : Staff Child Table : Staff_Attendance
Modality: Mandatory Mandatory
Cardinality: One to many Many to One
One instance of Staff is related Many instances of

Relationship: with one or more instances of Staff_Attendance is related to
Staff_Attendance one instance of Staff.
Insert Rules: - Dependent
Delete Rules: Cascade -
Staff and Saving_Account
Parent Table : Staff Child Table : Saving_Account
Modality: Mandatory Optional
One instance of Staff maybe Many instances of

Relationship: related with one or more Saving_Account is related to
instances of Saving_Account one instance of Staff.
Delete Rules: Nullify -

Staff and Loan_Account
Parent Table : Staff Child Table : Loan_Account
One instance of Staff maybe Many instances of

Relationship: related with one or more Loan_Account is related to one
instances of Loan_Account instance of Staff.
Delete Rules: Nullify -
Staff and Logs
Parent Table : Staff Child Table : Logs
Modality: Optional Optional
One instance of Staff maybe

Relationship: Many instances of Logs may be
related with one or more
related to one instance of Staff.
instances of Logs
Staff and Message
Parent Table : Staff Child Table : Message

One instance of Staff maybe Many instances of Message

Relationship: related with one or more may be related to one instance
instances of Message of Staff.
Customer and Saving_Account
Parent Table : Customer Child Table : Saving_Account
One instance of Customer Many instances of

Relationship: maybe related with one or more Saving_Account may be related
instances of Saving_Account to one instance of Customer.
Delete Rules: Restrict -
Customer and Loan_Account
Parent Table : Customer Child Table : Loan_Account
One instance of Customer Many instances of

Relationship: maybe related with one or more Loan_Account may be related
instances of Loan_Account to one instance of Customer.
Delete Rules: Restrict -

Customer and Logs
Parent Table : Customer Child Table : Logs
Modality: Optional Optional
One instance of Customer Many instances of Logs may be

Relationship: maybe related with one or more related to one instance of
instances of Logs Customer.
Customer and Message
Parent Table : Customer Child Table : message
One instance of Customer Many instances of Message

Relationship: maybe related with one or more may be related to one instance
instances of Message of Customer.
Saving_Account and Saving_Logs
Parent Table : Saving_Account Child Table : Saving_Logs

One instance of
Many instances of Saving_Logs
Relationship: Saving_Account may be
may be related to one instance
related with one or more
of Saving_Account.
instances of Saving_Logs
Loan_Account and Loan_Logs
Parent Table : Loan_Account Child Table : Loan_Logs
One instance of Loan_Account Many instances of Loan_Logs

Relationship: may be related with one or more may be related to one instance
instances of Loan_Logs of Loan_Account.

ARCHITECTURAL DESIGN
INTRODUCTION
Architectural Design refers to the frame design of the system. It talks on the modular level of
the system, partitioning the whole system into chunks of small programs. The sundar system
can be divided into four main modules as follows:
1. Administrative module
2. Employee module
3. Customer module
4. General Visitors module
ARCHITECTURAL MODULES
ADMINISTRATIVE MODULE
The administrative module is the main control panel of the system. One can handle the whole
system operations from this module. This module contains the following sub- modules.
Staff Panel
 Add Staffs
 View Staff‟s Records
 Edit Staff’s Records
 Delete Staff‟s Records
 Set up Staff Privileges
 View logs of the Staff
 Add Staff Attendance
 View Staff‟s Attendance Reports

Customer Panel
 Add Customers
 View Customer‟s Records
 Edit Customer‟s Records
 Delete Customer‟s Records
 Set up Customer‟s Privileges
 View Customer‟s logs
Saving Panel
 Create Saving Account
 View Saving Account‟s Information
 Edit Saving Account‟s Information
 Delete Saving Account
 View Account‟s Statements
Loan Panel
 Create Loan Account
 View Saving Account‟s Information
 Edit Saving Account‟s Information
 Delete Saving Account
 View Account‟s Statements
Transaction Panel
 Perform withdraw transaction
 Perform deposit transaction
 Perform loan payment transaction

Website Panel
 Add news and events, notice, career, schemes
 View news and events, notice, career, schemes
 Edit news and events, notice, career, schemes
 Delete news and events, notice, career, schemes
 View feedback and queries and respond accordingly
EMPLOYEE MODULE
Employee panel is the subset of the Administrative Panel. Each Employee has his/her own
sub modules depending on the privileges given by the administrator. If the staff is assign as
administrator, he does have the access to administrative module.
CUSTOMER MODULE
Customer Panel can be accessed via the internet by the customer of Co-operative. It requires
the PIN (Personal Identification Number) to get access to the online account.
Customers can
 View their profile
 View the account statement
 Send message, get message
 Perform fund transfer
GENERAL VISITORS WEBSITE

The system also provides the website as the source of information for the general visitors.
The website is accessed from the internet and maintained by the administrative or employee
modules. It contains the parts like
 about us, giving information about the organization, board of directors, team, location
etc.
 schemes, giving information about the saving schemes and loan schemes

 Ebanking features for customers (Account Holder)
 News and Events, giving information about the recent news and events of the
company
 Career to give the information about the available vacancies.
 Feedback and Query form for visitors to submit feedback or queries.

PROGRAM STRUCTURE
ADMINISTRATIVE MODULE
Staff Panel
Admin Panel
Program Start Program Body Program End
1, 2 14
Check Staff privilege
If C1
Staff Interface
-
While C3
While C2
* Attendance*
Add Staff List Staffs Attendance
reports
3,4 5 13
11,12
List Details Edit Record Delete Record Privileges
6 7,8 9 10
Functions List Condition list

1. Declare Library files for use C1: staff privilege == 1
2. Declare data variables C2 not end of file staff records
3. Show Staff Add Form C3 not end of file attendance reports
4. Save Staff Record
5. Get all staff’s Records
6. Get a particular staff detail
7. Show Edit Form
8. Save updated Record
9. Delete Record
10. Set Up privileges
11. Show Attendance Form
12. Save Attendance
13. Get all Attendance report
14. Close the files
Fig : Program Structure : Staff Sub- Module

Customer Panel
Admin Panel
1, 2 11
Check Customer
privilege
If C1
Customer
Interface -
While C2
*
Add Customer List Customer
3,4 5
List Details Edit Record Delete Record privileges
6 7,8 9 10
Functions List
Condition list
1. Declare Library files for use
C1 : customer privilege == 1
2. Declare data variables
C2 not end of file customer records
3. Show Customer Add Form
4. Save Customer Record
5. Get all customer’s Records
6. Get a particular customer detail
7. Show Edit Form
9. Delete Record
10. Set up privileges
11. Close library files
Fig : Program Structure : Customer Sub- Module

Saving Panel
Admin Panel
1, 2 11
Check Saving privilege
If C1
Saving Interface
-
While C2
Create *
List Accounts Statement
Account
3,4 5
10
List Details Edit Record Delete Record
6 7,8 9
Functions List
1. Declare Library files for use Condition list
2. Declare data variables C1: saving privilege == 1
3. Show Saving Account Open C2 not end of file saving account records
Form
4. Save Account Information
5. Get all Account Information
6. Get a particular Account detail
7. Show Edit Form
9. Delete Record
10. Get Accounts Statement
Fig : Program Structure : Saving Sub- Module

Loan Panel
Admin Panel
1, 2 11
Check Loan privilege
If C1
Loan Interface
-
While C2
Create *
List Accounts Reports
Account
3,4 5
10
List Details Edit Record Delete Record
6 7,8 9
Functions List
Condition list
1. Declare Library files for use
C1: loan Privilege == 1
C2 not end of file loan account records
3. Show Loan Account Open Form
4. Save Account Information
5. Get all Account Information
6. Get a particular Account detail
7. Show Edit Form
9. Delete Record
10. Get Accounts Reports
Fig : Program Structure :Loan Sub- Module

Transaction Panel
Admin Panel
1, 2 11
Check Transaction
privilege
If C1
Transaction
Interface -
Withdraw Deposit
Loan Payment
Authenticate
3 7, 8,9 7,8,10
If C2
Withdraw Error Message
4, 5, 6

1. Declare Library files for use C1: transaction privilege == 1
2. Declare data variables C2 : account number is true
3. Ask For Ac No. and PIN
4. Get total balance and available
balance
5. Prompt for amount and check
6. Update the balance
7.Prompt for Ac No
8. Prompt for amount
9. Update balance
10. Get loan info
Fig : Program Structure Transaction Sub- Module

Website Panel
Admin Panel
1, 2 9
Check Website privilege
If C1
Website Interface
-
News & Events Feedback and Career Schemes

Query
3, 4, 5, 6 4,6,7 3, 4, 5, 6,
3, 4, 5, 6
Applies
4, 6, 8

1. Declare Library files for use C1 is Website privilige == 1
3. Add Record
4. View Records
5. Edit Records
6. Delete Records
7.Respond Query
8. Email the Applicants
Fig : Program Structure Website Sub- Module

EMPLOYEE MODULE
The program structure of Employee is like that of Administrative module but the features
depends upon the privileges provided.
CUSTOMER MODULE
Website Panel
1, 2 9
Check Id and Password
3
If C1
Ebanking Login form
View Profile View Statement Transfer Fund
4 5 6, 7, 8

1. Declare Library files for use C1: customer id and password is true
3. Ask For Ac No. and PIN
4. Get customer’s Profile
5. Get customer’s Account
Information
6.Prompt for Ac No
7. Prompt for amount
8. Update balance
Fig : Program Structure Customer Module

PROCEDURAL DESIGN
The procedural design transforms the structural design of the system into the procedural
description. There are several ways to represents the procedural details. Some programmers
may use English like phrases, some may use graphical notations or some others may use the
tabular design notation. In our case we use Graphical Design Notation i.e. Program flows to
transform the structural modules into procedural description.
Overall System Flow
Start
Username
and
password
Check
Authentication
Is Username and No
password valid?
Yes
Click a link
Yes
Is link equal to
Staff Panel
staff?
No
A B

A
B
Yes
Is link equal to
Customer Panel
Customer?
No
Yes
Is link equal to
Savingr Panel
Saving?
No
Is link equal to
Loan Panel
Loan? Yes
No
Is link equal to Yes

Transaction Panel
Transaction?
Is link equal to
Website Panel
website
Is link equal to
Reports panel
reports
Is equal to logout
Stop

Stop
Staff panel
Click action
tab
Yes Add staff

Is action equal to
information Save to database
addstaff?
form
No
Is action equal to Yes Show

Get records
view staff? records
No
Yes Update
Is action equal to
Staff Save to database
edit satff?
Information
No
Is action equal to Yes Get privilege

Save to database
privilege? form
No
Is action equal to Yes

Get records
logs
No
Get add
attendance Save to database
attendance
form
No

Get records
attendance reports
No
Stop

Customer Panel
Stop
Customer panel
Click action
tab
Yes Add customer

Is action equal to
add customer?
form
No

Get records
view customer? records
No
Yes Update
Is action equal to
customer Save to database
edit customer?
Information
No

Save to database
privilege? form
No

Get records
logs
No
Stop

Saving Panel
Stop
Saving panel
Click action
tab
Yes Add account

Is action equal to
create account?
form
No

Get records
view account? records
No
Yes Update
Is action equal to
account Save to database
edit account?
Information
No

Save to database
statement? form
No
Stop

Loan Panel
Stop
Loan panel
Click action
tab
Yes Add account

Is action equal to
create account?
form
No

Get records
view account? records
No
Yes Update
Is action equal to
account Save to database
edit account?
Information
No

Save to database
statement? form
No
Stop

Transaction Panel
Stop
Transaction panel
Click action
tab
Prompt
Is action equal to Yes Account
Save to database
withdraw? Number,
amount
No
Is action equal to Yes Prompt Ac Save to

deposit? number, amount database
No
Yes Prompt Ac
Is action equal to
number, Save to database
loan payment?
amount
No
Stop

Website
start
Get action
Yes
Is action equal to News & Events
News & Event? panel
No
Yes
Is action equal to
FaQ Panel
FaQ?
No

Career Panel
career?
No

Transaction Panel
?
No
Is link equal to Yes

Website Panel
website
No
No
Is equal to logout
Yes
Stop

INTERFACE DESIGN
Administrative/Staff Module
Welcome Screen
Link
Application Banner
Text Icon Icon Icon Icon
Link 1
Link 2
Link 3
Link 4
Welcome text
Link 5
Link 6
Text

Staff/customer Addition form
Link
Application Banner
Link 1 Tab 1 Tab 2 Tab 3 Tab 4

Link 2 Heading Text
Link 3
Prompt Input Text Box
Link 4 Text
Prompt Text Radio Radio
Link 5 Button Button
Text
Link 6 Prompt Input Text Box
Text
Prompt Text Input Text Box
Text
Prompt Text File Browser Text Box Button

Text
Text
Text
Text
Prompt Text Drop Down list
Button Button
Text
Button Button
Text

Staff record view page
Link
Application Banner
Link 2 Header Text
Link 3 Prompt Input Text Box Button

Text
Link 4
Button
Link 5 Column Column
heading heading
Link 6
Data Data
Button Button Button
Data Data
Text

Staff view Record => Details
Link
Application Banner
Link 2 Header Text

Text
Link 4
Edit Link Image
Link 5
Link 6
Personal Data
Edit Link
Edit Link
Contact Data
Edit Link
Official Data
Button
Text

Staff view Record => Privileges
Link
Application Banner
Title Text X

Info Text
Link 2 Header Text
Link 3 Text
Prompt Input Text Box Button
Text
Text
Link 4 Text
Button
heading heading
Link 6 Button Button
Data Data
Data Data
Text

Staff view Records => logs
Link
Application Banner
Title Text X
TextText Icon Icon Icon Icon
Link 1Column Header

Tab 1 Column Header Tab 3Column Header
Tab 2 Tab 4
Link 2Data Data

Header Text Data
Link 3Data Prompt Data Input Text Box Data Button

Text
Link 4
< < 123Button
> >>
Link 5< Column Column
heading heading
Link 6
Data Data
Data Data
Text

Staff Attendance Form
Link
Application Banner
Link 1
Tab 1 Tab 2 Tab 3 Tab 4
Link 2
Header Text
Link 4 Text
Text
Text
Link 6 Text Text
Prompt Text
Prompt Text Text area
Button Button
Text

Staff Attendance report
Link
Application Banner
Link 1
Tab 1 Tab 2 Tab 3 Tab 4
Link 2
Header Text
Link 3
Text
Link 5
Text
Link 6
Column Column Column Column
header header header header
Data Data Data Data
Data Data Data Data
Text

Customers View Records
Link
Application Banner
Link 1 Tab 1 Tab 2 Tab 3
Link 2 Header Text

Text
Link 4 Prompt Text Button
Link 5
Button
heading heading
Data Data
Data Data
< < 123 > >>

<
Text

Customer view records =>Details [Same as Staff view records=>Details]

Customer view records=>Privileges [Same as Staff view records=>Privileges]
Customer view records=>Logs [Same as Staff view records=>Logs]
Saving =>Create Account
Link
Application Banner
Link 1 Tab 1 Tab 2
Link 2
Header Text
Link 3
Link 4
Text
Link 5
Link 6 Text
Prompt Text Text
Text
Prompt Text Radio Radio Radio
Prompt Text Button
Radio Button
Radio Button
Radio
Text
Text
Text
Prompt Text Button Button Button
File Browser Text Box Button
Button Button
Text

Saving=> Account Actions
Link
Application Banner
Link 1 Tab 1 Tab 2
Link 2
Header Text
Link 3
Link 4 Text
Prompt Text Button
Link 5
Link 6
Column Column
Header Header
Data Data
Button Button
Data Data
Button Button
< < 123 > >>

<
Text

Loan => Create Account
Link
Application Banner
Link 1 Tab 1 Tab 2
Link 2
Header Text
Link 3
Link 4
Text
Link 5
Link 6 Text
Prompt Text Text
Text
Prompt Text Button
Text area Button

Text
Text
Text
Prompt Button
Input Text Box Button Button
Text
Text
Button Button
Text

Loan => Account Actions [Same as Saving Account Actions]
Transactions [withdraw and deposit]
Link
Application Banner
Link 1 Tab 1
Link 2
Text
Link 4 Radio Radio Radio
Link 5
Link 6 Prompt Input Text Box Button Button

Text
Text

Transactions [loan repayment]
Link
Application Banner
Link 1 Tab 1
Link 2
Text
Link 4 Radio Radio Radio
Link 5
Link 6 Prompt Input Text Box Button Button

Text
Text Text
Text

Website
News and events=> add news and events
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Link 5
Text
Link 6 Prompt Text Rich Text area
Prompt Text File Browser Text Box Button Link
Button Button
Text

News and Events=> View News and Events
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Prompt Text Button
Link 5
Link 6 Button
Column Column Column Column Header

Header Header Header
Data Data
Button Button
Data Data
Button Button
< < 123 > >>

<
Text

Website =>feedback and query
Link
Application Banner
Link 2 Header Text
Link 3 Prompt Text Button
Link 4 Button
Link 5 Column Column Header Column Column

Header Header Header
Link 6
Data Data Data
Button
Data Data Data
Button
< < 123 > >>

<
Text

Website =>Career=>Add Career
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Link 5
Text
Link 6
Text
Text
Text
Text
Prompt Text Rich Text area
Button Button
Text

Website => Career=> View Career [Same as Website=>News and Events=>view News and
Events]
Website =>Schemes=>add schemes
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Link 5
Text
Link 6
Button Button
Text
Text
Prompt Text Rich Text area
Button Button
Text

Website =>Schemes=>View Schemes [Same as Website=>News and Events=>View News and

Events]
Messages
Inbox/Outbox
Link
Application Banner
Link 2 Header Text
Link 3 Prompt Text Drop Down list Button
Link 4 SELECT ALL

Message Detail Area
Link 5 Data
Link 6 Data
Data
Data
Data
Data
Data
< < 123 > >>

<
Text

New Messages
Link
Application Banner
Link 2 Header Text
Link 3 Prompt Text Drop Down list

Text
Text
Link 6 Prompt Text
Text Area
Button Button
Text

User Settings
Link
Application Banner
Title Text X
Text Text Icon Icon Icon Icon

Link 1 Text Tab 1 Tab 2 Tab 3
Link 2 Text Header Text
Link 3 Text Prompt Text Drop Down list
Button
Text
Text
Link 6 Prompt Text
Text Area
Button Button
Text

HARDWARE AND SOFTWARE SELECTION
Development Hardware and Software Equipment:
For the development of the system, following hardware equipment are recommended for the
smooth development of the system.
1. A Personal computer
A Personal computer is required for the coding, storing and testing of the system. It is
the main hardware where the developer codes. The following minimum configuration
is required for the PC.
HARDWARE MINIMUM CONFIGURATION
Processer: Intel(R) Pentium(R)4 2.20GHz
Ram: 1 GB 333 MHz
Hard Disk 120 GB
2. An UPS (Uninterruptible Power Supply)
An UPS with minimum half an hour back up is needed to prevent from the data loss
since the electricity cut is more frequent at present.
Software Required:
1. Operating System:
Windows XP (SP2)
2. Web Server:
Apache
Web Server is required to host the system as the system is a server based system.
3. DBMS (Database Management System)
MySQL
DBMS is required in order to manage the database for the system. MySQL is most
common for the small and medium scale system.
4. Code Editor

Macromedia Dreamweaver
The code Editor is needed to write and edit the code. It makes the coding easier than
other plain text editor like notepad or wordpad.
5. Graphical designing software
Adobe Photoshop CS2 or higher and Sothink SWF easy Animation creator
Graphical designing software is required to design and create the graphics such as
buttons, backgrounds and layouts. Animation creator software is required to create
flash banners.
6. Web Browser
Mozilla Firefox
The system runs on the browser. Mozilla Firefox is recommended because it supports
the CSS3(stylesheet) and most of the JavaScript used in the system.
Implementation Hardware and Software Requirement
For the implementation of the system a separate server is needed which needs to be highly advanced.
Server is the heart of the system. So if the server is down then the whole system becomes unusable.
Hardware Requirement for the server:
1. A server
A server is needed to host the system to the end users. Since it has to host the system to the
several of the end users, it has to be powerful. The following minimum configuration is
needed to the server.
Processer Intel(R) CORE(R)i5 M430 @ 2.27GHz
Ram 4 GB DDR3 800MHz
Hard Disk 1 TB
2. An UPS (Uninterruptible Power Supply)
An UPS with minimum ten hour back up is needed to keep the server running which
is most important for the efficient outcome of the system.

Hardware Requirement For the End Users
1. A Personal computer
A Personal computer is required for connecting to the server and run the system. The
following minimum configuration is required for the PC.
Processer: Intel(R) Pentium(R)4 2.20GHz
Ram: 1 GB DDR2 333 MHz
Hard Disk 120 GB
Software Requirement for the Server
1. Operating System
Windows Server 2003
Operating System for a server should be such that it can manage and troubleshoot the server
efficiently when needed. So Operating System specially developed for the Server is
recommended.
2. Web Server
Apache
Web Server is required to host the system as the system is a server based system.
3. DBMS (Database Management System)
MySQL
DBMS is required to manage the database used in the system.
4. Web Browser
Mozilla Firefox
the CSS3 (stylesheet) and most of the JavaScript used in the system.
Software Required For the End Users
1. Operating System
Windows XP (SP2)

The End Users do not need the latest operating system, the system can run efficiently in the
Windows XP.
2. Web Browser
Mozilla Firefox
the CSS3 (stylesheet) and most of the JavaScript used in the system.

DEVELOPMENT AND
IMPLEMENTION

TESTING
INTRODUCTION
As an immediate phase after the complete development of the system, testing is an important
phase of the system development. A system‟s productivity, efficiency, reliability, all depends
on the output of the testing phase. Though a system can never be tagged as an error free, a
sincere testing helps us to gain the maximum possibility of reliable software.
In fact, in modern software engineering, the objective of testing is not to make sure that the
software is error free but to excavate as many possible of errors as we can.
TESTING STRATEGIES
For an effective carryout of testing, the whole testing phase was divided into three main parts:
1. Unit Testing
2. Integration Testing
3. System Testing
Unit Testing:
In this phase, each units (modules) of the system were tested individually. Dividing a whole
system into many smaller chunks of programs makes it easier to test the program as well as
increase its reusability.
Integration Testing:
After the completion, of unit testing each module is then integrated together to built a system.
While integrating, testing were done to find any errors and complications and make sure that
each module is functioning well along with others.
System Testing:
After each and every module were integrated together to make a complete system, testing
were conducted once again to make sure that the system was performing according to its
requirement. Any errors found while testing were noted down and debugged accordingly.
TESTING TECHNIQUES
For each of the above testing strategies, following testing techniques were used determining
the suitability of each.

1. Condition Testing
2. Data Flow Testing
3. Loop Testing
4. Equivalence Partitioning
5. Boundary Value Analysis
Condition Testing
Each condition of a program determines the flow of the program. So test cases were
designed to test the logical conditions in the program.
Data Flow Testing
Data flow testing was used to find the errors in the flows of data through the system
according to the location of definitions and variables used in the programs.
Loop Testing
Loop testing was used to find the occurrence of the errors in the loop construct of the
program. All types of loops were checked for the possible errors.
Equivalence Partitioning
Equivalence partitioning was used to derive the test cases by dividing the input domain to
the classes of data according the input conditions.
Boundary Value Analysis
Boundary value analysis was used to the find the possible errors at the edges of the input
data ranges.
TEST PLAN
Organizing the testing phase helps to achieve our testing goals. For this reason, test plan was
developed to clarify our testing objectives.
Common module

Login Form
Cases Objectives
1 To test if alert message is displayed when blank form is submitted.
2 To test if alert message is displayed when username is empty.
3 To test if alert message is displayed when password is empty.
4 To test if error message is displayed when incorrect username and password is

given.
5 To test if the page is directed towards the administrator/staff panel when staff id
and correct password is given.
6 To test if the page is directed towards the customer panel when customer id and
correct password is given.
Administrative / Staff Module
Add Staff form
Cases Objectives
1 To test if the submit button remains disabled if the required form fields are not
filled.
2 To test if alert message is displayed when telephone number is invalid.
3 To test if alert message is displayed when mobile number is invalid.
4 To test if alert message is displayed when email id is invalid.
5 To test if the pop up date selector works or not.
6 To test if the image file is uploaded or not.
7 To test if the submit button is enabled when all the required fields are filled and
valid.

View Record tab page (staff)
Cases Objectives
1 To test if searching of record by staff name works.
2 To test if multiple selection works.
3 To test if confirm message is displayed when delete button is clicked.
4 To test if record(s) is deleted when deletion is confirmed.
5 To test if the record detail is displayed when view button is clicked.
6 To test if the edit form is displayed when edit link is clicked.
7 To test if the updated record is displayed when save button is clicked.
8 To test if the current record is displayed when cancel button is clicked.
9 To test if privilege setting is displayed when privilege button is clicked.
10 To test if the logs records of a staff is displayed when logs button is clicked.
11 To test if the page is refreshed when refresh button is clicked.
Staff Attendance form
Cases Objectives
1 To test if alert message is displayed if blank form is tried to submit.
2 To test if staff suggestion are displayed when entering in the text input.
3 To test if the staff id and office timings are automatically generated after
selecting a staff.
4 To test if the hour input text box rejects the value more than 12
5 To test if the minute text box and second text box rejects value more than 60.
6 To test if the time input box pads the single digit number into double digit
number.

Staff Attendance Reports
Cases Objectives
1 To test if the corresponding records are shown when date is selected.
Customer addition form
Cases Objectives
1 To test if the submit button remains disabled if the required form fields are not
filled.
2 To test if alert message is displayed when telephone number is invalid.
3 To test if alert message is displayed when mobile number is invalid.
4 To test if alert message is displayed when email id is invalid.
5 To test if the pop up date selector works or not.
6 To test if the submit button is enabled when all the required fields are filled and
valid.
View Record tab page (Customer)
Cases Objectives
1 To test if searching of record by customer name works.
5 To test if the record detail is displayed when view button is clicked.
6 To test if the edit form is displayed when edit link is clicked.
7 To test if the updated record is displayed when save button is clicked.
8 To test if the current record is displayed when cancel button is clicked.

9 To test if privilege setting is displayed when privilege button is clicked.
10 To test if the logs records of a customer is displayed when logs button is clicked.
11 To test if the page is refreshed when refresh button is clicked.
Creating saving Account Form
Cases Objectives
1 To test if customer suggestion is shown when entering in the text box.
2 To test if a message is shown if the customer selected has already an active

saving account.
3 To test if form is displayed when the customer not having an account is selected.
4 To test if corresponding rate is generated when account name is selected.
5 To test if the principal input box accepts only the numeric numbers.
6 To test if alert message is displayed when blank form is tried to submit.
Saving Accounts Actions
Cases Objectives
1 To test if searching of record by A/c no works.
5 To test if the record detail is displayed when detail button is clicked.
6 To test if statement is displayed.
7 To test if the multiple activate/deactivate works.

Creating Loan Account Form
Cases Objectives
1 To test if customer suggestion is shown when entering in the text box.
2 To test if a message is shown if the customer selected has already an active loan
account.
3 To test if form is displayed when the customer not having an loan account is
selected.
4 To test if corresponding installment amount is generated when installment

frequency is selected.
5 To test if the issued amount input box accepts only the numeric numbers.
6 To test if alert message is displayed when blank form is tried to submit.
Loan Accounts Actions
Cases Objectives
1 To test if searching of record by A/c no works.
5 To test if the record detail is displayed when detail button is clicked.
6 To test if statement is displayed.
7 To test if the multiple activate/deactivate works.
Transaction
Cases Objectives
1 To test if error message is displayed when transaction category is clicked with

empty A/c no.

2 To test if transaction form is displayed when a valid A/c no is entered.
3 To test if alert message is displayed when amount is null.
4 To test if amount accepts only natural numbers.
Website
Cases Objectives
1 To test if an alert message is displayed when blank news and events form is tried
to submit.
2 To test if additional image upload is displayed when clicked in the “more” link
while adding images for news and events.
3 To test if multiple deletions are possible in news and events records.
4 To test if edit form is displayed when edit button clicked in news and events.
5 To test if respond form is displayed when respond button is clicked in feedback

and query.
6 To test if mail is sent to valid email address while responding the feedback.
7 To test if an alert message is displayed when blank career form tried to submit.
8 To test if edit form is displayed when edit button is clicked in career records.
9 To test if multiple deletions are possible in career records.
10 To test if an alert message is displayed when blank schemes form is tried to

submit.
11 To test if edit form is displayed when edit button is clicked in schemes records.
12 To test if multiple deletions are possible in schemes records.
Calendar
Cases Objectives
1 To test if new window showing calendar is opened when calendar icon is

clicked.

Messages
Cases Objectives
1 To test if latest message is shown first in inbox.
2 To test if respective message detail is shown in the left side in inbox.
3 To test if messages can be marked as read/unread.
4 To test if respective message detail is shown in the left side in outbox.
5 To test if contact suggestion is displayed based on category when clicking TO in

new message.
6 To test if contact can be selected when clicking in the suggestion list.
7 To test if contact selected earlier can be deleted.
8 To test if error message displayed when empty message is send.
User settings
Case Objectives
1 To test if user setting dialogue box is displayed when clicked on the hammer
icon.
2 To test if error message is displayed for an invalid password.
3 To test if change password option is displayed when valid password is given.
4 To test if an alert message is given when new password and confirm password
do not match.
5 To test if the password has been changed.
Customer Module
Account Summary
Cases Objectives
1 To test if new window showing statement is shown when statement button is

clicked.
Messages
Cases Objectives
1 To test if latest message is shown first in inbox.
2 To test if respective message detail is shown in the bottom in inbox.
3 To test if messages can be marked as read/unread.
4 To test if respective message detail is shown in the bottom in outbox.
5 To test if staff contacts suggestion is displayed when clicking TO in new

message.
6 To test if contact can be selected when clicking in the suggestion list.
7 To test if contact selected earlier can be deleted.
8 To test if error message displayed when empty message is send.
Transfer amount
Cases Objectives
1 To test if customer‟s own A/c number is shown automatically.
2 To test if error message is shown if the account number is invalid or null.
3 To test if error message is shown if the destine account number is same as

source a/c no.
4 To test if error message is shown when the amount is more than the 30% of the
available balance.
5 To test if the amount input box accepts the natural numbers only.
6 To test if an error message is shown when the invalid security code is entered.
7 To test if the amount is transferred to the destine account if the fields data are
valid.

Change Password
Case Objectives
1 To test if error message is displayed for an invalid password.
2 To test if change password option is displayed when valid password is given.
3 To test if an alert message is given when new password and confirm password
do not match.
4 To test if the password has been changed.
General Visitors Module
Feedback and Query
Case Objectives
1 To test if error message is displayed when a blank form is tried to submit.
2 To test if error message is displayed when invalid security code is given.

Test Cases
Test cases for the test plans are:
Common Login Form
TEST CASE 01
Test Objectives To test if alert message is displayed when blank form is submitted.
Test data Blank login form

Expected Result An alert message should be displayed.
Actual Result An alert message was displayed.
Conclusion Actual Result matched with the expected result.
TEST CASE 02
Test Objectives To test if alert message is displayed when username is empty.
Test data Login form with empty username.

TEST CASE 03
Test Objectives To test if alert message is displayed when password is empty.
Test data Login form with empty password.

TEST CASE 04
Test Objectives To test if error message is displayed when incorrect username and
password is given.
Test data Login form with random username and password.

Expected Result An error message should be displayed.
Actual Result An error message was displayed.

TEST CASE 05
Test Objectives To test if the page is directed towards the administrator/staff panel
when staff id and correct password is given.
Test data Username: STA1000 and Password: moon

Expected Result The page should be directed towards the staff panel.
Actual Result The page was directed towards the staff panel.
TEST CASE 06
Test Objectives To test if the page is directed towards the customer panel when
customer id and correct password is given.
Test data Username: CUS1000 and Password: smarika

Expected Result The page should be directed towards the customer panel.
Actual Result The page was directed towards the customer panel.
Administrative/ Staff module
Add staff form
TEST CASE 01
Test Objectives To test if the submit button remains disabled if the required form
fields are not filled.
Test data Empty form

Expected Result The submit button should be disabled.
Actual Result The submit button was disabled.

TEST CASE 02
Test Objectives To test if alert message is displayed when telephone number is
invalid.
Test data 5545256sO2

TEST CASE 03
Test Objectives To test if alert message is displayed when mobile number is
invalid.
Test data 98456t446

TEST CASE 04
Test Objectives To test if alert message is displayed when emailID is invalid.
Test data Fdsfa465

TEST CASE 05
Test Objectives To test if the pop up date selector works or not.
Test data Focus on the date input field.

Expected Result A pop up date picker should be displayed.
Actual Result A pop up date picker was displayed.

TEST CASE 06
Test Objectives To test if the image file is uploaded or not.
Test data Image file named “tulips.jpg”

Expected Result There should be a image with the name like tulips.jpg in the
upload folder.
Actual Result There was a image with the name dr54etulips.jpg in the upload
folder.(The name was slightly different as it was coded.)
TEST CASE 07
Test Objectives To test if the submit button is enabled when all the required fields
are filled and valid.
Test data Valid and filled form data.

Expected Result The submit button should be enabled.
Actual Result The submit button was enabled.
TEST CASE 01
Test Objectives To test if searching of record by staff name works.
Test data Ram

Expected Result Record of staff with name like “Ram” should be displayed.
Actual Result Record of staff with name “Ram Kumar Bhandari” was displayed.
TEST CASE 02
Test Objectives To test if multiple selection works.
Test data Select the checkbox in the header of the table.

Expected Result All the checkboxes in the table should be selected.
Actual Result All the checkboxes in the table were selected.

TEST CASE 03
Test Objectives To test if confirm message is displayed when delete button is
clicked.
Test data Click on the delete button by selecting any one of the records.
Expected Result A confirm message to delete record should be displayed.
Actual Result A confirm message to delete record was displayed.
TEST CASE 04
Test Objectives To test if record(s) is deleted when deletion is confirmed.
Test data Click on the yes button when ask to confirm the deletes.
Expected Result Selected records should be deleted.
Actual Result Selected records were deleted.
TEST CASE 05
Test Objectives To test if the record detail is displayed when view button is
clicked.
Test data Click on the view button of Staff name “Ram Kumar Bhandari”.
Expected Result The detail record of staff “Ram Kumar Bhandari” should be
displayed.
Actual Result The detail record of staff “Ram Kumar Bhandari” was displayed.
TEST CASE 06
Test Objectives To test if the edit form is displayed when edit link is clicked.
Test data Click on the edit button on the detail record page.
Expected Result The edit form should be displayed with current data.
Actual Result The edit form was displayed with current data.

TEST CASE 07
Test Objectives To test if the updated record is displayed when save button is
clicked.
Test data Click on the save button on the detail record page with some new
form data.
Expected Result The record detail should be displayed with recently saved data.
Actual Result The record detail was displayed with recently saved data.
TEST CASE 08
Test Objectives To test if the current record is displayed when cancel button is
clicked.
Test data Click on the cancel button on the detail record page without any
changed.
Expected Result The record detail should be displayed with no changed data.
Actual Result The record detail was displayed with no changed data.
TEST CASE 09
Test Objectives To test if privilege setting is displayed when privilege button is
clicked.
Test data Click on the privilege button of staff “Ram Kumar Bhandari”.
Expected Result Privilege details of “Ram Kumar Bhandari” should be displayed
Actual Result The privilege detail of “Ram Kumar Bhandari” was displayed.
TEST CASE 10
Test Objectives To test if the logs records of a staff is displayed when logs button
is clicked.
Test data Click on the logs button of staff “Ram Kumar Bhandari”.
Expected Result Logs details of “Ram Kumar Bhandari” should be displayed
Actual Result The logs detail of “Ram Kumar Bhandari” was displayed.

TEST CASE 11
Test Objectives To test if the page is refreshed when refresh button is clicked.
Test data Click on the Refresh button.

Expected Result The page should be refreshed.
Actual Result The page was refreshed.
Staff Attendance form
TEST CASE 01
Test Objectives To test if alert message is displayed if blank form is tried to
submit.
Test data Leave the fields empty and submit.

TEST CASE 02
Test Objectives To test if staff suggestion are displayed when entering in the text
input.
Test data Enter “r” on the text box

Expected Result “Ram Kumar Bhandari should be displayed”
Actual Result “Ram Kumar Bhandari was displayed”
TEST CASE 03
Test Objectives To test if the staff id and office timings are automatically
generated after selecting a staff.
Test data Click on the suggested “Ram Kumar Bhandari”

Expected Result Staff id and office timing of “Ram Kumar Bhandari should be
displayed.”
Actual Result Staff id and office timing of “Ram Kumar Bhandari were
displayed.”

TEST CASE 04
Test Objectives To test if the hour input text box rejects the value more than 12
Test data Enter 13 on the hour input text box

Expected Result 13 should be converted to 12.
Actual Result 13 was converted to 12.
TEST CASE 05
Test Objectives To test if the minute text box and second text box rejects value
more than 60.
Test data Enter 61 in both the minute text box and hour text box.
TEST CASE 06
Test Objectives To test if the time input box pads the single digit number into
double digit number.
Test data Enter 1 in all the time input boxes.

Staff Attendance Reports
TEST CASE 01
Test Objectives To test if the corresponding records are shown when date is
selected.
Test data Select a date from the popup date picker

Expected Result The date title should be changed accordingly
Actual Result The date title was changed accordingly

Customer Addition Form
TEST CASE 01
Test Objectives To test if the submit button remains disabled if the required form
fields are not filled.
Test data Empty form fields

Expected Result The submit button should be disabled.
Actual Result The submit button was disabled.
TEST CASE 02
Test Objectives To test if alert message is displayed when telephone number is
invalid.
Test data 55234ds654

TEST CASE 03
Test Objectives To test if alert message is displayed when mobile number is
invalid.
Test data 9803l652s

TEST CASE 04
Test Objectives To test if alert message is displayed when emailID is invalid.
Test data Tertrtg8979


TEST CASE 05
Test Objectives To test if the pop up date selector works or not.
Test data Focus on the date input field.

Expected Result A pop up date picker should be displayed.
Actual Result A pop up date picker was displayed.
TEST CASE 06
Test Objectives To test if the submit button is enabled when all the required fields
are filled and valid.
Test data Valid and filled form data.

Expected Result The submit button should be enabled.
Actual Result The submit button was enabled.
TEST CASE 01
Test Objectives To test if searching of record by customer name works.
Test data Smarika

Expected Result Record of staff with name like “Smarika” should be displayed.
Actual Result Record of staff with name “Smarika Basnet” was displayed.
TEST CASE 02

Expected Result All the checkboxes in the table should be selected.
Actual Result All the checkboxes in the table were selected.

TEST CASE 03
clicked.
Test data Click on the delete button by selecting any one of the records.
Expected Result A confirm message to delete record should be displayed.
Actual Result A confirm message to delete record was displayed.
TEST CASE 04
TEST CASE 05
Test Objectives To test if the record detail is displayed when view button is
clicked.
Test data Click on the view button of customer name “Moon Bajracharya”.
Expected Result The detail record of customer “Moon Bajracharya” should be
displayed.
Actual Result The detail record of customer “Moon Bajracharya” was displayed.
TEST CASE 06
Test Objectives To test if the edit form is displayed when edit link is clicked.
Test data Click on the edit button on the detail record page.
Expected Result The edit form should be displayed with current data.
Actual Result The edit form was displayed with current data.

TEST CASE 07
Test Objectives To test if the updated record is displayed when save button is
clicked.
Test data Click on the save button on the detail record page with some new
form data.
Expected Result The record detail should be displayed with recently saved data.
Actual Result The record detail was displayed with recently saved data.
TEST CASE 08
Test Objectives To test if the current record is displayed when cancel button is
clicked.
Test data Click on the cancel button on the detail record page without any
changed.
Expected Result The record detail should be displayed with no changed data.
Actual Result The record detail was displayed with no changed data.
TEST CASE 09
Test Objectives To test if privilege setting is displayed when privilege button is
clicked.
Test data Click on the privilege button of customer “Moon Bajracharya”.

Expected Result Privilege details of “Moon Bajracharya” should be displayed
Actual Result The privilege detail of “Moon Bajracharya” was displayed.
TEST CASE 10
Test Objectives To test if the logs records of a customer is displayed when logs
button is clicked.
Test data Click on the logs button of customer “Moon Bajracharya”.

Expected Result Logs details of “Moon Bajracharya” should be displayed
Actual Result The logs detail of “Moon Bajracharya” was displayed.

TEST CASE 11
Test Objectives To test if the page is refreshed when refresh button is clicked.
Test data Click on the Refresh button.

Expected Result The page should be refreshed.
Actual Result The page was refreshed.
Creating Saving Account Form
TEST CASE 01
Test Objectives To test if customer suggestion is shown when entering in the text
box.
Test data Enter “p” on the text box.

Expected Result Customers with name starting from “p” should be suggested.
Actual Result Customers with name starting from “p” were suggested.
TEST CASE 02
Test Objectives To test if a message is shown when the customer selected has
already an active saving account.
Test data Select “Prahlad Giri” from the suggestion.

Expected Result A message telling that “Prahlad Giri has already an active
account” should be displayed.
Actual Result A message telling that “Prahlad Giri has already an active
account” was displayed.
TEST CASE 03
Test Objectives To test if form is displayed when the customer not having an
account is selected.
Test data Select a customer not having an saving account

Expected Result A saving account form should be displayed.
Actual Result A saving account form was displayed.

TEST CASE 04
Test Objectives To test if corresponding rate is generated when account name is
selected.
Test data Select “Saving Account” from the account type.

Expected Result 7.9% should be displayed in the interest rate.
Actual Result 7.9% was displayed in the interest rate.
TEST CASE 05
Test Objectives To test if the principal input box accepts only the numeric
numbers.
Test data Try to enter 45465ds

Expected Result “ds” should be automatically deleted.
Actual Result “ds” was automatically deleted.
TEST CASE 06
Test Objectives To test if alert message is displayed when blank form is tried to
submit.
Test data Empty form fields.

TEST CASE 01
Test Objectives To test if searching of record by A/c no works.
Test data “10sa1”

Expected Result Records with A/c no starting with “10sa1” should be displayed.
Actual Result Records with A/c no starting with “10sa1” were displayed.

TEST CASE 02

Expected Result All the checkboxes in the record must be selected.
Actual Result All the checkboxes in the record were selected.
TEST CASE 03
clicked.
Test data Click on the delete button

Expected Result A confirm message should be displayed.
Actual Result A confirm message was displayed.
TEST CASE 04
TEST CASE 05
Test Objectives To test if the record detail is displayed when detail button is
clicked.
Test data Click on the detail button of A/c no 10sa1000

Expected Result The detail record account with A/c no 10sa10000 should be
displayed.
Actual Result The detail record account with A/c no 10sa10000 was displayed.

TEST CASE 06
Test Objectives To test if statement is displayed.
Test data Click on the statement button of A/c no 10sa10000

Expected Result The statement of account with A/c no 10sa10000 should be
displayed.
Actual Result The statement of account with A/c no 10sa10000 was displayed.
TEST CASE 07
Test Objectives To test if the multiple activate/deactivate works.
Test data Select the multiple checkboxes and click on activate or deactivate
button.
Expected Result The selected records should be activated or deactivated.
Actual Result The selected records were activated.
Creating Loan Account Form
TEST CASE 01
Test Objectives To test if customer suggestion is shown when entering in the text
box.
Test data Enter “p” on the text box.

Expected Result Customers with name starting from “p” should be suggested.
Actual Result Customers with name starting from “p” were suggested.
TEST CASE 02
Test Objectives To test if a message is shown when the customer selected has
already an active saving account.
Test data Select “Sampurna Lamichhane” from the suggestion.

Expected Result A message telling that “Sampurna Lamichhane has already an
active loan account” should be displayed.
Actual Result A message telling that “Sampurna Lamichhane has already an
active loan account” was displayed.

TEST CASE 03
Test Objectives To test if form is displayed when the customer not having an
account is selected.
Test data Select a customer not having an saving account

Expected Result A saving account form should be displayed.
Actual Result A saving account form was displayed.
TEST CASE 04
Test Objectives To test if corresponding installment amount is generated when
installment frequency is selected.
Test data Installment amount: 100000, Interest Rate : 13, time :3 and select
1 months
Expected Result 3369.4 should be displayed as installment amount.
Actual Result 3369.4 was displayed as installment amount.
TEST CASE 05
Test Objectives To test if the principal input box accepts only the numeric
numbers.
Test data Try to enter sa4785

Expected Result “sa” should be automatically deleted.
Actual Result “sa” was automatically deleted.
TEST CASE 06
Test Objectives To test if alert message is displayed when blank form is tried to
submit.


TEST CASE 01
Test Objectives To test if searching of record by A/c no works.
Test data “10lo1”

Expected Result Records with A/c no starting with “10lo1” should be displayed.
Actual Result Records with A/c no starting with “10lo1” were displayed.
TEST CASE 02

Expected Result All the checkboxes in the record must be selected.
Actual Result All the checkboxes in the record were selected.
TEST CASE 03
clicked.
Test data Click on the delete button

Expected Result A confirm message should be displayed.
Actual Result A confirm message was displayed.
TEST CASE 04

TEST CASE 05
Test Objectives To test if the record detail is displayed when detail button is
clicked.
Test data Click on the detail button of A/c no 10lo10000

Expected Result The detail record account with A/c no 10lo1000 should be
displayed.
Actual Result The detail record account with A/c no 10lo10000 was displayed.
TEST CASE 06
Test Objectives To test if statement is displayed.
Test data Click on the statement button of A/c no 10lo10000

Expected Result The statement of account with A/c no 10lo10000 should be
displayed.
Actual Result The statement of account with A/c no 10lo10000 was displayed.
TEST CASE 07
Test Objectives To test if the multiple activate/deactivate works.
Test data Select the multiple checkboxes and click on activate or deactivate
button.
Expected Result The selected records should be activated or deactivated.
Actual Result The selected records were activated.
Transaction
TEST CASE 01
Test Objectives To test if error message is displayed when transaction category is
clicked with empty A/c no.
Test data Click to an empty category with empty A/c no.

Expected Result Error message should be displayed.
Actual Result Error message was displayed.
TEST CASE 02
Test Objectives To test if transaction form is displayed when a valid A/c no is
entered.
Test data 10sa10000 click on the withdraw/deposit category

Expected Result Transaction form should be displayed.
Actual Result Transaction form was displayed.
TEST CASE 03
Test Objectives To test if alert message is displayed when amount is null.
Test data Left the amount null

TEST CASE 04
Test Objectives To test if amount accepts only natural numbers.
Test data “100000a”

Expected Result “a” should be removed.
Actual Result “a” was removed.
Website
TEST CASE 01
Test Objectives To test if an alert message is displayed when blank news and
events form is tried to submit.
Test data Empty form field.


TEST CASE 02
Test Objectives To test if additional image upload is displayed when clicked in the
“more” link while adding images for news and events.
Test data Click on the “more link”

Expected Result An additional file upload box should appear.
Actual Result An additional file upload box had appeared.
TEST CASE 03
Test Objectives To test if multiple deletions are possible in news and events
records.
Test data Select two or more records and click delete button.
Expected Result The selected record should be removed from the list.
Actual Result The selected record was removed from the list.
TEST CASE 04
Test Objectives To test if edit form is displayed when edit button clicked in news
and events.
Test data Click on the edit button of a record.

Expected Result Edit form should be displayed.
Actual Result Edit form should be displayed.
TEST CASE 05
Test Objectives To test if respond form is displayed when respond button is
clicked in feedback and query.
Test data Click on the respond button of a record.

Expected Result Respond form should be displayed.
Actual Result Respond form was displayed.

TEST CASE 06
Test Objectives To test if mail is sent to valid email address while responding the
feedback.
Test data Write a message in the respond form and click send.
Expected Result Mail should be sent to the concerned email id.
Actual Result Mail was sent to the concerned email id.
TEST CASE 07
Test Objectives To test if an alert message is displayed when blank career form
tried to submit.

TEST CASE 08
Test Objectives To test if edit form is displayed when edit button is clicked in
career records.

TEST CASE 09
Test Objectives To test if multiple deletions are possible in career records.
Expected Result The selected records should be removed from the list.
Actual Result The selected records were removed from the list.

TEST CASE 10
Test Objectives To test if an alert message is displayed when blank scheme form
tried to submit.

TEST CASE 11
Test Objectives To test if edit form is displayed when edit button is clicked in
scheme records.

TEST CASE 12
Test Objectives To test if multiple deletions are possible in scheme records.
Expected Result The selected records should be removed from the list.
Actual Result The selected records were removed from the list.
Calendar
TEST CASE 01
Test Objectives To test if new window showing calendar is opened when calendar
icon is clicked.
Test data Click on the calendar icon.

Expected Result A new window showing the calendar should be displayed.
Actual Result A new window showing the calendar was displayed.

Messages
TEST CASE 01
Test Objectives To test if latest message is shown first in inbox.
Test data Send a message from another user.

Expected Result The message just sent should be in top of the first page.
Actual Result The message just sent was in top of the first page.
TEST CASE 02
Test Objectives To test if respective message detail is shown in the left side in
inbox.
Test data Click a message thumbnail.

Expected Result The detail of the message should be shown in the left side.
Actual Result The detail of the message was shown in the left side.
TEST CASE 03
Test Objectives To test if messages can be marked as read/unread.
Test data Select one or more messages and choose read/unread.

Expected Result The icon of the messages should change after the page refreshes.
Actual Result The icon of the messages changed after the page refreshed.
TEST CASE 04
outbox.


TEST CASE 05
Test Objectives To test if contact suggestion is displayed based on category when
clicking TO in new message.
Test data Choose a contact category and click on To text box.

Expected Result The contact suggestion should be displayed.
Actual Result The contact suggestions were displayed.
TEST CASE 06
Test Objectives To test if contact can be selected when clicking in the suggestion
list.
Test data Clicked a contact suggestion.

Expected Result The clicked contact must be displayed on the To text box.
Actual Result The clicked contact was displayed on the To text box.
TEST CASE 07
Test Objectives To test if contact selected earlier can be deleted.
Test data Select some contacts and click on the “x”.

Expected Result The contact must be removed from the To box.
Actual Result The contact was removed from the To box.
TEST CASE 08
Test Objectives To test if error message displayed when empty message is send.
Test data Empty message fields.


User settings
TEST CASE 01
Test Objectives To test if user setting dialogue box is displayed when clicked on
the hammer icon.
Test data Click on the hammer icon.

Expected Result User setting dialogue box should be displayed.
Actual Result User setting dialogue box was displayed.
TEST CASE 02
Test Objectives To test if error message is displayed for an invalid password.
Test data An invalid password.

TEST CASE 03
Test Objectives To test if change password option is displayed when valid
password is given.
Test data A valid password.

Expected Result Change password form should be appended.
Actual Result Change password form was appended.
TEST CASE 04
Test Objectives To test if an alert message is given when new password and
confirm password do not match.
Test data “ram” “mar”

Expected Result Alert message should be shown.
Actual Result Alert message was shown.

TEST CASE 05
Test Objectives To test if the password has been changed.
Test data Logout and again login with old password.

Expected Result Error message should be shown.
Actual Result Error message was shown.
Customer Module
Account Summary
TEST CASE 01
Test Objectives To test if new window showing statement is shown when
statement button is clicked.
Test data Click the statement button.

Expected Result A new window showing account statement should be shown when
“Statement” Button is clicked.
Actual Result A new window showing account statement was shown when
“Statement” Button is clicked.
Messages
TEST CASE 01
Test Objectives To test if latest message is shown first in inbox.
Test data Send a message from another user.

Expected Result The message just sent should be in top of the first page.
Actual Result The message just sent was in top of the first page.
TEST CASE 02
inbox.

TEST CASE 03
Test Objectives To test if messages can be marked as read/unread.
Test data Select one or more messages and choose read/unread.

Expected Result The icon of the messages should change after the page refreshes.
Actual Result The icon of the messages changed after the page refreshed.
TEST CASE 04
outbox.

TEST CASE 05
Test Objectives To test if staff contacts suggestion is displayed when clicking TO
in new message.
Test data Click on To text box.

Expected Result The staff contacts suggestion should be displayed.
Actual Result The staff contacts suggestions were displayed.
TEST CASE 06
Test Objectives To test if contact can be selected when clicking in the suggestion
list.
Test data Clicked a contact suggestion.

Expected Result The clicked contact must be displayed on the To text box.
Actual Result The clicked contact was displayed on the To text box.
TEST CASE 07
Test Objectives To test if contact selected earlier can be deleted.
Test data Select some contacts and click on the “x”.

Expected Result The contact must be removed from the To box.
Actual Result The contact was removed from the To box.
TEST CASE 08
Test Objectives To test if error message displayed when empty message is send.
Test data Empty message fields.

Transfer Amount
TEST CASE 01
Test Objectives To test if customer‟s own A/c number is shown automatically.
Test data Log in to the system by user id cus1000

Expected Result A/c no 10sa10001 should be displayed.
Actual Result A/c no 10sa10001 was displayed.
TEST CASE 02
Test Objectives To test if error message is shown if the account number is invalid
or null.
Test data NULL or 4dssaa

Expected Result An error message should be shown.
Actual Result An error message was shown.

TEST CASE 03
Test Objectives To test if error message is shown if the destine account number is
same as source a/c no.
Test data 10sa10001

TEST CASE 04
Test Objectives To test if error message is shown when the amount is more than
the 30% of the available balance.
Test data 88888888888

TEST CASE 05
Test Objectives To test if the amount input box accepts the natural numbers only.
Test data 100d

Expected Result “d” should be removed automatically.
Actual Result “d” was removed automatically.
TEST CASE 05
Test Objectives To test if the amount input box accepts the natural numbers only.
Test data 100d

Expected Result “d” should be removed automatically.
Actual Result “d” was removed automatically.

TEST CASE 06
Test Objectives To test if an error message is shown when the invalid security
code is entered.
Test data fdsds

Expected Result An error should be displayed.
Actual Result An error was displayed.
TEST CASE 07
Test Objectives To test if the amount is transferred to the destine account if the
fields data are valid.
Test data Valid amount transfer data.

Expected Result The total amount of sender should be decreased and receiver
should be increased.
Actual Result The total amount of sender was decreased and receiver was
increased.
General visitors
Feedback and Query
TEST CASE 01
Test Objectives To test if error message is displayed when a blank form is tried to
submit.

TEST CASE 02
Test Objectives To test if error message is displayed when invalid security code is
given.
Test data lkjjfsd



SYSTEM IMPLEMENTATION
After the efficient testing and appropriate debugging of the errors found during the phase, the
system is now ready to be implemented in a live environment of the customer. This phase
demonstrate the actual usability of the system and may excavate new runtime errors which
may have escaped through the testing phase due to the lack of appropriate test data.
For the implementation of the system certain planning should be made before the
implementation known as Pre-Implementation and for after the implementation known as
Post-Implementation.
Pre-Implementation
The pre-implementation phase is signified by the preparation made for the installment of new
system to the customer‟s place along with the release of documents and the user training. Pre-
Implementation helps to make the end user familiar with the system and increase its
productivity.
 Data Conversion
As a part of Pre-implementation, data conversion is one of the major phase which

includes the conversion of the existing data of the old system so that it can be
inherited by the new system. Hence all the paper based data where fed into the system
by means of electronic input device such as keyboard and mouse.
 Document Release
Before the user training session is started, documentation such as “User Manual”,
“Operational Manual”, etc are distributed to the end users. This helps the user to know
more about the operations and the functions of the system and helps in easy
understanding during the training session.
 User Training
User Training was conducted for a week to explain the system‟s uses and
functionality to the customers and mainly end users. The areas covered during the
training session are:
 How to log into the system [For both Staffs and Customers]

 The functions performed by each of the links.
 Input/Output data of the system
 Capabilities and limitation of the system.
 How to set up the different users.
 Control Procedure Of Changeover
Now after the data conversion and user training has successfully been conducted, it
was time for the system change. Since the data and procedure of an Co-operative can
be vital, so Parallel [i.e running both systems for a certain period of time] changeover
was preferred to prevent the loss of data during the changeover process.
Post-Implementation
Post-Implementation includes the continue maintenance and review of the system. The user‟s
requirement can be changed during the actual running of the system. This change can be due
to the government policy, co-operative policy or due to the customer‟s desire. So continuous
maintenance is required for full functionality of the system. If the maintenance cannot
address the requirement, a review must be conducted which may advise the system be
redeveloped.
USER MANUAL:
To start the system, open Mozilla Firefox and type http://www.sundarco.com in your address
bar. Type in the corresponding Username(userid) and the password in the login box.
For staff/Administrator :
Username/Id: STA1000
Password : password
For Customer:
Username/Id : CUS1000
Password : password
Generally there are two users of this system. They are staff and customer. So our user manual is
divided into two parts.

i) User manual for staff
ii) User manual for customer
USER MANUAL (STAFF):
Please enter your staff username and password in the login section of the website.
Press enter to login.
The system will verify and direct you to the staff panel (fig 1) if your username and password are
correct.
Fig: Administrator or Staff login
We could perform the below activities in this section.
 Activities related to staff.
 Activities related to customer.
 Activities related to accounts (Loan and Saving).
 Managing content of the website.
1 Staff:

1.1 Add Staff:
 Press on the staff button at the left hand side of the main panel.
 Staff panel will open.
 Select Add Staff option.
 Fill in the details about the staff and Press submit button.
Fig: Add Staff
1.2 View Staff Record:
 Select View Record option.
 All record will be displayed.
 Select the view button at the right hand side of the staff whose detail you want to view.

Fig: View staff record.
1.3 Add Staff Attendance:
 Select Attendance option.
 A form will be displayed.
 Fill the detail in the form and click Add button.

1.3 Staff Attendance report
 Select Attendance report option.
 Select a date of which you want to see the attendance report.
 Press GO button.

Fig: Attendance report
2. Customer
2.1 Add new customer
 Press on the Customer button at the left hand side of the main panel.
 Customer panel will open.
 Select Add Customer option.
 Fill in the details about the Customer and Press submit button.

Fig: Add Customer Detail
2.2 View Customer Record
 Select the view button at the right hand side of the staff whose detail you want to view.

Fig: View Customer Record
Fig: Viewing Individual Record

2.2.3 Granting Privilege for customer
 Select the privilege button at the right hand side of the staff whose privilege you want to
set.
 Check the privilege you want to provide to the customer.
 Press Save button.
Fig: Granting Privilege

2.3 Viewing Reports:
 Select Reports option.
 Report will be displayed.
Fig: Viewing Report
3. Saving
3.1 Create New Account
 Press on the saving button at the left hand side of the main panel.
 Saving panel will open.
 Select Create Account option.
 Fill in the Account owner name.
 Press Enter.

Fig: Creating Saving Account
3.2 Controlling Account Action:
 Select Account actions option.
 Record will be displayed.
 You Could Delete, Activate, Deactivate, view detail and statement in this section.

Fig: Account Action main panel
3.2.1 Viewing Account Detail:
 Press on the Saving button at the left hand side of the main panel.
 Select Account Action option.
 Select the Detail button at the right hand side of the each data whose detail you want to
view.

Fig: Viewing Individual Account Detail.
3.2.2 Generating Statement:
 Press on the Saving button at the left hand side of the main panel.
 Select the Statement button at the right hand side of the each data whose saving
statement you want to view.

Fig: Saving statement
3.2.3 Deleting/Activating/ Deactivating an Account:
 Check a record which you want to delete/activate/deactivate.
 Press delete button to delete, activate to activate and deactivate to deactivate an account.

Fig: Account actions
4. Loan
4.1 Create Loan Account:
 Press on the Loan button at the left hand side of the main panel.
 Loan panel will open.
 Select Create Account option.
 Fill in the Account owner name.
 Press Enter.

Fig: Create Loan Account
4.2 Account Action Loan:
 Select Account actions option.
 Record will be displayed.
 You Could Delete, Activate, Deactivate, view detail and statement in this section.

Fig: Account Actions
4.2.1 Viewing Detail:
 Select the Detail button at the right hand side of the each data whose detail you want to
view.
 A window will pop out with the loan detail.

Fig: Individual Loan Detail
4.2.2 Generating Statement:
 Select the Statement button at the right hand side of the each data whose saving
statement you want to view.

4.2.3 Deleting/Activating/Deactivating an Account:
 Press on the loan button at the left hand side of the main panel.

5. Transaction:
 Press on the transaction button at the left hand side of the main panel.
 Transaction panel will open.
 Enter an Account number whose detail you want to see.
 Press Enter.
Fig: Transaction

6. Website Control:
6.1 Add news and Events:
 Press on the Web site button at the left hand side of the main panel.
 Web site panel will open where generally work related to web site is performed.
 A form will appear, fill in the form and press submit.
 News and event will be added in the web site.
Fig: Adding News and Events
6.2 View News and events:
 Select view news and events option.
 All news and events will appear.
 You can edit, delete, and deactivate the news and events you like.
Fig: Viewing news and events
6.2.1 Deleting/Editing/Deactivating News and Events:
 Press on the web site button at the left hand side of the main panel.
 Web panel will open.
 Select View news and Events option.

Fig: Deleting/Deactivating news and events
6.3 View feedback and Query:
 Select feedback and Query option.
 All feedback and query will appear.
 You can edit, delete, and deactivate the news and events you like.

Fig: View feedback and Query
6.3.1 Deleting a feedback or Query:
 Check the record you want to delete.
 Press delete button.

Fig: Deleting Record
6.3.2 Responding a feedback/Query
 Press respond button at the end of that feedback query you want to respond.
 Fill in the feedback form and press send.

6.4 Career:
6.4.1 Add new vacancy:
 Select Career option.
 Career panel will open.
 Fill in the form to add new vacancy.
 Press submit button.

Fig: Add Career
6.4.2 View Career:
 Career panel will open.
 Press submit button.

Fig: View Career
Editing/Deactivating/deleting:
 All record will appear.
 Check the record you want to delete/deactivate.
 Press delete/deactivate button.

Fig: Delete/Deactivate Career
6.5 Schemes
6.5.1 Add Schemes
 Select schemes option.
 Scheme panel will open.
 Press submit button

Fig: Add Schemes
6.5.2 View schemes:
 Select Scheme option.
 Scheme panel will open which shows all the schemes records.

6.5.3 Deleting schemes:
 Check the scheme record you want to delete.
 Press delete button after selecting:

6.5.4 Editing Schemes:
 Select the edit button at the side of the record you want to edit.
 A new edit window will pop out.
 Edit the record and press save button.

Fig: Edit scheme
7 .Sending mail:
 This icon at the right hand side indicates mail box.
 There are generally three parts in the mailbox Inbox, outbox and new message.
 Inbox contains the mails we received. Similarly outbox contains the message we sent.
 Click New message button to create a message.
 You can send mail by filling the required form.

Fig: Inbox
Fig: Creating new message
USER MANUAL (Customer):

Users are mainly benefitted with the following facilities;
 E banking
 Individual mail account
 Online statement review as well as printing.
1. Transferring Amount:
 Press on the Amount Transfer button at the left hand side of the Customer main panel.
 A form will appear.
 Fill in the information required.
 Click the Transfer button.
Fig: Amount Transfer
2. Sending Mail:
 Press on the New Message button at the left hand side of the Customer main panel.
 A form will appear.

 Fill in the information required.
 Click the Send button to send

mail
Fig: Sending mail
3. Viewing Account Summary:
 Press on the Account Summary button at the left hand side of the Customer main
panel.
 Your account information will appear
 To view the account statement click Statement button at the bottom.

Fig: Account Summary(i)
Fig: Statement

CRITICAL APPRAISAL
Group Appraisal
At present, Computer technology has made the world easier to perform day to day tasks. In
every sector, implementation of computer and its related equipments and programs are the
major objectives. Keeping in view of the importance of the computer driven system, Sundar
Saving and Credit Co-operative Limited made an approach to implement a computer driven
system.
The scopes of the Co-Operative were very small and till now the transaction were stored in
hard copies. So they didn‟t want the system to be complex. All they want was a simple
system that could act as bookkeeping. It was very difficult task to gather requirement from
them as they had very little time to share with us. Most often, the man responsible was unable
to meet.
The system is very easy to use and we have tried our best to make it user-friendly. The
system is effective to use as bookkeeping software and perform simple transaction like
deposit, withdraw, loan repayment calculations and generate the statement of each account.
But it cannot perform the complex accounting transactions like generating trial balance,
generating annual profit/loss report etc.
Besides the problems in requirement gathering there were technical problems while
developing and implementing the system. The problems like the slow internet bandwidth,
frequent electricity cut off were common. Due to monetary constraints, the mobile SMS
implementation was disapproved.

Individual Appraisal
Ram Kumar Bhandari [1801T3080068]
Project Proposal:
During the preparation of the proposal, I had to prepare the proposal for the new system
which included the specification of the new system and its ability to overcome the drawbacks
of the old system. I also prepared the Gantt chart for the time and schedule of the project.
Analysis:
For the analysis phase, I was responsible to interview the customer/members of the Co-
operative. It became the difficult task for me as most of the customers where not ready to
give the interview. Much of my time was consumed while convincing them. I was lucky to
make few of them to give interview. Next task for me was to research about the Co-operative
in the internet, which was not a big deal. Then I drafted the modeling of the requirement
using the DFDs.
Design:
For the design phase we divide, all the phase into parts and we all had all four main designs
to do. For the data design I designed the Entity Relationship Diagram and the normalization.
For this I get the advices from my supervisor and I revised the ER Diagram and the
normalization.
Software Development:
For the Development of the system, I wrote the source code for the library files and all the
JavaScript and Ajax functions needed for the system.
Testing:
For the testing phase, I was given the responsibility to write the test plan and test cases for the
Staff, Customer and Message sub-modules of the system. During the testing, many errors
were found and accordingly debugged.
Implementation:
During the implementation phase, I gave training to the users, making sure that they felt
comfortable using the system.

Actual Working Gantt Chart
Apr 2010 May 2010 Jun 2010 Jul 2010 Aug 2010 Sep 2010 Oct 2010 Nov 2010
ID Task Name Start Finish Duration
4/11 4/18 4/25 5/2 5/9 5/16 5/23 5/30 6/6 6/13 6/20 6/27 7/4 7/11 7/18 7/25 8/1 8/8 8/15 8/22 8/29 9/5 9/12 9/19 9/26 10/3 10/10 10/17 10/24 10/31 11/7 11/14 11/21
1 Preparation of Proposal 24/04/2010 07/05/2010 14d
2 Analyze phase starts: Fact Finding 07/05/2010 31/05/2010 25d
3 Refinement 31/05/2010 04/06/2010 5d
4 Modelling 04/06/2010 07/06/2010 4d
5 Specification draft( to user) 07/06/2010 13/06/2010 7d
6 Review 13/06/2010 16/06/2010 4d
7 Final Requirement Specification 17/06/2010 22/06/2010 6d
8 Design Phase starts: Data Design 23/06/2010 16/07/2010 24d
9 Architectural Design 10/07/2010 29/07/2010 20d
10 Interface Design 24/07/2010 05/08/2010 13d
11 Procedural Design 06/08/2010 25/08/2010 20d
12 System Design Document 26/08/2010 26/08/2010 1d
13 Development 27/08/2010 15/10/2010 50d
14 Testing: Unit Testing 10/10/2010 16/10/2010 7d
15 Testing: Integration Testing 16/10/2010 18/10/2010 3d
16 Testing: System Testing 18/10/2010 19/10/2010 2d
17 Hardware and Software Installation 20/10/2010 22/10/2010 3d
18 Preparation of Manuals 23/10/2010 26/10/2010 4d
19 Data conversion 27/10/2010 04/11/2010 9d
20 Release user guide and User training 07/11/2010 13/11/2010 7d
21 Implementation 13/11/2010 14/11/2010 2d
22 Review and maintenance 15/11/2010 24/11/2010 10d

Project Documentation

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Project Documentation

Diunggah oleh

Hak Cipta:

Format Tersedia

Online Co-Operative System 2010

Sundar Saving & Credit Co-Operative Ltd.

Project Group Members:

CENTER: INFORMATICS COLLEGE, KATHMANDU NEPAL

PROJECT SUPERVISOR: PRASHANT LAL SHRESTHA

Sundar Saving & Credit Co-Operative Ltd. 1

DFD for the Current System .................................................................................................................................... 9

Basic Problems and Limitations ......................................................................................................................... 11

Proposal of the New System .................................................................................................................................. 12

Objectives of the System:....................................................................................................................................... 12

Description of the system: .................................................................................................................................... 12

First Module: Admin Panel............................................................................................................................... 14

Second Module: Staff Panel .............................................................................................................................. 14

Third Module: Customer Panel / Guest Panel .......................................................................................... 14

Initial Specification .................................................................................................................................................... 15

Functional Specification: ....................................................................................................................................... 15

Work Distribution ...................................................................................................................................................... 16

Benefits of the New System ................................................................................................................................... 20

Hardware and Software Specification............................................................................................................. 20

For Operation of System: ....................................................................................................................................... 21

Cost/ Benefit Analysis of New System ............................................................................................................. 22

Payback Period Analysis Table:.......................................................................................................................... 24

Return on Investment Analysis: ......................................................................................................................... 24

Sundar Saving & Credit Co-Operative Ltd. 2

Introductive Description ........................................................................................................................................ 27

Questionnaire and survey ..................................................................................................................................... 34

Final Requirements from the Fact- Findings ............................................................................................... 42

Functional Requirements ...................................................................................................................................... 42

Non-Functional Requirements ............................................................................................................................ 43

Description of the Current System .................................................................................................................... 44

Organizational Structure ....................................................................................................................................... 45

Roles and Responsibilities within the organization ................................................................................... 45

Input/Output Specification of the current system ................................................................................... 48

Process Flow Diagram (Data Flow Diagram) .............................................................................................. 51

Problems and Limitation of the system.......................................................................................................... 53

Scope and Constraints .............................................................................................................................................. 55

Requirements Specification .................................................................................................................................. 57

Module 1: "System Administration Module" ................................................................................................. 57

Module 2: "Employee Panel Module" ............................................................................................................... 57

Module 3: "Customer Panel Module"................................................................................................................ 58

Module 4: "General Visitor Module" (Website)............................................................................................ 58

Description of the new System ............................................................................................................................ 60

Functional Modeling ................................................................................................................................................ 60

Data Flow Diagram .............................................................................................................................................. 60

Data Dictionary ..................................................................................................................................................... 63

Behavioral Modeling ............................................................................................................................................... 79

Sundar Saving & Credit Co-Operative Ltd. 3

State Transition Diagram.................................................................................................................................. 79

Data Design .................................................................................................................................................................... 86

Database System ....................................................................................................................................................... 86

Data Used in system................................................................................................................................................. 86

Entity Relationship Diagram [Before Normalization] ............................................................................... 93

Entity Relationship Diagram (After Normalization) ................................................................................ 100

Converting Entities into Relations (Tables) ................................................................................................ 102

Relationship Description between the entities (Relations) .................................................................. 113

Architectural Design ............................................................................................................................................... 118

Introduction .............................................................................................................................................................. 118

Architectural Modules .......................................................................................................................................... 118

Administrative Module .................................................................................................................................... 118

Employee Module .............................................................................................................................................. 120

Customer Module ............................................................................................................................................... 120

General Visitors Website ................................................................................................................................ 120

Program Structure.................................................................................................................................................. 122

Administrative Module .................................................................................................................................... 122