Step 3: Using Patterns

Home

Design Patterns and Guidelines

Oracle Business Intelligence Enterprise Edition

Design Process

Design Patterns

Design Guidelines

Design Patterns and Guidelines for Oracle Applications


	Receive occasional updates on Applications User Experience such as new articles, new tools, meeting our staff, and opportunities to get involved in our Customer Programs.

Process for Using BI Patterns and Guidelines
Step 3: Using Patterns

You should understand the pattern structure and guidelines and know how to use them. This section provides an overview of a typical design pattern and helps you understand the various parts of a pattern.

Before using the patterns to create new designs, you should understand the structure of a typical design pattern. All patterns on this Web site follow a similar structure.

When Should You Use Patterns?

Product Managers

Product Development

Customers and Consultants

When determining requirements for a new product
During the conceptual phase
When redesigning an existing application
Before the functional design and technical design phase of application development

When determining requirements for a new product
During the conceptual phase

Note: This step is not required if product managers are involved in identifying design patterns.

When redesigning an existing application

Pattern structure

Each pattern consists of the following sections:

Figure 1. Pattern structure

Description Section

This section provides a high-level description of the pattern, its purpose, and its applicability.
This section also identifies the target users who could benefit from the pattern.

Figure 2. Example of a Pattern Title and Description

Selection Criteria

This section provides a list of user roles and descriptions. The pattern is designed for the users listed here.

Figure 3. Example of Pattern Selection Criteria

Required Screen Elements

This section provides a list of various elements from OBIEE that are required to create the recommended layouts.
This section helps developers identify the correct screen elements to apply while using the pattern.

Figure 4. Example of a List of Required Screen Elements

Example Layout

This section contains example layouts to illustrate the pattern definition and various ways to apply the pattern.

Example Layout of Summary Page:

The layout below provides a typical arrangement of page regions to accommodate one or more metrics for KPIs and reports for key tasks related to data correlation and comparison. The example below is a two-column arrangement of page regions. This arrangement is good for representing metrics with bigger timelines and complex data on the horizontal axis. The top four metrics or reports could be placed in the visible region of the page and the rest could be stacked below these page regions. A user could access these additional metrics by scrolling the page vertically. However, if there are more than seven or eight metrics, it's better to create more logical groupings and assign a new tab for them.

Figure 5. Example Layout


	Sample from OBIEE This section contains examples generated from OBIEE tools. These examples help to illustrate the featured pattern. Figure 6. An example from OBIEE to explain the outcome of a Pattern