軟體缺失是決定軟體專案是否能在品質與成本的要求下，如期交付產品的關鍵影響因子，且由於軟體是高度仰賴人及團隊開發的心智性工作，因此缺失是無可避免的。組織只能透過有效的缺失管理、改善軟體流程、增進人員能力、提升軟體開發績效，以降低缺失注入的機會，提高軟體產品品質。
目前，產業應用軟體缺失度量資料來分析專案，獲取回饋資訊的風氣仍不普及；且因蒐集缺失資料的過程較為繁雜，導致企業對導入軟體缺失度量的意願仍舊不高。對於目前已導入軟體缺失度量的組織來說，皆是以自身的目標需求來定義指標，導致指標缺乏完整性及一致性，而且忽略將個別的度量指標進行整合及應用歷史缺失資料，獲取更具價值的管理資訊，以做為組織流程改善、資源配置及後續專案規劃及監控時之參考依據。
基於上述原因，本研究參考軟體度量相關文獻及考量專案開發架構後，將軟體缺失度量指標集分成三個構面、十一個指標類別，一共制定45個軟體專案缺失度量指標；且為提高指標的一致性及完整性，本研究參考SEI GQ(I)M方法論制定操作型定義，並將個別的指標依其相關性進行整合訂定整合性指標，進階分析專案及組織管理資訊供管理者參考，利用線性規劃模型及歷史專案缺失度量值來解析達成目標過程中的問題，並建置軟體缺失應用管理雛形系統，輔助組織蒐集缺失資料，並自動產生指標度量值報表，做為管理者於專案規劃、執行、監控、評估流程及人員績效時參考。

Software defect is a main factor in determining whether a software project can be delivered on time, within the budget and with the highest quality. Software development requires an effective teamwork and its performance improvements can be made through effective defect management, software process improvement, personal skill enhancement and so on.
It is still uncommon among companies to use software defect indicator to analyze historical software project data and further gain feedback information from it. Moreover, the complicated process in collecting defects information has caused low desire among the major industry to introduce the system into the market. For those who have already been using the system, many users are only based on their own needs, so the system appears to lack integrity and consistency. Also, they ignore the application and integration of those software defect metrics, which can be used to gain valuable management and feedback information, and hence improving the planning and management of software development projects.
After referring to the existing software defect metrics in the literature, we have divided the indicator into three different structures, eleven indicator categories and forty-five software defects indicator. In order to improve the precision and consistency of the indicator, we have referenced SEI GQ(I)M for operation definition, and also integrated these metrics into indicators based on their correlations, so valuable information about software defect management can be provided to advance software project management.The thesis also used linear programming model and information of past defects indicator to analyze the problem of their projects, and also developed the prototype of software defect management software system. The system can be used to assist in organizing the collected defect information and producing the indicator values automatically, which can effectively help software project managers well plan, execute, monitor and evaluate the process and performance of each software development project.

1.Suma, V. and T.Nair, Defect Management Strategies in Software Development. 2012: arXiv preprint arXiv:1209.5573.
2.Ansar Khan, H., Establishing a Defect Management Process Model for Software Quality Improvement. International Journal of Future Computer and Communication, 2013: p. 585-589.
3.R.S., P., Software Engineering: A Practitioner's Approach. McGraw-Hill, NY., 2001.
4.Gopalakrishnan Nair, T.R., V. Suma, and P.K. Tiwari, Significance of depth of inspection and inspection performance metrics for consistent defect management in software industry. Software, IET, 2012. 6(6): p. 524-535.
5.CHAOS MANIFESTO. 2012, The Standish Group.
6.Ordonez, M.J. and H.M. Haddad, The State of Metrics in Software Industry, in Fifth International Conference on Information Technology: New Generations. 2008.
7.Grady, R.B., Successfully applying software metrics. Computer, 1994. 27(9): p. 18-25.
8.林信惠, 軟體專案管理. 2005: 智勝文化事業有限公司.
9.CMMI for Development, Version 1.3. 2010, Software Engineering Institute.
10.Kan, S.H., Metrics and Models in software quality engineering. Addison-Wisely Longman Publishing Co., Inc, 2002.
11.Park, R.E., W.B. Goethert, and W.A. Florac, Goal-Driven Software Measureemnt - A Guidebook. 1996.08, Software Engineering Institute.
12.Mujtaba, G., D.T. Mahmood, and P.Z. Nasir, A Holistic Approach to Software Defect Analysis and Management. Australian Journal of Basic and Applied Scienes, 2011.
13.V., S. and T.R.G. Nair, Effective Defect Prevention Approach in Software Process for Achieving Better Quality Levels. World Academy of Science, Engineering and Technology 2008.
14.Chang, C.-P. and C.-P. Chu, Defect prevention in software processes: An action-based approach. Journal of Systems and Software, 2007. 80(4): p. 559-570.
15.Ahmad, K. and N. Varshney, On Minimizing Software Defects during New Product Development Using Enhanced Preventive Approach. International Journal of Soft Computing and Engineering (IJSCE), 2012. 2(5).
16.IEEE Standard Classification for Software Anomalies. 2010, IEEE Std 1044-2009. p. 1-23.
17.Kumaresh, S. and R. Baskaran, Defect Analysis and Prevention for Software Process Quality Improvement. International Journal of Computer Applications (0975 – 8887) 2010. 8.
18.ANANTULA, P.R. and R. CHAMARTHI, Defect Prediction and Analysis Using ODC Approach in a Web Application. (IJCSIT) International Journal of Computer Science and Information Technologies, 2011. 2(5): p. 2242-2245.
19.Erturk, E. and E.A. Sezer, A comparison of some soft computing methods for software fault prediction. . Expert Syst. Appl., 2015. 42(4): p. 1872-1879
20.Tolochko, M.o.S., Practical Software Measurement - A Foundation for Objective Project Management. 1965-1997.
21.Xu, R., et al., Research on CMMI-based Software Process Metrics. Computer and Computational Sciences, 2006. 2: p. 391-397.
22.Jones, C., Software Quality Metrics : Three Harmful Metrics and Two Helpful Metrics. 2012.
23.陳健發, 軟體缺失度量指標制定與缺失管理系統之建置, in 資訊管理系. 2013: 國立臺灣科技大學: 台北市. p. 115.
24.Trivedi, P. and S. Pachori, Modelling and Analysing of Software Defect Prevention Using ODC. (IJACSA) International Journal of Advanced Computer Science and Applications, 2010. 1(3).
25.IBM, Orthogonal Defect Classification v 5.2 for Software Design and Code. 2013.
26.Raninen, A., et al., Defect Data Analysis as Input for Software Process Improvement. 2012: O. Dieste, A. Jedlitschka, and N. Juristo (Eds.): PROFES. 3-16.
27.BugTracker. Available from: http://www.twbsd.org/cht/bug_tracker/.
28.JIRA. Available from: https://www.atlassian.com/software/jira.
29.Mantis. Available from: http://www.mantisbt.org/.
30.吳宗穆, 軟體流程改善量化績效指標制定之研究, in 資訊管理系. 2007: 國立臺灣科技大學: 台北市. p. 177.