Three Categories of Context-Aware Systems

Composite Public Values and Software Specifications

“…As the figure suggests, it is not only the requirements specification [1] but also the operationalization of atomic values [9], that are needed as input for the (software) system design -we refer to the conclusion of Shishkov & Mendling that it is "important to clearly distinguish values from requirements and acknowledge the limitations of requirements engineering with regard to the development of value-sensitive software systems" [10]. For this reason we do not consider the operationalization of values as part of the requirements specification, as seen from the figure.…”

“…Whereas, atomic values are weave-able in the (software) design, as studied by Shishkov et al [8,9,10], they are claimed to be not very "instrumental" as it concerns social feedback. In our view that is because most of those values (such as privacy, transparency, accountability, and so on) are to be considered in a particular context [8,9,11].…”

“…In our view that is because most of those values (such as privacy, transparency, accountability, and so on) are to be considered in a particular context [8,9,11]. Then people consider them differently depending on the context.…”

“…Even though the value concept (assuming atomic values) is crucial with regard to this work, we are not presenting and discussing ATOMIC values in the current paper because this is done in other papers from the current proceedings -hence, we refer readers to [9,10].…”

“…Therefore, studying in general what somebody's attitude is towards privacy (for example), could be of limited use. For this reason, we argue that atomic values could only be adequately operationalized if this concerns context-aware systems [9].…”