A project report on Bank Application (Salesforce Administrator and App Building).

1. 1
ABSTRACT
The new way of building and running applications are enabled by the world of cloud
computing, where we can access applications, over the Internet as utilities, rather than as
pieces of software running on our desktop or in the server room. This model is already quite
common for consumer apps and for certain business applications, like Customer Relationship
Management (CRM). This Bank Application has been designed on Force.com platform which
is a PaaS (Platform-as-a-Service) product for Salesforce.com. Salesforce is a global web-
based application and cloud computing company best known for its customer relationship
management product. It is a customer success platform, designed to help users sell, service,
market and analyze, and connect with their customers. PaaS is an environment where users
can build, compile and run applications without worrying about underlying infrastructure.
This application is build with an administrative‟s perspective where he can maintain all the
services of a bank. Different type of accounts can be created, transactions like withdraw and
deposit can be managed. The user interface of the application can be modified by
administrator only. Every application requires strong security and this app provides proper
data security. Not only this, the tasks can be automated as well. An administrator can even
create some restrictions for its employees. The administrator and employees can create
accounts for users and manage them by sending information regarding their accounts. They
can be provided by different type of loans also. Bank app stores data information in one place
with the help of Reports and Dashboards. One of the major benefits of this app is that it can be
accessed from anywhere, one need not to be present at a single place as it is based on cloud.
An admin or employee can just download an app called Salesforce1 in mobiles and they are
ready to go.

2. TABLE OF CONTENT
Certificate i
Acknowledgement ii
Candidate‟s Declaration iii
Abstract iv
Table of Content v-vi
List of Abbreviations vii
List of Figures viii
List of Tables ix
SRS x
Chapter 1: Introduction 1
1.1 Purpose 1
1.3 About The Technology 3
1.3.1 Key Technologies behind Force.com 4-6
Chapter 2 : Literature Survey 7
2.1 Objective 7
2.2 Project Modules 7-8
2.3 Benefits of Bank App 8-9
Disadvantages of Existing Bank App 9
Chapter 3 : Feasibility Analysis 10
3.1 Introduction 10
3.1.1 Technical Feasibility 10
3.1.2 Economic Feasibility 11
3.1.3 Operational Feasibility 11
3.1.4 Legal Feasibility 11
3.1.5 Scheduling Feasibility 12
Chapter 4 : Requirement Analysis 13
4.1 Introduction 13
4.1.1 User Requirements 13
4.1.2 Hardware Requirements 13
4.1.3 Software Requirements 13
4.1.4 Functional Requirements 14
4.1.5 Performance Requirements 14
4.1.6 Safety Requirements 14
4.1.7 Security Requirements 14
4.2 Reliability Requirements 14-15
Chapter 5 : System Analysis and Design 16
5.1 Module Description 16-18
5.2 System Designing 18
5.2.1 E-R Diagram 18
5.2.2 Data Flow Diagram 19

3. 5.2.3 Class Diagram 20
5.2.4 Use Case Diagram 20
5.2.5 Sequence Diagram 21
5.2.5 Sequence Diagram 21
5.2.6 Activity Diagram 22
Chapter 6 : Coding 23
6.1 Validation Rules 23
6.2 Formula Fields 24
Chapter 7 : Project Snapshots 25
7.1 Login Page 25
7.2 Home Page 26
7.3 Tab Description 27-28
7.4 Report 29-30
7.5 Automated Email 31
7.6 Logout Screen 31
Chapter 8 : Testing and Maintenance 32
8.1 Types of Testing 32-33
8.2 Test Cases 33-34
8.3 Deployment and Maintenance 35
Conclusion 36
1. Summary 36
2. Future Scope 36
References 37

4. LIST OF ABBREVATIONS
S.No. Abbreviations Description
1. APP Application
2. UI User Interface
3. API Application Programming Interface
4. SAAS Software-as-a-Service
5. PAAS Platform-as-a-Service
6. ERD Entity Relationship Diagram
7. DFD Data Flow Diagram
8. IT Information Technology
9. OS Operating System
10. RAM Random Access Memory
11. GB Giga Byte
12. MB Mega Byte

5. LIST OF FIGURES
S.No. Figure Description Page No.
1 1.1 Company Logo 2
2 1.2 Salesforce Logo 3
3 1.3 Salesforce Architecture 6
4 5.2.1 E-R Diagram 18
5 5.2.2 Level 0 DFD 19
6 5.2.3 Level 1 DFD 19
7 5.2.4 Class Diagram 20
8 5.2.5 Use Case Diagram 20
9 5.2.6 Sequence Diagram 21
10 5.2.7 Activity Diagram 22
11 7.1 Login Page of Salesforce 25
12 7.2 Home Page 26
13 7.3.1 New Bank 27
14 7.3.2 New Branch 27
15 7.3.3 New Accounts Information 28
16 7.3.4 New Loan Details 29
17 7.4 Report of Transactions per week 29
18 7.5 Dashboard of Transaction per week 30
19 7.6 Automated email generation on account creation 30
20 7.7 Logout Interface 31

6. LIST OF TABLES
S.No. Table Description Page No.
1. Table 8.2 Test Cases 34

7. 1
Bank Application
Software Requirement Specification
Chapter-1
Introduction
1.1 PURPOSE
Building a bank application in Salesforce to make automation process easier. This
application is build with an administrative‟s perspective where he can maintain all the
services of a bank. Different type of accounts can be created, transactions like withdraw
and deposit can be managed. The user interface of the application can be modified by
administrator only.
Every application requires strong security and this app provides proper data security. Not
only this, the tasks can be automated as well. An administrator can even create some
restrictions for its employees. The administrator and employees can create accounts for
users and manage them by sending information regarding their accounts. They can be
provided by different type of loans also. Bank app stores data information in one place
with the help of Reports and Dashboard.
.
1.2 OVERVIEW
This application is developed in Salesforce Administration and App building. Salesforce
is a web-based application and cloud computing company, best known for its customer
relationship management(CRM) product. Salesforce specializes in software-as-a-service
(SaaS) to help users handle all of their business needs.
Salesforce is a customer success platform, designed to help users sell, service, market,
analyze and connect with their customers.
Salesforce has everything required to run a business from anywhere. Using standard
products and features, users can manage relationship with customers, collaborate and
engage with employees and partners, and store their data securely in the cloud.

8. 2
Bank Application
Fig 1.2 Salesforce Logo
But standard products and features are only the beginning. This platform allows to
customize and personalize the experience for customers, partners, and employees and
easily extend beyond out of the box functionality. It is suite of CRM products that work
together to make todays corporations function more efficiently and profitably. They touch
many functional areas in the company.
1.3 ABOUT THE TECHNOLOGY
The technology used in designing this application is Force.com, which is a platform for
Salesforce. Force.com is a Platform-as-a-Service (Paas) product designed to simplify the
development and deployment of cloud based applications and websites.
Developers can create apps and websites through the cloud IDE and deploy them quickly
to Force.com multi-tenant servers.
It is used to create and deploy next generation cloud apps because there and no servers or
software to buy or manage. Developers can solely focus on building apps that include
builtin features like social and mobile functionality, business processes, reporting and
search.
Apps run on a secure, proven service that scales, tunes and backups data automatically.
1.3.1 KEY TECHNOLOGIES BEHING FORCE.COM
1. Multi-tenant Architecture:
An application model in which all users and apps share a single, common
infrastructure and code base. Consequently, no one has to worry about buying and

9. 3
Bank Application
maintaining their own physical stack of hardware and software or making sure that
their applications always have the latest patch installed.
Besides the Force.com platform, several popular, consumer-based applications also
use a multitenant architecture, including eBay, MyYahoo!, and Google Gmail.
Multitenant architecture allows these applications to be low-cost, quick to deploys,
and open to rapid innovation-exactly the qualities for which Salesforce has also
become known.
2. Metadata-driven Development Model:
An app development model that allows apps to be defined as declarative
“blueprints”, with no code required. Data models, objects, forms, workflows and
more are defined by metadata. The Force.com platform uses a metadata-driven
development model to help app developers become more productive in putting
together apps. It means that the basic functionality of an app-that is, the tabs, forms
and links-are defined as metadata in a database rather than being hard coded in a
programming language. When a user accesses an app through the force.com
platform, it renders the app‟s metadata into the interface the user experiences.
Anyone who is familiar with using a web browser can quickly get up to speed,
even if he or she doesn‟t know any programming languages.
3. API Access:
Several application programming interfaces(APIs) provide direct access to all data
stored in force.com from virtually any programming language and platform.
Sometimes app developers want to modify the actual data in an app and use third
party services to create more customized app behaviors. To do this, they can use a
number of APIs to integrate with the platform. The core set of APIs include
Force.com SOAP API and REST API, the Bulk API, Streaming API, and metadata
API. You can call these APIs from a wide variety of client-side languages – and
toolkits are also available to ease the integration.

10. 4
Bank Application
4. Mobile Access:
With Salesforce mobile apps, you can access custom apps built using the
force.com platform point-and-click development tools. Users can access those apps
on their mobile devices and you don‟t have to learn any mobile programming
languages.
Downloadable versions of these apps install on mobile devices and use them native
functionality of the device. When users log in on a mobile device, they can access
and update their data via an interface specially designed for mobile device screens.
Both apps allow you to work with most standard Sales objects, some standard
service object, and all custom objects.
5. AppExchange Directory:
A web directory where hundreds of Force.com apps are available to Salesforce
customers to review, demo, comment upon, and/or install. Developers can submit
their apps for listing on the AppExchange Directory if they want to share them
with the community. The AppExchange is a Web directory where apps built on the
Force.com platform are available to Salesforce customers to browse, demo, review,
and install.
Developers can submit their apps for listing on the AppExchange directory if they
want to share them with the community. AppExchange contains hundreds of
innovative and exciting apps that exist today, including everything from payroll
management to telephony integration, service and support surveys, adoption
dashboards, and beyond. Some of these apps have been created inhouse at
Salesforce, but most are built by partners and individual developers who have
chosen to take advantage of the Force.com platform.

11. 5
Bank Application
Fig. 1.3 Salesforce Architecture

12. 6
Bank Application
Chapter-2
Literature Survey
In this chapter, we will see the literature review about this topic and related work, objective
also described. In this section, brief introduction of literature survey or literature review of
“Bank Application” is provided.
A literature survey means that anyone can read and report on what the literature in the field
has to say about any topic or subject. There may be a lot of literature in the field to say about
any topic or subject.
2.1 OBJECTIVE
To develop a Bank Application that helps in making the banking process easier by
automating all the process. This application is build with an administrative‟s perspective
where he can maintain all the services of a bank. Different type of accounts can be
created, transactions like withdraw and deposit can be managed. The user interface of the
application can be modified by administrator only.
2.2 PROJECT MODULES
Bank application contains 5 modules:
1) Data Modeling Module
2) UI Customization Module
3) Data Security Module
4) Approval Process Assignment Module
5) Reports and Dashboards Module
 DATA MODELING MODULE

13. 7
Bank Application
This is the first module in which an app in Salesforce simulates the functionalities
of a bank. It stores the data of bank, loan, account, loan details and transaction.
 UI CUSTOMIZATION MODULE
In this module, the interface for bank application can be modified. This module
gives the details of the item that is being selected by the user.
 DATA SECURITY MODULE
In this module, the application deals with security and sharing setting of data and
visibility between users or group of users across organization. Force.com platform
provides a flexible, layered, sharing model that makes it easy to assign different
data set to different users.
 APPROVAL PROCESS ASSIGNMENT MODULE
A text email template is provided when the account is created and a description of
total balance in account is sent.
 REPORTS AND DASHBOARDS MODULE
In this module, report and dashboard is provided. Report is a list of records that
meet particular criteria which gives answer to a particular question.
Dashboards are graphical representation of reports.
2.3 BENEFITS OF BANK APP
1. EFFICIENT WORKING:
Bank App works very efficiently and provides prompt service to its customers.
2. QUICK DECISIONS:

14. 8
Bank Application
It is used to meet the financial requirements of all the people promptly and
efficiently.
3. LESS IRREGULARITIES:
There are fewer chances of fraud and irregularities under this app because of the
close supervision and control of the management.
4. PREVENTION OF MONOPOLY:
This app helps in prevention of monopoly banking.
2.4 DISADVANTAGES OF EXISTING BANK APP
1. Manager has to seek permission from the head office on each and every matter,
these results in unnecessary delay and red- tapism in the banking business.
2. Managers generally lack initiative on all-important matters; they cannot take
independent decisions and have to wait for.
3. Less customer contact and so it is harder to build personal relationships with
customers.
4. Banks have to employ specialist web developers and expensive computers to run
the site.
5. If the website goes down then customers cannot access their accounts.

15. 9
Bank Application
Chapter 3
Feasibility Analysis
3.1 INTRODUCTION
A feasibility study is an analysis and evaluation of a proposed project to determine if it is
1. Technically feasible
2. Feasible with the estimated cost
3. Will be profitable
A feasibility study determines the actual steps required to build the project in order to
achieve success.
There are different types of feasibility done in the development of the project:
 Technical Feasibility
 Economic Feasibility
 Operational Feasibility
 Legal Feasibility
 Scheduling Feasibility
3.1.1 TECHNICAL FEASIBILITY
 Technical Feasibility focuses on the technical resources available to
the organization.
 It helps organizations determine whether the technical resources meet
capacity and whether the technical team is capable of converting the
ideas into working systems.
 Technical feasibility also involves evaluation of the hardware,
software, and other technology requirements of the proposed system.
 Technical feasibility is concerned with specifying equipment and
software that will meet the equipment and goals.
 The project should be developed such that the necessary functions and
performance are achieved within the constraints.
 The project is developed within latest technology.

16. 10
Bank Application
This project is developed on Force.com platform and it is technically feasible
for the development.
3.1.2 ECONOMIC FEASIBLITY
 This assessment typically involves a cost/benefits analysis of the
project, helping organizations determine the viability, cost, and
benefits associated with a project before financial resources are
allocated.
 It also serves as an independent project assessment and enhances
project credibility – helping decision makers determine the positive
economic benefits to the organization that the proposed project will
provide.
 Number of persons involved will be reduced.
 The maintenance cost is low.
 Financial benefits must equal or exceed the development cost.
The project is economically feasible and will give earning to the development
organization as it bears less development cost.
3.1.3 OPERATIONAL FEASIBILITY
 This assessment involves undertaking a study to analyze and determine
whether – and how well – the organization‟s needs can be met by
completing the project.
 Operational feasibility studies also analyze how a project plan satisfies
the requirements identified in the requirements analysis phase of
system development.
 In the proposed system, manpower and time is reduced.
 The project should work properly after it is being developed and
implemented.
3.1.4 LEGAL FEASIBILITY
 This assessment investigates whether any aspect of the proposed project
conflicts with legal requirements like zoning laws, data protection acts,
or social media laws.

17. 11
Bank Application
3.1.5 SCHEDULING FEASIBILITY
 This assessment is the most important for project success; after all, a
project will fail if not completed on time.
 In scheduling feasibility, an organization estimates how much time the
project will take to complete.

18. 12
Bank Application
Chapter-4
Requirement Analysis
4.1 INTRODUCTION
For the successful development of any project, it is very necessary to study about
all the requirements of the project. These requirements may be related to resource,
hardware, software, functionalities etc.
This requirement analysis is an important as the implementation of the project.
The requirement analysis basically emphasizes on the listing of the necessary
requirements required for the development of the project.
Bank Application is a cloud based application it only requires a browser and an
Internet connection to run the application on cloud.
4.1.1 USER REQUIREMENTS
 A high-speed Internet Connection is needed as an interface between the
service provider and User.
 User name and Password provided by the administrator is needed to the
user to work with the application.
4.1.2 HARDWARE REQUIREMENTS
 Processor : 32 bit Processor
 RAM : 512 Mb
 Hard Disk : 40 GB
 Internet : 512 Kbps high speed internet connection
4.1.3 SOFTWARE REQUIREMENTS
 OS : All OS supporting internet browsing
 Environment : Force.com Environment

19. 13
Bank Application
4.1.4 FUNCTIONAL REQUIREMENTS
 Understand the cloud environment provided by Salesforce.com
 Deploying the application.
 Providing the User accounts.
 Accessing the application from user accounts and should work with the
applications clearly.
4.1.5 PERFORMANCE REQUIREMENTS
 The performance will be fully based on the Internet connection. The
user may not worry about their local system. The local system will
be only used as a terminal.
4.1.6 SAFETY REQUIREMENTS
 There are the possibilities of data loss due to the interruption of
connection in Internet. So the user must ensure about his
uninterrupted internet connection.
4.1.7 SECURITY REQUIREMENTS
 All the security issues will be provided by the services provider
itself (Salesforce.com).
 No users are allowed to enter and view the details without proper
authentication (password protection).
4.2 RELIABILTY REQUIREMENTS
The main reliability requirement is the validation used. Without proper validation,
the system does not allow to enter that value into database. All the required
validation controls are kept to keep the system secure.

20. 14
Bank Application
The following are the some of the reliability requirements during register of the
applicant:
 In the email ID the user cannot enter any dummy value, the validation
checks that whether there is „@‟ or „_‟ symbol in that.
 Any null value is not allowed in place of compulsory field.
 In numeric field, user cannot enter any character value.
 Duplicate email ID is not allowed.

21. 15
Bank Application
Chapter-5
System Analysis and Design
5.1 MODULE DESCRIPTION
Modules are the partitions of any project done to ease the task of development.
Different modules are designed so that debugging and other development phase
gets the easiest implementation.
This project is divided into different modules:
1. Home Screen
2. Branches
3. Accounts Information
4. Loans
5. Loan Details
6. Transactions
5.1.1 HOME SCREEN
As soon as the app opens up, the screen which appears after the
splashscreen is the home screen. Home screen is the very interesting part
of any project as it gives the knowledge to the user what the app is all
about.
The home screen contains icons with names representing different
category of items that the user can click to explore further.
Clicking these icons let the user explore each item specifically.
The home screen consists of following items:
 Calendar, to know about events scheduled for the upcoming days.
 Items to Approve, by higher authorities.
 Tasks to be performed.
 Dashboards to provide graphical representation of snapshots.

22. 16
Bank Application
5.1.2 BRANCHES
When the user clicks on the Branch tab, all the information about the
branch like branch ID, Branch Name, total number of accounts the branch
contains, city and state are visible.
The bank employee fills the branch name, contact number of user, the
bank which it is associated with, state and city to keep the records of
branches.
5.1.3 ACCOUNTS INFORMATION
Accounts Information contains all the information of a branch, like its
account ID, the branch which it is associated with, total balance in the
account and the amount of starting balance.
Accounts Information contains details of a user using that account. A user
can have open any type of account like current account, saving account or
savings minor account.
5.1.4 LOANS
Different types of loans can be provided to the customers. The loans are
Home loan, gold loan, student loan, car loan, education loan and business
loan.
A user can take more than one loan.
5.1.5 LOAN DETAILS
Loan Details is an another object which stores information about the
remaining amount, remaining number of installments, type of loan and
the account which it is associated with.
5.1.6 TRANSACTIONS

23. 17
Bank Application
Transactions deals about whether the customer has deposited or
submitted the money. It is again associated with the account a person
have.
5.2 SYSTEM DESIGNING
5.2.1 E-R DIAGRAM
Fig. 5.2.1 Entity-Relationship Diagram

24. 18
Bank Application
5.2.2 DATA FLOW DIAGRAM
Fig. 5.2.2 Level 0 DFD
Fig. 5.2.3 Level 1 DFD

25. 19
Bank Application
5.2.3 CLASS DIAGRAM
Fig. 5.2.4 Class Diagram
5.2.4 USE CASE DIAGRAM
Fig. 5.2.5 Use Case Diagram

26. 20
Bank Application
5.2.5 SEQUENCE DIAGRAM
Fig. 5.2.6 Sequence Diagram

27. 21
Bank Application
5.2.6 ACTIVITY DIAGRAM
Fig. 5.2.7 Activity Diagram

28. 22
Bank Application
Chapter-6
Coding
This application is build in Salesforce on Force.com platform so it does not contains source
code, instead validation rules and different formula fields are applied in this project.
6.1 VALIDATION RULES
Validation rules verifies the data a user enters in a record. The data should meet the
standard specified by the organizations.
A validation rule can contain a formula or expression that evaluates the data in one or
more fields and returns a value true or false.
6.1.1 VALIDATION RULE FOR ACCOUNTS
a)MINIMUM BALANCE RULE:
IF(ISPICKVAL(Types_of_Accounts__c, “Savings Account”), IF(Balance__c<10000, true, false),
false)||IF(ISPICKVAL(Types_of_Accounts__c,”Current Account”), IF(Balance__c<25000,
true, false), false)||IF(ISPICKVAL(Types_of_Accounts__c, “Saving Minor Account”),
IF(Balance__c<2500, true, false), false)
b)STARTING BALANCE RULE:
IF( ISPICKVAL( Types_of_Accounts__c , "Savings Account") , IF(Starting_Balance__c <
10000,true,false),false) || IF( ISPICKVAL( Types_of_Accounts__c , "Current Account") ,
IF(Starting_Balance__c < 25000,true,false), false) || IF( ISPICKVAL(
Types_of_Accounts__c , "Saving Minor Account"), IF(Starting_Balance__c < 2500,
true,false), false)
6.1.2 VALIDATION RULE FOR TRANSACTION
a)DEPOSIT RULE
Transaction_Amount__c < 0

29. 23
Bank Application
b)WITHDRAW RULE
IF( Transaction_Amount__c >= 0, false, ISPICKVAL( Type_of_Transaction__c , "Withdraw") )
6.2 FORMULA FIELDS
It is a read only field, the value of formula field evaluate from expression is defined
by us. If we update any value in the expression, it automatically updates formula field
value.
A formula can contain references to the values of operators, functions, literal values,
or even other formulas. They are generally composed of the following components:
Literal values-A text string or number we enter that is not calculated or changed.
6.2.1 FORMULA FIELD FOR AVERAGE TRANSACTION
DEPOSIT
IF( Count_Transaction_Deposit__c < 1, 0, Total_Transaction_Deposit__c /
Count_Transaction_Deposit__c )
6.2.2 FORMULA FIELD FOR AVERAGE TRANSACTION
WITHDRAW
IF( Count_Transaction_Withdraw__c <1, 0, TotalTransactionWithdraw__c /
Count_Transaction_Withdraw__c )
6.2.3 FORMULA FIELD FOR BALANCE
Starting_Balance__c + Total_Transaction_Deposit__c - TotalTransactionWithdraw__c
6.2.4 FORMULA FIELD FOR LOAN DETAIL
( Loan_Amount__c * Loan__r.Rate_of_Interest__c * Loan__r.Tenure__c )

30. 24
Bank Application
Chapter-7
Project Snapshots
7.1 LOGIN PAGE
Fig.7.1 Login Page of Salesforce

31. 25
Bank Application
7.2 HOME PAGE
Fig.7.2 Home Page

32. 26
Bank Application
7.3 TAB DESCRIPTION
7.3.1 BANK TAB
Fig.7.3.1 New Bank
7.3.2 BRANCH TAB
Fig.7.3.2 New Branch

33. 27
Bank Application
7.3.3 ACCOUNTS INFORMATION TAB
Fig.7.3.3 New Accounts Information
7.3.4 LOAN DETAILS TAB
Fig.7.3.4 New Loan Details

34. 28
Bank Application
7.3.5 TRANSACTION TAB
Fig.7.3.5 New Transaction
7.4 REPORT
Fig.7.4 Report of Transactions per week

35. 29
Bank Application
7.5 DASHBOARD
Fig.7.5 Dashboard of Transactions per week
7.6 AUTOMATED EMAIL
Fig.7.6 Automated email generation on account creation

36. 30
Bank Application
7.7 LOGOUT SCREEN
Fig.7.7 Logout Interface

37. 31
Bank Application
Chapter-8
Testing and Maintenance
System Testing of software and hardware is testing conducted on a complete, integrated
system to evaluate the system‟s compliance with its specified requirements.
8.1 TYPES OF TESTING
8.1.1 BLACK BOX TESTING
The technique of testing without having any knowledge of the interior workings of the
application is called black-box testing. The tester is oblivious to the system architecture and
does not have access to the source code. Typically, while performing a black-box test, a tester
will interact with the system‟s user interface by providing inputs and examining outputs
without knowing how and where the inputs are worked upon.
8.1.2 WHITE BOX TESTING
White-box testing is the detailed investigation of internal logic and structure of the code.
White-box testing is also called glass testing or open-box testing. In order to perform white-
box testing on an application, a tester needs to know the internal workings of the code.
8.1.3 GREY BOX TESTING
Grey-box testing is a technique to test the application with having a limited knowledge of the
internal workings of an application.
8.1.4 UNIT TESTING
Unit Testing contains the testing of each unit. Each interface is tested by input values and
checked whether it is working properly or not.
8.1.5 INTEGRATION TESTING

38. 32
Bank Application
Integration testing is defined as the testing of combined parts of an application to determine if
they function correctly. Integration testing can be done in two ways: Bottom-up integration
testing and Top-down integration testing.
8.1.6 SYSTEM TESTING
System Testing tests the system as a whole. Once all the components are integrated, the
application as a whole is tested rigorously to see that it meets the specified quality standards.
This type of testing is performed by a specialized testing team.
8.2 TEST CASES
S.No Test Case Input Action
1. Test Case for Login Correct Username
and password.
Incorrect Username
or password or both
of them.
User login
successfully.
Message: Your login
attempt has failed.
The username or
password may be
incorrect.
2. Test Case for
Accounts Information
Starting Balance and
Type of Account.
Error: Starting
Balance should be
greater than or equal
to 10000 for Savings
Account, 2500 for
Savings Minor
Account and 50000
for current Account.
3. Test Case for
Transaction
Types of Transaction
and Transaction
Error: Transaction
amount should be

39. 33
Bank Application
Amount. less than minimum
balance.
4. Test Cases for
Mandatory Fields.
If you left the field
blank, if email has no
„@‟ symbol.
Error: You must
enter a value.
Error: Invalid email
address.
Table 8.1
1. Error message for invalid email ID and for mandatory fields
Fig.8.2.1 Invalid Email Address
2. Error message for starting balance and types of account
Fig.8.2.2 Error message for balance

40. 34
Bank Application
8.3 DEPLOYMENT AND MAINTENANCE
After successful testing and validation of the application, the application needs to be made
available to the users for implementation or use.
It is important to deploy during a period when users will not be making changes to the
organization. We should also perform a test deployment to guarantee the success of the
production deployment. These steps typically happen during a maintenance window. During
this time, users should be locked out of the system, so plan this well in advance and during
off-peak hours. Deployment is an all-or-nothing event – because any changes we make on
production during the deployment phase can nullify the final deployment, it is important that
no changes occur until deployment finishes.
It is advisable to create a staging environment that allows us to test deployment before
deploying to production. The staging environment is usually a full-copy sandbox, so it is as
similar to the production organization as possible.
Deployment to the staging environment follows the same procedure as migrating from one
development organization to another. This procedure include manual migration for any
component not in the meta-data API, and for any feature developed using the Salesforce user
interface. In addition, it is advisable to manually run all tests in the staging environment to
avoid any possible issues before the production deployment.
After unit and system testing, we have deployed Salesforce application on Salesforce.com‟s
cloud. Salesforce provide the cloud computing application running environment where all the
necessary packages is provided by Salesforce.com platform. AppExchange is a Salesforce
cloud application marketplace from where we can download application and customize them.

41. 35
Bank Application
CONCLUSION
1. SUMMARY
After we have completed the project we are sure the problems in the existing system
would overcome. The “Bank Application” made computerized to reduce human errors
and to increase the efficiency. The main focus of this project is to lessen human
efforts. Bank application is a Salesforce application for the banking purpose. It
provides information of transactions made by any account. This application is build
with an administrative‟s perspective where he can maintain all the services of a bank.
Different type of accounts can be created, transactions like withdraw and deposit can
be managed. The user interface of the application can be modified by administrator
only. Every application requires strong security and this app provides proper data
security. Not only this, the tasks can be automated as well. An administrator can even
create some restrictions for its employees. The administrator and employees can create
accounts for users and manage them by sending information regarding their accounts.
They can be provided by different type of loans also. Bank app stores data information
in one place with the help of Reports and Dashboards.
2. FUTURE SCOPE
 Future of this app is very wide.
 It automates the processes and make it easy and simple.
 It removes the manual work of creating multiple sheets which
consumes a lot of time and hard work.
 Security and sharing settings are respected in this app.
 This app is not restricted to a particular system. With Salesforce, it is
possible to work from anywhere, even with Salesforce1 mobile app.

42. 36
Bank Application
REFERENCES
[1] developer.salesforce.com
[2] Salesforce.com
[3] ecquire.com/blog/32-salesforce-guides
[4] Force.com fundamentals
[5] Wikipedia.org
[6] The Unified Modeling Language Reference Manual - James Rumbaugh, Ivar Jacobson,
Grady Booch- Addison Wesley
[7] Object Oriented Software Engineering Using UML, Second Edition -Bernd Bruegge,
Allen H. Dutoit, Pearson Education