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
T raditional forms of organisation Traditional forms of organisations were classified into five types based on the following differentiations. Functional differentiati

Question 1: i) How would you define a project? What are the different types of project that exist (please explain using a model with examples) ii) Enumerate and explain bri

Submit all required artefacts necessary to achieve the ‘Life Cycle Objectives Milestone' (LCOM). These are: A Vision document setting out the business objective and business cas

You are not expected to submit a formal proposal. However, you will be able to access Subject Tutors via HenleyConnect and you may seek feedback from them as to the suitability and

Problem 1: a) What is the role of strategy in project management? b Explain the importance of aligning H.R projects with the organizational strategy. c) What are the impa

Specification is an important quality document for the product because it is here that quality fo the product as a whole is defined in precise technical terms. Although the use

What are the pros and cons of a ‘pure’ project organisation compared along with a project operating into a matrix structure? A ‘pure’ project organisation comprises into itself

Levels of strategy There are three levels of strategy: Corporate strategy is the overall (grand) strategy for the organization as a whole. Business strategy refers to

2JN is a large manufacturing organisation which is structured with a number of supervisors every responsible for their own work production unit. Supervisors report to a team of sen

How is the Performance Appraisal help in operational decision making? Performance Appraisal helps in operational decision making in personnel management gives clues to manageme