以模型驅動架構（Model Driven Architecture，MDA）（詳見2.1節）為基礎，配合統一塑模語言（Unified Modeling Language，UML）（詳見2.2節）的開發過程中，僅是使用統一塑模語言中所提供的各種模型來輔助開發軟體，往往會有許多資訊無法藉由模型呈現。然而這些遺漏的資訊在最後撰寫程式碼的時候卻佔有很大的重要性。而在統一塑模語言中利用物件限制語言（Object Constraint Language，OCL）（詳見2.3節）幫助系統開發人員在需求分析過程中，將客戶所要求的資訊能更詳細並精確的加入到原先的UML圖形中，使分析階段與設計階段的開發人員能接收並對需求有更深入的理解。
本論文提供一個有系統的分析方法以透過分析使用個案（use case）和類別圖（class diagram），並且將各式需求的描述和限制轉換成OCL的表示式。在分析每個使用個案描述的過程中，輔以類別圖來觀察該案例中各屬性（attribute）的變化以及使用的操作（operation），可以得知針對屬性的限制和操作的實際運作過程，而將限制及操作以OCL描述並加入類別圖中，使類別圖更完整。且此OCL描述亦可利用現有的電腦輔助開發工具將其轉換成程式原始碼，讓程式撰寫人員在修改和補充之後得到最終程式原始碼。

In process of developing that is based on Model Driven Architecture（MDA）and cooperated with Unified Modeling Language（UML）, the UML models are used to facilitate development of software. However, many information always be missed in developing process. Unfortunately the missed information usually is important on implementation of system. Besides, Object Constraint Language（OCL）facilitates the developers to add the information into UML diagrams more detailed and accurately. This results in that the other developers understand the requirements more completely.
Hence, this study provides a systematic approach to analyze the use case description and class diagram. And then, the description and constraint of the requirement is transformed into OCL. In process of analyzing each use case description, we can observe the constraint on some attributes and the practiced process about the operations, and then use OCL to express them. Those OCL expressions can be transformed into source code by many Computer Aided Software Engineering（CASE） tools , so the developer can no longer write all the programs by themselves.

[1] 王傑民(民90)。「UML 分析資訊系統以建構再使用軟體元件之研究與製作─以鞋業B2B系統為例」。國立台北科技大學生產系統工程與管理研究所碩士論文。
[2] 田林一(民93)。「MDA入門必讀—MDA架構詳細介紹」，北京火龍果軟件工程技術中心。
[3] 簡瑞隆(民94)。「MDA：類別轉使用者介面之研究」,國立中山大學資管系碩士論文。
[4] Bernd Oestereich.(2002).Developing Software With UML.鄧文彥、陳昶宏(譯)。UML 軟體發展實務。台北市：台灣培生教育。
[5] Martin Fowler.(2005).UML Distilled Third Edition. 趙光正(譯)。UML 精華第三版標準物件模型語言。台北市：台灣培生教育。
[6] Alhir, S. S.(2003).Understanding the Model Driven Architecture (MDA).Methods &Tools, Fall 2003, pp.17-24.
[7] B. Roussev,(2002) "The Value Added Invariant: A Newtonian Approach for Generating Class Diagrams from a Use Case Model," WITUML, 16th European Conference on Object- Oriented Programming ECOOP 2002, Malaga, Spain.
[8] B.Roussev,(2002)“Generating OCL Specifications and Class diagrams from Use Cases：A Newtonian Approach,” 36th Hawaii International Conference on System Sciences,2002.
[9] Rumbaugh, J., Blaha M., Premerlani, W., Eddy, F. & Lorensen,W.(1991).Object-Oriented Modeling and Design, Englewood Cliffs,NJ:Prentice-Hall International,1991.
[10] The Object Management Group. MDA Guide Version 1.0.1, 2003,from http://www.omg.org/cgi-bin/doc?omg/03-06-01
[11] The Object Management Group. UML 2.0 OCL Specification,2003,from http://www.omg.org/cgi-bin/doc?ad/03-01-07.pdf
[12] Warmer, J., & Kleppe,A.(2003).The Object Constraint Language：Second Edition-Getting Your Models Ready for MDA. Addison-Wesley, Boston, 2003.
[13] "BABES-BOLYAI" University Computer Science Research Laboratory. Object Constraint Language Environment 2.0.4,2005, from http://lci.cs.ubbcluj.ro/ocle/index.htm