Problem
I have a payment processing application that integrates with SWIFT (which sends the cover messages to my application for every transaction) for wire transactions, and I have business requirements that must be translated to my App's functional requirements and features. Need help with this translation so I can use the functional requirements to design an architectural diagram.
Business requirements are in the form of scenarios/user stories as follows:
• Scenario I: MT103/202 message was received but not the matching cover payment or cover advise; i.e cover status of MT103/202 is "Unmatched". The system/app needs to be able to match the MT103/202 with a cover message where the value date of transaction is today.
• Scenario II: Cover payment or cover advice was received before MT103/202. Cover payment or cover advice does not match any MT103/202 in 'Cover' queue. System/app needs to be able to match cover payment/advice with MT103/202 where the value date of transaction is today.
• Scenario III: MT103/202 was received and the matching cover payment/advice was received afterwards. i.e cover status of MT103/202 is "Matched". System/app needs to be able to match MT103/202 with cover payment/advice where there is one and only one matched.
• Scenario IV: MT103/202 was received and matched with more than one cover payment/advice. i.e "Multiple match". System needs to manually search for a cover match and enter the unique transaction reference to force link with MT103/202, and system needs to be able to select cover message from the list of possible cover matches provided by the system.
• Scenario V: MT103/202 was received with future value date. i.e cover status is "Pending". System/app needs to be able to check if value date of MT103/202 is in the future so that it will postpone checking for cover match until value date is reached.
• Scenario VI: Generate report or notification at the end of day so as to send the report via email or post to UI for export.
• Scenario VII: Cancel or archive past value transactions where cover status is "Unmatched". System/app needs to be able to cancel/(archiveMT103/202 already addressed) MT103/202 when cover message is not received in order to clear items in 'Cover' queue.
• Scenario VIII: System receives a cancellation request, MT192/292 where matching MT103/202 is in 'Cover' queue. System/app needs to be able to join MT103 with MT192 in order to send MT196 to sender. System also checks the matching cover payment in order to return the funds back to Sender.