|
k
|
|||
| Regel 8: | Regel 8: | ||
The [[PQR_formula|PQR formula]] has already been discussed in great detail in another part of the wiki, however, the pattern and how it's visualised is hardly discussed. This page about the [[PQR_formula|PQR]] pattern aims to inform of the way [[PQR_formula|PQR]] is visually structured within the EMont. [[PQR_formula|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_formula|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. |
The [[PQR_formula|PQR formula]] has already been discussed in great detail in another part of the wiki, however, the pattern and how it's visualised is hardly discussed. This page about the [[PQR_formula|PQR]] pattern aims to inform of the way [[PQR_formula|PQR]] is visually structured within the EMont. [[PQR_formula|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_formula|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_formula|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_formula|PQR]] visualisations 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’. |
+ | Using the [[PQR_formula|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_formula|PQR]] visualisations 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’. This means that when a high degree of freedom is present, there will also be lots of actions to choose from, depending on the situation; this might or might not be ideal. When sequencing activities, there is not much room for freedom, the relevant activities will be done in a certain order, no questions asked. The results of a [[PQR_formula|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. Metaphorically speaking, the timeline can be seen as a railroad, at every halt, the train comes to a stop and performs certain activities, which allows the train to move its merry way. Different halts require different activities to take place, therefore there are multiple types of activities that are used in a use case map, the different types are: |
| − | |||
| − | This means that when a high degree of freedom is present, there will also be lots of actions to choose from, depending on the situation; this might or might not be ideal. When sequencing activities, there is not much room for freedom, the relevant activities will be done in a certain order, no questions asked. The results of a [[PQR_formula|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. Metaphorically speaking, the timeline can be seen as a railroad, at every halt, the train comes to a stop and performs certain activities, which allows the train to move its merry way. Different halts require different activities to take place, therefore there are multiple types of activities that are used in a use case map, the different types are: |
||
A '''sequential''' execution of activities means that all activities are done one after another. The next activity can't be started until the previous activity has been completed. In the context of flood protection, it could be the case that a dike has to be heightened, after that has been done, a test can be ran; but the test can't be performed until the dike has been heightened. |
A '''sequential''' execution of activities means that all activities are done one after another. The next activity can't be started until the previous activity has been completed. In the context of flood protection, it could be the case that a dike has to be heightened, after that has been done, a test can be ran; but the test can't be performed until the dike has been heightened. |
||
Versie van 7 mrt 2014 om 11:11
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
The PQR formula has already been discussed in great detail in another part of the wiki, however, the pattern and how it's visualised is hardly discussed. This page about the PQR pattern aims to inform of the way PQR is visually structured within the EMont. 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 visualisations 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’. This means that when a high degree of freedom is present, there will also be lots of actions to choose from, depending on the situation; this might or might not be ideal. When sequencing activities, there is not much room for freedom, the relevant activities will be done in a certain order, no questions asked. 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. Metaphorically speaking, the timeline can be seen as a railroad, at every halt, the train comes to a stop and performs certain activities, which allows the train to move its merry way. Different halts require different activities to take place, therefore there are multiple types of activities that are used in a use case map, the different types are:
A sequential execution of activities means that all activities are done one after another. The next activity can't be started until the previous activity has been completed. In the context of flood protection, it could be the case that a dike has to be heightened, after that has been done, a test can be ran; but the test can't be performed until the dike has been heightened.
A conditional execution means that a certain condition has to be met before an activity can start. For example it could be that an activity is to construct a dike, but before that can happen, money needs to be raised. The condition in the case is: Half a million euros are required. The activity 'build a dike' can't start until this condition has been met.
Parallel activities are executed alongside each other; this means that both of the activities will be executed at the same time, running parallel. For example; while building a dike, it's also possible to finish certain paperwork, it wouldn't make sense to wait until everything is done to finish this, so they are executed simultaneously. This does not necessarily mean that both activities have to work towards the same goal.
Last but not least, there's the wait activity. A wait activity is an activity that relies on the output of other activities to continue. The activity can already start before relying on the output, but after a while the activity will come to a halt; requiring certain facilitation. This facilitation will come from another activity, for example: A dike is being built, but certain permits have not yet been granted, bringing a temporal halt to the construction. Once the permit has been granted, the building can start again. Thus, the activity is waiting for external input.
<<image to be added>>
Alternative visualisation
Before alternative visualisations can be decided, it's first essential to find the flaws in the current visualisation, so it can be improved upon. This analysis still has to take place.
