在軟體專案開發的過程中，需求塑模的完整性與正確性是影響軟體專案開發成果的重要因素。使用個案圖 (Use Case Diagram)是對需求塑模進行物件導向分析與設計的標準語言。而在PIM階段時，要從使用個案圖建構出循序圖的過程中，對於辨識物件、操作與物件之間關係是一項不明確的工作。目前已經有研究提出強韌分析 (Robustness Analysis)的方法，來拉近使用者需求塑模與PIM塑模之間的差距。但是如何從需求文件實施強韌分析轉換出強韌圖 (Robustness Diagram)以及利用強韌分析強化使用個案之正確性與完整性是目前較為缺乏的部分。
為了解決這個問題，我們提出使用個案圖、活動圖與強韌圖來表示使用者需求。當使用個案圖已經建構，則使用活動圖來描述每一個使用個案活動的流程與流程相關的輸出入。最後使用強韌分析的轉換規則，來辨識使用者需求文件中的介面物件、控制物件與實體物件，並強化使用者需求的完整性。強韌分析完後的結果，可以用在建構循序圖的PIM階段。最後實施可行性測試，可行性測試包含模擬測試與實驗測試，透過此方式來驗證所提出的方法論。藉由這個方法論，系統開發工程師可以有效率地強化使用者需求的完整性與正確性，也因此減少系統開發失敗的風險。

The completeness and correctness of requirement modeling is the crucial factor that affecting the success of the system development. Use case diagram is the standard tool for modeling the use requirement for the objected-oriented systems analysis and design. However, to model the sequence diagram in the platform independent model (PIM) stage is still not a straightforward task to identify objects, operations and their relationships from the use case diagram. Robustness analysis has been proposed to bridge this gap between the user requirement modeling and the PIM modeling. However, the detailed guideline for the robustness analysis is lacking, while it is important for designer to enhance the completeness and correctness of the user requirement modeling.

To alleviate the forgoing problem, we proposed that use case diagram, activity diagram and robustness diagram are used to represent the use requirement. Once a use case diagram is constructed, the activity diagram is used to describe the activity flow and the associated input/output of each use case. Finally, the robustness analysis with the guideline proposed is used to help the identification of boundary, control, and entity objects and enhance the completeness of the user requirement. The outcome can then be used to construct a sequence diagram in the PIM. A real-world case is presented to illustrate the feasibility of using the proposed method. With this methodology, the system developer can enhance the completeness and correctness of user requirement efficiently and thereby reduce the risk of success development failure.

目錄 頁次
目錄 i
圖目錄 ii
表目錄 iii
中文摘要 iv
Abstract v
第一章、緒論 1
第一節、研究背景與動機 1
第二節、研究目的與範圍 2
第三節、研究方法 2
第四節、論文架構 3
第二章、文獻探討 4
第一節、使用者需求塑模 4
第二節、強韌分析之概念 10
第三節、強韌分析之物件 15
第四節、物件聚集原則 20
第三章、研究方法 22
第一節、軟體工程研究方法 22
第二節、研究流程 23
第四章、強韌分析方法論 26
第一節、建構強韌圖 27
第二節、精鍊使用個案之方法 32
第五章、可用性測試 34
第一節、評估項目與模擬測試 34
第二節、實際案例測試－便當王系統範例 44
第三節、觀察與評估 75
第六章、結論 76
第一節、研究成果 76
第二節、研究限制 76
第三節、研究貢獻 77
第四節、未來研究方向 77
參考文獻 79
中文參考文獻 79
英文參考文獻 79

中文參考文獻
吳仁和，「物件導向系統分析與設計：結合MDA 與UML」，二版，智勝，台北，2007 年。
英文參考文獻
Ambler, S.W., The Object Primer - Agile Model Driven Development with UML 2, 3rd Edition, Ambysoft, Canada, 2004.
Bailin, S., “An Object-Oriented Requirements Specification Method,” Communications of the ACM, Vol. 32, No. 5, 1989, pp. 608-623.
Booch, G., Object-Oriented Analysis and Design Applications, Second Edition, Addision-Wesley, 1994.
Borillo, D., Use Case Driven Object Modeling with UML, (Online information; retrieved 08/25/2006.) http://pst.web.cern.ch/PST/HandBookWorkBook/Handbook/SoftwareEngineering/UCDOM_summary.html, 2000.
Constantine, L., and Lockwood, D., Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design, ACM Press, New York, 1999.
Elmasri, R. and Navathe, S., Fundamentals of Database Systems, Third Edition, Addison-Wesley, Boston, 2000.
Glinz, M., “Problems and Deficiencies of UML as a Requirements Specification Language,” Proceedings of the Tenth International Workshop on Software Specification and Design, San Diego, 2000, pp. 11-22.
Jacobson, I., Christerson, M., Jonsonn, P., and Overgaard. G., Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, Reading, Massachusetts, 1992.
Jacobson, I., Object-Oriented Software Engineering: A Use Case Driven Approach, Addition-Wesley, Harlow, England, 1992.
Naur, P., Randell, B., and Buxton, N., Software Engineering: Concepts and Techniques, Mason/Charter Publishers, Inc., 1976.
Nunamaker, J., F. Jr., Chen, M. and Purdin, T. D. M., “Systems development in information systems research,” Journal of Management Information Systems, Vol. 7, No 3, pp. 89-106, 1991.
Oestereich, B., Developing Software with UML, Addison-Wesley, Reading, Massachusetts, 1999.
OMG, The Object Management Group, OMG Unified Modeling Language Specification, V1.5, (Online information; retrieved 08/25/2006.) http://www.omg.org/docs/formal/03-03-01.pdf, March 2003.
Rosenberg, D., and Scot, K., Applying Use-Case Driven Object Modeling with UML: An Annotated E-commerce Example, Addison Wesley, Reading, Massachusetts, 2001.
Rosenberg, D., and Scott, K., Driving Design with Use Cases, Software Development, (Online information; retrieved 07/10/2006.) http://www.sdmagazine.com/print/documented=11118, December 2000.
Rosenberg, D., and Scott, K., Use Case Driven Object Modeling with UML, Addison Wesley, Reading, Massachusetts, 1999.
Verner, M., Cox, S., and Cerpa, N., “Requirements Engineering and Software Project Success: An Industrial Survey in Australia and the U.S.,” Australia Journal of Information Systesm, Vol. 13, No. 1, 2004, pp. 225-238.
Vick, C. R., and Ramamoorthy, C. V., Handbook of Software Engineering, Van Nostrand Reinhold, New York, 1984.
Wegner, P., Paradigms of Infonnation Engineering, The Study of Information, John Wiley & Sons, New York, 1983, pp. 163-175.
Wiegers, K., Software Requirements, Second Edition Microsoft Press, Redmond, West Australia, 2003.