User Participation

User Participation

In a typical OLTP application, the users interact with the system through GUI screens. They use the screens for data input and for retrieving information. 

The users receive any additional information through reports produced by the system at periodic intervals. If the users need special reports, they have to get IT involved to write an hoc programs that are not part or the regular application.

In striking contrast, user interaction with it data warehouse is direct and intimate. Usually, there are no just a few set reports or queries. When the implementation is complete, your users will begin to use the data warehouse directly with no mediation from IT. There is no predictability. In the types of queries they will be running the types of reports they will be requesting, or the types of analysis they will  performing. If there is one major difference between OUT systems and data warehousing systems, it is in the usage of the system by the users.

What is the implication of this major difference in project team composition and data warehouse development? The implication is extremely consequential. What does this mean? This means that lithe users will be using the data warehouse directly in unforeseen ways they must have a strong voice in its development. They must be part of the project team all the way. More than an OLTP system project a data warehouse project calls for serious joint application development (JAD) techniques.

Your data warehouse project will succeed only if appropriate members of the user community are accepted as the team members with specific roles. Make use of their experience and knowledge of the business. Tap into their experience in making business decision. Actively involve them in the selection of information delivery tools. Seek their help in testing the system before implementation. 

Figure 4-9 illustrates how and where in the development process 'Users must he made to participate. Review each development phase and clearly decide how and where your users nerd to participate. This figure relates user participation to stages in the development process.

Like is a list of a few team roles that users can assume to participate in the development:

• Project Sponsor—executive responsible for supporting the project effort all the way
• User Department Liaison Representatives-7 help IT to coordinate meetings and review sessions; ensure active participation by the user departments
• Subject Area Experts—provide guidance in the requirements of the users in specific subject areas; clarify semantic meanings of business terms used in the enterprise
• Data Review Specialists—review the data models prepared by IT; confirm the data elements and data relationships
• In limitation Delivery Consultants --examine and test information delivery tools; assist in the tool selection
• User Support Technicians--act as the first-level, front-line support for the ti in their respective departments