大部分需求文件都用模糊的自然語言以及不精確的格式來描述,如果要把這種需求文件轉換成軟體開發中的物件導向分析以及物件導向設計階段所需的文件時,將會需要投入更多的成本,而且還有不一致的狀況產生。為了解決這個問題,在這篇論文當中,我們提出以模型為基礎之物件導向需求工程,一個新的需求模型Object-oriented Requirement Model(OORM)可以幫助系統開發者有系統地擷取需求,並且可以讓接下來的分析階段,設計階段使用,而不會有不一致的情況產生。以模型為基礎之物件導向需求工程不但可以增加需求階段的效率,也可以幫助簡化軟體開發流程裡的需求階段轉換到分析、設計階段,進而解決不一致的情況產生,降低開發成本。 Most requirement documents were written in ambiguous natural language which is less formal and imprecise. Without modeling the requirement documents, the knowledge of the requirement is hard to be kept in a way, that can be analyzed and integrated with artifacts in other phases of software life cycle, e.g. UML diagrams in analysis and design phases. Therefore, maintaining the traceability as well as maintained in a consistent in UML in a system. Transforming the requirement documents into well-accepted OO modeling languages of the following analysis and design phases for software development, with expertise and experiences, would be costly and inconsistent prone. In this paper, we propose empirical Model-based Object-oriented Requirement Engineering (MORE) from an empirical viewpoint for software development. An innovative requirement model OORM is presented to systematically assist developers in producing requirement paradigms which can be used consistently in the following phases of analysis, design, and implementation. MORE is to promise not only the efficient requirement development, but also the feasibility of software evolution streamline with the integration of paradigms from all the phases of software lifecycle.