Requirements for each project
Initial Requirements
The website should abide by the NHS website design guidelines. Within the website there will be examples of components that developers are able to use within the Peach project, ensuring the ability to integrate work. There will also be guidelines regarding design elements according to the client’s preferences. It will be reactive and compatible with mobile devices. The site should also be easily updated with regards, for example, to the list of components as new PEACH specific components are built and become available. The client also wishes for the site to be static, utilising Middleman.
The form renderer will accept a markup file (created by the form generator) and create a form artifact using the library of UI components. It will also have the function of pushing input data to the backend database. If the user attempts to input inappropriate data formats, there should be means of rejecting this and correcting the user behaviour. The renderer should also be scalable.
The dashboards are to be linked with the backend database and output data. Primarily, the dashboards will be means to visualise data through basic graph types, however these graphs will also be interactive, allowing the user to view more information about the data. The site is to be dynamic, and users will be able to use advanced, custom graphs to visualise data.
Although initially we were tasked with cleaning up of this functional application in preparation for publication, soon afterwards this subproject was removed from the team’s remit.
Gathering Requirements
The requirements for this site are mostly given by the client with regards to design preferences. For component and framework lists, the requirements will be ascertained by consulting with the other PEACH development teams so as to find which technologies are preferred for development.
The requirements for this component are dependent on how team 41 approach the form generator, as the two components will interact heavily. What type of data is to be pulled from the markup files and how it is to be requested is another question to put to the client.
How NHS professionals wish for data displayed and how they are to interact with it may vary hugely across medical specialties, therefore thorough requirements regarding detail such as what types of graph are preferred and when, can be answered by surveys put to the staff of UCLH.
Surveys and interviews conducted amongst radiologists working at UCLH would be ideal as they are the target users of the application.
Tags
background research testing dashboard plans for term 2 our project architecture research