| Introduction | Human Interface Target List | Scenario1, 2, 3 | Log Files |
| Observation | Recommendation |
| Users were disoriented by the lack
of a consistent look to the interface across the various areas of the
product. Some users thought that they were opening up a new window
when they traveled to a different place in the product by clicking on the
top menu bar.
|
Keep a consistent look and feel to all the navigation elements throughout the product. Allow the users to decide if they want to open or shut the side pane. |
| Some of the higher level users were uncomfortable with the percentage of real-estate taken up by navigation elements. | Move most of the elements to a closeable side pane. The icons for each section take up a lot of space. These could be pulled out to give more room to content. |
| High level users wanted to have
more control over the log's message fields. They wanted some way to
shrink down what is currently exposed and offer a way to get to the
details if requested.
|
This is not currently a great concern, but it maybe something to take into consideration as the product grows. |
| One user felt that the side pane should be labeled "navigation window" instead of "logs". | This issue shows that there is some confusion about the relationship between the top and side pane navigation. If the navigation was more consistent, these issues would fade. |
|
BUG: The top navigation pane crashed anytime users resized the screen.
|
Development has fixed this bug. |
| In the logs sections of the product, high level users wanted list control functionality. They wanted to be able to sift through the logs by sorting by column. | This functionality would be very powerful for users. It should be considered a priority for the next version release. |
|
One user pointed out a security concern. If security is NT based,
"What if I was to walk away from my machine? My security is
exposed."
|
This user came up with an interesting idea of pushing the overview or customizable home page to a screen saver. That way all the users can view the system before logging in. |
|
One user noticed the truncated text in the audit log area of the
product. He continued to point and click on it, trying to view the
missing text.
|
On UE's recommendation, development has provided tool tip text tip solve this problem for now. |
This is a shot of the overview screen before development made changes based on more UE feedback and user testing.
This is a shot of the event logs screen before development made changes based on more UE feedback and user testing.
This is a shot of the audit logs screen before development made changes based on more UE feedback and user testing.
This is a shot of the Guardian MD screen before development made changes based on more UE feedback and user testing. Notice the side pane disappears.
This is a shot of the overview screen after development made changes based on more UE feedback and user testing.
This is a shot of the event logs screen after development made changes based on more UE feedback and user testing.
In section 1 you will be touring the screens in the (product) Client application and setting up for later sections. Most of section 1 consists of viewing the different screens in the (product) Client and understanding what information is available on them. You will also be using the Add New wizard to add a shortcut to the Launch Pad. This will prepare your (product) Client for sections 2 and 3 of the lab.
In lab section 1, you will learn abou
t: | Logging in to the classroom network |
| Starting the (product) Client |
| (product) Client menu options |
| (product) Client toolbar and information bar |
| (product) Overview / Health screen |
| Logs screen |
| (product) screen |
| Launch Pad screen |
| Reports screen |
| (product) screen |
| Introduction | Human Interface Target List | Scenario1, 2, 3 | Log Files |