promotion image of download ymail app


The wide range of critical information requirements for business decision-making and their diverse sources, both internal and external to the organization, present a clear challenge to the development of data warehouses and the decision support systems that utilize them. Wetherbe recognizes that executive information requirements are different from operational requirements and chides IS professionals for their lack of adequate methodology to determine executive information needs. Simply capturing terabytes of transaction data and loading it into a data warehouse-a common data warehouse development method-is simply not sufficient. He proposes a methodology that addresses what he claims are four fundamental mistakes that developers typically make when attempting to determine executive information needs. bThese mistakes are viewing systems as functional instead of cross-functional, interviewing managers individually instead of jointly, asking the wrong questions during the interview, and not allowing trial-and-error in the detail design processQ.

Recognizing the cross-functional and more recent cross-organizational nature of executive information requirements demands significant integration efforts and presents organizational as well as technical challenges. Disciplined approaches, such as Joint Application Design (JAD), to bring stakeholders together can be used to deal with this challenge. But more telling are the questions and content discussed at such joint meetings. Wetherbe contends that simply asking, bWhat information do you want?Q is counter-productive. Questions must address problems, solutions, decisions, critical success factors, ends (goals, performance measures), and means (alternatives). Not unlike the information needs discussed above, these questions cause managers to focus on business performance, how to measure and evaluate business success, and how to improve business effectiveness. Data warehousing becomes an enabling technology.

1 個解答

  • 1 0 年前

    生意決策和他們的完全不同的來源的多種批判性的訊息需求,既內部又在以外組織,向一清楚挑戰介紹給數據倉庫和利用他們的決策支持系統的發展。認出執行訊息需求不同于操作要求並且申斥給他們缺乏足夠方法學確定執行訊息需要的專業人士。完全捕獲terabytes的交易數據的並且對倉庫數據的裝一普通方法發展倉庫數據完全不足夠。他提議一方法學位址他聲稱什麼在基本錯誤當試圖確定執行需要訊息時,開發者通常犯。錯誤正認為系統職能而不是十字架職能,分別接見經理而不是共同, 在接見期間問錯誤的問題,並且不在詳細設計過程中允許反覆試驗。

    認出以及技術挑戰執行訊息需求的十字架職能和更新近十字架機構化自然要求顯著綜合努力並且給機構化。 管教接近,例如共同應用設計(JAD),把賭金保管者集合在一起用來經營這幾次挑戰。但是告訴的更多是在這樣的共同會議討論的那些問題和內。鬥爭那僅僅問,你想要的訊息嗎? 產生相反結果的。 問題寄給必須問題,解決辦法,決定,關鍵原素成功,結束(目標,性能測量),並且的意思是(選擇)。不與訊息需要不同在上面討論,這些問題引起經理集中于商務運作,以便怎樣測量並且評價生意成功,和怎樣改進生意效力。 數據把儲存于倉庫成為一項啟動技術。

    參考資料: 自己翻譯的
    • Commenter avatar登入以對解答發表意見