Baokim Mobile

e-Wallet

1
 Supervisor
Mr. Nguyễn Tất
Trung

Project Manager
Vũ Hải Nam

Coding Team
Test Team
Business Analysis Design Team Vũ Hải Nam
Team Đỗ Thùy
Nguyễn Ngọc (Leader) Vân
Nguyễn Lưu Bách Hưng (Leader) Nguyễn Ngọc (Leader)
(Leader) Hưng
Vũ Hải Nam Trần Quang
Vũ Hải Nam Nguyễn Lưu Linh
Bách (support &
review)

2
Contents

1
• Baokim introduction

2
• Background

3
• Proposal

4
• Main Objectives

5
• Software Project Management Plan

6 • Software Requirement Specification

7
• Software Design Description

8
• Testing

9
• Demo

3
 Baokim introduction
 Online payment portal.
 Was built based on PayPal, Moneybookers models.
 Baokim.vn plays the role of payment intermediary.
 Provide services: Online payment, transfer funds online.
 BMW’s sponsor.

4
Background - Trend of smartphone in
Vietnam

Figure 1: Rate of people using smartphones

Figure 2: Rate of people using smartphone application daily

5
Background - Trend of smartphone in
Vietnam

Figure 3: Rate of people using Android smartphone

Figure 4: Kinds of popular smartphone applications used in Vietnam

6
Background - Trend of smartphone in
Vietnam

Android smartphones are

Android smartphones are
becoming hotter and
becoming hotter and
hotter in Vietnam
hotter in Vietnam
Android banking and
Android banking and
shopping applications are
shopping applications are
popular used in Vietnam
popular used in Vietnam

CHANCE
7
Proposal - Idea

AAmobile
mobilee-wallet
e-walletspecified
specifiedfor
forBaokim
Baokimusers
users

8
Proposal- E-wallet and mobile
e-wallet

e-Wallet:
• A virtual wallet that stores your
payment cards, offers, and more on
your phone and online.
• Some e-Wallets in Vietnam:
MobiVi, Momo, Payoo, VnMart.

Mobile e-Wallet:
• E-wallet is specialized for using on
mobile devices.

9
Proposal – Proposed system

10
Main Objectives

Transfer money Request money

to another BMW from another
user BMW user
Shopping
by scanning
QR code
View View account
transactions information
history

11
Software project management plan
Software process model

Iterative model
 Always have a
running version of the
program

 Easily identify the

source of last error

 Customers are
psychologically more
satisfying

 Less time for

corrections
12
Software project management plan
Master plan

13
Software project management plan
Master plan

14
Software project management plan
Quality plan

Estimated Quantity
Use cases 10
Test cases GUI test cases 106
Functional test cases 245

Defect density 5 bugs per kLOC

15
Software project management plan
Risk management
No. Risk Avoidance Contingency Plan Status
1 SRS does not cover Before writing SRS, hold one Hold an internal meeting to Closed
enough business meeting with customer to make review all meeting minutes and
logic. clear everything related to SRS notes related to SRS to find out
and take note carefully what we have missed

2 Unit test is not Developers are responsible for Re write unit test and every Closed
performed thoroughly. write unit test for their own codes developers are responsible for
reviewing.
3 Lack of testing tools Buy a new device named Sony Ask customer to support devices Closed
Xperia S for testing and for testing and developing.
developing

4 Baokim Rest APIs are Inform a specific plan for Delay implementing methods/use Closed
not completed on implementing BMW to customer. cases related to these APIs.
time. Implementing others
methods/use cases.

5 Conflicts happen Hold weekly meeting. On this Team leader is responsible for Closed
between team meeting, everyone has right to talking with those members to
members express his opinions and feeling find the solution.
about everything related to project
16
Software Requirement Specification
Functional Requirement

Function
Login
Initialize application
Shopping by scanning QR code
Remove product(s) from cart
Make payment for cart
Transfer money
Receive money
Request money
View transaction history
View account information

17
Software Requirement Specification
Functional Requirement

Login

18
Software Requirement Specification
Functional Requirement

Initialize application

19
Software Requirement Specification
Functional Requirement

Shopping by scanning
QR code

20
Software Requirement Specification
Functional Requirement

Remove products & Make payment

21
Software Requirement Specification
Functional Requirement

Transfer money

22
Software Requirement Specification
Functional Requirement

Request money

23
Software Requirement Specification
Functional Requirement

View transactions history

24
Software Requirement Specification
Functional Requirement

View account information

25
Software Requirement Specification
Non-Functional Requirement

Non-Function
Usability
Reliability
Security
Performance

26
Software Design Description
Overall system architecture

27
Software Design Description
ZXING library

28
Software Design Description
Digital Signature algorithm

29
Software Design Description
Component diagram

30
Software Design Description
Class diagram

31
Software Design Description
Sequence diagram

32
Software Design Description
Database design
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<string name="preferences_search_country">-</string>
<boolean name="preferences_play_beep" value="true" />
<boolean name="preferences_supplemental" value="true" />
<boolean name="licenseScreenShown" value="true" />
<boolean name="preferences_decode_QR" value="true" />
<boolean name="preferences_copy_to_clipboard" value="true" />
<string name="accessToken">54a6c9f23b90b2cd09ee69bc72d56f09</string>
<string name="email">[email protected]</string>
<string name="id">1015635</string>
<string name="phone_no">84973663054</string>
<string
name="rsaPrivateKey">MIICXwIBAAKBgQC6AzNJP9I5/Nx6igJnSsKzN096Z9Ot4FMR/q5qh
cpxl9ZuNJZv
HYWSqoaqHCTyRfGnXslbGwa22USD68bv1nRlw0w90gImnn+3u1DGOBaoNM08T45b
XEI4Rr5atJsoluxspvRqjiqDqZwVjo6puiq/mNvSA2um9HpPu6zIOWGd1wIDAQAB
AoGBALdmAGLwMe5KiXeoKsZ8x4q7tfkR9Xsx+bV8TatpTjjBZAI0hz329YOt7ig6
p5LXs3M52X2iH/SYMx1+kh5Wa1tY21HoJhCqE7vxUOp9h0mXVpm/QKCQkQYeEqtc
QPiiX7ZR94GfGooAsImgEwlIYBn7F96iBKZdFhFfkE3tj/eBAkEA9dw9W8WDbXbJ
0K7cac47KGqv2cZTvBQhPLCBNdKF6CW9gtoCpy9cS5rFl5Mo4/rnE2hZ7CibTvEO
HFh8uwRWqQJBAMGvGHDxpN7tdSumt0IvKyj5GGbX+RrNLA58/4ByR3ORj4jWmJ91
958xCSfmpIL7cdlG3hPjpGjKhbZlg+MpoH8CQQDr446fYWcS/JjvdwYVIgCSa6Ij
AO1QE8Q79WFTYZSGwscMJ93JyF/2Th3sqw3dhtp0PXehZOh2GkQeoCu0R5pZAkEA
sNmxZoeutIN8JpR+5ubs8OeqGVYBNjC7lqsaHW27wlHaDudrysbLiMcchht6gcMY
bH3iD6UfnTO3Lhm5eHWs/wJBALaKFFJUIKmKa3M94si7iJTCVXbDby3hV4IZwu90
gIybh1nd/dNoqFYiSROX1I/ayGahMIgt2ix+M33I/E/2u94=</string>
<string name="total_amount">12</string>

</map>

33
Testing
Testing phases

Software Development Phases Test Excuse Phases

User Acceptation 1/8-6/8

Requirement Validate Acceptation
Test
Test
System 28/7-31/7
System System Test
Requirement Verify/Validate System Test
Requirement
Spec
Spec
Integration 21/7-27/7
Architectural Integration
Architectural Verify Test
Design Spec Test
Design Spec
Detail Design Verify Unit Test 15/7-20/7
Detail Design Unit Test
Spec
Spec

Coding & 34
Review
Testing
Testing process

Create
Test
Test Revie Execut
test
plan
plan w TC e test
case

35
Testing
Defect log

• Using excel to log defect, includes:

• Communicate with developer via SVN or directly

36
Testing
Test result

37
Testing
Acceptance test result

38
39