IS480 Team wiki: 2013T1 BANKREVELS/Midterm

From IS480
Jump to navigation Jump to search

Group Logo.png

Project Progress Summary

Arrow bankrevels.png Please click HERE to download our Midterm Slides.

Arrow bankrevels.png Please click HERE to view our Project Description.

Project Overview



Project Highlights

Project Management

Prj status.png

We are currently at the stage of preparing for the midterms and have completed 9 out of 11 iterations so far.

Project Timeline


Key Issues

1. Iteration 7 Implementation of Next Best Offer with the LiveLabs took longer than expected. The iteration was shifted to iteration 10.

2. Iteration 9 The team spent hours solving the issues encountered on the funds transfer and thus leading to a shorter time frame to complete iteration 9. RM Scheduler has finished the back-end work, left the integration on the front end of mobile app Loan Calculator was shifted to iteration 10 as well. (done with mock-up of loan calculator) The team is given a shorter period of time to complete stock ticker and notification Team members have to put in extra man-hours to finish iteration 10 on the rescheduled time frame. PM have to readjust the project schedule and add in more man power to work on the tasks in iteration 10.

Priority Circle


Project Highlights

Highlights bankrevels.png

Iteration 6 No prior knowledge on the Titanium

Team members requires a period of time to be familiar and explore the use of Titanium

Arrange meeting during buffer time to complete outstanding tasks.Remind members of the risk involved.
Iteration 8 Resolving bugs generated during User Testing

Many bugs have surfaced during the UT 1, especially for the fund transfer functionality, and thus the team took more man hours than the planned duration to resolve them. After receiving the feedback from User Testing 1, our team has also decided to make a huge revamp (giving it a new and improved look) on the Internet Banking Application.

Consult Prof Alan immediately on the issues faced on the Fund Transfer backend services. Individual team member has to put in more man hours to complete the tasks at hand.

Man Hours

Man hours.png Sch.png

Project Metrics

1. Schedule Metrics

  • To ensure that all project tasks are completed on time and milestones are met which will be tracked by Project Manager on a per iteration basis.


Schedule Ratio = Actual Duration / Planned Duration

Schedule metrics table bankrevels.jpg

Sch metrics.png


  • To minimize and keep track of the number of bugs that surface during project development and thus ensuring the quality of the application.
  • A bug is defined as errors in code that causes system to behave differently from expected.

Bug Metrics

Bug metrics bankrevels.jpg

Bug bankrevels.png
Bugs identified from iteration 6 onwards.

Outstanding bankrevels.png
Iteration 8 has the highest number of bugs while iteration 9 has an increase in number of bugs due to the feedback from UT 1 participants. No immediate action is required as outstanding score is 5.

Action Plan

Total score = (1*Number of Low) + (3*Number of High) + (10*Number of Critical)

Action plan bankrevels.jpg

Project Risks


We prioritized the more specific and pertinent risks that we currently facing for our midterms. please refer to our detailed schedule for other risks identified.

Bankrevels risk.png

Change Management Log


Whenever there is a change in the services at the back-end during our client meeting, the changes has to be recorded in the change management log in order to assist individual team member to make successful personal transitions resulting in the adoption and realization of change.

Download the detailed project schedule

Technical Complexity

Login Using 2FA

Bankrevels midterm techdiagram01.png

RIB Mobile 2FA Login

BR RIBmobile2falogin.png


Bankrevels midterm techQuikpay.png

For the NFC integration within our Quikpay function, we made use of the Titanium NFC module. Quikpay consists of the sender and the recipient function. For the sender function, we made use of the foreground dispatcher. The foreground dispatcher allows the app to intercept the ndef messages containing the quikpayID. The recipient function makes use of the createNDEFRecord method to push the message to the sender. We will be having a Quikpay QR code version as well, which is currently still in progress.

The main issue faced with the NFC was with the Quikpay transaction. If a sender were to attempt to transfer funds more than once, it would not actually work. One of the reasons for the failure of the NFC in the Quikpay function was due to the design of the UI and the method in which the NFC was integrated within the application.



  • Integration of native QR code scanner into tBank mobile app
  • Language used : Objective – C


  • An open-source C barcode reading library
  • Suitable for iOS
  • Compared with Zxing, easier to use upon integration with the mobile app using X-code
    • Clearer API documentation
    • More samples
    • Can read both barcode and qr-code
    • More standardardised

Problems Encountered

  • Programming Language
    • No prior knowledge of the language used
  • Environment
    • OS X: UNIX Kernel
    • IDE: X-code

Project Quality

Intermediate Deliverables

Stage Specification Modules
Project Management Minutes
Analysis Use case
tBank Architecture Diagram


Area Details
Development Environment
  • Deployed to Apache Tomcat server, Android and iOS
  • mySQL
  • ActiveSpaces (In-memory data grid)

Web Links


User Testing 1 (UT 1)

The objectives of UT 1 are to understand the intuitiveness, ease of using the application, as well as to get feedback from users on the design and layout of the application on all two platforms (Android and web).

Devices tested for Android
  1. Samsung S3
  2. Samsung Note 2
  3. LG Optimus G

The purpose of the UT 1 is to find out the following from the users:

  1. How does user find the login 2FA using QR code instead of the conventional hardware token?
  2. Is the QuikPay function intuitive enough?
  3. Can the user use the Fund Transfer function with ease?
  4. How easy it is for the user to navigate through the whole application?
  5. How does the user feel about the layout and design of our application?
  6. What are the user's emotions when using the application?
  7. What are the user's general impressions of the application?

Data Collected
Qualitative Data Quantitative Data


  1. Feedback on the layout of Account Summary Page
  2. Feedback on the design of Account Summary Page
  3. Feedback on the improvements for Account Summary Page
  4. Feedback on the layout of Transaction History Page
  5. Feedback on the design of Transaction History Page
  6. Feedback on the improvements for Transaction History Page
  7. Feedback on the things they like
  8. Feedback on the things they dislike
  9. Feedback on general impressions of the application

Observation sheet

  1. Recorded comments on Login 2FA
  2. Recorded comments on Funds Transfer
  3. Recorded feelings of user throughout the test
  4. Recorded general observations of users

For RMB only

  1. Recorded comments Login 2FA
  2. Recorded comments on QuikPay


  1. Age
  2. Gender
  3. Frequent User (Yes or No)
  4. Ease of using Funds Transfer (1 - very difficult, 5 - very easy)
  5. Ease of adding a payee (1 - very difficult, 5 - very easy)
  6. Ease of removing a payee (1 - very difficult, 5 - very easy)
  7. Ease of navigating the application (1 - very difficult, 5 - very easy)

For RMB only

  1. Ease of using QR code as login 2FA (1 - very difficult, 5 - very easy)
  2. Ease of using QuikPay (1 - very difficult, 5 - very easy)

Observation Sheet

  1. Time taken for login 2FA
  2. Time taken for Fund Transfer
  3. Number of times the user asked for help for login 2FA
  4. Number of times the user asked for help for Fund Transfer
  5. Number of times the user asked for help for the rest of the functions

For RMB only

  1. Time taken for QuikPay
  2. Number of times the user asked for help for QuikPay
Participants, Timing and Venue held

Number of participants: 20
Date and Time held: 19 - 20 September 2013 (10am - 7pm)
Venue: SMU



Participants will be welcomed to the user testing by the facilitator. Thereafter, participants will be given a brief overview of the application and given a list of tasks they need to complete. Participants will be required to complete all tasks, without the guidance of the facilitator. However, the participants can ask the facilitator for help should they face any problems and such instances will be recorded down on the Observation Sheet provided.

After going through the user testing of the application, participants are required to do an evaluation of the application on the Questionnaire provided. Participants are encouraged to discuss any problems they encounter with the facilitator.

The User Testing will end after the participants complete the Questionnaire. The facilitator will then thank the participants for their time and feedback provided.

Functions Tested
No. Functions Tested
1 Login 2FA
2 View account information
3 View transaction history
4 Fund Transfer
5 QuikPay
6 Add new payee
7 Remove existing payee
Results and Follow Up

Data will be collected using the Questionnaire provided by the team which participants are required to fill it up after going through the application, and the facilitator's Observation Sheets. After the collection of all the data required, the team will collate and organize the raw data into appropriate tables and give a summary of the results of this user testing. A team meeting will be held to discuss the changes to be made.

Key Findings

Mobile Banking

  1. Most users have given positive feedback about using QR code such as increased convenience and ease of use. However, several users also point out the lack of security of QR code as it does not generate a dynamic password unlike the hardware token.
  2. Almost all users find using QR code for login 2FA easy
  3. No issue in usability for Account Summary and Transaction History
  4. Almost all users have no problems using QuikPay, Standard Funds Transfer and Adding a new payee
  5. Some users mentioned the lack of intuitiveness and instructions required for the delete payee function
  6. Navigation of the whole application is easy among the users
  7. Users had feedback that the application is easy to use and navigate and commented that they like the bright colour scheme of the application
  8. For points that users dislike, many users reflect that they had problems deleting the payee as the function is not obvious. Security issue is another point brought up by users for the usage of QR code login 2FA
  9. The general impression of users is our application is relatively easy to use and is able to navigate without any major issues. Some commented that they like the trendy feel the application gives

Internet Banking

  1. A variety of feedbacks from users on Account Summary were collected. The difficulty in reading grey fonts stood out the most among the other feedbacks collected
  2. A variety of feedbacks from users on Transaction History were collected. The inappropriate font size stood out the most among the other feedbacks collected. Users commented that font size used is too small to read
  3. No major issue in usability for Standard Funds Transfer, Adding a payee and Deleting a payee
  4. Navigation through the whole application is deemed to be moderately difficult among users. Users commented that the segments of the web application are unclear
  5. For points that users like, many users commented that it is easy to navigate the web application. The basic neat design is well-liked by the users
  6. For points that users dislike, some users reflect that they had problems reading the font due to its size and it being grey in colour. Few users reflect that there is too much white space for some pages
  7. The general impression of the application is that it is relatively easy to use

Deployment exercise


The objectives of the deployment exercise is to carry out stress testing of the our application (web and android) and to identify any bugs present in our application that we have not surfaced out during our own testing.

Participants, Timing and Venue held

Number of participants: 45 students from the Retail Banking class
Date and Time held: 2 October 2013 (8.15am - 9.30am)
Venue: SMU


Participants are required to go through a Retail Banking Lab that involves the mobile and internet banking functions. 2 of the members will be facilitators of the exercise to help the participants should they face any problems with the application.

After going through the lab exercise, participants are encouraged to give any feedback to the facilitators.

Functions Tested

Internet Banking

No. Functions Tested
1 Login 2FA
2 View account information
3 View transaction history
4 Fund Transfer
5 Set up Customer Preferences

Mobile Banking

No. Functions Tested
1 Login 2FA
2 View account information
3 View transaction history
4 Fund Transfer
Follow Up

The facilitators will collect the feedback and communicate to the members of the group to make any necessary changes to the application (Android and web).


Team Reflection


Individual Reflection