Modelling the 'registration' process
This week has been focussed on modelling the data flows and trying to reverse engineer some of the service logic working backwards from the existing DARS prototype and the access that I have got to the DARS Online staging server and SDE platform.
This has involved meeting with some of the platform technical teams, and involved a fair bit of clicking backwards and forwards through the different stages of both the prototype and the live, or staged version of the services.
The need for this is driven by not having a clear single source of truth for the current routing or service logic for either the DARS service or the SDE service.
The need to understand, or be sure we have a clear single source of truth for the logics of both DARS and SDE is being driven by a desire to remove duplication from each of these journeys; specifically, that we aren't asking users for the same information in both of these, and also to develop a single source of truth about what data we are gathering from users.