Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourYellowGreen
titleIN REVIEWAccepted

On their desktop, this user has: 

...

The user receives a message in the chat application containing an instrument identifier for Tesla. They want to do some analysis on Tesla and so see what applications are available through right clicking on the identifier for Tesla. They have the option to launch an app in their proprietary platform, or in the third party platform. 

Workflow 2

The user decides to launch an app in the proprietary analytics platform.

...

wants to see internally created and shared information on Tesla and so launches a proprietary research app that opens showing internal research published on Tesla. 

Workflow 3

The user wants to do further analysis on Tesla and so launches a third party research app and analytics platform that opens showing internal research financial statements and calculated financial data (such as market capitalization, P/E ratio, growth rate, earnings margins, etc)  and 3rd party research documents published on Tesla that they are entitled to access

Workflow 4

The user decides thatthey that they want to do some technical analysis. The third party analytics platform has an integration with the third party charting application and the user launches the app, which opens in a browser window.

Workflow 5

The user wants to see information about another competitive international automobile company such as BMW.  The user changes the selected identifier from Tesla to BMW in one app in the third party platform and the open applications, including the charting application, change to show information on BMW instead of Tesla. 

Workflow 6

The user adds BMW and Tesla to a shared group of companies (aka a Watchlist) named "Automotive comparables" to a list within the watchlist This group of companies is shared with all applications which use this group for any comparative analytics.

Possible to meet workflow using Broadcast, but not fully fit for purpose. 

API would need to be extended to support channels. 

Need to have FDC3 specific channels eg 'FDC3 Blue' and 'FDC3 all' - default channel 

Option to declare which types the app wants to listen to 

Interoperability Points

  • API
  • Intents
  • Context