Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Page content:

User Stories

This is what came out of a session between PO and Data manger and BA to flesh out high-level stories for the migration of Northern Ireland data onto TIS and onboarding of the users. These might need to be further refined and broken down to smaller stories by devs.

Item no.

User Story

Acceptance Criteria

Comments

1

As a Northern Ireland Admin
I want to be able to access to TIS
So that I can manage Northern Ireland training processes

Given Northern Administrators are currently using Intrepid V10
When specific Roles for the NI users have been created on TIS
And they have appropriate the appropriate permissions
Then they should be able to access TIS and Manage their training data

Given I am a NI TIS Admin
When I access TIS
Then I should be able to see trainees that have trained in NI before, or is currently training in NI or is going to train with NI in the future

Given I am a NI TIS Admin
When I access TIS
Then I should not be be able to see trainees that have NOT trained in NI before and is NOT currently training in NI and is NOT going to train with NI in the future

  • New Role/s definitions that will be required for NI
    NIMDTA Admin
    Any others?

  • Permissions-based access to Northern Ireland specific Data (c.f. similar to HEE Trust Admins roles)

  • Taxonomisation/Categorisation of Nations in addition to Local Offices

  • Avoid duplication of trainees data where they happen to have Programmes in both HEE and NI

  • An approach to Ownership of Data in the TIS model that is scalabable

2

As a Northern Ireland Admin
I want NI data to be migrated to TIS
So that I can access Northern Ireland specific Data on TIS and comply with Information Governance for Northern Ireland

  1. NI TIS Admins to have Access to Northern Ireland Specific data for:

  • People

  • Posts

  • Programmes

  • Placements

  • Rotations

  • Reference data

  • No duplication of data between HEE and NI

  1. Merge Rules to be applied pre-migration and migrate data to TIS as defined here:
    https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/1375469590/Data+alignment#Merge-Rules

  2. No duplicates to be created across TIS and NI data including Reference Data
    https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/1375469590/Data+alignment#Merge-Rules

This story is to:

  1. Migrate Northern Ireland data from Hicom NI Data Repository to TIS:
    Data alignment

  • People

  • Posts

  • Programmes

  • Placements

  • Rotations

  • Reference data

  • No duplication of data between HEE and NI

2. Research and come up alternatives for:

3

As a NI Admin
I want to have access to HEE National Data Warehouse (NDW)
So that I can run reports on NI specific data

  • How to send NI data to NDW? Existing ETL’s?

    • Data to be only accessible in NDW to NI Admins

  • NI data not to feed back to Intrepid vis the NDW-Hicom ETL?

    • Depending on whether it will be a clean cut-over from Intrepid to TIS

Jira Tickets

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  • No labels