HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
 
(41 intermediate revisions by 2 users not shown)
Line 46: Line 46:
 
| width="100%" |
 
| width="100%" |
 
'''Midterm Slides'''<br/>
 
'''Midterm Slides'''<br/>
Download:  
+
Download: [[Media:A3xy_Imidtermslides.pdf | Midterm presentation]]
 
|}
 
|}
 
<br/>
 
<br/>
Line 53: Line 53:
 
| width="100%" |
 
| width="100%" |
 
'''Deployed website'''<br/>
 
'''Deployed website'''<br/>
Trade Portal :<br/>
+
Trade Portal : http://smu.tbankonline.com/SMUtBank_CIB<br/>
Trade Operations :<br/>
+
Trade Operations : https://smu.tbankonline.com:9443/ProcessPortal/login.jsp<br/>
 
|}
 
|}
 
<br/>
 
<br/>
Line 63: Line 63:
 
'''1st''' Oct - '''14th''' Oct
 
'''1st''' Oct - '''14th''' Oct
 
</div>
 
</div>
Team faced some delay in a few iterations but made up for it by completing the last iteration in less than estimated time.  
+
Team faced some delay in a few iterations but made up for it by completing the last iteration in less than estimated time. Team is confident of delivering the project on time.
 
<br/><br/>
 
<br/><br/>
 
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 :
 
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 :
 
[[Image:A3xy_midscope.png|center|800px|link=]]
 
[[Image:A3xy_midscope.png|center|800px|link=]]
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Project Management</font></div>==
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Project Management</font></div>==
 +
<br/><div style="font-size:20px">'''Iteration Tasks'''</div><br/>
 +
[[Image:A3xy_midtasks.png|left|800px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 
<br/><div style="font-size:20px">'''Project Schedule (Planned VS Actual)'''</div>
 
<br/><div style="font-size:20px">'''Project Schedule (Planned VS Actual)'''</div>
 
{| class="wikitable"
 
{| class="wikitable"
Line 92: Line 94:
 
|}
 
|}
 
<br/>
 
<br/>
 +
Payment Advise functionality was added and Bill Discounting functionality was omitted from the scope of the project.
 +
<br/><br/>
 +
<div style="font-size:20px">'''Schedule Metrics'''</div>
 +
<br/>
 +
{| width="50%" |
 +
[[Image:A3xy_midSM.png|left|400px|link=]]
 +
| width="50%" |
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Iteration
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Completion %
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Planned Days
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Actual Days
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Metric Index
 +
|-
 +
| style="text-align:center" | 1
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 16
 +
| style="text-align:center" | 87.5%
 +
|-
 +
| style="text-align:center" | 2
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 15
 +
| style="text-align:center" | 93.33%
 +
|-
 +
| style="text-align:center" | 3
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 100%
 +
|-
 +
| style="text-align:center" | 4
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 17
 +
| style="text-align:center" | 82.4%
 +
|-
 +
| style="text-align:center" | 5
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 9
 +
| style="text-align:center" | 155.6%
 +
|-
 +
| style="text-align:center" | 6
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 17
 +
| style="text-align:center" | 82.4%
 +
|-
 +
| style="text-align:center" | 7
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 15
 +
| style="text-align:center" | 93.3%
 +
|-
 +
| style="text-align:center" | 8
 +
| style="text-align:center" | 100%
 +
| style="text-align:center" | 14
 +
| style="text-align:center" | 10
 +
| style="text-align:center" | 140.0%
 +
|-
 +
|}
 +
|}
 +
<br/><br/><br/>
 +
Below are the reasons for high and low schedule metrics for the iterations : <br/>
 +
[[Image:A3xy_midSM1.png|center|900px|link=]]
 +
[[Image:A3xy_midSM2.png|center|900px|link=]]
 +
[[Image:A3xy_midSM3.png|center|900px|link=]]
 +
[[Image:A3xy_midSM4.png|center|900px|link=]]
 +
<br/>
 +
<div style="font-size:20px">'''Bug Metrics'''</div>
 +
<br/>
 +
Below are the bug points distribution for each iteration:
 +
[[Image:A3xy_midbug1.png|center|850px|link=]]
 +
Below is the distribution of bugs based on their severity for each iteration:
 +
[[Image:A3xy_midbug3.png|center|850px|link=]]
 +
<br/>
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;width:100px; border:1px solid #999" | Iteration
 +
! style="font-weight: text-align: center; bold;width:100px; border:1px solid #999" | Bug Score
 +
! style="font-weight: text-align: center; bold;width:200px; border:1px solid #999" | Summary of Bugs
 +
! style="font-weight: text-align: center; bold;width:200px; border:1px solid #999" | Action Taken
 +
|-
 +
| style="text-align:center" | 5
 +
| style="text-align:center" | 13
 +
| style="text-align:center" | Most of the bugs were in exposing BPM as a web service and UI  improvements.
 +
| style="text-align:center" | Stop current development and resolve the bug immediately. Project Manager reschedules the project.
 +
|-
 +
| style="text-align:center" | 7
 +
| style="text-align:center" | 4
 +
| style="text-align:center" | Bugs were related  to parsing of XML element.
 +
| style="text-align:center" | The system does not need immediate fixing, could be fixed during buffer time or during coding sessions.
 +
|-
 +
| style="text-align:center" | 8
 +
| style="text-align:center" | 7
 +
| style="text-align:center" | Errors involved UI improvements and calling of web services.
 +
| style="text-align:center" | Use planned debugging time in the iteration to solve the bug.
 +
|-
 +
|}
 +
<div style="font-size:20px">'''Risk Management'''</div>
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Risk
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Consequences
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Likelihood
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Impact
 +
! style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:200px; border:1px solid #999" | Mitigation Strategy
 +
|-
 +
| style="text-align:center" | Team is unfamiliar with technologies used.
 +
| style="text-align:center" | Project will be potentially delayed due to incorrect estimates.
 +
| style="text-align:center" | High
 +
| style="text-align:center" | High
 +
| style="text-align:center" | Team members will research and guide each others. Project manager will allocate more time to this task.
 +
|-
 +
| style="text-align:center" | Delay in development due to downtime of server.
 +
| style="text-align:center" | Front-end and IBM BPM implementation not possible if the server is down.
 +
| style="text-align:center" | Low
 +
| style="text-align:center" | High
 +
| style="text-align:center" | Coordinate with the client on a regular basis to modify the schedule if required.
 +
|-
 +
| style="text-align:center" | Failure to factor in minor coding tasks due to lack of experience.
 +
| style="text-align:center" | Project will be potentially delayed as these minor tasks need to be performed.
 +
| style="text-align:center" | Medium
 +
| style="text-align:center" | Medium
 +
| style="text-align:center" | PM has to work closely with the Back-End and front-end lead developers and bridge the gap between business process and technical components.
 +
|-
 +
|}
 +
<div style="font-size:20px">'''Technical Complexities'''</div>
 +
{| class="wikitable"
 +
! style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:100px; border:1px solid #999" | Feature Involved
 +
! style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:100px; border:1px solid #999" | Description of Technical Complexity
 +
! style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:200px; border:1px solid #999" | What is to be achieved as the end result
 +
|-
 +
| style="text-align:center" | Web service calling from BPM.
 +
| style="text-align:center" | Use of SOAP request message and IBM BPM mapping to make web services call from IBM BPM.
 +
| style="text-align:center" |  BPM can access data from the database only through web services in order to read a Letter of Credit, uploaded documents and other data.
 +
|-
 +
| style="text-align:center" | Exposing web service through BPM.
 +
| style="text-align:center" | Use of undercover agent feature of IBM BPM.
 +
| style="text-align:center" | This is used in order to trigger the BPM process by a web service call or any action from the front-end portal.
 +
|-
 +
| style="text-align:center" | Messaging standard web services between banks.
 +
| style="text-align:center" | Use of Gateway that supports both SWIFT and ISO standards.
 +
| style="text-align:center" | 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.
 +
|-
 +
|}
 +
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Quality of Product</font></div>==
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Quality of Product</font></div>==
 +
<div style="font-size:20px">'''Intermediate Deliverables'''</div>
 +
There should be some evidence of work in progress.<br/>
 +
{|  class="wikitable"  border="1"
 +
|- style="background:#fcd703; color:white"
 +
|align="center"| Stage
 +
|align="center"| Specification
 +
|-
 +
|rowspan="5"| Project Management
 +
 +
|| [[IS480_Team_wiki:_2015T1 A3XY_ProjectManagement|Project schedule]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_ScheduleMetrics|Schedule Metrics]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_BugMetrics|Bug Metrics]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_RiskManagement|Risk Management]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_ChangeManagement|Change Management]]
 +
|-
 +
 +
|rowspan="5"| Project Overview
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3xy_ProjectOverview|Project Description]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1 A3XY_Motivation|Motivation]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_Scope|Scope]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_Technologies|Technologies]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_Xfactor|X-factor]]
 +
|-
 +
 +
|rowspan="6"| Documentation
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3xy_Documentation|Technical Documents]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_DesignDocuments|Design Documents]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_TestDocuments|Test Documents]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_MeetingMinutes|Meeting Minutes]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_ProjectDocuments|Project Documents]]
 +
|-
 +
 +
|| [[IS480_Team_wiki:_2015T1_A3XY_Deployment|Deployment]]
 +
|-
 +
|}
 +
<div style="font-size:20px">'''User Test 2'''</div>
 +
<b>Objective : Are we building an understandable portal?</b><br/><br/>
 +
The tasks assigned can be found here: [[Media:A3xy_UT2.pdf| A3XY User Test 2 Plan]]<br/>
 +
<b>Demographic</b> <br/>
 +
{| class="wikitable"
 +
| style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:100px; border:1px solid #999" | Users
 +
| style="text-align:center" | Students
 +
|-
 +
| style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:100px; border:1px solid #999" | Number of Users
 +
| style="text-align:center" | 5
 +
|-
 +
| style="font-weight: text-align: center; bold;background: #57E3AB;color:#fff; width:100px; border:1px solid #999" | Venue
 +
| style="text-align:center" | SMU school campus
 +
|-
 +
|}
 +
<br/>
 +
<b>Brief information on the participants:</b>
 +
*Experienced with background in Consumer Internet Banking
 +
*Understand banking terms
 +
*Have not being exposed to the software being used (IBM BPM)
 +
<br/>
 +
<b>Goals:</b>
 +
*Students should find the BPM portal and Trade Finance portal user friendly.
 +
*Students should like the web interface of the portal.
 +
*Students should understand the process of LC Application and Document Presentation.
 +
<br/>
 +
<b>Feedback Collected:</b>
 +
The feedback collected can be found here: [[Media:A3xy_UT2Results.pdf| A3XY User Test 2 Results]]
 +
<br/><br/>
 +
<b>Results:</b>
 +
*Time Spent in finishing the LC Application process (in mins)<br/>
 +
[[Image:a3xy_UT2_result1.png|left|500px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 +
*Time Spent in finishing the Document Presentation process (in mins)<br/>
 +
[[Image:a3xy_UT2_result2.png|left|500px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 +
*Did you understand the full process?<br/>
 +
[[Image:a3xy_UT2_result3.png|left|400px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 +
*Was the application easy to use?<br/>
 +
[[Image:a3xy_UT2_result4.png|left|400px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 +
<b>Key Findings:</b>
 +
*Participants find the technical names confusing sometimes. They have to go back to the Trade Finance home page every time in order to recall the meaning of different terms.
 +
*Participants pointed out that it would be better if the URL of the document is clickable on the portal itself rather than copy pasting
 +
*Participants find the IBM BPM portal easy to use and straightforward with minimum clicks involved.
 +
*Participants liked the user interface of the Trade Finance portal.
 +
*80% of the participants understood the process of LC Application and Document Presentation using this application.
 +
*60% of the participants did not find the application easy to use.
 +
*Participants were a bit confused about the ISO and SWIFT messaging standards display.
 +
<br/>
 +
<div style="font-size:20px">'''User Test 3'''</div>
 +
<b>Objective : Process Verification</b><br/><br/>
 +
The tasks assigned can be found here: [[Media:A3xy_UT3.pdf| A3XY User Test 3 Plan]]<br/>
 +
<b>Demographic</b> <br/>
 +
{| class="wikitable"
 +
| style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Users
 +
| style="text-align:center" | Professors
 +
|-
 +
| style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Number of Users
 +
| style="text-align:center" | 2
 +
|-
 +
| style="font-weight: text-align: center; bold;background: #fcd703;color:#fff; width:100px; border:1px solid #999" | Venue
 +
| style="text-align:center" | SIS MR 4.3
 +
|-
 +
|}
 
<br/>
 
<br/>
 
+
<b>Brief information on the participants:</b>
 +
*Experienced with background in Trade Finance
 +
*Work at Ngee Ann Polytechnic
 +
<br/>
 +
<b>Goals:</b>
 +
*To gather suggestions and feedback after using the application.
 +
*To verify content and check consistency throughout the platform.
 +
*To find pain points identified by the Professors while using the platform and trade portal.
 +
*To find out whether the platform would act as a good teaching tool or not.
 
<br/>
 
<br/>
 +
<b>Usability:</b><br/>
 +
Ratings of various elements of the portal<br/>
 +
[[Image:a3xy_UT3_result.png|left|600px|link=]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Reflection</font></div>==
 
==<div style="background: #4d627f; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:24px"><font color= #FFFFFF>Reflection</font></div>==
<br/>
+
[[Image:A3xy_midref1.png|center|800px|link=]]
 
+
[[Image:A3xy_midref2.png|center|800px|link=]]
 
|}
 
|}

Latest revision as of 15:57, 21 February 2016

A3xy team logo1.png



A3xy HomeIcon.png

HOME

  A3xy UserIcon.png

ABOUT US

  A3xy Project.png

PROJECT OVERVIEW

  A3xy StatsIcon.png

PROJECT MANAGEMENT

  A3xy PapersIcon.png

DOCUMENTATION

 
Main Wiki Midterm WikiWP SubPlane.png Final Wiki


Project Progress Summary


A3xy midterm.png

Midterm Slides
Download: Midterm presentation


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. Team is confident of delivering the project on 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


Iteration Tasks

A3xy midtasks.png























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


Payment Advise functionality was added and Bill Discounting functionality was omitted from the scope of the project.

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


Below are the bug points distribution for each iteration:

A3xy midbug1.png

Below is the distribution of bugs based on their severity for each iteration:

A3xy midbug3.png


Iteration Bug Score Summary of Bugs Action Taken
5 13 Most of the bugs were in exposing BPM as a web service and UI improvements. Stop current development and resolve the bug immediately. Project Manager reschedules the project.
7 4 Bugs were related to parsing of XML element. The system does not need immediate fixing, could be fixed during buffer time or during coding sessions.
8 7 Errors involved UI improvements and calling of web services. Use planned debugging time in the iteration to solve the bug.
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.
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

Intermediate Deliverables

There should be some evidence of work in progress.

Stage Specification
Project Management Project schedule
Schedule Metrics
Bug Metrics
Risk Management
Change Management
Project Overview Project Description
Motivation
Scope
Technologies
X-factor
Documentation Technical Documents
Design Documents
Test Documents
Meeting Minutes
Project Documents
Deployment
User Test 2

Objective : Are we building an understandable portal?

The tasks assigned can be found here: A3XY User Test 2 Plan
Demographic

Users Students
Number of Users 5
Venue SMU school campus


Brief information on the participants:

  • Experienced with background in Consumer Internet Banking
  • Understand banking terms
  • Have not being exposed to the software being used (IBM BPM)


Goals:

  • Students should find the BPM portal and Trade Finance portal user friendly.
  • Students should like the web interface of the portal.
  • Students should understand the process of LC Application and Document Presentation.


Feedback Collected: The feedback collected can be found here: A3XY User Test 2 Results

Results:

  • Time Spent in finishing the LC Application process (in mins)
A3xy UT2 result1.png











  • Time Spent in finishing the Document Presentation process (in mins)
A3xy UT2 result2.png











  • Did you understand the full process?
A3xy UT2 result3.png












  • Was the application easy to use?
A3xy UT2 result4.png












Key Findings:

  • Participants find the technical names confusing sometimes. They have to go back to the Trade Finance home page every time in order to recall the meaning of different terms.
  • Participants pointed out that it would be better if the URL of the document is clickable on the portal itself rather than copy pasting
  • Participants find the IBM BPM portal easy to use and straightforward with minimum clicks involved.
  • Participants liked the user interface of the Trade Finance portal.
  • 80% of the participants understood the process of LC Application and Document Presentation using this application.
  • 60% of the participants did not find the application easy to use.
  • Participants were a bit confused about the ISO and SWIFT messaging standards display.


User Test 3

Objective : Process Verification

The tasks assigned can be found here: A3XY User Test 3 Plan
Demographic

Users Professors
Number of Users 2
Venue SIS MR 4.3


Brief information on the participants:

  • Experienced with background in Trade Finance
  • Work at Ngee Ann Polytechnic


Goals:

  • To gather suggestions and feedback after using the application.
  • To verify content and check consistency throughout the platform.
  • To find pain points identified by the Professors while using the platform and trade portal.
  • To find out whether the platform would act as a good teaching tool or not.


Usability:
Ratings of various elements of the portal

A3xy UT3 result.png












Reflection

A3xy midref1.png
A3xy midref2.png