熟知的「模式驅動架構」、「統一塑模語言」及「電腦輔助軟體工程」 (CASE)工具等知識可以解決目前軟體開發所面臨的生產率、可攜性、互動性及維護性等四大問題，但目前尚未有以主流的 CASE 工具，提出可遵循的系統分析方法研究。因此本研究目的在建立公司內部可遵循的系統分析與設計的方法，透過 CASE 工具來簡化文件製作、提升維護效率，以分治的原理，從企業組織的宏觀面定義出系統的範圍，再以物件導向去分析其行為與結構，建立一組循序漸進的分析流程。

在分析方法上，加入了「 企業流程塑模」 及「雙向需求追溯表」 , 企業流程圖讓整體塑模的成果有明確的入口地圖 (sitemap)，而塑模成果因為有 CASE 工具支持，具有層級展示效果，改善了過往分析師直接面對各式塑模圖的困境。在類別圖、循序圖部份簡化了 CRUD 等控制物件， 傳達更明確；雙向需求追溯表為系統分析的階段性確認提供了有效的措施。在物件轉換技術上， 先使用轉換經驗法則，找出潛在的介面物件，再使用「交易樣式」找出實體類別，對使用者以故事板進行情境展示。兼具企業（組織）觀點與系統功能（使用個案）的塑模流程研究，
可做為公司內部的系統分析規範與訓練教材。

在案例展示的過程中，由於使用 CASE 工具單一且完整性的軟體工具，改善了分析師原來需要使用多種繪圖軟體工具，隨時可將結果輸出成文件，節省最後再整理成文件的軟體操作與文件排版時間，且 CASE 工具在塑模過程中，能使用元件轉換與模型同步修正，更能讓分析師集中精力在思考系統塑模的問題點，有效率的縮短了系統分析花費時間，同時提升文件的正確性與效率。

Current common methodologies such as Model Driven Architecture (MDA),
Unified Modeling Language (UML) and computer-aided software engineering (CASE) tools could partially fulfil the main requirements of software development - productivity, portability, user interaction design, and maintenance, however, none are able to provide reproducible research for systems analysis. The aim of this research is to establish a method for systems design and analysis that can be easily implemented within any
enterprise, as it facilitates documentation and improves maintenance efficiency through CASE tools. A step-by-step analysis process produced by analysing behaviour and structure.

Business process Modeling (BPM) and Requirements Traceability Matrix should be implemented in order to perform systems analysis. The flow chart of an enterprise creates a clear entry (sitemap) and a hierarchical effect as a result of utilising the CASE tool. This also improves the current approach as analysts create superfluous Modeling diagrams. Users and developers are able to communicate more clearly as a result of simplified CRUD functions expressed in class and sequence diagrams. The Requirements Traceability Matrix additionally provides an effective method for system analysis through the usage of object conversion technique, the transitive property of the matrix helps locate the entity type as well as identifies potential objects for the interface and adds to the storyboard. By understanding the use cases and its accompanying design
interactions, this research developed from the Modeling process of software scope could even serve as a business internal analysis and implementation process for the organization.

As per the method presented above, the comprehensiveness of the CASE tool reduces the dependency on usage of a variety of software drawing tools and allows documents to be easily generated into proper format and layout, avoiding the time-consuming and the computational cost of organising them into files. Furthermore, the CASE tool is able to automatically perform component conversion and synchronise
versions of the model during the Modeling process, allowing analysts to concentrate on solving other problems arising from systems Modeling. As a result, the tool effectively shortens the time and effort spent on system analysis and also improves on document integrity.

論文審定書.................................................... i
致謝................................................................ ii
摘要................................................................ iii
Abstract........................................................... iv
目錄................................................................. vi
圖次................................................................. viii
表次................................................................. x
第一章 緒論...................................................... 1
第一節 研究背景與動機.................................. 1
第二節 研究目的與範圍.................................. 2
第二章 文獻探討.............................................. 3
第一節 物件導向分析設計方法論.................. 3
第二節 模式驅動架構.......................................11
第三節 電腦輔助軟體工程工具...................... 12
第四節 交易樣式.............................................. 13
第五節 需求分析.............................................. 14
第六節 強韌分析.............................................. 15
第三章 研究方法.............................................. 18
第一節 設計科學研究法.................................. 18
第二節 研究流程與步驟.................................. 20
第四章 設計與發展解決方案.......................... 23
第一節 CASE 工具專案設定............................. 24
第二節 需求塑模............................................... 26
第三節 互動行為塑模....................................... 34
第四節 使用者介面塑模................................... 42
第五節 物件結構塑模....................................... 46
第六節 雙向需求確認....................................... 48
第五章 展示與評估........................................... 50
第一節 案例展示............................................... 50
第二節 案例評估............................................... 78
第六章 討論與結論........................................... 81
第一節 研究成果............................................... 81
第二節 研究貢獻............................................... 83
第三節 研究限制與未來研究方向................... 85
參考文獻............................................................ 86

中文部份
吳仁和，物件導向系統分析與設計──結合MDA與UML， 第七版，台北：元照，Feb 2022。
邱郁惠，寫給SA的UML／MDA實務手冊，初版，台北：上奇科技，2007。
陳會安，新觀念UML系統分析與設計實務，初版，台北：旗標出版，Mar 2013。

英文部份
Booch, G., Jacobson, I., and Rumbaugh, J., The Unified Modeling Language User Guide (Reading, MA: Addison-Wesley), 1999
Booch, G., Unified Modeling Language User Guide, 2/e, The (Addison-Wesley Object Technology Series), July 2017
Coad, P., Object Models: Strategies, Patterns, & Applications, Prentice Hall, 1995
Davenport, T. H., and Short, J. E., The New Industrial Engineering: Information Technology and Business Process Redesign, Sloan Management Review, Summer 1990, pp. 5-14.
FIPS, Integration Definition for Function Modeling, Federal Information Processing Standards Publications, U.S. Department of Commerce, 1993, p. 183
Hoffer, A. J., George, F. J., Valacich, S. J., ModernSystem Analysis and Design. 2nd Ed. Reading, Massachusetts: Addison Wesley Logman, Inc.,1998, pp.108-109
Jacobson, I., Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, 1992, pp. 130-133
Jacobson, I., Ericsson, M.,nd Jacobson, A., The Object Advantage: Business Process Reengineering With Object Technology, First Edition, Addison-Wesley, 1995, p.3
Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Software Development Process, Reading, New Jersey: Prentice Hall, 2012
Krigsman, M. CIO analysis: Why 37 percent of projects fail, ZDnet, March 2011, https://www.zdnet.com/article/cio-analysis-why-37-percent-of-projects-fail/, [Retrieved 2022/02]
Peffers, K., Tuunanen, T., Rothenberger, M. A. and Chatterjee, S., A design science research methodology for information systems research, Journal of management information systems, 2007, pp. 45-77.
Martin, J., Information Engineering, Englewood Cliffs, NJ: Prentice Hall, 1989
OMG, The Object Management Group, OMG Unified Modeling Language Speceification, V2.5.1, Dec 2017, https://www.omg.org/spec/UML/2.5.1/, [Retrieved 2022/02]
Wiegers, K. E., MORE ABOUT SOFTWARE REQUIREMENTS : Thorny Issues and Practical Advice, Microsoft Press, 2006
Yourdon, E., Modern Structured Analysis, Englewood Cliffs, NJ: Yourdon Press, 1989