FDC3 Business Analyst Persona
- Dominant language
- TypeScript
- Stars
- 270
- Forks
- 194
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 36
Description
## Overview
Discovery exercise to understand the **Business Analyst** user personas within financial services that would be a user of FDC3.
### Additional Context:
Exercise to break down this list and investigate further. The spreadsheet can be [found here](https://docs.google.com/spreadsheets/d/1b506f6v2TFlKHlkhry4CMa1pbMOAP3-biwJJr9gwYAU/edit#gid=394965526).
- Is it a Context linking use case or is it an Intent use case typically?
- What Intent would you use? What's the natural Context?
By running through the above we can quickly identify where the gaps are with the FDC3 Standard
### Contribute
Contributions are welcomed to this issue.
**Add further workflows that are related to the Business Analyst for any use-cases you are trying to build on FDC3.**
Contributor guide
Research direction
Start with the linked spreadsheet and review the Business Analyst workflows it lists. For each workflow, identify whether it uses FDC3 Context linking or an Intent, record the natural Context or Intent, and document additional workflows and gaps in the FDC3 Standard.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100