研究並建立一個敏捷式軟體維護流程模式 －以銀行資訊系統維護為例

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：120

、訪客IP：3.146.221.249

姓名

池珍銘(Chen-Ming Chih) 查詢紙本館藏

畢業系所

資訊管理學系在職專班

論文名稱

研究並建立一個敏捷式軟體維護流程模式－以銀行資訊系統維護為例
(Establishing an Agile-based Software Maintenance Process Model for Banking Information System Maintenance)

相關論文

★ 專案管理的溝通關鍵路徑探討─以某企業軟體專案為例	★ 運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例
★ 專案化資訊服務中人力連續派遣決策模式之研究─以高鐵行控資訊設備維護為例	★ 以組織正義觀點介入案件指派決策之研究
★ 應用協調理論建立系統軟體測試中問題改善之協作流程	★ 應用案例式推理於問題管理系統之研究 -以筆記型電腦產品為例
★ 運用限制理論於多專案開發模式的人力資源配置之探討	★ 應用會議流方法於軟體專案開發之個案研究：以翰昇科技公司為例
★ 多重專案、多期再規劃的軟體開發接案決策模式：以南亞科技資訊部門為例	★ 會議導向敏捷軟體開發及系統設計：以大學畢業專題為例
★ 一種基於物件、屬性導向之變更影響分析方法於差異化產品設計	★ 會議流方法對大學畢業專題的團隊合作品質影響之實驗研究
★ 實施敏捷式發展法於大學部畢業專題之行動研究 – 以中央大學資管系為例	★ 建立一個用來評核自然語言需求品質的線上資訊系統
★ 結合本體論與模糊分析網路程序法於軟體測試之風險與風險關聯辨識	★ 在軟體反向工程中針對UML結構模型圖之線上品質評核系統

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

[檢視]

[下載]

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

摘要(中)

軟體維護對於銀行金融資訊領域來說尤為重要，因銀行資訊系統使用的客戶眾多且須符合金管單位的法令規範及消費者權益，在決策過程中往往會以系統穩定性、符合金融法規、資訊安全為主要考量。然而近年來金融科技FinTech為金融領域帶來重大衝擊，從技術、觀念、流程乃至人才招募，各層面都有著顯著的影響。有鑑於快速回應市場（Time to market）的行銷方式儼然成為銀行行銷單位的必須手段，而銀行系統的維護也要跟上這個趨勢。如何在追求穩定又能快速回應變化成為銀行系統維護業務現今的重要課題。本研究嘗試以個案研究方式，透過研究個案維護團隊實際運作敏捷方法的經驗，同時結合ISO/IEC/IEEE 14764維護流程並應用CMMI Institutionalization Design制度化措施建立一套「敏捷式軟體維護流程模式」。本研究的成果或可做為金融資訊單位，在推廣Agile Scrum敏捷方法過程中，當遇到跨業務組織、規劃單位與技術團隊運作時的參考實踐，協助其順利導入敏捷開發與維護流程。

摘要(英)

Software maintenance is critical to the stability and sustainability of banking information systems. However, in today’s changing and fast-evolving business environments, time-to-market has become a marketing necessity for banks and thus the maintenance of banking systems needs to keep up with the trend. It is also essential for the banking system maintenance to ensure stability as well as to achieve quick responsiveness to changes. Therefore, this study seeks to examine how the maintenance team in the studied case operates with agility, stability and sustainability, and establishes an agile-based software maintenance process model by combining the ISO/IEC/IEEE 14764 maintenance standard and the CMMI institutionalization design. The research findings can serve as a reference to banking information departments where the Agile method is promoted.

關鍵字(中)

★ 軟體維護
★ 敏捷方法
★ 個案研究
★ Scrum
★ CMMI制度化設計

關鍵字(英)

★ Software Maintenance
★ Agile
★ Scrum
★ Case Study
★ CMMI Institutionalization Design

論文目次

目錄
摘要 i
目錄 v
一、緒論 1
1-1背景 1
1-2動機 1
1-3目的 2
二、文獻探討 4
2-1軟體維護 4
2-2 ISO/IEC/IEEE 14764軟體維護流程 5
2-3 Agile敏捷軟體工程 7
2-4 Agile Scrum敏捷式軟體維護 11
2-5 CMMI Institutionalization Design制度化設計 14
三、研究方法 16
3-1個案研究方法 16
3-2資料蒐集與成效評估 19
四、個案分析 21
4-1個案介紹 21
4-2個案問題描述與現況 21
4-3敏捷式軟體維護流程模式 25
4-4永續化敏捷式軟體維護流程模式 33
五、研究討論 36
5-1關鍵績效指標 36
5-1-1指標定義 36
5-1-2數據分析 37
5-2訪談與分析 39
5-3 研究限制 44
六、結論與與未來發展方向 46
七、參考文獻 47

表格目錄
表 1：能力度與成熟度等級對應表 14
表 2：CMMI能力度目標與與措施彙整表 15
表 3：五種社會科學研究方法相關之類型與適用條件 16
表 4：四種檢驗個案研究設計的方法策略 18
表 5：個案研究設計類型 19
表 6：維護類型彙整表一 23
表 7：維護類型彙整表二 24
表 8：敏捷式軟體維護流程與制度化措施(GP) 34
表 9：Sprint Velocity（導入前） 37
表 10：Sprint Velocity（導入後） 38
表 11：Sprint P_Rate導入前 38
表 12：Sprint P_Rate導入後 38
表 13：訪談人員表 39
表 14：制度化流程之實施成效 44

圖片目錄
圖 1：變更請求的類型 5
圖 2：敏捷四大價值觀 8
圖 3：敏捷十二大原則 8
圖 4：Scrum Framework流程圖 10
圖 5：個案組織所在之組織架構 22
圖 6：需求處理流程現況 23
圖 7：敏捷式軟體維護流程模式 25
圖 8：個案組織應用敏捷式軟體維護流程模式實務 32

參考文獻

1. 天下雜誌 (2021),成功抵禦疫情衝擊,國泰世華勇奪權威媒體「台灣最佳銀行」的三大關鍵,檢自 https://www.cw.com.tw/article/5118217 (Sep. 30th, 2021)
2. 邱莉婷 (2011),我國金融服務業發展之回顧與展望, 經濟研究第11期(100年4月)
3. 金管會 (2022), 金融監督管理委員會法規資訊,檢自https://www.fsc.gov.tw/ch/main.jsp?websitelink=fatfooter_list.jsp&contentid=3&mtitle=法規資訊 (May 29th, 2022)
4. 金管會 (2022), 金融監督管理委員會金融業務統計輯要(111年3月) ,檢自 https://www.banking.gov.tw/ch/home.jsp?id=157&parentpath=0,4&mcustomize=bstatistics_view.jsp&serno=201105120014 (May 23th, 2022)
5. 財金資訊季刊 (2020/05),” 開放銀行趨勢下的 IT 再轉型 - 國泰世華 New Heights 2020 計畫”, 第97期
6. 財資雜誌The Asset (2021), 國泰世華打造數位新金融國際肯定,檢自國泰世華打造數位新金融國際肯定 - C4 富裕人生 - 20210707 - 工商時報 (ctee.com.tw) (Jul. 7th, 2021)
7. 國家教育研究院 (2000),行政院研考會,檢自 http://terms.naer.edu.tw/detail/1309184/ (Mar. 5th, 2022)
8. 陳仲儼, 馬成珉, & 馮立琪. (2010). 應用 ITIL 及 CMMI 來建立並維持資訊服務流程改善. 資訊管理學報, 17(3), 71-105.
9. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
10. Agile Alliance (2001), Manifesto for Agile Software Development, Retrieved from https://agilemanifesto.org/iso/zhcht/manifesto.html (Jun. 1st, 2021)
11. April, A., Abran, A., & Dumke, R. R. (2003). Software maintenance capability maturity model (SM-CMM): process performance measurement. In 13 th International Workshop on Software Measurement–IWSM (pp. 23-25), Montréal, Quebec, Canada.
12. April, A., Huffman Hayes, J., Abran, A., & Dumke, R. (2005). Software Maintenance Maturity Model (SMmm): the software maintenance process model. Journal of Software Maintenance and Evolution: Research and Practice, 17(3), 197-223.
13. Basili, V., Briand, L., Condon, S., Kim, Y. M., Melo, W. L., & Valen, J. D. (1996, March). Understanding and predicting the process of software maintenance releases. In Proceedings of IEEE 18th International Conference on Software Engineering Berlin Germany (pp. 464-474). IEEE.
14. Beck, K., & Andres, C. (2004). Extreme Programming Explained: Embrace Change. Second Edition. XP Ser.
15. Benbasat, I., Goldstein, D. K., & Mead, M. (1987). The case research strategy in studies of information systems. MIS quarterly, 369-386.
16. Bennett, K. H., & Rajlich, V. T. (2000, May). Software maintenance and evolution: a roadmap. In Proceedings of the Conference on the Future of Software Engineering Limerick Ireland (pp. 73-87).
17. Boehm, B. W. (1976). Software engineering. IEEE Trans. Computers, 25(12), 1226-1241.
18. Boehm, B. W. (1983). Seven basic principles of software engineering. Journal of Systems and Software, 3(1), 3-24.
19. Canfora, G., & Cimitile, A. (2001). Software maintenance. In Handbook of Software Engineering and Knowledge Engineering: Volume I: Fundamentals (pp. 91-120).
20. Charette, R. N., Adams, K. M., & White, M. B. (1997). Managing risk in software maintenance. IEEE Software, 14(3), 43-50.
21. Choudhari, J., & Suman, U. (2010, October). Iterative maintenance life cycle using extreme programming. In 2010 International Conference on Advances in Recent Technologies in Communication and Computing NW Washington, DC United States (pp. 401-403). IEEE.
22. CMMI Product Team. (2010). CMMI for Development, Version 1.3 (CMU/SEI-2010-TR-033). Retrieved from the Software Engineering Institute, Carnegie Mellon University website: http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=9661 (May 7th, 2022)
23. Dave West (2016)，Updates to the Scrum Guide: The 5 Scrum values take center stage, Retrieved from https://www.scrum.org/resources/blog/5-scrum-values-take-center-stage (Feb. 8th, 2022)
24. de Souza, S. C. B., Anquetil, N., & de Oliveira, K. M. (2005, September). A study of the documentation essential to software maintenance. In Proceedings of the 23rd annual international conference on Design of communication: documenting & designing for pervasive information NY, United States (pp. 68-75).
25. de Souza, S. C. B., Anquetil, N., & de Oliveira, K. M. (2006). Which documentation for software maintenance?. Journal of the Brazilian Computer Society, 12(3), 31-44.
26. Dekleva, S. M. (1992). The influence of the information systems development approach on maintenance. MIS quarterly, 355-372.
27. Devulapally, G. K. (2015). Agile in the context of software maintenance: a case study.
28. Gupta, A., & Sharma, S. (2015). Software maintenance: Challenges and issues. Issues, 1(1), 23-25.
29. Hedrick, T. E., Bickman, L., & Rog, D. J. (1993). Applied research design: A practical guide. Sage Publications.
30. Heeager, L. T., & Rose, J. (2015). Optimising agile development practices for the maintenance operation: nine heuristics. Empirical Software Engineering, 20(6), 1762-1784.
31. Ibrahim, K. S. K., Yahaya, J., Mansor, Z., & Deraman, A. (2019, July). The Emergence of agile Maintenance: A preliminary study. In 2019 International Conference on Electrical Engineering and Informatics (ICEEI) Bandung, Indonesia (pp. 146-151). IEEE.
32. ISO/IEC (2006). ISO/IEC 14764 IEEE Std 14764‐2006 International Standard—Software Engineering — Software Life Cycle Processes — Maintenance.
33. ISO/IEC/IEEE. (2022). ISO/IEC/IEEE 14764:2022(E). International Standard - Software engineering — Software life cycle processes — Maintenance (pp. 1–46). IEEE. Retrieved from https://doi.org/10.1109/IEEESTD.2022.9690131(Mar. 20th, 2022)
34. iThome(2020/11/12), 靠技術轉型輔助數位轉型，國泰將技術力變成發展飛輪加速力，檢自 https://www.ithome.com.tw/news/140992 (Jun. 26th, 2021)
35. iThome(2020/12/10), ”國泰世華靠技術驅動全行轉型，打造微服務中臺讓核心瘦身”，檢自 https://www.ithome.com.tw/people/141487 (Jun. 26th, 2021)
36. Jain, P., Sharma, A., & Ahuja, L. (2018). Software Maintainability Estimation in Agile Software Development. International Journal of Open Source Software and Processes (IJOSSP), 9(4), 65-78.
37. Janicic, M. V. Maintenance and maintainability within agile software development . Science of Maintenance. Journal homepage www.m-sci.rs, 1(2021), 1.
38. Kitchenham, B. A., Travassos, G. H., Von Mayrhauser, A., Niessink, F., Schneidewind, N. F., Singer, J., ... & Yang, H. (1999). Towards an ontology of software maintenance. Journal of Software Maintenance: Research and Practice, 11(6), 365-389.
39. Malhotra, R., & Chug, A. (2016, March). Comparative analysis of agile methods and iterative enhancement model in assessment of software maintenance. In 2016 3rd International Conference on Computing for Sustainable Global Development (INDIACom) New Delhi, India (pp. 1271-1276). IEEE.
40. McFeeley, B., & IDEAL, A. (1996). A User′s Guide for Software Process Improvement. Software Engineering Institute (SEI).
41. Merriam, S. B. (1988). Case study research in education: A qualitative approach. Jossey-Bass.
42. Miller, G. G. (2001, July). The characteristics of agile software processes. In Technology of Object-Oriented Languages, International Conference on Zurich, Switzerland. (Vol. 1, pp. 0385-0385). IEEE Computer Society.
43. Mohapatra, S. (2009). Software project management. New Delhi, India: Cengage Learning Pvt. Ltd..
44. Mohapatra, S. (2013). Best Practices in Software Maintenance Projects. International Journal of IT/Business Alignment and Governance (IJITBAG), 4(1), 11-26.
45. Niessink, F., & Van Vliet, H. (2000). Software maintenance from a service perspective. Journal of Software Maintenance: Research and Practice, 12(2), 103-120.
46. Omanovic, S., & Buza, E. (2013, October). Importance of stable velocity in agile maintenance. In 2013 XXIV International Conference on Information, Communication and Automation Technologies (ICAT) Sarajevo, Bosnia and Herzegovina (pp. 1-8). IEEE.
47. Pigoski, T. M. (1996). Practical software maintenance: best practices for managing your software investment. Wiley Publishing.
48. Pino, F. J., Ruiz, F., Garcia, F., & Piattini, M. (2012). A software maintenance methodology for small organizations: Agile_MANTEMA. Journal of Software: Evolution and Process, 24(8), 851-876.
49. PMI, (2017). Agile practice guide. Project Management Institute.
50. Poole, C., & Huisman, J. W. (2001). Using extreme programming in a maintenance environment. IEEE Software, 18(6), 42-50.
51. Prochazka, J. (2011). Agile support and Maintenance of IT services. In Information Systems Development (pp. 597-609). Springer, New York, NY.
52. Schneidewind, N. F. (1987). The state of software maintenance. IEEE Transactions on Software Engineering, (3), 303-310.
53. Schwaber, K., & Beedle, M. (2001). Agile software development with Scrum Prentice Hall PTR Upper Saddle River. NJ, USA.
54. Schwaber, K., & Sutherland, J. (2020). “Scrum Guide”. Retrieved from https://scrumguides.org/download.html (Feb. 8th, 2022)
55. Scrum.org (2020), “WHAT IS SCRUM?”, Retrieved from https://www.scrum.org/resources/what-is-scrum (Feb. 8th, 2022)
56. SES Committee. (1998). Ieee standard for software maintenance. IEEE Std, 1219-1998.
57. Shaw, S. (2007). Using agile practices in a maintenance environment. Intelliware Development Inc.
58. Sliger, M., & Broderick, S. (2008). The software project manager′s bridge to agility. Addison-wesley professional.
59. Svensson, H., & Host, M. (2005, March). Introducing an agile process in a software maintenance and evolution organization. In Ninth European Conference on Software Maintenance and Reengineering , Manchester, UK (pp. 256-264). IEEE.
60. Syed, K., Barqawi, N., & Mathiassen, L. (2019). Release cycle management: An action research study into a software company. International Journal of Business Information Systems, 30(2), 152-176.
61. Tellis, W. (1997). Introduction to case study. The qualitative report, 269.
62. Tett, G. (2015). The silo effect: The peril of expertise and the promise of breaking down barriers. Simon and Schuster.
63. The Banker (2021). Top 1000 World Banks 2021. Retrieved from https://www.thebanker.com/Top-1000/2021/Top-1000-World-Banks-2021 (May 24th, 2022)
64. Thomas, D. (2006). Agile evolution: Towards the continuous improvement of legacy software. J. Object Technol., 5(7), 19-26.
65. Yin, R. K. (2018). Case study research: Design and methods (6th ed.). Thousand Oaks, CA: Sage.
66. Ziauddin, S. K. T., & Zia, S. (2012). An effort estimation model for agile software development. Advances in computer science and its applications (ACSA), 2(1), 314-324.

指導教授

陳仲儼(Chung-Yang Chen)

審核日期

2022-6-27

推文