我國軟體產業資訊系統發展人員資訊系統發展方法論使用之研究

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：124

、訪客IP：3.149.23.182

姓名

謝清華(Afago Shieh) 查詢紙本館藏

畢業系所

資訊管理學系

論文名稱

我國軟體產業資訊系統發展人員資訊系統發展方法論使用之研究

相關論文

★ 信用卡盜刷防治簡訊規則製作之決策支援系統	★ 不同檢索策略之效果比較
★ 知識分享過程之影響因子探討	★ 兼具分享功能之檢索代理人系統建構與評估
★ 犯罪青少年電腦態度與學習自我效能之研究	★ 使用AHP分析法在軟體度量議題之研究
★ 優化入侵規則庫	★ 商務資訊擷取效率與品質促進之研究
★ 以分析層級程序法衡量銀行業導入企業應用整合系統(EAI)之關鍵因素	★ 應用基因演算法於叢集電腦機房強迫對流裝置佈局最佳近似解之研究
★ The Development of a CASE Tool with Knowledge Management Functions	★ 以PAT tree 為基礎發展之快速搜尋索引樹
★ 以複合名詞為基礎之文件概念建立方式	★ 利用使用者興趣檔探討形容詞所處位置對評論分類的重要性
★ 透過半結構資訊及使用者回饋資訊以協助使用者過濾網頁文件搜尋結果	★ 利用feature-opinion pair建立向量空間模型以進行使用者評論分類之研究

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

[檢視]

[下載]

本電子論文使用權限為同意立即開放。
已達開放權限電子全文僅授權使用者為學術研究之目的，進行個人非營利性質之檢索、閱讀、列印。
請遵守中華民國著作權法之相關規定，切勿任意重製、散佈、改作、轉貼、播送，以免觸法。

摘要(中)

我國軟體人員生產力偏低，軟體品質亦未達國際水準，主要原因在於軟體廠商未能有效運用軟體工具開發軟體，而且軟體開發方法過程不健全，產生系統多次修改、品質不穩定無法驗收等情事，導致每人年產生之營業額偏低。
使用資訊系統發展方法論來開發資訊系統，有助於提高資訊系統的品質與開發過程的效率與效益。但是由國外研究報告指出，資訊發展人員不會使用及不知道在不同系統發展階段，應該使用何種方法來發展資訊系統是效果不彰的原因之一。因此本研究以資訊系統發展人員所具備的資訊系統發展方法論知識的觀點，探討資訊系統發展方法論技術的使用情況，及其對所發展系統成效的影響。
本研究將資訊發展人員所具備的資訊系統發展方法論知識，分成對「知識了
解的不一致」與「知識的混亂沒有結構」，並進一步去探討這兩項因素對資訊系統發展方法論技術使用的影響，及資訊系統發展方法論技術的使用對資訊系統發展效益的影響。最後研究發現，〈1〉資訊系統發展人員對資訊系統發展方法論知識了解的不一致，對資訊系統發展方法論技術的使用會有負面的影響。〈2〉資訊系統發展方法論的知識混亂沒有結構，對資訊系統發展方法論技術的使用會有負面的影響。〈3〉資訊系統發展方法論技術的使用，對資訊系統發展效益會有正面的影響。

摘要(英)

關鍵字(中)

★ 資訊系統發展方法論知識
★ 資訊系統發展方法論技術

關鍵字(英)

★ no

論文目次

目錄
圖目錄 …………………………………………………………………………III
表目錄 ……………………………………………………………………………IV
第一章緒論 ………………………………………………………………………1
第一節研究背景 ……………………………………………………………1
第二節研究動機 ……………………………………………………………2
第三節研究目的 ……………………………………………………………3
第四節研究範圍 ……………………………………………………………3
第五節研究程序 ……………………………………………………………3
第二章文獻探討 …………………………………………………………………4
第一節軟體產業 ……………………………………………………………4
第二節知識的定義 …………………………………………………………5
第三節資訊系統發展方法論 ………………………………………………5
第四節資訊系統發展效益…………………………………………………17
第三章研究設計與方法…………………………………………………………19
第一節研究架構與構念定義………………………………………………19
第二節研究命題……………………………………………………………19
第三節變數操作……………………………………………………………20
第四節研究假說……………………………………………………………22
第五節問卷設計……………………………………………………………23
第六節研究對象與資料蒐集………………………………………………24
第四章資料分析與結果…………………………………………………………25
第一節樣本結構分析………………………………………………………25
第二節問項的收斂程度……………………………………………………29
第三節信度與效度分析……………………………………………………32
第四節研究假說檢定………………………………………………………38
第五節研究發現……………………………………………………………43
第五章結論與建議………………………………………………………………44
第一節研究結論……………………………………………………………44
第二節管理實務建議………………………………………………………45
第三節研究限制……………………………………………………………46
第四節後續研究……………………………………………………………47
參考文獻 …………………………………………………………………………49
附錄一研究問卷

參考文獻

參考文獻
中華民國資訊軟體協會，「2002會員名錄」，中華民國資訊軟體協會。2002年3月20日
季延平、郭鴻志，系統分析與設計，1th，華泰，1995年。
孫如珍，「我國軟體產業發展趨勢與因應策略分析」，財團法人資訊工業策進會，資訊市場情報中心（MIC）。2000年12月。
陳勇如（民86），“以圖形分解機制對 DFDs 自動轉換Structure Charts的方法” ，淡江大學資訊工程研究所未出版碩士論文。
許瓊予，「我國軟體產業競爭力分析」，財團法人資訊工業策進會，資訊市場情報中心（MIC）。1997年7月。
黃以宜（民86），“國內軟體業者使用應用軟體開發工具之研究” ，淡江大學資訊管理研究所未出版碩士論文。
游雅祺（民90），“技術知識特性、知識整合機制與知識移轉關係之研究”，國立
中央大學企業管理研究所碩士論文
賴威龍（民86），“組織知識流通之研究－以臺灣資訊硬體業為例”，政治大學科技管理研究所未出版碩士論文。
Ashworth, C. and Slater, L., An Introduction to SSADM Version 4, McGraw-Hill, 1993.
Attewell, P., “Technology diffusion and organization learning: the case of business
computing,” Organization Science, Vol. 3(1), 1992. 1-19.
Bailey, J. E. & Pearson, S. W., “Development of A Tool For Measuring and Analyzing
Computer User Satisfaction,” Management Science, Vol. 29, No. 5, May 1983. 530-543.
Carmar, M., ”CASE is software automation,” Prentice-Hall, 1989.
Carey, J. M. & Mcleod, R., ”Use of System Development Methodology and Tools,” Journal of Systems Management, Vol. 39, No. 3. Mar 1988. 63-64.
Charles, R., Necco, C. L., Nancy, G. & Tsai, W., “Systems Analysis and Design : Current Practices,” MIS Quarterly, December 1987. 461-477.
Chatzoglou, P., “Use of methodologies: an empirical analysis of their impact on the economics of the development process,” European Journal of Information Systems, Vol. 6, 1997. 256-270.
Chou, Shih-chieh, “Knowledge Management on Cognitive Processing with System Development Knowledge,” WDSI 2002 Proceedings, Western Decision Science Institute 2002 Annual Meeting, Las Vegas, U.S.A., Apr. 2-5, 2002, 735-737.
Corbitt, G. F. & Norman, R. J., “CASE implementation:accounting for the human element,” Information and Software Technology, Vol. 33(9), 1991. 637-649.
Fayad, M.E., Tsai, W. & Fulghum, M.L., “Transition to object-oriented software development,” Communications of ACM, Vol. 39 (2), 1996.108-121.
Fedorowicz, J. & Villeneuve, A. O., “Surveying object technology usage and benefits: A test of conventional wisdom,” Information & Management, Vol. 35, 1999. 331-344.
Fichman, R. G., “Information trechnology diffusion: A review of empirical research,” In DeGross, J. I., Becker. J. D. and Elam. J. J. Eds., Proceedings of the thirteenth International Conference on Information Systems.(Dallas, TX, 1992). 195-206.
Fichman, R. G. & Kemerer, C. F., “Object-Oriented and Conventional Analysis and Design Methodologies,” Computer, October 1992. 22-39.
Finkelstein, C. An Introduction to Information Engineering: From Strategic Planning to Infromation System. Addison Wesley. 1990.
Fitzgerald, B.,” Whither system development: time to move the lamppost?,” In Lissoni et al. (Eds.), Proceedings of Second Conference on Information Systmes Methodologies, 1994. 371-380.
Fitzgerald, B., “An empirical investigation into the adoption of systems development methodologies,” Information & Management, Vol.34, 1998. 317-328.
Galletta, D. F., and Lederer, A. L., “Some Cautions on the Measurement of User Information Satisfaction,” Decis. Sci., Vol. 20, 1989. 419-438.
Galup, S. D. & Dattero, R., “Information Engineering Methodologies and Organizational Change: An Exploratory Study,” Journal of Computer Information Systems ,Winter 2000-2001. 48-51.
Gladden, G.R., “Stop the Life-Cycle, I Want to Get Off,” Software Engineering Notes, Vol. 7, No. 2, 1982. 35-39.
Guinan, P. J., Cooprider, J. G. & Sawyer, S., ”The effective use of automated application development tools,” IBM SYSTEM JOURNAL, Vol. 36(1), 1997. 124-139.
Hardy, C. J., Thompson, J. B. & Edwards, H. M., “ The use, limitations and ustomization of structured systems development methods in the United Kingdom,” Information and Software Technology, Vol. 37, No. 9, 1995. 467-477.
Hedlund, ”A model of Knowledge management and the N-form corporation,” Strategic Management Journa, Vol.15, 1994. 73-90.
Howard, G. S., Bodnovich, T., Janicki, T., Liegle, J., Klein, S., Albert, P. & Cannon, D., “The efficacy of matching information systems development methodologies with application characteristics – an empirical study,” The Journal of Systems and Software, Vol. 45, 1999. 177-195.
Hunter, J. E. and D. W. Gerbing,“Unidimensional Measurement, Second Order Factor Analysis, and Casual Models, ” Research in Organizational Behavior, JAI Press, 4, 1982. pp.267-320.
Iivari, J., “Why are CASE tools not used ? ,” Communication of the ACM, Vol. 39(10), 1996. 94-103.
Isoda, S., Yamamoto, S., Kuroki, H. & Oka, A., “Evaluation and Introduction of the Structured Methodology and A CASE Tool,” J. SYSTEMS SOFTWARE, Vol. 28, 1995. 49-58.
Jaakkola, J. E. & Drake, K. B., “The Universal Systems Development Methodology,” Journal of Systems Management Feburary, 1991. 6-11.
Johnson, R. A. & Hardgrave, B. C., “Object-oriented methods: current practices and attitudes,” The Journal of Systems and Software, Vol. 48. 1999. 5-12.
Johnson, R. A., “THE Ups and Downs of Object-Oriented Systems Development,” Communication of the ACM, Vol. 43, No. 10, October 2000. 69-73.
Kim, C. S. & Peterson, D. K.,”Developers’ Perceptions of Information Systems Success Factors,” Journal of Computer Information Systems, Winter 2000-2001. 29-35.
Kliem, R. L., “Selecting The Right Structured Analysis Software Package,” Journal of Systems Management, July, 1989. 11-30.
Kramer, M., “Developers Find Gains Outweight OO Learning Curve,” Software
Magazine, November, 1993. 23-33.
Lyytinen, K., “Expectation Failure Concept and Systems Analysts View of Information System Failures: Results of an Exploratory Study,” Information and Management, Vol. 14, 1988. 45-56.
McDermid, J. (ED), Software Engineer’s Reference Book. Butterworth. Heinemann.1993.
Mel, A. C., “A Comparative Examination of System Analysis Analysis Techniques,” MIS Quarterly, March 1984. pp. 51-67.
Meredith, D. C., “Don’t gamble when choosing a system development methodology,” DATA MANAGEMENT, July 1986. 36-39.
Miklic, E. R. & Zupancic, J., “Experience and expectation with CASE technology – an example from Slovenia,” Information & Management, Vol. 28, 1995. 377-391.
Morris, M. G., Speier, C. & Hoffer, J. A., “An Examination of Procedural and Object-oriented System Analysis Methods: Does Prior Experience Help or Hinder Performance,” Decision Sciences, Vol. 30, No. 1, Winter, 1999. 107-136.
Nonaka, I. & Takeuchi, H., ”The Knowledge Creating Company:How Japanese Companies Create the Dynamics of Innovation.” Oxford University Press, 1995.
Norman, R. J., “Object-Oriented Systems Analysis: A Methodology For The 1990s,” Journal of Systems Management, July, 1991. 32-40.
Palvia, P. & Nosek, J. T., “A Field Examination of System Life Cycle Techniques and Methodologies,” Information & Management,Vol. 25, 1993. 73-84.
Pancake, C.M., “The Promise and the Cost of Object Technology:a five year forcast,” Communications of ACM, Vol. 38 (10), 1995. 33-49.
Paul, H., “CASE, Object-Oriented Programming & Expert System,” American Programmer, October 1991. 57-71.
PC Week Vol. 16, Jan. 1995. 68.
Plyler, R. W. & Kim, Y. G., ”METHODOLOGY MYTHS Four Tenets for Systems Developers,” Information Systems Management, Spring 1993, 39-44.
Poo, D. & Chung, M. K., “Software engineering practices in Singapore,” The Journal of Systems and Software, Vol. 41. 1998. 3-15.
Rademacher, R. A., “Critical Factors For Systems Success,” Journal of Systems Management, June 1989. 15-17.
Robert, T., “Why Can’t We Implement This SDM?,” IEEE Software, Nov./Dec., 1999. 70-75.
Roberts, T. L. & Hughes, C. T., “Obstacles to Implementing a System Development Methodology,” Journal of Systems Management, vol. 47, No. 2, Mar/Apr, 1996. 36-40.
Roberts, T. L., Gibson, M. L., Fields, K. T. & Rainer, R. K., “Factors that Impact Implementing a System Development Methodology,” IEEE Trans. Software Eng., vol. 24, No. 8, Aug., 1998. 640-649.
Saarinen, T., “System development methodology and project success,” Information & Management, Vol. 19, 1990. 183-193.
Sheetz, S. D., Irwin, G., Tegarden, D. P., Nelson, H. J. & Monarchi, D. E., “Exploring the Difficulties of Learning Object-Oriented Techniques,” Journal of Management Information Systems, Fall Vol.14, No. 2, 1997. 103-131.
Smith, R. S., “Project life cycles aid the systems development process,” DATA MANAGEMENT, March, 1987. 10-41.
Sumnwe, M. & Sitek, J., “Are Structured Methods for Systems Analysis and Design Being Used ?,” Journal of Systems Management, June, 1986. 18-23.
Tesch, D. B., Klein, G. & Sobol, M. G., “Information System Professionals’ Attitudes:Development Tools and Concepts,” J. SYSTEMS SOFTWARE, Vol. 28, 1995. 39-47.
Thong, J. Y. L., ”An integrated model of information systems adoption in small businesses,” Journal of Management Information Systems, Vol. 15(4), 1999. 187-214.
Tse, T. H., Chen, T. Y. & Kwok, C. S., “ The use or prolog in the modeling and evaluation of structure charts,” Information and Software Technology, Vol. 36, No. 1, 1994. 23-33.
Wang, S. H., “Two MIS analysis methods: An experimental comparison,” Journal of Education for Business, Vol. 71, No. 3, Jan. 1996. 136-141.
www.dsc.com.tw.
www.oracle.com.
www.sap.com.
Yang, H. L., “Adoption and implementation of CASE tools in Taiwan,” Information & Management, Vol. 35, 1999. 89-112.
Young, G. quoted in P. Springett, Wiley, New York, 1990.
Zander, U. & Kought, B., ”Knowledge of the Firm, Combinative Capabilities and the Replication of Technology.” Organization Science, Vol. 3(3), 1992. 383-397.

指導教授

周世傑(Shyh-Jye Jou)

審核日期

2003-1-14

推文