Software architects' experiences of quality requirements: what we know and what we do not know?

摘要: [Context/motivation] Quality requirements (QRs) are a concern of both requirement engineering (RE) specialists and software architects (SAs). However, the majority empirical studies on QRs take RE analysts'/clients' perspectives, only recently very few included SAs' perspective. As result, (i) relatively little is known about involvement in their coping strategies, (ii) whatever mostly comes from small midsized projects. [Question/problem] The question this exploratory study how SAs cope with context large contract-based system delivery [Principal ideas/results] We executed an case 20 interest. key results indicate role play engineering, type communication processes involved in, ways discovered, documented, quantified, validated negotiated. Our most important findings that contexts: (1) approached same due diligence as functional architecture design demand, (2) act proactively embrace responsibilities over QRs, (3) willingness to pay affordability seem prioritization criteria cost benefits do, (4) perceived social activity not much tool method centric activity. [Contribution] main contributions paper explication process perspective, comparison our previously published results.