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
Project Closure   Project closure is the last stage of the Project Life Cycle. The beginning of the Project Closure Phase is analysed by the completion of all project objectives

Explain about the term performance management systems in brief. Performance management systems: Measurement processes of frequently assessing a projects progress in oppos

Risk Matrix Terminology  It is a term where table used in risk analysis in which rows show the risks and columns show their likelihood (probability) of occurrence and their imp

It is essential that you study the list below to ensure that you understand the terminology used in assignment and examination questions. The successful outcome of your assessment

Question: (i) What are the different measures taken by Government so far to address problems of redundancy in public sector organisations in Mauritius? (ii) What reasonable

Quantitative layout analysis - Trial and Error Method Here we use simple travel chart and graphical approach to reduce to minimize nonadjacent flows by centrally locating the

What skills are helpful when working in Project and Programme support office? The skills which are most helpful probably include in Project and Programme support office: a.

#questionhi i sent my assignment yesterday but havenot recieved any reply yet ..


PERIL Database   The Project Experience Risk Information Library (PERIL) is a database, which provides a basis for the analysis of high-tech project risk.  A project can have