Background

These guidelines have been approved by the Use Cases Working Group in August of 2019.  They started as an 'opinionated' discussion document, followed by discussions, and then votes on what Use Cases (UC) the Working Group (WG) should accept. Having a set of agreed guidelines will provide provides two benefits :

• improve consistency in reviewing the use cases to accept in FDC3.
• The act of producing these guidelines should allow certain recurring points to be discussed and agreed once, rather than raising them in each UC discussion.

...

• reject a UC
• add the UC to their backlog
• indicate that the UC is already supported and show how the specification is used to deliver the UC.

But it is expected that the WG's will at least update the UC WG Confluence page with their decision and a brief 'reason'.

Please continue to engage with these Guidelines either by comments or by creating an alternative set of guidelines and referencing them in a comment on this page.

The Guidelines

In considering a use case, there are two separate questions to answer:

...

The following are points to consider in answer answering the two questions.

Is this a Valid Use Case?

...

• Is it a real UC for FDC3 Personas?
• Does it apply to areas of concern for FDC3? Or areas which may require inclusion in FDC3 (e.g. Mobile to Desktop workflows)?
• Is it unique from other UCs?

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

• A User running applications on a desktop
• A Technologist enabling a User to run applications (

Please see this

...

document

...

 for further details on

...

Personas/Participants.

The FDC3 areas of concern are :

• ‘to create standards for desktop application interoperability in the financial industry.’
• Help these standards to be used to help create applications that implement this interoperability. This is achieved by publicising the standards and by offerings products and services that help with the FDC3 application delivery. These products may be open source and/or commercial. 

Is this a Useful Use Case?

In general a useful use case is one that will help solve interoperability issues found among members of FDC3 and will therefore, by definition, be a test case for the specifications being defined in other working groups.

Some specific questions to consider are :

...