文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > METHODOLOGICAL APPROACH FOR DEVELOPING A KMS A CASE STUDY
侵权投诉

METHODOLOGICAL APPROACH FOR DEVELOPING A KMS A CASE STUDY

This article describes the construction of a Knowledge Management System (KMS) by applying fundamental concepts and principles of Software Engineering, such as process, models, methodology, technology and architectures, among others. They are applied to th

e. Complementary specification. f. Identifying domain objects. g. Preparing the object model.

2. a. Identifying the actors. b. Icases.

c. Preparing the use case model d. Selecting the use cases. e. Benchmarking.

f. Establishing the metrics.

3. Preparing the plan for the Elaboration

phase.

4. plan.

5. Identifying risks.

Table 6. Iteration plan for the Inception

phase These activities seek to achieve a common understanding of the business and establish the critical KM use cases with which the process will be started. Five critical use cases were chosen from the results of this phase and an operational goal was set for the development process, as well as the metrics for ensuring its success. After the Inception phase the use cases selected were redesigned in order to obtain a prototype of a beta version of the KMS and then propose architecture for the prototype developed. This was done during the Elaboration phase in which the activities listed in Table 7 were involved.

ELABORATION PHASE

1. Forward Engineering of the new KM

processes a. Identifying actors b. Identifying use cases

c. Preparing the new use case model

d. Preparing the ideal object model e. Preparing the real object model

f. g. Model of KMS use cases h. Prototype of the KMS

i. Development of the Architecture j. Selection of tools

2. Preparing the Construction phase plan. 3. plan.

4. Reconsideration of risks.

Table 7. Iteration plan for the

Elaboration phase Note that the main activity in this phase consists of generating new processes from the existing ones, with the support provided by IT. This phase could therefore lead to new use cases or change the former ones.

A series of twelve use cases was one of the results of this phase, they were: evaluation and selection of technology, project management, selection and planning of training, virtual meetings, search and retrieval of data, information and knowledge, exchange with internal and external sources, support for users, updating of the knowledge base, discussion, updating of data and information, interaction with suppliers and, evaluation and selection of candidates.

These twelve use cases represent the redesign of the use cases selected in the previous phase (Figure 2). These use cases fall within the following areas: technological acquisition, project management, organizational memory, internal learning and external learning.

上一页第14页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email