Online
Health Monitoring System
Detailed Design: System Navigation
COP 4331, Fall 2014
Modification history:
|
Version |
Date |
Who |
Comment |
|
v0.0 |
|
G. H. Walton |
Template |
|
v1.0 |
|
Ethan Pitts |
First Revision |
Team Name: Team 14
Team Members:
- Jon Carelli - email - web page
- Chris McCue - email - web page
- Chris Chaffin - email - web page
- Ethan Pitts - email - web page
- David Gundler - email - web page
- James Luke - email - web page
Contents
of this Document
Trace of Requirements to Design
Design Issues:
The primary concerns in this
module are usability and reliability. The menu bar is a core system
functionality, which serves a dual purpose of providing quick and simple
navigation between major features of the system, as well as a context for the
user's current screen.
We believe that the menu bar is
the optimal way of navigating the system, because it provides separation of the
unrelated modules of the system without sacrificing accessibility of features.
The menu bar is static on the left side of the screen, and each box in the menu
bar will load a different module in the main viewer, which lies just to the
right of the menu, and covers most of the screen. To navigate to a new module,
the user clicks on one of the menu's boxes, each of which contain
an icon, which represents the associated module.
It is also necessary for the
user to have a visual indication on the menu bar, which allows them to know
which module is currently selected. We have chosen do to this by highlighting
the selected menu item by changing the background of the box from grey to a blue-grey.
The menu bar must also be reliable, and free of glitches. It is paramount that the correct modules be loaded when the menu item's box is clicked, since a failure to load the module means that that particular feature will be impossible to access. Given the nature of the system, that could result in injury or even death if a doctor cannot contact his/her patient with vital information.
Detailed Design Information:
System
Navigation Overview:
The design of the System
Navigation module is driven by functional requirements. Per the requirements, the user will be able
to quickly and easily access any of the available modules using the Menu Bar,
and view the module in the View Loader.
User
Interface Visualization:
At this point, it is helpful to
visualize the functionality-driven user interface.
Doctor
Mode:
Patient
Mode:
Operations:
See “System Navigation
Overview” section for operations and descriptions.
There are two main operations
that need to be noted. These are navigateTo(item :
int) and loadHtml(file : String).
The loadHtml operation takes
the relative file path to an HTML file, and loads that file in the View Window.
This allows us to have a separate HTML file for each module, which in turn
simplifies the development process.
The navigateTo operation is
called when a selection is made on the Menu Bar. The item's position number
that was selected is passed to the function. The menu item clicked should then
become "active," which is shown by changing the background color to a
grey-blue, and changing all other menu item's
background color to grey. The loadHtml operation should then be called to load
the corresponding HTML file into the View Window.
Interfaces:
Interface A: View Loader - The main area to the right of
the Menu Bar, where the different modules are loaded.
Interface B: Menu Bar - The navigational entity which
selects and displays which module is being used.
Event
Sequence Diagram:
The following sequence diagram
is a general sequence for any menu item 'x.'
Class
Diagram:
Trace of Requirements to Design:
|
Item
Description |
Detailed
Design Section |
Document
of Origin |
Sections
of Origin |
|
Patient Interface Navigation |
Specific Requirements |
Software Requirements Specification |
3.2 No. 10 |
|
Physician Interface Navigation |
Specific Requirements |
Software Requirements Specification |
3.2 No. 9 |
Template
created by G. Walton (GWalton@mail.ucf.edu) on
This
page last modified by Ethan Pitts (ethanempe@gmail.com) on