Service and Delivery

Knowledge Element: User requirements list

Definition of Knowledge Element:

Know how to construct a user requirements list

A very brief summary of the Knowledge:

Begin with essential features like the budget available, establish what the service is supposed to achieve in use and work out which particular criteria will deliver those requirements. Establish the need for spare capacity and establish the costs.

A summary of expert opinion:

The knowledge named 'User requirements list' is considered to be quite important.
In addition, the knowledge is thought to be slightly difficult to replace, it is learned with a study experience balance, and Less than 6% of the Group are Experts.
It is also quite specialised knowledge, and generally stable knowledge.
See Parameter table below for more detail.

Risk:

This knowledge element has a risk value of 4.81, whilst the average risk for the whole knowledge structure is 4.862. Consult the RISK page for more details.

Knowledge linked by learning dependency:

Postrequisite knowledge implies that User requirements list must be understood before for a person can gain a full understanding of the knowledge listed in the top row of the Linked Knowledge table.

User requirements list has no prerequisite knowledge items and is therefore known as a leaf node. A leaf node is knowledge that has not been investigated further when the map was constructed.

Parameters assigned for User requirements list.

People Involved with User requirements list:

Computed Similarity

The most similar node to User requirements list is Geographical strategy.

The most dissimilar node to User requirements list is System diagnostics.