Field Guide 4 · Business Analysis · Companion ArtefactFirst Edition · 2026
A worked example of the methodology
The artefact the system produces
An end-to-end service-journey, process and integration model for a Core HR transformation — built from a working JIRA dataset of 426 items. This is what falls out the other end when the requirements engineering system described in the companion guide is put in place: a scrutable, traceable, navigable picture of the work.
13
Service journeys
426
JIRA items
310
Requirements
11
Value streams
40
Systems
Worked example · Core HR transformation
What the method produces
Core HR System is replacing fragmented Document Management System, Word and Excel-based processes across recruitment, onboarding, position management, access provisioning, pay, and reporting. This artefact maps the resulting service journeys, integrations and traceable requirement set — 5 workstreams, 13 approved journeys, 310 logged requirements, all anchored to the hierarchy and naming conventions described in the field guide.
Value streams
11 HR value streams covered by the 310 requirements. Click any pill to filter the Requirement Explorer to that stream.
Stakeholder groups (32 groups across 310 requirements)
Click any group to see all requirements that impact them in the Req Explorer.
Cross-cutting systems & journeys
Systems and journeys referenced most across requirements — highest integration complexity. Click any row to explore matching requirements.
Workstreams
Requirement priority breakdown
Click any card to filter Req Explorer.
Service journey index
The 13 approved service journeys. Each ticket reference is a stable name in the traceability set — see the journey, process, architecture and explorer pages for detail.
Click any journey name to open it in JIRA. Click any phase to see its detail and linked requirements. Filter by value stream, workstream, or status.
Filter
Approved
In review
In progress
To do
Backlog
Process Detail
Phase-level swimlane maps
Each tab covers one capability cluster. Click any chip to open its JIRA ticket. Chip colour = requirement type.
Must have
Should have
System touchpoint
Handoff / trigger
Current-state pain point
Recruit to Hire
New Starter
JML Access
Position & Pay
Workforce Change
Pay & Reporting
System Architecture
Platform tiers & integration patterns
Core HR System = single source of truth. Integration Platform carries all integration traffic. Workflow Platform orchestrates fulfilment. Identity Platform is the authoritative IAM — not Workflow Platform. Click any system box to explore its requirements.
Record layer
Core HR System (HRIMS)
Position · Person · Org structure · Default access profiles · 292 reqs
Identity Platform
Identity authority — NOT Workflow Platform · SSO · Auth
Directory Services
RBAC · Security groups · 56 reqs across 6 journeys
Payroll System
Pay source of record · 142 reqs across 12 journeys
position events + effective dates + person data
Integration
Integration Platform
Events · APIs · Data pipelines · Data Lake feed · 60 reqs across 10 journeys
Position data (FTE, cost centre, classification, reporting line) auto-populates requisitions, JML triggers, and downstream systems. Managers cannot override at the requisition level without upstream position approval. 292 of 310 requirements reference Core HR System.
Identity Platform = IAM authority (not Workflow Platform)
Workflow Platform orchestrates and captures audit evidence but is not the IAM platform. Identity and access flows Core HR System → Identity Platform → downstream. Workflow Platform's role is orchestration and evidence only (per CHR-433 discussion thread).
Effective-dating is non-negotiable
Every position change, pay movement, increment, restructure, and working arrangement must be effective-dated. Future and back-dated changes must be supported without inconsistency across payroll and access. Present across all 12 approved journeys.
Document Management System / Word / Excel → retire
COI forms, screening templates, interview guides, reference check evidence, background check citations currently in Document Management System as Word/PDF. Every approved journey moves these in-system to Core HR System. 24 requirements explicitly reference legacy document management retirement.
SJ8 · JML Access Provisioning · 32 reqs
Joiner / Mover / Leaver event flow
Position-based RBAC anchored in Core HR System. A single effective-dated position event fans out via Integration Platform into three distinct Workflow Platform workflows, then converges at Identity Platform before reaching downstream systems. Click any step to open the JIRA ticket.
Core HR System — position event
Position stores access + hardware attrs (CHR-230) · mapped to Identity Platform roles (CHR-231) · dual role/overlap controlled (CHR-232)
pre-effective + effective-dated trigger (CHR-234)
↓
Integration Platform — trigger hub
Distinct J/M/L event types (CHR-235) · cancel + date-change rollbacks (CHR-236) · single front door for JML (CHR-237)
Joiner ↓Mover ↓Leaver ↓
Joiner path
Workflow Platform new starter case created
Auto Day 1 provisioning from position profile (CHR-239)
Baseline vs high-risk access split (CHR-240)
Training prereqs for sensitive roles (CHR-241)
Bulk joiner handling for cohort intakes (CHR-243)
Mover path
Workflow Platform mover case created
Auto grant new + remove old access (CHR-244)
Prevent access creep (CHR-245)
Controlled dual access for handover (CHR-246)
New position readiness confirmed (CHR-247)
Leaver path
Workflow Platform leaver case + checklist
Termination date drives full deprovisioning (CHR-249)
HR + IT offboarding alignment (CHR-251)
Early cutoff for walked leavers (CHR-253)
Vargo audit evidence trail (CHR-255)
↓↓↓
↓
Identity Platform
Group membership set/removed atomically · Role assignment from position profile · Account disable on leaver effective date
From a candidate finding an ad through to leaver deprovisioning. Each arrow shows the specific system event or status change that passes control between journeys. Click any block to filter the Req Explorer to that journey's requirements.
Derived directly from System(s) Impacted field across all 310 requirements. Numbers show actual requirement counts. Click any system name to filter Req Explorer. Click a journey header to open its JIRA epic.
Present (with req count)
Indirectly referenced
Most cross-cutting systems
Click any card to filter the Req Explorer to requirements referencing that system.
Requirement Explorer
Slice & dice all 310 requirements
Filter by value stream, system, stakeholder, type, MoSCoW, assignee, or status. Click any row for full detail including user story, trigger/outcome, and traceability metadata. Filter chips are additive (AND logic).
Filter by
Key
Summary
MoSCoW
Type
Value streams
Status
Assignee
Business Experience Layer
Service journey deep-dives — process, roles & triggers
60 Business Processes across 13 journeys — each with inputs/outputs, step-by-step process flows, RACI roles, scope boundaries, and linked requirements. Click any phase card to expand its full detail.
Integration Catalogue
System integration flows & requirement mapping
60 system-to-system integration pairs derived from requirements data. Each card shows the integration pattern, requirement count, linked journeys, and hypothetical message flow. Click any pair to explore its requirements.