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
Question: (a) A famous man once said: "If you do not know where you are going, how will you know how you will reach your destination". This sentence captures the importance of

The WAM Organisation is one of the very successful supermarket chains within its own country. Reputation for innovation of it is unparalleled into its own country along with the wi

What types of errors disclosed in Trial Balance? A Trial Balance discloses the given types of errors as illustrated follows: a. An item posted two times. b. A mistake int

Explain about the Economic Order Quantity and Total Cost with diagram. Economic Order Quantity and Total Cost: The total of Inventory procurement cost and also inventory carryi

Line Balancing Procedure in Assembly Layout step1: Determine what tasks must be performed to complete one unit of a finished product and the sequence in which the tasks mus

Question: (a) Describe why risk management is a crucial component of project management. (b) Critically show the different responses to risks that should be developed ear

Differences between wbs and product breakdown structure, Project Management

This project requires you to choose an organisation of your own choice and discuss on the following with respect to your chosen organisation: External Environment Mega

Disadvantages of Three Dimensional Models They require more storage area, They are comparatively expensive than templates, It is difficult to take them to sh

Risk Breakdown Structure for a Project  Risk Breakdown Structure (RBS) is a hierarchical list of risks, which standardises the department's personnel resources that help in pla