Quality Goals Make the Difference
by Peter Wagner, Uwe Neukam
ISO 25010 has been proven to be a suitable and successful model to define the quality goals of a software system. Based on them you are able to develop a suitable architecture.
However we need quality goals first – and neither product owners nor architects are keen on developing them and formulating them according to SMART criteria.
In our day-to-day project work, we often come across statements such as ‘we don’t need quality now, we’ll do that later’ or ‘everyone knows: security and a good user experience is essential and of course our cloud services have to run 24/7.’
That is not enough – we’ll tell you about some projects for which the architectures were initially developed without taking quality goals into account, what consequences this had and how the architecture changed after the definition of quality goals.
Afterwards we want to discuss whether this is only a phenomenon at our company and what we as architects can do to avoid it.
