臺灣博碩士論文加值系統

本論文研製之目的是以手持裝置軟體開發為例來探討CMMI Level 2 需求管理流程領域，由於通訊的世代交替，功能性需求的增加，以及硬體元件的單晶片模組化，使得有效率的軟體開發成為重要的課題，軟體開發之首要為需求管理，了解需求並確保需求變更的正確追蹤，需要適當的需求管理工具的輔助，雖然商務的需求管理工具已相當成熟，但是卻價格昂貴、缺乏客製化和維護成本高；因此，本研究著重於從需求管理出發，提出一個適當的方法來增進軟體開發的效率，並克服上述之缺點。
軟體開發的活動包含:需求分析、設計、實作和測試等。相關的工作產出包含:需求規格書、設計規格書及程式源碼…等。這些活動、資源、工作產出的管理和專案成員之間的溝通，都需要適當的工作流程和自動化工具來協助。
為滿足基本的軟體開發的活動和產出的管理，本文提出研究架構之整合運作環境為免費的軟體工具整合而成，使其具有管理需求、維護需求的追溯、版本控管和自動化整合等整合性功能。使其滿足CMMI成熟度等級第二級的需求管理的要求與部分符合建構管理的要求。另外，也同時以需求管理工具之相關評量項目，進行評估並以手機軟體開發的實際案例分析來加以驗證。本文研究之結果可提供軟體開發組織之參考，用以提升其軟體開發效率與管理及作為導入CMMI流程改善的基礎。

The purpose of this thesis is base on the software development of handheld devices to study CMMI Maturity Level 2 Requirement Management. Due to the upcoming generation of communication, the functionalities of needs are dramatically increasing and hardware components are being packaged in single IC. Software development has become an important topic. Requirement management is the critical portion of software development. Therefore, to realize the requirement and keep track of requirement change are the topics to attract our attention. The demand of adequate requirement management tool is thus very high. Although commercial products are quite mature, they are very expensive, short of customization, and high maintain cost. To overcome these problems, this study will provide suitable methods to increase the effectiveness of software developing.
The activities of software developing will compose of requirement analysis, design, practice, testing and so on. Related work products include requirement specification, design specification, source code and so on. These activities, resource and output should be managed. Meanwhile, the communication between team members requires the support of work flow and automatic tool.
In order to fulfill the needs of software developing and management of artifacts, this paper will offer the research structure on integration of open software tools. This structure will demonstrate the feasibility of integration within requirement management, traceability maintenance, version control and auto build. Also, this study will satisfy the requirement of configuration management in CMMI Level 2. By using cell phone software as a real case can support this study and provide an example for software organization to enhance the efficiency and management. To fully utilize this method can further introduce the improvement of CMMI process.

摘要 i
Abstract ii
誌謝 iii
目錄 iv
表目錄 vi
圖目錄 vii
第1章 緒論 1
1.1 簡介 1
1.2 研究背景 1
1.3 研究動機與目標 2
1.4 文獻探討 3
1.5 研究方法 3
1.6 章節導讀 4
第2章 背景知識 5
2.1 軟體開發之生命週期 6
2.2 需求與需求管理 7
2.3 需求的問題 8
2.4 需求分析與系統設計方法 10
2.5 需求分類 13
2.6 需求追溯 15
2.7 能力成熟度整合模式 16
2.7.1 能力成熟度整合模式簡介 16
2.7.2 表述方式 17
2.7.3 模式組件 21
2.7.4 流程領域 23
2.7.5 國內 CMMI 推動情形 26
2.7.6 需求管理流程領域 28
2.8 與需求有關之國際標準 29
2.9 商用需求工具 29
2.10 手持裝置軟體的特性-以手機為例 33
第3章 需求管理之架構設計與說明 35
3.1 軟體開發角色工作與流程 35
3.2 輔助工具的需求與設計 38
3.2.1 需求管理工具-Excel 38
3.2.2 需求議題追蹤系統-Scarab 39
3.2.3 版本控管系統-CVS 40
3.2.4 缺陷議題追蹤系統-Scarab 45
3.2.5 資料庫系統 46
3.3 自動化整合運作環境 47
3.3.1 自動化機制 48
3.3.2 建構流程定義與特性 52
3.3.3 系統架構 53
3.3.4 工作流程 53
3.3.5 自動化整合的益處 54
3.4 功能需求流程架構 55
3.4.1 需求狀態流程 55
3.4.2 需求工作狀態流程 57
3.4.3 需求議題欄位屬性之建置 60
3.5 SCARAB重要操作界面 63
3.6 需求議題與驗證測試 65
第4章 研究分析與實例探討 66
4.1 與CMMI流程領域特定執行方法之要求比較 66
4.2 與四大商務需求管理工具比較 66
4.3 實例探討 69
第5章 結論與未來發展 72
參考文獻 73
附錄 76
簡歷 77

1.台灣面面觀，產業資訊，軟體產業，經濟部人才網http://hirecruit.nat.gov.tw/chinese/html/taiwan_08_05.htm
2.「軟體大未來：台灣軟體業世紀新願景」座談會，記者明雲青整理，台北，Digit Times網站http://office.digitimes.com.tw/ShowNews.aspx?zCatId=B12&zNotesDocId=2D5B362FCA9C4BB24825704400416B89, 2005
3.經濟部技術處，能力成熟度整合模式CMMI-SE/SW/IPPD V1.02, 2000.
4.Tvete, B., “Introducing Efficient Requirements Management,” Proc. of the 10th International Workshop on Database and Expert Systems Applications, 1999.
5.Leffingwell, D., Widrig, D., Yourdon, E., Managing Software Requirements: A Unified Approach, New York: Addison- Wesley; 1999.
6.Wiegers, E. K., “Software Requirements,” Microsoft Press , San Francisco, 2002.
7.Rational Unified Process, online documentation, http://www.rational.com , 2003.
8.Pozgaj, Z., Sertic, H., Boban, M., “Effective requirement specification as a precondition for successful software development project,“ Proc. of the 25th International Conference on Information Technology Interfaces IT 200, pp.669-674, 16-19 June 2003.
9.Boeham, B., and Grunbacher, P., and Briggs, R. O., “Developing Groupware for Requirements Negotiation: Lesson Learned”, IEEE Software, Vol 18, No. 3, pp. 46-55, 2001.
10.Sommerivlle, I., Software Engineering, Sixth Edition Addison-Wesley, 2001.
11.Grady, R., Practical Software Metrics for Project Management and Process Improvement, Prentice-Hall, 1992.
12.Zulter, R., “Quality Function Deployment for Software: Satisfying Customers,” American Programmer, pp.28-41, February 1992.
13.Wiegers, K., “Automating Requirements Management”, Software Development, June 29 2001. http://www.ddj.com/article/printableArticle.jhtml?articleID=184415706&dept_url=/
14.Hoffmann, M., Kühn, K., Weber, M., Bittner ,M., “Requirements for Requirements Management Tools,” Proc. of the 12th IEEE International Requirements Engineering Conference (RE'04), pp.301- 308, IEEE Computer Society, 2004.
15.Ali Babar, M., Zowghi, D., “Developing a Requirements Management Toolset: Lessons Learned,” Proc. of Australian Software Engineering Conference, 2004, Melbourne, Australia, pp.10, IEEE Computer Society, 2004.
16.Han, J., “Experience with designing a requirements and architecture management tool,” Proc. of the 2000 International Conference on Software Methods and Tools, Wollongong, Australia, pp.10, IEEE Computer Society, November 2000.
17.金子葳、洪秀朋，軟體工程--實務專家作法，第五版(Software Engineering, 5/e). 出版廠商：儒林書局，民國90年3月。
18.Carnegie Mellon Software Engineering Institute http://www.sei.cmu.edu/cmmi/cmmi.html
19.Waterbird軟體、軟體危機、軟體工程，http://www.dotspace.idv.tw/sofeeng/sofeeng_4.htm, 2001
20.經濟部技術處，CMMI 導入指引V1.0 (第二級) 2002.
21.IBM Rational,需求管理白皮書,v1.0, IBM http://searchcio.techtarget.com.cn/ciozjdysummary/2/2192002.shtml
22.The Institute of Electrical and Electronics Engineers, Inc. IEEE/EIA 12207 1998.
23.顏春煌、卓政宏，軟體工程，第二版，出版廠商：空中大學，民國 92 年
24.Borland公司, Borland CaliberRM™， http://www2.borland.com.tw/tw/Caliber.pdf
25.劉雅涵譯，系統分析、設計與開發導論，出版廠商：博碩文化，民國91年12月。
26.Booch, G., Rumbaugh, J. and Jacobson, I., The Unified Modeling Language User Guide, Addison-Wesley, 1999.
27.IBM Rational, IBM Rational Rose, http://www-8.ibm.com/software/tw/rational/products/rose/
28.IBM Rational, IBM Rational Suite AnalystStudio,
http://www-8.ibm.com/software/tw/rational/products/analyst/
29.彭淑文，「軟體需求管理之物件導向輔助架構」，中華大學資訊工程學系所，碩士班論文，全國博碩士論文摘要檢索系統 系統編號: 91CHPI0392009，民國95年。
30.Ramesh, B., Edwards, M., “Issues in the Development of a Model of Requirements Traceability,” Proc. of Int'l Symp. Requirements Engineering, pp. 256–259, Jan. 1993.
31.Ambler, S., “Trace Your Design,” Software Development, pp. 48-54, 1999.
32.Gotel, O., Finkelstein, A., “An Analysis of the Requirements Traceability Problem,” Requirements Engineering, 1 Colo.,pp. 94-101,1994.
33.Jarke, M., “Requirements tracing”, Communication of the ACM, Vol. 41, No. 12, pp. 32-36, 1998.
34.Pinherio, F., Goguen, J., “An Object-Oriented Tool for Tracing Requirements,” IEEE Software, pp.52-64, 1996.
35.資訊服務業發展綱領及行動方案簡報，經濟部工業局，民國93年9月20日。
36.Hammer, T., Huffman, L., “Automated Requirements Management-Beware How You Use Tools: An Experience Report,” Proc. of The Third International Conference on Requirement Engineering, pp.34-40, 1998.
37.Borland公司, Borland CaliberRM™ 2005, http://www.borland.com/tw/products/caliber/
38.Telelogic公司, Telelogic DOORS, http://www.telelogic.com
39.Integrated Chipware Inc. RTM Workshop 5.0 http://www.chipware.com ,2003
40.IBM Rational, IBM Rational RequisitePro, http://www-8.ibm.com/software/tw/rational/products/requisitepro/
41.Serena Software Inc. ,Serena RTM http://www.serena.com/Products/
42.陸麗娜、王志敏，軟體需求，機械工業出版社，民國89年。
43.International Council on System Engineering,” Tools Survey” “Tools Survey: RM tools”, Available from http://www.incose.org/tools/tooltax.html , 2002.
44.GSM word, http://www.gsmworld.com/index.shtml
45.IEEE Std 830, Software Requirement Specification, IEEE, 1998
46.Open Source Software Engineering Tools, 網站http://scarab.tigris.org/
47.Concurrent Versions System, http://www.nongnu.org/cvs/
48.CVSGUI, http://www.wincvs.org/
49.劉安瑋，“ 好用的工具就在你身邊--用CVS執行CMMI建構管理作業” ， 產業通訊，第56期，軟體協會，民國94年。
50.MySQL官方網站：http://www.mysql.com/
51.Chen, T.L., Lee, T.-L., Huang, Y.M., Lo, A., Chiou, C.W., “On Continuous Integration for Mobile Software Development,” Proc. of The First Taiwan Software Engineering Conference, Taipei, Taiwan, pp.38-42, June 3-4, 2005.
52.Cruisecontrol, http://cruisecontrol.sourceforge.net/
53.ANT, http://ant.apache.org/
54.Tomcat, http://www.tom-cat.com/tomcat.html
55.JDK(Java Development Kit), http://java.sun.com/