KNOWLEDGE MANAGEMENT SYSTEMS LIFE CYCLE

Get Started. It's Free
or sign up with your email address
Rocket clouds
KNOWLEDGE MANAGEMENT SYSTEMS LIFE CYCLE by Mind Map: KNOWLEDGE MANAGEMENT SYSTEMS LIFE CYCLE

1. Motivation

1.1. For any task, from as simple as planning a trip, working on a maths problem The process involves a number of steps until you come up with a solution.,

1.2. In developing a large software system used in industry, the process also follows a number of defined steps which are accepted as best practices by practitioners

1.3. -How many programming courses have you taken either here or elsewhere before? -What would be the steps you would take in completing a programming assignment

1.4. read the problem statement mentally think about how to solve it select a programming language (if decided, select what kind of data structures) translate into program code compile, run and test modify if program doesn't function as expected Satisfied!!

2. CHALLENGES IN BUILDING KM SYSTEMS

2.1. Culture:

2.1.1. getting people to share knowledge

2.2. Knowledge evaluation

2.2.1. assessing the worth of knowledge across the organization

2.3. Knowledge processing

2.3.1. documenting how decisions are reached

2.4. Knowledge implementation

2.4.1. organizing knowledge

3. Users Versus Experts

4. Stages of KMSLC

4.1. (1) Evaluate Existing Infrastructure

4.1.1. System justifications

4.1.1.1. What knowledge will be lost through retirement, transfer, or departure to other firms?

4.1.1.2. Is the proposed KM system needed in several locations?

4.1.1.3. Are experts available and willing to help in building a KM system?

4.1.1.4. Does the problem in question require years of experience and tacit reasoning to solve?

4.1.2. The Scope Factor

4.1.2.1. Consider breadth and depth of the project within financial, human resource, and operational constraints

4.1.2.2. Project must be completed quickly enough for users to foresee its benefits

4.1.2.3. Check to see how current technology will match technical requirements of the proposed KM system

4.1.3. Role of Strategic Planning

4.1.3.1. Risky to plunge into a KMS without strategy

4.1.3.2. Knowledge developer should consider:

4.1.3.2.1. Vision

4.1.3.2.2. Resources

4.1.3.2.3. Culture

4.2. (2) Form the KM Team

4.2.1. Identify the key stakeholders of the prospective KM system.

4.2.2. Team success depends on: Ability of team members Team size Complexity of the project Leadership and team motivation

4.3. (3) Knowledge Capture

4.3.1. Explicit knowledge captured in repositories from various media

4.3.2. Tacit knowledge captured from company experts using various tools and methodologies

4.3.3. Knowledge developers capture knowledge from experts in order to build the knowledge base

4.3.4. Selecting an Expert

4.3.4.1. How does one know the expert is in fact an expert?

4.3.4.1.1. What makes someone an expert:

4.3.4.2. How would one know that the expert will stay with the project?

4.3.4.3. What backup should be available in case the project loses the expert?

4.3.4.4. How could we know what is and what is not within the expert’s area of expertise

4.4. (4) Design the KM Blueprint

4.4.1. The KM blueprint addresses several issues

4.4.1.1. Finalize scope of proposed KM system with realized net benefits

4.4.1.2. Decide on required system components

4.4.1.3. Develop the key layers of the KM software architecture to meet company requirements

4.4.1.4. System interoperability and scalability with existing company IT infrastructure

4.5. (5)Testing the KM System

4.5.1. Verification procedure: ensures that the system has the right functions

4.5.2. Validation procedure: ensures that the system has the right output

4.5.3. Validation of KM systems is not foolproof

4.6. (6) Implement the KM System

4.6.1. Converting a new KM system into actual operation: -includes conversion of data or files -also includes user training

4.6.2. Quality assurance is important, which includes checking for: -Reasoning errors -Ambiguity -Incompleteness -False representation (false positive and false negative)

4.7. (7) Manage Change and Rewards Structure

4.7.1. Goal is to minimize resistance to change -Experts -Regular employees (users) -Troublemakers

4.7.2. Resistances via projection, avoidance, or aggression

4.8. (8) Post-system Evaluation

4.8.1. Assess system impact in terms of effects on: -People -Procedures -Performance of the business

4.8.2. Areas of concern: -Quality of decision making -Attitude of end users -Costs of Knowledge processing and update

5. Key Questions

5.1. Has accuracy and timeliness of decision making improved?

5.2. Has KMS caused organizational changes?

5.3. What are users’ reactions towards KMS?

5.4. Has KMS changed the cost of operating the business?

5.5. Have relationships among users affected?

5.6. Does KMS justify the cost of investment?

6. Types (Categorization) of Knowledge

6.1. Shallow (readily recalled) and deep (acquired through years of experience)

6.2. Explicit (already codified) and tacit (embedded in the mind)

6.3. Procedural (repetitive, stepwise) versus Episodical (grouped by episodes)

6.4. Knowledge exist in chunks