VUS Design

Work Streams

1. Core Logic

Approach

Further breakdown by messages

• VUS 1, 2 or .. 7

Or breakdown by type

• Trade transactions
• MF trade transactions
• Corporate action transactions

Capture design approach for each breakdown and success criteria?

Core functions

• VUS Ref Id generation
  • ensuring uniqueness, durable with re-start

Concerns regarding NFR including:

• reliability
  • redundancy
  • durable message
  • system recovery
• capacity
  • scalability - both horizontal and vertical
  • on which component? core only?
• performance
  • what, where, how and when to measure?
  • establish benchmark?

2. Event Source Adapters

Need to filter and/or transform each input data and supply that to the Core system. The source system involved are:

• RTCR
• FX Away
• MFPS
• InfoM(?) - depends on VUS 5 handling

For each system identified, (may) need an adapter (or wraper?) with filter/transformer. The actual integration with respective systems are the concern of the integration stream.

3. Integration

Define the communication channel, queues, set up of MQ, and message types between systems. Concerned with message consuming and dispatch.

3.1. Client (i.e. SEB)

• Message transformation (is this really the concern of the integration layer? or should it be moved out/up to adapter?)

3.2. Reference data

• UAF
• Static database

3.3. Source systems / Upstream systems

• RTCR
• FX Away
• MFPS
• InfoM(?)

4. Operational Concerns

4.1. Monitoring / Alerts

4.2. Reporting (only in relation to VUS messages)

4.3. UI

---

Core

• Generation of VUS ref id and mapping from tx id(s)
• Creation and dispatch VUS messages to SEB

Adapters

---

How to handle things?

• Message loss?
• Exception