Versions Compared

Old Version 4

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Background 

Schools are TBCcreated in order to link Heads of Schools to Programmes and enable reporting


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 SchoolsTrainees/trainers never sees the School, so no impact to themSchools at a single point in time
  • Schools should be displayed within Programme membership of a Person record



Field Validation

Field SequenceField name (V10)DR fieldReference tableExample valueOther fields available in DRType (free text, drop down, check box) & InteractionMandatory (Y/N)Validation / Error MessagingFilter (Y/N)Search (Y/N)Sort (Y/N)Summary (S) / Detail (D)NotesDelete (Y / N)
Reference Table
1School Name
vwProgrammeSchool

  • Free text
Y
  • Must be unique 
  • limit to 25 characters
N/AN/AN/AN/AN/AN/A
2Programme NameSmart search drop Local Office Owner
vwProgrammeSchool

  • Drop down
Y
  • Must must select 1
N/AN/AN/AN/AN/AN/A
3School StatusProgramme Number
Derived from programme namevwProgrammeSchool

  •  Drop down
Y
  • Must select 1
N/AN/AN/AN/AN/AN/A
4Local Office OwnerDrop School Number
vwProgrammeSchool

  • Smart search drop down
Ymust select 1N
  • free text
N/AN/AN/AN/AN/AN/A
5School StatusType
vwProgrammeSchool

  •  Drop drop down
YN
  • Must select 1
N/AN/AN/AN/AN/AN/A6Start Date
  • Calender picker
YMust select 1N/AN/AN/AN/AN/AN/A7End Date
  • Calender picker
Y
  • Must select 1
N/AN/AN/AN/AN/AN/A8Sites
  • Smart search drop down
N
Can add multiple6Head of School
vwPerson

  • smart search drop down
N
  • only select from trainer list




It may no be possible to differentiate between role types i.e. Trainer v Trainee
Programme Form
N/ASchool Name



  • drop down
N
  • can only be selected from list
N/AN/AN/AN/AN/AN/A




Scenarios

Process NamePGSC-1 Create SchoolComment
DescriptionUser creates the School grouping so that this can be used elsewhere in TIS
ActorsHEE Admin
Pre-ConditionsProgrammes must be defined

User must have appropriate access


Post ConditionsSchool group created and available to be reported against
Process Steps
  1. Navigate to reference data space
  2. Select to create new
  3. Enter all mandatory fields
    1. School name
    2. Programme name
    3. Programme number (autopopulated)
    4. Local Office Owner
    5. School Status
    6. Start Date
    7. End DateSchool Number
    8. School Type
    9. Head of School
  4. Save
  5. New School grouping is available within DWacross TIS as a reference value

Alternative FlowN/A
Rules
  • name is free text
  • limit to 25 characters
  • name / number must be unique

JIRA Reference

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-3247
Jira Legacy
key
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
TISDEV-3248


Audit Log
  • Create record - who / when



Process NamePGSC-2 View / Edit SchoolComment
DescriptionUser 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 ConditionsChanges saved to already created School
Process Steps
  1. Navigate to reference data space
  2. Select field to be edited
  3. Make changes
  4. Save

Alternative FlowN/A
Rules
  • Changes can be made to name or programme linkany/all fields in the record
  • Display warning message displayed to warn user of potential impact to previously/already linked Programmes, Trainees, Posts etc

JIRA Reference

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-3889


Audit Log
  • Edit record - who/when



Process NamePGSC-3 Remove SchoolsSchool Record from Reference ValuesComments
DescriptionUser should be able to remove a Rotation groupingSchool
ActorsProgramme / Placement

TIS Admin

HEE Admin


Pre-ConditionsProgrammes must be defined

User must have appropriate access


Post-Conditions

School removed from Reference Table


Process Steps
  1. Navigate to reference data space
  2. Select field to be edited
  3. Change status to inactive
  4. Save

Alternative FlowN/A
RulesN/A
JIRA Reference
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-3890

Audit Log
  • Delete record - who/when


Process NmeSC-4 Assign School to Programme
DescriptionUser should be able to assign a school to a Programme record
Actors

HEE Admin

TIS Admin


Pre-Conditions

Schools must be defined

Programme must be in creation or already defined


Post-ConditionsSchool is associated with a Programme
Process Steps
  1. Navigate to Programme record (create or edit journey)
  2. Select School from drop down menu
  3. Save to add School association

Alternative FlowN/A
Rules
  • only one 
  • must be from drop down list

Jira Reference
Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTISDEV-3891

Audit Log
  • added - who/when
  • removed - who when
  • amended - who/when




For Discussion

#QuestionCommentOwner
1Are schools purely required for reporting puroses?No, also for reference to Trainees and Trainers
2Do they need to be displayed anywhere else on TIS? Does it require more functinality than is described above? i.e. to support educational training?
  • Programmes should display the school reference
  • Schools should be displayed within Programme Membership L3 for Person record (trainees & trainers)

3Does school need to be displayed within a Programme form?Yes (see above)
4