Emotions Shown to Requirements Changes by Software Developers Across the World
This form is intended to collect your feedback on what is presented through the visualisation only. This does not involve any formal research activity, and your participation is voluntary. Feel free to share your contact details through the last question if you like to participate in any of our research works.

Many thanks for your feedback!
Sign in to Google to save your progress. Learn more
Definition: A requirements changes can be an addition/deletion/modification/combination of functional/non-functional requirements represented in any forms such as a user story/use case.
Do you find this finding useful? *
Why do you think so?
If you are a software developer/practitioner, do you feel any other emotions than is presented in the visualisation, when handling requirements changes? *
If not, what other emotions do you feel when handling requirements changes?
Anything else you like us to study/anything else you want to share?
I am a: *
(Select multiple options if you are playing more than one role)
If you like to be interviewed/participate in any of our coming surveys, feel free to drop your contact details below.
Clear form
Never submit passwords through Google Forms.
This form was created inside of Monash University. Report Abuse