Skip to main content

Information Aggregation general guidelines

Overview

To help you determine if the Information Aggregation business pattern is appropriate for the design of your Web-based application, the following information details the business and IT scenario into which an Information Aggregation solution fits.

Business and IT Drivers

Businesses developing a solution needing the following characteristics should consider using the Information Aggregation business pattern:

Context

Users of applications, built according to the Information Aggregation business pattern might be internal or external to an organization. In both cases, the objective is to transform raw data into useful information. For example:

Initially, one may find architectural similarities between applications that implement the Information Aggregation and Self-Service business patterns. However, what distinguishes these two is the user’s interaction with data versus a business transaction. Applications that implement the Information Aggregation business pattern facilitate direct interaction between users and data. These applications provide significant freedom and flexibility in accessing and manipulating data. This is one of the primary characteristics that differentiate this pattern from the Self-Service business pattern, which facilitates direct interaction between users and business transactions and processes. Typically, applications that implement the Information Aggregation business pattern depend on applications that implement the Self-Service business pattern as the original source of much of the data. This is especially true because business activities are recorded on a minute-to-minute basis by applications that implement the Self-Service business pattern.

Designing applications that implement the Information Aggregation business pattern can be challenging for many reasons. User requirements tend to be vague and constantly changing. Several applications can be built simultaneously, some of which have common data needs while others may have conflicting needs. To overcome these challenges, best practice suggests that population and information access functionality be separated in the design. This separation allows for greater flexibility in changing either the population function or the information access function without impacting the other.

This Business pattern can be realized using several Application patterns based on the needs of the application.

Solution

This pattern typically consists of:

Putting the Information Aggregation business pattern to use

This pattern can be observed in solutions such as:

What's Next

If you have determined that the Information Aggregation business pattern can provide an appropriate solution design for the application you are developing, next familiarize yourself with a few important Information Aggregation concepts.

If the Information Aggregation business pattern is not appropriate for your development efforts, review the Business patterns to determine which pattern best addresses your e-business needs.

Content navigation