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.
theory triangulation, & methodological triangulation...for developing ideas for future study (not for ... – 8% Research approach or methodology (2-5 ...
a methodological challenge.1 Previous studies in ...approach for exploring and collecting terms used ...In developing professional terminologies, there would...
The methodological literature covers the topic ...vehicle for generalizing a case study’s results....Developing a formal research design 3. Using ...
The case study is not actually a data-gathering...a methodological approach that incorporates a number...questions and assist in developing a theoretical ...
The second reason is purely for newly developing methodology; human secretory...In addition, this approach has several methodological advantages, including the...
Services—A Case Study in Northeastern China_工学...t analysis as the methodological approach. Turner ...higher precipitation than the developing countries. ...
profile for interaction design the Wisdom approach...interactive system by small software developing ...methodological background because it is our belief ...
An important methodological limitation of the ...developing LBP as a symptom being explained by ...generating research approach for conditions such as...
research methodological level the deduction ...Applying GUPRO to GEOS – A Case Study. 1/...Towards a Logical Approach for Soccer Agents ...
热门文档