一九九三年Michael Hammer與James Champy，以企業流程再造的觀念，全面提升企業績效而掀起了企業經營者對於企業流程再造與企業流程管理的高度重視。企業流程管理提供了一個以端對端為主的企業流程整合系統，並且解決企業資源規劃之問題。

企業架構管理則是將企業之靜態的結構面規劃出來，並將企業動態的流程面緊緊依附在結構面上，使靜態的結構面與動態的流程面整而合一之模型。藉由此模型企業管理者能夠將企業所有面象看得清楚，並且易於分析、控管相關資訊技術與系統整合。透過企業架構管理軟體，我們可以了解到企業架構相較於企業流程方面之整合之下更突顯其重要性，而企業架構管理之優勢在於使企業之結構面與企業之流程面整合為一。

研究的目的以科學邏輯法則來建構一個企業架構管理軟體之模型，並以企業流程管理為文獻探討之議題。研究中利用Backus-Naur Form語法與圖示語法為兩種建構企業架構管理模型之方法，並以三個步驟來進行建模 (一)將企業中的結構元素與操作建構出來。 (二)再經由結構元素間操作，導出企業的流程面。(三)最後將企業之結構面與企業流程面整合為一。

研究範例以某證券公司之企業組織，利用架構工具，建構一個企業架構管理之證券交易平台系統模型。總結中，比較企業流程管理與企業架構管理兩者之優缺點，我們發現企業架構管理軟體更能使企業之管理者易於控管相關之資訊技術與系統整合。根據上述研究結論，可以發現本研究的貢獻，同時也可以提供企業經營者或系統管理者諸多建議來提供建構企業架構管理軟體時之參考。

In 1993, Michael Hammer and James Champy advanced the Business Process Reengineering theory, which had promoted the enterprises overall achievement, therefore, raises the Enterprise managers to think carefully of the Business Process Reengineering and the Business Process Management (BPM) software. The BPM provides a consolidated end-to-end perspective of all the processes within the enterprise, and to resolve the problem of the Enterprise Resource Planning system.

The Business Architecture Management (BAM) software is to map out the business structure of the enterprise, and make the business process integrated with the business structure closely, the purpose is to build business structure and business process in one unity. This model will support the enterprise managers to see, analyze and control the information technology and system integrations. Via the BAM model, we realize that the Business Architecture contains more views than Business Process. Therefore, the advantage of the BAM software is to have the business structure integrated with business process. In contrast, the disadvantage of the BPM software is to separate the business structure from the business process.

The study is based on the scientific logic principle and to create a model of the BAM software. Using the Backus-Naur Form grammar and the graphical language, we define the BAM software model, and list three steps: the first step is to construct structure elements and operations which from the business structure. The second step is to derive the business process from the business structure. The third step is to integrate the business structure with and the business process.

An example of Securities Transaction Platform software is developed via the BAM model. In this study, we also compare the BPM with BAM. We conclude that the BAM software will assist the enterprise managers to analyze and control the information technology and system integrations easily. Beside the above conclusion, this study also provides many useful references and suggestions to aid entrepreneurs and system managers to create BAM software.

摘要 i
Abstract ii
致謝詞 iv
目錄 v
圖目錄 vii
表目錄 ix
1. 緒論 1
1.1 研究背景與動機 1
1.2研究目的 3
1.3 研究步驟與方法 4
1.4 重要名詞解釋 5
2. 文獻探討 6
2.1企業流程管理之相關理論 6
2.2 企業流程管理之模型 25
2.3企業架構管理之概論 36
2.4企業架構軟體之模型 43
3 企業架構管理建模之方法與步驟 45
3.1 企業架構管理建模之方法 45
3.2企業架構管理之工具軟體建構之步驟 47
4企業架構管理模型範例-以證劵業為例 55
4.1證劵業簡介 55
4.2證券市場概況 58
4.3 證券業之組織結構 60
4.4 證券公司建模範例 61
5. 企業架構管理之總結 73
5.1 企業架構管理和企業流程管理樹狀圖之比較 73
5.2以證券交易平台系統模型圖比較 74
5.3 企業架構管理與企業流程管理之區別 75
5.4企業軟體開發之成敗關鍵因素 76
5.5企業流程整合之成敗關鍵因素 78
5.6企業架構管理之優點 83
6. 結論與建議 84
6.1研究結論 84
6.2 後續研究 84
參考文獻 85
中文部分 85
英文部份 86

參考文獻
中文部分
[1]Hammer, M. and J. Champy（民83）。楊幼蘭譯，「改造企業─再生策略的藍本」，牛頓出版社。
[2]司徒達賢等著（民74）。「企業概論」，建華印書有限公司。
[3]司徒達賢。「流程是組織競爭力的重要來源」議題，工商時報，2006年9月1日，取自http://cdnet.stpi.org.tw/techroom/analysis/pat_A062.htm
[4]李仁芳等著（民89）。「企業概論」，華泰文化事業公司。
[5]張緯良、陳育亮（民91）。「ERP成敗關鍵-企業流程再造」，資訊與電腦，pp.14-16。
[6]陳春山（民86年12月、87年1月）。「我國證券市場之現況、特徵及發展趨勢－證券市場發展對券商業務之影響」，證券櫃檯18、19。
[7]曾煥釗（民91）。「企業資源管理(ERP，ERM)大辭典」，松崗。
[8]葛文怡（民95）。「企業導入BPM系統成功要素之個案討論研究」，東吳大學商學院企業管理學系碩士論文。
[9]楊基載(民95)。BPM 與 SOA的演進與展望(上), iThome企業軟體技術應用專刊, 2006年8月12日，取自http://www.flowring.com/pagelogic/mainpage.jsp
[10]維基百科(民94) 。「商業過程管理」，自由的百科全書，2006年8月10日，取自http://en.wikipedia.org/wiki/Business_Process_Management
[11]劉珍蘭等人 (民90)。「企業導入企業資源規劃(ERP)對組織文化的影響」，私立世新大學資訊管理系, 管理研究方法分組報告 。2006年12月28日，取自http://tx.shu.edu.tw

英文部份
[12]Armour, F.J., Kaisler, S.H . and Liu, S.Y.(1999). A big-picture look at enterprise architectures, IT Professional, no. 35-42.
[13]Booch, G.., Rumbaugh, J. and Jacobson, I. (1999).The Unified Modeling Language User Guide, Addison-Wesley.
[14]BPML, (2002). Business Process Modeling Language, Bpmi.org.
[15]Cummins, Fred A.(2002).Enterprise Integration, Wiley.
[16]Davenport, Thomas & Short, J.(1990, Summer). The New Industrial Engineering: Information Technology and Business Process Redesign, in: Sloan Management Review, pp 11-27.
[17]Davenport, Thomas (1993). Process Innovation: Reengineering work through information technology, Harvard Business School Press, Boston.
[18]Davenport, Thomas (1995).Reengineering - The Fad That Forgot People, Fast Company.
[19]Debevoise, Neilson T (2005).Business Process Management with a Business Rules Approach, Business Knowledge Architects.
[20]Devlin, K. (1991).Logic and Information, Cambridge University Press, New York.
[21]Drucker, Peter (1972).Work and Tools, in: W. Kranzberg and W.H. Davenport (eds), Technology and Culture, New York
[22]Engberg, U. and Nielsen, M. (1986).A calculus of communicating systems with label-passing. Report DAIMI PB-208, Computer Science Department, University of Aarhus, Denmark.
[23]Fische, Layna R.(2005). Future Strategies , Workflow Handbook 2005.
[24]Fowler, Martin (2002).Patterns of Enterprise Application Architecture, Addison-Wesley Professional.
[25]Ghemawat, Pankaj, Collis, David J., Pisano, Gary P. & Rivkin, Jan W.(1999). Strategy and the Business Landscape, Addison-Wesley.
[26]Graham, I.(2000).Object-Oriented Methods: Principles and Practice, Addison-Wesley.
[27]Greenbaum, Joan (1995).Windows on the workplace, Cornerstone.
[28]Guha, S., Kettinger, W. J. and Teng, T. C., (1993, summer).Business Process Reengineering: Building a Comprehensive Methodology, Information Systems Management.
[29]Hammer, Michael (1990, Jul/Aug).Reengineering Work: Don’t automate, obliterate, Harvard Business Review, pp 104-112.
[30]Hammer, Michael and Champy, James (1993). Reengineering the Corporation: A Manifesto for Business Revolution, Harper Business.
[31]Havey, Michael (2004)."Essential Business Processing Modeling", O’Reilly.
[32]Hohpe, G.and Woolf, B.(2004)."Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions Addison-Wesley.
[33]Industry Week (1994). De-engineering the corporation, Industry Week article.
[34]Inmon, Bill (2005).A Brief History of Architecture, Microsoft.
[35]Jensen, Kathleen and Wirth, Niklaus (1974).PASCAL user manual and report, Lecture notes in computer science ; vol. 18., Berlin [etc.] : Springer.
[36]Johansson, Henry J. et.al. (1993), Business Process Reengineering: BreakPoint Strategies for Market Dominance, John Wiley & Sons
[37]Johnson, S.C. (1960).Yacc: Yet Another Compiler Compiler, Computer Science Technical Report #32, Bell Laboratories, Murray Hill, NJ.
[38]Leavitt, H.J. (1965). Applied Organizational Change in Industry: Structural, Technological and Humanistic Approaches, in: James March (ed.), Handbook of Organizations, Rand McNally, Chicago
[39]Lloyd, P. T. L. and Galambos, G. M.(1999). Technical Reference Architectures, IBM Systems Journal 38, No. 1, 51-75
[40]Loyd, Tom (1994).Giants with Feed of Clay, Financial Times, Dec 5 1994, p 8
[41]Marcotty, M. & Ledgard, H. (1986).The World of Programming Languages, Springer-Verlag, Berlin, pages 41 and following.
[42]McDavid, D. W. (1997).Business Language Analysis for Object-Oriented Information Systems, IBM Systems Journal 35, No. 2, 128-150.
[43]McDavid, D. W. (1999). A standard for business architecture description. IBM
[44]Milner, R., Parrow, J. and Walker, D.(1992).A calculus of mobile processes, Parts I and II. Information and Computation, 100, 1, pp 1-77.
[45]Minsky, M. (1985).Society of Mind , Simon & Schuster, New York.
[46]Naur, Peter (ed.), (1960).Revised Report on the Algorithmic Language ALGOL 60., Communications of the ACM, Vol. 3 No.5, pp. 299-314.
[47]Plachy, E. C.and Hausler, P. A. (1999).Enterprise Solutions Structure, IBM Systems Journal 38, No. 1, 4-11.
[48]Reston,V. A. (1994).Technical Architecture Framework For Information Management (TAFIM) Volumes 1 – 8, Version 2.0, DISA Center for Architecture.
[49]Smith, Howard and Fingar, Peter (2002).Excerpts from Business Process Management: The Third Wave , ISBN 0-929652-33-9 Off-press November, Meghan-Kiffer Press.
[50]Smith, Howard and Fingar, Peter (2002).Business Process Management：The Third Wave[M] Tampa：Meghan—Kiffer Press f91.
[51]Taylor (1911). Frederick, The principles of scientific management, Harper & Row, New York
[52]Thompson, James D. (1969). Organizations in Action, MacGraw-Hill, New York
[53]Wirth, Niklaus (1982).Programming in Modula-2, Berlin, Heidelberg: Springer.
[54]Youngs, R. D., Spaas, Redmond-Pyle, P. and Kahan, E. (1999).A Standard for Architecture Description, IBM Systems Journal 38, No. 1, 32-50