Versions Compared

Key

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

...

  •  A business overview of the product (i.e., FDC3 standards), its value to organization, and an explanation of what why businesses should implement it and/or
    use/buy software that does implement it -- in layperson’s terms. (Key Message: "Your firm should deploy trader desktop applications, tools, and platforms that
    comply with the FDC3 standards because...)
  •  A technical overview of the standards, including any overview of opinionation, preferred design patterns, coding conventions, etc.
  •  An explanation of how to get involved and contribute (with a link over to the wiki for more information on program/WG participation)
  •  An explanation of how the standards (i.e., different work group products) are intended to be used together but also how they can be implemented as a standalone
  •  A “getting started” guide / cookbook to implementing the standard
  •  Links to reference implementations

...

  • Developers and Technologists who might be interested in implementing a standard like FDC3 and/or will be expected to write code that leverages the standards
  • Product managers and business architects or of internal trading systems (either bought/deployed or homegrown/internally built)
  • Project managers within financial services organizations who implement trader desktop systems, applications, and tools
  • Executives and other project sponsors in the trading lines of business at banks
  • Product managers for fintechs and other software companies whose products might be good candidates to adopt, either wholly or in part, the FDC3 
  • Consultants who may implement, customize, and/or develop software that uses FDC3 at/for their clients


What Gets Written Where and For Whom?

...