首頁 考試吧論壇 Exam8視線 考試商城 網(wǎng)絡(luò)課程 模擬考試 考友錄 實(shí)用文檔 求職招聘 論文下載
2011中考 | 2011高考 | 2012考研 | 考研培訓(xùn) | 在職研 | 自學(xué)考試 | 成人高考 | 法律碩士 | MBA考試
MPA考試 | 中科院
四六級 | 職稱英語 | 商務(wù)英語 | 公共英語 | 托福 | 雅思 | 專四專八 | 口譯筆譯 | 博思 | GRE GMAT
新概念英語 | 成人英語三級 | 申碩英語 | 攻碩英語 | 職稱日語 | 日語學(xué)習(xí) | 法語 | 德語 | 韓語
計(jì)算機(jī)等級考試 | 軟件水平考試 | 職稱計(jì)算機(jī) | 微軟認(rèn)證 | 思科認(rèn)證 | Oracle認(rèn)證 | Linux認(rèn)證
華為認(rèn)證 | Java認(rèn)證
公務(wù)員 | 報(bào)關(guān)員 | 銀行從業(yè)資格 | 證券從業(yè)資格 | 期貨從業(yè)資格 | 司法考試 | 法律顧問 | 導(dǎo)游資格
報(bào)檢員 | 教師資格 | 社會(huì)工作者 | 外銷員 | 國際商務(wù)師 | 跟單員 | 單證員 | 物流師 | 價(jià)格鑒證師
人力資源 | 管理咨詢師考試 | 秘書資格 | 心理咨詢師考試 | 出版專業(yè)資格 | 廣告師職業(yè)水平
駕駛員 | 網(wǎng)絡(luò)編輯
衛(wèi)生資格 | 執(zhí)業(yè)醫(yī)師 | 執(zhí)業(yè)藥師 | 執(zhí)業(yè)護(hù)士
會(huì)計(jì)從業(yè)資格考試會(huì)計(jì)證) | 經(jīng)濟(jì)師 | 會(huì)計(jì)職稱 | 注冊會(huì)計(jì)師 | 審計(jì)師 | 注冊稅務(wù)師
注冊資產(chǎn)評估師 | 高級會(huì)計(jì)師 | ACCA | 統(tǒng)計(jì)師 | 精算師 | 理財(cái)規(guī)劃師 | 國際內(nèi)審師
一級建造師 | 二級建造師 | 造價(jià)工程師 | 造價(jià)員 | 咨詢工程師 | 監(jiān)理工程師 | 安全工程師
質(zhì)量工程師 | 物業(yè)管理師 | 招標(biāo)師 | 結(jié)構(gòu)工程師 | 建筑師 | 房地產(chǎn)估價(jià)師 | 土地估價(jià)師 | 巖土師
設(shè)備監(jiān)理師 | 房地產(chǎn)經(jīng)紀(jì)人 | 投資項(xiàng)目管理師 | 土地登記代理人 | 環(huán)境影響評價(jià)師 | 環(huán)保工程師
城市規(guī)劃師 | 公路監(jiān)理師 | 公路造價(jià)師 | 安全評價(jià)師 | 電氣工程師 | 注冊測繪師 | 注冊計(jì)量師
繽紛校園 | 實(shí)用文檔 | 英語學(xué)習(xí) | 作文大全 | 求職招聘 | 論文下載 | 訪談 | 游戲
您現(xiàn)在的位置: 考試吧(Exam8.com) > 軟件水平考試 > 計(jì)算機(jī)專業(yè)英語 > 正文

How To Do a Data Warehouse Assessment (And Why)

  Performing the Assessment

  Data warehouse assessment is most effectively performed using a systematic and proven process. Figure 2 illustrates this process and the value derived from it. The following steps provide an overview of the process by which a proto-typical data warehouse assessment is executed using the multiple-perspectives method. The usual team size is three-to-four senior data warehousing analysts who collectively have expertise in all of the identified areas of assessment.

Figure 2: The Data Warehouse Assessment Process

  Initial Parallel Investigation

  Identify and prioritize executive and management reporting and analysis needs, priorities, constraints and expectations. As discussed, these are typically not well documented, if known at all. At minimum, known and documented business requirements will need to be validated. A series of structured interviews with primary stakeholders works well, followed by a group session to validate, synthesize and prioritize findings.

  In parallel with the review of management needs to support the business assessment, an initial review of documents and identification of potential issues can be performed for each of the remaining perspectives. While findings are ultimately interdependent, and particularly dependent on business needs, this initial investigation is an essential data gathering step, and early comparison against benchmarks and best practices is informative. A discussion of the benchmarks is beyond the scope of this article. (Best practices and benchmarks could easily demand an entirely separate series of articles.) Good references for best practices are available in TDWI publications and other literature. Suffice it to state that you should investigate, identify, and have at hand a set of benchmarks against which your own projects and practices will be assessed.

  Initial Outputs:

  List of prioritized business information needs

  Understanding of the information, technology, organization, methodology and project management context.

  Initial identification of key problems in each area.

  List of what data is available is available in the current DW and any limitations on its completeness, accessibility, data quality.

  Gap Analysis

  Map the prioritized business information needs against the current warehouse in terms of data availability. This establishes a view of key gaps from the perspective of business need.

  Map prioritized business information needs against identified architectural (and possibly organizational) problems. This is a mapping of information needs to architectural issues that inhibit meeting the business needs, and whose resolution would significantly improve delivery of required business information and analysis capabilities. This mapping provides a sense of which architectural issues have the greatest adverse impact on the business and are most urgent to address.

  Methodology and project management gaps, and some of the organizational considerations, may not readily map to specific business priorities. These are more global in nature, and issues in this area are likely to have broad impact across all business needs and priorities. Issues from these perspectives are better suited to qualitative, rather than quantitative, analysis of impact.

  Identify Solution Sets

  Identify an initial list of potential solutions to addressing warehousing problems and correspondingly impacted business needs. This activity involves a subjective analysis of problem affinity analysis based on the earlier mapping. Evaluation of affinity leads to parsing of logically distinct solutions.

  Refine and consolidate the set of logical, prioritized solutions based on

  Contributions to addressing prioritized business needs.

  Contributions to addressing highest impact architectural problems.

  Logical groupings of functionality based on architectural feasibility and technical cohesion.

  Organizational capability to implement.

  High level estimates of time and cost.

  Package and Present Recommendations

  This involves:

  Compilation and final documentation of analysis.

  Presentation of findings.

  Validation of recommendations with management.

  Decisions on which solution set(s) to pursue.

上一頁  1 2 3 4 5 6 7 8 9 下一頁
文章責(zé)編:ak47  
看了本文的網(wǎng)友還看了
文章搜索
軟件水平考試欄目導(dǎo)航
版權(quán)聲明:如果軟件水平考試網(wǎng)所轉(zhuǎn)載內(nèi)容不慎侵犯了您的權(quán)益,請與我們聯(lián)系800@exam8.com,我們將會(huì)及時(shí)處理。如轉(zhuǎn)載本軟件水平考試網(wǎng)內(nèi)容,請注明出處。