IS480 Team wiki: 2013T1 Kungfu Panda Final Wiki

From IS480
Revision as of 15:01, 6 November 2013 by Yh.koon.2010 (talk | contribs)
Jump to navigation Jump to search

Main WikiKP-Main Wiki Link.PNG

Project Progress Summary

Midterm Presentation Slides Download!
Link to our Banch Teller Application:

Our team, Kungfu Panda, have been progressing well since the start of iteration 1; currently, we are in iteration 9 of our project. Although through the first half of the semester, we faced some changes requested by our client, our team faced them well. We were very focused. However, due to some last minute changes to our requirement, our team is currently rescheduling some task to the next iteration in order to complete the prioritized task first.

After Midterm, our team should have completed about 65% of the Branch Teller Application which includes the Party Customer, Deposit Account, Loan Account and Transaction use cases. We will be moving on to complete our X-Factor (Credit Approval and Teaching Tool) after our Midterm.

Project Highlights

Project Management

Project Status

Currently, our project is 68.12% completed.
Percentage of Development Tasks Complete = Number of Completed Tasks (in Green) / Total Number of Tasks
The below diagram shows a coloured diagram / map of development tasks that are completed and outstanding.

1144 × 469px
1145 × 361px

Project Milestone & Schedule



Our Updated Project Schedule Download!

Project Metrics

Schedule Metrics


KP-Individule MetricsWk23.PNG

Below are some graphs which shows our schedule metrics for each iterations and for each individual members.
We have also calculated the average man hours per week each member put in.


KP-Individule MetricsGraphWk23.PNG


Bug Metrics

Total number of bugs encountered: 38
Bug Metric for FYP Week 22: 1 KP-GoodBugMetric.PNG
Below shown are the latest 25 bugs our team have encountered and is recorded in our Bug Tracker.

Bug tracker 101013.PNG



KP Bug Metrics wk24a.PNG

KP Total Bug wk24b.PNG

KP Bug Score wk24c.PNG

Project Risk

Below are our team's top 3 Risk - High Likelihood and High Impact

1. Lack of Market Research due to Confidentiality of Proprietary Systems

  • Product Comparison with Oracle Flexcube Branch Teller
  • Subject Matter Experts to be interviewed
    • i.e. OCBC’s Head of Credit Risk

2. Dependencies on Services Built by Others

  • Changes requested by other teams for shared services
  • MDM Billing Organization Read List
    • Delivered 6 September by FYP Team IRONmen

3. Project Scope & Requirement Changes

  • Increase time spent with Client outside of Weekly Meetings
    • BA & PM 4-6 hrs / week
  • BIAN (Banking Industry Architecture Network Documentation for Developed Services
  • Documentation in industry defined template, common terminology & language
  • “Irons out” the little details
  • Longevity of the SMU tBank project after our FYP


Technical Complexity

Frontend Complexity

KP-Frontend Complexity.PNG

Backend Complexity

Summary of Complexities Faced

  1. Data Integrity
    1. Ensured that insert statements made to the databases were ordered (serialized)
    2. Handled error flow should a transaction violation error occur
  2. Finance Formulas
    1. Had to research on finance formulas and understand the time value of money in order to complete this task
    2. Translated finance formulas (annuity formula) into Java code to be used in the Loan creation process
  3. Business Logic Errors
    1. Used XPath formulas within Tibco Designer to check for conditions such as insufficient balance or no such account and what to do subsequently
  4. Business Process Flow
    1. Entire business logic of the core banking systems is programmed inside the back-end services
    2. Deciding the order of events (which should come first etc.) in terms of business requirements was a key consideration in the design as well

Development using Tibco Enterprise Messaging Service (EMS)
Tibco Enterprise Messaging Service is a middleware product that implements the Java Messaging Service (JMS). Its flexible architecture helps simplify operational complexity by supporting the communication with a wide variety of technologies so that businesses can focus on the development and refinement of business requirements.

To develop on the EMS, our team had to use a sister product of Tibco, the Tibco Designer. This is a GUI-based developmental interface that allows developers to minimise coding whilst maintaining a high level of efficiency in capturing business process logic.

Sample Service: Account_Loan_Create Service KP-Account Loan Create.PNG

Product Comparison


1. Features Comparison

2. Screen Space Utilization Comparison
KP-ProductCompare2a.PNG KP-ProductCompare2b.PNG

3. Modern UI Element Comparison


Quality of Application

Project Deliverables

Stage Specification Modules
Project Management Project Scope
Progress Overview
Meeting Minutes
Design ER Diagram
General Architecture Diagram
Branch Teller Architecture Diagram
Testing UT 1 - Informal Testing
UT 2 - Deployment Exercise



The following Branch Teller Functionalities have been deployed in the SMU tBank Server:
These represent 17 of 18 core functionalities.
- Party Create
- Party User PIN Create
- Party Read & Update
- Customer's Accounts Dashboard
- Account Deposit Read & Update
- Account Loan Create
- Manage Customer's Loan Accounts
- Account Loan Read & Update
- Transaction Deposit
- Transaction Withdrawal
- Transaction History Read
- Payment Credit Transfer Bill Payment
- Payment Loan Repayment Full
- Payment Loan Repayment Partial

The following Back End Services have been deployed in the SMU tBank Server:
These represent all 17 SMU Core Services.
- Party Customer Create
- Party Customer Read
- Party Customer Update
- Party Customer Read IC
- Account List Read
- Account Deposit Create
- Account Deposit Read
- Account Deposit Update
- Account Loan Create
- Account Loan Read
- Account Loan Update
- Transaction Deposit
- Transaction Withdrawal
- Transaction History Read
- Payment Credit Transfer Create
- Transaction FullLoanRepayment Create
- Payment Loan Repayment Partial


Client Testing

Deployment Exercise

User Test 1

User Test 2


Team Reflection

Individual Reflections