| Abstract: | 物件管理組織(OMG)提出模型驅動架構已有一段時間，使得學術及產業上的軟體開發多處利用模型來處理物件與流程的設計，導入此架構後的軟體系統能具備獨立的特性，將使用者的行為與軟體程式碼架構區分開來，於是能改善專案的複雜度管理，妥善處理日漸提高的軟體抽象化程度。另外，在軟體的生命週期中，需求階段裡主要是進行需求訪談及定義需求的工作，這些工作因為專案關係人並非具備軟體專業知識，造成透過自然語言的描述常模糊不清、不一致，使需求管理發生困難，同時，再加上隨時可能的變更，使得訂定規格所帶來的效益減低。 從以上兩方面，本研究期望藉由需求模型化後，能讓各個需求具備獨立的特性，也同時易於分析與統一格式，再透過實作之編輯器，建立需求輸入的介面，讓使用者能利用清單及按鈕等介面方便地撰寫完整的需求，並將資料整理成一份文件記錄。近年來，多核心嵌入式系統的發展迅速，在企業界及學術上都有許多的研究，是一重要的研究議題，因此，本研究也探討如何輔助開發多核心的軟硬體需求，利用預先定義的屬性欄位來處理各類需求，使得分類與辨識的工作更容易，同時，透過參考概要的輔助，使塑模圖形能附帶多核心嵌入式系統的屬性，以輔助後續開發。最後，以上的工作將使整個需求階段達成良好的輔助。
Object Management Group (OMG) has introduced Model-Driven Architecture for a while; this made many software adopted models to handle designs for objects and processes. These software systems then could have an independent feature, which separates the behavior of user and software codes architecture, and thus it can improve the complexity management of project and take good charge of the daily increasing software visiualization level. Besides, in software life cycle, the main tasks in requirement phase are requirement interview and requirements definition. In these tasks, because stakeholders didn't have professional knowledge about computer software, the statements about requirements described by natural lanyguage are often ambiguous and inconsistent, and thus bring difficulty to requirement management. Moreover, with possible requirement changes at any time, the benefits from defining specifications lost. To the two aspects stated above, this research was expected to make every requirements have independent features and make analysis easier by requirement modeling. Further, construct the interface for requirement inputs by this implementation, and then let users use lists and buttons easily describe complete requirements, and arrange the data to be a document record. Recently, multi-core embedded system trend was widely spread, and there are many research in both enterprise area and academic community which shows its importance. Therefore, this research also study about how to assist the development of HW/SW requirements of multi-core ES. We use pre-defined attributes to handle all different kinds of requirements in order to make the work of classification and recognition easier. Further, by the assistant from profile, we can add multi-core ES properties to modeling diagrams and then support following development. Finally, the work stated above would make requirement phase achieve good support. |
