Please use this identifier to cite or link to this item: https://ah.lib.nccu.edu.tw/handle/140.119/95534
題名: 以企業樣版為基礎之需求分析架構
作者: 朱明強
貢獻者: 曾淑峰
朱明強
關鍵詞: 企業樣版
統一化程序
需求分析
UML
Zachman Framework
日期: 2002
上傳時間: 9-May-2016
摘要:   系統分析困難的地方是找出符合使用者要求的需求,有時候使用者的需求與企業目標之間產生不能配合的狀況,傳統的需求分析鮮少注意此,大抵都是只著重於滿足客戶眼前的需求,並未考量這需求是否符合企業策略目標。傳統的需求分析方法,如:訪談、問卷、觀察使用者、研讀企業的文件,還是需要的,但對大型系統而言,整理文件是很費時的,對目前快速變化的競爭環境,所造成的需求變動性,上述的需求分析方法必須做個改進,如此才能跟得上競爭環境快速變化而導致的需求改變。基於此,只有重覆利用前人對某一問題的解決方式,才能避免浪費資源於解決已有標準解答的問題,樣版(Pattern)的概念似乎可以幫助我們避免無謂的資源浪費。\r\n  本研究以Zachman Framework的計劃者的觀點做為需求分析的思考架構,亦即建構系統時所需考慮的六種角度─5W1H。至於如何充實此架構的內容,本研究提出以E-P企業模型的企業樣版做為此架構的內涵。建議依塑模企業的情況,尋找合適的企業樣版。以企業樣版塑模企業可以比較一致的方式調適企業面臨動態的環境挑戰,面對不斷的變,企業必須動態的調整企業策略,而資訊系統也需即時的更新,本研究利用前人已證實無誤且已存在的企業樣版可以幫助企業快速建立新的或是變更已有的企業模型,而順利找到符合企業策略目標的需求並建立系統進而輔助策略的遂行。本研究目的是建立協助尋找系統功能需求的分析架構,不直接以描述使用案例進行,即資訊系統與使用者之間的互動,來了解資訊系統應提供的功能。理由在於本研究強調找出符合企業策略目標的需求,必須先進行策略分析,然後找出策略活動,進而以本資訊需求架構模塑企業的目標、達成企業目標的程序。這樣的好處在於可對企業程序做深入的了解,當環境變化時而需要對企業程序做改進甚至創造新的企業程序時可以有參考的模型。這是直接進行描述使用案例所做不到的。
參考文獻: 一、中文部分\r\n1.李美華等譯,Earl Babbie著,1998,The Practice of Social Research, 8th ed.,台北,時英出版社。\r\n2.宋珍儀,民90,資訊需求分析架構─以網路基金下單為例,國立政治大學資訊管理研究所碩士論文。\r\n3.李幸秋、曾淑峰,以樣式概念進行物件導向企業塑模--以銀行小額信用貸款為例(系列之二),待發表,2002/7。\r\n4.陳志昌譯,Sinan Si Alhir 著,2000,UML In a Nutshell,台北,美商歐萊禮(股)公司。\r\n5.戴瑞芝、吳景章,民91,台北金融大學eMBA電子銀行課程報告。\r\n二、英文部分\r\n1. Alexander, C. Timeless Way of Building, New York: Oxford University Press, 1979.\r\n2. Alhir, S. S. UML In A Nutshell, O’Reilly, 1999.\r\n3. Beck, K. \"Using a Pattern Language for Programming, Workshop on Specification and design\", ACM SIGPLAN Notices, p.16, 1988.\r\n4. Benyon, D., and Skidmore, S. “Towards a Tool Kit for the Systems Analyst”, The Computer Journal, 30(1): 2-7, 1987.\r\n5. Berlin, L. M. “User-Centered Approach Definition: A Methodology and Case Study”, Hewlett-Packard Journal, 40(5) : pp. 90-97, 1989.\r\n6. Bohner, S. A. and Arnold, R. S. (Ed.) Software Change Impact Analysis, IEEE Computer Society Press, 1996\r\n7. Boehm, B.W. Software Engineering Economics, Prentice-Hall, 1981.\r\n8. Booch, G., Rumbaugh, J. and Jacobson, I. The Unified Modeling Language, Addison-Wesley, 1999.\r\n9. Booch, G., Jacobson, I. and Rumbaugh, J.The Unified Modeling language User Guide, Addison-Wesley, MA, 1998.\r\n10. Booch, G., Rumbaugh, J. and Jacobson, I The Unified Software Development Process, Addison-Wesley, 1999\r\n11. Cunningham, W. \" Panel on Design Methodology \", ACM SIGPLAN Notices, pp:94-95.,1993\r\n12. Dobson, J. E., Martin, M. J., Olphert, C. W., and Strens, M. R. ”The ORDIT Approach to Requirements Identification”, Proceedings of the Sixteenth Annual International Computer Software & Applications Conference, IEEE Computer Society, Sep. 1992.\r\n13. Eriksson, H. E. and Penker, M. UML toolkit, John Wiley & Sons, Inc., 1998.\r\n14. Eriksson, H. E. and Penker, M. Business Modeling with UML─Business Patterns at Work, John Wiley & Son, Inc., 2000.\r\n15. Evernden, R. ”The Information Framework”, IBM System Journal, 35(1), p.37, 1996.\r\n16. Ferdinandi, P. L. A Requirements Pattern: Succeeding in the Internet Economy, Addison-Wesley, 2001.\r\n17. Gale, T. and Elred, J. Getting Results with the Object-Oriented Enterprise Model, SIGs Books, New York, 1996.\r\n18. Gamma, E. ”Object-Oriented Software Development based on ET++:Design Patterns, Class Library, Tools”, PhD thesis, University of Zurich, 1991.\r\n19. IEEE Standards Collection Software Engineering 1993 Edition, IEEE, Inc. NY, 1993\r\n20. Kang, K. C., Cohen, S. G., Hess, J. A., Novak, W. E., and Peterson, A., S.”Feature-Oriented Domain Analysis Feasibility Study”, Software Engineering Institute, Pittsburgh, PA, Nov, 1990.\r\n21. Kilov H,and Simmonds I. ”Business Patterns and Viewpoints”, SIGSOFI’ 96 Workshop, San Francisco CA USA, 1996 ACM.\r\n22. Larman, G. Applying UML and Patterns, 2nd edition, Prentice Hall PTR, 2002.\r\n23. McDermid, J. A. “Requirements Analysis: Problems and the STARTS Approach”, In IEE Colloquium on ‘Requirements Capture and Specification for Critical Systems’(Digest No. 138), Institution of Electrical Engineers, November 1989.\r\n24. Milson, F. D., “Using CORE with SDL to Specify Requirements”, SETSS 89 (Conf. Publ. No. 306), pp. 137-141. Institution of Electrical Engineers(IEE), London, 1989.\r\n25. Nuseibeh, B., and Easterbrook, S. Proceedings of the Conference on The Future of Software Engineering 2000, Limerick, Ireland, ACM Press, pp: 35 - 46 New York\r\n26. Rumbaugh J. \"What is a Method?\", JOOP, OCT 1995.\r\n27. Sowa, J. F, and Zachman, J. A. \" Extending and Formalizing the Framework for Information Systems Architecture \", IBM Systems Journal, 31(3), 1992.\r\n28. Scott-Morton, M.S. “The State of the Art of Research”, The Information Systems Research, Poston:Harvard Business School Press, 1984, pp.13-41。\r\n29. Sommerville, I. Software Engineering, 5th edition Addison-Wesley, 1996\r\n30. Sommerville, I., Rodden, T., Sawyer, D., Bentley, R.and Twidale, M. “Integrating ethnography into the Requirements engineering Process”,In Proc. RE’93,San Diego CA,165-73.\r\n31. Timmers, P. “Business Models for Electronic Markets,” Electronic Markets, 8(2), pp: 3 — 8, 1998\r\n32.Vasudeva, G.,Adams, J.,Koushik,S., and Galambos,G. Patterns for e-business─A Strategy for Reuse, IBM Press, 2001.\r\n33. Weirich, H. “ The TOWS Matrix: A Tool for Situational Analysis”,Long Range Planning, 1982.\r\n34. Zachman, J. A. \"A Framework for Information Systems Architecture.\", IBM Systems Journal, 26(3), 1987.\r\n35. Zave, P. ” Classification of Research Efforts in Requirements Engineering ” ACM Computing Surveys, 29(4), pp: 315-321,1997.\r\n三、網站部份\r\n1.Harverd Business School, http://www.hbs.edu/dor/papers2/0001/01-002.pdf,“The role of the business model in capturing value from innovation: evidence from Xerox corporation’s technology Spinoff companies “, Henry Chesbrough, Richard s. Rosenbloom, 2001.\r\n2.Innovation Labs, http://kmlab.com./4Gwarfare.html, June 20, 2000\r\n3. The Rational Edge, http://www.therationaledge.com/content/jan_01/f_rup_pk.html, Philippe Kruchten, Jan 1st, 2001.\r\n4.Information Engineering Service(IES) Web Site, http://members.ozmail.com.au/~visible/papers/zachman3.htm,\"Concepts of the Framework for Enterprise Architecture\", John Zachman,1996.\r\n5.The Zachman Institute for Framework Advancement, http://www.zifa.com/frmwork.htm, 2001.
描述: 碩士
國立政治大學
資訊管理學系
89356002
資料來源: http://thesis.lib.nccu.edu.tw/record/#A2010000336
資料類型: thesis
Appears in Collections:學位論文

Files in This Item:
File SizeFormat
index.html115 BHTML2View/Open
Show full item record

Google ScholarTM

Check


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.