Académique Documents
Professionnel Documents
Culture Documents
PROJECT
DOCUMENTATION
Project Title: Online Co-operative System
TIME FRAME:
TABLE OF CONTENTS
PROPOSAL .......................................................................................................................................................................... 6
Introduction...................................................................................................................................................................... 7
Organization ..................................................................................................................................................................... 8
Current System................................................................................................................................................................ 9
Non-Functional Specification............................................................................................................................... 15
For development:...................................................................................................................................................... 20
Gantt Chart...................................................................................................................................................................... 24
ANALYSIS ......................................................................................................................................................................... 26
Fact findings................................................................................................................................................................... 28
Interview ...................................................................................................................................................................... 28
Observations ............................................................................................................................................................... 41
Research ....................................................................................................................................................................... 42
DESIGN .............................................................................................................................................................................. 59
Introduction ................................................................................................................................................................ 86
Normalization ............................................................................................................................................................ 95
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:
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.
Managing
Director
Sachin Bhattarai
Operational
Manager
Rahul Bhattarai
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.
Context Diagram
(current system)
Customer A/C
reception Transaction
Customer (loan)
process Process
Loan
Customer (deposit) Loan Information acception/
rejection
Customer A/C Loan data process
Customer Data
A/C opening Loan proposal
process Account Information study process
Diagram 0
(current system)
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 way of publicity and information flow between the customers.
Lack of reliable and secure data storage medium with the provision of proper backup
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.
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.
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.
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.
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
Customer data
New A/C Loan evaluation
Transaction
opening process A/C Information process
data
Diagram 0
(New 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
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.
NON-FUNCTIONAL SPECIFICATION
The system must be robust and secure enough from the unauthorized access and loss
of data.
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.
Student ID : 1801T3080068
Responsibilities:
Proposal:
Gantt Chart
Analysis:
Feasibility study
Fact findings
Requirement modeling
Requirement Specification
Design:
Data Design
Architectural Design
Procedural Design
Interface Design
Software Development
Software Testing
Operational manual
Implementation
Student ID : 1801T3080076
Responsibilities:
Proposal:
Introduction
Analysis:
Sundar Saving & Credit Co-Operative Ltd. 17
Online Co-Operative System 2010
Introduction
Fact findings
o Observation.
Design:
Data Design
Architecture Design
Procedural Design
Interface Design
Software Development
Software Testing
User training
Data conversion
Student ID : 1801T3080056
Responsibilities:
Proposal:
System benefits
Cost/Benefit study
Analysis:
Feasibility study
Fact findings
o Questionnaire preparation
Design:
Data Design
Architecture Design
Procedural Design
Interface Design
Software Development
Software Testing
User training
Data Conversion
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 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.
FOR DEVELOPMENT:
Minimum hardware requirement:
512 Mb of RAM,
Tools requirement:
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...
Server Requirement:
Web Server
Database Server
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
Operational Cost
Electricity
Similarly, assuming that multipurpose device consumes Rs. 15 in a day and the server
will also consumes Rs 15 in a day.
Therefore the total electricity consumption per year is Rs. 100*30*12 = Rs. 36,000
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
Sundar Saving & Credit Co-Operative Ltd. 22
Online Co-Operative System 2010
enlarging the market. This will obviously be an undeniable benefit in term of the
organization.
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.
(Note: It is not the actual annual profit of the overall organization. This benefit is only from the online
service)
Return on Investment (ROI) is calculated over the six years of system implementation.
GANTT CHART
The project will be started on 24th April 2010 and end on 19th November 2010 about 210
days.
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 Objectives:
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..
Post: Chairman
Interview Time: 10 am
Yes.
The new system should provide the feature of online account query,cash transfer for
customer through their account number as well .
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.
Should have feature of account query and cash tansfer for the customer.
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?
Yes.
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.
Date: 27/01/2010
Time: 1 PM
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.
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.
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.
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.
Participants
Co-operative Staffs: 15
Customers: 25
Yes
No
Partially
Yes
No
c. What are the problems you are facing with the current system?
Difficulty in management
Both
e. Do you think the proposed system will eradicate the faced problem?
Yes
No
Partially
Yes
No
g. Should account query feature via account number be included in new system?
Yes
No
Yes
No
Yes
No
Fair
More
Less
Yes
No
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.
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.
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.
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.
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.
FUNCTIONAL REQUIREMENTS
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
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
Managing
Director
Sachin Bhattarai
Operational
Manager
Rahul Bhattarai
Organization Chart
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:
The managers make use of the system for performing the following jobs:
Operational Manager
Make sure that the employees are performing their jobs well
Finance Manager
Provide suggestion and advice on the financial matters to the upper level employees.
Remove an employee.
Marketing Manager
Miscellaneous Manager
Make sure of the availability of the materials required to run the system.
Computer operator.
The current input and output of the process in system are shown in tabular form below.
Process No 01
Description Opening of the account for the saving and withdraw process.
Process No 02
Process No 03
Process No 04
Input Data Request Data including the customer information and the loan
information
Process No 05
Process No 06
Process Name 07
Process Name 08
Description Put the customer's name in black list if he/she hasn't pay the loan in
required amount of time.
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
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 Data
A/C opening Loan proposal
process Account Information study process
Level 1 DFD
(current 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.
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.
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.
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.
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.
The cost of operating the current system is higher in comparison to the output
provided by the system.
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 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 receive, save and reply the queries from various users.
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.
REQUIREMENTS SPECIFICATION
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.
ix. Able to generate different reports or manipulate database using the SQL query.
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.
xi. Able to fill the loan data form and save it.
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]
DESIGN
“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.
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.
Provide Statement
Provide Statement
Perform Amount Transfer Issue/reject loan
Sundar CMS
Output Information System Provide response
Context Diagram
Level 1 Diagram
Output
Confirmation
data
Query/
Feedback
Processing
Visitors
Level 1 Diagram
DATA DICTIONARY
Data Elements:
Length : 5
Source : System
Type : String
Length : 15
Type : String
Length : 15
Type : String
Length : 15
Type : String
Length : 25
Type : String
Length :
Type : String
Length :
Type : Date
Length :
Type : String
Length : 20
Type : String
Length : 20
Type : Numbers
Length: 15
Type : String
Length: 25
Type : Date
Length:
Type : String
Length: 20
Type : String
Length : 20
Type : String
Length : 15
Type : String
Length: 20
Type : String
Length: 35
Type : String
Length : 45
Type : Date
Length :
Type : String
Length: 25
Type : String
Length: 6
Type : String
Length : 50
Type : String
Length : 45
Type : String
Length : 45
Type : String
Length : 45
Type : String
Length : 50
Type : String
Length : 45
Type : String
Length : 50
Type : String
Length : 15
Type : String
Length : 20
Length:
Type : Number
Length :
Length :
Type : Number
Length :
Data Flows :
Description : Notification message to notify the customer about the acceptance or rejection of
the loan request.
Data Store :
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 :
Purpose : To perform the appropriate transaction while depositing and withdrawing amount
from an account.
Purpose : To perform appropiate procedure while transformin amount from one account to
another account.
Purpose : To receive and respond the query and feedback from the visitors
Sundar Saving & Credit Co-Operative Ltd. 77
Online Co-Operative System 2010
Purpose : Act as intermediate process to perorm the task related with database
External Entities :
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
BEHAVIORAL MODELING
Unauthenticate
User Authenticated
Staff panel
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
Customer Panel
On click Delete
On click X
Button
Invoke close privilege Box
On click Add Customer Button Invoke confirmation
Invoke appropriate message
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
Saving Panel
Creating New
Viewing Records Viewing Reports
Account
On click Delete
Button
On click X
On click Create Button Invoke confirmation
Invoke close statement Box
Invoke appropriate message
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
Loan Panel
Creating New
Viewing Records Viewing Reports
Account
On click Delete
Button
On click X
On click Create Button Invoke confirmation
Invoke close statement Box
Invoke appropriate message
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
Transaction Panel
Displaying Balance
Information & Prompting for Prompting for
prompting for amount amount
amount
Website
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]
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.
The data used by the system can be categorized into two main categories.
Manually fed data are those which are fed to the system by means of forms by the user.
c. Date of Birth
e. Avatar (image)
g. Email Id
i. Office timing
j. Username, Password
a. Date
b. Incoming time
c. Outgoing Time
d. Remark
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
b. Account Name
c. Account type
e. Entered By N
f. Approved By
g. Interest Rate
h. Principal Amount
i. Time
b. Loan type
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.
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
a. Heading
b. Body
c. Images
a. Name
b. Email
c. Comments/ query
a. Post Title
b. Required no.
c. Qualification
d. Experience
e. Details
a. Schemes Type
b. Name
c. Rate
d. Details
a. Heading
b. Details
a. Message Detail
System generated data are those data that are generated by the system using the generic
logics or some predefined function.
a. Customer PIN
b. Added Date
a. Account Number
b. Date
a. Account Number
b. Date
a. Debit amount
b. Credit amount
c. Total balance
d. Available balance
a. News id
b. Date
a. Id
b. Date
c. Time
a. Id
b. Date
a. Id
a. ID
b. Date
c. Time
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.
4. Only customers having saving accounts active can apply for the loan.
Queries/
Visitors send
Feedbacks
Queries/
Staff respond
Feedbacks
NORMALIZATION
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)
Sundar Saving & Credit Co-Operative Ltd. 95
Online Co-Operative System 2010
1NF
Loan_logs()
2NF
Loan_logs()
3NF
Loan_logs()
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
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) - - -
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 - -
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) - - -
ADDEDDATE Date - - -
ACC_STATEMENT Int(1) 0 - -
AMT_TRANSFER Int(1) 0 - -
CHNG_PASSWORD Int(1) 0 - -
VIEW_SUMMARY Int(1) 0 - -
SAVING_ACNO Varchar(15) - -
SAVING_NAME Varchar(20) - - -
SAVING_TYPE Varchar(20) - - -
SAVING_SIGNATURE Varchar(50) - - -
SAVING_TIME Double - - -
SAVING_ENTEREDBY Varchar(15) - - -
SAVING_APPROVEDBY Varchar(15) - -
SAVING_OPENEDDATE Date - - -
SAVING_TOTALBALANCE Double - - -
SAVING_AVAILABLEBALANCE Double - - -
CUST_PIN Varchar(15) - -
SAVING_INTERESTDAY Date -
LOAN_ACNO Varchar(15) - -
LOAN_TYPE Varchar(20) - - -
LOAN_BUSSNAME Varchar(20) - - -
LOAN_BUSSADD Varchar(50) - - -
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_APPROVEDBY Varchar(15) - -
LOAN_APPROVEDDATE Date - - -
CUST_PIN Varchar(15) - -
SAVINGLOGS_DATE Date - -
SAVING_ACNO Varchar(15) - -
SAVINGLOGS_DESCRIPTION Text - - -
BALANCE Double - - -
LOANLOGS_DATE Date - -
LOAN_ACNO Varchar(15) - -
ATTEND_DATE Date - -
STAFF_ID Varchar(15) -
ATTEND_INTIME Time - - -
ATTEND_REMARK Text - - -
LOGS_ID Date - -
LOGS_DATE Date - - -
LOGS_CONCERN Varchar(15) - -
LOGS_DESCRIPTION Text - - -
LOGS_TIME Time - - -
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) - - -
NEWS_ID Int(10) - -
NEWS_HEAD Text - - -
NEWS_BODY Text - - -
NEWS_IMAGE Text - - -
NEWS_DATE Date - - -
NEWS_STATUS Int(1) - - -
COMMENT_ID Int(10) - -
COMMENT_NAME Varchar(40) - - -
COMMENT_EMAIL Varchar(20) - - -
COMMENT_FEEDBACK Text - - -
COMMENT_DATE Date - - -
COMMENT_STATUS Int(1) - - -
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) - - -
SCHEME_ID Int(10) - -
SCHEME_NAME Varchar(25) - - -
SCHEME_TYPE Varchar(20) - - -
SCHEME_DETAIL Text - - -
SCHEME_STATUS Int(10) - - -
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
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
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
Customer Panel
Add Customers
Saving Panel
Loan Panel
Transaction Panel
Website Panel
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
about us, giving information about the organization, board of directors, team, location
etc.
schemes, giving information about the saving schemes and loan schemes
News and Events, giving information about the recent news and events of the
company
PROGRAM STRUCTURE
ADMINISTRATIVE MODULE
Staff Panel
Admin Panel
1, 2 14
If C1
Staff Interface
-
While C3
While C2
* Attendance*
Add Staff List Staffs Attendance
reports
3,4 5 13
11,12
6 7,8 9 10
Customer Panel
Admin Panel
1, 2 11
Check Customer
privilege
If C1
Customer
Interface -
While C2
*
Add Customer List Customer
3,4 5
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
8. Save updated Record
9. Delete Record
10. Set up privileges
11. Close library files
Saving Panel
Admin Panel
1, 2 11
If C1
Saving Interface
-
While C2
Create *
List Accounts Statement
Account
3,4 5
10
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
8. Save updated Record
9. Delete Record
10. Get Accounts Statement
11. Close library files
Fig : Program Structure : Saving Sub- Module
Loan Panel
Admin Panel
1, 2 11
If C1
Loan Interface
-
While C2
Create *
List Accounts Reports
Account
3,4 5
10
6 7,8 9
Functions List
Condition list
1. Declare Library files for use
C1: loan Privilege == 1
2. Declare data variables
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
8. Save updated Record
9. Delete Record
10. Get Accounts Reports
11. Close library files
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
4, 5, 6
Website Panel
Admin Panel
1, 2 9
If C1
Website Interface
-
3, 4, 5, 6 4,6,7 3, 4, 5, 6,
3, 4, 5, 6
Applies
4, 6, 8
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
3
If C1
4 5 6, 7, 8
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.
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
Website Panel
website
Is link equal to
Reports panel
reports
Is equal to logout
Stop
Stop
Staff panel
Click action
tab
No
No
Yes Update
Is action equal to
Staff Save to database
edit satff?
Information
No
No
No
Get add
Is action equal to Yes
attendance Save to database
attendance
form
No
No
Stop
Customer Panel
Stop
Customer panel
Click action
tab
No
No
Yes Update
Is action equal to
customer Save to database
edit customer?
Information
No
No
No
Stop
Saving Panel
Stop
Saving panel
Click action
tab
No
No
Yes Update
Is action equal to
account Save to database
edit account?
Information
No
No
Stop
Loan Panel
Stop
Loan panel
Click action
tab
No
No
Yes Update
Is action equal to
account Save to database
edit account?
Information
No
No
Stop
Transaction Panel
Stop
Transaction panel
Click action
tab
Prompt
Is action equal to Yes Account
Save to database
withdraw? Number,
amount
No
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
No
No
No
No
Is equal to logout
Yes
Stop
INTERFACE DESIGN
Administrative/Staff Module
Welcome Screen
Link
Application Banner
Link 1
Link 2
Link 3
Link 4
Welcome text
Link 5
Link 6
Text
Link
Application Banner
Button Button
Text
Link
Application Banner
Text
Link
Application Banner
Link 6
Personal Data
Edit Link
Edit Link
Contact Data
Edit Link
Official Data
Button
Text
Link
Application Banner
Title Text X
Link 3 Text
Prompt Input Text Box Button
Text
Text
Link 4 Text
Button
Link 5 Column Column
heading heading
Link 6 Button Button
Data Data
Button Button Button
Data Data
Button Button Button
Text
Link
Application Banner
Title Text X
Text
Link
Application Banner
Link 1
Tab 1 Tab 2 Tab 3 Tab 4
Link 2
Header Text
Link 3 Prompt Input Text Box
Link 4 Text
Prompt Input Text Box
Text
Link 5 Prompt Input Text Box
Text
Link 6 Text Text
Prompt Text
Button Button
Text
Link
Application Banner
Link 1
Tab 1 Tab 2 Tab 3 Tab 4
Link 2
Header Text
Link 3
Link 4 Prompt Input Text Box Button
Text
Link 5
Text
Link 6
Column Column Column Column
header header header header
Text
Link
Application Banner
Link 5
Button
Link 6 Column Column
heading heading
Data Data
Button Button Button
Data Data
Button Button Button
Text
Link
Application Banner
Link 2
Header Text
Link 3
Prompt Input Text Box Button
Link 4
Text
Link 5
Prompt Input Text Box
Link 6 Text
Prompt Text Text
Prompt Input Text Box
Text
Prompt Text Radio Radio Radio
Prompt Text Button
Radio Button
Radio Button
Radio
Prompt Input Text Box
Button Button Button
Prompt Input Text Box
Text
Text
Prompt Input Text Box
Text
Prompt Text Radio Radio Radio
Prompt Text Button Button Button
File Browser Text Box Button
Prompt Text Drop Down list
Button Button
Text
Link
Application Banner
Link 2
Header Text
Link 3
Prompt Input Text Box Button
Link 4 Text
Prompt Text Button
Link 5
Button Button Button
Link 6
Column Column
Header Header
Data Data
Button Button
Data Data
Button Button
Text
Link
Application Banner
Link 2
Header Text
Link 3
Prompt Input Text Box Button
Link 4
Text
Link 5
Prompt Input Text Box
Link 6 Text
Prompt Text Text
Prompt Input Text Box
Text
Prompt Text Radio Radio
Prompt Text Button
Text area Button
Button Button
Text
Link
Application Banner
Link 1 Tab 1
Link 2
Link 3 Prompt Input Text Box Button
Text
Link 4 Radio Radio Radio
Button Button Button
Link 5
Text
Link
Application Banner
Link 1 Tab 1
Link 2
Link 3 Prompt Input Text Box Button
Text
Link 4 Radio Radio Radio
Button Button Button
Link 5
Text
Website
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Prompt Input Text Box
Link 5
Text
Link 6 Prompt Text Rich Text area
Button Button
Text
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Prompt Text Button
Link 5
Link 6 Button
Data Data
Button Button
Data Data
Button Button
Text
Link
Application Banner
Link 4 Button
Text
Link
Application Banner
Link 2
Tab 1 Tab 2
Link 3
Heading Text
Link 4
Prompt Input Text Box
Link 5
Text
Prompt Input Text Box
Link 6
Text
Prompt Input Text Box
Text
Prompt Input Text Box
Text
Prompt Input Text Box
Text
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
Prompt Input Text Box
Link 5
Text
Prompt Text Radio Radio
Link 6
Button Button
Prompt Input Text Box
Text
Prompt Input Text Box
Text
Button Button
Text
Messages
Inbox/Outbox
Link
Application Banner
Link 6 Data
Data
Data
Data
Data
Data
Text
New Messages
Link
Application Banner
Button Button
Text
User Settings
Link
Application Banner
Title Text X
Button Button
Text
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.
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.
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.
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.
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.
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.
Hard Disk 1 TB
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.
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.
1. Operating System
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.
MySQL
4. 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.
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 system runs on the browser. Mozilla Firefox is recommended because it supports
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
3. Loop Testing
4. Equivalence Partitioning
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 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 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
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.
Cases Objectives
1 To test if the submit button remains disabled if the required form fields are not
filled.
7 To test if the submit button is enabled when all the required fields are filled and
valid.
Cases Objectives
10 To test if the logs records of a staff is displayed when logs button is clicked.
Cases Objectives
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.
Cases Objectives
Cases Objectives
1 To test if the submit button remains disabled if the required form fields are not
filled.
6 To test if the submit button is enabled when all the required fields are filled and
valid.
Cases Objectives
10 To test if the logs records of a customer is displayed when logs button is clicked.
Cases Objectives
3 To test if form is displayed when the customer not having an account is selected.
5 To test if the principal input box accepts only the numeric numbers.
Cases Objectives
Cases Objectives
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.
5 To test if the issued amount input box accepts only the numeric numbers.
Cases Objectives
Transaction
Cases Objectives
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.
4 To test if edit form is displayed when edit button clicked in news and events.
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.
11 To test if edit form is displayed when edit button is clicked in schemes records.
Calendar
Cases Objectives
Messages
Cases Objectives
User settings
Case Objectives
1 To test if user setting dialogue box is displayed when clicked on the hammer
icon.
4 To test if an alert message is given when new password and confirm password
do not match.
Customer Module
Account Summary
Cases Objectives
clicked.
Messages
Cases Objectives
Transfer amount
Cases Objectives
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
3 To test if an alert message is given when new password and confirm password
do not match.
Case Objectives
Test Cases
TEST CASE 01
Test Objectives To test if alert message is displayed when blank form is submitted.
TEST CASE 02
Test Objectives To test if alert message is displayed when username is empty.
TEST CASE 03
Test Objectives To test if alert message is displayed when password is empty.
TEST CASE 04
Test Objectives To test if error message is displayed when incorrect username and
password is given.
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 CASE 06
Test Objectives To test if the page is directed towards the customer panel when
customer id and correct password is given.
TEST CASE 01
Test Objectives To test if the submit button remains disabled if the required form
fields are not filled.
TEST CASE 02
Test Objectives To test if alert message is displayed when telephone number is
invalid.
TEST CASE 03
Test Objectives To test if alert message is displayed when mobile number is
invalid.
TEST CASE 04
Test Objectives To test if alert message is displayed when emailID is invalid.
TEST CASE 05
Test Objectives To test if the pop up date selector works or not.
TEST CASE 06
Test Objectives To test if the image file is uploaded or not.
TEST CASE 07
Test Objectives To test if the submit button is enabled when all the required fields
are filled and valid.
TEST CASE 01
Test Objectives To test if searching of record by staff name works.
TEST CASE 02
Test Objectives To test if multiple selection works.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 11
Test Objectives To test if the page is refreshed when refresh button is clicked.
TEST CASE 01
Test Objectives To test if alert message is displayed if blank form is tried to
submit.
TEST CASE 02
Test Objectives To test if staff suggestion are displayed when entering in the text
input.
TEST CASE 03
Test Objectives To test if the staff id and office timings are automatically
generated after selecting a staff.
TEST CASE 04
Test Objectives To test if the hour input text box rejects the value more than 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.
Expected Result 61 should be converted to 60.
Actual Result 61 was converted to 60.
Conclusion Actual Result matched with the expected result.
TEST CASE 06
Test Objectives To test if the time input box pads the single digit number into
double digit number.
TEST CASE 01
Test Objectives To test if the corresponding records are shown when date is
selected.
TEST CASE 01
Test Objectives To test if the submit button remains disabled if the required form
fields are not filled.
TEST CASE 02
Test Objectives To test if alert message is displayed when telephone number is
invalid.
TEST CASE 03
Test Objectives To test if alert message is displayed when mobile number is
invalid.
TEST CASE 04
Test Objectives To test if alert message is displayed when emailID is invalid.
TEST CASE 05
Test Objectives To test if the pop up date selector works or not.
TEST CASE 06
Test Objectives To test if the submit button is enabled when all the required fields
are filled and valid.
TEST CASE 01
Test Objectives To test if searching of record by customer name works.
TEST CASE 02
Test Objectives To test if multiple selection works.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 09
Test Objectives To test if privilege setting is displayed when privilege button is
clicked.
TEST CASE 10
Test Objectives To test if the logs records of a customer is displayed when logs
button is clicked.
TEST CASE 11
Test Objectives To test if the page is refreshed when refresh button is clicked.
TEST CASE 01
Test Objectives To test if customer suggestion is shown when entering in the text
box.
TEST CASE 02
Test Objectives To test if a message is shown when the customer selected has
already an active saving account.
TEST CASE 03
Test Objectives To test if form is displayed when the customer not having an
account is selected.
TEST CASE 04
Test Objectives To test if corresponding rate is generated when account name is
selected.
TEST CASE 05
Test Objectives To test if the principal input box accepts only the numeric
numbers.
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 CASE 02
Test Objectives To test if multiple selection works.
TEST CASE 03
Test Objectives To test if confirm message is displayed when delete button is
clicked.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 05
Test Objectives To test if the record detail is displayed when detail button is
clicked.
TEST CASE 06
Test Objectives To test if statement is 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.
Conclusion Actual Result matched with the expected result.
TEST CASE 01
Test Objectives To test if customer suggestion is shown when entering in the text
box.
TEST CASE 02
Test Objectives To test if a message is shown when the customer selected has
already an active saving account.
TEST CASE 03
Test Objectives To test if form is displayed when the customer not having an
account is selected.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 05
Test Objectives To test if the principal input box accepts only the numeric
numbers.
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 CASE 02
Test Objectives To test if multiple selection works.
TEST CASE 03
Test Objectives To test if confirm message is displayed when delete button is
clicked.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 05
Test Objectives To test if the record detail is displayed when detail button is
clicked.
TEST CASE 06
Test Objectives To test if statement is 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.
Conclusion Actual Result matched with the expected result.
Transaction
TEST CASE 01
Test Objectives To test if error message is displayed when transaction category is
clicked with empty A/c no.
TEST CASE 02
Test Objectives To test if transaction form is displayed when a valid A/c no is
entered.
TEST CASE 03
Test Objectives To test if alert message is displayed when amount is null.
TEST CASE 04
Test Objectives To test if amount accepts only natural numbers.
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 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 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.
Conclusion Actual Result matched with the expected result.
TEST CASE 04
Test Objectives To test if edit form is displayed when edit button clicked in news
and events.
TEST CASE 05
Test Objectives To test if respond form is displayed when respond button is
clicked in feedback and query.
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.
Conclusion Actual Result matched with the expected result.
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.
Test data Select two or more records and click delete button.
Expected Result The selected records should be removed from the list.
Actual Result The selected records were removed from the list.
Conclusion Actual Result matched with the expected result.
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.
Test data Select two or more records and click delete button.
Expected Result The selected records should be removed from the list.
Actual Result The selected records were removed from the list.
Conclusion Actual Result matched with the expected result.
Calendar
TEST CASE 01
Test Objectives To test if new window showing calendar is opened when calendar
icon is clicked.
Messages
TEST CASE 01
Test Objectives To test if latest message is shown first in inbox.
TEST CASE 02
Test Objectives To test if respective message detail is shown in the left side in
inbox.
TEST CASE 03
Test Objectives To test if messages can be marked as read/unread.
TEST CASE 04
Test Objectives To test if respective message detail is shown in the left side in
outbox.
TEST CASE 05
Test Objectives To test if contact suggestion is displayed based on category when
clicking TO in new message.
TEST CASE 06
Test Objectives To test if contact can be selected when clicking in the suggestion
list.
TEST CASE 07
Test Objectives To test if contact selected earlier can be deleted.
TEST CASE 08
Test Objectives To test if error message displayed when empty message is send.
User settings
TEST CASE 01
Test Objectives To test if user setting dialogue box is displayed when clicked on
the hammer icon.
TEST CASE 02
Test Objectives To test if error message is displayed for an invalid password.
TEST CASE 03
Test Objectives To test if change password option is displayed when valid
password is given.
TEST CASE 04
Test Objectives To test if an alert message is given when new password and
confirm password do not match.
TEST CASE 05
Test Objectives To test if the password has been changed.
Customer Module
Account Summary
TEST CASE 01
Test Objectives To test if new window showing statement is shown when
statement button is clicked.
Messages
TEST CASE 01
Test Objectives To test if latest message is shown first in inbox.
TEST CASE 02
Test Objectives To test if respective message detail is shown in the left side in
inbox.
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.
Conclusion Actual Result matched with the expected result.
TEST CASE 03
Test Objectives To test if messages can be marked as read/unread.
TEST CASE 04
Test Objectives To test if respective message detail is shown in the left side in
outbox.
TEST CASE 05
Test Objectives To test if staff contacts suggestion is displayed when clicking TO
in new message.
TEST CASE 06
Test Objectives To test if contact can be selected when clicking in the suggestion
list.
Actual Result The clicked contact was displayed on the To text box.
Conclusion Actual Result matched with the expected result.
TEST CASE 07
Test Objectives To test if contact selected earlier can be deleted.
TEST CASE 08
Test Objectives To test if error message displayed when empty message is send.
Transfer Amount
TEST CASE 01
Test Objectives To test if customer‟s own A/c number is shown automatically.
TEST CASE 02
Test Objectives To test if error message is shown if the account number is invalid
or null.
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 CASE 04
Test Objectives To test if error message is shown when the amount is more than
the 30% of the available balance.
TEST CASE 05
Test Objectives To test if the amount input box accepts the natural numbers only.
TEST CASE 05
Test Objectives To test if the amount input box accepts the natural numbers only.
TEST CASE 06
Test Objectives To test if an error message is shown when the invalid security
code is entered.
TEST CASE 07
Test Objectives To test if the amount is transferred to the destine account if the
fields data are valid.
General visitors
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.
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
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]
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.
Please enter your staff username and password in the login section of the website.
The system will verify and direct you to the staff panel (fig 1) if your username and password are
correct.
1 Staff:
Press on the staff button at the left hand side of the main panel.
Fill in the details about the staff and Press submit button.
Press on the staff button at the left hand side of the main panel.
Select the view button at the right hand side of the staff whose detail you want to view.
Press on the staff button at the left hand side of the main panel.
Press on the staff button at the left hand side of the main panel.
Press GO button.
2. Customer
Press on the Customer button at the left hand side of the main panel.
Fill in the details about the Customer and Press submit button.
Press on the Customer button at the left hand side of the main panel.
Select the view button at the right hand side of the staff whose detail you want to view.
Press on the Customer button at the left hand side of the main panel.
Select the privilege button at the right hand side of the staff whose privilege you want to
set.
Press on the Customer button at the left hand side of the main panel.
3. Saving
Press on the saving button at the left hand side of the main panel.
Press Enter.
Press on the saving button at the left hand side of the main panel.
You Could Delete, Activate, Deactivate, view detail and statement in this section.
Press on the Saving button at the left hand side of the main panel.
Select the Detail button at the right hand side of the each data whose detail you want to
view.
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.
Press on the saving button at the left hand side of the main panel.
Press delete button to delete, activate to activate and deactivate to deactivate an account.
4. Loan
Press on the Loan button at the left hand side of the main panel.
Press Enter.
Press on the Loan button at the left hand side of the main panel.
You Could Delete, Activate, Deactivate, view detail and statement in this section.
Press on the Loan button at the left hand side of the main panel.
Select the Detail button at the right hand side of the each data whose detail you want to
view.
Press on the Loan 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.
Press on the loan button at the left hand side of the main panel.
Press delete button to delete, activate to activate and deactivate to deactivate an account.
5. Transaction:
Press on the transaction button at the left hand side of the main panel.
Press Enter.
Fig: Transaction
6. Website Control:
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.
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.
You can edit, delete, and deactivate the news and events you like.
Sundar Saving & Credit Co-Operative Ltd. 227
Online Co-Operative System 2010
Press on the web site button at the left hand side of the main panel.
Press delete button to delete, activate to activate and deactivate to deactivate an account.
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.
You can edit, delete, and deactivate the news and events you like.
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.
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.
Press respond button at the end of that feedback query you want to respond.
6.4 Career:
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.
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.
Editing/Deactivating/deleting:
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.
6.5 Schemes
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.
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.
Scheme panel will open which shows all the schemes records.
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.
Scheme panel will open which shows all the schemes records.
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.
Scheme panel will open which shows all the schemes records.
Select the edit button at the side of the record you want to edit.
7 .Sending mail:
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.
Fig: Inbox
E banking
1. Transferring Amount:
Press on the Amount Transfer button at the left hand side of the Customer main panel.
2. Sending Mail:
Press on the New Message button at the left hand side of the Customer main panel.
Press on the Account Summary button at the left hand side of the Customer main
panel.
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
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.
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