| dc.contributor.advisor | 季延平 | zh_TW |
| dc.contributor.advisor | Chi,Yan Ping | en_US |
| dc.contributor.author (Authors) | 林于新 | zh_TW |
| dc.contributor.author (Authors) | Lin, Yu-hsin | en_US |
| dc.creator (作者) | 林于新 | zh_TW |
| dc.creator (作者) | Lin, Yu-hsin | en_US |
| dc.date (日期) | 2008 | en_US |
| dc.date.accessioned | 8-Dec-2010 15:55:05 (UTC+8) | - |
| dc.date.available | 8-Dec-2010 15:55:05 (UTC+8) | - |
| dc.date.issued (上傳時間) | 8-Dec-2010 15:55:05 (UTC+8) | - |
| dc.identifier (Other Identifiers) | G0096356008 | en_US |
| dc.identifier.uri (URI) | http://nccur.lib.nccu.edu.tw/handle/140.119/49653 | - |
| dc.description (描述) | 碩士 | zh_TW |
| dc.description (描述) | 國立政治大學 | zh_TW |
| dc.description (描述) | 資訊管理研究所 | zh_TW |
| dc.description (描述) | 96356008 | zh_TW |
| dc.description (描述) | 97 | zh_TW |
| dc.description.abstract (摘要) | 1960年代起資訊科技應用興起以協助組織運行，多數企業因缺乏資訊知識背景，紛紛購入套裝軟體協助業務營運。但套裝軟體無法切合企業的流程，且隨環境變遷和科技演進，不敷使用的問題日益嚴重。從資料庫設計的角度出發，套裝軟體複雜的資料架構、長期修改和存取資料而欠缺管理、無關連式資料庫的概念，導致組織的資料品質低落。當今組織如何將資料庫重新設計以符合所需、新舊系統資料該如何轉換以提升品質，是企業面臨的一大挑戰。 有鑑於此，本研究設計一套資料庫重構流程，以企業流程為基礎為企業設計客製化的資料庫，並將資料從套裝軟體移轉至該理想的資料庫。流程分三階段，階段1是運用資料庫反向工程（Database Reverse Engineering）的方法，還原企業現行資料庫的資料語意和模型架構；階段2則結合流程模型（Process Model）和資料模型（Data Model）的概念，建立以企業流程為基礎的理想資料庫；階段3利用ETL（Extract、Transform、Load）和資料整合的技術，將企業資料從現行資料庫中萃取、轉換和載入至理想資料庫，便完成資料庫重構的作業。 本研究亦將資料庫重構流程實做於個案公司，探討企業早期導入之套裝軟體和以流程為基礎的理想資料模型間的設計落差。實做分析結果，二者在資料庫架構設計、資料語意建立和正規化設計等三部分存有落差設計，因此在執行資料庫重構之資料移轉解決落差時，需釐清來源端資料的含糊語意、考量目的端資料的一致性和參考完整性、以及清潔錯誤的來源資料。 最後，總結目前企業老舊資料庫普遍面臨資料庫架構複雜、無法吻合作業流程所需、未制訂完善資料庫管理機制等問題，而本研究之資料庫重構流程的設計概念，能為企業建立以流程為導向的理想資料庫。 | zh_TW |
| dc.description.abstract (摘要) | The raising of information technique helped organization governance greatly was started since 1960s, but because of lack information background and knowledge, many organizations just simply brought software packages to assist business processes or organization governance. The result was those software packages which couldn`t fit in with the processes of organization` requirements were getting worse because of changes of environment. From the view of database design, it results in low quality of data because of the complexity of database structure, long-term modifications and accessing to data, and the lack of relational database knowledge. Nowadays, the problems of redesign database structure or transform data from a old system to a new system are great challenges to enterprises.Based on the above, thie research designed a process of database restruction in order to establish customized database based on businesss processes. There are three phases of this process. In phase 1, a company acquires the original data structure and semantic of its software package by the method of database reverse engineering. In phase 2, using concepts of process model and data model, the company establishes its ideal database based on businesss processes. In phase 3, it extracts, transforms, and load data from the current database of software package to ideal database by the technique of ETL and data integration. After these three phases, the company completes the process of data restriction.The process of database restruction is done in a case company to analyze the design gap between the current data model of software package and the ideal data model based on business processes. In the result of analysis, this research found out there are three gaps between its as-is and to-be data models. These three gaps are the design of database struction, the definition of data semantic, and the design of database normalization. Because of these design gaps, when removing gaps by data transformation, a company should pay attention to clarify the semantic of source data, considerate the consistency and referential integrity of destination data, and clean dirty data from source database.Finanlly, the summary of the problems a company using old database are the complexity of database structure, the unfit database for businesss processes, the lack of database management, etc. The process of database restruction this research design can assist a company in establishing ideal database based on business processes. | en_US |
| dc.description.tableofcontents | 第一章 緒論 1第一節 研究背景 1第二節 研究動機 3第三節 研究目的 4第四節 研究流程 5第二章 文獻探討 8第一節 企業流程之探討 8第二節 資料模型之探討 15第三節 資料庫反向工程之探討 19第四節 ETL之探討 24第五節 資料整合之探討 29第三章 研究架構與方法 31第一節 研究方法 31第二節 研究架構 33第三節 研究步驟 35第四章 個案探討與流程設計 39第一節 個案公司背景與資訊系統現況分析 39第二節 資料庫重構流程的三階段 47第三節 階段1：還原現行資料庫的實體資料模型 48第四節 階段2：設計理想資料庫的實體資料模型 55第五節 階段3：現行和理想資料庫的資料移轉 62第六節 資料庫重構流程 69第五章 個案實做與分析 70第一節 階段1：還原現行資料庫的實體資料模型之實做 70第二節 階段2：設計理想資料庫的實體資料模型之實做 75第三節 階段3：現行和理想資料庫的資料移轉之實做 84第六章 結論與建議 103第一節 研究結論 103第二節 研究貢獻 104第三節 後續研究建議 104參考文獻 105附件 個人保戶編號自動編號函式 110 | zh_TW |
| dc.format.extent | 171151 bytes | - |
| dc.format.extent | 288324 bytes | - |
| dc.format.extent | 372058 bytes | - |
| dc.format.extent | 550391 bytes | - |
| dc.format.extent | 639549 bytes | - |
| dc.format.extent | 3847590 bytes | - |
| dc.format.extent | 2718183 bytes | - |
| dc.format.extent | 5121757 bytes | - |
| dc.format.extent | 6847351 bytes | - |
| dc.format.extent | 578925 bytes | - |
| dc.format.extent | 675160 bytes | - |
| dc.format.extent | 525944 bytes | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.format.mimetype | application/pdf | - |
| dc.language.iso | en_US | - |
| dc.source.uri (資料來源) | http://thesis.lib.nccu.edu.tw/record/#G0096356008 | en_US |
| dc.subject (關鍵詞) | 資料庫重構 | zh_TW |
| dc.subject (關鍵詞) | 流程模型 | zh_TW |
| dc.subject (關鍵詞) | 資料模型 | zh_TW |
| dc.subject (關鍵詞) | 資料庫反向工程 | zh_TW |
| dc.subject (關鍵詞) | ETL | zh_TW |
| dc.subject (關鍵詞) | database restruction | en_US |
| dc.subject (關鍵詞) | process model | en_US |
| dc.subject (關鍵詞) | data model | en_US |
| dc.subject (關鍵詞) | database reverse engineering | en_US |
| dc.subject (關鍵詞) | ETL | en_US |
| dc.title (題名) | 以企業流程模型導向實施資料庫重構之研究－以S公司為例 | zh_TW |
| dc.title (題名) | The study of database reverse engineering based on business process module－with S company as an example | en_US |
| dc.type (資料類型) | thesis | en |
| dc.relation.reference (參考文獻) | 中文部分： | zh_TW |
| dc.relation.reference (參考文獻) | 1. 李玉秀，2008，不可不知的資料整合秘訣。2009年6月20日，取自：http://www.zdnet.com.tw/。 | zh_TW |
| dc.relation.reference (參考文獻) | 2. 李卓翰，2006，資料倉儲理論與實務，台北：學貫行銷股份有限公司。 | zh_TW |
| dc.relation.reference (參考文獻) | 3. 明雲青，2009，ETL。2009年6月15日，取自：http://www.digitimes.com.tw/。 | zh_TW |
| dc.relation.reference (參考文獻) | 4. 林傑斌、卓彰賢、張一岑，2006，資料倉儲理論、設計與應用，台北：網奕資訊科技。 | zh_TW |
| dc.relation.reference (參考文獻) | 5. 胡百敬、姚巧玟，2008，SQL Server 2008 SSIS 整合服務，台北：精誠資訊。 | zh_TW |
| dc.relation.reference (參考文獻) | 6. 盛銳、韵湘，2006『基於PowerDesigner的數據庫設計與實現』，電腦應用技術，2006年．第二期：1～5頁。 | zh_TW |
| dc.relation.reference (參考文獻) | 7. 藍中賢、吳郁瑩、李火山、陳銘智譯，Ramaz Elmasro & Shamkadant B. Navathe 著，2003，資料庫系統原理，台北：台灣培生教育出版股份有限公司。 | zh_TW |
| dc.relation.reference (參考文獻) | 英文部分 | zh_TW |
| dc.relation.reference (參考文獻) | 1. Chen, Peter P. “The Entity-Relationship Model - Toward a Unified View of Data,” ACM Transaction on Database System (1:1) 1976 pp: 9-36 | zh_TW |
| dc.relation.reference (參考文獻) | 2. Davis, K.H. “Lessons Learned in Data Reverse Engineering,” Proceedings of the 8th Working Conference on Reverse Engineering, Suttgart, Germany, 2001, pp: 323-327 | zh_TW |
| dc.relation.reference (參考文獻) | 3. Eiserhardt, K. “Building theories from case study research,” Journal of Management Review, (14:4) 1989, pp:523-550 | zh_TW |
| dc.relation.reference (參考文獻) | 4. Luo, Wenhong and Tung, Y. Alex “A framework for selecting business process modeling methods,” Industrial Management & Data Systems 1999, pp:312-319 | zh_TW |
| dc.relation.reference (參考文獻) | 5. Mayer, R.J. “IDEF0 Function Modeling,” Knowledge Based Systems, College Station Texas, 1992 | zh_TW |
| dc.relation.reference (參考文獻) | 6. Seligman, Len, Rosenthal, Arnon, Lehner, Paul, and Smith, Angela “Data Integration: Where Does the Time Go?,” IEEE Technical Committee on Data Engineering, Data Engineering Bulletin, California, 2002 | zh_TW |
| dc.relation.reference (參考文獻) | 7. Yeh, D.M., Li, Y.W., and Chu, C.W., “Extracting entity-relationship diagram from a table-based legacy database,” The Journal of System and Software (81) 2008, pp:764-711 | zh_TW |
