Method: Difference between revisions
Jump to navigation
Jump to search
(answer updated) |
(→Answer: updated reflecting ovariable structure) |
||
Line 14: | Line 14: | ||
==Answer== | ==Answer== | ||
Methods are typically [[ovariable]]s that contain case-specific dependencies. Their names are given in the dependencies, but the output cannot be calculated until the method is used in some assessment where the outputs of these case-specific ovariables are known. | |||
In contrast, methods commonly contain generic inputs, such as emission or unit factors, for calculating the output. These inputs are given in the Rationale/Input of the method. | |||
{| {{prettytable}} | {| {{prettytable}} | ||
|+''' | |+'''The attributes of a method. | ||
!Attribute | !Attribute | ||
!Subattribute | !Subattribute | ||
Line 28: | Line 32: | ||
| | | | ||
*Purpose | *Purpose | ||
*Boundaries | *Boundaries | ||
| | | Subattributes are not often needed as titles, because texts are short. | ||
|---- | |---- | ||
|'''Answer | |'''Answer | ||
| | | | ||
* Procedure | * Procedure: An example R code for ''using'' the ovariable, or other detailed instructions for the actual work. | ||
* Management | * Management: Instructions, tools, or software that make the actual work easier | ||
| | | | ||
Subattributes are not often needed as titles, because texts are short. | |||
|---- | |---- | ||
|'''Rationale | |'''Rationale | ||
| | | | ||
*Input | *Input: Typically a data table for e.g. unit factors and other inputs needed by the method ovariable. | ||
* | *Computing: R code for ''defining'' the ovariable. | ||
* | *Output: Description of output, e.g. units and formats used. | ||
*Rationale: why the presented procedure fulfills the purpose. | |||
| Computing could and maybe should be in Answer. However, it is easier for the user that only one R code, the one she has to use in an assessment, is in Answer. | |||
* | |||
|} | |} | ||
Revision as of 12:36, 16 October 2012
Moderator:Nobody (see all) Click here to sign up. |
|
Upload data
|
<section begin=glossary />
- Method is a systematic procedure for a particular information manipulation process that is needed as a part of an assessment work. Typically, a method is a "how-to-do" instruction to calculate a variable; it is used if the dependencies of the variable are unknown until an assessment is executed. In other words, methods can be used to calculate variables within assessments in situations where it is not practical or possible to calculate variables outside an assessment. In these cases, the method page is used within an assessment (e.g. in the dependencies slot) as if it was the variable that it is used to calculate. Method is the basic building block for describing the assessment work (not reality, like the other universal objects). Some methods can be about managing other methods.
<section end=glossary />
Question
What is a structure for a method such that it
- applies to any method that may be needed in any assessment work,
- enables a detailed enough description so that the work can be performed based on it,
- complies with the structure of the universal objects.
Answer
Methods are typically ovariables that contain case-specific dependencies. Their names are given in the dependencies, but the output cannot be calculated until the method is used in some assessment where the outputs of these case-specific ovariables are known.
In contrast, methods commonly contain generic inputs, such as emission or unit factors, for calculating the output. These inputs are given in the Rationale/Input of the method.
Attribute | Subattribute | Comments |
---|---|---|
Name | An identifier | |
Question |
|
Subattributes are not often needed as titles, because texts are short. |
Answer |
|
Subattributes are not often needed as titles, because texts are short. |
Rationale |
|
Computing could and maybe should be in Answer. However, it is easier for the user that only one R code, the one she has to use in an assessment, is in Answer. |
See also
References
Related files
<mfanonymousfilelist></mfanonymousfilelist>