Difference between revisions of "IS480 Team wiki: 2015T1 A3xy Midterm Wiki"
Poojat.2012 (talk | contribs) |
Poojat.2012 (talk | contribs) |
||
Line 156: | Line 156: | ||
<br/><br/><br/> | <br/><br/><br/> | ||
Below are the reasons for high and low schedule metrics for the iterations : <br/> | Below are the reasons for high and low schedule metrics for the iterations : <br/> | ||
− | [[Image:A3xy_midSM1.png| | + | [[Image:A3xy_midSM1.png|center|900px|link=]] |
− | [[Image:A3xy_midSM2.png| | + | [[Image:A3xy_midSM2.png|center|900px|link=]] |
− | [[Image:A3xy_midSM3.png| | + | [[Image:A3xy_midSM3.png|center|900px|link=]] |
− | [[Image:A3xy_midSM4.png| | + | [[Image:A3xy_midSM4.png|center|900px|link=]] |
<br/> | <br/> | ||
<div style="font-size:20px">'''Bug Metrics'''</div> | <div style="font-size:20px">'''Bug Metrics'''</div> |
Revision as of 17:34, 4 October 2015
Main Wiki | Midterm Wiki | Final Wiki |
|
Midterm Slides |
Deployed website |
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 :
Project Management
Planned | Actual |
---|---|
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.
Planned | Actual |
---|---|
|
Below are the reasons for high and low schedule metrics for the iterations :
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
Reflection