Difference between revisions of "Help talk:Assessment toolbox"

From Testiwiki
Jump to: navigation, search
m (Assumption 6)
(comments to Mikko's comments)
Line 13: Line 13:
  
 
{{discussion
 
{{discussion
|Dispute= Variable validation using data about the variable
+
|Dispute= "Variable validation using data about the variable" is inconsistent.
|Outcome= Under discussion (to be changed when a conclusion is found)
+
|Outcome= Agreed and the text changed accordingly.
 
|Argumentation =
 
|Argumentation =
{{attack|#1: |The variable validation should be done using data about the part of reality that the variable intends to describe, not data about the variable itself. After all, the variable itself is merely an object describing reality that is created in order to make it easier to operate with the information we have about the reality, it is not the same as reality.|--[[User:Mikko Pohjola|Mikko Pohjola]] 07:05, 18 December 2007 (EET)}}
+
{{defend|#1: |The variable validation should be done using data about the part of reality that the variable intends to describe, not data about the variable itself. After all, the variable itself is merely an object describing reality that is created in order to make it easier to operate with the information we have about the reality, it is not the same as reality.|--[[User:Mikko Pohjola|Mikko Pohjola]] 07:05, 18 December 2007 (EET)}}
 +
:{{defend|#2: |I agree.|--[[User:Jouni|Jouni]] 13:50, 18 December 2007 (EET)}}
 
}}
 
}}
  
Line 22: Line 23:
  
 
{{discussion
 
{{discussion
|Dispute= Should we call the theory, methods and toolbox to cover
+
|Dispute= We should we call the theory, methods, and toolbox to cover risk assessment. All suggested alternatives are
*Risk assessment?
+
*A Risk assessment
*Impact assessment?
+
*B Impact assessment
*Integrated assessment?
+
*C Integrated assessment
*All of the above?
+
*D All of the above
*just plainly ''Assessment''?
+
*E Just plainly ''Assessment''
 +
*F Open assessment
 
|Outcome= Under discussion (to be changed when a conclusion is found)
 
|Outcome= Under discussion (to be changed when a conclusion is found)
 
|Argumentation =
 
|Argumentation =
{{defend|#1: |E is the best option. All of the more or less established terms mentioned above are already somewhat fixed (although varyingly) in different people's minds. Using any of these terms to describe something that is meant to be broader than any of them just tends to lead to confusion and resistance to change among people who already possess some (fixed?) interpretation of these terms.|--[[User:Mikko Pohjola|Mikko Pohjola]] 07:05, 18 December 2007 (EET)}}}}
+
{{attack|#1: |E is the best option. All of the more or less established terms mentioned above are already somewhat fixed (although varyingly) in different people's minds. Using any of these terms to describe something that is meant to be broader than any of them just tends to lead to confusion and resistance to change among people who already possess some (fixed?) interpretation of these terms.|--[[User:Mikko Pohjola|Mikko Pohjola]] 07:05, 18 December 2007 (EET)}}
 +
 
 +
{{attack|#2: |F is the best option, if we agree that openness in participation and collaborative work are important in the toolbox. It is a new term and therefore does not have an existing (too narrow) scope).|--[[User:Jouni|Jouni]] 13:50, 18 December 2007 (EET)}}
 +
}}

Revision as of 11:50, 18 December 2007

Assumption 1

How to read discussions

Statements:

Resolution: Resolution not yet found.

(A stable resolution, when found, should be updated to the main page.)

Argumentation:

#1: : Using causal diagrams means describing the risk situations as states of entities, as (so called event-medium composite) objects and their properties, given their causal relations. Flow charts consist of process objects and mass flows without explicit description of causalities, and mind maps allow for all kinds of relations between any kinds of objects. Flow charts and mind maps are thus incoherent with causal diagrams and should be not allowed as alternative means alongside causal diagrams. Also, it is primarily the understanding of causalities between phenomena that is striven for in carrying out assessments, which is a strong argument for using causal diagrams. --Mikko Pohjola 07:05, 18 December 2007 (EET)

#2: : There are no objections for using mind maps and/or flow charts in organizing ones thinking in relation to risk situations, if seen applicable or necessary. The understanding created with using mind maps and flow charts should anyhow be translated into the form of a causal diagram for a proper description about the issue. --Mikko Pohjola 07:05, 18 December 2007 (EET)


Assumption 4

How to read discussions

Statements:

Resolution: Resolution not yet found.

(A stable resolution, when found, should be updated to the main page.)

Argumentation:

#1: : The variable validation should be done using data about the part of reality that the variable intends to describe, not data about the variable itself. After all, the variable itself is merely an object describing reality that is created in order to make it easier to operate with the information we have about the reality, it is not the same as reality. --Mikko Pohjola 07:05, 18 December 2007 (EET)

#2: : I agree. --Jouni 13:50, 18 December 2007 (EET)


Assumption 6

How to read discussions

Statements:

Resolution: Resolution not yet found.

(A stable resolution, when found, should be updated to the main page.)

Argumentation:

#1: : E is the best option. All of the more or less established terms mentioned above are already somewhat fixed (although varyingly) in different people's minds. Using any of these terms to describe something that is meant to be broader than any of them just tends to lead to confusion and resistance to change among people who already possess some (fixed?) interpretation of these terms. --Mikko Pohjola 07:05, 18 December 2007 (EET)

#2: : F is the best option, if we agree that openness in participation and collaborative work are important in the toolbox. It is a new term and therefore does not have an existing (too narrow) scope). --Jouni 13:50, 18 December 2007 (EET)