Story: Write the journey extraction standard and the ores.refdata journeys
Table of Contents
This page documents a story in Sprint 26. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
1. Goal
The User Journey Extraction Standard is written, and its first run documents the ores.refdata journeys, with every action its Qt screens offered covered by a journey or recorded as dropped. This was the second pass of the sprint 26 mission; the UX is built from these journeys in the third, and the remaining components split to Extract the remaining component user journeys at the sprint 26 close on 2026-10-05.
The method is the User Journey Extraction Standard, written from the sprint 25 IAM journey work and extended with a pass over the legacy Qt screens. Each component runs it after its codegen clean-up story, because the coverage tables check each operation against the generated protocol.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 26 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-05 |
On 2026-10-05, at the sprint 26 close, this story was reworded to the standard and the ores.refdata journeys it delivered and closed DONE. The thirteen remaining component tasks moved to Extract the remaining component user journeys.
3. Acceptance
- The User Journey Extraction Standard is written.
- The ores.refdata tasks below are DONE: its journeys are documented, its Qt actions all have a disposition, and its defects and gaps are recorded.
4. Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Write the user journey extraction standard | DONE | 2026-09-23 | 2026-09-23 | Generalise the sprint 25 IAM journey work into a checklist every component with a UX can follow, including the legacy ores.qt screens. |
| Extract the ores.refdata user journeys | DONE | 2026-10-04 | 2026-10-04 | Run the User Journey Extraction Standard for ores.refdata, reading its legacy screens in ores.qt/refdata. |
| Write the remaining ores.refdata user journeys | DONE | 2026-10-04 | 2026-10-04 | Write the nine refdata journeys the agreed catalogue still lacks: currency pair, desk groups, counterparty onboarding, party details, book structure, conventions and tenors. |
5. Scope
Only components that had screens in ores.qt run the standard. From
the Qt tree: scheduler, workspace, workflow, iam, refdata,
analytics, compute, reporting, synthetic, marketdata (with
mktdata), dq and trading, plus the application shell. api holds
shared widgets and is read with the shell; headless has no screens.
The other components never had a UX.
The order follows the codegen clean-up order, so each component's journeys start once its clean-up is done. The application shell runs last, because it composes the other journeys.
| # | Component | Qt .ui files |
Qt window headers | Task |
|---|---|---|---|---|
| 1 | ores.scheduler | 2 | 9 | Extract the ores.scheduler user journeys |
| 2 | ores.workspace | 2 | 4 | Extract the ores.workspace user journeys |
| 3 | ores.workflow | 0 | 4 | Extract the ores.workflow user journeys |
| 4 | ores.iam | 12 | 33 | Extract the ores.iam user journeys |
| 5 | ores.refdata | 61 | 194 | Extract the ores.refdata user journeys |
| 6 | ores.analytics | 4 | 12 | Extract the ores.analytics user journeys |
| 7 | ores.compute | 14 | 45 | Extract the ores.compute user journeys |
| 8 | ores.reporting | 4 | 12 | Extract the ores.reporting user journeys |
| 9 | ores.synthetic | 8 | 31 | Extract the ores.synthetic user journeys |
| 10 | ores.marketdata | 1 | 18 | Extract the ores.marketdata user journeys |
| 11 | ores.dq | 27 | 68 | Extract the ores.dq user journeys |
| 12 | ores.trading | 17 | 11 | Extract the ores.trading user journeys |
| 13 | ores.qt application shell | 2 | 22 | Extract the application shell user journeys |
6. Decisions
- One story, one task per component. Journeys are grouped by topic, not by component, so a task's journeys may land in groups other tasks also use.
- The Qt screens are evidence, not a design. They are read so that no action a person had is lost without a decision; the journeys still start from the person's goal.
7. Out of scope
- The prototypes and the UX build, which is the third pass.
- The Wt client, which was removed with the Qt client.