Browse Prior Art Database

Dynamically Adjusting a User Interface Based Upon Origination Point and Availability of Data Disclosure Number: IPCOM000218081D
Publication Date: 2012-May-18
Document File: 3 page(s) / 57K

Publishing Venue

The Prior Art Database


Disclosed is a method to extend the usability of a user interface through more intelligent customization.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 43% of the total text.

Page 01 of 3

Dynamically Adjusting a User Interface Based Upon Origination Point and Availability of Data

Most user interfaces (UI) are designed to be "one size fits all". However, this philosophy often fails as applications are being used by many different users for many different tasks, bringing with them varied levels of expertise, different sets of expectations, and different sets of goals. User interfaces are often developed, delivered to the customer, and then grow in functionality and accessibility over time (e.g., the addition of new sections or new access points to the UI). Over time, the user interface becomes too large and too complex to be useful to most customers.

The most obvious solution to reducing the complexity is to splinter the large UI into several smaller UIs, each with a dedicated focus. However, this often does not reduce the complexity from a user's perspective because the net result is more choices and uncertainty as to which UI is the right choice for accessing the data they need.

This invention proposes extended usability of the user interface through more intelligent customization. This customization is driven not only by context (e.g., where the user is within the application and the type of data they are looking at), but also by availability of the data, obscuring parts of the UI where data is either unavailable or does not make sense to present in the current perspective. The result is a single UI (e.g., a report) that dynamically adjusts itself based upon inputs provided by the user and the system to an artificial intelligence engine.

Most solutions today are focused on modifying the user interface based upon user preferences or more explicit controls. For example, if the user is viewing a report for their infrastructure devices, the UI should only present data for the devices they have configured to see or have permission to see.

This invention, instead of being focused on a user's contextual clues, is focused on using system and user workflow clues to streamline the set of information provided to the user of the application. The information is streamlined within the UI by collecting and analyzing contextual clues implicitly provided by the user (e.g., "I am on this page within the application…"). This is done either through an artificial intelligence engine (e.g., "While viewing data about network traffic with suspicious hosts, I only want to see firewall data for specific IP address pairs, and not all IP addresses.") or by the system (e.g., no vulnerability data is available for this host, so this element of the UI is hidden). The invention also takes into the account the complexity of the data by further restricting the user interface to hide elements when the data would be too noisy or would fail to reveal any meaningful patterns (e.g., using an IP address as a pivot point would reveal thousands of potential matches which are far too many for a human to understand and take action upon). The key advantag...