|
|
| |
| Design Patterns and Guidelines for Oracle Applications |
|
|
|
|
|
|
|
|
| Information Display |
| The Information Display pattern group helps project managers, developers, and designers select visualization techniques such as tables and graphs, which enable users to understand the meaning and significance of the numbers. Numbers are central to a user's understanding of business, and they help users make informed decisions. |
|
|
| |
|
|
|
|
|
|
|
| |
|
|
| |
|
|
|
|
This Analytic Grid pattern set helps product managers, developers, and designers understand the advantages and disadvantages associated with displaying data using different types of OBIEE grid components. Data is organized in columns and rows, displaying relationships between quantitative values and the categorical subdivisions to which these values are related. |
|
|
|
|
|
Use the following decision table to determine what pattern is appropriate based on user needs:
| |
|
|
|
| Does the end user need to examine values to discern patterns or trends? |
Yes |
No |
No |
| Does the end user need an easy way to look up a particular value? |
No |
Yes |
No |
| Does the end user need only a single data point summary (for example, Up/Down)? |
No |
No |
Yes |
| |
|
|
| User Type |
Casual |
Casual |
| Do the quantities need to be grouped in hierarchies? |
No |
No |
| Do the quantities of two different dimensions need to be grouped in hierarchies? |
No |
No |
| Are objects sortable within a group? |
Yes
|
Yes
|
|
|
|
|
|
|
|
|
|
|
|
