Design And Implementation Of Mobile Banking System

First of all, we report the status and background of mobile banking around the world.After that we introduce WAP mobile banking, including its advantage and disadvantagesuch as out time protocol and lack of security system, and we found that we need a solutionof new generation mobile banking system.We analysis functions and non-function requirements of this project. In the aspect offunctions requirements, we clear the business-flow of most important functions sense viadata-flow graph. And in the aspect of non-functions requirements, according to peculiarityof banking system and peculiarity of environment where mobile devices are, we claim threekey points, we found that our system needs to be a stable, security, platform crossingsystem. The results of this chapter, should be the statement of the chapter III.In the Chapter of “Design and Implementation”, We analysis several developmentpatterns which is actively these days on market. And pay more attention on Hybriddevelopment patterns and Client/Server development patterns. Finally we chose Hybriddevelopment patterns as our choice, because this one can solve the problems of C/S, suchas lower reusable ability in different operating systems of smart devices. And it can alsosolve problems of B/S, such as the lacking of user-experience, accessibility of hardware andetc.And then, we discuss the security requirement. In the second of this chapter, We talkabout security of data transmit between client and server, during that process we encryptdata with passkey, and makes passkey un-revealable, and for client security, we apply antidebugging, anti injection and packing classes solution to our client. And also track ourapplication after it is distributed to app store. But because the security of mobile bankingsystem is too sensitive to our system, this chapter would not to reveal detail and code toreaders.At last we talk about how to enhance user experience with "static recourses cached", and make a prototype for that. We discussed kinds of problems and possibility of thissolution, and reveal key points of this solution via codes and business flow graph. At lastwe compare data between the performance with and without "static recourses cached"solution.After read this article, we found solutions of development patterns, security anduser-experience to build a mobile banking system. These solutions will provide basetheories for future mobile banking system of this commercial bank, and it is possible forthis bank to deploy new features on different smart devices rapidly.