資訊科技快速的發展，使得電腦軟體系統的應用範圍無所不及，對軟體系統的需求是愈來愈高，而系統的複雜度也是直線攀升。軟體產品品質已成為軟體需求者或企業所重視的問題，而如何確保系統或是軟體產品的品質，便成為一個非常重要的議題。現今的台灣軟體產業中，對於軟體產品品質的管控與評估仍存在許多問題，追究其原因，除了缺乏一套合適的軟體產品品質管理流程外，也缺乏一套評估軟體產品品質等級的機制，以至於軟體開發團隊無法掌控每個階段工作產出的軟體產品品質，也無法客觀地評估軟體產品品質的等級，使得開發出來的軟體產品品質往往不能滿足使用者的品質需求，而軟體籌獲方也是很難定義、監控與評估軟體工作產出與最終產品的品質，以致造成雙方的爭執與衝突。
因此本研究的主要目的是以全軟體開發生命週期為基礎，制訂一套軟體產品品質管理流程。此軟體產品品質管理流程能適用於各種軟體產品類型，並可依各公司產品屬性的不同，調適成適合各公司軟體產品的流程及品質評估問項，根據使用者與軟體開發者透過事先對軟體產品品質需求的重要性及期望的品質等級的規劃，再蒐集相關的執行程度進行符合標準的判斷，進而分析出軟體產品品質等級，分析後的結果可提供作為軟體產品品質改善的依據或滿足使用者品質需求的證據。本研究所提出的全軟體產品品質管理流程主要特色是提供一個標準且實用的評估步驟，來指引整個軟體開發生命週期軟體工作產出與最終軟體產品品質評估作業的執行，以幫助軟體委外籌獲方與軟體開發廠商共同規劃、管控、評估與改善軟體產品品質，並提供甲乙雙方達成共識的機制，能夠針對軟體工作產出與最終產品品質需求順利進行協商，避免在軟體開發過程中雙方所產生的爭執與衝突。最後本研究將所提出的以全軟體生命週期工作產出為基礎之軟體產品品質管理流程實際導入於一個個案公司，以驗證本流程模式的可行性。

In recent years, Information technology has been growing rapidly and hence software systems are widely utilized in all types of organizations. Meanwhile, the complexity of software systems is becoming higher and the requirements of software systems are also getting much higher than before. Accordingly, the software product quality is very important to its users and organizations and therefore it is an essential issue about how to assure the quality of software systems. Nowadays, many problems still exist due to the lack of adequate plan, monitor and control, and assessment of the software product quality in domestic software industry. Without an objective evaluation of software work products and final product in whole software development life cycle, the software product quality will not satisfy its users, nor are software users unable to define and further evaluate the quality of software systems they acquired. Therefore, the conflict between the software acquirers and developers often arises.
This study aims at building an whole software life cycle-based software product quality management process. It can be applied to all types of software products after. The proposed software product quality management process and the assessment items can also be adjusted to fit different software products according to their attributes. The software users and developers can work together to decide the importance and the expected level of the required software quality, collect the relevant data and then analyze the actual quality level of the software work and final products. The analyzed result of the software product quality can be treated as the basis of improving the software product quality and of whether the acquired software product fulfills the users’ quality requirements. The features of the proposed software product quality management process lies on providing a standardized and practical evaluation of quality of the software work and final products in whole software life cycle, and guiding the plan, monitor and control, evaluation, and improvement of software product quality for both software acquirers and developers. Furthermore, both sides can have an agreement for working together to define and evaluate software product quality without conflicts. Finally, this study also conducted a case study to verify the proposed software product quality management process.

[1] 朱三元, 軟體品質及其評價技術. 1994: 儒林圖書.
[2] 江仁宏, 應用模糊理論於軟體品質評估之研究. 國防管理學院 碩士論文, 2000.
[3] 周佩儀、王永心, 軟體產品品質模式衡量之研究. 大同大學 資訊經營研究所 碩士論文, 2004.
[4] 林信惠、黃明祥、王文良, 軟體專案管理. 2002: 智勝文化.
[5] 陳耀茂, 談軟體品質與品質特性的模式化. 中華民國品質協會 品質管制月刊, 1997.
[6] 湯政仁、謝欽賢, 自動化軟體組態管理系統. 大同大學 通訊工程研究所 碩士論文, 2008.
[7] 黃世禎、邱炳堯, 軟體產品品質等級評估流程模式的制定. 國立台灣科技大學 資訊管理系 碩士論文, 2006.
[8] 資策會MIC經濟部ITIS計畫, 2009資訊服務產業年鑑. 2009年5月.
[9] ISO/IEC 14598-5: Software engineering – Product evaluation – Part 5: Process for evaluators. International Standard Organization, 1998.
[10] ISO/IEC 14598-4: Software engineering – Product evaluation – Part 4: Process for acquirers. International Standard Organization, 1999.
[11] ISO/IEC 14598-2: Software engineering – Product evaluation – Part 2: Planning and management. International Standard Organization, 2000.
[12] ISO/IEC 14598-3: Software engineering – Product evaluation – Part 3: Process for developers. International Standard Organization, 2000.
[13] ISO/IEC 14598-1: Information technology – Software product evaluation – Part 1: General overview. International Standard Organization, 2001.
[14] ISO/IEC 14598-6: Software engineering – Product evaluation – Part 6: Documentation of evaluation modules. International Standard Organization, 2001.
[15] ISO/IEC 15504: Information technology – Process assessment – Part 2:Performing an assessment. International Standard Organization, 2003.
[16] ISO/IEC 15504: Information technology – Process assessment – Part 1: Concepts and vocabulary. International Standard Organization., 2004.
[17] Azuma, M., Software products evaluation system: quality models, metrics and processes--International Standards and Japanese practice. Information and Software Technology, 1996. 38(3): p. 145-154.
[18] Boehm, B., A spiral model of software development and enhancement. ACM SIGSOFT Software Engineering Notes, 1986. 11(4): p. 14-24.
[19] Boehm, B., T. Gray, and T. Seewaldt. Prototyping vs. specifying: A multi-project experiment. 1984: IEEE Press.
[20] Datamonitor, Global Application Software-Industry Profile. April 2008.
[21] Donald, R.J., State of the Art in Software Quality Management Torrance：Reifer Consultants. 1985.
[22] John, B., A prototype approach to information system design and development. Information & Management, 1977. 1(1): p. 21-26.
[23] Jung, H., S. Kim, and C. Chung, Measuring software product quality: A survey of ISO/IEC 9126. IEEE software, 2004: p. 88-92.
[24] Kececi, N. and A. Abran, Analyzing, Measuring & Assessing Software Quality Within A Logic-Based Graphical Framework. Proceeding of the 4th International Conference on Probabilistic Safety Assessment and Management, France, 2001.
[25] Lee, K. and S. Lee. A software product evaluation process for supporting the component based development. 2005.
[26] Lee, K. and S. Lee. A quantitative software quality evaluation model for the artifacts of component based development. 2005.
[27] Mills, H., Top-down programming in large systems. Debugging Techniques in Large Systems, 1971: p. 41¡V55.
[28] Ramamoorthy, C. Evolution and evaluation of software quality models. 2002.
[29] Royce, W. Managing the development of large software systems. 1970.
[30] Suratida, R. and M. Settapong. Information technology implementation by applying NIE-SDLC model: the case study on an organization in thailand. 2005.
[31] Whitten, J., L. Bentley, and K. Dittman, Systems Analysis andDesign Methods. 1998, Irwin/McGraw-Hill, Boston, MA.
[32] Yeo, A. Global-software development lifecycle: an exploratory study. 2001: ACM.
[33] Zhu, H., et al., Application of hazard analysis to software quality modelling. COMPSAC-NEW YORK-, 2002: p. 139-146.