Download70341's Blog

Blog For Free!

2013 August
2013 June

My Profile
Send tMail
My tFriends
My Images

Create a Blog!

The Development Phases
08.19.13 (3:12 am)   [edit]

The Development Phases
In the previous section, we again referred to the overall functional components of a data warehouse as data acquisition, data storage, and information delivery. These three functional components from the general architecture of the data warehouse. There must be the proper technical infrastructure to support these three functional components. Therefore, when we formulate the development phases in die life cycle, we have to ensure that the phases include tasks relating to the three components. The phases must also include tasks to define the architecture as composed of the three components and to establish the under-lying infrastructure to support the architecture. The design and construction phase for these three components may run somewhat in parallel.

Refer to Figure 4-5 and notice the three tracks of the development phases. In the development of every data warehouse, these tracks are present with varying sets of tasks. You may change and adapt the tasks to suit your specific requirements. You may want to emphasize one track more than the others. If data quality is a problem in your company, you need to pay special attention to the related phase. The figure shows the broad division of the project life cycle into the traditional phases:

DEPLOYMENT DETAILS Figure 4-4 Data warehouse project plan: sample outline.
  • Project plan
  • Requirements definition
  • De.--i!in 6 Construction
  • Deployment
  • Growth and maintenance

Figure 4-5 Data warehouse development phases.

Interleaved within the design and construction phases are the three tracks along with the definition of the architecture and the establishment of the infrastructure. Each of the boxes shown in the diagram represents a major activity to be broken down further into individual tasks and assigned to the appropriate team members. Use the diagram as a guide for listing the activities and tasks for your data warehouse project. 

The Life-Cycle Approach
08.19.13 (3:00 am)   [edit]

The Life-Cycle Approach Astir
As IT professional you are all too familiar with the traditional system development life cycle (SDIC) know how to begin with a project plan, move into the requirements analysis phase, then into the design, construction, and testing phases, and finally into the implementation phase.

The life cycle approach accomplishes all the major objectives in the system development process. it enforces orderliness -and enables a systematic approach to building computer systems. The life cycle methodology breaks down the project complexity and removes any ambiguity with regard to the responsibilities of project team members. It implies a predictable set of tasks and deliverables. That the life cycle approach breaks down the project complexity is alone reason enough for this approach to be applied to a data warehouse project. A data warehouse project is complex in terms of tasks, technologies, and team member roles. But a one-size-fits-all life cycle approach will not work for a data warehouse project. Adapt the life cycle approach to the special needs of your data warehouse project. Note that a life cycle for data warehouse development is not a waterfall method in which one phase ends and cascades into the next one.

The approach for a data warehouse project has to include iterative tasks going through cycles of refinement. For example, if one of your tasks in the project is identification of data sources, you might begin by reviewing all the source systems and listing all the source data structures. The next iteration of the task is meant to review, the data elements with the users. You move on to the next iteration of reviewing the data elements with the database administrator and some other IT start. The next iteration of walking through the data elements one more time completes the refinements and the task. This type of iterative process is required for each task because of the complexity and broad scope of the project. Remember that the broad functional components of a data warehouse are data acquisition, data storage, and information delivery. Make sure the phases of your development, life cycle wrap around these functional components. Figure 4-3 shows how to relate the functional components to SDLC.

Figure 4-3 DW functional components and SDLC

As in any system development life cycle, the data warehouse project begins with the preparation of a project plan. The project plan describes the project, identifies the specific objectives, mentions the crucial success factors, lists the assumptions, and highlights the critical issues. The plan includes the project schedule, lists the tasks and assignments, and provides for monitoring progress. Figure 4-4 provides a sample outline of a data ware-house project plan.

Assessment of Readiness
08.19.13 (2:14 am)   [edit]
Assessment of Readiness
Let us say you have justified the data warehouse project and received the approval and blessing of the top management. You have an overall plan for the data warehousing initiative. You have grasped the key issues and understood how a data warehouse project is different and what you have to do to handle the differences. Are you then ready to jump into the preparation of a project plan and gel moving swiftly?

Not yet. You need to do a. formal readiness assessment. Normally, to many or the project team members and to almost all of the users, data warehousing would be a brand new concept. A readiness assessment and orientation is important. Which person does the readiness assessment? The project manager usually does it with the assistance of an out-side expert. By this time, the project manager would already be trained in data warehousing or he or she may have prior experience. Engage in discussions with the executive users, and potential team members. The objective is to assess their familiarity with data warehousing in general, assess their readiness, and uncover gaps in their knowledge: Prepare a formal readiness assessment report before the project plan is firmed up the readiness assessment report is expected to serve the following purposes:
  • Lower the risks of big surprises occurring implementation
  • Provide a proactive approach to problem resolution
  • Reassess corporate commitment
  • Review and identify project scope and size
  • Identify critical success factors
  • Restate user expectations
  • Ascertain training needs

70-341 Question 7
06.17.13 (10:30 pm)   [edit]
70-341 Question 7
You need to recommend which tasks must be performed to meet the technical requirements of the research and development (R&D) department. Which two tasks should you recommend? (Each correct answer presents part of the solution. Choose two.)

A. Create a new global address list (GAL) and a new address book policy.
B. Modify the permissions of the default global address list (GAL), and then create a new GAL.
C. Run the Update AddressList cmdlet.
D. Run the Set-Mailbox cmdlet.
E. Create an OAB virtual directory.

Answer: A, D

70-341 Question 6
06.17.13 (10:29 pm)   [edit]
70-341 Question 6
You need to recommend which type of group must be used to create the planned department lists. Which type of group should you recommend?

A. Universal Distribution
B. Dynamic Distribution
C. Global Security
D. Universal Security

Answer: A