摘要(英) |
CMMI (Capability Maturity Model Integrated) developed by Software Engineering Institute of Carnegie Mellon University is for improving the quality of software development. Many studies have demonstrated that CMMI can bring lots of advantages for organizations. But it still has many barriers to overcome for organizational implementation, as evidenced by the large numbers of unsuccessful or painful implementations. With the huge structure and many requirements of CMMI, many organizations will meet the great resistence from their project members when initiating the CMMI project. To resolve this problem, it is important to let the members know what will be changed and how to make such changes effectively. Many software development companies apply CMMI without considering their own capability and realizing the situation which they are in. The requirements of CMMI tend to be in conflict with the old work habits and organizational culture, making aggressive promotiion of CMMI a must. This case study, which is analyzed at the project level of implementing CMMI Level 3, describes and explains how to implement the process improvement of CMMI Level 3 and idetifies the key successful factors for achieving the project goals. |
參考文獻 |
英文文獻
1. Baker, Emanuel R. ( 2001). “Which Way, SQA”, IEEE Software, January/February.
2. CMMI Product Team. (2002a). Capability Maturity Model Integration, Version 1.1, CMMI-SW/SE/IPPD/SS, Staged representation CMU/SEI-2002-TR-011.
3. CMMI Product Team. (2002b). Capability Maturity Model Integration, Version 1.1, CMMI-SW/SE/IPPD/SS, Continuous representation CMU/SEI-2002-TR-012.
4. Dinsmore, Paul C. (1999). “Winning in Business with Enterprise Project Management”, American Management Association.
5. Goldenson, D.R. and Gibson, D.L. (2003). Demonstrating the Impact and Benefits of CMMI: An Update and Preliminary Results, CMU/SEI-2003-SR-009.
6. International Standard Organization. (2003a). ISO/IEC TR 9126-2:2003, Software Engineering - Product Quality - Part 2: External Metrics.
7. International Standard Organization. (2003b). ISO/IEC TR 9126-3:2001, Software Engineering - Product Quality - Part 3: Internal Metrics.
8. Johnson, Donna. L. and Brodman, Judith. G. (2000). “Applying CMM Project Planning Practices to Diverse Environments”, IEEE Software, July, pp. 40-47.
9. Might, R.J. and Fischer, W.A., (1985). “The Role of Structural Factors in Determining Project Management Success”, IEEE Transactions on Engineering Management, May, pp.71-77.
10. Phan, D.D.and Vogel, D.R. and Jeremiah, J.F.N. (1995). “Empirical Studies in Software Development Projects: Fields Survey and OS/400 Study”, Information & Management, Vol. 28, pp.271-280.
11. PMBOK Guide 2000 Edition, PMI.
中文文獻
1. 林信惠與黃明祥,軟體專案管理,智勝文化,2002。
2. 黃世禎與呂欣樺,如何評估軟體產品品質,軟體產業通訊,第 55 期:42-55 頁,2003 年 12 月。
3. 資訊工業策進會,CMMI 導入指引 v1.0 – CMMI導入指引總論,經濟部科技處,2002。
4. 經濟部技術處,我國資訊軟體產業發展現況,資訊工業年鑑,2003。
網站資料
1. Software Engineering Institute網站,2008/5,網址:http://www.sei.cmu.edu/cmmi/adoption/pdf/cmmi-overview07.pdf
2. Software Engineering Institute網站,2008/5,網址:http://www.sei.cmu.edu/ideal
3. CMMI 與軟體工程網站,2008/5,網址:http://dbmaker.syscom.com.tw/mag/110/se-cmmi_02.htm
4. 中華專案管理學會網站,2008/5,網址: http://www.npma.org.tw/
5. 台灣商會聯合資訊網網站,2008/5,網址:http://www.tcoc.org.tw/newslist/034200/34261.aspx
6. 經濟部工業局提升資訊軟體品質計畫網站,2008/5,網址:http://www.cmmi-taiwan.org.tw/cgi-bin/big5/cmmi/po00?q1=picdata&q22=5&q3=ea055
7. 寶發科技網站,2008/5,網址: http://www.cmmi.com.tw/ |