為了因應目前瞬息萬變的市場，各個產業不免要為各種經營模式進行不斷的檢討及改善，且創意不斷的新興產業、令人眼花撩亂的新式產品、促銷手法，都在在顯示現今大環境變化的快速。因此，傳統的套裝軟體，已無法因應日益擴大的企業功能及隨時變化的企業模式，亦無法令一般企業滿足其功能需求。套裝軟體失去優勢後，專案系統就成為企業的主要倚靠對象，而對資訊單位而言，如何有效又快速地完成每一個專案系統，也已成為刻不容緩的課題。
因此為了達到此快速反應的目的，應該要有彈性的資訊系統以便適應企業多變的資訊需求。在資訊系統開發、維護中，資訊系統最常被修改的部分是系統程序。絕大部分的系統開發工具中，在系統程序的部分，僅僅只做到文件的功能，程式碼的部分還是得靠程式設計師在一堆如文字般的程式碼中來作找尋需要修改的部分，這是很困難且浪費時間的，也因此耽誤了資訊系統開發的時效。為了能快速完成專案系統，可以求助經驗豐富、技術優良之技術人員，亦可以利用前端開發工具配合後端開發工具，有效地完成專案系統開發工程。
所以，本研究提出一個建立此種開發工具的系統架構，在此架構下，使用了圖形化的企業程序表達方式來表達資訊系統的系統程序（及資訊系統的運作流程），以使得開發者與資訊系統使用者可以有充分溝通，並且也使用傳統的表單式設計畫面來讓開發者設定資訊系統的系統程序，最後，提供了自動化程序的機制來自動將所設定的系統程序實際地運作起來。
為了驗證本研究所提出的系統架構之可行性，本研究使用了由 肯美資訊所發展出來的XUPPER 來作為執行此系統架構中圖形化的企業程序表達介面與設定系統程序表單畫面的技術，以及使用由美商商渠所發展出來 cEAP BPM來作為執行此系統架構中自動將所設定的系統程序實際地轉換成系統物件。最後，本研究會以退貨授權系統的系統程序為例，來套用兩個開發工具的操作方式，讓大家更容易瞭解此開發工具。

In order to face the ever challenge marketing that changes every minute, all industries can not void to examine their biz model and aim for improvement continuously. Adding the factor that the innovative new biz is blooming everywhere, the variety of new products and attractive promotion package, it obviously shows the speed of the dynamic changing biz environment. Thus, traditional software package can not satisfy enterprise functionality needs and the dynamic changing enterprise model. Neither can it meet the functional needs of any organization. Ever since those software packages lose their competitive edge, project management system play an important roles that enterprise can rely on. For IT department, it is even more challenge and crucial as how to complete each IT project more efficiently and effectively.
On the purpose of rapid reaction, it should have a flexible information system so that it could accommodate to the changeable information requirements for business. It modifies mostly in System Procedure section in the Information System Developing or Maintenance. In the majority of System Developing Tools, it only has Documenting function in the System Procedure section. The most difficult section is the Programming Codes. It also wastes time when programmer has to search for the section which needs to be modified in a pile of programming codes. Hence, it usually delays the timing for Information System Developing. For expediting IT projects, it can rely on experienced and professional technical people. Or even more effectively, it can make the most of the Upper CASE tool along with the lower CASE tool to effectively completed the development life cycle.
Therefore, we bring up a system architecture to establish this developing tool. We use the graphic business procedure to express the System Procedure (and the Information Operation Procedure) of Information System under this architecture, so that the developer and the user of Information System can communicate adequately. Also, it uses the traditional sheet frame, and then the developer can setup the System Procedure. Finally, it provides the Automation Mechanism to run the System Procedure practically and automatically.
To prove the feasibility of the proposed system architecture, this research adopt the XUPPER technology developed by KenSys Information Cop. to execute the system architecture of enterprise processes which is represented by GUI diagram, and also to setup the system design form screen. Moreover, cEAP BPM develpped by TBCommerce Technology Inc. is used to perform the transformation of system procedure to system objects automatically in this architecture. Finally, to show how easily use the development tools are, RMA process steps is taken as the case study to prove the procedure by adopting these 2 development tools and operations.

一. 中文部分
1. 林仁常，現代軟體工程導論，松岡電腦圖書資料股份有限公司，1997。
2. 賴蘊真， “以企業流程分析為導向之系統分析方法—結合 IDEF3 與 Use Case”， 國立中山大學資訊管理研究所碩士論文， 1998。
3. 張志強， “流程管理技術手冊”， 中國生產力中心， 1992。
4. 吳仁和、林信惠，系統分析與設計，智勝，台北，2002。
5. 包東意，物件導向分析與設計-方法導引，松岡電腦圖書資料股份有 限公司，1996。

二. 英文部分
T. H. Davenport and J. E. Short, The New Industrial Engineering: Information Technology and Business Process Redesign, Sloan Management Review, 1990 Summer 11-27.
B. Curtis, M. I. Kellner and J. Over, Process Modeling, Communication of the ACM, Vol.33, No.9, 75-90. Sep. 1992.
K. Liu, T. Ong, “A Modelling Approach for Handling Business Rules and Exceptions,” The Computer Journal, Vol. 42, No. 3, 1999, 221-231.
T. Gale and J. Eldred, “Getting Results with the Object-Oriented Enterprise Model,” SIGS Books, Cambridge, 1996.
J. Rumbaugh, “Models through the development process”, J. Object-Oriented Programming, 10, 1997, 5-8.
S. Wang, “OO Modeling of Business Processes,” Information Systems Management, Spring 1994.
T. Gale and J. Eldred, “Getting Results with the Object-Oriented Enterprise Model,” SIGS Books, Cambridge, 1996.
R.J. Mayer et al., “Information Integration for Concurrent Engineering (IICE) IDEF3 Process Description Capture Method Report”, pp.4, 1995. (1995b) (http://www.idef.com/idef3)。
E.Yourdon, K. Whitehead, J. Thomann, K. Oppel, P. Neverman, “Mainstream Objects An Analysis and Design Approach For Business,” 1995.
J. Papows, “Enterprise.com : Market Leadership in the Information Age,” Perseus Books, Reading, MA, 1998
W. Applehan, A. Globe, and G. Laugero, “Managing Knowledge: A Practical Web-Based Approach”, Addison Wesley, 1999
I. Jacobson, S. Bylund, “Intelligent Agents Assisting Software Developers”, Jaczone AB, 2002
J. Rumbaugh, I. Jacobson, and G.Booch, “The Unified Modeling Language Reference Manual”, Addison Wesley, Reading, Massachusetts, 1999.
G. Booch, J. Rumbaugh and I. Jacobson, “The Unified Modeling Language for Object - Oriented Development Documentation Set Version 0.9 Addendum,” Rational Software Corporation,1996.
G. Booch, J. Rumbaugh, and I. Jacobson, “Unified Modeling Language User Guide”, Addison Wesley, 1998
J. Rumbaugh, I. Jacobson, and G. Booch, “The Unified Software Development Process”, Addison Wesley, Reading, Massachusetts, 1999.
R. S. Pressman, “Software Engineering: A Practitioner’s Approach, Third Edition, McGraw-Hill, New York, 1991.
I. Sommerville, “Software Engineering”, Addison Wesley, Reading, Massachusetts,1996.
D. F. D’Souza, A. C. Wills, “Catalysis: Objects, Frameworks, and Components in UML”, Addison-Wesley, Boston, 1999
D. F. D’Souza, A. C. Wills, “Objects Components and Frameworks with UML: The Catalysis Approach,” Addison Wesley, Reading, Massachusetts, 1998.
P. Stevens, R.Pooley, “Using UML: Software Engineering with Objects and Components,” Addison Wesley, Reading, Massachusetts, 2000.
R.Veryad, “SCIPIO: Aims, Principles and Structure,” SCIPIO Consortium, 1998.
S. D. Lee, Y. J. Yang, E. S.Cho, S. D. Kim, and S. Y. Rhew, “COMO: A UML Based Component Development Methodology,” in Proceeding of the 6th Asia Pacific Software Engineering Conference, Takamatsu, Japan, 1999.
R. Ganesan, S. Sengupta, “O2BC: A Technique for the Design of Component-Based Applications,” in Proceedings of the 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems, 2001.
R. Veryard, “SCIPIO: Aims, Principles and Structure ”, SCIPIO Consortium, April 1998
R. Veryard, “SCIPIO: Effe ctive management of component-based system project”, SCIPIO Consortium, November 1998
J. Chessman, J. Daniels, “UML Components”, Addison-Wesley, Boston, 2001
R. Ganesan, S. Sengupta, “O2BC: a Technique for the Design of Component-Based Applications ”, Proc. 39th International Conference and Exhibition on Technology of Object-Oriented Languages and Systems, Santa Barbara, USA,2001