Difference between revisions of "IS480 Team wiki: 2015T1 A3xy FinalWiki"
Poojat.2012 (talk | contribs) |
Poojat.2012 (talk | contribs) |
||
Line 138: | Line 138: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 16 | | style="text-align:center" | 16 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 0.88 |
|- | |- | ||
| style="text-align:center" | 2 | | style="text-align:center" | 2 | ||
Line 144: | Line 144: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 15 | | style="text-align:center" | 15 | ||
− | | style="text-align:center" | 93 | + | | style="text-align:center" | 0.93 |
|- | |- | ||
| style="text-align:center" | 3 | | style="text-align:center" | 3 | ||
Line 150: | Line 150: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 1.00 |
|- | |- | ||
| style="text-align:center" | 4 | | style="text-align:center" | 4 | ||
Line 156: | Line 156: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 17 | | style="text-align:center" | 17 | ||
− | | style="text-align:center" | 82 | + | | style="text-align:center" | 0.82 |
|- | |- | ||
| style="text-align:center" | 5 | | style="text-align:center" | 5 | ||
Line 162: | Line 162: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 9 | | style="text-align:center" | 9 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 1.56 |
|- | |- | ||
| style="text-align:center" | 6 | | style="text-align:center" | 6 | ||
Line 168: | Line 168: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 17 | | style="text-align:center" | 17 | ||
− | | style="text-align:center" | 82 | + | | style="text-align:center" | 0.82 |
|- | |- | ||
| style="text-align:center" | 7 | | style="text-align:center" | 7 | ||
Line 174: | Line 174: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 15 | | style="text-align:center" | 15 | ||
− | | style="text-align:center" | 93 | + | | style="text-align:center" | 0.93 |
|- | |- | ||
| style="text-align:center" | 8 | | style="text-align:center" | 8 | ||
Line 180: | Line 180: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 10 | | style="text-align:center" | 10 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 1.40 |
|- | |- | ||
| style="text-align:center" | 9 | | style="text-align:center" | 9 | ||
Line 186: | Line 186: | ||
| style="text-align:center" | 9 | | style="text-align:center" | 9 | ||
| style="text-align:center" | 9 | | style="text-align:center" | 9 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 1.00 |
|- | |- | ||
| style="text-align:center" | 10 | | style="text-align:center" | 10 | ||
Line 192: | Line 192: | ||
| style="text-align:center" | 14 | | style="text-align:center" | 14 | ||
| style="text-align:center" | 19 | | style="text-align:center" | 19 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 0.74 |
|- | |- | ||
| style="text-align:center" | 11 | | style="text-align:center" | 11 | ||
Line 198: | Line 198: | ||
| style="text-align:center" | 15 | | style="text-align:center" | 15 | ||
| style="text-align:center" | 15 | | style="text-align:center" | 15 | ||
− | | style="text-align:center" | | + | | style="text-align:center" | 1.00 |
|- | |- | ||
|} | |} | ||
Line 213: | Line 213: | ||
<br/> | <br/> | ||
Below are the bug points distribution for each iteration: | Below are the bug points distribution for each iteration: | ||
− | [[Image: | + | [[Image:A3xy_finalbug1.png|center|850px|link=]] |
Below is the distribution of bugs based on their severity for each iteration: | Below is the distribution of bugs based on their severity for each iteration: | ||
− | [[Image: | + | [[Image:A3xy_finalbug3.png|center|850px|link=]] |
<br/> | <br/> | ||
{| class="wikitable" | {| class="wikitable" |
Revision as of 02:29, 21 November 2015
Main Wiki | Midterm Wiki | Final Wiki |
|
Midterm Slides |
Deployed website |
Current Progress : 100%
Current Iteration : 12
12th Nov - 23rd Nov
Below is the scope of our project and the functionalities :
Lab session |
Users |
Purpose
|
Feedback from students :
Below are some pictures from the lab session :
Project Management
Planned | Actual |
---|---|
Planned | Actual |
---|---|
|
Below are the reasons for high and low schedule metrics for the iterations :
Below are the bug points distribution for each iteration:
Below is the distribution of bugs based on their severity for each iteration:
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 | 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. |
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
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 |
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)
- Time Spent in finishing the Document Presentation process (in mins)
- Did you understand the full process?
- Was the application easy to use?
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.
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