Chapter Twelve. Step 12: Application Development


graphics/ch12.gif

Chapter Overview

This chapter covers the following topics:

  • Things to consider about access and analysis tools

  • The advantages of using online analytical processing (OLAP) tools and some of their popular features

  • Multidimensional analysis factors, with emphasis on multivariate analysis using both object dimensions and variable dimensions

  • Three OLAP architectural layers : presentation services, OLAP services, and database services

  • Four common application development environments: prototyping, development, quality assurance (QA), and production

  • A short discussion of the Web environment

  • Brief descriptions of the activities involved in application development, the deliverables resulting from those activities, and the roles involved

  • The risks of not performing Step 12

Things to Consider

Prototyping Results

Did we prototype the access and analysis components of the BI application? If so, what did we learn from the prototype?

What portions of the application prototype can we save? What portions have to be redesigned?

Did we decide to develop the access and analysis components using the operational prototype as a rapid and iterative development method? Will this be the final iteration?

Access and Analysis Tools

What access and analysis tools do we already have in place? Are we happy with them?

Will the business people use an OLAP tool for multidimensional analysis?

In what other ways will they analyze the data? Do we need to acquire another query or reporting tool?

Skills and Training

What skill sets (beginning, advanced, expert) do the business people have? What type of additional training do they need?

How many business people have already been trained on the access and analysis tools? How many more need training?

Are they familiar with OLAP and multidimensional reporting concepts?

Do we need to implement a context-sensitive online help function for the access and analysis components of the BI application?

Scope and Project Requirements

Are our project requirements still the same? Or has the scope changed?

How many reports and canned queries do we need to develop? Which ones?

Have we validated the necessary number of dimensions needed for those reports and queries?

Do we know how the knowledge workers, business analysts, and business managers want to drill down and roll up when working with the data? Are their requirements similar or different?

Web Considerations

Do we have to include a Web portal with this BI application?

Have we developed Web portals before? Have we prototyped one?

What are the additional security requirements for the Web? Do we have the necessary firewalls and security packages installed?

Technical Considerations

Are the development and production environments configured the same or are they different?

What are the differences? A different database management system (DBMS)? A different operating system? Different hardware?

The main reason for a BI decision-support initiative is to provide fast and easy access to data for business analysis. A high percentage of that access will be by predefined patterns. A predefined pattern means that data has been precalculated (derived, aggregated, summarized) and stored in that fashion for faster access. This is the reason for the high popularity of multidimensional OLAP tools, and it is the hallmark of BI decision-support applications.



Business Intelligence Roadmap
Business Intelligence Roadmap: The Complete Project Lifecycle for Decision-Support Applications
ISBN: 0201784203
EAN: 2147483647
Year: 2003
Pages: 202

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net