簡易檢索 / 詳目顯示

研究生: 陳健發
Chien-fa Chen
論文名稱: 軟體缺失度量指標制訂與缺失管理系統之建置
Definition of Software Defect Indicators and the Development of Defect Management System
指導教授: 黃世禎
Sun-jen Huang
口試委員: 魏小蘭
Hsiao-lan Wei
羅治民
Chih-min Lo
學位類別: 碩士
Master
系所名稱: 管理學院 - 資訊管理系
Department of Information Management
論文出版年: 2014
畢業學年度: 102
語文別: 中文
論文頁數: 115
中文關鍵詞: 軟體品質軟體缺失度量軟體缺失指標軟體缺失管理系統
外文關鍵詞: Software Quality, Software Defect Metrics, Software Defect Indicator, Software Defect Management System
相關次數: 點閱:233下載:5
分享至:
查詢本校圖書館目錄 查詢臺灣博碩士論文知識加值系統 勘誤回報

軟體是一種無形的知識性產品,需求很難正規的描述,且由於軟體開發專案是一種需要多人參與的勞務性工作,因此軟體缺失的產生是不可避免的。軟體開發流程的任何階段都會產生軟體缺失,當缺失未即時被修復,其將可能移植(migration)至下游階段或擴散(expansion)產生更多的缺失,因此當一個缺失存在於軟體開發流程越久,其缺失修復成本將會越高,故管理缺失成為組織一項重要的任務。雖然目前已經有部分的組織導入議題管理系統(issue tracking system),以記錄與處理軟體專案開發過程中的問題,然而對於運用軟體缺失度量指標(software defect metrics)進行軟體缺失資料分析,以獲取專案回饋資訊的概念仍尚未遍布於軟體產業中,且組織間對於軟體缺失度量指標尚未有標準化的操作型定義,以至於組織與組織間的專案無法藉由軟體缺失度量指標進行比較。
基於上述原因,本研究參考軟體缺失度量指標相關文獻,以彙整學術與實務上的軟體缺失度量指標,並由軟體開發流程品質、專案成員績效、軟體產品品質三個專案構面,制訂30個軟體缺失度量指標,並整合其中相關的軟體缺失度量指標,提供專案管理回饋資訊。最後,本研究亦實際建置一個軟體缺失管理系統,整合軟體缺失資料收集與軟體缺失度量指標分析的流程,輔助使用者收集與管理軟體開發專案的缺失資料,並以報表呈現軟體缺失度量指標的計算結果,提供使用者分析專案回饋資訊。


Software is an invisible knowledge-based product and hence was hard to be described specifically. Moreover, software project development often needs many people to participate in, so it is inevitable to generate software defect. Most phases of software processes will generate software defect. If any one of defects does not fix in time, it may migrate and expand them to next phase. Besides, as long as defects exist in software development processes longer, the cost of fix will increase much more. Therefore, defect management becomes a vital task for organizations. Although some of the organizations had implemented the issue tracking system to record and manage problems occurred during the software development life cycle, the use of software defect indictors to analyze software defect so as to acquire feedback on projects was not be used widely in the software industry. Also, the software defect indicators had not been defined between organizations so that the organizations’ projects could not be compared by software defect indicators.
This thesis referred to the literature, which was related to software defect metrics, to define 30 software defect indicators. They were classified into three categories: the quality of software development process, the efficiency of staff, and the quality of software product. In addition, this thesis integrated software defect related indicators to provide the information which could help the defect management of the software development project. Finally, to integrate the collection of software defect data and the analysis of software defect indicators, we developed a software defect management system to demonstare the feasibility of the proposed indicators.

摘 要 I Abstract II 誌 謝 III 目 錄 IV 表目錄 VI 圖目錄 VIII 第1章 緒論 1 1.1 研究背景 1 1.2 研究動機 2 1.3 研究目的 3 1.4 研究流程與步驟 4 1.5 本文架構 5 第2章 文獻探討 6 2.1 軟體缺失相關文獻彙整 6 2.1.1 軟體異常相關詞彙定義 6 2.1.2 軟體缺失度量指標的發展 8 2.1.3 軟體缺失度量指標 8 2.2 軟體缺失相關工具探討 13 第3章 制訂軟體缺失度量指標 15 3.1 軟體缺失度量指標架構 15 3.2 軟體缺失度量指標操作行定義 17 3.3 軟體缺失基本度量資料 82 3.4 整合運用缺失度量指標 83 第4章 系統建置 86 4.1 系統需求定義 86 4.2 系統分析與設計 87 4.3 系統開發工具與運作平台 91 4.4 系統架構 91 4.5 資料庫設計 94 第5章 系統展示與評估 100 5.1 系統展示 100 5.1.1 系統前端功能畫面介紹 102 5.1.2 系統後台功能畫面介紹 106 5.2 軟體缺失管理相關工具比較分析 108 第6章 結論與建議 112 6.1 研究貢獻 112 6.2 研究限制 113 6.3 後續研究建議 113 參考文獻 114

1. Kan, S.H., Metrics and models in software quality engineering. 2002: Addison-Wesley Longman Publishing Co., Inc.
2. 行政院公共工程委員會. Available from: http://www.pcc.gov.tw/pccap2/TMPLfronted/ChtIndex.do?site=002.
3. Suma, V. and T. Nair, Effective defect prevention approach in software process for achieving better quality levels. arXiv preprint arXiv:1001.3552, 2010.
4. Tiejun, P., Z. Leina, and F. Chengbin. Defect tracing system based on orthogonal defect classification. in Computer Science and Software Engineering, 2008 International Conference on. 2008. IEEE.
5. Kumaresh, S. and R. Baskaran, Defect Analysis and Prevention for Software Process Quality Improvement. International Journal of Computer Applications, 2010. 8(7).
6. Mujtaba, G., T. Mahmood, and P.Z. Nasir, A Holistic Approach to Software Defect Analysis and Management. Australian Journal of Basic & Applied Sciences, 2011. 5(6): p. 1632.
7. Simcoe, C.W., An ounce of prevention. American Intra-Ocular Implant Society Journal, 1978. 4(1): p. 39-44.
8. Suma, V. and T. Nair, Defect management strategies in software development. arXiv preprint arXiv:1209.5573, 2012.
9. Ordonez, M.J. and H.M. Haddad. The State of Metrics in Software Industry. in Information Technology: New Generations, 2008. ITNG 2008. Fifth International Conference on. 2008.
10. NASA. Available from: http://www.nasa.gov/.
11. ISBSG. Available from: http://www.isbsg.org/.
12. Zhi-bo, L., et al., Analysis of software process effectiveness based on orthogonal defect classification. Procedia Environmental Sciences, 2011. 10: p. 765-770.
13. 張育銓, 一個支援個人軟體程序之缺陷收集與分析的工具, in 資訊工程系研究所. 2007, 國立台北科技大學: 台北市. p. 103.
14. IEEE Standard Classification for Software Anomalies, in IEEE Std 1044-2009 (Revision of IEEE Std 1044-1993). 2010. p. 1-23.
15. Laitenberger, O. and J.-M. DeBaud, An encompassing life cycle centric survey of software inspection. Journal of Systems and Software, 2000. 50(1): p. 5-31.
16. Guide, A., PROJECT MANAGEMENT BODY OF KNOWLEDGE (PMBOKR GUIDE). Project Management Institute. 2001.
17. 吳宗穆, 軟體流程改善量化績效指標制訂之研究, in 資訊管理系. 2007, 國立臺灣科技大學: 台北市. p. 177.
18. Ghapanchi, A.H. and A. Aurum. Measuring the Effectiveness of the Defect-Fixing Process in Open Source Software Projects. in System Sciences (HICSS), 2011 44th Hawaii International Conference on. 2011.
19. 彭振晃, ezTrack:一個與ezScrum整合之議題追蹤系統, in 資訊工程系研究所. 2010, 國立台北科技大學: 台北市. p. 72.
20. Bugzilla. Available from: http://www.bugzilla.org/.
21. Mantis. Available from: http://www.mantisbt.org/.
22. JTrac. Available from: http://www.jtrac.info/.

QR CODE