開發企業資訊平台往往開發週期過長,導致專案成本增加,讓專案的風險也提高不少。專案週期過長,規格到後期常常會出現落差。修正落差所帶來的時間,也增加了專案的成本。除此之外,也間接增加了人事成本。要如何在縮短開發時間,降低專案風險。在這樣前題下,如何快速開發兼具溝通的零誤差的資訊平台,正是所被關心的議題。 透過MDA的方式就能很輕易的快速開發資訊平台 。利用可視的模型定義系統,再透過轉化將不同的模型轉換成對應的檔案或是程式碼。如此一來專案就可由模型快速的產生出來。採用MDA的方式開發,一個完善的整合開發工具更是少不了,如何讓工具符合MDA的精神也是關注的議題。而本文研究在於提供工具,透過工具可以很輕易完成模型的定義,藉由拖曳的方式,以及口語化的script的撰寫,來完成轉化系統。而不僅僅在於文字上的定義。除此之外工具的使用門檻也不能過高,以此工具的使用度才會提高,不會衍生其他更高的成本。 程式碼由模型轉化出來。程式設計師所要撰寫的程式碼大幅降低,也間接減少除錯的範圍,專案的品質也得以維護,不會參差不齊。利用一系列的UML模型來描述系統,使系統更具可視性。對於日後系統的維護與交接帶來不少幫助。透過MDA的方式,不僅讓系統能被快速開發,也帶來更多好處。在本文最後,也討論到採用MDA的方式開發系統所帶來的優勢與優點。
There is usually spending too much time to develop enterprise information platform, so that the project cost was increased, and the risk of project was raised as well. The cycle of project is long, thus the embryonic specification usually differenced to the subsequent specification, and the time of fixed bugs will increase project costs also. How to develop information platform which is no discrepancy of communication quickly is the issue we concerned. Through MDA, developing information platform will be more easily and quickly. Define systems using visible models and transfer different models to its matched files or codes. And therefore the project can be generated quickly by the models. A complete integrated development environment is important in using MDA. How to let the tool be matched to the tenet of MDA is also a concerned issue. The code of system was transformed by models. The codes via programmer will be decreased substantially and also consequential decrease the range of debug. The quality of project will be guaranteed and accordant. To describe system by a series of UML models will let the system be more visible. It will be more helpful to maintain and to associate system afterward. Through the way of MDA, it is not only makes system be quickly developed, but also bring more advantages.