Académique Documents
Professionnel Documents
Culture Documents
On
Submitted to
(2014-2017)
By
akanksha Singh
(a1004914066)
Ginni arora
i akanksha Singh of B.Sc iT hereby declare that the project titled Mobile
Banking application which is submitted by me to Department of a.i.i.T,
amity University Uttar Pradesh, Noida, in partial fulfillment of requirement
for the award of the degree of (B.Sc iT), has not been previously formed the
basis for the award of any degree, diploma or other similar title or recognition.
The author attests that permission has been obtained for the use of any copy
righted material appearing in the Project report other than brief excerpts
requiring only proper acknowledgement in scholarly writing & all such use is
acknowledged.
Signature
Noida
To the best of my knowledge this work has not been submitted in part or full for
any Degree or Diploma to this University or elsewhere.
aiiT
;
Table Of Contents
Chapter-3 analysis 6
3.1.1 introduction
3.1.1.1 Purpose
3.1.1.3 References
3.1.2.6 assumption
3.1.5.1 Performance
3.1.5.2 Reliability
Chapter-4 architecture 9
4.1 DFD
4.2 ER Diagram
Chapter-5 Testing 17
Chapter-6 interface 20
Chapter-7 Conclusion 31
Chapter-8 References 32
Chapter-1 introduction & Objective
Technical Feasibility
Economical Feasibility
Operational Feasibility
Specialized Feasibility figures out if the association has the innovation &
abilities important to carryout the undertaking & how this ought to be
acquired. The framework can be attainable in view of the accompanying
grounds.
Our task is in fact plausible on the grounds that, all the innovation required
for our venture is promptly accessible.
Practical Feasibility:
The expense of h/w & s/w for the class of utilization being considered.
The techniques for h&ling & presentation are totally acknowledged by the
customers since they can meet all client prerequisites.
The customers have been included in the arranging & improvement of the
framework.
The proposed framework won't bring about any issue under any
circumstances.
Our venture is operationally possible in light of the fact that the time
necessities & work force prerequisites are fulfilled. We are a group of four
individuals & we dealt with this anticipate for three working months.
Chapter-3 analysis
3.1.1 introduction
3.1.1.1 Purpose
Tellingly, 12 million people used mobile banking services in 2009, according to Frost & Sullivan, a
research firm. That number will climb to 45 million by 2014.
Mobile banking offers many advantages, such as good security, easy access & plentiful applications
for smart phones. The biggest benefit is that you have more control of your money, says James Van
Dyke, president of Javelin Strategy & Research in Pleasanton, Calif. You dont have internet
connections everywhere you go. But you do have a mobile connection.
Mobile banking takes us back to the days when we used passwords, he says. You knew where you
stood at any moment. For example, you can be sitting on an airport tarmac checking your account
balance or looking at recent transactions.
The downside is that mobile banking isnt as good as it could be, says Van Dyke. The reason: Many
services are pretty basic. People use it to check balances & monitor finances. Largely, its an
augment to the internet, he adds.
Van Dyke gives the highest marks to Wells Fargos & Bank of americas mobile banking services,
though. There are lots of great features, he says. Theyre strong in security & they offer multiple
downloadable applications.
He adds that there are far fewer banking options for mobile banking than internet banking. On that
front, mobile banking has a long way to go, he says. But the best services offer bank transaction data
& use personal finance software.
Mobile banking isnt as fully functional as online banking, says Thomas Trebilcock, vice president
of e-business & payments at PNC Bank. We offer things you can do every day, such as looking at
account activity & paying bills.
Yet, many experts say that mobile banking offers many benefits worth using, & some are getting
increasingly better. Heres a rundown.
Good security
No fees
Easy access
The following has been covered under the project Mobile Banking.
3. SMS banking
4. E-Banking
5. iT in Banking
3.1.1.3 References
SYSTEM SPECiFiCaTiON
HaRDWaRE REQUiREMENTS :
Hard Disk : 80 GB
SOFTWaRE REQUiREMENTS :
System Feature
c) Security, Privacy & Trust: a customer must be able to trust a mobile payment
application provider that his or her credit or debit card information may not be
misused. Secondly, when these transactions become recorded customer privacy
should not be lost in the sense that the credit histories & spending patterns of
the customer should not be openly available for public scrutiny. Mobile payments
have to be as anonymous as cash transactions. Third, the system should be
foolproof, resistant to attacks from hackers & terrorists. This may be provided
using public key infrastructure security, biometrics & passwords integrated into
the mobile payment solution architectures.
The user interface for the software shall be compatible to any browser such as
internet Explorer, Mozilla or Netscape Navigator by which user can access to the
system.
Hard Disk : 80 GB
any user should be logged in to do any activity. New Student should be able register
for account.
Student can register once & can use their login for lifetime.
Security:
Only authorized person can view & modify confidential details.
Each Student has his/her own access rights & to lower level Student there are
restrictions of not using some of the system components.
One Student can not access other users account.
Scalability:
Performance of the system should not be degraded when many users are logged-in &
accessing the database at the same time.
The system must be scalable enough to be able to add any additional functionality
even after the project is developed once.
Reliability:
The database of various modules like Super admin, admin & Student maintained by
the system should be correct & maintained up to date.
Usability:
The system must provide user friendly environment to its users & must be easy to
access its various features.
in the Email id, the user will not be able to enter any dummy value, the validation will
check that whether there is a or . symbol in that or not.
in our system each & every field must be filled with proper information otherwise the
record will not going to be saved.
in Numeric field user will not be allowed to enter any character values.
in Date & Time textbox, user cannot enter date & time other than given format,
because here system always takes current date & time from the system this provides
defense against fake entries.
in entry of Phone number if there is a mobile number than user must enter a 11 digit
phone number.
While inserting any new information or details user is not allowed to update or search
any other record which may be restricted to him/her.
Limited visibility of different modules & sub-modules should be based on group
created for specific domain.
in all these validation actions if system found one or more entries violating
validation rules then user will be warned by proper error messages & the details
or the record is not going to be saved until corrections are made to them.