Ontology-Based Knowledge Extraction from Application Project Building

• Main Authors: Wu-Kuei Isabel Chi, 戚務奎
• Other Authors: Ruey-Shun Chen
• Format: Others
• Language: zh-TW
• Published: 2007
• Online Access: http://ndltd.ncl.edu.tw/handle/37766594209192072761

碩士 === 國立交通大學 === 管理學院碩士在職專班資訊管理組 === 95 === While starting a new software application project, we usually focus on how to build up a system to solve a specific domain problem and to reply information requirements from customers soon. Leaning from the building process to construct a model for high-quality application delivery and to quickly response to customer for requirements changes is critical successful factor for any application projects. To build up a new application, we construct system architecture and project plan by an experienced domain expert or old-timey system analyst. It is important to reuse and apply the same domain knowledge for information application development. The purpose is to shorten the period to realize what are user needs and prototype it as soon as possible. If we can’t communicate with customers in same domain laguage, it is impossible to establish an application to help user to accomplish their job, which means the project is probably unsuccessful. Setting up a common library to extract knowledge from application project building in a standard pattern is the purpose of this paper. We setup an ontology model trying to mine the core knowledge of application building. The precious experiences and developments from each project, especially sucessful project, should be kept and easy to reach. Two faces of ontology knowledge pattern will be defined in this paper, one is for application project management and another is for software engineering process. We decompose the knowledge from the sme domain application into several ontology units, entiies and attributes, in one standard formula with tree maps. Applying the ontology model defined in this paper for a new application project and we have a conclusion that development cost and requirement cost is lower and user satisfaction is higher than the application without ontology model and the reusefulness is regular in the project process. We just need the old-timey system analyst and the project manager at first time to build a new application, after that, access the library and find out these experiences and learning from it.