博碩士論文 etd-0624103-221031 詳細資訊


[回到前頁查詢結果 | 重新搜尋]

姓名 許正沂(Cheng-Yi Hsu) 電子郵件信箱 andyhsu@tw.ibm.com
畢業系所 資訊管理學系研究所(Information Management)
畢業學位 碩士(Master) 畢業時期 91學年第2學期
論文名稱(中) 套裝軟體導入之需求對應及差異分析方法論
論文名稱(英) Package Implementation :
A Methodology For Requirement Gap Analysis
檔案
  • etd-0624103-221031.pdf
  • 本電子全文僅授權使用者為學術研究之目的,進行個人非營利性質之檢索、閱讀、列印。
    請遵守中華民國著作權法之相關規定,切勿任意重製、散佈、改作、轉貼、播送,以免觸法。
    論文使用權限

    電子論文:校內公開,校外永不公開

    論文語文/頁數 中文/88
    統計 本論文已被瀏覽 5560 次,被下載 58 次
    摘要(中) 在全球化激烈競爭下,企業為提高競爭優勢,思考採用套裝軟體,以快速滿足企業需求已成為主要趨勢。但企業進行資訊系統導入往往遇到許多障礙,造成專案時程及專案成本失去控制,以致於失敗多於成功。這失敗的主要關鍵之一是缺乏一套需求與套裝軟體的對應方法來做系統異差分析。
    本論文主要目的是發展一套企業需求與套裝系統差異分析的方法論,來解決上述問題。應用此方法論可以快速正確地分析使用者之需求與目標系統之差異,讓使用者、分析師,程式設計師間有良好的溝通方法,提供未來系統客製化之依據,最後能讓專案成功上線。
    摘要(英) The global business is facing the intensive competitive environment. To overcome the competition, most enterprises contentiously try different information systems to strengthen their competition and to extent their businesses. In order to execute the enterprises marketing strategies effectively, business organization applies various software from in-house development to standard package software either made in Taiwan or made in nations. However, while implementing the information system into specific project, this software caused many obstructions in both project time framing design and project cost control. To exam this problem, we found there is no appropriate requirement and package software or tool to manage the system gaps analysis.
    The main purpose of this thesis is to solve the present package software problem and develop a method to meet the enterprise needs in system difference analysis. We use the Unified Module Language (UML), use case diagram, drawing , activity diagram, use case description and decision table to complete the difference analysis between package software and specific project. Applying this method, the user not only can control the difference between the requirement system and object system precisely, but also build a communication channel among the users, system analysis, and programmers. In addition, the method provides a trend of customized system to succeed the project on line
    關鍵字(中)
  • 物件導向
  • 需求目標
  • 需求分析
  • 套裝軟體
  • 差異分析
  • 關鍵字(英)
  • object oriented
  • gaps analysis
  • Goal
  • UML
  • package software
  • requirement module
  • 論文目次 第一章 緒論……………………………………………………………………………11
    第一節 研究背景與動機…..……………………………….……………………………….11
    第二節 研究目的與範圍.……………………………….…………………………………..12
    第三節 研究方法概述…..…………………………………………..………………………14
    第四節 論文架構 ………………………………………….……………………………….16
    第二章 文獻探討..….…………………………….….…………………..…………..18
    第一節 需求工程..……………………………………….….…………………………..….18
    第二節 套裝軟體的導入方法探討……….……………………...…………………..…….22
    第三節 需求分析方法..…………………………………….………….…….……………..25
    第四節 本研究的方向………………………………………………………..…………….28
    第三章 企業需求與套裝軟體塑模方法論 …………………………..…..29
    第一節 找出使用者目標 …….……………………………………..…………………….32
    第二節 使用者需求分析及功能塑模…..…………………………………..……….…….33
    第三節 套裝軟體功能塑模…………………………………………………….……….…41
    第四節 使用者需求與套裝軟體的對應……………………………….…….……………43
    第五節 使用者需求與套裝軟體差異分析……………………………………..…………46
    第四章 實例應用 …………………………………………………………….……49
    第一節 使用者需求描述………………………………………………….……………….49
    第二節 找出使用者之目標……….……………………………………………….………53
    第三節 需求轉換…………….………………………………………………………….…56
    第五章  實例應用-差異分析(Gap Analysis)…….……….……….……..71
    第一節 使用者需求與套裝軟體對應………………….………………….……………71
    第二節 使用者需求與套裝軟體差異分析…………….………..……………….….….74
    第三節 差異彙總……………………………………….…….……………..…………..79
    第六章  結論與建議 ……………………………..…….……….…….…………...83
    參考文獻 …………………………………………….……….…….……….…………85
    參考文獻 1.吳仁和,林信惠,系統分析與設計-理論與實務應用,智勝文化,台北,2002。
    2.張君龍,“企業資源規劃系統(ERP),”企業資訊化年鑑,開放時代通訊社,台北市,1999。
    3.林海光,“導入ERP之道,企業資訊化年鑑,”開放時代通訊社,台北市,1999。
    4.李煒杰,“應用於企業資訊系統之動態樹狀結構需求分析方法”東海大學,台北市,2000。
    5.吳仁和、戴偉峻、夏則智、屠益民,”企業資源規劃系統之導入模式與應用:以某大企業為例”,2000。
    6.游育蓁&何玉美,“如何成功導入ERP,”管理雜誌,哈佛企業管理顧問(股)公司,台北市,1999。
    7.洪子凂,”企業資源規劃(ERP)導入策略與模式”國立台北科技大學,2000
    8.王育民,”介面藍圖:一個需求表達與溝通工具”,中山大學資管系碩士論文,1995
    9.Booch, G., “Object-Oriented Analysis and Design – With Applications,” Addison-Wesley ,Reading, Massachusetts, 1994.
    10.Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, Addison-Wesley, Reading, Massachusetts,1999
    11.Byrd,T.A.,Cossick,K.L., and Zmud,R.W.,”A Synthesis of Research on Requirements Analysis and Knowledge Acquisition Techniques,” MIS Quarterly,1992
    12.Cockburn, A., Writing Effective Use Cases, Addison Wesley, Boston,2001.
    13.Davis, G..B. Commentary on information system:To buy, build, or customize? Accounting Horizons , 1988.
    14.Davis,A. M. and Hsia,P., “Giving Voice to Requirements Engineering.” IEEE Software, 1994.
    15.Fowler, M. and Scott, K., UML Distilled: A Brief Guide to the Standard Object Modeling Language, 2nd Edition, Reading, Massachusetts, Addison-Wesley,2000.
    16.Goodrich. Victoria, and Lorne Olfman, :An Experimental Evaluation of Task and Methodology Variables for Requirements Definition Phase Success” In Bruce D. Shriver (editor) Proceedings of the Twenty-Third Annual Hawaii International Conference on System Sciences, 1990.
    17.Grosz, G., “Building Information Ssytem Requirements Using Generic Structure,” IEEE 16th Annual International Computer Software and Applications Conference, 1992,
    18.Hooper, J. W. and Hsia, P., “Scenario-based for Requirements Identification,” ACM Sigsoft Software Engineering, 1982.
    19.IBM “ Method Blue Project Work Plan”, Technique Paper ,IBM Global Service, 2000.
    20.IBM “Use Case Model”, APP130,IBM Global Services, 2000.
    21.Institute of Electrical and Electronics Engineers, IEEE Standard Glossary of Software Engineering Terminology, 1983.
    22.Jacobon,I., Booch, G., and Rumbaugh, J., The Unified Software Development Process,Addison-Wesley,Reading, Massachusetts,1999.
    23.Jacobon, I., Christerson, M., Jonsson, P., and Overgaard, G., Object-Orientd Software Engineering:A Use Case Driven Approach,Addison-Wesley,Reading,Massachusetts,1996.
    24.Jonathan Lee Nien-Lin Xue,Jong-Yih Kuo,”Structuring Requirement Specifications with Goals” Information and Software Technology,SCI
    25.Jonathan Lee Nien-Lin Xue,1999,”Analyzing User Requirement by User Cases : A Goal –Driven Approach” IEEE software,.SCI.
    26.J. Lee, N.L.,Xue,K.H Hsu and S.J.H. Yang 1999.”Modeling Imprecise Requirement With Fuzzy Objects” Information Sciences: on International Journal..SCI.
    27.J. Mylopoulos, L. Chung. and B. Nixon, “Representing and using nonfunctional requirements:A process-oriented approach.” IEEE Transaction on Software Engineering, 1992.
    28.J. Mylopoulos, L. Chung. and E. Yu.,“From object-oriented to goal-oriented requirements analysis.” Communication of ACM ,1999.
    29.Lewis, T. G. and Oman, P. W., “The Challenge of Software Development,” IEEE Software Engineering,1990.
    30.Lucas, H.C., Jr., Walton, E.J., and Ginzberg, M.J. Implementing package software. MIS Quarterly 12 ,1988.
    31.Priddle, P.”Package/Solution Selection Approach Notes for Guidance”, IBM , 2001.
    32.R. Darimont A. van Lamsweerde and E. Leitier. “Managing conflicts in goal-driven requirements engineering.” IEEE Transactions on Software Engineering. ,1998
    33.S. Easterrook. “Domain modeling with hierarchies of alternative viewpoints” In Proceedings of the IEEE International Symposium on Requirements Engineering.,1993.
    34.SAP AG, “Global Accelerated SAP: Your Flight Plan for Implementing a Comprehensive Stratrgic”,SAP,2001
    35.SAP AG., “AcceleratedSAP cuts time and cost of implementing SAP Solution”,http://www.sap.com/press/index.htm
    36.SAP AG, “Global AcceleratedSAP: Your Flight plan for Implementing a Comprehensive Strtegic Solution”,
    37.SAP AG, “Global AcceleratedSAP: “Driving Rapid Implementions for Rapid Results”
    38.Soh, C., Kien, S.S., and Tay-Yap, J.,”Cultural Fits and Misfits: Is ERP a Universal Solution?” Communications of the ACM, 2000.
    39.Software Test & Evaluation Panel (STEP), Requirements Definition Implementation Team. Operational Requirements for Automated Capabilities,Draft Pamphlet, 1991.
    40.Southwell, K., K. James, B. A.Claarke, B. Ashworth, M. Norris and V. Patel, “Requirements Definition and Design”, The STARTS Guide, 1987.
    41.W.N. Robinson and S.Fickas. “Supporting multi-perspective requirements engineering.” In Proceedings of first International Conference on requirement engineering,.IEEE Computer Society,1994
    42.W.N. Robinson and V. Volkov.”Supporting the negotiation.” Communications of the ACM. 1998.
    43.Yourdon, E., Managing the System Life Cycle, Yourdon Press,Englewood Cliffs, New Jersey,1988.
    44.Yourdon, E., Modern Structured Analysis, Yourdon Press ,Englewood Cliffs, New Jersey,1989.
    口試委員
  • 林信惠 - 召集委員
  • 趙善中 - 委員
  • 吳仁和 - 指導教授
  • 口試日期 2003-05-20 繳交日期 2003-06-24

    [回到前頁查詢結果 | 重新搜尋]


    如有任何問題請與論文審查小組聯繫