Programmes - Schools Field Validation & Scenarios DRAFT

Background

Schools are TBC

Scope for TIS

Act as Reference Data
Available as labels / drop downs within relevant components in the Admin UI
Editable by the local office and data leads
Functionality should include -
- create school
- view/edit school
- remove school

Currently << TO BE REVIEWED BY DATA LEADS

users can associate schools with Programmes
a Programme can be assigned to only one / multiple Schools
Trainees/trainers never sees the School, so no impact to them

Field Validation

Field Sequence

Field name (V10)

DR field

Reference table

Example value

Other fields available in DR

Type (free text, drop down, check box) & Interaction

Mandatory (Y/N)

Validation / Error Messaging

Filter (Y/N)

Search (Y/N)

Sort (Y/N)

Summary (S) / Detail (D)

Notes

Delete (Y / N)

1

School Name

Free text

Y

Must be unique
limit to 25 characters

N/A

2

Programme Name

Smart search drop down

Y

Must select 1

N/A

3

Programme Number

Derived from programme name

Y

Must select 1

N/A

4

Local Office Owner

Drop down

Y

must select 1

N/A

5

School Status

Drop down

Y

Must select 1

N/A

6

Start Date

Calender picker

Y

Must select 1

N/A

7

End Date

Calender picker

Y

Must select 1

N/A

8

Sites

Smart search drop down

N

Can add multiple

N/A

Scenarios

Process Name	PG-1 Create School	Comment
Description	User creates the School grouping so that this can be used elsewhere in TIS
Actors	HEE Admin
Pre-Conditions	Programmes must be defined User must have appropriate access
Post Conditions	School group created and available to be reported against
Process Steps	Navigate to reference data space Select to create new Enter all mandatory fields School name Programme name Programme number (autopopulated) Local Office Owner Status Start Date End Date Save New School grouping is available within DW
Alternative Flow	N/A
Rules	name is free text limit to 25 characters must be unique
JIRA Reference	TISDEV-3247 - Getting issue details... STATUS TISDEV-3248 - Getting issue details... STATUS
Audit Log	Create record - who / when

Process Name	PG-2 View / Edit School	Comment
Description	User should be able to view and make edits to existing School groupings
Actors	HEE Admin TIS Admin
Pre-Conditinos	Programmes must be defined User must have appropriate access
Post Conditions	Changes saved to already created School
Process Steps	Navigate to reference data space Select field to be edited Make changes Save
Alternative Flow	N/A
Rules	Changes can be made to name or programme link Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc
JIRA Reference
Audit Log	Edit record - who/when

Process Name	PG-3 Remove Schools	Comments
Description	User should be able to remove a Rotation grouping
Actors	Programme / Placement Admin
Pre-Conditions	Programmes must be defined User must have appropriate access
Post-Conditions	School removed from Reference Table
Process Steps	Navigate to reference data space Select field to be edited Change status to inactive Save
Alternative Flow	N/A
Rules	N/A
JIRA Reference
Audit Log	Delete record - who/when

For Discussion

#	Question	Comment	Owner
1	Are schools purely required for reporting puroses?
2	Do they need to be displayed anywhere else on TIS? Does it require more functinality than is described above? i.e. to support educational training?
3	Does school need to be displayed within a Programme form?
4