FDC3 Persona/Participant Definition

FDC3 Participant or an FDC3 Persona (as used in the Use Case Acceptance Guidelines document) is defined as someone working with :

• A Member of the FDC3
• Financial industry firm.
• Product Vendor supplying end-user Platforms or Applications to the Financial Industry.
  An example might be ChartIQ. 
  Their applications will typically be run at multiple companies, all of whom are running the same code. 
• Platform Vendor supplying products or services to developers producing end-user Products/Applications.
  Examples might be companies like OpenFin, Glue42 and Plexus (even though DB also provide end-user applications).
  These products are often not visible to the User but they can are used to make the production of FDC3 compliant applications easier.
  

Valid Personas are used to introduce a use case, typically using the words 'As a <persona> ...'. Valid Persona for FDC3 UCs are:

• A User running applications on a desktop
• A Technologist enabling a User to run applications.  A Technologist could be:
  • In-House Developers and Architects and Business Analysts (BAs) producing in-house applications the users run.
    The people are often working in-house either as employees or consultants. 
    A key differentiator is that their applications are typically only used in one company
  • Product Developers and Architects and BAs working in a Vendor to design, implement, install and configure the Platform or Application for a User.
  • Vendor Developers and Architects and BAs working in a Vendor to design and implement the products and services that can be used by In-house Developers and/or Product Developers. 
  • CTOs, BAs, and other enablers of Users's business needs.