English  |  正體中文  |  简体中文  |  Items with full text/Total items : 21921/27947 (78%)
Visitors : 4201322      Online Users : 1028
RC Version 6.0 © Powered By DSPACE, MIT. Enhanced by NTU Library IR team.
Scope Tips:
  • please add "double quotation mark" for query phrases to get precise results
  • please goto advance search for comprehansive author search
  • Adv. Search
    HomeLoginUploadHelpAboutAdminister Goto mobile version


    Please use this identifier to cite or link to this item: http://140.128.103.80:8080/handle/310901/2471


    Title: 以模型為基礎之物件導向需求工程
    Other Titles: A Model-based Object-oriented Approach to Requirement Engineering
    Authors: 詹正吉
    Chan, Cheng-Chi
    Contributors: 朱正忠
    Chu, Cheng-Chung William
    東海大學資訊工程學系
    Keywords: 需求工程;軟體模型;物件導向
    Object-oriented;requirement engineering;software model
    Date: 2007
    Issue Date: 2011-03-18T01:07:24Z (UTC)
    Abstract: 大部分需求文件都用模糊的自然語言以及不精確的格式來描述,如果要把這種需求文件轉換成軟體開發中的物件導向分析以及物件導向設計階段所需的文件時,將會需要投入更多的成本,而且還有不一致的狀況產生。為了解決這個問題,在這篇論文當中,我們提出以模型為基礎之物件導向需求工程,一個新的需求模型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.
    Appears in Collections:[資訊工程學系所] 碩士論文

    Files in This Item:

    File Description SizeFormat
    095THU00394003-001.pdf829KbAdobe PDF320View/Open
    095THU00394003-002.pdf829KbAdobe PDF178View/Open


    All items in THUIR are protected by copyright, with all rights reserved.


    本網站之東海大學機構典藏數位內容,無償提供學術研究與公眾教育等公益性使用,惟仍請適度,合理使用本網站之內容,以尊重著作權人之權益。商業上之利用,則請先取得著作權人之授權。

    DSpace Software Copyright © 2002-2004  MIT &  Hewlett-Packard  /   Enhanced by   NTU Library IR team Copyright ©   - Feedback