CHAPTER SUMMARY and Reviews

CHAPTER SUMMARY

  • Unlike the requirements for an operational system, the requirements for a warehouse are quite nebulous.
  • Business data is dimensional in nature and the users of the data warehouse dr terms of business dimensions.
  • A requirements definition for the data warehouse can, therefore, be based on business dimensions such as product, geography, lime, and promotion.
  • Information packages—a new concept–are the backbone of the requirements definition. An information package records the critical measurements or facts and business dimensions along which the lack are normally analyzed.
  • Interviews and group sessions arc standard methods for collecting requirements.
  • Key to be interviewed or to be included in group sessions arc senior executives including the sponsors, departmental managers, business analysts, and operational systems.
  • Review all existing documentation of related operational systems.
  • Scope and content of the requirements definition document include data sources, data transformation, data storage, information delivery, and information package diagrams.

REVIEW QUESTIONS

1. What arc the essential differences between defining requirements for operational systems and for data warehouses’?
2. Explain business dimensions. Why and how can business dimensions be useful for defining requirements for the data warehouse?
3. What data does an information package contain?
4. What are dimension hierarchies? Give three examples.
5. Explain business metrics or facts with live examples.
6. List the types of users who must be interviewed for collecting requirements. What information can you expect to get from them?
7 In which situations can JAD methodology be successful for collecting requirements?
8. Why arc reviews of existing documents important’? What can you expect to get out of such reviews’?
9. Val ions data sources feed the data warehouse. What are the pieces of information you need to get about data sources’?
10. Name any five major Components of the formal requirements definition document. Describe what goes into each of these components.

Requirements Definition Document Outline

Requirements Definition Document Outline

1. Introduction. State the purpose and scope of the project. Include broad project justification. Provide an executive summary of each subsequent section.
2. General requirements descriptions. Describe the source systems reviewed. Include interview summaries. Broadly state what types of information requirements needed in the data warehouse.
3. Specific requirements. Include details of source data needed. List the data tr; formation and storage requirements. Describe the types of information delivery meth needed by the users.
4. Information packages. Provide as much detail as possible for each inform package. Include in the form of package diagrams.
5. Other requirements. Cover miscellaneous requirements such as data extract sequences, data loading methods, and locations to which information must be delivered.
6. User expectations. State the expectations in terms of problems and opportune Indicate how the users expect to use the data warehouse.
7. User participation and sign-off. List the tasks and activities in which the user expected to participate throughout the development life cycle;
8. General implementation plan. Al this stage gives a high-level plan for implementation.

Information Package Diagrams

Information Package Diagrams
The presence of information package diagrams in the requirements definition document is the major and significant difference between operational systems and data warehouse systems. Remember that information package diagrams are the best approach for determining requirements for a data warehouse.

The information package diagrams crystallize the information requirements for data warehouse. They contain the critical metrics measuring the performance of the business units, the business dimensions along which the metrics arc analyzed, and the information how drill-down and roll-up analyses are done.

Spend as much time as needed to make sure that the information package diagrams complete and peculate. Your data design for the data warehouse will be totally depend on the accuracy and adequacy of the information package diagrams.

70-331 Question 5

70-331 Question 5
DRAG DROP
You need to install the appropriate versions of Windows Server, Microsoft SQL Server, and Microsoft .NET Framework in the server environment. Which operating system and applications should you install? (To answer, drag the appropriate operating systems and applications to the correct server layers in the answer area. Each operating system or application may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.)

70-331

Answer:

Explanation:
Server Layer, Web
Operation System: Windows Server 2008 R2 SP1
Application: .NET Framework 4.5
Server Layer, Application
Operation System: Windows Server 2008 R2 SP1
Application: .NET Framework 4.5
Server Layer, Database
Operation System: Windows Server 2008 R2 SP1
Application: SQL Server 2008 R2 SP1

Note:
* From scenario: Install the minimum supported versions of all software on the servers.
* Minimum requirements for a single server with built-in database: include:
The 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Standard or Datacenter
Microsoft .NET Framework version 4.5 Microsoft SQL Server 2008 R2 SP1 -

70-331 Question 1

70-331 Question 1
You create a User Profile Synchronization connection. You need to grant the necessary permissions to the synchronization account. What should you do?

A. Grant the account Full Control on the ActiveUsers OU.
B. Grant the account Full Control on the AuthenticatedUsers AD security group.
C. Grant the account Read permission on the domain.
D. Grant the account the Replicate Directory Changes permission on the domain.

Answer: D