Human values and the design of computer technology
Human values and the design of computer technology
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Agent-oriented software engineering: the state of the art
First international workshop, AOSE 2000 on Agent-oriented software engineering
Redesigning the agents' decision machinery
Affective interactions
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Tropos: An Agent-Oriented Software Development Methodology
Autonomous Agents and Multi-Agent Systems
Proceedings of the 2007 international ACM conference on Supporting group work
Investigating the Role of 'Soft Issues' in the RE Process
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Using three AOSE toolkits to develop a sample design
International Journal of Agent-Oriented Software Engineering
On Non-Functional Requirements in Software Engineering
Conceptual Modeling: Foundations and Applications
The Tropos software development methodology: processes, models and diagrams
AOSE'02 Proceedings of the 3rd international conference on Agent-oriented software engineering III
Architecture-Based Design of Multi-Agent Systems
Architecture-Based Design of Multi-Agent Systems
| Hi-index | 0.00 |
As software plays an increasingly important role in people's lives, the impact it has on their values frequently becomes apparent. Many software design methods address "soft issues", but very few address values explicitly. We present six principles that design methods should meet in order to properly deal with values. One area in which adherence to stakeholder values is important, is Agent-Oriented Software Engineering (AOSE). The Tropos AOSE method, with its concept of soft-goal, comes close to meeting our principles, but does not address values explicitly. Value-Sensitive Design is a methodology that does explicitly address value issues, but it offers little guidance in operationalizing them. We discuss a case study in which we attempt to capture values in Tropos' soft-goals after eliciting them using Value-Sensitive Design. Subsequently, we discuss to what extent Tropos adheres to our principles. Finally, we propose the introduction of values as a first-class entity in Tropos in order to meet our aims of dealing with values.