Group 37

Updated: 04/12/2016

Background Research: Form Renderer

Introduction

This part of the project is concerned with the application which will be used to retrieve information about patients, communicate between staff and many more. Our task is to establish the connection between markup files and the user interface to display data upon request. Therefore, our team was performing two tasks at once:

Communicating with other teams in the Cancer distribution, ensuring the final integration will be delivered on time and will be compatible with the other parts of the application

Closely working with Team 41 which is responsible to make templates which are then transformed into markup files and used by our team to retrieve the data

Furthermore, our team was reviewing the files provided by the client which have the requirements for the application defining its architecture, workflow and other processes. However, we found most of the documentation to be irrelevant to our specific task. Therefore, our main approach is to continue close development with the other teams, as we are working on a front-end and therefore our solution is highly dependent on the output produced by Team 41, and to allow safe integration with the rest of the application.

Features

Name of the feature: User interface (UI)

Part of the project: Form Renderer

Use case: The users of the application will be accessing the information using the UI specified by our team.

Limitation: In return, our UI will be linked to the markup file and therefore limited to the information that markup will be able to deliver.

Name of the feature: Connection with the markup

Part of the project: Form Renderer

Use case: This is the actual connection between user interface (UI) and markup file used to retrieve the data.

Limitation: We need to ensure safe and secure connection which retrieves the data, or displays an error in case of any difficulty. This may be a limitation as due to constraints in the connection.

Name of the feature: Edit information

Part of the project: Form Renderer

Use case: Allow users to edit markup via simple user interface (UI) means which would not need any prior programming knowledge.

Limitation: There might be limitation in terms of how the other team defines the data that can be received. This may require certain restrictions in the UI to ensure users do not cause any server crashes.

Name of the feature:	User interface (UI)
Part of the project:	Form Renderer
Use case:	The users of the application will be accessing the information using the UI specified by our team.
Limitation:	In return, our UI will be linked to the markup file and therefore limited to the information that markup will be able to deliver.

Name of the feature:	Connection with the markup
Part of the project:	Form Renderer
Use case:	This is the actual connection between user interface (UI) and markup file used to retrieve the data.
Limitation:	We need to ensure safe and secure connection which retrieves the data, or displays an error in case of any difficulty. This may be a limitation as due to constraints in the connection.

Name of the feature:	Edit information
Part of the project:	Form Renderer
Use case:	Allow users to edit markup via simple user interface (UI) means which would not need any prior programming knowledge.
Limitation:	There might be limitation in terms of how the other team defines the data that can be received. This may require certain restrictions in the UI to ensure users do not cause any server crashes.

Existing Solutions

This sub-project is new to the Peach project, so there is no previous information to draw upon. With regards to the “Edit information” feature, HTML5 readily supports user editing of the markup file, via the ‘contenteditable’ attribute. However, there may come some difficulty in restricting user input and correcting user behaviour. Extracting data from HTML files is a fairly common practice known as ‘web scraping’ and there exist numerous tools (such as ‘Beautifulsoup’ for Python) that allow data to be pulled from a markup files via tags.