以現今軟體系統漸趨複雜的研究來看，大多數的企業，並沒有測試設計人員，因此測試案例的規劃與設計上，往往缺乏模組化設計與制度化的作法，讓測試人員很難多人分工合作，而產出的測試案例文件不規則與不完整，只能採用手動測試，導致浪費很多人力測試時間與成本，無法達到將測試案例與工具整合自動化。

在本篇論文中，為了要解決目前測試人員規劃與設計測試案例的問題，因此參考Rational 統一流程(Rational Unified Process,RUP) 、統一塑模語言(Unified Modeling Language, UML)、IEEE/EIA 12207國際標準、CMMI(Capability Maturity Model Integration)流程改善方法論、EIA/IEEE J-STD-016文件規範、測試成熟度模式分析的方法論與經驗值，將測試流程與細部定義，訂定測試制度化的四大步驟，1. 建立共有字彙表單、2. 定義使用案例目的與場景描述、3. 定義測試資料、4. 依使用案例場景描述對應至測試案例，再經由訂購產品案例實作，成功地找出一套可運作的方法，解決功能測試應用於測試案例的問題，有效降低測試時間與成本。

In today's software systems become increasingly complex studies. The majority of enterprises are no test designers. Therefore, the planning and design of test cases often the lack of modular design and institutionalized practices. Let testing members make it difficult to cooperate. The output of test case’s documentation are irregular and incomplete. Only it can do manual testing. It causes to waste time of manpower and cost. It can not achieve the automation of test cases and tools integration.

In this paper, in order to resolve the current testers test case planning and design issues. Therefore reference Rational Unified Process, Unified Modeling Language, IEEE / EIA 12207 international standard, CMMI process improvement methodology, EIA / IEEE J-STD-016, test Maturity model Analysis methodology and experience. To define detailed definition of the testing process and the four steps of institutionalization. 1. To create a total vocabulary form. 2. To define the purpose and use case scenario description 3. To define test data 4. Depending on use case scenario description corresponds to the test case. Implemented through the order product case again, successfully identify a set of workable test cases solutions to the functional test, and effectively reduce test time and cost.

1. 朱慧德，”軟體測試標準之探討”， 軟體產業通訊 37期，http://it.moeaidb.gov.tw/sinet/pub/PUB37/37-10.htm
2. 吳祖寰(民96)，「奠基於UML狀態圖的測試案例產生器」，國立中正大學碩士論文
3. 金子葳、溫哲彥譯, Roger S. Pressman原著,「軟體工程實務專家作法」, 儒林出版社
4. 洪麗玲，”測試工作觀念與實務”，http://www.iii.org.tw/system/html/ testtool/Doc/23A02-1.htm
5. 陳瑞池(民90)，「軟體測試技術」，資訊工業策進會
6. 葉政邦 (民97)，「軟體自動化測試應用於資訊系統維護之研究」，國立台灣科技大學碩士論文
7. 楊昭仁，”軟體測試管理經驗談”，http://www.iii.org.tw/system/html/ testtool/Doc/23A03-1.htm

英文參考文獻
8. Burnstein, Ilene、Suwannasart, Taratip and Carlson C.R., “Developing a Testing Maturity Model, Part I”, http://www.stsc.hill.af.mil/crosstalk/1996/aug/developi.asp
9. CMMI Product Team,"CMMI for Development, Version 1.3", Software Engineering Institute, Nov., 2010.
10. Dustin, Elfriede、Rashka, Jeff、Paul, John，”Automated Software Testing”， Addison-Wesley, 1999
11. Fewster, Mark、Graham, Dorothy，”Software Test Automation; Effective use of test execution tools”，Addison-Wesley, 1999
12. Greenberg B. and Reynolds K.，”Software Testing Processes; From Concept to Reality”, in Proc. of 18th Annual International Software Testing Conference, Orlando, USA.1998
13. Humphrey, W., T. Snyder, and R. Willis, "Software Process Improvement at Hughes Aircraft," IEEE Software, July 1991, pp. 11-23.
14. IEEE/EIA 12207.0-1996, March 1998, The Institute of Electrical And Electronics Engineers, Inc Electronic Industries Association Engineering Department
15. IEEE/EIA 12207.1-1996, March 1998, The Institute of Electrical And Electronics Engineers, Inc Electronic Industries Association Engineering Department
16. IEEE/EIA 12207.2-1996, March 1998, The Institute of Electrical And Electronics Engineers, Inc Electronic Industries Association Engineering Department
17. International Organization for Standardization, “ISO/IEC 12207 Standard for Information Technology - Software life cycle process” 1996.
18. J-STD-016-1995, 30 September 1995, The Institute of Electrical And Electronics Engineers, Inc Electronic Industries Association Engineering Department
19. Koomen, Tim、Pol, Martin, “Test Process Improvement”, Addison-Wesley, 1999
20. Kruchten, P. (2002). The Rational Unified Process An Introduction (Second ed.):Addison-Wesley.
21. Paulk, M., C. Weber, B. Curtis, and M. Chrissis, The Capability Maturity Model Guideline for Improving the Software Process, Addison-Wesley, 1995.
22. Paulk, M.C., et al., “The Capability Maturity Model: Guidelines for Improving the Software Process”, Addison-Wesley, 1995.
23. Rumbaugh, J., "Getting Started: Using Use Cases to Capture Requirements, " Journal of Object-Oriented Programming (JOOP, SIGS Publications, Vol.7, No.5, New York, Sep, 1994