臺灣博碩士論文加值系統

對於應用資訊系統開發者而言，開發合乎使用者需求的軟體始終是一大重要課題，在軟體的設計開發中，常會遭遇到不可預期的需求變更，為了讓系統之開發者與專案管理者在系統開發過程中，都能有效管理需求變更，減少開發成本支出，當務之急為營造一個需求管理的環境。需求管理在系統開發的每一個階段均須徹底執行以確保需求變更的正確追蹤，本研究將著重於應用系統之需求的規格化與管理。
本論文提出一個可用於說明、分析、並管理應用系統需求的物件導向架構。由於物件的繼承特性，可以帶來許多設計上的優勢，物件導向設計方法已儼然成為系統設計的新潮流。我們將需求定義為物件，並分類為不同的需求類別，以預先定義的方式管理類別與其屬性，我們所提出的架構可以有效的維護以及利用系統需求。
根據本研究架構提出之理論所實作的系統，除了提供基本的需求維護管理功能，也包含雙向需求追蹤(bi-directional requirements tracing)的機制，追蹤需求改變的影響與差異內容，同時也利用既存的需求資訊進行使用案例(use case)資訊的分析，供系統分析相關人員參考，進而能夠使需求資訊得以演化為後續的設計資訊，這些應用使需求管理架構更為完善。

Producing software that fulfills the user requirements has always been a concerned issue for the application developers. The requirements are always changing during the development process. To provide an effective way of managing requirement changes and reducing the production cost during the requirements engineering process, a requirement management environment plays an important role in the software development project. Requirement management should be performed throughout the entire project cycle to keep track of the changes. The specification and management of requirements will be the focus of this thesis
This research aims to construct an object-oriented framework for specifying, analyzing, and managing requirements for application systems. Object-oriented design methodologies have made a new trend for system design. It does bring a number of benefits because of the inherent characteristics. The requirements will be defined as objects and classified as classes. A mechanism will be employed to maintain the class and their attributes. By storing the requirements and presenting them as objects, the system requirements of different projects can be well maintained and used by the proposed framework.
Based on the proposed framework, a prototype system has been implemented. In addition to maintain the requirements, this system also provides a tracing mechanism for bi-directional tracing of the requirement changes. Furthermore, according to the existing requirement relations, use cases can be advised by the system.

中文摘要 i
Abstract ii
第一章　緒論 1
1.1　研究背景 1
1.2　研究動機及目的 2
1.3　研究範圍 3
1.4　研究方法及步驟 4
1.5　章節導讀 6
第二章　文獻探討 7
2.1　物件導向設計與模組化方法 7
2.2　需求分析與需求表示法 8
2.3　需求分類 10
2.4　需求管理與需求追蹤 12
2.5　需求管理工具 16
2.6　軟體組態管理 20
2.7　文獻探討結語 21
第三章　軟體需求的定義與分類 22
3.1　物件化需求定義 22
3.2　需求類別 26
3.2.1　功能性需求 29
3.2.2　非功能性需求 31
3.2.3　網路相關需求 33
3.2.4　專業領域需求 35
3.3　需求類別與屬性定義機制 36
3.3.1　預先定義類別與屬性 36
3.3.2　動態新增屬性 38
3.3.3　動態新增類別與屬性 39
3.4　需求關係 40
3.5　設計物件 43
第四章　需求管理架構之設計理念與說明 46
4.1　架構設計理念 46
4.1.1　需求的演化 46
4.1.2　需求的分析與部署 48
4.1.3　需求管理與需求追蹤 49
4.2　需求管理架構 50
4.2.1　需求管理架構概念模型 51
4.2.2　需求管理架構模組說明 54
4.3　需求維護模組 55
4.4　需求分析輔助模組 57
4.5　需求部署模組 59
4.6　需求追蹤模組 60
第五章　系統實作 63
5.1　開發環境 63
5.2　系統功能架構與說明 64
5.3　實例說明 73
5.3.1　需求物件與傳統需求規格之對應說明 75
5.3.2　需求類別與屬性初始化定義 79
5.3.3　專案的新增與選用 80
5.3.4　需求的增修維護 81
5.3.5　需求分析進階支援 84
5.4　系統評估 90
第六章　未來研究與結論 93
6.1　未來研究 93
6.2　結論 95
參考文獻 97
中文文獻 97
英文文獻 98

中文文獻
1.[Wate01] Waterbird (2001)，軟體、軟體危機、軟體工程，http://www.dotspace.idv.tw/sofeeng/sofeeng_4.htm。
2.[林雅鈞01] 林雅鈞、王素華(2001)，應用於物件導向系統設計之版本變更差異分析架構，物件導向研討會，頁271-278。
3.[徐惇雷99] 徐惇雷、林子翔、蔡明成、蔡宗霖、陳惠慈(1999)，教學資源輔助系統，元智大學資訊管理學系電子商務課程實作專案。
4.[彭淑文00] 彭淑文、徐惇雷、謝佩芬、鄭功彥、戴梅芳、張亦姿(2000)，教學資源輔助系統，元智大學資訊管理學系軟體專案管理課程評估專案。
5.[陸麗娜00] 陸麗娜、王忠民、王志敏(2000)，軟體需求，機械工業出版社。
英文文獻
1.[Ambl99] Ambler, S., “Trace Your Design,” Software Development, April 1999, pp. 48—54.
2.[Bach98] Bach, J., “The Highs and Lows of Change Control,” Computer, Vol. 31, No. 8, August 1998, pp. 113—115.
3.[Booc99] Booch, G., J. Rumbaugh, and I. Jacobson, The Unified Modeling Language User Guide, Addison-Wesley, 1999.
4.[Buck94] Buckley, F., “Implementing a Software Configuration Management Environment,” Computer, Vol. 272, February 1994, pp. 56—61.
5.[Cali03] CaliberRM?, Version 5.0 Borland Software Corporation, 2003, http://www.borland.com/caliber/
6.[Chan97] Chan, A. and S. Hung, “Software Configuration Management Tools,” Proceedings of the 8th International Workshop on Software Technology and Engineering Practice, 1997, pp. 238—250.
7.[CORE03] CORE Enterprise, Version 4.0, Vitech Corporation, 2003, http://www.vitechcorp.com/core/enterprise.html
8.[Crnk99] Crnkovic, I., P. Funk, and M. Larsson, “Processing Requirements by Software Configuration Management,” Euromicro 99 Conference, Milano, Italy, Vol. 2, 1999, pp. 260—265.
9.[Davi93] Davis, A. M., Software Requirements: Objects, Functions and States, Prentice-Hall, 1993.
10.[Davi99] Davis A. and D. Leffingwell, “Making Requirements Management Work for You,” Crosstalk, Journal of Defense Software Engineering, April 1999, http://www.stsc.hill.af.mil/Crosstalk/1999/APR/davis.asp
11.[Do99] Do, A., “The Impact of Configuration Management During the Software Product’s Lifecycle,” Proceedings of the 18th Digital Avionics Systems Conference, 1999, pp. 1.A.4-1—1.A.4-8.
12.[DOOR02] Telelogic DOORS, Version 6.0, Telelogic AB, 2002, http://www.telelogic.com/products/doorsers/doors/
13.[Eele01] Eeles, P. “Capturing Architectural Requirements,“ The Rational Edge, 2001, http://www.therationaledge.com/content/nov_01/t_architecturalRequirements_pe.html
14.[Feil91] Feiler, P., “Configuration Management Models in Commercial Environments,” Technical Report CMU/SEI-91-TR-7, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, 1991.
15.[Fink91] Finkelstein, A., “Tracing back from requirements,” IEE Colloquium on Tools and Techniques for Maintaining Traceability During Design, 2 Dec 1991, pp. 7/1—7/2.
16.[Gard92] Grady, R., Practical Software Metrics for Project Management and Process Improvement, Prentice-Hall, 1992.
17.[Gote94] Gotel, O. and A. Finkelstein, “An Analysis of the Requirements Traceability Problem,” Proceedings of the First International Conference on Requirements Engineering, Colorado Springs, Colo., April 1994, pp. 94—101.
18.[Hamm98] Hammer, T. and L. Huffman, “Automated Requirements Management-Beware HOW You Use Tools: An Experience Report,” Third International Conference on Requirements Engineering, 1998. Proceedings, 1998, pp.34—40.
19.[IEEE87] IEEE Guide to Software Configuration Management, IEEE/ANSI Standard, 1987.
20.[INCO02] International Council on Systems Engineering, “Tools Survey: Requirements Management (RM) Tools,” December 29, 2002, http://www.incose.org/tools/tooltax.html
21.[Jaco99] Jacobson, I., G. Booch, and J. Rumbaugh, The Unified Software Development Process, Addison-Wesley, 1999.
22.[Jark98] Jarke, M., “Requirements tracing,” Communication of the ACM, Vol. 41, No. 12, December 1998, pp. 32—36.
23.[Jasm98] Jasmine Concepts, Version 1.2, Computer Associates International, Inc., 1999.
24.[Koto96] Kotonya, G. and I. Sommerville, “Requirements Engineering with Viewpoints,” BCS/IEE Journal of Software Engineering, Vol. 11, No. 1, 1996, pp. 5—18.
25.[Leff00] Leffingwell, D. and D. Widring, Managing Software Requirements, Addison-Wesley, 2000, pp. 261—268.
26.[Leon00] Leon, M., “Staying on Track,” Intelligent Enterprise, September 2000, pp. 54—57.
27.[Pinh96] Pinherio, F. and J. Goguen, “An Object-Oriented Tool for Tracing Requirements,” IEEE Software, Special Issue of Papers from International Conference on Requirements Engineering ’96, 1996, pp. 52—64.
28.[Rame93] Ramesh, B. and M. Edwards, “Issues in the Development of a requirement Traceability Model,” Proceedings of IEEE International Symposium on Requirements Engineering, 1993, pp. 256—259.
29.[Rame95] Ramesh, B., Lt. C. Stubbs, Lt. Cmdr. T. Powers, and M. Edwards, “Lessons Learned from Implementing Requirements Traceability,” Crosstalk, Journal of Defense Software Engineering, April 1995, http://www.stsc.hill.af.mil/crosstalk/1995/apr/Lessons.asp
30.[Rame01] Ramesh, B., D. Dwiggins, G. DeVries and M. Edwards, “Towards requirements traceability models,” Proceedings of the 1995 International Symposium and Workshop on Systems Engineering of Computer Based Systems, 1995, pp. 229—232
31.[Requ03] Rational RequisitePro v2003, IBM Corporation, 2003, http://www.rational.com/products/reqpro/index.jsp
32.[Rose03] Rational Rose family v2003, IBM Corporation, 2003, http://www.rational.com/products/rose/index.jsp
33.[RTM03] RTM Workshop Version 5.0, 2003, Integrated Chipware Inc., http://www.chipware.com/
34.[Rumb99] Rumbaugh, J., I. Jacobson, and G. Booch, The Unified Modeling Language Reference Manual, Addison-Wesley, 1999.
35.[Somm01] Sommerville, I., Software Engineering, Sixth Edition, Addison-Wesley, 2001.
36.[Spen98] Spence, I. and L. Probasco, “Traceability Studies for Managing Requirements with Use Cases,” 1998, http://www.rational.com/products/whitepapers/022701.jsp
37.[VB99] Microsoft Visual Basic 6.0 Enterprise Edition, Microsoft Corporation, 1999, http://www.microsoft.com/taiwan/vstudio/vbasic/default.htm
38.[Vita03] Vital Link Requirements Management Tool, 2003, http://www.complianceautomation.com/software/software.htm
39.[VSS99] Microsoft Visual SourceSafe 6.0, Microsoft Corporation, 1999, http://msdn.microsoft.com/ssafe/default.asp
40.[Watk94] Watkins, R. and M. Neal, “Why and How of Requirements Tracing,” IEEE Software, July 1994, pp. 104—106.
41.[Wieg99a] Wiegers, K., Software Requirements, Redmond, Washington: Microsoft Press, 1999.
42.[Wieg99b] Wiegers, K. E. “Automating Requirements Management.” Software Development, July 1999.
43.[Zult92] Zulter, R., “Quality Function Deployment for Software: Satisfying Customers,” American Programmer, February 1992, pp. 28—41.