Difference between revisions of "IS480 Team wiki: 2015T1 A3xy Midterm Wiki"

From IS480
Jump to navigation Jump to search
Line 54: Line 54:
'''Deployed website'''<br/>
'''Deployed website'''<br/>
Trade Portal : http://smu.tbankonline.com/SMUtBank_CIB<br/>
Trade Portal : http://smu.tbankonline.com/SMUtBank_CIB<br/>
Trade Operations :<br/>
Trade Operations : https://smu.tbankonline.com:9443/ProcessPortal/login.jsp<br/>

Revision as of 17:42, 4 October 2015

A3xy team logo1.png

A3xy HomeIcon.png


  A3xy UserIcon.png


  A3xy Project.png


  A3xy StatsIcon.png


  A3xy PapersIcon.png


Main Wiki Midterm WikiWP SubPlane.png Final Wiki

Project Progress Summary

A3xy midterm.png

Midterm Slides

A3xy computer.png

Deployed website
Trade Portal : http://smu.tbankonline.com/SMUtBank_CIB
Trade Operations : https://smu.tbankonline.com:9443/ProcessPortal/login.jsp

Development Progress

Current Progress : 75%
Current Iteration : 9
1st Oct - 14th Oct

Team faced some delay in a few iterations but made up for it by completing the last iteration in less than estimated time.

Our implementation is divided into two parts : Trade Portal for importer and exporter and Trade Operations for Issuing Bank and Advising Bank. Below is the scope of our project and the functionalities we have completed till now :

A3xy midscope.png

Project Management

Project Schedule (Planned VS Actual)
Planned Actual

A3xy timeline v1.jpg

A3xy timeline.png

In the process we needed to finish Amendment before Shipping Guarantee and Trust Receipt. The main changes are from iteration 6 onwards. Also, we had to add the payment functionality into the iteration plan.

Project Scope (Planned VS Actual)
Planned Actual

A3XY Scope.png

A3XY Scope1.png

Schedule Metrics

A3xy midSM.png
Iteration % Completion Planned Days Actual Days Metric Index
1 100% 14 16 87.5%
2 100% 14 15 93.33%
3 100% 14 14 100%
4 100% 14 17 82.4%
5 100% 14 9 155.6%
6 100% 14 17 82.4%
7 100% 14 15 93.3%
8 100% 14 10 140.0%

Below are the reasons for high and low schedule metrics for the iterations :

A3xy midSM1.png
A3xy midSM2.png
A3xy midSM3.png
A3xy midSM4.png

Bug Metrics

Risk Management
Risk Consequences Likelihood Impact Mitigation Strategy
Team is unfamiliar with technologies used. Project will be potentially delayed due to incorrect estimates. High High Team members will research and guide each others. Project manager will allocate more time to this task.
Delay in development due to downtime of server. Front-end and IBM BPM implementation not possible if the server is down. Low High Coordinate with the client on a regular basis to modify the schedule if required.
Failure to factor in minor coding tasks due to lack of experience. Project will be potentially delayed as these minor tasks need to be performed. Medium Medium PM has to work closely with the Back-End and front-end lead developers and bridge the gap between business process and technical components.
Change Management

Technical Complexities
Feature Involved Description of Technical Complexity What is to be achieved as the end result
Web service calling from BPM. Use of SOAP request message and IBM BPM mapping to make web services call from IBM BPM. BPM can access data from the database only through web services in order to read a Letter of Credit, uploaded documents and other data.
Exposing web service through BPM. Use of undercover agent feature of IBM BPM. This is used in order to trigger the BPM process by a web service call or any action from the front-end portal.
Messaging standard web services between banks. Use of Gateway that supports both SWIFT and ISO standards. Banks have different standards for sending messages across each other. The gateway is used for sending advise and acknowledgement messages from one bank to the other.

Quality of Product


A3xy midref1.png
A3xy midref2.png