臺灣博碩士論文加值系統

知識經濟時代，資訊與電腦科技進步增加企業營運利潤。企業軟體產品、資料有賴於良好的軟體。許多企業購買軟體來降低人事成本、改善作業流程、有效管理企業經營、增加企業競爭力。但軟體缺陷卻有可能造成更急遽的損失，因此有更多的成本投入在軟體的維護。軟體品質的管理能有效降低軟體的支出成本、減少軟體運作風險、維持企業穩定快速的運作。因此軟體的可維護性為企業管理的一個重要評估項目。軟體品質決定了軟體成本的多寡。越來越多的企業組織著重於良好的軟體開發流程，最終目的是為了降低軟體成本。軟體維護成本往往遠大過於軟體開發成本，因此軟體可維護性為決定企業軟體支出的一個重要因素。軟體維護有三種型態分別為軟體錯誤的維護、軟體功能的維護、軟體環境的維護。不同的軟體需求會有不同維護型態的考量。如何測量評估軟體維護性的優劣成為一個重要的研究課題。本研究著重在軟體產品品質各個評估項目的度量，透過相關人員的經驗對產品資訊加以量化，進而制定一個完整有效的可維護性評估模型。採用維護需求的不同觀點，結合國際標準組織(International Standard Organziation,ISO)ISO 9126軟體產品品質模型中的品質子特性、度量指標，建立維護評估的測量架構。我們的測量架構是以層級的方式來描述整個複雜的問題，並以主成份分析有效地處理主觀資料。依照層級間的關係，定義出屬性的測量方法。在研究過程中，我們提出計算各屬性對產品可維護性加權值或貢獻度，與屬性之間的相依程度,進而建立評估及改善流程的標準。最後以資料驗證的方式，分析及驗證這個評估模型的穩定度。藉以檢驗此測量模組的準確度。

In this knowledge-based economy era, the advancement of information and computer science generate enterprise benefit. The effort of managing enterprise software product and data depends on the quality of software. However, software failure may cause more serious damage. For this reason, they spend more costs in software maintenance. The software quality management can reduce software cost, software risk, and sustain enterprise stability effectively and efficiently. Therefore, software maintainability is one of important evaluating subject in the enterprise management arena. There are three types of maintainability proposed in the literature. They are error, functional and environmental maintenance. Different information needs required different type of maintainability in consideration. Therefore, how to measure software maintainability emerged as a popular research topic. In this research, we start at determining the important factors for measuring the software maintainability, followed by collecting the quantitative measure of each characteristics, and developing a complete and effective evaluation model for software maintainability. Based on a particular maintenance type, combined with software product quality measurement model defined in ISO 9126, we propose a measurement construct for evaluating the software maintainability. We described this complex problem by a hierarchical structure, and applied the principal component analysis to process some subjectical data either by simulation or by soliciting from users. By the relationship in this hierarchy, we defined metrics of all attributes. calculated the weighting value or degree of contribution of each attribute, and the dependency between attributes in order to establish a standard for evaluation and process improvement. Finally, we valided our proposed model for stability and applicability using a cross validation technique.

目　錄

摘　要……………………………………………………….…ii
Abstract.…………………………………………………….….iii
目　錄……………………………………………………….…v
圖目錄…………………………………………………………vi
表目錄………………………………………………………...vii
第一章 導論 1
一、 研究背景 1
二、 研究動機 1
三、 研究目的 2
四、 研究流程 3
五、 論文架構 4
第二章 文獻探討 6
一、 軟體可維護性 6
二、 軟體評估方法 7
1. ISO/IEC 15939 7
2. PSM 10
三、 軟體屬性 12
1. ISO 9000 12
2. ISO/IEC 9126 16
3. ISO/IEC 14598 25
四、 分析方法 27
1. AHP 27
2. PCA 28
第三章 研究方法 30
一、 軟體可維護性的評估概念 30
二、 軟體可維護性的屬性模型 31
三、 測量方法 34
四、 主成份分析 35
第四章 模型的驗證 40
一、 實驗設計 40
二、 交叉驗證及結果分析 41
第五章 結論與未來展望 44
文獻參考 45

[1] André Koscianski and João Candido Bracarense Costa, “Combining Analytical Hierarchical Analysis with ISO/IEC 9126 for a Complete Quality Evaluation Framework”, Fourth IEEE International Symposium and Forum on Software Engineering Standards, pp.218, 1999.
[2] Baxter Peter, “Using Measurement: Current Standards and Guidance”, Distributive Software.
[3] David N. Card and Khaled El Eman, “ISO/IEC 15939 – Software Measurement Process Framework”
[4] http://web.thu.edu.tw/wenwei/www/cgi/stat/pca/
[5] http://www.sei.cmu.edu/cmmi/
[6] Ian Sommervill, "Software Engineering (6th Edition)", Addison Wesley, 2001.
[7] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 1: General Overview.
[8] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 2: Planning and management.
[9] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 3: Process for developers.
[10] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 4: Process for buyers.
[11] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 5: Process for evaluators.
[12] ISO/IEC JTC1/SC7/WG6, ISO/IEC 14598: Information Technology - Evaluation of software product; Part 6: Evaluation modules.
[13] ISO/IEC JTC1/SC7/WG6, ISO/IEC 9126-1: Information Technology - Software quality characteristics and metrics – Part 1: Quality characteristics and subcharacteristics.
[14] ISO/IEC JTC1/SC7/WG6, ISO/IEC 9126-2: Information Technology - Software quality characteristics and metrics – Part 2: External measures.
[15] ISO/IEC JTC1/SC7/WG6, ISO/IEC 9126-3: Information Technology - Software quality characteristics and metrics – Part 3: Internal measures.
[16] Khorramshahgol, R. and V.S. Moustakis, ”Delphic Hierarchy Process(DHP): A Method for Priority Setting Derived from the Delphic Method and Analytical Hierarchy Process”, European Journal of Operational Research, pp.347-354, 1988.
[17] McKee, J. R. (1984), "Maintenance as a function of design. AFIPS National Computer Conf.;Las Vegas.
[18] Satty , T. L., “The Analytical Hierarchy Process”, McGraw-Hill, New York,1980.
[19] Solomon Paul, “Practical Software Measurement, Performance-Based Earned Value”, www.stsc.hill.af.mil.
[20] Ton Van Der Wiele and Alan Brown, “ISO 9000 Series Certification Over Time: What Have We Learnt?”