First steps towards building a dictionary ofemotional requirements in healthcare andwell-being.xlsx

Emotional requirements represent how a user<br>should feel when interacting with a software system.<br>Capturing and addressing these requirements during the<br>early phases of the system design is essential for a successful<br>system as it improves the system’s acceptance. However,<br>this is not an easy task because stakeholders express<br>the desired emotional requirements using very different<br>terminology and expressions, which may result in confusion<br>and inconsistency between what a stakeholder says and<br>what a requirement engineer understands. Specifically,<br>there is a lack of a standardized approach to understand<br>and capture such requirements. This paper aims to solve<br>this problem by developing a standardized dictionary of<br>emotional requirements that offers a clear and organized<br>set of terms, which can be used to properly elicit stakehold-<br>ers’ emotions considering the healthcare and well-being<br>domain as a disclosure domain.