设计数据仓库的注意事项(Part I)

设计|数据

Introduction
Identifying and understanding the business and operational requirements that drive any data warehousing project are essential to the project抯 successful completion. You cannot meet your clients?needs if you have not assessed and analyzed what those needs are and how you can address them.

Who Knows?

The most important part of the business requirements process is finding out who knows what the requirements should be. In most cases, the answer to "Who knows what we need to know?" is that nobody knows it all, but everyone knows a part.

And What Do They Know?

The answer to this question is they know far more than they imagine. In most cases your sources do not know they have valuable information and to what extent they are the only possible source for vital information that will help insure the project抯 success.

The Biological Knowledge Base

Systems are designed, created, maintained and operated by people who have first hand system information. This group of experts is collectively identified as the biological knowledge base that you must tap effectively in order to extract the information you require.

Play by the Rules

Your organization抯 business rules (functional requirements) and operational characteristics (non-functional requirements) are the essence of the design requirements for your project. They must be carefully cataloged and analyzed to insure internal consistency. When inconsistencies are found, you need to identify the cause of the inconsistencies (you will find that in some cases the inconsistencies are perfectly valid and reasonable) and determine the proper method(s) for adjusting the project.

How It Has to Work and Why

For each component of your project, you will need to identify the operational and business requirements. For example, there will be times when the need for 24X7 availability will supercede the need for total accuracy. Situations such as this must be taken into consideration and included in your development plan.

Cultural/Political Constraints

Cultural and political constraints will have a serious impact on your success, so they must be addressed while collecting the business requirements that define the project. Even in those cases where the political environment is opposed to the needs of the project team, you can use political relationships to increase the visibility and acceptance of your project, but only if you have a clear understanding of the dynamics involved.

Assessing/Addressing Risks

Every project faces risks, some are minor, some severe. The successful project is based on identifying what those risks are, how likely they are to occur, how serious they are and what actions are best to prevent the issues from arising. Identify the tactics to be used in dealing with the issues when they do arise, because, despite your best efforts, some will still occur.
Mine the Biological Knowledge Base
The biological knowledge base is the complete body of human knowledge and intelligence available. The readily accessible biological knowledge base primarily consists of: designers and developers, knowledge workers, end users, management, system staff, security staff and physical maintenance staff.

Everything you learn from the biological knowledge base should become a part of the business requirements for your project and be fully documented to serve as valuable material for subsequent projects.

Designers/Developers

Design and development staff members are those who are or have been responsible for creating and maintaining existing systems and are tasked with integrating future systems. You will need to gather business requirements and functional constraint information from architects (business, data and system), database administrators, database analysts and programmer analysts. Each will have their own perspective on your project and on the information needed in order to make it successful.

Effectively interviewing the designers and developers will provide you with background information that will give your project a head start toward a successful completion. Their knowledge will provide a foundation upon which to build the final business requirements that your business partners identify.

Architects

Architects create the designs for the environments in which applications and systems function. They are seldom directly involved in building the applications, systems or databases, but provide the blueprints from which such structures are created.

Architects can detail information contained in the design documentation as well as the enterprise standards, logical limitations and business functionality. Architects also begin gathering the data requirements for the project.

DBAs

Database administrators and analysts are experts when it comes to creating, maintaining and optimizing the data structure behind information management applications. These DBAs are an invaluable resource.

DBAs can provide your team with nearly everything it needs to know about database management systems, structure, security, resource requirements (hardware, software and personnel), enterprise standards, physical limitations and how others have integrated business rules into their database implementations.

Programmer Analysts

Programmer analysts are the ones who create the code that makes applications work. Their job is to take a concept and turn it into a functioning system that provides the desired capabilities.

These specialists should be interviewed with the intention of deriving information on operation limitations in their applications, structural standards that constrained the design and development of the applications, how they enforce the business rules that defined their projects and a listing of the design requirements from which they worked.
Knowledge Workers (Subject Matter Experts)
Knowledge workers are those who work with the base information for your project. They consist of business analysts, actuaries, accountants and business consultants, as well as marketing, sales, clerical and production.

Business Analysts

Business analysts are your best resource for understanding the true business meaning for a particular data element or set and for identifying the logic on which the application is based.

They will provide you with information on which business questions need to be answered and where to find the data that will help to answer them. They will also provide you with the specifications on functional reporting requirements ?the information they need to have in order to develop the reports upon which decisions are based.

Actuaries

Actuaries are statistical analysis specialists who determine the likelihood that something will happen a specific number of times within an identified group during a given time period. They can also be called risk analysts because they job identify risks the business faces.

They provide your team with information on the data elements they require in order to perform the statistical analysis upon which their predictions are dependent. They can also identify many of the derived and dependent measures that will assist them in preparing analyses as needs and demographics change.

Accountants

Accountants are the true numbers crunchers of the organization. They are the ones who determine to what extent the organization is profitable. They make sure the books balance. They tend to be detail oriented to the exclusion of nearly every other consideration.

You will get specific information regarding the data that feeds the profit/loss analyses they use in building financial reports and budget management reports. They will also provide detail on the derived and calculated measures from which they build these reports.

Business Consultants

Business consultants, whether internal or external, specialize in identifying ways to improve business functionality and preparing plans for implementing the new processes. In order to accomplish their tasks, they must receive clear and reliable information regarding the current and historical views of the business as well as developing trends.

The consultants will identify the business questions they need answers to in order to identify the current state, which they base their trend analyses on. In many cases, the most important pieces of information are derived from profit/loss reports.

Marketing Staff

The marketing team is primarily interested in identifying potential customers, learning what products or services they want and determining how your organization can fill all or part of that need. In order to perform their tasks most effectively, they need to have sales, production and customer support data.

The marketing team will be able to provide you with information on the following topics: client segmentation, test marketing requirements, marketing program effectiveness, customer relationship management and value chain management.

Sales Staff

The sales staff is responsible for actually turning a marketing plan into financial transactions. They need to judge the effectiveness of sales strategies and tactics on a near real- time basis in order to adjust to market conditions.

Your sales professionals will identify the information they need in order to support both sales and production reporting. They will need this information on a periodic basis (sales for a specific date, week or month) as well as on a period to date basis (production so far this year or month). They will also need reports detailing projected production, inventory levels and sales in queue.

Clerical Staff

The clerical staff is primarily responsible for all data entry operations. They are usually hourly employees who do not have a highly developed technical skill set. They often overlooked in determining the design requirements for a business intelligence data store. However, they can be a font of knowledge regarding productivity reporting and data quality issues.

When interviewing these team members, focus on the data issues that effect their productivity. They will be able to help you identify the elements which are essential to developing a comprehensive data quality program as well as staff productivity reporting.

Production Staff

Your production staff is most intimately involved in developing, producing and delivering your organizations? products and services. The information that most directly affects production includes: pending orders, inventory (current and projected), changes in production requirements (especially special marketing) and personal productivity.

Production is another group that is frequently underutilized in determining data warehouse requirements. They can provide vital information on the data elements such as inventory control and order processing reporting systems. They will also be your best resources for validating that the productivity requirements you have identified are in fact those that have the highest value for the organization.

Other

Depending upon the structure of your organization and the business you are in, you may have several other categories of knowledge workers you will need to interview. Some examples include: legal, political action teams, environmental impact specialists, medical practitioners and product design professionals. In each case, take the time to get to know the job as well as the person doing it, so you can understand the context in which the required information is used.

时间: 2025-01-01 22:54:26

设计数据仓库的注意事项(Part I)的相关文章

设计数据仓库的注意事项(Part II)

设计|数据 End Users The end users are who you are designing and building the data warehouse for ?your customers. They rely on the information they extract from the warehouse in order to work more effectively and efficiently. They also ultimately determin

购物网站设计方法与注意事项

  1. 网站名称 通常,设计师可以从资料中查到客户的公司名称,但营销型网站都有自己特定的网站名称,所以这点必不可少. 该项目客户给到我的名称叫做"云南游戏网",经斟酌发现,游戏网并不能够准确的诠释该网站的内容及定位,尔后建议客户更改为"云南电玩网",遂被采纳. 2.网站Logo 按以往经验,不少营销型网站的运营商在项目执行前都有着充分的准备.在设计方面,可能事先已请广告公司等机构,设计出网站的Logo,整套项目VI等,甚至专门成立新的公司来进行该项目的运营.所以,

优化策略:网页设计的七大注意事项

由于不同的搜索引擎在网页支持方面存在差异,因此在设计网页时不要只注意外观漂亮,许多平常设计网页时常用到的元素到了搜索引擎那里会产生问题. 框架结构(Frame Sets) 有些搜索引擎(如FAST)是不支持框架结构的,他们的"蜘蛛"程序无法阅读这样的网页. 图象区块(Image Maps) 除AltaVista.Google和Northern Light(现已停止公共搜索服务)明确支持图像区块链接外,其他引擎是不支持它的.当"蜘蛛"程序遇到这种结构时,往往会感到茫然

网页导航设计九大注意事项

一.注意超连结颜色与单纯叙述文字的颜色呈现 WWW的语言-HTML允许Webpage设计者特别标明单纯叙述文字与超连结的颜色,以便丰富Webpage的色彩呈现.如果您的网站充满知识性的信息,欲传达给访问者,建议您将网页内的文字与超连结颜色,设计成较干净素雅的色调,会较有利于阅读∶纯粹的叙述文字采用较暗.较深的颜色来呈现(如∶黑色.墨绿色.暗褐色),超连结文字则以较鲜明抢眼的色彩来强调(如∶亮黄色.翠绿色.鲜橘色),至于探访过的超连结则采用较低于原超连结亮度的颜色做呈现. 二.测试所有的超连结与导

网站导航在网页设计中的注意事项

一.注意超连结颜色与单纯叙述文字的颜色呈现 WWW的语言-HTML允许Webpage设计者特别标明单纯叙述文字与超连结的颜色,以便丰富Webpage的色彩呈现.如果您的网站   充满知识性的信息,欲传达给访问者,建议您将网页内的文字与超连结颜色,设计成较干净素雅的色调,会较有利于阅读∶纯粹的叙述文字采用较暗.较深的颜色来呈现(如∶黑色.墨绿色.暗褐色),超连结文字则以较鲜明抢眼的色彩来强调 (如∶亮黄色.翠绿色.鲜橘色),至于探访过的超连结则采用较低于原超连结亮度的颜色做呈现. 二.测试所有的超

Memcache Key 设计技巧及注意事项

刚刚开始研究Memcache,觉得Memcache Key的设计其实是十分重要的,搜了搜,感觉资料不是很多,下面这些资料主要是从官网上获得的,有些地方可能不太精确,仅供参考. 初始化Memcache Client # perl my $memclient = Cache::Memcached->new({ servers => [ '10.0.0.10:11211', '10.0.0.11:11211' ]}); # pseudocode memcli = new Memcache memcl

艾伟也谈项目管理,软件开发前期设计时的注意事项

说起软件设计,我们可能每个人都做过,但是什么样的方案才是好的设计方案?如何才能设计出一个好的设计方案?在设计过程中需要注意哪些呢?不要总是说:低耦合.可维护性.可扩展性.简易性.可重用性等,本文试图另一个角度出发,带着前面的这些问题,使大家能明白那些问题的答案,并与大家一起探讨. 什么样的方案才是好的设计方案? 当我们完成了一个良好的设计方案后,我们回头再仔细分析是什么因素影响了我们的思路,使我们最终完成(确切的说是选择了)了这个设计方案(而不是另一个),我们会发现这些因素是:用户功能性的需求.

数据仓库之我见 (设计篇)

设计|数据 建造数据仓库要做些什么?一般说来,建造数据仓库主要两个方面: 1.     与操作性数据库的接口设计. 2.     数据仓库本身的设计. 看上去好像很简单,但事实并非就这么按部就班,假设我是一个数据库设计师,我完全可以不管三七二十一,先载入一部分数据,让DSS分析员(还没忘吧,就是那个给设计数据仓库的人要求的)分析去吧,等他先给点意见出来,我们在动手也不迟. 下面,我将按照提出问题.解决问题的顺序来上一堂学前班.  建造数据仓库的主要难点是什么?首先纠正一个广泛存在的错误认识:建造

三个例子,让你看懂数据仓库多维数据模型的设计

一.概述 多维数据模型是最流行的数据仓库的数据模型,多维数据模型最典型的数据模式包括星型模式.雪花模式和事实星座模式,本文以实例方式展示三者的模式和区别. 二.星型模式(star schema) 星型模式的核心是一个大的中心表(事实表),一组小的附属表(维表).星型模式示例如下所示:   三.雪花模式(snowflake schema) 雪花模式是星型模式的扩展,其中某些维表被规范化,进一步分解到附加表(维表)中.雪花模式示例如下图所示: 从图中我们可以看到地址表被进一步细分出了城市(city)