VUS - illyfrancis/scribble GitHub Wiki

Updates to BRD

  1. Clarify the assumption on multiple accounts structure and identify the system that manages accounts life cycle
  • Describe the linkage / association between accounts -> transactions (for each type)
    • and identify which system/component is responsible for maintaining
  • Describe the association between transactions (which field identifies etc)
    • and also identify which system/component is responsible for maintaining that relationship
  • Refine the current BRD to describe (per VUS messages 1-7) the condition/rule that initiates each transmission
    • identify the account type (A,B or C) that is triggering
    • identify the source systems in each case
    • instead of seeing it as ETL, describe in terms of event
      • the source systems may be an extension to existing component or a new sub-component implementing the rule/condition identified above
  • Remove reference to ETL

Information missing on Mutual Funds

Q's For BA

  • Start with accounts structure
  • What is SEB client cash account number (derived from a UAF lookup)?
  • How to distinguish the transactions for Acct A vs Acct B and C?
  • What's the association between the accounts and its transaction records?
    • For example, is there an account number field in the transaction?
  • What about the relationship between transactions for Acct A and transactions for Account B/C?
    • Any examples?
  • The assumption is that UAF will hold the relationship between Accounts A/B/C.
    • Does this mean given Account A, it can tell its associated accounts B/C? and also the reverse?
  • Is there a requirement to 'expose' the internal transaction identifier to SEB through VUS message?
    • If not, how to cater for SEB's inquiry wrt a transaction which is known only by its VUS id within BBH
    • If exposed SEB should inquire with internal transaction id
  • How to interface with SEB?
    • for both receiving messages from SEB and sending to SEB
    • should we follow what interM? swift net? (whatever that is?)

More general Q's for everyone

  • In the doc, there's additional message for Request FX Execution (relating to VUS3)
    • Need to describe and confirm

Design to produce

  • Define messages for each flow between the source system and VUS
  • Break up VUS component (not part of BRD?)
Design assumptions
  • UAF maintains the accounts relationship between A, B and C
    • does this mean given A, UAF can provide related B or C and vice versa?