| Page Properties | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Goals
- Simplify the user experience
...
The new user interface has low acceptance. This page documents items features that need improvement.
Assumptions
- Users will access Oscar EMR via web browser in desktop or tablet
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | ||||
| 2 |
User interaction and design
...
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
How to make sure the old and new UI performs the same exact functionalities? How much work is it to document use cases and generate Selenium test against them in the old and new UI? | |
| Can we add use of Google's lighthouse audit to test performance of UI and incorporate best practices to speed up the pages? | |
Beside performance, should we add analysis of business use cases and their overall connections (workflows) (Or a "project map" according to google's guide below) to ensure UI transition between pages and dialogs is user friendly? https://developers.google.com/web/fundamentals/design-and-ux/ux-basics Should we investigate if there is a tool to auto generate screenshots workflow of a web application to help make decisions. | |
| While considering new UI, what about considering mobile/responsive UI? |