金融業競爭日益激烈，無論在新金融商品的推出，或是提昇服務品質皆須仰賴資訊及相關技術方能達成，資訊科技已經變成企業營運的支柱，所以資訊系統開發及維護需要做適當管理，以提昇企業競爭力。
銀行資訊系統非常龐大且複雜，每當有業務需求需進行資訊系統異動時，程式員需自行準備編譯程式清單、過版程式清單等換版文件，之後才執行程式換版流程。換版時經常會遺漏某些相關的程式未編譯，導致換版失敗得重提換版；為避免上述問題發生，可以建立程式版本變更管理系統，日後程式員進行程式換版時，僅需提出欲換版的程式，之後由系統自動產生需編譯的程式及過版清單，執行換版作業。
在資訊系統開發及維護的流程中，減少錯誤即減少風險，而品質亦能獲得管理，導入CMMI可以改善流程。本研究希望自行開發的應用系統部分，可以CMMI Level 2為願景，導入CMMI模式中建構管理的目標與執行方法，使軟體設計人員能以更有效率的方法完成專案的開發，且符合CMMI的作業規範。
藉由文獻探討，本研究以CMMI建構管理(CM)流程領域之特定目標作業規範，與銀行現行程式變更管理流程進行差異分析，最後提出一套符合CMMI建構管理的程式變更管理程序，並希望研究結論能提供銀行業者導入CMMI專案之參考，進而提升整體銀行之競爭力與服務品質。

The financial markets are increasingly competitive. The launch of new financial products and the improvement of service quality are all relay on the information and the related technology. Information technology is now becoming the pillars of business operations. Hence, the management of development and post maintenance of software applications is the critical path for company to its competitiveness.
The information systems used by banking industry are complex and enormous. Whenever there are changes for business requirements, there are changes in banking applications. It is required for the software engineer to prepare the program list which will be impacted by the business requirements and need to be complied, and the related version control documents in order to execute the software version change workflow. Sometime the software release workflow failed to be executed due to some programs not to be included or not to be complied. So the entire software release procedure needs to be done again. In order to prevent this kind of failure of software releasing processes. We can build a software version control management system. By using this management system, software engineer can input the programs that need to be changed. Then the management system will automatically generate the list for all the programs that need to be complied and released and execute the software release procedure.
Throughout the application development and post maintenance lifecycle, the less mistake, the lower the risk, and resulting a better quality management. By introducing CMMI procedure, the same can be improved. The applications that need to be developed in this study are based on CMMI Level 2 standard and introduce the objectives and the methodology of software configuration management in CMMI model. This management application can help software engineers to implement a project in a more effective way and also compliant with CMMI standard.
By investigating related literatures, this study will perform a Gap analysis between specific objective operation model stated in the configuration management of CMMI and the existing program change control procedure in the bank. The objectives and results of this study are to build a program change control management procedure compliant with configuration management in CMMI. And the same can be as a reference for banks that will introduce the CMMI project helping the bank to improve the service quality and competitiveness.

誌 謝i
摘 要ii
ABSTRACTiii
目 錄v
圖目錄vi
表目錄vii
第一章、緒論1
1.1 研究動機與目的1
1.2 研究流程與論文架構2
第二章、文獻探討6
2.1 軟體品質6
2.2 軟體開發流程8
2.3 軟體能力成熟度模式CMM/CMMI10
2.4 小結20
第三章、研究方法21
3.1 個案研究法21
3.2 銀行資訊系統21
第四章、個案研究分析34
4.1 個案銀行現況診斷與CMMI標準比較研究分析與解釋34
4.2 提出建議41
第五章、結論與建議53
5.1 個案分析結果與討論53
5.2 研究限制53
5.3 後續研究建議53
參考文獻54
中文部分54
英文部分54
附錄55

中文部分
[1].王村文(2004)，「支援CMMI之建構管理系統研發」，國立成功大學資訊工程學系碩士論文。
[2].胡估長(2002)，淺談軟體品保與國際品保標準，軟體工業生產力提升特輯，第13~23頁。
[3].吳美芳，軟體程序成熟度、使用者參與度與軟體品質之相關研究，成功大學工業管理研究所碩士論文，民國91年。
[4].黃世禎、陳俊彥，「以量化軟體度量指標支援CMMI模式的導入與評鑑」，軟體產業通訊，54 期，民國92年11月，頁46-57。
[5].經濟部技術處, 能力成熟度整合模式CMMI-SE/SW V1.1, December 2001.
[6].姚俊羽(2003)，能力成熟度整合模式之導入—以文件管理系統為例，銘傳大學碩士論文。
[7].經濟部工業局, 資訊作業開發建置標準規範 V1.00, 2002.
[8].高惠堂，2006，CMMI簡介，資訊工業策進會網路多媒體研究所。
[9].謝欽賢(2008)，自動化軟體組態管理系統論文。
[10].林文質，「如何成為一個具備流程改善基礎的組織」，如何成為一個具備流程改善基礎的組織，台灣軟體流程改善聯盟，民國93年4月30日。

英文部分
[1].Humphrey, W.S., Managing the Software Process, Addison-Wesley, 1989.
[2].Bicego, A. and Kuvaja, P. “Software process maturity and certification,” Journal of System Architecture, Vol.42, p.611-620, 1996.
[3].Chroust, G., "What is a software process? ", Journal of System Architecture, Vol.42, pp.591-600, 1996.
[4].Ivica Crnkovic, Ulf Asklund, and Annita Persson Dahlqvist, Implementing and Integrating Product Data Management and Software Configuration Management,Artech House, 2003.
[5].Laura Wingerd and Christopher Seiwald, High-Level Best Practices in Software Configuration Management, Perforce Software, Inc., 1998.
[6].Yin, R. K. (1994/2001). Case study research: Design and methods(2nd ed). CA: Sage. 尚榮安（譯）。個案研究。台北：弘智。