|
中文文獻 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.
|