information-package-diagram . Information Package Diagram. Information Packages – novel idea for determining and recording information requirements for a data warehouse. Package diagrams are structural diagrams used to show the organization and arrangement of various model elements in the form of packages. A package is a grouping of related UML elements, such as diagrams, documents, classes, or even other packages.The aim of IPD is to define (or to redefine) the organizational processes which will supply the DW with data. The added-value of this approach will be the integration of the previous methods (demand-driven and data-driven) with organizational processes that will treat these sets of informations to be used by the DW.What is a package application? Application package software, or simply an application package, is a collection of software programs that have been developed for the purpose of being licensed to third-party organizations Word processors, spreadsheets, databases, graphics and presentation software are all examples of application packages. This type of software is sometimes called generic software. At the beginning of the project, you only have a limited number of diagrams and everything is simple and beautiful. However, when time flies, more and more diagrams have been created and they start to become unmanageable. As a result, your project becomes hard to navigate and diagrams become difficult to locate when you want to review or make changes. How can we fix it up? We can make use of the Package Diagram to organize your diagrams into different packages. This helps you in categorizing your diagrams according to their natures, making them easier to be navigated and located. The Package Diagram also serves as a catalog for you to jump to the diagram that you want to look at. In this tutorial, we will show you how this can be done. Create Packages for your diagrams First, we need to have our packages ready.

1. G.Anuradha
Information Package Diagram

2.  Information Packages – novel idea for
determining and recording information
requirements for a data warehouse.
 Determining requirements for a data warehouse
is based on business dimensions
 The relevant dimension and measurements in
that dimension are captured and kept in a data
warehouse
 This creates an information package for a specific
subject

3. An information Package

4. Business dimensions
 In requirements collection phase, the end users
can provide the measurements which are
important to that department.
 They can also give insights of combining the
various pieces of information for strategic
decision making.
 Managers think of business in terms of business
dimensions
 The managers try to evaluate business in
different dimensions.

6. Case
studies

7. Examples of business
dimensions

8. IPD enables you to….
 Define the common subject areas
 Design key business metrics
 Decide how data must be presented
 Determine how users will aggregate or roll up
 Decide the data quantity for user analysis or
query
 Decide how data will be accessed
 Establish data granularity
 Estimate data warehouse size
 Determine the frequency for data refreshing
 Ascertain how information must be packaged

9. Business dimensions for
automobile manufacturer

10. Hierarchies/Categories
 Hierarchies are paths for drilling down or rolling
up in our analysis
 Non hierarchical data which are very important in
analyzing are called categories
 Holiday flag is a category which helps in evaluating
the sales on a holiday