Banking System Project Proposal2

lOMoARcPSD|32529053
Banking System Project Proposal
Introduction to information systems (Mount Kenya University)
Studocu is not sponsored or endorsed by any college or university

Downloaded by kevin kimutai ([email protected])
lOMoARcPSD|32529053
DEDAN KIMATHI UNIVERSITY OF TECHNOLOGY
SCHOOL OF COMPUTER SCIENCE AND INFORMATION TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY
FINAL RESEARCH PRESENTATION FOR A DIPLOMA STUDENT IN INFORMATION

TECHNOLOGY
PRESENTED BY:
MARY GATHONI MWANGI
C132-01-0299/2022
PROJECT TITLE:
BANKING MANAGEMENT SYSTEM
SUPERVISOR:
MR.IRAD
Research proposal submitted to the department of information technology, school of computer science
and IT, Dedan Kimathi University of Technology in partial fulfillment of the award of a diploma in
Information Technology.
[DATE]

lOMoARcPSD|32529053
DECLARATION
I hereby declare that this project proposal titled “BANK MANAGEMENT SYSTEM” is my original
work, it has not been presented for a degree, diploma in any other university. I also declare that it has
no formed the basis for award of any other degree, diploma or any other similar titles.
STUDENT NAME: MARY GATHONI MWANGI
REGISTRATION NUMBER: C132-01-0299/2022
SIGNATURE: ……………………………
DATE: ………………………………………
SUPERVISOR’S NAME: MR.IRAD
SIGNATURE: …………………………………
DATE: ………………………………….

lOMoARcPSD|32529053
ACKNOWLEDGEMENT
Any attempt at any level cannot be satisfactorily completed without the support and guidance
of learned people. We would like to express our immense gratitude to Department Office of
Dedan Kimathi Campus for providing all the necessary resource and guideline that
encouraged us to come up with this report. Our special thanks go to our supervisor, Mr.Irad
who has been doing his best to solve all the problem we have faced during this entire project.
Special thanks also go to all our colleagues of our section who have rendered their whole
hearted support at all times for successful completion of this project directly as well as
indirectly by reviewing and suggesting the improvements.

lOMoARcPSD|32529053
Table of Contents
[DATE]..................................................................................................................................................1
DECLARATION...................................................................................................................................2
ACKNOWLEDGEMENT.....................................................................................................................3
Table of Contents...................................................................................................................................4
ABTSRACT..........................................................................................................................................9
CHAPTER 1: INTRODUCTION.......................................................................................................10
1.1 Background..........................................................................................................................11
1.2 Problem Statement.....................................................................................................................11
1.3 Objectives............................................................................................................................11
1.3.1 General Objective........................................................................................................11
1.3.2 Specific Objectives..........................................................................................................12
1.4 Gap Analysis........................................................................................................................13
1.5 Justification of the Study.....................................................................................................13
CHAPTER 2 : Literature Review........................................................................................................15
Introduction.................................................................................................................................15
CHAPTER 3: METHODOLOGY.......................................................................................................16
3.1 Introduction...............................................................................................................................16
3.2 Software development model.....................................................................................................16
3.4 Data Collection Methods...........................................................................................................18
The main objectives are;..............................................................................................................18
3.4.1 Interview.................................................................................................................................18
3.4.2 Observation.............................................................................................................................19
3.4.3 Questionnaires........................................................................................................................19
3.5 Target population and sampling technique.................................................................................20
3.6 Limitation of the study...............................................................................................................20
CHAPTER 4: SYSTEM ANALYSIS AND DESIGN......................................................................21
4.1 Analysis of the Existing System.................................................................................................21
THE FACTORS FOR THESE DIFFICULTIES ARE:.................................................................21
Labor-Intensive................................................................................................................................21
Human Error....................................................................................................................................21
Time Wasting...................................................................................................................................21
4.2 Description/Analysis of the New System...................................................................................23

lOMoARcPSD|32529053
The new system should possess the qualities stated below..............................................................23

QUALITIES OF THE NEW SYSTEM.......................................................................................23
1. Reduction in processing cost....................................................................................................23
2. Error reduction.........................................................................................................................23
3. Automatic calculation..............................................................................................................23
4. Improve reporting....................................................................................................................23
5. Automatic production of the documents and Reports..............................................................23
6. Faster response time.................................................................................................................23
7. Reduced dependency................................................................................................................23
8. Improves resource uses............................................................................................................23
9. Reduction in use of the paper...................................................................................................23
10. Reduction in Man Power......................................................................................................23
The system is a desktop Windows application. The system will provide the following Main
features:...........................................................................................................................................23
• Calculate the balance...............................................................................................................23
• Store account deposit and withdrawal information..................................................................24
• Store user details and other information...................................................................................24
• Print out reports as receipt. The System Can’t.........................................................................24
4.3 System Design...........................................................................................................................24
 Activity diagram......................................................................................................................24
 Use-case diagram.....................................................................................................................24
 Class diagram..........................................................................................................................24
 Sequence diagram....................................................................................................................24
 Dataflow diagram....................................................................................................................24
 Output design...........................................................................................................................24
 Input design.............................................................................................................................24
 Database design.......................................................................................................................24
 Data Flow diagram (DF Design)..............................................................................................24
 Context Flow Diagram.............................................................................................................24
4.4 Algorithm...................................................................................................................................24
3.2.1 For Creating Account..........................................................................................................24
3.2.2 For Withdraw/Deposit Account...........................................................................................25
3.2.3 For deleting an Account......................................................................................................25
4.5 SYSTEM DESIGN....................................................................................................................26
4.5.1 Architecture Diagram..........................................................................................................26
4.5.2. Domain Model...................................................................................................................27

lOMoARcPSD|32529053
4. 5.3. Entity Relationship Diagram with data dictionary............................................................28

4. 5.4. Class Diagram...................................................................................................................29
4. 5.5. Sequence / Collaboration Diagram...................................................................................30
4. 5.6. Operation contracts...........................................................................................................30
4. 5.7. Activity Diagram..............................................................................................................32
4. 5.8. State Transition Diagram..................................................................................................33
4. 5.9. Component Diagram.........................................................................................................34
4. 5.10. Deployment Diagram......................................................................................................34
4. 5.11. Data Flow diagram [only if structured approach is used - Level 0 and 1] No structural
approach is deployed...................................................................................................................35
4.5.12 Flowchart..........................................................................................................................36
CHAPTER 5: TESTING AND RESULTS..........................................................................................39
5.1 Introduction...............................................................................................................................39
5.7.1 Integration Testing..............................................................................................................39
5.7.2 Unit Testing........................................................................................................................39
5.7.3 System Testing....................................................................................................................39
5.7.4 Acceptance Testing.............................................................................................................39
5.7.5 Recovery Testing................................................................................................................39
5.7.6 Functional Testing...............................................................................................................39
5.7.7 Hardware/Software Testing.................................................................................................40
5.7.8 Security Testing..................................................................................................................40
5.8 TEST CASE...............................................................................................................................40
5.2.1 Test case 1:Dash board............................................................................................................40
5.2.2 Test case 2: Log in..................................................................................................................41
CHAPTER 6: SYSTEM IMPLEMENTATION AND DOCUMENTATION.......................................42
6.1 System Implementation.............................................................................................................42
6.2 Changeover Method...................................................................................................................42
6.3 Hardware Specification..............................................................................................................42
Hardware.....................................................................................................................................42
6.4 Software requirements...............................................................................................................43
6.5 Choice of Programing Language...............................................................................................44
6.6 System Documentation..............................................................................................................44
6.6.1 System Maintenance...........................................................................................................44
6.6.2 System Evaluation..............................................................................................................45
CHAPTER 7: SUMMARY, CONCLUSION AND RECOMMENDATION.......................................45
7.1 Summary...................................................................................................................................45

lOMoARcPSD|32529053
7.2 Conclusion.................................................................................................................................45
7.3 Recommendation.......................................................................................................................46
7.4 Problems Encountered...............................................................................................................46
7.5 Further Research........................................................................................................................46

lOMoARcPSD|32529053
ABTSRACT
As we are beginners and have no practical experience in the field of software development
and moreover the Banking System is very wide. So, we limit the scope of our project by
computerizing the following fields of the banking system: -

lOMoARcPSD|32529053
CHAPTER 1: INTRODUCTION
The “Bank Account Management System” project is a model Internet Banking Site. This site
enables the customers to perform the basic banking transactions by sitting at their office or at
homes through PC or laptop. The system provides the access to the customer to create an
account, deposit/withdraw the cash from his account, also to view reports of all accounts
present. The customers can access the banks website for viewing their Account details and
perform the transactions on account as per their requirements. With Internet Banking, the
brick-and-mortar structure of the traditional banking gets converted into a click and portal
model, thereby giving a concept of virtual banking a real shape. Thus, today's banking is no
longer confined to branches. E-banking facilitates banking transactions by customers round
the clock globally.
The primary aim of this “Bank Account Management System” is to provide an improved
design methodology, which envisages the future expansion, and modification, which is
necessary for a core sector like banking. This necessitates the design to be expandable and
modifiable and so a modular approach is used in developing the application software.
Anybody who is an Account holder in this bank can become a member of Bank Account
Management System. He has to fill a form with his personal details and Account Number.
Bank is the place where customers feel the sense of safety for their property. In the bank,
customers deposit and withdraw their money. Transaction of money also is a part where
customer takes shelter of the bank. Now to keep the belief and trust of customers, there is the
positive need for management of the bank, which can handle all this with comfort and ease.

lOMoARcPSD|32529053
Smooth and efficient management affects the satisfaction of the customers and staff
members, indirectly. And of course, it encourages management committee in taking some
needed decision for future enhancement of the bank. Now a day’s, managing a bank is
tedious job up to certain limit. So, software that reduces the work is essential. Also, today’s
world is a genuine computer world and is getting faster and faster day-by-day. Thus,
considering above necessities, the software for bank management has become necessary
which would be useful in managing the bank more efficiently. All transactions are carried out
online by transferring from accounts in the same Bank or international bank. The software is
meant to overcome the drawbacks of the manual system.
1.1 Background
Bank Account Management System keeps the day-by-day tally record as a complete banking system.
It can keep the information of Account type, account opening form, Deposit fund,
Withdrawal, and searching the transaction, Transaction reports, Individual account opening form,
Group Account. The existing part of this project is; it displays Transaction reports, Statistical
Summary of Account type and Interest Information.
1.2 Problem Statement

In the present context of Kenya the customer service is not effective because of lacking in
online banking system. Online banking system refers to the system that allows its users or its
customers to make online money transfer to keep track of their money, to deposit their cheque
online and so on. If the system is adopted by banks in Kenya then their users do not need to
wait in a line to deposit a cheque and then to keep track of their money. Online banking
syncing with the money application and then protect consumers online and pay their bills
online.
1.3Objectives
1.3.1 General Objective
The main aim of designing and developing this Internet banking System PHP primarily based
Engineering project is to provide secure and efficient net banking facilities to the banking customers
over the internet. Apache Server Pages, MYSQL database used to develop this bank application where

lOMoARcPSD|32529053
all banking customers can login through the secured web page by their account login id and password.
Users will have all options and features in that application like get money from western union, money
transfer to others, and send cash or money to inter banking as well as other banking customers by
simply adding them as payees.
1.3.2 Specific Objectives
I. Customer Satisfaction:
• Client can do his operations comfortably without any risk or losing of his
privacy.
• Our software will perform and fulfill all the tasks that any customer would desire.
II. Saving Customer Time:
• Client doesn't need to go to the bank to do small operation.
III. Protecting the Customer:
• It helps the customer to be satisfied and comfortable in his choices, this protection
contains customer’s account, money and his privacy.
IV. Transferring Money:
• Help client transferring money to/or another bank or country.
V. Protecting The Customer:
VI. Help client transferring money to/or another bank or country.
1.4 Gap Analysis

The criteria for selecting these banks were their deposit base. We have limited our Service Category to
the core services in Retail Banking and a few specialized services. The report is a mixture of

lOMoARcPSD|32529053
Secondary and Primary data, with Questionnaires being our major instrument to collect primary data.
Major topics we have attempted to cover in this project are to:
• Explore the services and products offered by the banks to individual customers.
• Understand the perception of the manage ment with respect to services offered by banks.
• Understand the perception of the customers with respect to services offered by banks.
1.5 Justification of the Study

The Traditional way of maintaining details of a user in a bank was to enter the details and record
them. Every time the user needs to perform some transactions he has to go to bank and perform the
necessary actions, which may not be so feasible all the time. It may be a hardhitting task for the users
and the bankers too. The project gives real life understanding of
Online Banking System and activities performed by various roles in the supply chain. Here, we
provide automation for banking system through Internet. Online Banking System project captures
activities performed by different roles in real life banking which provides enhanced techniques for
maintaining the required information up-to-date, which results in efficiency.
The project gives real life understanding of Online Banking System and activities performed by
various roles in the supply chain.
1.6

lOMoARcPSD|32529053

lOMoARcPSD|32529053
CHAPTER 2 : Literature Review
Introduction
Banking System is an online system which is developed in order to organize the person’s
account in a bank. The system provides the access to the customer to create an account,
deposit /withdraw the cash also view the records of accounts.
In past days, similar project has been already developed with similar features and platform.
For example, various reputed banks in Kenya are concurrently using similar type of system
allowing the people to enjoy the remote banking facility. This type of tasks has done already
and all are accurate and reliable, but need some modification. The techniques we will use be
similar to the techniques used by earlier investors with improvements. But the main
objectives of this project are to implement it on small scale banking branches which is not
providing this kind of facility. So, by allowing this facility the people would save lots of
efforts when needing to perform financial transactions and hope our project to be useful at
least in some manner.

lOMoARcPSD|32529053
CHAPTER 3: METHODOLOGY
3.1 Introduction
The methodology is an entire analysis made systematically and theoretically implemented in the field
of study. It contains the principles and objectives of the methodology related to the branch of that
knowledge. It encompasses ideas about various phases, paradigms, quantitative models, theoretical
studies, and qualitative methods. The concept of the methodology is not to give a solution to your
problems, instead of underpinning the steps considered as a solution is marked and processed to
calculate the correct result. So, this article explains about the different methodologies implemented for
solution analysis is briefly explained.
3.2 Software development model

In the development of the proposed software project, the prototyping model would be preferred
because it is build, tested, reworked until an acceptable proto type is achieved. It is an iterative, trial
and error method which takes place between developer and client
Figure 1: Protoyping Model
Figure 1.
The prototyping model is an iterative approach to software development that involves creating a series
of prototypes, or working models, of the software to be developed. This approach can be useful for
the development of a laundry management system for several reasons:

lOMoARcPSD|32529053
User involvement: The prototyping model encourages user involvement throughout the development
process. This means that the end-users of the laundry management system can provide feedback and
suggestions on the prototypes, helping to ensure that the final product meets their needs and
expectations.
Rapid development: The prototyping model allows for rapid development of the laundry
management system. Since each prototype is developed quickly and tested, the development team can
identify and address issues early in the process, before they become more difficult and costly to fix.
Flexibility: The prototyping model is a flexible approach to software development. The team can
adjust the design and functionality of the laundry management system as needed based on user
feedback and changing requirements.
Risk reduction: The prototyping model helps to reduce the risk of developing a laundry management
system that does not meet the needs of the end-users. By involving users early in the process and
testing each prototype, the team can identify issues and make changes before the final product is
released
Prototyping Model has following six SDLC phases as follow:
Step 1: Requirements gathering and analysis
In this phase, the requirements of the system are defined in detail. During the process, the users of the
system are interviewed to know what their expectation from the system is.
Step 2: Quick design
In this stage, a simple design of the system is created. However, it is not a complete design. It gives a
brief idea of the system to the user. The quick design helps in developing the prototype.
Step 3: Build a Prototype
In this phase, an actual prototype is designed based on the information gathered from quick design. It
is a small working model of the required system.
Step 4: Initial user evaluation
In this stage, the proposed system is presented to the client for an initial evaluation. It helps to find out
the strength and weakness of the working model. Comment and suggestion are collected from the
customer and provided to the developer.

lOMoARcPSD|32529053
Step 5: Refining prototype
If the user is not happy with the current prototype, you need to refine the prototype according to the
user’s feedback and suggestions.
This phase will not over until all the requirements specified by the user are met. Once the user is
satisfied with the developed prototype, a final system is developed based on the approved final
prototype.
Step 6: Implement Product and Maintain
Once the final system is developed based on the final prototype, it is thoroughly tested and deployed
to production. The system undergoes routine maintenance for minimizing downtime and prevent
large-scale failures.
3.4 Data Collection Methods

The system analyst uses different techniques to gather information on a system being studied. The
data collected is vital for the system development life cycle and system analysis stages.
The main objectives are;
 To collect information about the input of the present system.
 To find about the problems and weaknesses of the current system.
 To collect information about the input of the current system.
 To find what the present system is attempting to do, its scope and objectives.
3.4.1 Interview
This is a dialogue between two or more people where questions aimed at obtaining specific
information are asked and answered. Immediate feedback is obtained. Interviewing is important as
there are clarifications of comprehended questions and also gives room for observation of body
language. Interviewing is also considered reliable and efficient. I will interview the staff so as I get the
required information.
Some of the questions during interview were as follows:
Interviewer: What inspired you when you started working in the banking industry?

lOMoARcPSD|32529053
Bank manager: I started working in the banking industry because I wanted to help people manage
their banking accounts remotely and easily. I was inspired by the idea of helping people and making
their lives easier. I also thought it would be a great way to meet new people and learn new things
Interviewer: How have you developed your management style over the years?
Bank manager: My management style has evolved the years based on my experience and learning’s
from different situations. I would say that I am now more of a transformational leader, where I focus
on motivating and inspiring my team to achieve common goals.
Interviewer: How do you overcome obstacles and solve problems?
Bank manager: There are a few challenges that I have encountered while managing a banking
business.
• First challenge is finding reliable and affordable banking strategy.
• Secondly, keeping the banking data secure and organized.
• Thirdly, is dealing with customer complaints.
3.4.2 Observation
In this method the system analyst asks no questions from anyone but just observes how the
actions/objects are done. The analyst witnesses all the information that he/she may be looking for. The
method is very effective when combined with interview since it yields to more reliable information.
The objectives I will involve are;
o Sorting out files manually.
o Observing and recording the desired information only.
3.4.3 Questionnaires
A questionnaire allows the analyst to collect facts and figures from a large number of people thus
maintaining uniform responses. Questionnaires are relatively cheap thus simple and easy questions to
understand are set. I will prepare some questionnaires and send them out to the hospital for them to be
filled by the respondents and complex the questions on their own and collect them later:
i. Is the proposed system effective?

lOMoARcPSD|32529053
ii. If yes, give the reasons…………
iii. If no, give the reasons………….
iv. Are there problems facing the proposed system?
v. If yes, outline the problems…….
vi. If no, give the reasons why…….
vii. If there are problems, can they be solved?
viii. Can the system be improved?
3.5 Target population and sampling technique

The target population is the clients at the laundry, and the manager to ease the operation of the store.
The system will enable the store activities to be carried more efficiently and effectively and every
operation can be accounted for by the system example: the number of client, quantity of the services
supplied.
3.6 Limitation of the study

During the research, many problems occurred through the way for example I experienced bad
weathers i.e., rain. Also, during the filling of questionnaires some people gave wrong information.

lOMoARcPSD|32529053
CHAPTER 4: SYSTEM ANALYSIS AND DESIGN
4.1 Analysis of the Existing System
The current system operates manual laundry management system, from services, and
managing customer’s record etc. recorded in a book. This is faced with errors,
incompleteness, and insufficient data for analysis. Information regarding services of the
laundry is still in black and white which is not properly organized and managed. From the
staffs to customer bills, receipts of services are recorded in a book but further operations are
not being properly handled. As a result, it is difficult in processing, updating and managing.
THE FACTORS FOR THESE DIFFICULTIES ARE:
Labor-Intensive
A manual banking management system is that they can be highly labor-intensive to operate.
They require continuous monitoring to ensure that each transaction is accounted for and that
services are maintained at the appropriate module. It is also more difficult to share service
information throughout the business, because the lack of computerization makes accessing
service records a more cumbersome process. The time spent monitoring service application
could be used on more productive activities for the business.
Human Error
A manual laundry management system relies heavily on the actions of people, which
increases the possibility of human error. People might forget to record a transaction or simply
miscount the number of goods. This results in needless additional orders that increase the
company's inventory carrying costs and use up precious storage space. Inaccurate physical
counts could also result in not ordering enough of clothes, meaning the business could run out
of a crucial item at the wrong time.
Time Wasting

lOMoARcPSD|32529053
A manual laundry management system has a huge tendency of time wasting as the staff could
have a lot to tackle while many customers seek attention and this is really affecting the
business.

lOMoARcPSD|32529053
4.2 Description/Analysis of the New System
To reduce the shortcomings of the existing system there is a need to develop a new system
that could upgrade the status of the current system which is manual and slow to the system
that will be automatic and fast. The new system should be concern with offering the
requirements of the customer and the workers, the system should be reliable, easier, fast, and
more informative.
The new system should possess the qualities stated below.
QUALITIES OF THE NEW SYSTEM
1. Reduction in processing cost.
2. Error reduction.
3. Automatic calculation.
4. Improve reporting.
5. Automatic production of the documents and Reports.
6. Faster response time.
7. Reduced dependency.
8. Improves resource uses.
9. Reduction in use of the paper.
10. Reduction in Man Power.
The system is a desktop Windows application. The system will provide the following Main
features:
• Calculate the balance.

lOMoARcPSD|32529053
• Store account deposit and withdrawal information.
• Store user details and other information.
• Print out reports as receipt. The System Can’t
4.3 System Design
System Design is one of the tasking sections of the Programming. In this section of the
project many previews are going to be seen and we are gradually getting close to the new
system. System design is a transition from a user-oriented document to a document oriented
to programmers or database personnel. The system design is structured into the following
parts:
 Activity diagram
 Use-case diagram
 Class diagram
 Sequence diagram
 Dataflow diagram
 Output design
 Input design
 Database design
 Data Flow diagram (DF Design).
 Context Flow Diagram

lOMoARcPSD|32529053
4.4 Algorithm
3.2.1 For Creating Account
Step 1 : Start
Step 2 : Create a new account Form
Step 3 : Is form verifiable?
If YES goto Step 4

If NO goto Step 6.
Step 4 : Create the account and register it on database.
Step 5 : Show the message “Account Created”
Step 6 : Stop
3.2.2 For Withdraw/Deposit Account
Step 1 : Start
Step 2 : Select 1 for Withdraw and 2 for Deposit
Step 3 : If 1 is selected, then withdraw the amount after verification and goto
step 5.
Step 4 : If 2 is selected, then deposit it after verification and goto step 5.
Step 5 : Stop
3.2.3 For deleting an Account
Step 1 : Start
Step 2 : Admin Login
Step 3 : Select the Delete option
Step 4 : Provide necessary details for deletion

lOMoARcPSD|32529053
Step 5 : Remove the details from the database.
Step 6 : Show the message “Account deleted”
Step 7 : Stop
4.5 SYSTEM DESIGN
4.5.1 Architecture Diagram

lOMoARcPSD|32529053
4.5.2. Domain Model

lOMoARcPSD|32529053
4. 5.3. Entity Relationship Diagram with data dictionary

lOMoARcPSD|32529053
4. 5.4. Class Diagram

lOMoARcPSD|32529053
4. 5.5. Sequence / Collaboration Diagram
4. 5.6. Operation contracts
• Contractor to manage a range of activities.
• Generally short term, usually for two to five years.
• Traditionally been favored as transitional arrangements for

introducing the private sector into managing infrastructure but
longer term operation and maintenance agreements are becoming
more common in the water and energy sectors where more extensive
participation by the private sector through a lease, afterimage or
concession arrangement in these "essential services" is deemed to be
too politically sensitive or impractical.
• Commonly found in the water sector and, to a more limited extent,

energy sector.
• Limited potential for improvements in efficiency and performance

although more sophisticated management contracts (which are often
called operation and maintenance contracts) may introduce some
incentives for efficiency or improved bill collection, by defining
performance targets and basing a portion of the remuneration on
their fulfillment (and cover longer time periods).

lOMoARcPSD|32529053
• Operator is usually paid a fixed fee to cover its staff and expenses.
There may also be a performance based fee and liquidated damages
for failure to achieve performance parameters.
• Operator may be required to collect bills on behalf of the utility and

may accept some collection risk in terms of performance standards
but is unlikely to collect bills on its own behalf.
• Can be useful where condition of assets is uncertain where the

private sector would be unwilling to accept more extensive risk.

lOMoARcPSD|32529053
4. 5.7. Activity Diagram

lOMoARcPSD|32529053
4. 5.8. State Transition Diagram

lOMoARcPSD|32529053
4. 5.9. Component Diagram
4. 5.10. Deployment Diagram
4. 5.11. Data Flow diagram [only if structured approach is used - Level 0 and
1] No structural approach is deployed

lOMoARcPSD|32529053
4.5.12 Flowchart
Flowchart for creating account
New Account
User
New
Form
Verify
Rejected Create Account Data
base
Created

lOMoARcPSD|32529053
Flowchart for withdraw/deposit Account
User/Admin
Deposit
Withdraw
Withdraw
Bank Bank
Database
Verify
Database
Deposited
No Amount

lOMoARcPSD|32529053
Flowchart for deleting an account
Admin
Delete
Bank
Database
Account deleted

lOMoARcPSD|32529053
CHAPTER 5: TESTING AND RESULTS
5.1 Introduction
This laundry management system required the creation of a native website,php,HTML,CSS were used
to construct the native website.Inorder to administer the system’s database MYSQL was used.Testing
is done to demonstrate to the developer and customer that the software meets its requirement as well
as to discover faults and defects .
5.7.1 Integration Testing
Integration testing done before, during and after integration of a new module into the main software
package. This involves testing of each individual code module. One piece of software can contain
several modules which are often created by several different programmers. It is crucial to test each
modules effect on the entire program model. After integration testing the project works successfully.
5.7.2 Unit Testing
Unit testing performed on each module or block of code during development. Unit testing is normally
done by the programmer who writes the code.
5.7.3 System Testing
System testing done by a professional testing agent on the completed software product before it is
Introduced to the market.
5.7.4 Acceptance Testing
Acceptance testing is a beta testing of the product done by the actual end user.
5.7.5 Recovery Testing
Recovery testing is done to demonstrate a software salutation is reliable, trustworthy and can
successfully recoup form possible crashes.

lOMoARcPSD|32529053
5.7.6 Functional Testing
Functional Testing also known as functional completeness testing. Functional Testing involves trying
to think of any possible missing functions. Testers might make a list of additional functionalities that a
product could to improve it during functional testing.
5.7.7 Hardware/Software Testing
IBM refers to Hardware/Software testing as “HW/SW Testing”. This is when the tester focuses his/her
attention on the interactions between the hardware and software during system testing.
5.7.8 Security Testing
Security Testing is a variant of Software Testing which ensures, that system and applications in an
organization, are free from any loopholes that may cause a big loss. Security testing of any system is
about finding all possible loopholes and weaknesses of the system which might result into a loss of
information at the hands of the students or outsiders of the Organization.
5.8 TEST CASE

The test cases of the system are as below:
5.2.1 Test case 1:Dash board

Purpose: To test whether we can access the main dashboard interface of the website.
Prerequisites: To access our dashboard interface one is supposed to have an android mobile,a
computer and URL or the name of our website.
Procedure: Open the browser in your device and such the url or the name of the website and access
the first page of our interface.

lOMoARcPSD|32529053
Figure 1: Main dashboard page
5.2.2 Test case 2: Log in

Purpose:Log in enables the system to confirm the identity to the users and only approved user are able
to access the system dashboard interface through log in form
Prerequisite:To log in the dashboard the client must provide their identification password and email.
Procedure:Click the log in tab and provide the identification password in the space provided the click
sign in button to submit your details.
Results:Below is a screenshot after filling the details on space
Verdict:completely filled login form.

lOMoARcPSD|32529053
Figure 2: incompletely filled log in page.
I. Access the registration page:The client should input the system’s web address in a web
browser to view the registration page of the we-based laundry system
II. Fill out the registration form: The client should complete the registration form by providing
their name, location and other necessary data.
III. Submit the registration form: Once the client has filled out the registration form, they should
submit it to complete the registration process.
IV. Log in the system: Once the registration has been approved. The client should be able to log
in the web-based laundry system .

lOMoARcPSD|32529053
CHAPTER 6: SYSTEM IMPLEMENTATION AND

DOCUMENTATION
6.1 System Implementation

This chapter is the part that puts a planned system into action and examine in details the analysis and
design of the laundry management system. The present chapter discusses the implementation of the
system, highlighting the testing exercise and describing some of the main components of the system's
Graphical User Interface. It will give an output from programming language and other tools used to
develop our system. According to this plan, the activities are to be carried out, discussions made
regarding the equipment and resources and the additional equipment has to be acquired to implement
the new system.
6.2 Changeover Method

This section deals with the strategy used to change from the old system to the new system. There
are many methods available to swap from the old system to the new system these are direct
changeover, parallel operation, pilot operation and phased operation.
I prefer a parallel operation changeover method for this system change over because this kind of
method requires that both the old and the new information systems operate fully for a specified
period. Data is input to both systems and output generated by the new system is compared with the
equivalent output from the old system. When users, management, and IT group are satisfied that
the new system (LAUNDRY MANAGEMENT SYSTEM) operates correctly then the old system
should be terminated. It is the costliest changeover method but it involves lower risks.
6.3 Hardware Specification
Hardware
Computer or a laptop with the following specifications:
1. At least 2GB RAM (Giga Byte Random Access Memory)

This will allow for faster loading of the testing platforms.
2. 2.0 GHZ (Giga Hertz) processor speed

lOMoARcPSD|32529053
During the testing phase of the codes written, this will facilitate faster processing of the
requests by the application as well as speed up responses for the earlier given requests.
3. At least 20GB hard disk capacity
This is to provide the storage space for the application’s workspace where the various codes that
will be written will reside.
4. External Memory (External Hard disk) approximately 20GB
This is important in the project as it will enable for the process of backup for the purpose of
security in case of system crash
5. At least one NIC (network interface card) for connection purposes
6.4 Software requirements

The software requirements are as follows
1. MYSQL
We used MySQL server on the backend because it provides the ultimate in scalability, spoting the
capacity to handle deeply embedded applications with footprint of only 1 MB to running massive data
warehouses holding terabytes of information. It also offers exceptional security features that ensure
absolute data protection.
2. PHP
We used PHP because it is open source and because it can be used to build any kind of
website, right from the small, simple and personal blog to the large corporate blog.
3. Microsoft office
We used Microsoft office so as it aids in documenting our project and also for scheduling our
project by using Microsoft office project.
4. Operating system at least windows xp
This will form the platform that will be used by the system to run.
5. A computer antivirus

lOMoARcPSD|32529053
This is the software that will help shield the developed files against corruption due to malware and
viruses
6. yED graphical editor
This the software that we used during the design phase in drawing the usecases,activity diagram
,entity relationship diagram and others.
7. Apache
We used apache because it is free and it can run on pretty much any OS (linux,windows and Mac OS)
8. Xampp
Useful in hosting of the project.
6.5 Choice of Programing Language

In implementing the system, it uses php, html, cascading style sheet as the main programming
language and tools. This forms the front-end and the middleware.
At the back-end, MYSQL is used to maintain the information in the database. This is formed by the
databases and other data stores.
6.6 System Documentation
6.6.1 System Maintenance
The program may be maintained on the ground that the system requires an upgrade. When there is
a new field to be added or a new form to be added in other to serve users well. Though it is
compiled as a standalone software the database can be tempered with but it’s advisable that the
admin put a password on the file to secure the database from intrusion.
The following precaution should be done
• Ensure that the computer is kept in clean areas.
• System should be kept in cool places.
• Air conditioner is important to reduce room temperature and keep it constant.  Backup of
data is important

lOMoARcPSD|32529053
6.6.2 System Evaluation
This System is a high standard program that can weather the storm of technology advancement, it
is most needed in all Laundry and it is an antidote for business speed and transaction with record
keeping and maintenance, it will be very helpful to clients and customers in the marketing
business.
All it needs is a computer literate operative to make it work, it is stand alone and automated.
CHAPTER 7: SUMMARY, CONCLUSION AND

RECOMMENDATION
7.1 Summary
The laundry management system needs to be computerized to reduce human errors and increase the
efficiency. The proposed laundry management system in this project is computerized management
system developed to maintain all the daily work of laundry. Laundry management systems are
designed to store all information about customers and services offered. The focus of this project is to
lessen human efforts and encourage efficient record keeping.
7.2 Conclusion
In conclusion, Laundry Management System has to do with making appropriate effort to stop the
rising problem to all manual laundry operation in order to enhance the operation of such laundry. In
this project, the software or system that can be used to aid all laundries that is still operating manually
have been successfully developed. The software can be implementing in all types of laundry as
mentioned in the second chapter. The software has a large memory of storing all the services in the
laundries and also keeping record it is highly effective and accurate.

lOMoARcPSD|32529053
7.3 Recommendation
In the development of this laundry management system, I will recommend that if there is going to be
any modification the new writer should Endeavor to improve on the limitations such as changing the
graphical user interface of the system to further increase the system architecture and to satisfy users
need more for writing of the source code, Microsoft access for the database should be used and visual
basic for application for codes. There are some limitations during the development of this laundry
management system that will require improvement as stated in previous chapter writer should put
them in mind and face it as a challenge and not a problem.
7.4 Problems Encountered

A lot of challenges surfaced during the development of this incredible application though it tried
stopping this project but the doggedness and consistency of the writer was in match with the
challenge
The following are some of the problems or challenges encountered.
• Expensive internet facility.
• Understanding the M.S ADODC (Active X Data Object Data Control).
• Inadequacy of power supply and many more.
• Time factor on research to get a way of packaging the application successively.
7.5 Further Research

In the future, the mobile application of laundry management system will be developed and the
following components can be added to this current system in order to improve the effectiveness
and efficiency of the system, which includes:
1. An advanced password system that will be embedded into all login pages to increase the
security of the system.
2. A good internet backup should be automated after everyday services.
3. Internet Transactions should be allowed.

lOMoARcPSD|32529053
REFERENCES

Banking System Project Proposal2

Uploaded by

Copyright:

Available Formats

Banking System Project Proposal2

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Banking System Project Proposal2

Uploaded by

Copyright:

Available Formats

lOMoARcPSD|32529053

Banking System Project Proposal

Introduction to information systems (Mount Kenya University)

Studocu is not sponsored or endorsed by any college or university

DEDAN KIMATHI UNIVERSITY OF TECHNOLOGY

SCHOOL OF COMPUTER SCIENCE AND INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

FINAL RESEARCH PRESENTATION FOR A DIPLOMA STUDENT IN INFORMATION

MARY GATHONI MWANGI

BANKING MANAGEMENT SYSTEM

Downloaded by kevin kimutai ([email protected])

STUDENT NAME: MARY GATHONI MWANGI

REGISTRATION NUMBER: C132-01-0299/2022

SUPERVISOR’S NAME: MR.IRAD

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

The new system should possess the qualities stated below..............................................................23

Downloaded by kevin kimutai ([email protected])

4. 5.3. Entity Relationship Diagram with data dictionary............................................................28

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

1.2 Problem Statement

1.3.1 General Objective

Downloaded by kevin kimutai ([email protected])

1.3.2 Specific Objectives

II. Saving Customer Time:

• Client doesn't need to go to the bank to do small operation.

III. Protecting the Customer:

IV. Transferring Money:

• Help client transferring money to/or another bank or country.

V. Protecting The Customer:

VI. Help client transferring money to/or another bank or country.

1.4 Gap Analysis

Downloaded by kevin kimutai ([email protected])

1.5 Justification of the Study

Downloaded by kevin kimutai ([email protected])

Downloaded by kevin kimutai ([email protected])

CHAPTER 2 : Literature Review

Downloaded by kevin kimutai ([email protected])

3.2 Software development model

Figure 1: Protoyping Model

Downloaded by kevin kimutai ([email protected])

Prototyping Model has following six SDLC phases as follow:

Step 1: Requirements gathering and analysis

Step 2: Quick design

Step 3: Build a Prototype

Step 4: Initial user evaluation

Downloaded by kevin kimutai ([email protected])

Step 5: Refining prototype

Step 6: Implement Product and Maintain

3.4 Data Collection Methods

The main objectives are;

 To collect information about the input of the present system.

 To find about the problems and weaknesses of the current system.

 To collect information about the input of the current system.

Some of the questions during interview were as follows: