SENSE UI STATEMENT

Statement of how the UI fits into the application

• How it fits into the design

• Approach to be used

• Put this into your repository

Our application is UI-centric, the UI drives the application and we are generally designing the UI first. We have three separate user-interfaces: Sherpa, IQSign, and ALDS. Sherpa’s interface is finished, and is currently being left untouched.

IQSign

The main goal of SENSE is to display the user’s status based on sensors and rule-based triggers. The user-interface for IQSign is pivotal to the application. IQSign allows users to edit what signs are displayed, allowing for the final product to be more personalized towards the users and allowing every user self-expression.

Although the backend is already implemented, the UI team has decided to enhance the iQSign portal with a UI-first development approach. Our approach included identifying the existing operations, and gathering user feedback to determine the final design. We identified the following operations that should be available through the iQSign UI:

Add new Sign Templates (Background)

Update Sign Design

Use Profile

View Sign in different formats (web, image)

After identifying the main operations, we started building our UI prototype to support these operations. In upcoming sprints, we will update the necessary backend components to implement the new UI flows.

This front end will be coded with React.js and Javascript.

ALDS

[ how does the ALDS UI fit into the software system as a whole ]

[ what are the main operations in the UI ]

[ what approach will be used to build UI ]