Eigenschappen
| Context | Expertise Management Method (EMM) |
|---|---|
| prefLabel | |
| altLabel | |
| hiddenLabel | |
| inScheme | |
| subject | |
| broader | EMontPatronen |
| narrower | |
| partOf | |
| association | |
| related | |
| creator |
De View-Navigation (VN) pagina's.
Er zijn geen VN pagina's gelinkt.
Description
PQR is an extremely important part of the Expertise Management Ontology, as mentioned before: It’s considered to be the working horse of the EMont. The PQR pattern is widely used in the EMont and it can be used in multiple different situations due to the way it has been set up. Using the PQR method will generate numerous different approaches to reach a certain result. In some contexts it’s better to choose one of those actions, but other times it might be better to execute all the actions sequentially.
This is where the major distinction in PQR implementations comes in; the freedom of getting to choose which action is the most appropriate is labeled as the ‘Degree of freedom’, whilst executing the activities one after another is called ‘Sequencing of activities’. The results of a PQR implementation is a ‘use case map’, which is essentially a timeline which denotes the activities that need to take place to reach a certain goal. There are multiple types of activities that are used in a concept map, the different types are:
Sequential execution of activities simply means that activities are completed one after another; an activity following another activity cannot be started until the goal of the previous activity has been completed. Sequential activities are denoted as such:
<<insert image>>
Conditional execution means that a certain condition has to be met before the activity can start. For example it could be that an activity is ‘Build a house’, but with the condition that half a million euros have been saved up first. The activity ‘Build a house’ cannot start until the half a million euros have been saved up. In the EMont, this is visualized like this:
<<insert image>>
Parallel activities are executed alongside each other; this means that both of the activities will be executed at the same time, running parallel. In some cases an activity can have already started, but require a certain product before the activity can actually finish, this means that the activity has to wait until another activity can provide the needed product. This is known as the ‘wait’ activity. Parallel activities are shown like this:
<<insert image>>
Alternative visualisation
