BANK AND ATM SIMULATION [Publish Date]

CHAPTER 4

4.1 TESTING APPROACH USED

T
4.2 TEST CASES

4.3 IMPLEMENTATION APPROACHES

 TESTING APPROACH USES

 Testing

Developed By Mallick Habib BCA Sem-6 of Batch 2023/24

BANK AND ATM SIMULATION [Publish Date]

➢ A test approach is a test strategy implementation of a project, defines how testing would be
carried.
➢ Without Testing any system doesn’t Have A feel of completeness. We Also Have to Apply
Some Sort of Testing to Our Project. Testing Is Integral Part of Any System or Project.

❖ Objectives of testing:
o The main purpose of the testing and information system is to find the Errors and
correct them. A successful test is one finds errors.
o To ensure that during the operation the System Will Perform as Per
Specification.
o To Make Sure That the System Meet Use’s Requirement During Operation.
o To Verify That the Control Incorporated in The System Function is Intended.
o To See That the When Correct Input Are Fed to The System, The Output Are
Correct.
o To Make sure That During Operations, Incorrect Inputs, Processing and Outputs
Will Be Detected.
o Testing Is the Process of Executing A Program of Intent with Of Finding Errors.
o A Good Test Case Is. One of Has A High" Probability of Finding an
Undiscovered Error.
o A Successful Test Is One That Uncovers A Discovered Error.
o To Ensure Customer Satisfaction, Enhance Business and Set A Good Reputation
for the software developer.
o There Are Two Types of Technique to Test The system which are mainly black
box testing and white box testing

1. Black Box Testing: -

o Black box testing is a technique that ignores internal mechanism of the system
and focus in input and output.
o It is also called functional testing because the tester is only concern with
functionality of the system.
o Black box testing performs without planning and documentation.
o The above black-box can be any software system you want to test.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 2

BANK AND ATM SIMULATION [Publish Date]

o For example, an operating system like windows, a website like google, a

database like oracle or even your own custom application.
o Under black box testing, you can test these applications by just focusing on the
inputs and outputs without knowing their internal code implementation.

2. White Box Testing: -

o White box testing is a testing technique that focuses on internal mechanism of
the system.
o In white box testing, code is visible to testers, so it also called clear box testing,
open box testing, transparent box testing, code-based testing, and glass box
testing.
o White box testing is a testing of internal working of code of software application.
o White box testing is the detailed investigation of internal logic and structure of
the code.
o In order to perform white box testing of an application, the tester needs to process
knowledge of the internal working of the code.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 3

BANK AND ATM SIMULATION [Publish Date]

3. Grey Box Testing: -

o Grey box testing is a combination of black box and white box testing.
o The aim of this testing is to search for the defects if any due to improper usage of
application.
o Grey box testing is also knowns as translucent testing.
o Grey box testing is a software are commonly identified. It increases the testing
coverage by concentrating on all of layers of any complex system.
o Gray box testing is a software testing method, which is a combination of both
white box testing and black box testing method.
 In white box testing internal structure (CODE) is known.
 In black box testing internal structure (CODE) is unknown.
 In grey box testing internal structure (CODE) is partially
known.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 4

BANK AND ATM SIMULATION [Publish Date]

4.Performance Testing: -
o Performance testing is a type of testing to ensure software application with
performs under user specification.
o Performance testing is a non-functional software testing technique that determines
how the stability, speed, scalability, and responsiveness of a website.
o The goals of performance testing include evaluating website output, processing
speed, data transfer velocity, network bandwidth usage, and command response
times.

5. GUI Testing: -

o GUI Stands for Graphical User Interface.

o These test GUI characteristics like text, formatting, textbox, buttons, layouts,
colours, fonts.
o GUI testing is a software testing type that checks the graphical user interface of
the software.

6. Usability Testing: -

o Usability testing refers to evaluating a product or service by testing it with

representative.
o Usability testing lets the design and development teams identify problems before they
are resolved.

7. Procedure Testing: -
Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 5
BANK AND ATM SIMULATION [Publish Date]

o Procedure testing shall model the procedural requirements of the software system as a
complete and delivered unit.
o Procedure requirements shall define what is expected of any procedural
documentation and shall be written in the form of procedural instructions.

4.2 TEST CASE

► What are test cases?

o A TEST CASE is a set of conditions or variables under which a tester will

determine whether a system under test satisfies requirements or works correctly.
o The process of developing test cases can also help find problems in the
requirements or design of application.

 Object Oriented Testing: -

o Object oriented testing is strategically similar to the testing of conventional

systems, but it is tactically different. Because the Object-Oriented analysis and
design models are similar in structure and content to the resulting Object-Oriented
program, “testing” begins with the review of models.
o Once code has been generated, Object Oriented testing begins “in the small” with
class testing. A series of tests are designed to exercise class operations and examine
whether errors exist as one class collaborates with other classes.
o As classes are integrated to form a subsystem, thread-based, use-based and cluster
testing, along with fault-based approaches are applied to fully exercise collaborating
classes.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 6

BANK AND ATM SIMULATION [Publish Date]

o Strategy is a general approach rather than a method of devising particular systems

for component tests.
o Different Strategies may be adopted depending on the type of system to be tested
and the development process used testing strategies are:

1. Top-Down Testing
2. Bottom-Up Testing
3. Thread Testing
4. Stress Testing
5. Back-to-Back Testing

1. Top-Down Testing: -
 This testing starts with the most abstract component and works downwards.
2. Bottom-Up Testing: -
 This testing starts with the fundamental components and works upwards.
3. Thread Testing: -
 This is used for systems with multiple processes where the processing of a
transaction threads its way through these processes.
4. Stress Testing: -
 In documentation learning, requires whole project information, feasibility
requirements, and about current system.
5. Back-to Back Testing: -
 This is used when versions of a system are available. The systems are tested together
and their outputs are compared.
6. Performance Testing: -
 This is used to test the run-time performance of software.
7. Security Testing: -
 This attempt to verify that the protection mechanism built into the system will protect
it from improper penetration.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 7

BANK AND ATM SIMULATION [Publish Date]

8. Recovery Testing: -
 This forces software to fail in a variety of ways and verifies that recovery is property
performed.

4.3 IMPLEMENTATION APPROACHES

 Implementation can be defined as putting into effect.

 System implementation is the delivery of the system into production. It is important
to understand that this topic is not about building or programming a system, but
rather making system live.
 There are a variety of options that a project manager could consider when
implementing a solution.
 There are advantages and disadvantages to each type, and the choice usually depends
on the client organizational setup and the complexity of the solution to be
implemented.
 The implementation phase is where you and your project team actually do the project
work to produce the deliverables.
 The word “deliverable” means anything your project delivers. The deliverables for
your project include all of the products or services that you and your team are
performing for the client, customer, or sponsor, including all the project management
documents that you put together. These implementation choices available to a project
manager are:

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 8

BANK AND ATM SIMULATION [Publish Date]

 Parallel
 Phases
 Waterfall Model
 Spiral Mode
❖ Parallel: -
o A parallel implementation or approach implies that a new solution is implemented
parallel to the current operating system in use. Those who are using the system
will not see major downtime once it is implemented. The trick here is to
implement the system.
o Parallel approach to implementation allows the old and the new systems to run
concurrently for a time. At some point, organization switches entirely from the
old system to the new.
o The parallel approach is appropriate when problems or the failure of the system
can have a major impact on the organization.
o For example, an organization may be implementing a new account receivable
package. Before switching over completely to the new system, the organization
may run both the systems concurrently in order to compare the outputs of both the
systems.
o This approach provides confidence that the new system is functioning and
performing properly before relying on it entirely.

❖ Phases: -

o The phase approach works well because (1) there is minimal disruption to the client's
operation, and (2) problems are resolved quickly. The phased approach could also be
used if there is more than one department. The project manager could decide that
implementing the solution in one department at a time could be more reliable than
trying to roll out all departments at the same time.
o In the phased approach the system is introduced in modules or in different parts of
the organization incrementally. Different areas of organization.
o A phased approach may also allow the project team to learn from its experiences
during the initial implementation so that later implementations run smoothly.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 9

BANK AND ATM SIMULATION [Publish Date]

o Although a phased approach may take more time, it is less risky and much more
manageable.
o For example, an organization may implement an accounting information system
package by first implementing the general ledger component, then accounts payable
and accounts receivable, and finally, payroll.

❖ Waterfall Model: -

o The waterfall model is a sequential design process in which progress is seen as

flowing steadily downwards (like a waterfall) through the phases of Conception,
Initiation, Analysis, Design, Construction, Testing, Production/Implementation, and
Maintenance.
o Waterfall approach was the first SDLC Model to be used widely in Software
Engineering to ensure success of the project. In "The Waterfall" approach, the whole
process of software development is divided into separate phases. In this Waterfall
model, typically, the outcome of one phase acts as the input for the next phase
sequentially.
o The waterfall Model illustrates the software development process in a linear
sequential flow. This means that any phase in the development process begins only if
the previous phase is complete. In this waterfall model, the phases do not overlap.
o The advantages of waterfall development are that it allows for departmentalization
and control. A schedule can be set with deadlines for each stage of development and a
product can proceed through the development process model phases one by one.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 10

BANK AND ATM SIMULATION [Publish Date]

❖ Spiral Model: -
o The spiral model is a risk-driven software development process model. Based on
the unique risk patterns of a given project, the spiral model guides a team to
adopt elements of one or more process models, such as incremental, waterfall,
or evolutionary prototyping.
o Spiral Model is a combination of a waterfall model and iterative model. Each
phase in the spiral model begins with a design goal and ends with the client
reviewing the progress.
o The spiral model is another important SDLC model that came into use when the
iteration in product development came into the applied concept. The initial
phase of the Spiral model is the early stages of the Waterfall Life Cycle that are
needed to develop a software product. This model supports risk handling, and

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 11

BANK AND ATM SIMULATION [Publish Date]

the project is delivered in loops. Each loop in the Spiral model is the phase of the
software development process.

CHAPTER 5

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 12

 5.1 CONCLUSION
BANK AND ATM SIMULATION [Publish Date]

5.1 CONCLUSION
 Bank management system is a virtualization of transactions in banking system. The
banking system are used manual working but when we used online banking system it is
totally virtualization process which avoid manual process and converts it in automatic
process.
 If user can make a transaction in bank management system it is available in anywhere
also user can link Aadhaar with account, change branch location easily.
 Bank management system is saving the time with accuracy than bank manual system.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 13

 BANK AND ATM SIMULATION [Publish Date]

 The Loan system is important and helps to ensure success or failure of any credit
institution.
 Mortgage loan problems have always been a key note on the risk of loan loss. The scope
of this project is to provide good communication and communication between the
customer and the manager.
 The current system can be a user-friendly system, which does not store data in the proper
security and can easily track information and contains the operation of fast-recovery
information, such as customer data, all loan details and includes many documents.
 The scope of this project is to use the loan in a very smart way.
 The new computerized system will minimize errors while providing more control over
the system and more robust management information in the form of implementation
strategies.
 The new system was monitored to ensure that there was no error in the systems, so the
program results met the export target financial target. to enhance the effective
management of consumers, the system must also be developed to support other bidding
loan details.
 An ATM is a powerful tool to manage cash flow and transactions.
 By providing real time monitoring cash management and maintenance features the system
can help save money enhance security and improve customer security.
 As technology continues to evolves. ATM will become more sophisticated and play an
increasingly important role in banking system

5.2 LIMITATION OF THE SYSTEM

 Core-JAVA, being a server-side scripting language, may not be as efficient for
handling large-scale real-time communication. As the number of users increases, the
performance of the application may degrade.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 14

BANK AND ATM SIMULATION [Publish Date]

 Banking apps in JAVA applications can be vulnerable to various security threats such
as SQL injection, cross-site scripting (XSS), and session hijacking if not properly
secured. Ensuring robust security measures is crucial for protecting user data and
preventing unauthorized access.
 These applications may require frequent updates and maintenance to keep up with the
evolving web standards, security patches, and compatibility with newer versions of
JAVA and related libraries.
 Developing complex features in JAVA for real-time communication might have a
steeper learning curve compared to using other languages or frameworks more
specialized in this area. This could potentially increase development time and costs.
 JAVA applications may have dependencies on specific web server configurations,
JAVA versions, or extensions, which could limit their portability across different
hosting environments.
 Implementing advanced features like push notifications, file sharing, or multimedia
messaging may require additional libraries or modules in JAVA, which could add
complexity to the application.
 The bank management system currently only supports desktop platforms like PC or
Laptops.
 Also, it does not include insurance section in it.
 The user can update his/her city, address, pincode etc. and can’t update or change
bank account type or services provided by the bank.
 Money can’t be transferred through ATM, so the user has to compulsorily open the
application.

5.3 FUTURE SCOPE OF THE SYSTEM

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 15

BANK AND ATM SIMULATION [Publish Date]

► The following parts will be included in the future scope of the system:

 My first priority will be to develop an android based application for this same
concept. Mobile banking will continue to be a focal point for bank management
systems, with an emphasis on enhancing functionalities, security, and user
experience. Features such as mobile payments, digital wallets, and biometric
authentication will become more prevalent, catering to the increasing demand for
convenient and secure banking services on-the-go.
 Also, I will add a special section of insurance in it, which will allow the user to check
and confirm different types of insurance with calculation facilities.
 My next priority will be to add a special section of scholarship’s given to students.
The main aim of adding a scholarship section is to propagate awareness between
people who are not regularly not informed or have no knowledge regarding their or
their children’s future.
 At last remaining work is to be done on ATM as it still only has the basic the
functionalities of an ATM.
 Money transferring from the ATM itself will be possible in the future scope.
 Also, those users who are not registered member of the Banking Application will
have the access of ATM without any username or pin or account number, to transfer
money which will be called EASY TRANSFER.

5.4 BIBLIOGRAPHY AND WEBLIOGRAPHY

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 16

BANK AND ATM SIMULATION [Publish Date]

 Bibliography, as a discipline, is traditionally the academic study of books as

physical, cultural objects; in this sense, it is also known as bibliology.
 English author and bibliographer John Carter describes bibliography as a word
having two senses: one, a list of books for further study or of works consulted by an
author (or enumerative bibliography); the other one, applicable for collectors, is "the
study of books as physical objects" and "the systematic description of books as
objects" (or descriptive bibliography)
 For this I have taken the references of these books
 JAVA CONCURRENCY
AUTHOR: BRIAN GOETZ

 JAVA DEVELOPER

AUTHOR: MARTIN VERBURG

 The term Webliography is commonly used when discussing online resources. It is

referred to as “Web bibliography”.

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 17

BANK AND ATM SIMULATION [Publish Date]

 Accordingly, a Webliography is a list of resources relating to a particular topic that

can be accessed on the World Wide Web, and can be referred to in a scholarly work.
 ONLINE REFERENCE WEBSITE:
o https://www.wikipedia.org/
o https://openai.com/
o https://www.lucidchart.com/pages/
o https://github.com/
o https://www.youtube.com
o https://www.google.co.in
o https://looka.com

Developed by Mallick Habib TYBCA SEM-6 BATCH 2023-24 Page | 18