Posted by: cAmz on: April 19, 2009
TITLE: A Practical Mechanism for Ethical Risk Assessment-A SoDIS Inspection (Chapter 18)
AMAZON LINK: http://www.amazon.com/Handbook-Information-Computer-Ethics/dp/0471799599/ref=sr_1_1?ie=UTF8&s=books&qid=1233232091&sr=1-1
QUOTATION: In the risk sciences, it is common to distinguish between “objective risk” and “subjective risk”.
LEARNING EXPECTATIONS:
- To know the Generic Standards for Risk Analysis Models.
- To know A Practical Mechanism for Ethical Risk Assessment.
- To know what is Sodis Inspection Model.
- To know what happen in UK Election.
- To know the different influences of Sodis Inspection Model.
REACTION:
Issues of risk have given rise to heated debates on what levels of scientific evidence are needed for policy decisions. The proof standards of science are apt to cause difficulties whenever science is applied to practical problems that require standards of proof or evidence other than those of science.
Two major types of errors are possible in a decision whether or not to accept a scientific hypothesis. The first of these consists in concluding that there is a phenomenon or an effect when in fact there is none. This is called an error of type I (false positive). The second consists in missing an existing phenomenon or effect. This is called an error of type II (false negative). In the internal dealings of science, errors of type I are in general regarded as more problematic than those of type II. The common scientific standards of statistical significance substantially reduce the risk of type I errors but do not protect against type II errors.
This chapter talks about or discussed certain models that would help lessen or decrease the risk. This also discusses certain analysis and methods that would help understand and deal with the different risk that would possibly encounter in the world of technology, information and the like. This chapter also discusses about ethical risk and Sodis Inspection model, which illustrates and shows its effects and process.
This chapter covers a lot of topics about risk. And I find it more interesting and challenging. Because we cannot deny the fact those there times and most of the times we encounter risk in all what we do. In connection to this, it only explains that everything that is developed in the cloud or in the net was not always perfect, meaning most of the times users and developers to saw or encounter errors.
LESSON LEARNED:
- The risk identification process identifies potential negative impact on the project and its stakeholders.
- As a support for a quantitative risk analysis, a qualitative analysis is sometimes used. Surprisingly, in standard risk methodologies the qualitative risk approach typically looks at quantifiable data that can be easily prioritized and facilitates analysis.
- The ethical stakeholders in developed software are all those who are affected by it even though they are not directly related to the use or financing of a system.
INTEGRATIVE QUESTIONS:
