臺灣博碩士論文加值系統

在軟體系統開發的過程中，如何決定需求的可行性對於日後的系統功能與開發成本具有關鍵性的影響。需求的取捨與優先順序往往涉及許多複雜的因素，也是軟體工程相關領域的研究重點。本研究的目的在於發展一個軟體需求的決策模式，提供系統開發組織與人員以及使用者對於各項需求進行量化的評估，以符合預期的目標，增進系統的資訊品質，提升軟體流程改善效益。在研究方法上首先以建立階層式模型的方式，將影響軟體系統需求的各個特徵項目歸納至適當的需求類型屬性中。接著模擬專家對於各項目的評估資料，再利用主成份分析法(Principal Component Analysis)計算最大特徵值與特徵向量，決定系統需求的優先順位。最後並以交互驗證分析方式檢驗研究方法的穏定性。本研究的結果嘗試建立一個模擬專家對軟體需求順位的評分模式，同時可將這些需求項目列入系統分析階段的需求規格書，做為開發與驗收的基準，未來可以結合軟體品質度量的觀念做為協助軟體流程改善的參考。

During the process of software development, the feasibility study in the determination of software requirements plays a primary role in system functionality and developing cost. The prioritization of various requirements affected by many complicated factors becomes one of emphasized research topics. The goal of this research is to establish a decision model for prioritization of software requirements. This model can be used as a quantitative evaluation method of requirements by developing staff and general users. The resulting information system should match the expectation, improve information quality and promote software development process effectively. Our research start with a hierarchical model for representing important attributes of interest and grouping them into some categories. Next, we generate values of these attributes randomly and apply the Principal Component Analysis to calculate the maximum eigenvalues of covariance matrix of attributes, its corresponding eigenvectors and the priority of each software requirements. Finally, we conclude the model stability by a cross validation study. The result of this research might be an aid to developers in software requirement planning stage objectively. Also, the attributes discovered in analysis stage can be included in the software requirements documents as a baseline in developing stage and project completing stage. Furthermore, combing with the concept of software measurement, our result can be an important reference in software process improvement.

摘要 II
Abstract III
目次 IV
表目錄 VI
圖目錄 VII
第一章 緒論 1
1.1 研究背景 1
1.2 研究目的 1
第二章 文獻探討 2
2.1 軟體需求分析 2
2.2 系統模擬 16
2.3 主成份分析 18
2.4 ISO/IEC 9126 21
第三章 研究方法 23
3.1 研究架構 23
3.2 研究步驟 24
第四章 模擬實驗 31
4.1 實驗設計 31
4.2 主成份分析 34
4.3 實驗結果分析 43
第五章 結論 46
5.1 研究結論 46
5.2 未來研究建議 47
參考文獻 48

一、中文部份：
[1] 王存國、何靖遠、林子銘、侯昌永 編著，企業資訊系統，華泰，台北，pp.252-254，民國92年。
[2] 王妙雲 編著，系統分析與設計：方法、工具論，碁峰資訊，台北，pp.47-56，民國85年。
[3] 王保進 編著，多變量分析：套裝程式與資料分析，王保進，台北，pp.70-77，民國93年。
[4] 陳瑞順、蔡永順 編著，資訊管理:企業資訊系統管理與個案分析，智勝，pp.82-84，台北，民國93年。
二、英文部份：
[5] Abran, A., and James, W. Moore, Guide to the Software Engineering Body of Knowledge , IEEE Computer Society Press,2004.
[6] Andreou, A.S., “Promoting software quality through a human, social and organizational requirements elicitation process”, Journal of Requirements Engineering, Vol. 8, No.2, pp.85-101, 2003.
[7] Banks, J., Handbook of Simulation ：Principles, Methodology, Advances, Applications, and Practice , John Wiley & Sons, Inc., pp.1-18, 1998.
[8] Cattell, R.B., Handbook of multivariate experimental psychology, Chicago: Rand McNally,1966.
[9] Chrissis, M. B., Konrad M., and Shrum S., CMMI Guidelines for Process Integration and Product Improvement , Pearson Education, pp.465-497, 2003.
[10] Ferdinandi, P. L., A Requirements Pattern: Succeeding in the Internet Economy，Addison-Wesley, 2001.
[11] Firesmith, D., “Prioritizing Requirements”, Journal of Object Technology, Vol. 3, No. 8, pp. 35-47, 2004.
[12] Franch, X., and Carvallo, J. P., “Using Quality Models in Software Package Selection”, IEEE Software, Vol. 20, No. 1, pp. 34-41, 2003.
[13] Gause, D., and Weinberg G., Exploring Requirements: Quality before Design, Dorset House, 1989.
[14] Goguen, J., and Linde, C., “Techniques for Requirements Elicitation”, International Symposium on Requirements Engineering, San Diego, California, 1993.
[15] IEEE Recommended Practice for Software Requirements Specification, Institute of Electrical and Electronics Engineers, New York, IEEE Standard 830-1998, IEEE, 1998.
[16] ISO/IEC Standard 9126-1 Software Engineering—Product Quality—Part 1: Quality Model, ISO Copyright Office, Geneva, June 2001.
[17] Jalote, P., CMM in Practice: Processes for Executing Software Projects at Infosys, Addison-Wesley, pp.45-53, 2000.
[18] Kaiya, H., Horai, H., and Saeki, M., “AGORA: Attributed Goal-Oriented Requirements Analysis Method”, Proceedings of the IEEE Joint International Conference on Requirements Engineering, pp.13 – 22, 9-13 Sept. 2002.
[19] Laudon, K.C., and Laudon, J.P., Essentials of Management Information Systems: Organization and Technology in the Networked Enterprise, Prentice Hall, pp.288-305, 2001.
[20] Leon, S. J., Linear Algebra with Applications, Macmillan, pp.196-199, 1990.
[21] Li, M., and Smidts, C.S. ,“A Ranking of Software Engineering Measures Based on Expert Opinion”, IEEE Transactions on Software Engineering, Vol. 29, No. 9, pp. 811-824, 2003.
[22] McGarry, J., Practical Software Measurement: Objective Information for Decision Makers, Addison-Wesley, pp.31-38, 2001.
[23] Rockart, J. F., “Chief Executives Define Their Own Data Needs”, Harvard Business Review, March-April, pp.81-93, 1979.
[24] Sharma, S., Applied Multivariate Techniques, John Wiley & Sons, Inc., pp.58-89,1996.
[25] Skyrius, R., “User Information Needs Against Information Technology Services: Expectations and Delivery”, Journal of American Academy of Business, Vol. 7, No. 2, pp.191-196, 2005.
[26] Sommerville, I., Software Engineering, Addison-Wesley, pp.121-144, 2004.