1. A 2D Barcode-Based Mobile Payment System
Presented by

2. Project scope
 This system uses one standard 2D Barcode (Data Matrix) as
an example to demonstrate how to deal with underlying 2D
barcode-based mobile payment workflow, mobile
transactions and involved security mechanisms.
 Unlike other existing mobile payment systems, the
proposed payment solution provides distinct advantages to
support buy-and-sale products and services based on 2D
Barcodes. This system uses one standard 2D Barcode (Data
Matrix) as an example to demonstrate how to deal with
underlying mobile business workflow, mobile transactions
and security issues. The paper discusses system
architecture, design and implementation of the proposed
mobile payment solution, as well as 2D barcode based
security solutions.

3. User classes & characteristics
System Infrastructure and Framework Architectures
• Client Layer – This layer includes mobile user interface and online client
interface. The online client interface is designed support end customers
and merchants to perform user account and membership management.
The mobile payment client software supports mobile user interactions for
mobile payment.
The mobile payment client is supported by J2ME (with Netbeans IDE,
CLDC 1.1. MIDP 2.1), Bouncy Castle Light Weight Crypto APIs, JSON
utility, and the 2Dbarcode framework Middle Layer –the components in
the middle layer. They include wireless internet server (Tomcat server) and
other Java related middleware, such as Java 2 (J2SE), Bouncy Castle
Crypto Library, JSON utility, Java DB connectivity and Java Servlet
technology.
• Application Layer – This is the mobile payment server, which supports the
2D barcode-based mobile payment process and related transactions .
• Data Store Layer – This includes a database server, which stores,
maintains, and processes the customer account and membership data,
transaction data, and user digital wallet as well as necessary security data,
such as PIN and session records.

4. Operating environment
This application is developed in java platform and will be hosted by a
system using Java JDK and tomcat server. The system will
primarily be developed and tested on Windows Operating Systems.
But our goal is to make it a platform independent solution. The target
platforms are:
Linux
Microsoft Windows &
Solaris.

5. Design and Implementation
Constraints
All designing and coding will be done on Java
Platform. However application can be
implemented in C#.NET.

6. Assumptions and Dependencies
Since the application is based on Java platform. Hence we assume that user
system must installed JVM to run this application.

7. SYSTEM FEATURE
Functional requirements
Hard disk 80 GB
RAM 1GB
Processor Intel Pentium IV
Technology Java
Tools Net beans
Operating System Windows

8. EXTERNAL INTERFACE REQUIREMENTS
User Interfaces: The application is accessible through web browser. It will interact
with its users with web components interface. There are two types of user for this
system retail manager or analyst and customer each can interact with the system with
the following UIs.
Main screen: On this interface there are some options shown as per the user type
For the analysts there are some options related to what type of analysis they want to
do.
Method wise analysis
Decision tree analysis
KNN classifier analysis
For each of the above analysis there is separate new screen showing advanced
options for that analysis that is something like stated below:
There are buttons for ‘In which format output should be displayed Graphical formats
like pie charts , Bar graphs, Tabular format.
Output screen:
On this screen output will be produced in graphical format with proper description
and some options like save result for further use or compare it with old results or
you may discard it if it is of no use.

9. Software Interfaces
 Name: Java
Version Number: Version 6.0
 Name: Mysql
Version Number: Version 7.0.1
The system must use My SQL server as its database
 Name: NetBeans
Version Number: Version 6 onward

10. Communications Interfaces
The system will use Apache/tomcat server as the main
communication protocol trough internet/network.

11. NON-FUNCTIONAL REQUIREMENTS
Performance Requirements
• System can produce results faster on 4GB RAM.
• It may take more time for peak loads at main node
• The system will be available 100% of the time. Once
there is a fatal error, the system will provide
understandable feedback to the user.

12. Safety and Security Requirements
• All data will be backed-up everyday automatically and also the
system administrator can back- up the data as a function for
him.
• The system is designed in modules where errors can be
detected and fixed easily. This makes it easier to install and
updates new functionality if required.

13. Software Quality Attributes
 Usability : The application seem to user friendly since the GUI is
interactive.
 Maintainability : This application is maintained for long period of
time since it will be implemented under java platform .
 Reusability : The application can be reusable by expanding it to the
new modules. Performance: The application seems to be
performing faster under 4 GB of RAM. However, the basic
requirement to run the application is 1GB.
 Security: Since the application is developed on JAVA .It is much
more secure than the other environment.

14. Use case

15. Data flow diagram

16. UML Activity diagram

17. UML State transition diagram

18. UML Sequence diagram

19. TECHNICAL SPECIFICATION
ADVANTAGES
 The application is platform independent since it is
developed in JAVA.
 The behavior of the application is user friendly since the
GUI is compatible with all operating environment.
Disadvantage
 Since the application performs several task at same
time, It seems to generate output at long interval of time.

20. Applications
 Mobile E-commerce
 Mobile banking
 Mobile Transactions
 E-Wallet