首页 考试吧论坛 Exam8视线 考试商城 网络课程 模拟考试 考友录 实用文档 求职招聘 论文下载 | ||
2011中考 | 2011高考 | 2012考研 | 考研培训 | 在职研 | 自学考试 | 成人高考 | 法律硕士 | MBA考试 MPA考试 | 中科院 |
||
四六级 | 职称英语 | 商务英语 | 公共英语 | 托福 | 雅思 | 专四专八 | 口译笔译 | 博思 | GRE GMAT 新概念英语 | 成人英语三级 | 申硕英语 | 攻硕英语 | 职称日语 | 日语学习 | 法语 | 德语 | 韩语 |
||
计算机等级考试 | 软件水平考试 | 职称计算机 | 微软认证 | 思科认证 | Oracle认证 | Linux认证 华为认证 | Java认证 |
||
公务员 | 报关员 | 银行从业资格 | 证券从业资格 | 期货从业资格 | 司法考试 | 法律顾问 | 导游资格 报检员 | 教师资格 | 社会工作者 | 外销员 | 国际商务师 | 跟单员 | 单证员 | 物流师 | 价格鉴证师 人力资源 | 管理咨询师考试 | 秘书资格 | 心理咨询师考试 | 出版专业资格 | 广告师职业水平 驾驶员 | 网络编辑 |
||
卫生资格 | 执业医师 | 执业药师 | 执业护士 | ||
会计从业资格考试(会计证) | 经济师 | 会计职称 | 注册会计师 | 审计师 | 注册税务师 注册资产评估师 | 高级会计师 | ACCA | 统计师 | 精算师 | 理财规划师 | 国际内审师 |
||
一级建造师 | 二级建造师 | 造价工程师 | 造价员 | 咨询工程师 | 监理工程师 | 安全工程师 质量工程师 | 物业管理师 | 招标师 | 结构工程师 | 建筑师 | 房地产估价师 | 土地估价师 | 岩土师 设备监理师 | 房地产经纪人 | 投资项目管理师 | 土地登记代理人 | 环境影响评价师 | 环保工程师 城市规划师 | 公路监理师 | 公路造价师 | 安全评价师 | 电气工程师 | 注册测绘师 | 注册计量师 |
||
缤纷校园 | 实用文档 | 英语学习 | 作文大全 | 求职招聘 | 论文下载 | 访谈 | 游戏 |
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.
北京 | 天津 | 上海 | 江苏 | 山东 |
安徽 | 浙江 | 江西 | 福建 | 深圳 |
广东 | 河北 | 湖南 | 广西 | 河南 |
海南 | 湖北 | 四川 | 重庆 | 云南 |
贵州 | 西藏 | 新疆 | 陕西 | 山西 |
宁夏 | 甘肃 | 青海 | 辽宁 | 吉林 |
黑龙江 | 内蒙古 |