在開發軟體系統的生命週期中，軟體系統的需求管理是很重要的一個環節，但同時卻也是最常被忽略的部份。一個好的系統需求管理不僅可以幫助開發人員實作出符合使用者需求的系統，另外在與使用者之間的溝通也扮演了一個重要的角色。最常被用來描述與記錄系統需求的方法則是使用自然語言，然而使用自然語言卻也常常伴隨著許多的人為因素在內，進而造成與使用者之間的溝通不良、錯誤或模稜兩可的需求分析以及不一致的系統需求規格等相關問題。因此，為了避免錯誤的需求分析而導致日後系統開發的困難，適當的需求管理方法與工具便成為不可或缺。需求工程定義了一系列標準化的流程與方法來幫助開發人員有效率建立完整且正確的系統需求，同時也為系統需求管理提供一個良好的基礎。本論文使用系統塑模語言工具來為使用者的系統需求塑模，同時依據需求擷取樣板的資訊來引導使用者提出明確及完整的系統需求，最後再透過模型轉換語言定義的模型轉換規則將系統需求圖自動轉換成其它類型的模型圖。讓開發人員能夠以更便捷的流程與圖形化的界面來達到系統需求的擷取、分析與驗證，以確保所開發的軟體系統可以滿足使用者所提出的系統需求。 The requirement management is a very important link in the life cycle of software system development process, but in the mean time, is often ignored. A good system requirement management can not only help developers to implement the system which conforms to the users’ requirement but also play an important role of communication between developers and users. The most common approach is to describe and record system requirements by using natural language, which may cause several problems such as misunderstandings, imprecision, ambiguity and inconsistency requirement specification. Hence, in order to prevent the difficulties for developing the system by such requirements in the later phase, the proper methods and tools for the requirement management are necessary. The Requirements Engineering (RE) defines a serial standardized procedures and methods to help developers to generate system requirements effectively, completely, and precisely. It also provides a useful fundamental for system requirements management.In this paper, we propose an approach to describe and model users’ system requirements by using SysML system modeling language and according to the requirements elicitation template we can guide the users to provide explicit and complete system requirements. Eventually, we are going to transform requirements diagram to another type of diagrams automatically through model transform rules which defined by ATL model transformation language. Our purpose is to provide a convenient procedure and graphical interface to elicit, analyze, validate and verify system requirements and to ensure that the software system can satisfy users’ needs.
