Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added UC17 for review and vote #153

Merged
merged 7 commits into from
Jan 16, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/assets/uc17.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion docs/use-cases/004-client-side-fx-trader.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ layout: use_case
1. The FX Trader clicks button to book a trade in the third-party trading app (e.g. Autobahn FX)
1. The trading app executes an interop action to the client in-house proprietary credit check application to check the trader's credit limit. If this check indicates the limit has been reached, the trading app presents a rejection dialog as a standard error dialog box with an informational message which may be a standard message (e.g. "Credit Limit Reached") or may include an interop link/action (provided by the credit check application) to resolve the limit breach.

![Use Case 4 Workflow](assets/uc4.png)
![Use Case 4 Workflow](../assets/uc4.png)

## Required Features

Expand Down
2 changes: 1 addition & 1 deletion docs/use-cases/005-buy-side-treasurer.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ layout: use_case
1. A Corporate Treasurer enters or chooses the required trade parameters in an aggregator app which then sends requests to different providers to subscribe to rates updates
1. The aggregator app shows screen with all the rates received from the running provider apps and updates them in real-time as soon as provider sends new rate.

![Use Case 5 Workflow](assets/uc5.png)
![Use Case 5 Workflow](../assets/uc5.png)


## Workflow 2
Expand Down
33 changes: 33 additions & 0 deletions docs/use-cases/017-fine-tuning-interop-with-channels.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
---
id: uc-17
title: "Use Case 17: Fine-tuning InterOp with Channels"
sidebar_label: 17. Fine-tuning InterOp with Channels
layout: use_case
---

## Persona
A user in a multi-monitor desktop environment with a fairly hectic, time-sensitive and unpredictable working day based on market movement and interactions with clients and colleagues.

## User Goal
I want to be able to create "siloed" workflows on my desktop so that I can quickly switch context to serve a client or execute a trade while still keep an eye on the general market.

## Preconditions
The end-user's app desktop environment consists of:
- an FDC3 compliant in-house application
- several FDC3-compliant vendor applications

## Workflow 1
The user's organisation maintains a coverage list in the in-house application. When selecting a company in there, the user wants a chart and a news component to update in vendor application 1, an options montage to update in vendor application 2.

## Workflow 2
In vendor application 1, the user maintains a personal watchlist. When selecting a company in there, the user wants a research portal in vendor application 3 to update as well as a trading screen in vendor application 4.

## Workflow 3
In vendor application 2, the user have a tool for ad-hoc company look ups. When selecting a company there, the user wants a chart and a news component in vendor application 1 to update (not the ones from WF 1), a detailed company report in vendor application 2 and a separate trading screen in vendor application 4 (not the one in WF2).

![Use Case 17 Workflow](../assets/uc17.png)

## Interoperability Points
- API
- Context
- Financial Objects Program