Some software engineering researchers believe UX is yet another software quality (i.e. quality requirement or non-functional requirement-e.g. security, performance), or yet another 'cross-cutting concern'-e.g. architecture.
Therefore, these researchers believe the field of software engineering already has investigated and offered solutions how to deal with UX: follow what the field has to say about quality requirements/cross-cutting concerns. This also means that in their view software engineering practitioners can themselves approach UX from this perspective and achieve a good UX in their products.
Although, of course there are similarities between UX and quality requirements or cross-cutting concerns, I think there are major differences as well. One difference for instance is that basically anyone 'thinks' they can have an opinion about UX, because all of us have experiences each and everyday. This is while there are only few of us that dare to give opinion about 'architecture', quality requirements such as security.
My question is: what are similarities and difference between UX and quality requirements and between UX and other cross-cutting concerns?
I appreciate if you share reference that have touched this topic in general, or have touched part of it: e.g. compared UX to one quality requirement.
In my view, clarifying these similarities and differences helps 'software engineers' get a better view on UX, and appreciate the ongoing research in the field of UX more.