Explain risk knowledgebase and metadata , Project Management

Risk Knowledgebase and Metadata 

When we think of storing risk experience knowledge for our future use in the organisation and make it accessible is to build an automated repository that resides in a shareable database. The figure contains a conceptual entity-relationship  (ER) diagram for such a repository. This diagram represents the things about which we need to know information and shows how they are associated with each other.

While the information modelling community has precise definitions for numerous modelling techniques and their respective diagram conventions, the following definition can be taken out from the illustrations:  

405_Entity relationship diagram.png

Some of the definitions are: 

  • A box represents an entity that is information about a person, place or concept about which information can be given. Example customer and Project entities. 
  • The lines connecting entities, it represents the relationship between two entities. The numbers at each end of the relationships are two-way. Example Customer sponsoring zero or more projects, same way a project is sponsored by a customer.  

The diagram given below should be useful and analysed by business and technical professionals.  So risk knowledgebase can be defined as: 

  • A customer sponsors zero, one or more projects. A project is always sponsored by a customer 
  • A project always has one or more than one risks. A risk is always associated with a project. 
  • A risk is classified by a probability. It can be assigned to multiple risks 
  • A risk exhibits a severity. This can be exhibited by multiple risks 
  • A risk is placed in a timeframe. The same timeframe can be placed on many risks 
  • A risk is linked to a strategy. This strategy can be linked to many risks 
  • A mitigation strategy includes zero or more contingency pans. This plan is included with a mitigation strategy.  

Risk knowledgebase database structure 

This structure is based on database management system such as Microsoft access. A construction of database repository is made in which risk knowledgebase is stored. Figure shows an example of such a database constructed with MS access 2000.  

  • Risk Knowledgebase Tables: There are ten basic tables in the sample risk knowledgebase database shown in the figure. Each enterprise should examine the contents and determine the additional attributes (i.e. database columns) that are required. For example, the customer table contains only a unique identifier and the customer name, certainly more information is requires. The following describes the metadata for each table in the risk knowledge database structure. 
Posted Date: 9/25/2012 7:01:22 AM | Location : United States







Related Discussions:- Explain risk knowledgebase and metadata , Assignment Help, Ask Question on Explain risk knowledgebase and metadata , Get Answer, Expert's Help, Explain risk knowledgebase and metadata Discussions

Write discussion on Explain risk knowledgebase and metadata
Your posts are moderated
Related Questions
Probelm 1: a) Elaborate on the Verma;K(1996) model for effective human resource management and explain its importance in managing projects. b) According to the Verma; K(1996

Question: (a) Consider the following quality goals and provide a way to make the goal more tangible such that it can be easily verified: ?Software should be user friendl

o Are the goals and philosophy of the architecture explained? o Are assumptions and dependencies influencing the architecture identified? o Are architecturally significant re

Give an example of demonstrating a network or critical path by given activity and duration. Activity                      Duration (Wks)                   Preceded by

Question 1: (a) While managing HR projects, explain the different stages that ultimately lead to ‘crisis' in a conflict situation. (b) Despite that fact that conflicts bre

application of differential costing in project

How must be the downward communication from the superior to the subordinate? There formal communication in between subordinate and superior, here the superior sends directions

1. Objective ( Theme ) : Continuous quality improvement at every level at every place and at every stage. 2. Approach :Management involvement and leadership, Empowering s

Analysis The factory has the process for the following:  QC of sampling,  receiving orders,  receiving fabrics and accessories,  checking of fabrics,  drawing,  cutting,  sort

After the data have been collected the researcher turns to the task of analyzing them. The analysis of data requires a number of closely related operations such as esta